Tivoli Manager for R/3 User s Guide - IBMpublib.boulder.ibm.com/tividd/td/r3/GC31-8411-05/... · Uninstalling Tivoli Manager for R/3 ..... 22 Chapter 3. Getting Started with Tivoli

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

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

Tivoli Manager for R/3 User’s Guide

Copyright Notice

© Copyright IBM Corporation 1997, 2001. All rights reserved. May only be used pursuant to a TivoliSystems Software License Agreement, an IBM Software License Agreement, or Addendum for TivoliProducts to IBM Customer 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 anyform or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise,without prior written permission of IBM Corporation. IBM Corporation grants you limited permissionto make hardcopy or other reproductions of any machine-readable documentation for your own use,provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rightsunder copyright are granted without prior written permission of IBM Corporation. The document is notintended for production and is furnished “as is” without warranty of any kind. All warranties on thisdocument are hereby disclaimed, including the warranties of merchantability and fitness for aparticular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, DB2, and Tivoli Enterprise Console are trademarks orregistered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in theUnited States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation inthe United States, other countries, or both.

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

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not implythat they will be available in all countries in which Tivoli Systems or IBM operates. Any reference tothese products, programs, or services is not intended to imply that only Tivoli Systems or IBMproducts, programs, or services can be used. Subject to valid intellectual property or other legallyprotectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or servicecan be used instead of the referenced product, program, or service. The evaluation and verification ofoperation in conjunction with other products, except those expressly designated by Tivoli Systems orIBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patentapplications covering subject matter in this document. The furnishing of this document does not giveyou 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

What This Guide Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Tivoli Manager for R/3 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Accessing Publications on the Product CD . . . . . . . . . . . . . . . . . . . . . xix

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Conventions Used in This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Typeface Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

Operating System-dependent Variables and Paths . . . . . . . . . . . . . . . . xxi

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

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

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

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

R/3 Alert Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

R/3 CCMS Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

R/3 Syslog Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

R/3 IDOC Event Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Monitoring Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Event Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Event Server Rule Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

iiiTivoli Manager for R/3 User’s Guide

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

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

Automated R/3 SAPGUI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Security Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Policy Region Resource Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Providing Secure External Communication . . . . . . . . . . . . . . . . . . 7

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

Tivoli Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Tivoli Manager for R/3 Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

User Interface Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Using the Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Using Tivoli Business Systems Manager . . . . . . . . . . . . . . . . . . . . 8

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

Chapter 2. Planning for and Installing Tivoli Managerfor R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Where to Install Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

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

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

Installing Application Proxy Version 1.1 . . . . . . . . . . . . . . . . . . . 12

Upgrading to Application Proxy 1.1 . . . . . . . . . . . . . . . . . . . . . . . 13

Installing the Application Proxy Patch . . . . . . . . . . . . . . . . . . . . . 13

Planning for Event Server Configuration . . . . . . . . . . . . . . . . . . . . . . . 14

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

Upgrading to Version 2.2.0 from Version 1.5 or 1.5.1. . . . . . . . . . . . . . 16

Upgrading to Version 2.2.0 from Version 2.0 . . . . . . . . . . . . . . . . . . . . 17

Upgrading to Version 2.2.0 from Version 2.1 . . . . . . . . . . . . . . . . . . . . 18

Installing Tivoli Manager for R/3 Version 2.2.0 . . . . . . . . . . . . . . . . . . 19

iv User’s Guide Version 2.2.0

Uninstalling Tivoli Manager for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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

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

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

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

Using Tivoli 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 . . . . . . . . . . . . . . . . . . . . . . . 43

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

Copying the Transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Importing the Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

From the Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Using the Transport Management System. . . . . . . . . . . . . . . . . . . . . . . 49

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

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

Chapter 5. Configuring Tivoli 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

Configuring Automatic Discovery for Data Sharing . . . . . . . . . . . 56

vTivoli Manager for R/3 User’s Guide

Scheduling Automatic Discovery . . . . . . . . . . . . . . . . . . . . . . . . . 57

Scheduling Automatic Discovery for Windows. . . . . . . . . . . . . 58

Scheduling Automatic Discovery for UNIX . . . . . . . . . . . . . . . 59

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

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

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

Creating an Application Server Object from the Desktop . . . . . . . 61

Creating a Database Server Object from the Desktop . . . . . . . . . . 62

Creating an ITS Server Object from the Desktop . . . . . . . . . . . . . 63

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

Result of Creating an R/3 System Object . . . . . . . . . . . . . . . . . . . 64

Result of Creating an R/3 Application Server Object . . . . . . . . . . 65

Result of Creating an R/3 Database Server Object . . . . . . . . . . . . 66

Result of Creating an R/3 ITS Server Object . . . . . . . . . . . . . . . . 67

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 Tivoli Manager for R/3 for Windows . . . . . . . . . . . . . . . . . . . . 72

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

Example of a Start Exit Routine for an Oracle Database . . . . . . . 73

Example of a Stop Exit Routine for an Oracle Database. . . . . . . . 73

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

Enabling Automatic Discovery for Windows . . . . . . . . . . . . . . . . . . . . 74

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

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

vi User’s Guide Version 2.2.0

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

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

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

Configuring Tivoli Manager for R/3 for OS/390. . . . . . . . . . . . . . . . . . . . . . 77

R/3 Release Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

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

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

Data Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

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

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

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

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

Configuring a Version 3.6 Event Console. . . . . . . . . . . . . . . . . . . . . . . 83

Configuring a Version 3.7 Event Console. . . . . . . . . . . . . . . . . . . . . . . 85

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

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

Starting and Stopping an Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

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

Using the CCMS Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

How the CCMS Event Adapter Works . . . . . . . . . . . . . . . . . . . . . . . . . 89

Viewing and Intepreting Alert Events. . . . . . . . . . . . . . . . . . . . . . . . . . 91

Customizing the CCMS Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . 91

Changing the Monitoring Set and Monitor to Observe . . . . . . . . . 92

Controlling the Number of Alerts to Report . . . . . . . . . . . . . . . . . 92

Controlling Automatic Closing of Alerts in CCMS . . . . . . . . . . . . 93

Adding Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Using the Syslog Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

viiTivoli Manager for R/3 User’s Guide

Controlling Syslog Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Modifying Entries in the r3slogIID.cl File . . . . . . . . . . . . . . . . . . 96

Adding New Entries to the r3slogIID.cl File . . . . . . . . . . . . . . . . 96

Example of Controlling Syslog Events . . . . . . . . . . . . . . . . . . . . . . . . . 97

Using the IDOC Event Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

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

Viewing and Interpreting IDOC Events . . . . . . . . . . . . . . . . . . . . . . . 100

Interpreting SAP_IDOC_STATUS Events. . . . . . . . . . . . . . . . . . 101

Interpreting SAP_IDOC_XMIT Events. . . . . . . . . . . . . . . . . . . . 102

Controlling IDOC Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Filtering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 7. Monitoring R/3 Resources. . . . . . . . . . . . . . . . . . 109Monitoring Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Monitoring Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

R3 ITS Server Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

R3 Server Remote and R3 Server Central Monitors . . . . . . . . . . . . . . 111

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

Default Profile Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

R3 App Server Monitors Profile Manager. . . . . . . . . . . . . . . . . . . . . . 114

R3 DB Server Monitors Profile Manager . . . . . . . . . . . . . . . . . . . . . . 114

R3 Distributed Daemon Monitors Profile Manager . . . . . . . . . . . . . . . 115

R3 Managed Nodes Monitors Profile Manager . . . . . . . . . . . . . . . . . . 115

R3 ITS Monitors Profile Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

R3 Central Instance Monitors Profile Manager . . . . . . . . . . . . . . . . . . 116

Using Monitoring Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Using the Application Server Status Monitor . . . . . . . . . . . . . . . . . . . 117

viii User’s Guide Version 2.2.0

Using the Storage Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Using the Performance Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Using the File System Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

UNIX File System Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Windows NT File System Monitors . . . . . . . . . . . . . . . . . . . . . . 121

Using the User Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Using the Work Process Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Using the Work Process Monitor . . . . . . . . . . . . . . . . . . . . . . . . 123

Using the Work Process Dispatch Queue Monitor. . . . . . . . . . . . 124

Using the Long Running Work Process Monitor. . . . . . . . . . . . . 124

Using the Cancelled Job Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

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

OS Collect - Application Server . . . . . . . . . . . . . . . . . . . . . . . . . 127

OS Collect - Database Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 128

OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

OS/390 DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

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

R3 System Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Controlling the R/3 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

R3 App Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Controlling Event Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Controlling Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Displaying Application Server Performance Information . . . . . . . . . . . 138

Managing Batch Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Controlling R/3 Work Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

R3 DB Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Controlling a Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Controlling dbaccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

ixTivoli Manager for R/3 User’s Guide

R3 ITS Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Controlling ITS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

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

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

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

Distributing SAPGUI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 10. Tivoli Business Systems ManagerInstrumentation for R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Understanding Tivoli Business Systems Manager . . . . . . . . . . . . . . . . . . . . 152

Tivoli Business Systems Manager Management Server . . . . . . . . . . . . 152

Tivoli Business Systems Manager Console . . . . . . . . . . . . . . . . . . . . . 152

Tivoli Business Systems Manager Event Enablement . . . . . . . . . . . . . 153

Tivoli Business Systems Manager Task Server . . . . . . . . . . . . . . . . . . 153

Tivoli Business Systems Manager Event Handling . . . . . . . . . . . . . . . 153

Preparing to Install R/3 Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Installing and Configuring R/3 Instrumentation . . . . . . . . . . . . . . . . . . . . . 154

Installing the R/3 Instrumentation Definition Files . . . . . . . . . . . . . . . 154

Installing the R/3 Instrumentation Task Libraries . . . . . . . . . . . . . . . . 156

Adding the R/3 Instrumentation Rule Set . . . . . . . . . . . . . . . . . . . . . . 157

Instrumented Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

R/3 Instrumentation Desktop Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Synchronizing the Tivoli Business Systems Manager Console with theTivoli Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Deleting R/3 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Navigating to R/3 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Locating and Running R/3 Instrumentation Tasks . . . . . . . . . . . . . . . . . . . . 161

x User’s Guide Version 2.2.0

R3System Component Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

R3Application Component Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

R3Database Component Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

R3ITSServer Component Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Supported Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Viewing the Current Events Status . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Uninstalling R/3 Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Troubleshooting R/3 Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

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

SysMan and RFC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

wr3mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

wr3rfc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Appendix B. Event Classes and Rules. . . . . . . . . . . . . . . . . 183Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

R/3 Alert Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

R/3 Operational Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

R/3 CCMS Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

R/3 Syslog Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

R/3 IDOC Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

Distributed Monitoring Event Classes. . . . . . . . . . . . . . . . . . . . . . . . . 196

Status Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

R/3 Instrumentation Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Tivoli Business Systems Manager Event Classes . . . . . . . . . . . . . . . . 198

Error Event Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Alert Event Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

CCMS Event Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

xiTivoli Manager for R/3 User’s Guide

Syslog Event Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

IDOC Event Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Cancelled Job Event Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

CCMS-Generated Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Rules for Tivoli Manager for R/3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Duplicate Event Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Automatic Closing of Harmless Events . . . . . . . . . . . . . . . . . . . . . . . 207

Automatic Drill-Down (Alert Event Adapter Only). . . . . . . . . . . . . . . 207

Bidirectional Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Event Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Multi-Region Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Integration with Tivoli Business Systems Manager . . . . . . . . . . . . . . . 209

Integration with Tivoli Database Manager Products . . . . . . . . . . . . . . 209

Event Server Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Distributed Monitoring Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Database Status Integration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Correlation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Tivoli Business Systems Manager Instrumentation DistributedMonitoring Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Appendix C. Remote and Central MonitoringSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

OS Collect Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Roll Area Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Page Area Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Work Process Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Work Process Dispatch Queue Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Long Running Work Process Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Buffer Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

xii User’s Guide Version 2.2.0

Performance Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Heap Memory Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Extended Memory Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

User Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

OS/390 DB2 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

OS/390 Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Appendix D. IDOC Status Codes . . . . . . . . . . . . . . . . . . . . . . . 227

Appendix E. Function Module Authorization . . . . . . . . . . 231

Appendix F. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

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

Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Task Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Monitor Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Event Adapter Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Miscellaneous Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Alert Event Adapter Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Error Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Event Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

wr3mib (r3mibIID) Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 282

wr3rfc Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Configuring Monitor Logging Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

SAPGUI File Package Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Display OS Collect Information Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Icon State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

File System Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

xiiiTivoli Manager for R/3 User’s Guide

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

xiv User’s Guide Version 2.2.0

Preface

The Tivoli® Manager for R/3 User’s Guide provides informationabout planning for, installing, and managing R/3 systems with TivoliManager for R/3. This guide describes the tasks and monitors thatTivoli Manager for R/3 provides. It also describes how to distributeSAPGUI 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 Business Systems Manager, TivoliManager for DB2®, and Tivoli Manager for Oracle products.

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

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

Describes the basic features and functions of Tivoli Manager forR/3.

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

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

¶ “Getting Started with Tivoli 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 useTivoli Manager for R/3.

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

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

¶ “Configuring Tivoli 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/3

xvTivoli Manager for R/3 User’s Guide

database servers, and R/3 ITS servers with Tivoli Manager forR/3. This chapter also describes how to configure a remotefunction call and contains information about platform-specificconfiguration tasks.

¶ “Managing R/3 Events” on page 81

Describes how to configure the event server, event consoles, andTivoli Manager for R/3 Alert Event Adapter, CCMS EventAdapter, Syslog Event Adapter, and IDOC Event Adapter.

¶ “Monitoring R/3 Resources” on page 109

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

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

Describes Tivoli Manager for R/3 management tasks.

¶ “Distributing SAPGUI Software” on page 143

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

¶ “Tivoli Business Systems Manager Instrumentation for R/3” onpage 151

Describes how to plan for, install, and configure Tivoli BusinessSystems Manager Instrumentation for R/3 and how to manageR/3 resources from the Tivoli Business Systems Managerconsole.

¶ “Command Line Interface Commands” on page 171

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

¶ “Event Classes and Rules” on page 183

Describes the Tivoli Enterprise Console event classes and rulesdelivered with Tivoli Manager for R/3, slot values for the events,and background information on R/3 alerts.

¶ “Remote and Central Monitoring Sources” on page 215

xvi User’s Guide Version 2.2.0

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

¶ “IDOC Status Codes” on page 227

Describes the IDOC status codes.

¶ “Function Module Authorization” on page 231

Contains a list of the function modules delivered with TivoliManager for R/3 and the R/3 authorization required to run eachmodule.

¶ “Messages” on page 235

Contains a list of the messages produced by Tivoli Manager forR/3.

¶ “Troubleshooting” on page 267

Describes the diagnostic techniques for tasks, monitors, TivoliBusiness Systems Manager Instrumentation, and SAPGUIdistribution. This section describes diagnostic commands andproduct directories.

PublicationsThis section lists publications in the Tivoli Manager for R/3 libraryand any other related documents. It also describes how to accessTivoli publications online, how to order Tivoli publications, and howto make comments on Tivoli publications.

Tivoli Manager for R/3 LibraryThe following documents are available in the Tivoli Manager for R/3library:

¶ Tivoli Manager for R/3 User’s Guide, softcopy only

Provides information about how to manage R/3 systems withTivoli Manager for R/3.

¶ Tivoli Manager for R/3 Release Notes, GI10-3024

Provides information about system requirements andlate-breaking information related to using Tivoli Manager forR/3.

xviiTivoli Manager for R/3 User’s Guide

Related PublicationsThe following publications provide useful information related toTivoli Manager for R/3:

¶ Tivoli Framework User’s Guide

¶ Tivoli Framework Planning and Installation Guide

¶ Tivoli Framework Reference Manual

¶ Tivoli Enterprise Console® Rule Builder’s Guide

¶ Tivoli Enterprise Console User’s Guide

¶ Tivoli Enterprise Console Reference Manual

¶ Tivoli Enterprise Console Event Integration Facility Guide

¶ Tivoli Enterprise Console Adapters Guide

¶ Tivoli Distributed Monitoring User’s Guide

¶ Tivoli Software Distribution User’s Guide

¶ Tivoli Business Systems Manager product documentation

Related publications for Tivoli database manager products include:

¶ Tivoli Manager for DB2 User’s Guide

¶ Tivoli Manager for DB2 Release Notes

¶ Tivoli Manager for Oracle User’s Guide

¶ Tivoli Manager for Oracle Release Notes

Accessing Publications OnlineYou can access many Tivoli publications online at the TivoliCustomer Support Web site:

http://www.tivoli.com/support/documents/

These publications are available in PDF or HTML format, or both.Translated documents are also available for some products.

xviii User’s Guide Version 2.2.0


Accessing Publications on the Product CDThe following .pdf and the .htm documentation files are available onthe Tivoli Manager for R/3 CD in the /DOC directory:

Document Files

Tivoli Manager for R/3 User’sGuide

¶ sa22mst.pdf

¶ sa22msttfrm.htm (framesversion)

¶ sa22mst.htm (non-framesversion)

Note: The Tivoli Manager for R/3 Release Notes is not provided onthe Tivoli Manager for R/3 CD.

Ordering PublicationsYou can order many Tivoli publications online at the following Website:

http://www.ibm.com/shop/publications/order

You can also order by telephone by calling one of these numbers:

¶ In the United States: 800-879-2755

¶ In Canada: 800-426-4968

¶ In other countries, for a list of telephone numbers, see thefollowing Web site:

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoliproducts and documentation, and we welcome your suggestions forimprovements. If you have comments or suggestions about ourproducts and documentation, contact us in one of the followingways:

¶ Send an e-mail to [email protected].

xixTivoli Manager for R/3 User’s Guide

http://www.ibm.com/shop/publications/order

http://www.tivoli.com/inside/store/lit_order.html

¶ Complete our customer feedback survey at the following Website:

http://www.tivoli.com/support/survey/

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contactTivoli Customer Support. See the Tivoli Customer Support Handbookat the following Web site:

http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact TivoliCustomer Support, depending on the severity of your problem, andthe following information:

¶ Registration and eligibility

¶ Telephone numbers and e-mail addresses, depending on thecountry you are in

¶ What information you should gather before contacting support

Conventions Used in This BookThis book uses several conventions for special terms and actions andoperating system-dependent commands and paths.

Typeface ConventionsThe following typeface conventions are used in this book:

Bold Lowercase and mixed-case commands, commandoptions, and flags that appear within text appear likethis, in bold type.

Graphical user interface elements (except for titles ofwindows and dialogs) and names of keys also appearlike this, in bold type.

Italic Variables, values you must provide, new terms, andwords and phrases that are emphasized appear likethis, in italic type.

xx User’s Guide Version 2.2.0

http://www.tivoli.com/support/survey/

http://www.tivoli.com/support/handbook/

Monospace Commands, command options, and flags that appearon a separate line, code examples, output, andmessage text appear like this, in monospace type.

Names of files and directories and text strings youmust type, when they appear within text, also appearlike this, in monospace type.

Operating System-dependent Variables and PathsThis book uses the UNIX convention for specifying environmentvariables and for directory notation.

When using the Windows command line, replace $variable with%variable% for environment variables and replace each forwardslash (/) with a backslash (\) in directory paths.

Note: If you are using the bash shell on a Windows system, you canuse the UNIX conventions.

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.

xxiTivoli Manager for R/3 User’s Guide

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

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.

xxii User’s Guide Version 2.2.0

monitorIn the monitoring architecture, a collection of monitoringtree elements arranged together in a hierarchical monitoringtree.

monitor setIn the monitoring architecture, a collection of monitorsdisplayed in a hierarchical tree. Monitor sets are used togroup together the individual monitors.

monitoring architectureThe R/3 Computer Center Management System (CCMS)monitoring and alert facility used in R/3 releases 4.5B andlater to provide an integrated view of the entire SAPenvironment.

monitoring treeIn the monitoring architecture, a hierarchical tree thatdisplays system components that are monitored by themonitoring architecture.

monitoring tree elementIn the monitoring architecture, a node in the monitoring tree.The three types of monitoring tree elements are: monitoringsummary node, monitoring object, and monitoring attribute.

MTE See monitoring tree element.

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.

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/support/documents/glossary/termsm03.htm.

xxiiiTivoli Manager for R/3 User’s Guide

http://www.tivoli.com/support/documents/glossary/termsm03.htm

The term UNIX in this document includes the AIX, HP-UX, andSolaris platforms.

The term Windows in this document includes the Windows NT andWindows 2000 platforms and does not include the Windows 95/98platforms. References to the Windows 95/98 platforms are identifiedas such.

xxiv User’s Guide Version 2.2.0

Introducing Tivoli Manager forR/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 operating systems. The database servers can runon the UNIX, Windows, and OS/390 operating systems.

The typical Tivoli management environment consists of a Tivolimanagement region server (Tivoli server), a Tivoli EnterpriseConsole server, managed nodes, endpoints, and gateways.

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

¶ To manage at the machine level, Tivoli Manager for R/3 usesmonitors provided with the Tivoli Distributed Monitoringproduct. These monitors provide status on the machines anddaemons.

¶ To manage at the R/3 system level, Tivoli Manager for R/3 usesmonitors, event adapters, and tasks provided with the Tivoli

1

1Tivoli Manager for R/3 User’s Guide

1.In

trod

ucin

gTivo

liM

anag

erfo

rR

/3

Manager for R/3 product. Tivoli Manager for R/3 representseach R/3 system and server as a Tivoli object. Each object is aspecial type of Tivoli endpoint that enables Tivoli Manager forR/3 to distribute monitors and tasks directly to the endpoint. Aswith any Tivoli endpoint, you can run a task against one or moreapplication servers across the R/3 systems that the Tivoli servermanages. For more information, see “Tivoli Manager for R/3Object Endpoints” on page 29.

Tivoli Manager for R/3 provides four event adapters that run on R/3application servers. Two of these event adapters, the Alert EventAdapter and the Syslog Event Adapter, must be configured for eachR/3 application server. The other two event adapters, the IDOCEvent Adapter and the CCMS Event Adapter, must be configured foronly one R/3 application server in each R/3 system.

R/3 application servers are the primary resources used by TivoliManager for R/3 in managing the R/3 system. The applicationservers provide management information about themselves. Inaddition, the application servers are gateways for collecting R/3database server information. Tivoli Manager for R/3 obtainsperformance information about the R/3 database server through callsmade to one of the R/3 application servers, which allows TivoliManager for R/3 to gather database information for all platforms,including DB2 on OS/390.

Tivoli Manager for R/3 FunctionsTivoli Manager 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

2 User’s Guide Version 2.2.0

¶ R/3 release compatibility

¶ User interface options

¶ Integration with Tivoli database manager products

Availability ManagementWith Tivoli Manager for R/3, you can monitor and retrieve R/3alerts using the Alert Event Adapter for R/3 releases up to andincluding 4.0B and the CCMS Event Adapter for R/3 releases 4.5Band later. You can also monitor R/3 syslog messages using theSyslog Event Adapter, and you can monitor the transfer of businessdata from one R/3 system to another using the IDOC Event Adapter.With the monitoring collections, you can monitor R/3 applicationservers, Internet transaction servers (R/3 ITS servers), and R/3 filesystems and daemons. When so configured, events are forwarded toan event server for display and processing. You can use the filteringcapabilities to send specific events to the event console. TivoliManager 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 AdapterFor R/3 releases up to and including 4.0B, R/3 uses an alert facilitythat monitors various resources in the R/3 system and notifiesadministrators of potential problems. R/3 publishes some of thisinformation through its System Management (SysMan) interface.Tivoli Manager for R/3 provides the Alert Event Adapter to querythe SysMan interface for R/3 alerts and to convert the R/3 alert trapsinto Tivoli Enterprise Console events.

R/3 CCMS Event AdapterFor R/3 releases 4.5B and later, the CCMS Monitoring Architectureis used to monitor many resources in the R/3 system and to notifyadministrators of potential problems. Tivoli Manager for R/3provides the CCMS Event Adapter to query the CCMS MonitoringArchitecture for R/3 alerts and to convert the R/3 alerts into TivoliEnterprise Console events.


1.In

trod

ucin

gTivo

liM

anag

erfo

rR

/3

R/3 Syslog Event AdapterTivoli Manager for R/3 provides an event adapter that processes theR/3 syslog and converts new entries into Tivoli Enterprise Consoleevents.

R/3 IDOC Event AdapterTivoli Manager for R/3 provides an event adapter that monitors SAPIntermediate Documents (IDOCs) for error status codes and reportsthem as Tivoli Enterprise Console events. R/3 systems use IDOCs totransfer business data between business systems. A business systemcan be an R/3 system or a customer application. Successful transferof IDOCs is crucial to ensure that all R/3 systems are synchronizedon the business data they are processing.

Monitoring CollectionsTivoli Manager for R/3 supplies a set of monitoring collections thatprovide monitors for R/3 resources. These Tivoli DistributedMonitoring collections provide a wide range of internal and externalR/3 monitors, 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. Tivoli 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 Tivoli Enterprise Console events. See “MonitoringR/3 Resources” on page 109 for more information.

Event ConsoleThe event console provides a consolidated event view for one ormore R/3 systems, so that you can create and configure differentviews for any number of R/3 administrators and R/3 systems.

Event Server Rule BaseThe event server rule base provides intelligent event processing andcorrelation. The Tivoli Manager for R/3 Tivoli Enterprise Consolerule sets can be extended to meet local processing requirements. TheTivoli Enterprise Console Rule Builder’s Guide describes anon-programming environment for extending the functionality of the


rule sets. For example, you can easily automate the gathering ofadditional diagnostics for a specific event by specifying the triggerevent and the desired task.

The Tivoli Manager for R/3 provides rules that enable thesefunctions:

¶ Duplicate event checking

¶ Automatic closing of harmless events

¶ Automatic drill-down

¶ Bidirectional communication

¶ Event correlation

¶ Multi-region support

¶ Integration with Tivoli Business Systems Manager


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

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

Task LibrariesTivoli Manager 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 configureTivoli Manager for R/3 to meet the unique needs of each R/3 systembeing managed. See “R3 Configuration Tasks” on page 36 and“Tasks for Managing R/3 Resources” on page 131 for moreinformation about these tasks.


1.In

trod

ucin

gTivo

liM

anag

erfo

rR

/3

Automated R/3 SAPGUI InstallationThe R/3 presentation software, also known as the SAP graphical userinterface (SAPGUI), runs on UNIX systems (with the Motif windowmanager), Windows systems, and Windows 95/98 systems. TivoliManager for R/3 enables you to create a customized SAPGUIinstallation file package. The installation of the SAPGUI filepackage 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 the Tivoli 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:

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


example, 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 RolesTivoli Manager for R/3 configures each R/3 system as its own policyregion. In addition, Tivoli 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 Tivoli Manager for R/3 uses thisR/3 user ID and password for remote function call (RFC) processes.The password is stored in encrypted form. The Tivoli Manager forR/3 access program obtains the user ID and password as needed toaccess the RFC functions and the corresponding Advanced BusinessApplication Programming (ABAP) function modules.

ExtensibilityExtensibility is provided by the Tivoli Framework and TivoliManager for R/3 tools, monitoring collections (see “MonitoringCollections” on page 4), and event server rule sets (see “EventServer Rule Base” on page 4).

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

Tivoli Manager for R/3 ToolTivoli Manager for R/3 provides a powerful tool in the wr3rfcprogram when run as a command. The wr3rfc runs the R/3 function


1.In

trod

ucin

gTivo

liM

anag

erfo

rR

/3

modules that support the RFC interface. You can use this commandto manage the R/3 environment. (See “Command Line InterfaceCommands” on page 171.)

R/3 Release and System CompatibilityTivoli Manager for R/3 supports multiple R/3 systems and releases.These systems can be at different R/3 release levels. Tivoli Managerfor R/3 also supports multiple R/3 releases for distribution of theSAPGUI software and multiple R/3 ITS server release levels. Seethe Tivoli Manager for R/3 Release Notes for the release levels thatare supported.

User Interface OptionsTivoli software offers a choice of user interface options: Tivolidesktop or Tivoli Business Systems Manager workstation. Thisdocument, in general, provides procedures and screen illustrationsusing 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.

Using Tivoli Business Systems ManagerTivoli Business Systems Manager provides a GUI that representsmanaged resources in a business-systems view. This alternative viewgives administrators a way to view not only managed resources buttheir relationships with each other. (See “Tivoli Business SystemsManager Instrumentation for R/3” on page 151.)

Integration with Tivoli Database Manager ProductsIf you have the Tivoli Manager for DB2 or the Tivoli Manager forOracle installed, Tivoli 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 Installing TivoliManager for R/3

This chapter describes the requirements you must meet before youinstall Tivoli Manager for R/3. It describes how to install TivoliManager for R/3, and it also describes how to uninstall TivoliManager for R/3. If Tivoli Business Systems Manager is installed,you can optionally install Tivoli Business Systems ManagerInstrumentation for R/3. See “Tivoli Business Systems ManagerInstrumentation for R/3” on page 151.

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

¶ The Tivoli management region server (Tivoli server)

¶ The Tivoli Enterprise Console server that processes TivoliManager 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 (for endpoint support)

Installation RequirementsBefore you install the Tivoli Manager for R/3, you must meet thefollowing requirements:

2


2.P

lann

ing

and

Installin

g

1. Ensure that you are running on a supported operating system andthat you install all prerequisite software. Refer to the TivoliManager for R/3 Release Notes for details about supportedhardware and operating systems, prerequisite software, and diskspace requirements.

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

3. If you are running R/3 application servers on endpoints, ensurethat the endpoints and gateways are properly configured andfunctional. Refer to the Tivoli Framework Planning andInstallation Guide.

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

5. Configure the event server. See “Planning for Event ServerConfiguration” on page 14.

6. Optionally, if you manage R/3 resources with Tivoli BusinessSystems Manager, see “Tivoli Business Systems ManagerInstrumentation for R/3” on page 151 for installationrequirements. Also, ensure that the Tivoli Business SystemsManager server is configured and the Tivoli Business SystemsManager consoles are installed.

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

Configuring Tivoli Management RegionsBefore installing the Tivoli Manager for R/3, configure the region tocontain the Tivoli server, the 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 good


model for defining a region boundary. Region boundaries areimportant because of the relationship with event server boundaries; aregion can have only one event server.

You can manage multiple R/3 systems in a single region. These R/3systems can be used for development, test, and production. However,because production systems are so critical to an enterprise’sbusiness, consider placing production systems in their own regions.

When multiple R/3 systems are in the same region, events from allsystems go to the same event server. Separating production eventsfrom test and development events is another reason to put productionsystems in their own region.

Refer to the Tivoli Management Framework User’s Guide for moreinformation about configuring regions.

If you are planning to use gateways to manage endpoints and youare concerned about gateway failure, see “Deciding Where to CreateR/3 Objects” on page 54 for additional planning 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 TivoliManager for R/3. This section describes how to install ApplicationProxy 1.1 if you do not already have it installed. This section alsodescribes how to upgrade to Application Proxy 1.1 if you haveApplication Proxy 1.0 installed, and it describes how to install therequired Application Proxy patch. The following table lists thecontext and authorization roles required to install or upgrade theApplication Proxy:

Activity Context Required Role

Install or upgrade theApplication Proxy

Tivoli desktop install_product

Install the ApplicationProxy patch



2.P

lann

ing

and

Installin

g

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

1. From the Desktop menu, select Install –> Install Product todisplay the Install Product dialog.

2. Click Select Media to 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 Tivoli 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. Select ApplicationProxy, 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 andclick the right arrow button to move them to the AvailableClients list.

Note: Install the Application Proxy on the following machines:

¶ Tivoli server

¶ 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 Upgrade as a patch. Followthese steps:

1. From the Desktop menu on the Tivoli desktop, select Install –>Install Patch. The ApplicationProxy, Version 1.1 Upgrade islocated in the /APXYUPGD directory on the Tivoli Manager forR/3 CD.

Note: Install the ApplicationProxy, Version 1.1 Upgrade patch oneach machine on which you installed Application Proxy1.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 the Desktopmenu on the Tivoli desktop, select Install –> Install Patch. Thepatch is located in the /APXYPTCH directory on the Tivoli Managerfor R/3 CD. For information about the Application Proxy patch thatis required, refer to the Tivoli 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 Tivoli 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.


2.P

lann

ing

and

Installin

g

Planning for Event Server ConfigurationFor each configuration, the Tivoli Manager for R/3 Alert EventAdapter, CCMS Event Adapter, Syslog Event Adapter, and IDOCEvent Adapter send their events to the configured event serverregardless of the region in which the event server is located. For theAlert Event Adapter, additional drill-down processing is performed.Drill-down processing sends events using either Tivoli object calls orthe Tivoli wpostemsg command, depending on the type of endpointoriginating the event.

You can configure event servers in several ways:

¶ One region and one event server

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

¶ Multiple regions and multiple event servers

In this configuration, each region is assumed to have its ownevent server. Each event server receives all events from its localregion. Optionally, you can configure a event server toautomatically forward events to another event server in anotherregion. See “Configuring the Event Server” on page 82.

¶ Multiple regions and one event server

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

v If you want to collect Tivoli Manager for R/3 events onlyfrom managed nodes, you need to install the Tivoli EnterpriseConsole product in every region even though the event serverwill be active in only one region. Installing the TivoliEnterprise Console product in every region provides theinfrastructure needed by Tivoli Manager for R/3 to sendevents using Tivoli object calls. Resources must be sharedbetween the regions.

v If you want to collect Tivoli Manager for R/3 events onlyfrom endpoints, you need to install the Tivoli EnterpriseConsole product only in the region hosting the event server.


Resources must be shared between the regions, and theEventServer class must be registered in all regions nothosting the event server. This configuration enables TivoliManager for R/3 to send events using the wpostemsgcommand from the endpoints.

Note: Collecting Tivoli Manager for R/3 events to a single regionfrom both managed nodes and endpoints is not supported.

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

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

Note: Versions of Tivoli Manager for R/3 prior to Version 1.5are not supported.

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

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

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

Attention

Upgrading Tivoli Manager for R/3 to Version 2.2.0 from a previousrelease replaces files and, therefore, all local code modifications that youhave made will be lost. Before upgrading to Version 2.2.0, make a backupcopy of your local changes.

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


2.P

lann

ing

and

Installin

g

Activity Context Required Role

Install or upgradeTivoli Manager for R/3


Upgrading to Version 2.2.0 from Version 1.5 or 1.5.1Because the Tivoli Manager for R/3 product was restructured afterVersion 1.5.1, you cannot upgrade Tivoli Manager for R/3 directlyfrom Version 1.5 or Version 1.5.1 to Version 2.2.0. To upgrade toVersion 2.2.0, consider one of the following options:

¶ 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 Tivoli Manager for R/3 Version 2.0 and migrateconfiguration data as described in the Tivoli Manager for R/3Release Notes for 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/documents/).

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

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 the Tivoli Managerfor R/3 User’s Guide, Version 2.1. You can obtain a copy ofthe Version 2.1 user’s guide from the Tivoli CustomerSupport Web site (http://www.tivoli.com/support/documents/).






7. Upgrade to Version 2.2.0 as described in “Upgrading toVersion 2.2.0 from Version 2.1” on page 18.


¶ Do a fresh installation of Version 2.2.0 as follows:


2. Uninstall Tivoli Manager for R/3 Version 1.5 or Version1.5.1 as described in the Tivoli Manager for R/3 ReleaseNotes for Version 1.5.1. You can obtain a copy of the Version1.5.1 release notes from the Tivoli Customer Support Website (http://www.tivoli.com/support/documents/).

3. Install Version 2.2.0 as described in “Installing TivoliManager for R/3 Version 2.2.0” on page 19.


Upgrading to Version 2.2.0 from Version 2.0To upgrade Tivoli Manager for R/3 Version 2.0 to Version 2.2.0, youmust first upgrade to Version 2.1. To upgrade to Version 2.2.0,consider one of the following options:

¶ If you want to preserve Version 2.0 configuration data (R/3objects, RFC logon parameters, Alert Event Adapter and SyslogEvent Adapter parameters, subscription lists, and monitorprofiles), do the following:


2. Upgrade to Version 2.1 as described in the Tivoli Managerfor R/3 User’s Guide, Version 2.1. You can obtain a copy ofthe Version 2.1 user’s guide from the Tivoli CustomerSupport Web site (http://www.tivoli.com/support/documents/).Ensure that you read the about the considerations forupgrading the Syslog Event Adapter that are described in theTivoli Manager for R/3 Release Notes, Version 2.1. You canalso obtain a copy of the Version 2.1 release notes from theTivoli Customer Support Web site(http://www.tivoli.com/support/documents/).


2.P

lann

ing

and

Installin

g





4. Upgrade to Version 2.2.0 as described in “Upgrading toVersion 2.2.0 from Version 2.1”.


¶ Do a fresh installation of Version 2.2.0 as follows:


2. Uninstall Tivoli Manager for R/3 Version 2.0 as described inthe Tivoli Manager for R/3 User’s Guide, Version 2.0.

3. Install Version 2.2.0 as described in “Installing TivoliManager for R/3 Version 2.2.0” on page 19.


Upgrading to Version 2.2.0 from Version 2.1To upgrade Tivoli Manager for R/3 from Version 2.1 to Version2.2.0, back up the Tivoli database and then install Tivoli Managerfor R/3 Version 2.2.0 (Upgrade from Version 2.1) as a productpatch. Tivoli Manager for R/3 Version 2.2.0 (Upgrade from Version2.1) is located in the /UPGRADE directory on the Tivoli Managerfor R/3 CD.

Notes:

1. Install the upgrade on each machine on which you installedTivoli Manager for R/3 Version 2.1.

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

3. You can install the Version 2.2.0 transports either before or afterupgrading to Version 2.2.0. For information about installing thetransports, see “Moving R/3 Transports into an R/3 Landscape”on page 43.


4. To receive events from the CCMS Event Adapter, configure theevent console to add the WR3CCMS event source as describedin “Configuring an Event Console” on page 83.

The upgrade patch completely upgrades Tivoli Manager for R/3Version 2.1 to Version 2.2.0, replacing all product files and updatingR/3 system, R/3 application server, R/3 database server, and R/3 ITSserver objects. The upgrade also preserves the followingconfiguration data:

¶ RFC logon parameters

¶ Alert, Syslog, and IDOC event adapter parameters

¶ Subscription lists

¶ Monitor profiles

Notes:

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

2. Because the Alert, Syslog, and IDOC event adapters are replaced,you must start the Alert, Syslog, and IDOC event adapters thatare installed on UNIX. The Alert, Syslog, and IDOC eventadapters that are installed on Window NT are automaticallystarted even if the event adapters were not previously running.

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


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

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

4. Enter the full path to the Tivoli Manager for R/3 installationfiles in the Path Name text field. The Tivoli Manager for R/3files are located in the /PRODUCT directory on the TivoliManager for R/3 CD.


2.P

lann

ing

and

Installin

g

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.2.0 product is listed in the Select Product to


Install scrolling list.

7. Select Tivoli Manager for R/3, Version 2.2.0 in the SelectProduct to Install scrolling list.

8. Select the target clients on which you do not want to installTivoli Manager for R/3 from the Clients to Install On list andclick the right arrow button to move them to the AvailableClients list.

Note: Tivoli Manager for R/3 must be installed on thefollowing machines:

¶ Tivoli server

¶ 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


2.P

lann

ing

and

Installin

g

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 Tivoli 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 Tivoli Manager for R/3To uninstall Tivoli Manager for R/3, follow these steps:


Note: The create_uninstall_task.sh and R3Mgr_uninstall22.plcommands that are used in this procedure are installed withthe Tivoli Manager for R/3. If you do not find these scripts inthe $BINDIR/../generic_unix/TME/SAPUNINST directory,get a copy of these scripts from the /UNINST directory on theTivoli Manager 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 Tivoli Manager for R/3 Version 2.2.0 task.Go to the $BINDIR/../generic_unix/TME/SAPUNINST directoryon the Tivoli server and enter the following command:create_uninstall_task.sh Policy_Region_Name

Where Policy_Region_Name is the name of an existing policyregion in which you want to create the R3 Product ManagementTasks library and the Uninstall Tivoli Manager for R/3 Version2.2.0 task. Because the Uninstall Tivoli Manager for R/3 Version2.2.0 task uninstalls Tivoli Manager for R/3 policy regions andtask libraries, enter the name of an existing policy region that isnot part of the Tivoli Manager for R/3 product.

The create_uninstall_task.sh command creates the UninstallTivoli Manager for R/3 Version 2.2.0 task that you can run onmanaged nodes and endpoints to uninstall Tivoli Manager forR/3. The command also creates the R3 Product ManagementTasks library in the policy region you specify and adds theUninstall Tivoli Manager for R/3 Version 2.2.0 task to this tasklibrary.

3. Uninstall Tivoli Manager for R/3 from the Tivoli server. Followthese steps:

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


2.P

lann

ing

and

Installin

g

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_uninstall22.pl

¶ Windows:perl R3Mgr_uninstall22.pl

The syntax for the R3Mgr_uninstall22.pl command is:

R3Mgr_uninstall22.pl [–g] [–yes]

–g Uninstalls only Tivoli Business Systems ManagerInstrumentation for R/3 Version 2.2.0.

–yes Uninstalls the product without prompting forconfirmation.

The R3Mgr_uninstall22.pl command stops Tivoli Managerfor R/3 event adapters and removes the following items fromthe Tivoli server:

¶ Policy regions

¶ Task libraries

¶ Monitoring collections

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

¶ Profile managers

¶ Profiles

¶ Installed files

¶ Indicator collections


¶ Tivoli Enterprise Console sources (WR3MIB,WR3CCMS, WR3SLOG, and WR3IDOC)

¶ Tivoli Business Systems Manager installed files and tasklibraries

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

¶ Baroc classes

¶ Tivoli Enterprise Console rules

¶ Event console filters

¶ ABAP transports

¶ Tivoli Business Systems Manager Instrumentationdefinition files from the Tivoli Business SystemsManager server

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

¶ The SAPUNINST directory

¶ Scheduled jobs for automatic discovery

If you plan to reinstall Tivoli Manager for R/3, you donot need to remove the listed items. If you do not planto reinstall Tivoli Manager for R/3 and you want toremove the listed items, you can manually remove thebaroc classes, the Tivoli Enterprise Console rules, theevent console filters, the R3 Product ManagementTasks library, and the SAPUNINST directory.

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

4. Uninstall Tivoli Manager for R/3 on the managed nodes andendpoints. Run the Uninstall Tivoli Manager for R/3 Version2.2.0 task in the R3 Product Management Tasks library againstthe appropriate managed nodes and endpoints. The following


2.P

lann

ing

and

Installin

g

table describes the authorization role and target for the uninstalltask:

Task Role Target

Uninstall Tivoli Manager forR/3 Version 2.2.0

install_product Managed node andendpoint

The Uninstall Tivoli Manager for R/3 Version 2.2.0 task stops TivoliManager for R/3 event adapters and removes the following itemsfrom the managed nodes and endpoints:

¶ Installed files

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


Getting Started with TivoliManager for R/3

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

What Was InstalledAfter installing Tivoli Manager for R/3, the Manager for R3 policyregion on 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

etting

Started

with

Tivoli

Man

ager

for

R/3

See “Monitoring R/3 Resources” on page 109 for informationabout the monitor profile managers. See “Moving R/3 Transportsinto an R/3 Landscape” on page 43 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 131.

Open the Manager 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 Tivoli Manager for R/3 Configuration Tasks” onpage 35.

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

Tivoli 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

etting

Started

with

Tivoli

Man

ager

for

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 the SID of yourR/3 system.

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

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

1. Assign the Tivoli Manager for R/3 authorization roles to one ormore Tivoli administrators. See “Assigning AuthorizationRoles” on page 33.

2. If you are using the Tivoli Enterprise Console:

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

b. Create one or more event consoles if you have not alreadydone so. Refer to the Tivoli 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

etting

Started

with

Tivoli

Man

ager

for

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 Tivoli Manager for R/3 for Windows” onpage 72

¶ “Configuring Tivoli Manager for R/3 for HP-UX 11” onpage 75

¶ “Configuring Tivoli Manager for R/3 for OS/390” onpage 77

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 Tivoli Manager for R/3 uses three authorization roles: r3_user,r3_admin, and r3_senior. Each of the Tivoli Manager for R/3 tasksrequires one of the Tivoli Manager for R/3 authorization roles inaddition to the basic Tivoli authorization roles of user, admin, orsenior.

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


3.G

etting

Started

with

Tivoli

Man

ager

for

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 Tivoli Manager for R/3 tasks that require at least user andr3_user authorities 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, and Support andthree R/3 systems: PRD (a production system), QA1 (a test system),and QA2 (a test system). You might assign Tivoli authorization rolesto each administrator based on responsibilities as described in thefollowing table:


Administrator Responsibilities Tivoli 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 the Support 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 Tivoli Manager for R/3 Configuration TasksTivoli Manager for R/3 provides the following task libraries in theR3 Configuration policy region that contain tasks to help youconfigure Tivoli Manager for R/3:

¶ “R3 Configuration Tasks” on page 36

¶ “R3 List Maintenance Tasks” on page 38

Note: Tivoli Manager for R/3 also contains an R3 Internal Taskslibrary in the R3 Configuration policy subregion. Thetasks in this library support internal processing of TivoliManager 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. A job 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 Tivoli server or eventserver, as appropriate.

To locate the configuration tasks, follow these steps:


3.G

etting

Started

with

Tivoli

Man

ager

for

R/3

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

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

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

¶ Open the R3 List Maintenance Tasks library to display theCreate New Subscriber List task and job.

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

Tasks Role Target

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

r3_admin Windowsmanaged node orendpoint

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

r3_admin UNIX managednode or endpoint

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

r3_admin Tivoli 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 event server

Configure Event Server. See“Configuring the Event Server” onpage 82.

r3_admin event server

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



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

r3_admin Managed nodethat is the R/3SAPGUIinstallation server

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


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


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


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


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


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



3.G

etting

Started

with

Tivoli

Man

ager

for

R/3

Tasks Role Target

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

r3_admin Windowsmanaged node orendpoint

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

r3_admin UNIX managednode or endpoint

Send Heartbeat. See“Synchronizing the Tivoli BusinessSystems Manager Console with theTivoli Desktop” on page 158.

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.


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

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.

Tivoli Manager for R/3 sets the status of the database server usingthe following 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

etting

Started

with

Tivoli

Man

ager

for

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.Tivoli Manager for R/3 sets the status of the database serverbased on a Tivoli Manager for DB2 or Tivoli Manager forOracle database server status event. The database server statusevent can report up or down status.

Because there are potentially two methods by which Tivoli Managerfor R/3 sets database server status, Tivoli Manager for R/3 reflectsthe last status that is reported. If you shut down an R/3 system, theR/3 application 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 114.

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


3.G

etting

Started

with

Tivoli

Man

ager

for

R/3


Configuring Each SAP R/3System

After installing Tivoli Manager for R/3, configure each SAP R/3system that is to be managed so that Tivoli Manager for R/3 cancommunicate with that system. The following procedures must beperformed to enable this communication. These modifications willnot adversely affect your R/3 installation.

The configuration process requires the following:

¶ “Moving R/3 Transports into an R/3 Landscape”

¶ “Importing the Function Modules” on page 48

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

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

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

Moving R/3 Transports into an R/3 LandscapeTivoli Manager for R/3 provides a Base transport and an OS/390Extension transport. The OS/390 Extension transport must beinstalled after installing the Base transport. Refer to the TivoliManager for R/3 Release Notes for specific transport file names.

4


4.C

on

figu

ring

Each

SA

PR

/3S

ystem

The following tables describe the objects contained in each transport:

Base Transport

Object Type Objects

Development Class J8C1

Function Group ¶ J8C1¶ J8C2¶ J8C4¶ J8C5¶ J8C6¶ J8C8

Structure ¶ J_8C1_ALE1

¶ J_8C1_ALE2

¶ J_8C1_ALE3

¶ J_8C1_ALE4

¶ J_8C1_ALE5

¶ J_8C1_ALE6

¶ J_8C1_TIV1

¶ J_8C1_TIV2

¶ J_8C1_TIV3


Base Transport

Object Type Objects

Data element ¶ J_8C1_C001

¶ J_8C1_C006

¶ J_8C1_C008

¶ J_8C1_C016

¶ J_8C1_C030

¶ J_8C1_C032

¶ J_8C1_C055

¶ J_8C1_C180

¶ J_8C1_C255

¶ J_8C1_I004

¶ J_8C1_N020

Domain ¶ J_8C_C001

¶ J_8C_C006

¶ J_8C_C008

¶ J_8C_C016

¶ J_8C_C030

¶ J_8C_C032

¶ J_8C_C055

¶ J_8C_C180

¶ J_8C_C255

¶ J_8C_I004

¶ J_8C_N020

OS/390 Extension Transport

Object Type Objects

Function Group J8C3


4.C

on

figu

ring

Each

SA

PR

/3S

ystem

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 Tivoli server to use this method.

¶ Copy the transport files from the Tivoli 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 the R3 Transportsprofile manager icon to display the Profile Manager window.

2. If you are distributing the R3 ABAP file package to endpoints,follow these steps to change the R3 Transports profile managerfrom database mode to dataless mode:

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

b. Select Dataless Endpoint Mode.

Note: Refer to the Tivoli Management Framework User’sGuide for more information about database mode anddataless mode profile managers.

c. Click Change & Close.

3. Subscribe the appropriate managed nodes or endpoints to the R3Transports profile manager. In the Profile Manager window, fromthe Profile Manager menu, select Subscribers to display theSubscribers 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, edit the filepackage properties to modify the destination directory path.Follow these steps:

a. Right-click the R3 ABAP FilePackage icon and selectProperties to display the File Package Properties dialog.

b. From the Edit menu, select Platform-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 to driveLetter:/trans/, wheredriveLetter maps to \\SAPGLOBALHOST\sapmnt.SAPGLOBALHOST represents the host name of the centralinstance.

6. Distribute the transports. From the Profile Manager window,right-click the R3 ABAP FilePackage icon and select Distributefrom 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:

¶ For UNIX: /usr/sap/trans

¶ For Windows: driveLetter:/trans/.

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

Copying the TransportsTo copy the transport files from the Tivoli 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 directoryon the Tivoli server.


4.C

on

figu

ring

Each

SA

PR

/3S

ystem

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

Where sid 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 the Tivoli Manager for R/3 Release Notes forspecific 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]

Note: For R/3 releases prior to 4.0A, the u4 option must 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 43. 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 transaction STMS.

¶ From the Tools menu, select Administration, and then fromthe Transport menu, select Transport 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 the Overview menu, select Imports.

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

¶ Double-click the target system.


4.C

on

figu

ring

Each

SA

PR

/3S

ystem

¶ Select the target system and then from the Import Queuemenu, select Display.

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 the Extras menu, select Other requests –> Add todisplay the Add Transport Request to Import Queue dialog.

b. In the Transp. request field, enter the transport name thatyou want to add, such as TV1Kxxxxxx. Then, click the greencheck and click Yes on the confirmation dialog.

Note: Refer to the Tivoli Manager for R/3 Release Notes forspecific transport file names.

5. Import the transport as follows:

a. From the Import Queue window, select the transport. Then,from the Request menu, select Import 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 click Yes on the confirmationdialog.

6. Verify the import. From the Request menu, select Display –>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 authorization profileS_A.SYSTEM. This authorization profile can be used for the userID.

If you want to assign a more restrictive set of authorizations to theuser ID, use transaction SU02 to copy the S_A.SYSTEMauthorization profile and remove all authorizations except thosedescribed in the following table:

Object Authorization

S_RFC S_RFC_ALL

S_XMI_PROD S_XMI_ADMIN

S_DATASET S_DATASET_AL

S_LOG_COM S_LOGCOM_ALLNote: S_LOGCOM_ALL can bereplaced with T_5618443201.

S_BTCH_ADM S_BTCH_ALL

S_BTCH_JOB S_BTCH_ALL

S_RZL_ADM S_RZL_ALL

S_ADMI_FCD S_ADMI_ALL

Note: The S_XMI_PROD, S_DATASET, AND S_LOG_COMauthorization objects are required to use the CCMS Event Adapter.

If you want to create the most restrictive authorization profiles, referto “Function Module Authorization” on page 231 for information onthe authorizations required by each Tivoli 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.


4.C

on

figu

ring

Each

SA

PR

/3S

ystem

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. Tivoli Manager for R/3 requiresthat segment key 13 be assigned to shared memory pool 10. This isthe default allocation for R/3. This assignment is necessary tosupport proper functioning of the Alert Event Adapter and theautomatic discovery 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 parameteripc/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.


Configuring Tivoli Manager forR/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 with TivoliManager 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 Tivoli Manager for R/3, youmust configure Tivoli for each R/3 system, R/3 application server,R/3 database 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.

5


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

Notes:

1. To ensure that an R/3 application server reflects its current status,you must manually distribute the R3 Server AutodiscoveryMonitors 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 114.

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 114. 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 110.

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

R/3 system objects are created on the Tivoli 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 endpoints, by default, are created on the managednode that hosts the endpoint’s current gateway. However, you cancreate the R/3 server objects for endpoints on any managed node thatyou specify.

If you create R/3 server objects for endpoints on the defaultmanaged node, the R/3 server objects might be distributed across


multiple 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 Tivoli server or on a high availabilitymanaged node. With this approach, you can take steps to ensure thatthis managed node has the proper backup and recovery plans in caseof failure.

Tivoli Manager for R/3 objects cannot be moved after the objects arecreated. If the managed node hosting a endpoint’s gateway fails, youwill need to take recovery action. If possible, restore the managednode from a backup. If you cannot restore the managed node, youmust delete the R/3 server objects for the affected endpoints andthen recreate the R/3 server objects on another managed 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.


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

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

Configuring Automatic Discovery for Data SharingWhen Tivoli Manager for R/3 creates the R/3 application serverobjects within an R/3 system policy region, Tivoli Manager for R/3assigns the name of the policy region as SID_DBHostname. Thevalues for SID and DBHostname are obtained from the R/3application servers when they are discovered. In a data sharingenvironment, the R/3 application servers can report differentdatabase host names even though the R/3 application servers are inthe same R/3 system. This is particularly true for OS/390. (For moreinformation, see “Data Sharing” on page 78). For a data sharingenvironment, you can override the default processing of theautomatic discovery function to force the R/3 application servers intoan R/3 policy region named with the database host name of yourchoice. You do this by specifying the database host name for eachR/3 system in the sap_discovery.cfg configuration file. Theautomatic discovery function uses the database host names specifiedin the sap_discovery.cfg configuration file when it creates theR/3 policy regions.

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

Where SID is the three-character R/3 system identifier, anddatabase_hostname is 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 Tivoli 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 cannot be longer than


eight 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 aline. To specify the database host names for R/3 systems TV1and TV4, you would edit the sap_discovery.cfg file asfollows:TV1 puli

TV4 hound

2. Distribute the sap_discovery.cfg file to each managed nodeand endpoint on which you plan to run automatic discovery. Youcan use the file transfer protocol (FTP) or Tivoli SoftwareDistribution to distribute the file. The sap_discovery.cfg filemust reside in one of the following directories:

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

¶ Endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP/sh

Note: The $LCF_BINDIR/../../generic_unix/TME/SAP/shdirectory does not exist prior to running a TivoliManager for R/3 task on the endpoint. If you plan touse FTP to distribute the sap_discovery.cfg fileprior to running automatic discovery, you mustmanually create the$LCF_BINDIR/../../generic_unix/TME/SAP/shdirectory. If you plan to use Software Distribution todistribute the sap_discovery.cfg file, you do notneed to 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 the


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

automatic 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 thespecified 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 endpoints, you can force automaticdiscovery to create the R/3 objects on any managed node rather thanon the one hosting the current gateway.

Notes:

1. In the Execute Task dialog, specify only Windows managednodes or Windows endpoints for the Configure Autodiscovery forNT task. Specify only UNIX managed nodes or UNIX endpointsfor the Configure Autodiscovery for UNIX task.

2. In the Execute Task dialog, specify Serial in the Execution Modefield and, if you intend to run automatic discovery immediately,specify at least 180 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 WindowsTo schedule automatic discovery for Windows, 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

on

figu

ring

Tivoli

Man

ager

for

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 onendpoints, Tivoli 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 the Createmenu from the Tivoli Manager for R/3 Policy Region window, select


R3System to 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 named SID_DBHostname,where SID is the value specified in the R/3 System Name (SID)field, and DBHostname is 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 78 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

on

figu

ring

Tivoli

Man

ager

for

R/3

2. From the Create menu, select R3AppServer 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 the Create menu, select R3DBServer 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 the Create menu, select R3ITSServer 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

on

figu

ring

Tivoli

Man

ager

for

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 “Tivoli Managerfor 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 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 135.

¶ 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 R/3 instrumentation is installed, the object is added to theTivoli Business Systems Manager server database and an icon iscreated on the Tivoli Business Systems Manager workstation.See “Tivoli Business Systems Manager Instrumentation for R/3”on page 151.

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“Tivoli 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, youmust run this task from the same machineon which the R/3 application server isrunning.


5.C

on

figu

ring

Tivoli

Man

ager

for

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

Start CCMS Event Adapter

Stop CCMS Event Adapter

See “R3 App Server Tasks” on page 136.

¶ 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 “Tivoli Managerfor 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 database server icon, the task executes on that R/3


database 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 140.

¶ If R/3 instrumentation is installed, the object is added to theTivoli Business Systems Manager server database and an icon iscreated on the Tivoli Business Systems Manager console. See“Tivoli Business Systems Manager Instrumentation for R/3” onpage 151.

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 “TivoliManager 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 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.


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

Task Description

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.

Start ITS Server

Stop ITS Server

See “R3 ITS Server Tasks” on page 141.

¶ 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, or an R/3 ITS server object does not affect the R/3 system orthe server but removes the information about it that is stored in theTivoli 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 are running against objects inan R/3 system can potentially corrupt the Tivoli database. For moreinformation about this problem, refer to the information about deleting R/3objects in the ″Known Product Defects, Limitations and Workarounds″section of the Tivoli 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 the Edit menu, select Delete to remove the selected objectfrom the policy region.

4. Restart the Application Server Status and the ITS Server Statusmonitors as 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 R/3 instrumentation is installed, the object is deleted from theTivoli Business Systems Manager server database, and the iconis removed from the Tivoli Business Systems Managerworkstation.

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.

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

¶ If Tivoli Business System Manager Instrumentation for TivoliManager for R/3 is installed, the object is deleted from theTivoli Business Systems Manager server database, and the iconis removed from the Tivoli Business Systems Manager 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.


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

¶ The R3DBServer object is unsubscribed from all profilemanagers.


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 ListsTivoli Manager for R/3 automatically creates the following lists inthe R3 Configuration policy subregion:

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

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

These lists are subscriber-only profile managers and are updatedautomatically as resources are defined to Tivoli Manager for R/3,whether by discovery or when you manually create R/3 system andR/3 application server objects. You can use these lists as targetendpoints when you run tasks and monitors. All application serverlists are automatically subscribed to the R3 App Server Monitorsprofile manager. See “R3 App Server Monitors Profile Manager” onpage 114.


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 Tivoli 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 CallTivoli Manager for R/3 must connect to each managed R/3 systemusing the R/3 remote function call (RFC) to run certain tasks andmonitors. The user ID that is used for this access was defined whenthe R/3 administrator configured the R/3 system. (See “ConfiguringUser IDs for RFC Interface Access” on page 50). To use the RFCinterface for a particular R/3 system, you must configure the RFCfor that system in Tivoli. The Syslog Event Adapter, the IDOC EventAdapter, and the CCMS Event Adapter use this configurationinformation.

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

¶ Rerun the Configure Event Adapter task for the appropriateSyslog Event Adapter, IDOC Event Adapter, or CCMS EventAdapter and then stop and start the event adapter to update theRFC configuration information. See “Configuring EventAdapters” 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 the ConfigureRemote Function Call task in the R3 Configuration Tasks library.(See “Using Tivoli Manager for R/3 Configuration Tasks” onpage 35.) This task displays the Configure Remote Function Call


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

dialog.

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

Configuring Tivoli Manager for R/3 for WindowsThis section describes how to configure Tivoli Manager for R/3 ifyou are running R/3 in a Windows environment.

Creating Exit Routines for WindowsThe start and stop database tasks for Windows rely ondatabase-specific commands to fully implement their processing.Tivoli Manager for R/3 does not provide these commands. Instead,Tivoli Manager for R/3 provides database start and stop tasks thatcall user-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 called sap_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

¶ Endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP/sh


The Tivoli 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 must exit bywriting a numeric return code to standard output. A return code ofzero 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 10echo '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 AccessTivoli Manager 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.

Tivoli Manager for R/3 tasks are run as Administrator in a Windowsenvironment. In a Windows domain, Administrator maps to eachWindows local Administrator. To enable the Tivoli Manager for R/3tasks to run with the correct permissions, you must configure the


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

local Administrator on each Windows application server to be amember of the SAP_<sid>_LocalAdmin group.

Enabling Automatic Discovery for WindowsFor automatic discovery to work on Windows managed nodes, youmust ensure that the SYSTEM user ID is added to the list of loginsfor the root Tivoli Administrator. This is because the automaticdiscovery function relies on the Windows at command to providescheduling, and scheduled commands are run under the SYSTEMuser ID. Refer to the appropriate Windows documentation for moreinformation about the at command.

Enabling the Tivoli Authentication Package forWindows

If you are running R/3 on Windows, you might have configured yourR/3 installation to share file systems of the Central Instance withservers for Dialog instances. If your installation is configured in thisway, then Tivoli must be configured for remote file access privilegesfor some of the Tivoli Manager for R/3 tasks to gain access to theR/3 executables, in particular, for starting and stopping R/3 servers.

Remote file access is configured into Tivoli through the TivoliAuthentication Package. The configuration is set during installationof the managed node or the endpoint. To set remote file access afterinstallation of the managed node or endpoint, use the wsettap andwlcftap commands, respectively. Use one of the followingcommands to configure the Tivoli Authentication Package for use bythe 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, where sid is thethree-character R/3 system identifier.

¶ Endpoint:

v wlcftap -a -r Administrator

v wlcftap -a -r domain_name\Administrator


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

For more information about the Tivoli Authentication Package, referto the Tivoli Framework Planning and Installation Guide. For moreinformation about the wsettap and wlcftap commands, refer to theTivoli Framework Reference Manual.

Setting the Environment Variable for WindowsTo use the Tivoli Manager for R/3 start and stop SAPGUI tasks, youmust set an environment variable in the Windows systemenvironment. The following environment variable enables TivoliManager for R/3 to locate 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 Tivoli Manager for R/3 for HP-UX 11Tivoli Manager 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 SupportTivoli Manager for R/3 supports R/3 systems running on HP-UX 11in 64-bit mode. Tivoli Manager for R/3 automatically detects if anR/3 system is running on a 64-bit mode system and automaticallyinvokes the correct 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, TivoliManager for R/3 requires the following:

¶ The /etc/services.window file must contain entries thatspecify the application server name and the memory window in


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

which the application server is to start. For example, the/etc/services.window file must contain entries similar to thefollowing:peach_DO1_10 101peach_DO1_20 102

¶ The /usr/bin/setmemwindow and 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 sharedmemory 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 user sidadm and is approximately 4 KB insize. Note the ID of this memory segment.

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

Replace ID with the ID of the shared memory segment.

4. Restart the R/3 application server.

When these requirements are met, the Tivoli Manager for R/3 eventadapters and monitors will work. For the Tivoli Manager for R/3start and stop R/3 system tasks to work, it is assumed that theSAP-provided start and stop scripts in the sidadm home directoryhave been modified to use the memory windowing setmemwindowand getmemwindow commands.


Configuring Tivoli Manager for R/3 for OS/390This section describes considerations for using Tivoli Manager forR/3 if you 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. Tivoli Manager for R/3-supported application serveroperating systems with an OS/390 database server are AIX andWindows.

R/3 TransportsTivoli Manager for R/3 delivers transports for R/3. The base setprovides all function modules needed to run the standard TivoliManager for R/3 functions. An additional transport is provided forOS/390 that must be installed in your R/3 systems. The OS/390transport provides the function modules to obtain OS/390 operatingsystem information and OS/390 DB2 information. This transport isinstalled in the same manner as the base transport. For moreinformation about the transports, see “Moving R/3 Transports into anR/3 Landscape” on page 43.

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 Tivoli Manager for R/3function modules to obtain OS/390 information.

The function modules delivered in the OS/390 transport rely on theR/3 saposcol and rfcoscol programs being installed on the OS/390operating system. SAP delivers the saposcol and 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/390Tivoli Manager 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, TivoliManager for R/3 will not automatically discover your R/3 database


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

server, and you cannot create the R/3 database server objectmanually from the desktop. Also, Tivoli Manager for R/3 does notsupport starting and stopping 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.

In a data sharing environment, Tivoli Manager for R/3 attempts tocreate multiple R/3 policy regions for the same R/3 system becauseTivoli Manager 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 Tivoli Manager for R/3 uses acommon database host name value. Configuring automatic discoveryto use a common database host name prevents the creation ofmultiple R/3 policy regions. If you are creating your R/3 objectsentirely from the desktop, you can select any database host namewhen you create the R/3 system object.

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

Extending Database Server Status ReportingIf you have Tivoli Manager for DB2 or Tivoli Manager for Oracleinstalled, you can extend Tivoli Manager for R/3 database statusreporting. This means that you can update the status of the databaseserver with the status of the database as reported by the TivoliManager for DB2 or Tivoli 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 the Create RDBMSManager Status Monitor job in the R3 Configuration Taskslibrary. This job displays the Create RDBMS Manager StatusMonitor 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 Tivoli Manager for DB2instance objects or Tivoli Manager for Oracle instanceobjects.


5.C

on

figu

ring

Tivoli

Man

ager

for

R/3

c. Distribute the profile to the subscribers.

Both database status monitors are configured to run every 15minutes and to generate a Tivoli Enterprise Console event thatTivoli Manager for R/3 processes to update database serverstatus. A Tivoli Enterprise Console event is generated for each ofthe following response levels:

¶ Critical is set when the monitor returns Becomesunavailable.

¶ Warning is set when the monitor returns Becomesavailable.

2. Configure the event server to add the database status integrationrules. For information about how to configure the event server,see “Configuring the Event Server” on page 82. For informationabout the database status integration rules, see “Database StatusIntegration Rules” on page 213.

Note: If you installed Tivoli Manager for DB2 or TivoliManager for Oracle after you configured the event server,you must reconfigure the event server to install thedatabase status integration rules.

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

Note: The association between the Tivoli Manager for DB2 orTivoli Manager for Oracle database server object and theTivoli Manager for R/3 database server object depends onboth Tivoli Manager for DB2 or Tivoli Manager for Oracleand Tivoli Manager for R/3 reporting the same value for theR/3 SID. Tivoli Manager for R/3 sets the R/3 SID when youcreate the R/3 system object (see “Creating R/3 Objects” onpage 53).


Managing R/3 Events

Tivoli Manager for R/3 supplies new event classes and rule sets toenable you to view and work with R/3 events at your event console.You can extend these classes and rule sets to provide furtherenhancement, automation, and intelligent processing.

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

1. Configure the event server to recognize R/3 events and processrules concerning those events. Run the Configure Event Servertask against the event server to be configured.

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

3. Configure the event consoles to assign newly created eventgroups to the appropriate event consoles.

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

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 CCMS Event Adapter” on page 89

¶ “Using the Syslog Event Adapter” on page 94

6


6.M

anag

ing

R/3

Even

ts

¶ “Using the IDOC Event Adapter” on page 99

¶ “Filtering Events” on page 107

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 Event server

Configure Event Server r3_admin Event server

Display Event AdapterConfiguration

r3_user R3AppServer

Start Event Adapter r3_user R3AppServer

Stop Event Adapter r3_user R3AppServer

Configuring the Event ServerThe Configure Event Server task configures an event server forTivoli Manager for R/3 by importing new classes and rules,installing new event sources, compiling the new rule base, and thenstopping and restarting the 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. To do this, compile thecurrent rule base with the Tivoli Manager for DB2 or TivoliManager for Oracle rule base included. Tivoli Manager for R/3references the Tivoli Manager for DB2 or the Tivoli Manager forOracle status event classes (D2Manager_status orOracleInstanceManager_rdbmsstate, respectively). Then run theConfigure Event Server job.

Similarly, when using R/3 instrumentation (see “Tivoli BusinessSystems Manager Instrumentation for R/3” on page 151), it isnecessary to include additional R/3 instrumentation event classes andrules in the Tivoli Enterprise Console rule base.


To configure an event server, run the Configure Event Server jobin the R3 Configuration Tasks library. (See “Using Tivoli Managerfor R/3 Configuration Tasks” on page 35.) This job displays theConfigure Event Server dialog.


Configuring an Event ConsoleThe procedure to configure an event console differs according to theversion of the Tivoli Enterprise Console product that you haveinstalled. To configure an event console, follow one of theseprocedures:

¶ “Configuring a Version 3.6 Event Console”

¶ “Configuring a Version 3.7 Event Console” on page 85

Configuring a Version 3.6 Event ConsoleTo configure a version 3.6 event console, run the Configure EventConsole job in the R3 Configuration Tasks library. The ConfigureEvent Console job adds filters to the event console and assigns thegroup and event sources. This job displays the Configure Event


6.M

anag

ing

R/3

Even

ts

Console dialog.


View R/3 events from the event console as follows:

¶ To view all events that have passed the group filter criteria, openthe appropriate event group.

¶ To view all events from all Tivoli Manager for R/3 Alert EventAdapters, open the WR3MIB event source.

¶ To view all events from all Tivoli Manager for R/3 Syslog EventAdapters, open the WR3SLOG event source.

¶ To view all events from all Tivoli Manager for R/3 IDOC EventAdapters, open the WR3IDOC event source.

¶ To view all events from all Tivoli Manager for R/3 CCMS EventAdapters, open the WR3CCMS event source.

Here is an example of the event log:


Configuring a Version 3.7 Event ConsoleTo configure a version 3.7 event console, manually create an eventgroup for the R/3 events you want to manage. Add one or moreevent group filters to the event group with one or both of thefollowing attributes:

¶ Source

Add one or more of the following sources:

v WR3MIB (for Alert Event Adapter events)

v WR3SLOG (for Syslog Event Adapter events)

v WR3IDOC (for IDOC Event Adapter events)

v WR3CCMS (for CCMS Event Adapter events)

v SENTRY (for Distributed Monitoring events)

¶ Sub_source

Specify one or more R/3 systems (such as, WHF_erphpka) fromwhich you want to send events to this event console.

Here are two examples:


6.M

anag

ing

R/3

Even

ts

¶ To filter all events from the R/3 system WHF_erphpka, specifyWHF_erphpka for the sub_source attribute of the event groupfilter.

¶ To filter events from the CCMS Event Adapter and the IDOCEvent Adapter for R/3 system WHF_erphpka, specify WR3CCMSand WR3IDOC for the source attribute and WHF_erphpka for thesub_source attribute.

After you have created the event group, assign the event group tothe appropriate event console. For more information about creatingan event group and assigning an event group to an event console,refer to the Tivoli Enterprise Console User’s Guide.

To view R/3 events, open the event console and go to the eventviewer.

Configuring Event AdaptersTo configure the Alert Event Adapter, the CCMS Event Adapter, theSyslog Event Adapter, or the IDOC Event Adapter, run theConfigure Event Adapter task in the R3 Configuration Taskslibrary. (See “Using Tivoli Manager for R/3 Configuration Tasks” onpage 35.) This task creates an event adapter.

Notes:

1. If you reconfigure an event adapter, stop and start the appropriateevent adapter to incorporate the changes.

2. Select an event adapter for reporting R/3 alerts as follows:

¶ Configure the Alert Event Adapter for each R/3 applicationserver running R/3 releases up to and including 4.0B.

¶ Configure the CCMS Event Adapter for one R/3 applicationserver in each R/3 system running R/3 releases 4.5B andlater. Configuring a CCMS Event Adapter on more than oneR/3 system can generate duplicate events for each alert.

3. Configure the Syslog Event Adapter for each R/3 applicationserver running any R/3 release.


4. Configure an IDOC Event Adapter for one R/3 application serverin each R/3 system. Because IDOCs are system-wide resources,configuring an IDOC Event Adapter on more than one R/3application server in an R/3 system generates duplicate events foreach IDOC.

The Configure Event Adapter task displays the Configure EventAdapter dialog.


Displaying Event Adapter InformationTo display the event adapter information, run the Display EventAdapter Configuration task in the R3 Configuration Tasks library.(See “Using Tivoli Manager for R/3 Configuration Tasks” onpage 35.) This task displays the Display Event Adapter Configuration


6.M

anag

ing

R/3

Even

ts

dialog.

To display the current configuration of an event adapter, select AlertAdapter, CCMS Adapter, Syslog Adapter, or IDOC Adapter.

Starting and Stopping an Event AdapterTivoli Manager for R/3 provides the following tasks in the R3 AppServer Tasks library to start and stop an event adapter:

Start Event AdapterStarts the specified event adapter.

Stop Event AdapterStops the specified event adapter.

Using the Alert Event AdapterFor R/3 releases up to and including 4.0B, R/3 uses an alert facilitythat monitors various elements of the R/3 system. R/3 publishesrelated alerts through its SysMan interface. The Alert Event Adapterqueries the R/3 SysMan interface for new entries and forwardsformatted events to the event console. Alerts can be generated in thefollowing ways:

¶ Automatically based on predetermined criteria

¶ In response to the R/3 Basis Administrator setting thresholdvalues against monitored measurements

You can view the alerts that have occurred in an R/3 system usingtransaction RZ03.


The Alert Event Adapter can generate many events. See “EventClasses and Rules” on page 183 for a listing of these events. Tominimize the number of events that are sent to the event console,you can filter these events at the Alert Event Adapter. To filterevents, add filter statements to the r3mibIID.conf file, where IIDrepresents the two-digit R/3 instance number. See “Filtering Events”on page 107.

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

¶ Endpoint: $LCF_BINDIR/../TME/SAP/2.2C

Using the CCMS Event AdapterFor R/3 releases 4.5B and later, CCMS uses the MonitoringArchitecture to monitor many resources in the R/3 system. CCMSposts the results of each monitored resource as an attribute of anobject in the monitoring tree. You can view alerts, complete openalerts, and change the threshold values that determine when alertsare generated using transaction RZ20.

Because R/3 alerts are treated as system-wide resources in CCMS,you only need to configure and run one CCMS Event Adapter ineach R/3 system. Although CCMS enables you to monitor multipleR/3 systems, you must configure and run one CCMS Event Adapterin each R/3 system to reliably report R/3 alerts.

How the CCMS Event Adapter WorksThe CCMS Event Adapter interfaces with the MonitoringArchitecture to read open R/3 alerts from a specified monitoring setand monitor. By default, the CCMS Event Adapter reads open alertsfrom the Operating System monitor contained in the SAP CCMSMonitor Template monitoring set. Although the CCMS Event


6.M

anag

ing

R/3

Even

ts

Adapter reads all open alerts, it might not report some alerts asevents. By default, the CCMS Event Adapter reports the most alertfor each monitoring attribute.

You can use the CCMS Event Adapter as shipped, or you cancustomize the CCMS Event Adapter to meet your needs. TivoliManager for R/3 provides the following configuration files thatcontrol how the CCMS Event Adapter works:

r3moniIID.confDefines the CCMS Event Adapter runtime parameters, suchas the polling cycle and the number of alerts to report foreach monitoring attribute. This file also contains the name ofthe monitoring set and monitor to observe. However,manually changing the name of the monitoring set andmonitor in this file does not cause the CCMS Event Adapterto observe a new monitoring set and monitor. To change thename of monitoring set and monitor to be observed, youmust run the Configure Event Adapter task.

r3moniIID.evtDefines the event classes that the CCMS Event Adapter useswhen forwarding alerts as Tivoli Enterprise Console events.

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

These configuration files are located in one of the followingdirectories:

¶ Managed node: $BIN DIR/TME/SAP/2.2C


The CCMS Event Adapter configuration files are created after yourun the Configure Event Adapter task and, therefore, exist only afteryou have run this task at least once for the specific R/3 applicationserver.

The CCMS Event Adapter obtains R/3 alerts through the R/3 RFCinterface. Therefore, the CCMS Event Adapter must log on to theR/3 system. The CCMS Event Adapter uses the same R/3 user ID


information that was specified when you configured an RFC. See“Configuring a Remote Function Call” on page 71.

Viewing and Intepreting Alert EventsCCMS organizes alert reporting into a tree structure based onmonitoring sets and monitors. For example, SAP delivers amonitoring set named SAP CCMS Monitor Templates. Thismonitoring set contains many monitors, such as Buffers, Database,and Entire System. A basis administrator can create new monitoringsets and monitors that are configured to report resources of interest.

CCMS organizes its monitoring attributes into collections ofmonitoring tree element (MTE) classes. The CCMS Event Adaptergenerates an event class based on the MTE class name. Becausesome MTE classes have a one-to-one relationship to the monitoringattributes and other MTE classes have a one-to-many relationshipwith the monitoring attributes, you might see a few events with anevent class of one type and many events with an event class ofanother type.

You can determine the relationship between Tivoli EnterpriseConsole events and CCMS alerts by comparing the Tivoli EnterpriseConsole event values to the CCMS alerts values as described in thefollowing table:

This event value corresponds to... This CCMS alert value...

Event class name MTE class name on the MTEattribute properties

alert_objectname event slot MTE attribute parent name

alert_fieldname event slot MTE attribute name, the lowestlevel node in the monitoring tree

Customizing the CCMS Event AdapterYou can use the CCMS Event Adapter as shipped, or you cancustomize the CCMS Event Adapter in the following ways:

¶ “Changing the Monitoring Set and Monitor to Observe” onpage 92


6.M

anag

ing

R/3

Even

ts

¶ “Controlling the Number of Alerts to Report”

¶ “Controlling Automatic Closing of Alerts in CCMS” on page 93

¶ “Adding Event Classes” on page 93

Whenever you modify a configuration file, stop and start the CCMSEvent Adapter to incorporate the changes.

Changing the Monitoring Set and Monitor to ObserveTo change the monitoring set and monitor that you want the CCMSEvent Adapter to observe, run the Configure Event Adapter task andmodify the settings of the Monitoring Set and Monitor parameters.Type the names of the Monitoring Set and Monitor exactly as theyappear in CCMS because these names are case sensitive.

Controlling the Number of Alerts to ReportTo control the number of most recent CCMS alerts that the CCMSEvent Adapter sends to the event console for each monitoringattribute, run the Configure Event Adapter task and modify thesetting of the Alerts Per CCMS Attribute parameter. You canspecify a specific limit or you can specify zero (0) to report all alertsfor each monitoring attribute as events.

The setting in the Alerts Per CCMS Attribute parameter is a globalparameter because it affects all attributes in the monitoring tree.Some attributes, such as CPU utilization, are significant only for thelast reported value. Other attributes, such as ABAP dumps, aresignificant for every occurrence. For example, specifying a lownumber, such as 1, for the Alerts Per CCMS Attribute parametermight provide good tuning for CPU utilization alerts, but it alsocauses the CCMS Event Adapter to send a limited number of eventsfor ABAP dumps. Specifying a high number for the Alerts PerCCMS Attribute parameter causes the CCMS Event Adapter tosend more events for ABAP dumps, but it also causes the CCMSEvent Adapter to send a large number CPU utilization events that arenot important.


Controlling Automatic Closing of Alerts in CCMSThe CCMS Event Adapter enables you to automatically close alertsin CCMS. Any alerts that the CCMS Event Adapter does not reportas events (those alerts that are in excess of the number specified bythe Alerts Per CCMS Attribute parameter) qualify for automaticclosing. As shipped, the CCMS Event Adapter does notautomatically close these alerts in CCMS.

To control automatic closing of these alerts in CCMS, run theConfigure Event Adapter task and modify the setting of the CloseCCMS Alerts parameter. Because CCMS can contain many activealerts and because the CCMS Event Adapter reads all active alerts ateach polling cycle, closing the alerts in CCMS improves theperformance of the CCMS Event Adapter.

Adding Event ClassesTo add event classes, edit the r3moniIID.evt configuration file. Ther3moniIID.evt file defines all event classes for an R/3 4.6B system,but you might need to add event classes if you have customizedMTE classes. If an event class is not defined for an alert in ther3moniIID.evt file, the CCMS Event Adapter sends an event usingthe SAP_CCMS_Default_Alert event class.

The set of event classes that Tivoli Manager for R/3 provides weregenerated by prepending the name of the MTE class withSAP_CCMS and replacing blank characters in the MTE class namewith underscore ( _ ) characters. The r3moniIID.evt file consists ofa comma-separated list of CCMS MTE class name and TivoliEnterprise Console event class pairs as follows:MoniKnownClass="MTE_class_name1" SAP_CCMS_MTE_class_name1,

"MTE_class_name2" SAP_CCMS_MTE_class_name2

Note: The last line in the r3moniIID.evt does not contain acomma.

Here is an example of several event class mappings in ther3moniIID.evt file:MoniKnownClass = "Paging" SAP_CCMS_Paging,

"Filesystems" SAP_CCMS_Filesystems,"CPU_Utilization" SAP_CCMS_CPU_Utilization


6.M

anag

ing

R/3

Even

ts

You can add additional MTE class and event class pairs to meet theneeds of your installation. If you add an event class, you mustupdate the tecad_wr3moni.baroc file in the active rule base onyour event server.

Using the Syslog Event AdapterThe Syslog Event Adapter processes the R/3 syslog and convertsnew entries into Tivoli Enterprise Console events. Because theSyslog Event Adapter obtains syslog messages through the R/3 RFCinterface, the Syslog Event Adapter must log on to the R/3 system.The Syslog Event Adapter uses the same R/3 user ID informationthat was specified when you configured an RFC. See “Configuring aRemote Function Call” on page 71.

Tivoli Manager for R/3 provides two configuration files for theSyslog Event Adapter: r3slogIID.cl and r3slogIID.conf, whereIID represents the two-digit R/3 instance number. Theseconfiguration files are created after you run the Configure EventAdapter task and, therefore, exist only after you have run this task atleast once for the specific R/3 application server. The r3slogIID.cland the r3slogIID.conf configuration files are located in one of thefollowing directories:



The configuration files are used as follows:

r3slogIID.clDefines the syslog events that are sent to the event console.Events that are not defined in this file cause the SyslogEvent Adapter 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 event console or add newentries to this file to send additional syslog events to the


event console. See “Modifying Entries in the r3slogIID.clFile” on page 96 and “Adding New Entries to ther3slogIID.cl File” on page 96.

r3slogIID.confContains event filter statements. By default, all syslog eventsthat 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 event console. If you want to see all syslogevents, comment out the Filter statement in ther3slogIID.conf file. See “Filtering Events” on page 107.

The following table describes the syslog events that are defined inthe r3slogIID.cl file and are sent to the event console by default.You can use the Syslog Event Adapter as shipped, or you cancustomize which syslog events are sent to event console. See“Controlling Syslog Events” on page 96.

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.


6.M

anag

ing

R/3

Even

ts

Controlling Syslog EventsYou can control the syslog events you want sent to the event consolein the following ways:

¶ “Modifying Entries in the r3slogIID.cl File”.

¶ “Adding New Entries to the r3slogIID.cl File”.

¶ “Filtering Events” on page 107.

Modifying Entries in the r3slogIID.cl FileTo control the syslog events that are sent to the event console,modify the entries in the r3slogIID.cl file. Entries for many syslogevents are defined in the r3slogIID.cl file for your convenience.Most of the entries are commented. Commented lines are precededby a semicolon (;). To send additional syslog events to the eventconsole, uncomment the appropriate event entries. Similarly, if youdo not want to send one of the default events to the event console,do one of the following:

¶ Precede the appropriate event entry with a semicolon (;).

¶ Add filter criteria to the r3slogIID.conf file. See “FilteringEvents” on page 107.

Adding New Entries to the r3slogIID.cl FileIf you want to define additional syslog events to send to the eventconsole, add new syslog event entries to the r3slogIID.cl file inthe following format: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 is 30 (warning).

ClassnameSpecifies the event class. This parameter is optional. If youdo not specify an event class, the default class isSAP_SYSLOG_msgID, where msgID is the three-charactermessage ID. The SAP_SYSLOG_msgID event 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. Ifyou need to create specific Syslog event classes by messageID, 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:


6.M

anag

ing

R/3

Even

ts

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

SAP_SYSLOG_MSG forsyslog message, msgID,where msgID 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 Tivoli EnterpriseConsole events. The IDOC Event Adapter sends the following eventsto the event console:

¶ 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 Tivoli Enterprise Console. A harmlessSAP_IDOC_STATUS event is also sent for each IDOC when theIDOC 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,


6.M

anag

ing

R/3

Even

ts

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

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 Tivoli EnterpriseConsole events during the first polling cycle, and it does notgenerate events for IDOCs that have a non-error status from onepolling cycle to the next.

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 event console events(SAP_IDOC_STATUS and SAP_IDOC_XMIT events) as illustratedin the following Tivoli Enterprise Console event log:


Tivoli Manager for R/3 reports the most current information abouteach IDOC by using Tivoli Enterprise Console rules that closeduplicate SAP_IDOC_STATUS events. A duplicateSAP_IDOC_STATUS event is identified by three events 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 202.

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 event console can help you determinewhich SAP_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 give


6.M

anag

ing

R/3

Even

ts

you 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 event console provides information to helpyou determine the cause of the transmission problem associated witha SAP_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.

Controlling IDOC EventsYou can control the IDOC events to be sent to the event console bymodifying the r3idocIID.conf file, where IID represents thetwo-digit R/3 instance number. The r3idocIID.conf file is createdafter you run the Configure Event Adapter task and, therefore, existsonly after you have run this task at least once for the specific R/3application server. The r3idocIID.conf file is located in one of thefollowing directories:




You can customize the r3idocIID.conf file in the following ways:

¶ Add filter statements to minimize the number of events that aresent to the event console by filtering the events at the IDOCEvent Adapter. For more information, see “Filtering Events” onpage 107.

¶ 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 thedefault values that the IDOC Event Adapter uses:

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.

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


6.M

anag

ing

R/3

Even

ts

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 yourevent server. This section provides information to help you evaluateyour environment so that you can determine a configuration thatmeets 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 Tivoli Enterprise Consoleevents. Thus, both ability of the R/3 system to automatically resolveIDOC errors and the IDOC Event Adapter polling interval affect thenumber and type of IDOC events that you see on your eventconsole.

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 event server. Considerthe 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 events for which you do not need to takeaction. In this case, setting the polling interval to a higher rate (5


to 15 minutes) can cause a higher percentage of IDOC eventssent to the event console 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 Tivoli Enterprise Console events forpertinent IDOCs at each polling interval, if you have manyIDOCs in your R/3 system, a higher polling interval can result inmany IDOC events (several hundred or more) to be sent to yourevent server at the 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 102. 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 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 beextended. 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:


6.M

anag

ing

R/3

Even

ts

¶ 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 Tivoli Enterprise Console in ten seconds.

¶ The 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.

¶ Event server

v IntelliStation

– One 333 MHz processor

– 256 MB RAM

– One 6.2 GB IDE disk

– Windows NT 4.0

– Tivoli Enterprise Console 3.6.1 using the default rule base

– Oracle 7.xx as the RIM RDBMS

The event load for the event server was limited to the eventsfrom the IDOC Event Adapter.


Filtering EventsYou might not want certain types of R/3 events to appear on yourevent consoles because you regard them as harmless or unlikely torequire action. The event console provides the following ways foryou to filter out events that you do not want to view:

¶ You can specify that the event is not to be forwarded to theevent server. To do this, specify filter criteria in the appropriateevent adapter configuration files. Here is an example of a Filterstatement:FilterMode=OUTFilter:Class=SAP_ALERT_Trace;r3configDBName=TV5

For more information about filter statements, refer to the TivoliEnterprise Console Adapter’s Guide.

Specify the filter criteria in one or more of the followingconfiguration files:

Event Adapter Configuration File

Alert r3mibIID.conf

CCMS r3moniIID.conf

Syslog r3slogIID.conf

IDOC r3idocIID.conf

Alternatively, if you want to distribute a common set of filterstatements to multiple endpoints, you might consider specifyingthe filter criteria in one or more of the following event adaptertemplate configuration files on the gateways:

Event Adapter Template Configuration File

Alert tecad_wr3mib.conf

CCMS tecad_wr3moni.conf

Syslog tecad_wr3slog.conf

IDOC tecad_wr3idoc.conf


6.M

anag

ing

R/3

Even

ts

The template configuration files are located in the$BINDIR/TME/SAP/2.2C directory on the gateways.

To run an event adapter with the filter criteria specified in thetemplate configuration file, follow these steps:

1. Update the template configuration file on the gateway.

2. Delete the instance-specific configuration file(r3mibIID.conf, r3moniIID.conf, r3slogIID.conf, orr3idocIID.conf), if it exists, on each R/3 application serverendpoint.

3. Run the Configure Event Adapter task to create theinstance-specific configuration file.

When you run the Configure Event Adapter task, the updatedtemplate configuration file is automatically distributed to theendpoint, and the instance-specific configuration file iscreated based on this updated template.

4. Start the appropriate event adapter to incorporate thechanges.

¶ You can create new rules to exclude the event. In this case, theevent is forwarded to the event server, but it is eliminated by therules engine. Refer to the Tivoli Enterprise Console RuleBuilder’s Guide for more information.


Monitoring R/3 Resources

This chapter describes the monitoring collections that TivoliManager for R/3 provides to help you manage R/3 resources. Thischapter also explains how to use and customize Tivoli Manager forR/3 monitors.

Like any Distributed Monitoring monitor, these R/3-specific monitorsmust 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 the Tivoli Distributed Monitoring User’s Guide.

Tivoli Manager for R/3 monitors are specifically designed to workwith object types provided with the Tivoli Manager for R/3 productjust as Distributed Monitoring monitors are designed to work withthe standard Tivoli endpoints and managed nodes. Distribution ofone product’s monitors to another product’s endpoints is notsupported. This means that you cannot distribute Tivoli Manager forR/3 monitors to managed nodes and endpoints, and you cannotdistribute Distributed Monitoring monitors to Tivoli Manager for R/3object endpoints. For example, distribute the application server statusmonitor to an R3AppServer object and not to a managed node orendpoint.

7


7.M

on

itorin

gR

/3R

esou

rces

Monitoring CollectionsTivoli Manager for R/3 provides the following monitoringcollections for the 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 is to run, one ormore threshold levels, and actions to be taken at each threshold.

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


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. TivoliManager for R/3 provides the R3 Server Remote and R3 ServerCentral monitoring 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 Tivoli 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. Tivoli Manager for R/3 is able to providecentral monitors 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 Tivoli server andcommunicate with an R/3 application server using an R/3 RFC. Youspecify the R3AppServer endpoint as an attribute when you add themonitor. Tivoli Manager for R/3 provides a list of validR3AppServer objects from which to select when setting the attribute.

The following table lists the monitoring sources, their correspondingmonitoring collection, and a reference to the attributes that pertain tothat source.


7.M

on

itorin

gR

/3R

esou

rces

Source

R3 ServerRemote

Collection

R3 ServerCentral

CollectionAttributeReference

Roll AreaX X

See “Roll Area” onpage 217

Page AreaX X

See “Page Area” onpage 218

Work ProcessX

See “Work ProcessSource” onpage 219

Work ProcessDispatch Queue

X

See “Work ProcessDispatch QueueSource” onpage 220

Long Running WorkProcess

X

See “Long RunningWork ProcessSource” onpage 220

CUA Menu and TextBuffer

X XSee “Buffer” onpage 221

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 221


Source

R3 ServerRemote

Collection

R3 ServerCentral

CollectionAttributeReference

OS Collect -Application Server

X XSee “OS Collect” onpage 216

Application ServerStatus

XNo attributes

Dialog PerformanceX

See “Performance”on page 222

Update PerformanceX


Batch PerformanceX


Spool PerformanceX


OS Collect -Database Server

XSee “OS Collect” onpage 216

OS/390X

See “OS/390” onpage 225

OS/390 DB2X

See “OS/390 DB2”on page 223

Cancelled Job X No attributes

Heap Memory X X See “Heap MemorySource” onpage 222

Extended Memory X X See “ExtendedMemory Source” onpage 222

User X X See “User Source”on page 223

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.


7.M

on

itorin

gR

/3R

esou

rces

These monitors are organized according to the underlying operatingsystem. For more information, see “Using the File System Monitors”on page 120.

Default Profile ManagersTo facilitate immediate monitoring capabilities, Tivoli Manager forR/3 provides 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 Tivoli server. Monitoring of remotemachines is performed from the Tivoli region by distributingthe profile 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 Tivoli server.


Monitoring of the remote machines is performed from the Tivoliregion by distributing 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 endpoints tothis profile manager. This profile manager contains the followingprofiles:

R3 Windows NT Print MonitorsContains a monitor for reporting the status (up or down) ofthe saplpd daemon on Windows.

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 Tivoli server. Subscribe the appropriate managed nodes to thisprofile manager. Refer to the Tivoli Management Framework User’sGuide for more information about creating a profile within a profilemanager.

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.


7.M

on

itorin

gR

/3R

esou

rces

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

Tivoli Manager for R/3 ships a message server statusmonitor for UNIX and for Windows in different monitoringcollections: R3 UNIX File System Monitors and R3Windows NT File System Monitors. Tivoli 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 Windowsonly, replace the message server status monitor in the R3Message Server Monitors profile with a message serverstatus monitor for Windows. If you want to run a messageserver status monitor for both UNIX and Windows, eithercreate a new profile that contains a message server statusmonitor for Windows or add a message server status monitorfor Windows to the R3 Windows NT File System Monitorsprofile.

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


page 120. Distribute this profile to each Windows R/3application server that has a unique file system.

Using Monitoring SourcesThe following topics provide additional information about using theTivoli Manager for R/3 monitoring sources:

¶ “Using the Application Server Status Monitor”

¶ “Using the Storage Monitors” on page 118

¶ “Using the Performance Monitors” on page 119

¶ “Using the File System Monitors” on page 120

¶ “Using the User Monitor” on page 123

¶ “Using the Work Process Monitors” on page 123

¶ “Using the Cancelled Job Monitor” on page 125

¶ “Using OS Collect and OS/390 Monitors” on page 127

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 Tivoli Manager for R/3 events. Therefore, thismonitor must be properly configured and must be distributed to allR/3 application servers for complete and accurate Tivoli Manager forR/3 processing. You must manually distribute this monitor aftercreating the R3AppServer objects.

Tivoli Manager for R/3 provides a correctly configured applicationserver status monitor in the R3 Server Autodiscovery Monitorsprofile. This monitor supports the following response levels thatcorrespond to each of the returned statuses:

¶ Critical level is set when the monitor returns Becomesunavailable.

¶ Reset level is set when the monitor returns Becomes available.

¶ Warning level is set when the monitor returns Becomesstandby.


7.M

on

itorin

gR

/3R

esou

rces

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 the always response level.

The default Application Server Status monitor is configured togenerate an event for each of the response levels. These events mustbe generated so that Tivoli Manager for R/3 rules can properly closeTivoli 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 TivoliManager for R/3 processing, 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.

Tivoli Manager for R/3 processing depends on the generation of asingle event 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 MonitorsTivoli Manager for R/3 provides monitors in the R3 Server Remoteand R3 Server Central monitoring collections for many of the keystorage areas in R/3 application servers. You can monitor critical


values, such as free space, used spaced, and percentages for manystorage areas. The specific values that can be monitored depend onthe particular storage area. You can monitor the following storageareas:

¶ 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 215.

Using the Performance MonitorsTivoli Manager 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


7.M

on

itorin

gR

/3R

esou

rces

¶ Spool

For a complete listing of the monitoring sources and how they relateto the R/3 system, see “Remote and Central Monitoring Sources” onpage 215.

Using the File System MonitorsTivoli Manager for R/3 provides file system monitors that make iteasier for you to monitor R/3 file systems than if you usedDistributed Monitoring file system monitors. Many R/3 file systemshave names that include the R/3 SID. For example, the transportdirectory is named /usr/sap/SID/trans. To monitor the transportdirectory using Distributed Monitoring monitors, you would need tocreate a monitoring profile for each SID, and you would need toensure that you distributed the correct monitoring profile to theappropriate R/3 application server. Because Tivoli Manager for R/3file system monitors automatically substitute the SID based on theR/3 application server to which the monitoring profile is distributed,you can create one profile that you distribute to multiple R/3application servers.

Tivoli Manager for R/3 provides two monitoring collections: R3UNIX File System Monitors and R3 Windows NT File SystemMonitors that contain monitoring sources for various R/3 UNIX andWindows file 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, where SID 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, where n represents a numberfrom 1 through 20. Specify sapdata1 throughsapdata20 in the Monitor Arguments section of theAdd Monitor dialog.

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.

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 WindowsNT file system monitors rely on Windows registry keys and valuenames that are set when R/3 is installed using SAP installation tools.


7.M

on

itorin

gR

/3R

esou

rces

Note: If you have reconfigured your system or moved files afterinstalling R/3, you must ensure that the Windows registryreflects your changes.

You can monitor various R/3 Windows file systems for the followingvalues:

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,where SID is the three-character R/3 system identifier, and the valuename that must exist in the Windows registry:

File System Windows Directory Windows Value Name

SAP Home ...\usr\sap\SID ImagePath

Oracle ...\oracle\SID SAPDATA_HOME

Oracle datan ...\oracle\SID\sapdatan, where n 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

Oracle Check ...\oracle\SID\sapcheck SAPCHECK

Oracle Statistics ...\oracle\SID\sapstat SAPSTAT

Oracle Trace ...\oracle\SID\saptrace SAPTRACE


File System Windows Directory Windows Value Name

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.

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

Using the Work Process MonitorsTivoli Manager for R/3 provides the following monitors in the R3Server Remote monitoring collection that enable you to monitor R/3work processes:

¶ Work Process

¶ Work Process Dispatch Queue

¶ Long Running Work Process

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


7.M

on

itorin

gR

/3R

esou

rces

¶ 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 219.

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

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

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.

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.


7.M

on

itorin

gR

/3R

esou

rces

The Cancelled Job monitor reports the number of cancelled jobs forwhich the monitor has 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 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 rules to processthe event, keying on the job name, for example. If you want tomonitor for periods of high batch job failure, you can set thresholdsagainst the reported value of the monitor. In both cases, you willneed a general idea of the expected cancelled job rate to properly setthe monitoring interval. As a recommendation, set your monitoringinterval to be two to three times the rate at which you expect batchjob 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 116). Distributing the Cancelled Job monitor tomultiple 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 to


provide 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 Tivoli Manager for R/3 areintended to be run directly on the remote endpoints. Typically, theseendpoints are the R/3 application server machines. The OS/390 andsome of the OS Collect monitors do not fit this model. BecauseTivoli Manager for R/3 does not always have direct access to theR/3 database server, database monitoring information is collectedindirectly using R/3 itself to provide the information. This sectionexplains the differences between the OS/390 and OS Collectmonitoring sources and 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 Tivoli 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.

2. Add a monitor using the OS 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.


7.M

on

itorin

gR

/3R

esou

rces

To use these monitors on the Tivoli 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 the OS 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 Tivoliserver 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 the OS Collect - Database Server source.

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 the OS/390 source.



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 the OS/390 DB2 source.




7.M

on

itorin

gR

/3R

esou

rces


Tasks for Managing R/3Resources

Tivoli Manager for R/3 provides the following task libraries thatinclude tasks 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: Tivoli Manager for R/3 also provides task libraries thatcontain configuration tasks to help you configure the TivoliManager for R/3. See “Using Tivoli Manager for R/3Configuration Tasks” on page 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

for

Man

agin

gR

/3R

esou

rces

1. From the desktop, open the Manager 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 Tasks to display R/3 system tasks

¶ R3 App Server Tasks to display application server tasks

¶ R3 DB Server Tasks to display database server tasks

¶ R3 ITS Server Tasks to 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 the R3 App Server Tasks icon.


8.Tasks

for

Man

agin

gR

/3R

esou

rces

3. Run the appropriate task to display the Execute Task dialog.

4. Complete the Execute Task dialog, 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 as SID_DBhostname (R3System).

¶ For an R/3 application server task, select an endpoint of typeR3AppServer, such as hostname_SID_IID (R3AppServer)

¶ For an R/3 database server task, select an endpoint of typeR3DBServer, such as hostname_SID_DB (R3DBServer).


¶ For an R/3 ITS server task, select an endpoint of typeR3ITSServer, such as hostname_VIIN_ITS (R3ITSServer).

For more information, see “Tivoli Manager for R/3 ObjectEndpoints” on page 29.

5. Click Execute and Dismiss to start the task. If the task requiresarguments, a dialog is displayed.

If a dialog is displayed, complete the dialog and then click Setand Execute to 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 SystemTivoli Manager for R/3 provides the following tasks in the R3System Tasks 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

for

Man

agin

gR

/3R

esou

rces

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 137

¶ Start EventAdapter

¶ Stop EventAdapter

r3_user R3AppServerendpoint

“ControllingApplicationServers” onpage 137

¶ Start Server

¶ Stop Server


“DisplayingApplicationServerPerformanceInformation” onpage 138

¶ Display BufferInformation

¶ Display Roll PageInformation

¶ Display OSCollectInformation

¶ Display OS/390Information

¶ Display OS/390DB2 Information




“Managing BatchJobs” onpage 138

¶ Display BatchJobs

¶ Cancel Batch Job

¶ Release Batch Job


“Controlling R/3Work Processes”on page 139

¶ Display WorkProcesses

¶ Cancel WorkProcess


Controlling Event AdaptersTivoli Manager for R/3 provides the following tasks in the R3 AppServer Tasks library to control event adapters:

Start Event AdapterStarts the Alert Event Adapter, the CCMS Event Adapter, theSyslog Event Adapter, or the IDOC Event Adapter on thespecified R/3 application server.

Stop Event AdapterStops the Alert Event Adapter, the CCMS Event Adapter, theSyslog Event Adapter, or the IDOC Event Adapter on thespecified R/3 application server.

A dialog is presented in which you specify which adapter to start orstop.

Controlling Application ServersTivoli Manager for R/3 provides the following tasks in the R3 AppServer Tasks 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

for

Man

agin

gR

/3R

esou

rces

Note: The stop command output may sometimes report an errorwith awk. This is caused when the SAP-provided stopsapscript 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 Tivoli Manager for R/3 monitors report, exceptfor percentages which are calculated. For more information about theinformation that is returned, each task in the following list includes areference to the appropriate Tivoli Manager for R/3 monitor.

¶ Display Buffer Information. See “Buffer Source” on page 221.

This task presents a dialog in which you can specify the R/3buffer type. The default is PXA – Program Buffer.

¶ Display Roll Page Information. See “Roll Area Source” onpage 217 and “Page Area Source” on page 218.

¶ Display OS Collect Information. See “OS Collect Source” onpage 216.

¶ Display OS/390 Information. See “OS/390 Source” on page 225.

¶ Display OS/390 DB2 Information. See “OS/390 DB2 Source” onpage 223.

Managing Batch JobsTivoli Manager 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 ProcessesTivoli Manager for R/3 provides the following tasks to help youmanage R/3 work processes:

Display Work ProcessesDisplays information for R/3 work processes that are runningon the specified application server. R/3 work processinformation includes the process ID, status, reason, and CPUtime. A dialog is displayed in which you can specify if youwant the CPU time for each process to be returned as part ofthe data.

Cancel Work ProcessCancels an R/3 work process. A dialog is displayed in whichyou specify the process ID and if you want a core dump.Use the Display Work Processes task to determine theappropriate process ID.


8.Tasks

for

Man

agin

gR

/3R

esou

rces

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 ServerTivoli Manager for R/3 provides the following tasks to control theR/3 database 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 as sidadm 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 machine.

2. Starting or stopping a Windows database server requirescustomer exit routines. For more information, see “Creating ExitRoutines for Windows” 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 the dbaccess xterm window is


displayed. You can use structured query language (SQL) commandsto access the R/3 database. Press the Ctrl-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 ServersTivoli Manager for R/3 provides the following tasks in the R3 ITSServer Tasks 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

for

Man

agin

gR

/3R

esou

rces


Distributing SAPGUI Software

This chapter describes how to create SAPGUI software file packagesfor distribution of the SAPGUI for Windows, Windows 95/98, andUNIX. It also 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 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 144.

Note: Software Distribution must be installed on the Tivoliserver.

¶ For Windows and Windows 95/98 SAPGUI versions 4.5B andlater, see “Creating SAPGUI File Packages for WindowsSAPGUI Versions 4.5B and Later” on page 147.

9


9.D

istribu

ting

SA

PG

UI

So

ftware

Note: Software Distribution must be installed on the R/3SAPGUI installation server, and SAP requires that the R/3SAPGUI installation server resides on a Windowsmachine.

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 and Windows 95/98 prior to Version 4.5B andfor 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 Tivoli server before executing this job.

For Windows 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 andWindows 95/98 Start menus for sapgui.exe, saplogon.exe,and sapicon.exe. On Windows targets, the AFTER script willbe able to find the location of the sapgui.exe, saplogon.exe,and sapicon.exe executables regardless of where they existwithin the source code. On Windows 95/98 targets, you mustplace these executables at the root of the directory in whichthe source code resides.

¶ Configure UNIX Client Install

This is an R/3 native installation.

¶ Configure Windows 95/98 Client Install

This is an R/3 native installation.

¶ Configure Windows NT Client Install

This is an R/3 native installation for Windows NT andWindows 2000.

The platform-specific Configure Client Install dialog is displayed.For example, the following dialog is displayed as a result of


9.D

istribu

ting

SA

PG

UI

So

ftware

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), whereConfigurationName is 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, considerusing the optional command fields on the platform-specificConfigure Client Install dialog.

Creating SAPGUI File Packages for Windows SAPGUIVersions 4.5B and Later

For Windows and Windows 95/98 SAPGUI versions 4.5B and later,SAPGUI file packages are created on an R/3 SAPGUI installationserver using R/3 tools and procedures. Tivoli 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 andTivoli Manager for R/3 must be installed on the SAPGUI installationserver.

To create SAPGUI file packages for distribution of the SAPGUI forWindows 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 148. Otherwise, run the List Available SAPGUIFile Packages task 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

istribu

ting

SA

PG

UI

So

ftware

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 the List 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 Package task 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 the car program. Each selectable SAPGUI optioncorresponds to a car file that will be unpacked duringinstallation.

¶ For native installations of SAPGUI versions prior to 4.5B onWindows and Windows 95/98, the installation is performed bycalling the SAP-provided sapsetup program.

Note: For Windows 95/98 installations, the sapsetup programreturns control to the installation AFTER program beforesapsetup actually completes its processing. If errors occurin the sapsetup program 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 and Windows 95/98, the installation is performed byusing 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

istribu

ting

SA

PG

UI

So

ftware

SAPGUI file package on a machine that is in the samedomain 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 the Profile Manager menu, select Subscribers and 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 endpoints, follow thesesteps to change the file package profile manager from databasemode to dataless mode:

a. From the Profile Manager window, from the Edit menu,select Profile Manager to display the Edit Profile Managerdialog.

b. Select Dataless Endpoint Mode. Then click Change &Close.

Note: For more information about database mode anddataless mode profile managers, refer to the TivoliManagement Framework User’s Guide.

3. Right-click the file package icon and select Distribute from thepop-up menu.

4. Complete the Distribute File Package dialog, referring to theonline help for additional information.

For more information, refer to the Tivoli Software DistributionUser’s Guide.


Tivoli Business SystemsManager Instrumentation for R/3

You can optionally manage R/3 resources on a Tivoli managed nodeor endpoint from the Tivoli Business Systems Manager console. Todo this, you must install the following:

1. Tivoli Manager for R/3, Version 2.2.0

2. Tivoli Business Systems Manager Instrumentation for R/3,Version 2.2.0

This chapter provides an overview of Tivoli Business SystemsManager, and it describes how you can manage R/3 resources fromthe Tivoli Business Systems Manager console. This chapter alsodescribes the installation prerequisites and how to install anduninstall Tivoli Business Systems Manager Instrumentation for R/3(R/3 instrumentation).

Tivoli Business Systems Manager defines the concept of a businesssystem to organize related applications. A business system includesall the applications that together perform a business function, such asTivoli Manager for R/3 processing. It also includes performancemeasures that determine whether the business system is functioningproperly. For more information about Tivoli Business SystemsManager, refer to the Tivoli Business Systems Manager productdocumentation.

10


10.R

/3In

strum

entatio

n

Understanding Tivoli Business Systems ManagerTivoli Business Systems Manager consists of the followingcomponents:

¶ Tivoli Business Systems Manager management server

¶ Tivoli Business Systems Manager console

¶ Tivoli Business Systems Manager event enablement

¶ Tivoli Business Systems Manager task server

Tivoli Business Systems Manager Management ServerThe Tivoli Business Systems Manager management server interactswith instrumented applications, such as R/3, to provide informationfor display on the Tivoli Business Systems Manager console. TheTivoli Business Systems Manager management server is the recipientof heartbeat events from instrumented application components. Themanagement server receives events from the event server. Using thisinformation, Tivoli Business Systems Manager creates and maintainsa view of the components and their availability.

The Tivoli Business Systems Manager management server furnishesthe Tivoli Business Systems Manager console with a set of tasks thatare applicable for a component. The management server stores fileson behalf of the Tivoli Business Systems Manager console, includingicons, customized views, and settings.

Tivoli Business Systems Manager ConsoleThe Tivoli Business Systems Manager console graphically displaysthe component information from the Tivoli Business SystemsManager management server. As the Tivoli Business SystemsManager management server receives status updates pertaining to thecomponent information, it updates the Tivoli Business SystemsManager console, enabling you to view the status of the component.

Alerts are overlaid on the component object when availability of thatcomponent is threatened. The Tivoli Business Systems Managerconsole can run Tivoli tasks on behalf of the Tivoli BusinessSystems Manager management server and display the output of thetasks.


Tivoli Business Systems Manager Event EnablementTivoli Business Systems Manager Event Enablement is installed onthe event server and causes the event server to forward TivoliBusiness Systems Manager instrumentation events to the TivoliBusiness Systems Manager management server. Event Enablementdefines event classes and rules for handling Tivoli Business SystemsManager-related events.

Tivoli Business Systems Manager Task ServerThe Tivoli Business Systems Manager task server is installed withEvent Enablement. The task server receives task requests from theTivoli Business Systems Manager console, runs the tasks on theTivoli server on which it is installed, and returns the output to TivoliBusiness Systems Manager.

Tivoli Business Systems Manager Event HandlingThe Tivoli Business Systems Manager management server discoversthe R/3 components upon receipt of heartbeat events. As the TivoliBusiness Systems Manager management server receives monitor andstatus updates for the R/3 component, it updates the Tivoli BusinessSystems Manager console. Event Enablement must be installed andconfigured on the event server for Tivoli Business Systems Managerevents to be forwarded from the event server. Configuring EventEnablement includes defining the APM_HEARTBEAT andAPM_THRESHOLD event classes for the event server.

Preparing to Install R/3 InstrumentationBefore installing R/3 instrumentation, meet the followingrequirements:

¶ Tivoli regions must be properly configured.

¶ Tivoli Business Systems Manager must be installed andoperational.

¶ Tivoli administrators need the following authorization roles:

v To install R/3 instrumentation, install_product authority isrequired.


10.R

/3In

strum

entatio

n

v To start tasks from the Tivoli Business Systems Managerconsole, super authority is required for the user ID that startsEvent Enablement and the task server.

Installing and Configuring R/3 InstrumentationThe following table shows the location of the installed components:

Installed Component Tivoli BusinessSystems ManagerServer

Tivoli Server

Instrumentationdefinition files

X

Instrumentation tasklibraries

X

Installing the R/3 Instrumentation Definition FilesTo install the R/3 instrumentation definition files, you must installthe applications management package file (sapr3_22.pkg) on theTivoli Business Systems Manager database server. To do this, followthese steps:

Note: The commands use in the procedure assume that the\TivoliManager\xdfparser\bin directory is included inyour path statement.

1. Create a directory structure on a local drive in which to copy thesapr3_22.pkg file and to create the files that you will install onthe Tivoli Business Systems Manager database server. Thisprocedure uses the following directories:

Directory Purpose

Local_drive:\sapr3_22\pkg Contains the contents of thesapr3_22.pkg file

Local_drive:\sapr3_22\sqi Contains the sqi files used to buildthe R/3 components


Directory Purpose

Local_drive:\sapr3_22\tll Contains the sqi file that is createdfrom the tll file used to associate thetask library with the R3Applicationcomponent

2. Unzip the contents of the sapr3_22.pkg file from the\TBSMFILES directory on the Tivoli Manager for R/3 CD into theLocal_drive\sapr3_22\pkg directory.

3. Create the sqi files from the Tivoli Business Systems Managerdefinition files. From the Local_drive:\sapr3_22\pkg directoryin a Korn shell window, enter the following command:parser.sh –d '.' –o 'Local_Drive:\sapr3_22\sqi'

4. Install the sqi files on the Tivoli Business Systems Managerdatabase server. From the Local_Drive:\sapr3_22\sqidirectory, enter the following command:bldgemsc.sh –S 'DB_Server_name' –U 'userid' –P 'password' –f '*'

Where DB_Server_name is the host name of your TivoliBusiness Systems Manager database server, userid is yourdatabase user ID, and password is the password for the specifieduser ID.

5. Create the task library sqi file from the tll file. From theLocal_Drive:\sapr3_22\pkg, enter the following command:TllParser.sh –p 'R3Application' –v '2.2.0' –t \'TL_SAPR3_2.2.0_Default_R3Application_2.2.0_%REGION_NAME%' \–o 'Local_drive:\sapr3_22\tll' –f 'R3ApplicationTBSM.tll'

6. Install the task library sqi file on the Tivoli Business SystemsManager database server. From theLocal_Drive:\sapr3_22\tll directory, enter the followingcommand:bldgemtasks.sh –S 'Db_Server_name' –U 'userid' –P 'password' \–f 'R3ApplicationTBSM.tll.sqi'

7. Recycle the Tivoli Business Systems Manager database server.


10.R

/3In

strum

entatio

n

Installing the R/3 Instrumentation Task LibrariesTo install the R/3 instrumentation task libraries on the Tivoli server,follow these steps:


2. From the desktop, select Install Product from the Install menuto display the Install Product dialog.

3. Click Select Media to display the File Browser dialog.

4. On the File Browser dialog, type the full path to the R/3instrumentation installation files in the Path Name text field.The R/3 instrumentation files are located in the /TBSMIMAGEdirectory on the Tivoli 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. The Tivoli Business Systems ManagerInstrumentation for R/3, Version 2.2.0 product is listed in theSelect Product to Install scrolling list.

7. Select Tivoli Business Systems Manager Instrumentation forR/3, Version 2.2.0 in the Select Product to Install scrollinglist.

8. Select the targets on which you do not want to install R/3instrumentation from the Clients to Install On list and click theright arrow button to move them to the Available Clients list.

Note: Install R/3 instrumentation on the Tivoli 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 displays messages that show theprogress of the installation.

Note: Successful installation is not indicated by a Finishedproduct installation message. You must look at the


messages in the task output dialog to determine whetherthe product installation was successful.

11. Click Close.


R/3 instrumentation is installed in thePR_SAPR3_Default_region_name policy region within theApplications_region_name policy region on the desktop.

Adding the R/3 Instrumentation Rule SetThe R/3 instrumentation rule file, sap_gemevents.rls, includesevent server rules that forward all Tivoli Manager for R/3 heartbeatevents to the Tivoli Business Systems Manager server. To addthe sap_gemevents.rls rule file to the current rule set, use theTivoli Manager for R/3 Configure Event Server task. See“Configuring the Event Server” on page 82.

Note: If you ran the Configure Event Server task before youinstalled R/3 instrumentation, you must run the ConfigureEvent Server task again to install the sap_gemevents.rlsrule file.

Instrumented ComponentsR/3 instrumentation includes instrumentation for the componentswhich correspond to each Tivoli Manager for R/3 object as describedin the following table:

R/3 Instrumentation Component Tivoli Manager for R/3 Object

R3System R3System

R3Application R3AppServer

R3Database R3DBServer

R3ITSServer R3ITSServer


10.R

/3In

strum

entatio

n

R/3 Instrumentation Desktop StructureSuccessful installation of R/3 instrumentation creates task librariesthat are visible on the Tivoli desktop. The following is an overviewof the resulting desktop structure:Top-Level Policy Region Applications _region_name

Policy Region PR_SAPR3_Default_region_nameTask LibrariesTL_SAPR3_2.2.0_Default_R3System_2.2.0_region_nameTL_SAPR3_2.2.0_Default_R3Application_2.2.0_region_nameTL_SAPR3_2.2.0_Default_R3Database_2.2.0_region_nameTL_SAPR3_2.2.0_Default_R3ITSServer_2.2.0_region_name

Synchronizing the Tivoli Business Systems ManagerConsole with the Tivoli Desktop

The Tivoli Business Systems Manager console is synchronized withthe Tivoli Manager for R/3 objects on the Tivoli desktop. When anR/3 object is created, a heartbeat event is automatically sent to theevent server. The event server forwards the event to the TivoliBusiness Systems Manager server, and an icon is displayed on theTivoli Business Systems Manager console. If the Tivoli BusinessSystems Manager console becomes unsynchronized with the desktop,run the Send Heartbeat task in the R3 Configuration Tasks libraryagainst the appropriate R3System, R3AppServer, R3DBServer, andR3ITSServer objects. The Send Heartbeat task sends a heartbeatevent to the Tivoli Business Systems Manager server for each R/3resource, and an icon is created on the Tivoli Business SystemsManager console, if needed. The Tivoli Business Systems Managerconsole might not be synchronized with the desktop if the TivoliBusiness Systems Manager server was down when the R/3 objectwas created, if you installed R/3 instrumentation after you createdthe R/3 objects, or if the Tivoli Business Systems Manager databaseswere erased.


Deleting R/3 ResourcesTo delete R/3 resources, delete the R/3 objects on the desktop. AGONE heartbeat is generated for the object. and the GONE heartbeatevent is automatically sent to the event server. The component isdeleted from the Tivoli Business Systems Manager managementserver database and the icon is removed from the Tivoli BusinessSystems Manager console.

Navigating to R/3 ResourcesYou can view R/3 resources in Tivoli Business Systems Manager inthe following ways:

¶ Tree view, which displays objects in a hierarchical tree format.This is the default view.

¶ HyperView, which displays objects in an elliptical view from thelaunch point of the selected object.

¶ Managed Object view, which displays objects in list or columnformat that has sorting capabilities.

¶ Business Impact view, which displays objects in a combinationpictorial and list view.

To locate a specific R/3 resource in the tree view, follow these steps:

1. Open the Tivoli Business Systems Manager console.

2. Expand the Business Object Container icon or the Line ofBusiness Container icon and locate the R/3 resource icon asfollows:

¶ In the Business Object Container:BUSC view, the defaultplacement of the R/3 resource icon depends on the TCP/IPhost name of the business component that forwarded theevent.

¶ In the Line of Business Container:LOBC view, the defaultplacement of the icon appears in the following places:

v Line of Business: SAP R3System 2.2.0

v Line of Business: SAP R3Application 2.2.0


10.R

/3In

strum

entatio

n

v Line of Business: SAP R3Database 2.2.0

v Line of Business: SAP R3ITSServer 2.2.0

You can view additional information using the HyperView,Managed Object view, and Business Impact view. The followingfigure illustrates the Tree view of the Business Object:

3. Double-click the object to obtain the object detail properties,such as current events, object attributes, or alerts. For moreinformation, refer to the Tivoli Business Systems Managerproduct documentation.


Locating and Running R/3 Instrumentation TasksTo run R/3 instrumentation tasks from the Tivoli Business SystemsManager console, select the task from the pop-up menu on anR3System, R3Application, R3Database, or R3ITSServer icon. Thefollowing is an example of an R3Application icon’s pop-up menu:

R3System Component TasksTivoli Business Systems Manager supports the following subset ofTivoli Manager for R/3 tasks for the R3System component:

¶ Start_System

¶ Stop_System

See “R3 System Tasks” on page 135 for more information aboutthese tasks.

R3Application Component TasksThe following R/3 instrumentation task is available for theR3Application component:

¶ Query_State

Reports whether the R/3 application server is up (running andaccepting R/3 logons), standby (running and not accepting R/3


10.R

/3In

strum

entatio

n

logons), or down (not running).Tivoli Business Systems Manager also supports the following subsetof Tivoli Manager for R/3 tasks 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 136 for more informationabout these tasks.

R3Database Component TasksThe following R/3 instrumentation task is available for theR3Database component:

¶ Query_State

Reports whether the R/3 database server is up, unknown, ordown.

Tivoli Business Systems Manager also supports the following subsetof Tivoli Manager for R/3 tasks for the R3Database component:

¶ Start_Database

¶ Stop_Database

See “R3 DB Server Tasks” on page 140 for more informationabout these tasks.


R3ITSServer Component TasksThe following R/3 instrumentation task is available for theR3ITSServer component:

¶ Query_State

Reports whether the R/3 ITS server is up, unknown, or down.Tivoli Business Systems Manager also supports the following subsetof Tivoli Manager for R/3 tasks for the R3ITSServer component:

¶ Start_ITS_Server

¶ Stop_ITS_Server

See “R3 ITS Server Tasks” on page 141 for more information aboutthese tasks.

Supported MonitorsR/3 instrumentation provides monitor collections that contain TivoliManager for R/3-supported monitors. All monitors communicate withTivoli Business Systems Manager by sending Tivoli EnterpriseConsole events to the event server. Event Enablement then forwardsthe event to the Tivoli Business Systems Manager managementserver. Tivoli Business Systems Manager maps the event severityslot value to a Tivoli Business Systems Manager alert state andpriority. If the event is threatening the availability of the monitoredresource, an alert is overlaid on that object. For more informationabout Tivoli Business Systems Manager, refer to the Tivoli BusinessSystems Manager product documentation.

To use Tivoli Manager for R/3 monitors with Tivoli BusinessSystems Manager, add the monitors to your Distributed Monitoringprofile and configure the monitors to send events. Before you runthe monitors, run the Configure Event Server task to specify the hostname of Tivoli Business Systems Manager management server towhich events should be forwarded. The events are translated intoAPM_THRESHOLD events at the event server and are forwarded tothe Tivoli Business Systems Manager management server.


10.R

/3In

strum

entatio

n

R/3 instrumentation supports the following Tivoli 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 215 for moreinformation.

R/3 instrumentation also supports the Database Server Status andITS Server Status monitors for the R3Database and R3ITSServercomponents, respectively.

Viewing the Current Events StatusTo view the status of current events, expand an icon for the specificR/3 resource.

Uninstalling R/3 InstrumentationTo uninstall R/3 instrumentation, go to the$BINDIR/../generic_unix/TME/SAPUNINST directory and enter oneof the following commands:

¶ UNIX:R3Mgr_uninstall22.pl –g


¶ Windows:perl R3Mgr_uninstall22.pl –g

For more information about the R3Mgr_uninstall22.pl command,see “Uninstalling Tivoli Manager for R/3” on page 22.

Troubleshooting R/3 InstrumentationThis section contains some questions and answers that might helpyou resolve problems related to using R/3 instrumentation.

Why am I not seeing any R/3 instrumentation events on theevent console?

When you are not receiving events that you expect on your eventconsole, check the following:

¶ Ensure that the Tivoli Manager for R/3-supported monitors havebeen distributed to the R/3 application servers, R/3 databaseservers, and R/3 ITS servers.

1. From Distributed Monitoring Profile Properties, select Edit,Set User & Group ID and verify that the permissions areappropriate for the platform.

2. Run the following command to list the distributed monitors:wlseng –z endpoint_name

Where endpoint_name is the name of the Tivoli endpoint ormanaged node hosting the R/3 server.

¶ Ensure that Event Enablement Version 1.5 is installed on theevent server. Version 1.5 is required to receive heartbeat events.

¶ Ensure that the event server is operational.

¶ Ensure that the R/3 instrumentation event classes are installedand configured on the event server.

1. Run the following command to display the name of theactive rule base:wlscurrb


10.R

/3In

strum

entatio

n

2. Run the following command to list the defined R/3instrumentation event classes:wlsrbclass active_rulebase_name | grep APM

Ensure that the APM_HEARTBEAT and theAPM_THRESHOLD event classes are defined.

3. If the required R/3 instrumentation event classes are notdefined, run the Configure Event Server task.

Why isn’t the Tivoli Business Systems Manager console beingupdated with the R/3 components?

When the Tivoli Business Systems Manager console is notdiscovering or updating the R/3 components, check the following:

¶ Ensure that Tivoli Business Systems Manager event enablementand the Tivoli Business Systems Manager task server arerunning on the event server. Do one of the following:

v On Windows, ensure that the Tivoli Business SystemsManager event enablement and the Tivoli Business SystemsManager task server are running in the Services ControlPanel. Stop and start these services to verify that they arefunctioning.

v On UNIX, stop and start the Tivoli Business SystemsManager event enablement process, ihsdmai, and the TivoliBusiness Systems Manager task server process, ihscts, toverify that the processes are functioning.

Use the following command to stop both Tivoli BusinessSystems Manager event enablement and the Tivoli BusinessSystems Manager task server:$BINDIR/TDS/EventService/bin/ee_stopd.sh

Use the following command to start Tivoli Business SystemsManager event enablement:$BINDIR/TDS/EventService/bin/ee_start

Use the following command to start the Tivoli BusinessSystems Manager task server:


$BINDIR/TDS/EventService/bin/tserver start

Run the following command to ensure that the ihsdmai andthe ihscts processes are running:ps –ef|grep ihs

¶ Ensure that all required Tivoli Business Systems Managerservices are running on the Tivoli Business Systems Managermanagement server.

¶ Ensure that Tivoli Business Systems Manager event enablementis configured and connected on the event server:

1. From a Korn shell window on the Tivoli Business SystemsManager database server, run the following command:GemEEConfig

2. Verify that the event server is listed and connected. If theevent server is not listed as an Event Enabler, run thefollowing command from a Korn shell window:GemEEConfig –a event_server_hostname –e 1

3. Recycle the Tivoli Business Systems Manager Agent Listenerservice.

4. Ensure that GEM_APMHBMsgs events are being receivedfrom Event Enablement. On the Microsoft SQL queryanalyzer, run the following query:Select time, * from GEM_APMHBMsgs where eehost like \'%event_server_hostname%' order b time desc

5. Ensure that GEM_APMTHRMsgs events are being receivedfrom Event Enablement. On the Microsoft SQL queryanalyzer, run the following query:Select time, * from GEM_APMTHRMsgs where eehost like \'%event_server_hostname%' order b time desc

6. Turn on Event Enablement tracing to trace the events sent toTivoli Business Systems Manager. To do this, enter thefollowing command from the$BINDIR/TDS/EventServer/bin directory on the eventserver:tserver ee_utility –t


10.R

/3In

strum

entatio

n

The Event Enablement log file is located in theihseemsg.log file in the $BINDIR/TDS/EventService/logdirectory.

Why don’t the R/3 Instrumentation tasks run?

When R/3 instrumentation tasks do not run from the Tivoli BusinessSystems Manager console, ensure that the R/3 instrumentation tasksrun from the Tivoli desktop. Follow these steps from the Tivolidesktop:

1. If you are running the event server on an HP-UX machine, thetask server must run on a non-HPUX managed node, and youmust associate the task server with the event server. To do this,enter the following command on the machine running the taskserver:TGMTaskConfig –a event_server_hostname –r \task_server_hostname

2. Log on to the Tivoli desktop using an ID that has Tivoli superauthority. (R/3 instrumentation tasks require super authority bydefault.)

3. Open the Applications_region_name policy region.

4. Open the PR_SAPR3_Default_region_name policy region.

5. Open the Component_region_name task library, whereregion_name is the host name of the event server andComponent is one of the following:

¶ TL_SAPR3_2.2.0_Default_R3System_2.2.0

¶ TL_SAPR3_2.2.0_Default_R3Application_2.2.0

¶ TL_SAPR3_2.2.0_Default_R3Database_2.2.0

¶ TL_SAPR3_2.2.0_Default_R3ITSServer_2.2.0

6. For this example, open theTL_SAPR3_2.2.0_Default_R3Application_2.2.0_region_nametask library.

7. Double-click the Query_State task icon.


8. Select an R/3 application server to run this task on.

9. Click Execute & Dismiss.

10. Ensure that Tivoli Business Systems Manager operational tasksare running on the Tivoli Business Systems Managermanagement server. On the Microsoft SQL query analyzer onthe Tivoli Business Systems Manager database server, run thefollowing query:Select start_time, * from GEM_OpTaskMsgs order by \start_time desc

Why don’t the R/3 instrumentation tasks run from the TivoliBusiness Systems Manager console even though the tasks runfrom the Tivoli desktop?

When the R/3 instrumentation tasks do not run from the TivoliBusiness Systems Manager console even though the tasks run fromthe Tivoli desktop, check the following:

1. Ensure that task server processes are running on the event server.Do one of the following:

¶ On Windows, ensure that the Tivoli Business SystemsManager task server is running in the Services Control Panel.Stop and restart this service to verify that it is functioning.

¶ On UNIX, stop and start the Tivoli Business SystemsManager task server process, ihscts, to verify that the processis functioning.

Use the following command to stop the Tivoli BusinessSystems Manager task server:$BINDIR/TDS/EventService/bin/stopd.sh

Use the following command to start the Tivoli BusinessSystems Manager task server:$BINDIR/TDS/EventService/bin/tserver start

Run the following command to ensure that the ihscts processis running:ps –ef|grep ihs


10.R

/3In

strum

entatio

n

2. Ensure that the task server has been started with the correct userID as follows:

¶ On Windows, from the Services Control Panel, view theStartup settings for Tivoli Business Systems Manager eventenablement and the Tivoli Business Systems Manager taskserver. The Log On As setting must not be System Account.The Log On As setting must be This Account, where ThisAccount has Tivoli super authority.

¶ On UNIX, the ishcts and the ihsdmai processes must bestarted by root, and root must have Tivoli super authority.


Command Line InterfaceCommands

Tivoli Manager for R/3 uses the wr3mib and wr3rfc commands tosupport its internal processing. These commands can be run directlyfrom a command line to support diagnostic processing as describedin “Troubleshooting” on page 267. This appendix describes the TivoliManager for 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.

Co

mm

and

Lin

eIn

terfaceC

om

man

ds

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 systemNumber argumentsare optional.

SysMan and RFC CommandsThe following table lists the Tivoli Manager for R/3 commands andtheir purposes:

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 the wr3mib_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 standard output.

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

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

Co

mm

and

Lin

eIn

terfaceC

om

man

ds

–s Prints the SysMan system table.

–d Writes debug information to standard error.

–n systemNumberSpecifies the R/3 instance number. Only one systemNumberis 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, or 4 for spool).

–t iterations polling_delayPrints SysMan trap information, where iterations specifiesthe number of times to query the SysMan and polling_delayspecifies the amount of time between iterations. If you donot enter a value for iterations, the default is infinite. Youmust specify a value for iterations if you want to specify avalue for polling_delay. The default for polling_delay is 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]...

DescriptionTivoli Manager for R/3 includes a program that enables you to writesimple ASCII control files to interface with R/3 RFC, rather thanhaving to write C programs to accomplish this task. This capabilitygreatly simplifies this task and reduces the time that is required toexecute SAP modules from outside the SAP system.

The wr3rfc command reads two ASCII files: a configuration file andan rfc_interface file.

It is recommended that the configuration file contain only commandline arguments and the rfc_interface file contain only stanzalabels and keywords.

The configuration file and rfc_interface file can specify any ofthe command line arguments for the wr3rfc command except thefollowing arguments:

¶ -D

¶ -C

¶ rfc_interface file

¶ [arg]

The wr3rfc command processes input in the following order:

1. configuration file

2. rfc_interface file

3. Command line

Duplicate values are overridden by the last instance that isencountered.


A.

Co

mm

and

Lin

eIn

terfaceC

om

man

ds

The wr3rfc command uses information from the rfc_interface fileto populate the appropriate data structures for the RFC API calls.

Notes:

1. A sample configuration file, wr3rfc_cfg.txt, is provided in oneof the following directories:

¶ Managed node:$BINDIR/../generic_unix/TME/SAP/2.2C/rfc

¶ 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 and DESTINATION=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 50.

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.


CLIParameter

NameConfiguration File Parameter

Name Description

–l LANGUAGE= Specifies the single-character languageidentifier. E is English.

–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 named dev_rfc. Thefile is in the working directory of thewr3rfc program.

–h HOSTNAME= The target host. Enter a target host namesuch as myhost.

–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 is sapgwNN, 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.


A.

Co

mm

and

Lin

eIn

terfaceC

om

man

ds

Stanzas in the rfc_interface file include:

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 the wr3rfc 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 the RfcFilecommand file on system TV1 on SAP system number 00 on hosttron:wr3rfc -h tron -d TV1 -s 00 RfcFile

This example uses the configuration file (./.wr3rfc_cfg):


A.

Co

mm

and

Lin

eIn

terfaceC

om

man

ds

COMMAND OPTIONS:CLIENT = 000USER = SAP*PASSWORD = 06071992LANGUAGE = EMODE = 3TRACE = NO# These are for CPIC only#GATEWAYHOST = gatehost#GATEWAYSERVICE = sapgw00

This example uses the rfc_interface file: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.

Co

mm

and

Lin

eIn

terfaceC

om

man

ds


Event Classes and Rules

This appendix contains information about the Tivoli EnterpriseConsole event classes delivered with Tivoli Manager for R/3, newslot values for these events, and background information on R/3alerts. It also contains information about the rules that TivoliManager for R/3 provides.

Event ClassesTivoli Manager for R/3 provides a set of Tivoli Enterprise Consoleevent classes. These event classes are categorized according to theirorigin and usage. The event classes that are provided are:

¶ R/3 Alert Event Classes

These event classes arise from alerts placed onto the SysManinterface by R/3 releases up to and including 4.0B. The AlertEvent Adapter generates the events for these event classes.

¶ 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 CCMS Event Classes

These event classes arise from R/3 alerts for R/3 releases 4.5Band later. The CCMS Event Adapter generates the events forthese event classes.

¶ R/3 Syslog Event Classes

B


B.

Even

tC

lassesan

dR

ules

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

These event classes are associated with the Tivoli Manager forR/3 monitors.

¶ Special Event Classes

These event classes support internal Tivoli Manager for R/3processing.

R/3 Alert Event ClassesThese event classes correspond to alerts placed on the SysManinterface by R/3 releases up to and including 4.0B. R/3 identifies itsalerts by an R/3 alert class. The Alert Event Adapter reads R/3 alertsand converts them to Tivoli Enterprise Console events of theappropriate event classes. Additional information on R/3 alerts isprovided in “CCMS-Generated Alerts” on page 204.

The R/3 Alert Event Classes, the R/3 Alert Class, and a descriptionof the R/3 alert are described in the following table:

Alert Event Classes

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.


Alert Event Classes


Class Description

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.

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.


B.

Even

tC

lassesan

dR

ules

Alert Event Classes


Class Description

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.











Alert Event Classes


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 event console as a result of the Tivoli Manager forR/3 processing 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):

Operational Event Classes

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.


B.

Even

tC

lassesan

dR

ules



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.

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.


B.

Even

tC

lassesan

dR

ules



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.

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 CCMS Event ClassesR/3 CCMS event classes correspond to alerts for R/3 releases 4.5Band later. The CCMS Event Adapter reads R/3 alerts and convertsthem to Tivoli Enterprise Console events of the appropriate eventclasses.

SAP_CCMS_ALERT is a superclass definition for all CCMS eventclasses. CCMS event classes have the following format:SAP_CCMS_MTE_class_name, where MTE_class_name is the classname of the monitoring tree element. CCMS event classes areprovided for all attributes belonging to the Entire System monitor inthe SAP CCMS Monitor Templates monitoring set (all SAP-providedmonitors) whether or not the events are sent to the event console.For more information, see “Using the CCMS Event Adapter” onpage 89.

The CCMS Event Adapter sends a SAP_CCMS_Default_Alert eventwhen reporting an alert for a monitor for which an event class is notdefined.

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, where MsgID 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 TivoliEnterprise Console. For more information, see “Using the SyslogEvent Adapter” on page 94.

The following table describes the syslog event classes:

Syslog Event Classes

Event Class Syslog Message

SAP_SYSLOG_A05 No memory available.

SAP_SYSLOG_A07 Timeout.

SAP_SYSLOG_A08 Main memory destroyed.


B.

Even

tC

lassesan

dR

ules



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

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.


B.

Even

tC

lassesan

dR

ules



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.

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, where xx is the two-digit status code. These eventclasses should be leaf classes of the SAP_IDOC event class.


B.

Even

tC

lassesan

dR

ules

IDOC Event Classes


SAP_IDOC_STATISTICS This event is generated when the number ofIDOC events to be sent to Tivoli EnterpriseConsole reaches the 500 limit, 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 Tivoli Manager for R/3monitoring collections has an associated event class. These eventclasses are used when Tivoli Enterprise Console events are generatedautomatically from received Distributed Monitoring monitors. Theseevent classes and their associated monitoring sources are listed in thefollowing table:

Distributed Monitoring Event Classes

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


Distributed Monitoring Event Classes

Event Class Monitoring Source

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

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:

Status Event Classes


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.


B.

Even

tC

lassesan

dR

ules

R/3 Instrumentation Event ClassesThe R/3 instrumentation event classes are described in the followingtable:

R/3 Instrumentation Event Classes


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 Business Systems Manager Event ClassesThe Tivoli Business Systems Manager event classes are described inthe following table:

Tivoli Business Systems Manager Event Classes


APM_HEARTBEAT This event is generated when an R/3 objectis created.

APM_THRESHOLD This event is generated when a TivoliManager for R/3 monitor exceeds thethreshold.

Error Event ClassesThe error event classes support internal Tivoli Manager for R/3processing. These event classes and their descriptions are listed inthe following table:

Error Event Classes


AMS_WR3MIB_PROCESS_ALERT This event is generated whenever the alertcontrol or alert reader routines encounter anerror.

AMS_WR3CCMS_PROCESS_ALERT This event is generated whenever the CCMSalert control routines encounter an error.


Error Event Classes


R3MGR_RFC_ERROR_IDOC This event results from a communicationerror between the IDOC Event Adapter andthe R/3 system.

SAP_CCMS_RFC_ERROR This event results from a communicationerror between the CCMS 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 Tivoli Manager for R/3 event classes listed under R/3 AlertEvent Classes, 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 Tivoli Enterprise Consolerules. The following table describes the event slots:

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

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.


B.

Even

tC

lassesan

dR

ules

Alert Event Slots

Slot Description

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.

CCMS Event SlotsThe Tivoli Manager for R/3 event classes described in “R/3 CCMSEvent Classes” on page 191 contain a set of event slots that containinformation pertinent to the R/3 server being monitored. These slotvalues are available for use in Tivoli Enterprise Console rules. Thefollowing table describes these event slots:

CCMS Event Slots

Slot Description

alert_value The alert value.

alert_severity The severity of the alert (red, yellow, green).

alert_status The status of the alert (open, closed)

alert_objectname The alert object name, which corresponds to the MTEobject name.

alert_fieldname The alert field name, which corresponds to the MTEattribute.

aid_alsysid The alert system identifier (SID).

aid_alertdate The date on which the alert occurred in local time.


CCMS Event Slots

Slot Description

aid_alertgmtdate The date on which the alert occurred in Greenwich meantime.

aid_alerttime The time at which the alert occurred in local time.

aid_alertgmttime The time at which the alert occurred in Greenwich meantime.

aid_alindex The alert index.

aid_aluniqnum The alert unique identifier.

aid_msegname The alert monitoring segment name.

alert_message A text string that provides more description informationfor the alert.

conf_filename The file name of the event adapter configuration file.

r3alert_host The originating location, which can be the name of theR/3 application server or the machine name.

tid_extindex The monitoring tree extended index.

tid_mtclass The monitoring tree class.

tid_mtindex The monitoring tree index.

tid_mtmcname The monitoring tree monitoring class name.

tid_mtnumrange The monitoring tree number range.

tid_mtuid The monitoring tree unique identifier.

tid_sysid The monitoring tree system identifier (SID).

Syslog Event SlotsThe Tivoli Manager for R/3 event classes described in “R/3 SyslogEvent Classes” on page 191 contain a set of event slots that provideinformation about the syslog event. The following table describesthese event slots:

Syslog Event Slots

Slot Description

r3syslogMsgNumber The three-character message ID from the syslog.

r3syslogDate The date that the message was written in the syslog.


B.

Even

tC

lassesan

dR

ules

Syslog Event Slots

Slot Description

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 Tivoli Manager for R/3 event classes described in “R/3 IDOCEvent Classes” on page 195 contain a set of event slots that provideinformation about the IDOC event. The following table describes theevent slots for the SAP_IDOC event class:

IDOC Event Slots for SAP_IDOC Events

Slot Description

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 Tivoli Enterprise Consolelimits this event slot to a maximum of 255 characters, theR/3 information can be truncated in some circumstances.

r3idocNum The 16-digit R/3 IDOC number.


IDOC Event Slots for SAP_IDOC Events

Slot Description

r3idocStatus The two-digit R/3 IDOC status code.

r3idocStacod The eight-character R/3 IDOC status code.

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:

IDOC Event Slots for SAP_IDOC_XMIT Events

Slot Description

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.


B.

Even

tC

lassesan

dR

ules

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:

Cancelled Job Event Slots

Slot Description

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.

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 Tivoli Manager for R/3 does forward key operatingsystem events to the 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 not


B.

Even

tC

lassesan

dR

ules

enough 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 Tivoli Manager for R/3 EventsThe event console includes a rules engine that processes eventsaccording to a set of rules that are provided by Tivoli products oradded by users. Tivoli Manager for R/3 supplies a default rule base,which is a set of rules that provides correlation of related events andgives automated responses where possible. You can extend theserules by writing rules that are tailored for your installation. Refer tothe Tivoli Enterprise Console Rule Builder’s Guide.

Tivoli Manager for R/3 rules provide these functions:


¶ Duplicate event checking

¶ Automatic closing of harmless events

¶ Automatic drill-down (Alert Event Adapter only)

¶ Bidirectional communication

¶ Event correlation

¶ Multi-region support

¶ Integration with Tivoli Business Systems Manager


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.

Tivoli Manager for R/3 provides a rule that automatically closesduplicate events when a new event is received, which is effective forall of the R/3 alert classes. A duplicate event is defined as an eventof the same event class in which designated slot values are identical.

Automatic Closing of Harmless EventsTypically, event console users do not want the event consolepopulated with harmless events. However, it is valuable to display aharmless event for a period of time when the event is generated as aresult of a self-correcting condition. To permit this, a rule isprovided that automatically closes harmless R/3 events after 60seconds.

Automatic Drill-Down (Alert Event Adapter Only)When the event server rule base receives certain R/3 SysMan events,it automatically runs an R/3 function module through the RFCinterface. The R/3 function module obtains additional and morespecific internal CCMS information about the alert. For example,


B.

Even

tC

lassesan

dR

ules

when the event server receives the R/3 SysMan buffer alert, itautomatically runs a special function module supplied with TivoliManager for R/3 to identify the specific buffer that is having aproblem.

Bidirectional CommunicationBy converting R/3 alerts into R/3 internal alerts, the event serverrule base can use the RFC interface to control R/3 alerts from theevent console.

For alerts sent by the Alert Event Adapter, closing or acknowledgingan R/3 internal alert from the event console automatically causes theR/3 alert to be reset or acknowledged in the appropriate R/3application server. Acknowledging or resetting an alert in R/3 causesa harmless event to be sent to the event server. This harmless eventcauses the associated non-harmless event to be closed on the eventconsole.

For alerts sent by the CCMS Event Adapter, closing oracknowledging the event on the event console automaticallycompletes the R/3 alert in CCMS. Completing an alert in CCMScauses the CCMS Event Adapter to send a harmless event to theevent server. This harmless event causes the associated non-harmlessevent to be closed on the event console.

Event CorrelationThe event server rule base correlates certain types of events andtakes the appropriate action. For example, the event server rule baseautomatically resets R/3 buffer alerts for 35 minutes after receivingan 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 and


can discard them as not relevant. Event correlation helps to removethese events and alleviate such flooding situations.

Multi-Region SupportOptionally, you can use the event server rule base to forward eventsfrom multiple regions. Then, a single administrator can monitor alarge number of R/3 systems in different regions.

Integration with Tivoli Business Systems ManagerOptionally, you can manage R/3 resources from the Tivoli BusinessSystems Manager console (see “Tivoli Business Systems ManagerInstrumentation for R/3” on page 151). Tivoli Manager for R/3provides rules that forward Tivoli Manager for R/3 monitor events tothe Tivoli Business Systems Manager server and synchronize theTivoli Business Systems Manager console with the Tivoli Managerfor 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(see “Extending Database Server Status Reporting” on page 78).Tivoli Manager for R/3 provides rules that set the status of thedatabase server from the Tivoli Manager for DB2 or Tivoli Managerfor Oracle database status event.

Event Server RulesThe sap_tecad.rls file contains the following event server rules:

Rule Name Description

ack_sap_alert Acknowledges R/3 alerts when thecorresponding events from the Alert EventAdapter are acknowledged.

ack_sap_moni_alert Completes R/3 alerts when the correspondingevents from the CCMS Event Adapter areacknowledged.

close_sap_alert Closes R/3 alerts when the corresponding eventsfrom the Alert Event adapter are closed.


B.

Even

tC

lassesan

dR

ules


close_sap_moni_alert Completes R/3 alerts when the correspondingevents from the CCMS Event Adapter areclosed.

convert_mib_to_internal_alert Performs drill-down event processing. When theevent server receives certain R/3 SysMan events,the R/3 function module obtains more detailedevent information. The original event is closed,and only the drill-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 anIDOC event is received.

drop_r3mgr_rfc_error_syslog_event Removes the syslog RFC error event when asyslog event is received.

drop_sap_moni_rfc_error_event Removes duplicate CCMS Event Adapter RFCerror events and keeps the original RFC errorevent.

dup_all_sap_idoc_event Removes duplicate IDOC events.

dup_r3mgr_rfc_error_event Removes duplicate IDOC RFC error events andkeeps the original RFC error event.

dup_sap_event Removes duplicate Alert Event Adapter events.

forward_sap_events Forwards events to an alternate event server.

harmless_set_timer Sets a timer on each harmless event. The timeris set to 60 seconds. A timer rule will close theevent when the 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.

sap_ccms_close_with_harmless Closes non-harmless CCMS events when aharmless event is received.

sap_ccms_drop_duplicate Removes duplicate non-harmless CCMS EventAdapter events.

sap_remap_moni_msg_slot Remaps the msg event slot for CCMS events toinclude the alert object and the alert field names.



sapsysdown_clone_appstatus_event Creates an event of classAPSRVR_STATUS_MONITOR when anapplication server’s status is down.

sapsysup_clone_appstatus_event Creates an event of classAPSRVR_STATUS_MONITOR when anapplication server’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_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_standby Removes duplicate R/3 application server standbyevents.

dup_sap_system_up Removes duplicate R/3 application server status upevents.


B.

Even

tC

lassesan

dR

ules


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.

sap_its_down Closes ITS server status up events.

sap_its_up Closes ITS server status down events.

sap_system_down Closes all outstanding open events for an applicationserver when the R/3 application server statuschanges from up to down.

sap_system_standby Closes R/3 system down events and all DistributedMonitoring events because the R/3 server is instandby state.

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 statusof the Distributed Monitoring application changesfrom up to down.

sentry_daemon_or_application_up Closes all outstanding open events when the statusof the Distributed Monitoring application changesfrom down to up.

sentry_host_down Closes all outstanding open events when the statusof the Distributed Monitoring host machine changesfrom up to down.

sentry_host_up Closes all outstanding open events when the statusof the 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 Business Systems Manager InstrumentationDistributed Monitoring Rules

The sap_gemevents.rls file contains the following rules forprocessing events that are sent from the Tivoli Manager for R/3monitors:


sap_gemevents_rule1 Forwards Tivoli Manager for R/3 monitor events to theTivoli Business Systems Manager server.

sap_gemevents_rule2 Forwards R/3 application server status events to the TivoliBusiness Systems Manager server.

sap_gemevents_rule3 Changes the SAP_APM_HEARTBEAT event to theAPM_HEARTBEAT event and forwards the event to theTivoli Business Systems Manager server.


B.

Even

tC

lassesan

dR

ules


sap_gemevents_rule4 Changes the SAP_APM_THRESHOLD event to theAPM_THRESHOLD event and forwards the event to theTivoli Business Systems Manager server.


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

ote

and

Cen

tralM

on

itorin

gS

ou

rces

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 Free FREE_MEMORY st06 / Physical mem free kb

Pages in per second PAGE_INS_SEC st06 / Pages in/sec

Pages out per second PAGE_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 space MAX_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

ote

and

Cen

tralM

on

itorin

gS

ou

rces


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 Space PAGE_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

ote

and

Cen

tralM

on

itorin

gS

ou

rces


******* ******* 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 Entries FREE_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 Percent PERCENT_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

ote

and

Cen

tralM

on

itorin

gS

ou

rces


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 Percent PERCENT_USED_MEMORY Not directly available.USED_MEMORY divided byAVAILABLE_MEMORY

Performance SourcePerformance sources include the following attributes and theirkeyword equivalents:


Frequency per minute FREQUENCY 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 memoryminus Extended CurrentlyUsed.

Extended PercentFree

EXTENDED_PERCENT_FREE Not directly available.Extended Free Spacedivided by total size ofextended memory.

Extended MaxPercent Used

EXTENDED_MAX_PERCENT_USED Not directly available.Extended Max Used dividedby 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

ote

and

Cen

tralM

on

itorin

gS

ou

rces


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 as Max 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 as Max 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 second PAGE_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

ote

and

Cen

tralM

on

itorin

gS

ou

rces


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 count UNUSED_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 frames TOTAL_AVAILABLE_FRAMES os07 / No. of available frames


IDOC Status Codes

This appendix describes the IDOC status codes and thecorresponding event severities. For more detailed information aboutIDOC status codes, refer to the appropriate SAP documentation.

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 Tivoli Enterprise Console 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

09 Yes Error Interchange handling

D


D.

IDO

CS

tatus

Co

des

Outbound IDOCs


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

39 No Harmless Receive confirmed


Outbound IDOCs


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 Tivoli Enterprise Console 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

tatus

Co

des


Function Module Authorization

This appendix contains a list of the function modules delivered withTivoli Manager for R/3. For each function module, the R/3authorizations required for that module are given. The authorizationslist the authorization object referenced followed by the field valuesrequired for the function module. The references to the S_RFCauthorization object are only necessary to have the RFC securitycheck 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.

Fu

nctio

nM

od

ule

Au

tho

rization


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.

Fu

nctio

nM

od

ule

Au

tho

rization


Messages

This appendix describes Tivoli 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 Tivoliserver.

Explanation: The Configure Event Server task was run on a Tivoli server thatdoes not have Distributed Monitoring installed. The Configure Event Server taskrequires Distributed Monitoring.

User Response: Install Distributed Monitoring on the Tivoli 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 event server.

Explanation: The Configure Event Server task was distributed to a host that is notthe event server.

User Response: Distribute the task to the 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 the sidadm 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 the sidadm 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 the sidadm 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 the sidadm 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 Windowsmachine. 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” 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 the wruntask 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 requires a user-supplied stopexit 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” 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 Windowsmachine. 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” 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 object S_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 theobject S_BTCH_ADM and the Batch Administrator ID field needs to beset to Y.

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 CCMS Event Adapter, the Syslog Event Adapter, orthe IDOC Event Adapter, you must first configure the remote function call (RFC)for the corresponding R/3 system.

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 Heartbeat task was not run against a valid object. Thistask should be run against R3AppServer, R3DBServer, R3ITSServer, and R3Systemobjects only.

User Response: Run the task against a valid object.


ABH0563E &1 Could not start the schedule service.

Explanation: The Windows 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 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 Tivoli management region name.

Explanation: The Tivoli management region name was not provided.

User Response: Start the program again specifying the Tivoli management regionname.

ABH0567E &1 Error setting the at command.

Explanation: The Configure Autodiscovery task for NT failed because it could notschedule the job using the at 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 the sidadm 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. Tivoli Manager for R/3 does not start or stopan OS/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 event server, a rules trace of the current rule set, if available, andcontact 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, CCMS Event Adapter, Syslog Event Adapter, or IDOC Event Adapter.Possible return codes and their meanings are:

27 No unique name. The Alert Event Adapter, CCMS Event Adapter, SyslogEvent Adapter, or IDOC Event Adapter is not named r3mibIID,r3moniIID, r3slogIID, or r3idocIID, respectively. If you are using TivoliManager for R/3 event adapter tasks, contact Tivoli Customer Support.

30 Windows only. The Alert Event Adapter, the CCMS Event Adapter, theSyslog Event Adapter, or the IDOC Event Adapter has been invoked with


a value other than –install, –start, –stop, or –remove. If you are usingTivoli Manager for R/3 event adapter tasks, contact Tivoli CustomerSupport.

31 Windows only. The Alert Event Adapter, the CCMS Event Adapter, theSyslog Event Adapter, or the IDOC Event Adapter has been invokedwithout a value. The event adapter should be invoked with one of thefollowing values: –install, –start, –stop, or –remove. If you are usingTivoli Manager for R/3 event adapter tasks, contact Tivoli CustomerSupport.

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

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 Tivoli Enterprise Console, and call Tivoli CustomerSupport.

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.


F.M

essages

ABH0576E &1 File &2 does not exist.

Explanation: A required file was not found on the SAPGUI installation server.

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 the NetSetup.exe executable 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.exe executable is located.

ABH0582I 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: Tivoli 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. Tivoli Manager for R/3 could not add the database status monitor tothe monitoring profile.



F.M

essages

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.


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,CCMS Event Adapter, Syslog Event Adapter, or IDOC Event Adapter), and run theStart Adapter task again.

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. Tivoli Manager for R/3 will attempt to start the application servers.However, if the database server is not running, the attempt to start the applicationservers will fail.


User Response: Either create the R3DBServer object, or start the database servermanually before running the start R/3 system task.

ABH0601I Default variables for package &1

Explanation: The SAPGUI file package specified by &1 contains the defaultvariables that are listed after this message.


ABH0602I Components in package &1.

Explanation: The SAPGUI file package specified by &1 contains the componentsthat are listed after this message.


ABH2501E Conflicting arguments specified

Explanation: The command syntax used for the wr3mib command is not valid.

User Response: Run the wr3mib command again, ensuring that the commandsyntax is correct. For information about the command syntax for the wr3mibcommand, see “Command Line Interface Commands” on page 171.

ABH2502E No valid arguments specified

Explanation: The command syntax used for the wr3mib command is not valid.

User Response: Run the wr3mib command again, ensuring that the commandsyntax is correct. For information about the command syntax for the wr3mibcommand, see “Command Line Interface Commands” on page 171.

ABH2503E r3system Exists failed for SysNum &1

Explanation: The R/3 application server associated with the instance numberspecified by &1 was not found. The application server might not be running, or thevalue specified for the –n option is not valid.

User Response: Ensure that R/3 application server is running. Then run thewr3mib command again, specifying the correct instance number for the –n option.

ABH2504E r3configInfo failed for sysNum &1



F.M

essages


ABH2505E r3configServiceInfo failed for sysNum &1



ABH2506E r3perfInfo failed for SysNum &1



ABH2507E r3alertInfo failed for SysNum &1



ABH2508E r3alertTraps failed for SysNum &1



ABH2509E Unexpected performance attribute

Explanation: The value specified for the –P option is not valid.

User Response: Run the wr3mib command again, specifying F, R, or W as thevalue for the –P option. For more information about the wr3mib command, see“Command Line Interface Commands” on page 171.


ABH2510E Uexpected service type: &1

Explanation: Either the service type specified for the –T option is not valid or nowork processes of the type specified are running on the R/3 application server.

User Response: Run the wr3mib command again, specifying 1, 2, 3, or 4 as thevalue for the –T option. For more information about the wr3mib command, see“Command Line Interface Commands” on page 171.

ABH2511E System number is out of range 0 – &1

Explanation: The value specified for the –n option is not valid.

User Response: Run the wr3mib command again, specifying 00 through 96 forthe value of the –n option.

ABH2512E Error in Syntax: MIB information: wr3mib –afcpst –n sysNum

Explanation: The syntax used for the wr3mib command is not valid.

User Response: Run the wr3mib command again using the correct syntax. Forinformation about the syntax of the wr3mib command, see “Command LineInterface Commands” on page 171.

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


F.M

essages

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

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.

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 using an RFC. Itcan fail if RfcOpen is called with the wrong password.

User Response: Verify the command line options, such as password and username.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 171.

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.


F.M

essages

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 or NO.

User Response: Specify a valid trace value.

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 or 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 TYPC, TYPNUM, TYPX, and TYPP fields within the EXPORTPARAMETER 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 TYPC, TYPNUM, TYPX, and TYPP fields within the IMPORTPARAMETER 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.


F.M

essages


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 directory

in 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 the wr3rfc command is incorrect.

User Response: For the command line syntax, see “Command Line InterfaceCommands” on page 171.

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 endpoint name specified in the dialog is not valid.

User Response: Specify a valid 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.


F.M

essages

User Response: Specify either a managed node name or an endpoint name in thedialog.

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.

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 endpoint name specified in dialog is not valid.

User Response: Run the task again and specify a valid 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 endpoint name was not specified in thedialog.

User Response: Run the task again and specify either the managed node name orthe 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.



F.M

essages

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 an R/3 system with the name &1.

Explanation: Tivoli 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.


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: Endpoint &1 not found.

Explanation: The endpoint name specified in the dialog is not valid.

User Response: Run the task again and specify a valid 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 endpoint name was not specified in the dialog.

User Response: Run the task again and specify a managed node name or aendpoint 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.


F.M

essages

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.

ABH0598W &1 Running the Alert Event Adapter on an R/3 system other than 31I or 40B isnot recommended. (This system is &2.) The CCMS Event Adapter isrecommended instead.

Explanation: The Alert Event Adapter has been configured or started on an R/3system running the R/3 release specified by &2.

User Response: For R/3 releases 4.5B and later, use the CCMS Event Adapter.

ABH0598W &1 Running the CCMS Event Adapter on an R/3 system other than 45B, 46B,46C, or 46D is not recommended and may not be possible. (This system is &2.)The Alert Event Adapter is recommended instead.

Explanation: The CCMS Event Adapter has been configured or started on an R/3system running the R/3 release specified by &2.

User Response: For R/3 releases up to and including 4.0B, use the Alert EventAdapter.

ABH6600E R3Mgr_uninstall22.pl [–g] [–yes]

Explanation: The syntax used for the R3Mgr_uninstall22.pl command was notvalid. Use the –g option to uninstall Tivoli Business Systems ManagerInstrumentation only. Use the –yes option to continue the uninstall process withoutprompts.

User Response: Run the R3Mgr_uninstall22.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% directoryon Windows.

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.


ABH6606I &1 This will uninstall the Tivoli Manager for R/3 Version 2.2.0. You shouldback up your Tivoli database before uninstalling Tivoli Manager for R/3. Doyou want to continue? Enter y to continue or n to quit.

Explanation: This is a reminder to back up the Tivoli database before running theR3Mgr_uninstall22.pl command.


¶ If you already backed up the Tivoli database, enter y to continue.

¶ If you did not back up the Tivoli database, do the following:

1. Enter n 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 –yes parameter is specified with theR3Mgr_uninstall22.pl command. The uninstall process continues withoutprompting for a confirmation.



F.M

essages

ABH6647I Uninstalling R/3 Instrumentation only...

Explanation: This message is issued when the –g parameter is specified with theR3Mgr_uninstall22.pl command. The R3Mgr_uninstall22.pl –g commanduninstalls Tivoli Business Systems Manager Instrumentation for R/3 only.



Troubleshooting

This chapter describes diagnostic information and tools availablewith Tivoli Manager for R/3. This chapter includes the followingtopics:

¶ “Setting Up the Environment”

¶ “Log Files” on page 268

¶ “Alert Event Adapter Events” on page 280

¶ “Configuring Monitor Logging Mode” on page 285

¶ “SAPGUI File Package Distribution” on page 286

¶ “Display OS Collect Information Task” on page 286

¶ “Icon State” on page 286

¶ “File System Layout” on page 287

Setting Up the EnvironmentTo use the diagnostic tools (wr3mib and wr3rfc), you should set upthe environment to ensure that shared libraries are available. Settingup the environment also makes it easier to locate Tivoli Manager forR/3 log 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:

G


G.

Trou

blesh

oo

ting

. /etc/Tivoli/setup_env.sh

v For C shell:source /etc/Tivoli/setup_env.csh

¶ On a UNIX endpoint, enter one of the following commands:

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 managed node, enter:%SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd

¶ On a Windows endpoint, enter:%SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd

Note: For endpoints, replace x with 1 for the first endpointinstalled on the machine, replace x with 2 for the secondendpoint installed on the machine, and so 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 Tivoli Manager for R/3 log files.

Task Log FilesThe following table describes the log file that is associated with eachTivoli Manager for R/3 task. The task log files are located in one ofthe following directories:

¶ UNIX: /tmp

¶ Windows managed node: %DBDIR%\tmp

¶ Windows endpoint: %LCF_DATDIR%

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

CCMS Alert Control(internal task)

SID_DBhostname_sap_alert_control_moniIID.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_MIB_IID.log

¶ For the CCMS Event Adapter:

SID_DBhostname_sap_config_adapter_CCMS_IID.log

¶ For the IDOC Event Adapter:

SID_DBhostname_sap_config_adapter_IDOC_IID .log

¶ For the Syslog Event Adapter:

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


G.

Trou

blesh

oo

ting

Task Log File

Configure SAPGUIPackage

sap_sapgui_inst.log

Configure UNIX ClientInstall

sap_unix_ci_config.log

Configure Windows95/98 Client Install

sap_w95_ci_config.log

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, where PID 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_info_MIB_IID.log


SID_DBhostname_sap_adapter_info_CCMS_IID.log


SID_DBhostname_sap_adapter_info_IDOC_IID.log


SID_DBhostname_sap_adapter_info_SLOG_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


Task Log File

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

Remove Autodiscoveryfor UNIX

sap_uncrontab.log

Replace Event Adapter(internal task)

SID_DBhostname_sap_replace_adapter_IID.log

Send 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_r3ccms_IID.log


SID_DBhostname_sap_start_r3idoc_IID.log


SID_DBhostname_sap_start_r3slog_IID.log


G.

Trou

blesh

oo

ting

Task Log File

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

Stop Event Adapter ¶ For the Alert Event Adapter:

SID_DBhostname_sap_stop_r3mib_IID.log


SID_DBhostname_sap_stop_r3ccms_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 eachTivoli Manager for R/3 monitor. The monitor log files are located inone of the 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


G.

Trou

blesh

oo

ting


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

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 Free SID_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


G.

Trou

blesh

oo

ting


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

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


G.

Trou

blesh

oo

ting


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

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 Performance SID_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 eachTivoli Manager for R/3 event adapter. The event adapter log files arelocated in one of the following directories:

¶ UNIX: /tmp

¶ Windows: %SYSTEMROOT%\temp, where %SYSTEMROOT% isthe drive where Windows is installed, usually C:

If the \temp directory is not found, the event adapter log filesare written in one of the following directories:

v Managed node: %BINDIR%\TME\SAP\2.2C

v Endpoint: %LCF_BINDIR%\..\TME\SAP\2.2C

Event Adapter Log File

Alert Event Adapter r3mibIID.log

IDOC Event Adapter r3idocIID.log

CCMS Event Adapter r3moniIID.log

Syslog Event Adapter r3slogIID.log

Miscellaneous Log FilesThe following table describes miscellaneous log files, such as the logfiles associated with uninstalling Tivoli Manager for R/3 and TivoliEnterprise Console scripts.

Log Type Function Log Name

R3Mgr_uninstall22.pl Tivoli Manager forR/3 uninstall

R3Mgr_uninstall22.log

sap_alert_control_cb.sh Tivoli EnterpriseConsole script

sap_alert_control_cb.log

sap_alert_control_moni_cb.sh Tivoli EnterpriseConsole script

sap_alert_control_moni_cb.log

sap_alert_reader_cb.sh Tivoli EnterpriseConsole script

sap_alert_reader_cb.log

sap_gemhbfwd.sh Tivoli EnterpriseConsole script

sap_gemhbfwd.log


G.

Trou

blesh

oo

ting

Log Type Function Log Name

sap_gemtecfwd.sh Tivoli EnterpriseConsole script

sap_gemtecfwd.log

sap_gemthfwd.sh Tivoli EnterpriseConsole script

sap_gemthfwd.log

sap_set_r3db_state.sh Tivoli EnterpriseConsole script

sap_set_r3db_state.log

sap_sysupdown_clone_event.sh Tivoli EnterpriseConsole script

sap_sysupdown_clone_event.log

Notes:

1. The R3Mgr_uninstall22.log is located in one of the following directories:

¶ UNIX: /tmp



2. Logs related to Tivoli Enterprise Console scripts are located in one of the followingdirectories on the event server:

¶ UNIX: /tmp


Alert Event Adapter EventsTivoli Manager for R/3 alert events for R/3 releases up to andincluding 4.0B originate from the Alert Event Adapter. Ther3mibIID program reads the R/3 SysMan interface for a managedR/3 application server. R/3 provides information about R/3 alertsthrough the SysMan interface. The r3mibIID program captures eachR/3 alert, converts it to a Tivoli Enterprise Console event, andforwards the event to the event server. Tivoli Enterprise Console


event processing is illustrated in the following diagram:

The Tivoli Manager for R/3 provides a set of rules that are run onthe event server. These rules will determine if the event is generic orspecific. Generic events are high-level indications of a problem.More information about the alert is available inside of the R/3system. For these events, the Tivoli 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 theevent consoles.

The drill-down process begins with the event console rules callingthe sap_alert_reader_cb.sh script. This script runs on the 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.sh script triggers the running of a task onthe remote R3AppServer. The remote task is sap_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 calledsap_alert_reader.log.


G.

Trou

blesh

oo

ting

The sap_alert_reader.sh script calls the wr3rfc program to actuallyconnect to the R/3 application server. The wr3rfc 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 event server by the sap_alert_reader.sh script. This moredetailed event is forwarded to the event consoles.

Error AlertsErrors in the sap_alert_reader_cb.sh and the sap_alert_reader.shscripts will often generate a special error event to the event server.These events are of class AMS_WR3MIB_PROCESS_ALERT. Ifone of these events occurs, check the sap_alert_reader_cb.logand sap_alert_reader.log files for additional diagnosticinformation.

Event Diagnostic ToolsThe processing flow for event generation involves many steps. Youcan debug these steps individually to facilitate problemdetermination. In particular, you can run the wr3mib and wr3rfcprograms from the command line to determine if the wr3mib 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 267.

3. Go to one of the following directories:




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

Where systemNumber is 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. The wr3mib_64 command usesthe same syntax as the wr3mib 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 52 and “Configuring Tivoli Manager forR/3 for HP-UX 11” on page 75. Then, contact Tivoli customersupport.

The r3mibIID program can have tracing enabled when running as aTivoli Enterprise Console event adapter daemon. To turn on thisdebug tracing, use the Configure Event Adapter task. See“Configuring Event Adapters” on page 86. When tracing is enabled,the r3mibIID program generates a log file. See “Log Files” onpage 268.

wr3rfc DiagnosticsYou can also run the wr3rfc program directly from the commandline. Several levels of diagnostics can be performed.

The most basic test is to ensure that the wr3rfc program iscommunicating with the R/3 application server. The followingcommand tests this connection:


G.

Trou

blesh

oo

ting

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 175. Substitute values for the userid, client, password,

language, SID, ManagedNode, and InstanceNumber parameters. Thiscommand lists the R/3 buffer names.

The wr3rfc program and the J_8C1* files that the wr3rfc programreferences are installed in different directories. To facilitatediagnostic testing, it is recommended to copy these files into acommon directory such as /tmp. The wr3rfc 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

¶ Endpoint:$LCF_BINDIR/../../generic_unix/TME/SAP/2.2C/rfc

To see additional detail, use the wr3rfc 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 Tivoli Manager for R/3 RFC functionality.

Configuring Monitor Logging ModeTivoli Manager for R/3 provides a method for turning on monitortrace for Tivoli Manager for R/3 monitors in the R3 Server Central,R3 Server Remote, R3 ITS Server, R3 Windows NT File System,and R3 UNIX File System monitoring collections. When monitortrace is enabled, each monitor running on the target R3AppServer orR3ITSServer object creates a log file. See “Log Files” on page 268.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 the wr3rfc program. If these monitors are failing, referto diagnostic techniques for wr3rfc as explained in “wr3rfcDiagnostics” on page 283.


G.

Trou

blesh

oo

ting

SAPGUI File Package DistributionTo determine the source of problems resulting from distributingclient software (SAPGUI) file packages, look in the profile.log file,where profile is the name of the file package profile. The profile.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

¶ Endpoint:

$LCF_BINDIR/../generic_unix/TME/SAP/fp/profilemgr,where profilemgr is the name of the profile manager

Display OS Collect Information TaskTo run the Display OS Collect Information task, the saposcolprogram must be running. If the saposcol program is not running,the Display OS Collect Information task fails and returns thefollowing message:EXCEPTION SHARED_MEMORY_NOT_AVAILABLE RAISEDsap_display_OSCollect_info.sh Module WR3RFC failed with return code 1 and output (null)

If you receive this message when you run the Display OS CollectInformation task, start the saposcol program and run the Display OSCollect Information task again.

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 Tivoli Manager for R/3 installation process creates the followingdirectories:

¶ Managed node:

$BINDIR/../generic_unix/TME/SAP

$BINDIR/TME/SAP

¶ Endpoint:

$LCF_BINDIR/../../generic_unix/TME/SAP

$LCF_BINDIR/../TME/SAP

The Configure Event Server task creates a rule base on the eventserver in the following default location: /usr/tec_rules/SAP.


G.

Trou

blesh

oo

ting


Index

Numerics64-bit support, HP-UX 11 75

Aadapter, event, parameters

configuring 86displaying 87

administrator authorizationManager for R/3 33

alert, R/3CCMS-generated 204event classes 184event slots 199wr3mib diagnostics 282wr3rfc diagnostics 283

alert event adapterdescription 88filtering events 107parameters


r3mibIID.conf file 88starting 137stopping 137

application proxyinstalling 11upgrading 13

application proxy patch, installing 13application server

central monitors profile 114display performance information 138monitors profile manager 114OS collect monitoring source 127remote monitors profile 114starting 137status, determining 38

application server (continued)status monitor 114, 117stopping 137

application server status monitoring source 117assigning authorization roles

Tivoli Manager for R/3 33attributes, monitoring 110authentication package for Windows,

enabling 74authorization

configuration tasks 36list maintenance task 38R3 App Server tasks 136R3 DB Server tasks 140R3 ITS Server tasks 141R3 System tasks 135RFC access 50roles, assigning

example 34Manager for R/3 33

Tivoli Manager for R/3 function module 231automatic discovery

configuring data sharing 56description 55enabling for Windows NT 74scheduling

UNIX 59Windows NT 58

stopping 60availability management

description 3event adapters

alert 88CCMS 89IDOC 99syslog 94


Ind

ex

Bbatch jobs, managing 138bidirectional communication 208buffer monitoring source 221

Ccancel batch job task 138cancel process task 139cancelled job, monitoring 125cancelled job event slots 204CCMS event adapter

description 89event classes 191events sent to event console

controlling 91filtering events 107how it works 89parameters


r3moniIID.conf file 89r3moniIID.evt file 89

CCMS event slots 200CCMS-generated alerts 204central monitors 110client software

file packageconfiguring for versions 4.5B and

later 147configuring for versions prior to

4.5B 144distributing 149

installationconfiguring for versions 4.5B and


4.5B 144distributing 149

closing harmless events 207collections, monitoring 4commands

create_uninstall_task.sh 22

commands (continued)GEMinstall_after.sh 164R3Mgr_uninstall22.pl 22syntax conventions 171wlcftap 74wr3mib 173wr3mib_64 173wr3rfc 175wsettap 74

Computing Center Management System(CCMS) 3, 204

configuration filesr3idocIID.conf 102r3mibIID.conf 88r3moniIID.conf 89r3moniIID.evt 89r3slogIID.cl 94r3slogIID.conf 94sap_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 88stop event adapter 88

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 147versions prior to 4.5B 144

event adapter 86event console 83event handling

event adapter 86event console 83event server 82overview 81tasks 82Tivoli Enterprise Console event server 82

event server 14, 82Manager for R/3

authorization roles, example 34automatic discovery, enabling for Windows

NT 74environment variable for Windows 75exit routines for Windows 72extending database server status

reporting 78for Windows 72HP-UX 11 enhancements 75SAP file access, enabling for

Windows 73tasks, overview 35Tivoli authentication package for

Windows 74monitor logging mode 285remote function call (RFC) 71SAPGUI file package

versions 4.5B and later 147versions prior to 4.5B 144

Tivoli Enterprise Console event server 14,82

Tivoli management regions 10Tivoli Manager for R/3

authorization roles, assigning 33configuration tasks, locating 35desktop after configuration 32overview of tasks 31R/3 objects, automatic discovery,

stopping 60R/3 objects, creating 53

configuring (continued)Tivoli Manager for R/3 (continued)

R/3 objects, creating by automaticdiscovery, description 55

R/3 objects, creating by automaticdiscovery for NT 58

R/3 objects, creating by automaticdiscovery for UNIX 59

R/3 objects, creating manually 60user ID for RFC access 50

copying R/3 transports 47correlation rule 213create new subscriber list task 70create RDBMS manager status monitor task 78create_uninstall_task.sh command 22creating

exit routines for Windows 72R/3 objects

automatic discovery for NT 58automatic discovery for UNIX 59description 53manually 60result 64where to create 54

subscriber lists 70customizing events sent to event console

alert, filtering 107CCMS

adding event classes 93changing monitor set and monitor to

observe 92controlling number of alerts to report 92filtering 107

IDOCfiltering 107r3idocIID.conf file, modifying 102

syslogfiltering 107r3slogIID.cl file, adding entries 96r3slogIID.cl file, modifying 96


Ind

ex

Ddaemons, monitoring

sappld 115saprouter 115

data sharing 56, 78database server

central monitors profile 114monitors profile manager 114OS collect monitoring source 128status

determining 39extending 78

database status integration rules 213dbaccess, starting 140deleting R/3 objects 68directory names, notation xxidiscovery, automatic

configuringfor data sharing 56UNIX 59Windows NT 58

description 55enabling for Windows NT 74stopping 60

display batch jobs task 138display buffer information task 138display event adapter information task 87display OS/390 DB2 information task 138display OS/390 information task 138display OS collect information task 138display OS collect information task,

troubleshooting 286display process information task 139display processes task 139display roll page information task 138displaying event adapter configuration 87distributed monitoring

event classes 196rules 211

distributingclient software 149SAPGUI software 149transports 46

drill-down processing 187duplicate event checking 207

Eendpoint

R3AppServer 29R3DBServer 29R3ITSServer 29R3System 29target

configuration tasks 36event handling tasks 82list maintenance task 38R3 App Server tasks 136R3 DB Server tasks 140R3 ITS Server tasks 141R3 System tasks 135

environment, setting up 267environment variables, notation xxierror alerts, troubleshooting 282error event classes 198event

classescategories 183CCMS 191distributed monitoring 196error 198IDOC 195operational 187R/3 alert 184R/3 instrumentation 198R/3 syslog 191status 197Tivoli Business Systems Manager 198

rulescorrelation 213database status integration 213distributed monitoring 211event server 209Tivoli Business System Manager

Instrumentation 213Tivoli Enterprise Console event

server 209slots

cancelled job 204CCMS 200IDOC 202R/3 alert 199


event (continued)slots (continued)

R/3 syslog 201Tivoli Enterprise Console processing 280troubleshooting

wr3mib diagnostics 282wr3rfc diagnostics 283

event adapteralert

configuring 86description 3, 88displaying configuration parameters 87filtering events 107r3mibIID.conf file 88starting 88, 137stopping 88

CCMSconfiguring 86description 3, 89events sent to event console 91events sent to event console,

controlling 91filtering events 107how it works 89r3moniIID.conf file 89r3moniIID.evt file 89starting 88stopping 88

IDOCdescription 4, 99displaying configuration parameters 87events sent to event console 100events sent to event console,

controlling 102filtering events 107how it works 99performance considerations 104r3idocIID.conf file 102starting 88stopping 88

monitoring architecturedisplaying configuration parameters 87

syslogconfiguring 86description 4, 94displaying configuration parameters 87

event adapter (continued)syslog (continued)

events sent to event console,controlling 96

events sent to TEC by default 95files 94filtering events 107r3slogIID.cl file 94r3slogIID.cl file, adding entries 96r3slogIID.cl file, modifying 96r3slogIID.conf file 94starting 88, 137stopping 88

event console, configuring 83event correlation 208event drill-down processing 207event enablement, Tivoli Business Systems

Manager 153event handling

configuringevent adapter 86event console 83event server 82overview 81tasks 82Tivoli Enterprise Console event server 82

event handling, Tivoli Business SystemsManager 153

event serverconfiguring 14, 82rule base

bidirectional communication 208closing harmless events 207duplicate event checking 207event correlation 208event drill-down processing 207multi-region support 209

rules 209event server, Tivoli Enterprise Console,

configuring 82, 83events

CCMS, sent to event consolecontrolling 91interpreting 91

IDOC, sent to event consolecontrolling 102


Ind

ex

events (continued)IDOC, sent to event console (continued)

interpreting 100syslog, sent to event console

controlling 96syslog, sent to TEC

by default 95examples

authorization roles, assigning 34filtering events 107syslog events, customizing events sent to

event console 97Windows

start exit routine 73stop exit routine 73

wr3rfc command 179executing a task

from the desktop 131exit routines for Windows, creating 72extended database status reporting 8, 78extended memory monitoring source 222extensibility 7

Ffeatures 1file package

client softwaredistributing 149log file 286

SAPGUIdistributing 149log file 286

transportsdistributing 46objects included 43

file system layout 287file systems, R/3, monitoring 120files

event adapter, alert, r3mibIID.conf 88event adapter, CCMS, r3moniIID.conf 89event adapter, CCMS, r3moniIID.evt file 89event adapter, IDOC, r3idocIID.conf 102

files (continued)event adapter, syslog

r3slogIID.cl 94r3slogIID.conf 94

log, location of 268sap_discovery.cfg file 56sap_gemevents.rls 157

free space checking 6function modules

authorization, Tivoli Manager for R/3 231importing

from command line 48using TMS 49

wr3rfc command 175

GGEMinstall_after.sh command 164getting started 27

Hheap memory monitoring source 222hints and tips, R/3 instrumentation 165HP-UX 11

64-bit support 75shared memory windows 75

IIDOC event adapter

description 99events sent to event console, controlling 102filtering events 107how it works 99parameters


performance considerations 104


IDOC event adapter (continued)r3idocIID.conf file 102

IDOC event slots 202IDOC status codes 227importing function modules

from command line 48using TMS 49

installationclient software

configuring for versions 4.5B andlater 147

configuring for versions prior to4.5B 144

distributing 149processing 6requirements

Tivoli Manager for R/3 9SAPGUI

configuring for versions 4.5B andlater 147

configuring for versions prior to4.5B 144

distributing 149installing

application proxy 11application proxy patch 13Manager for R/3

overview 15results 27where to install 9

R/3 instrumentationprocedure 156required role 154

Tivoli Manager for R/3authorization role required 19desktop after installation 27overview 9prerequisites 9procedure 19requirements 9

instrumented components 157interconnected Tivoli management regions 14ITS server

monitoring collection 110status, determining 40

ITS server status monitor 115

Jjobs 35

Llibraries, task

description 5R3 App Server tasks 136R3 Configuration tasks 36R3 DB Server tasks 140R3 Internal tasks 35R3 ITS Server tasks 141R3 List Maintenance tasks 38R3 System tasks 135

locating configuration tasks 35log files, location of 268logging mode, monitor, configuring 285long running work process monitoring 124, 220

Mmanaged nodes, monitors profile manager 115management tasks

cancel batch job 138cancel process 139display batch jobs 138display buffer information 138display OS/390 DB2 information 138display OS/390 information 138display OS collect information 138display process information 139display processes 139display roll page information 138R/3 instrumentation

R3Application component 161R3Database component 162R3ITSServer component 163R3System component 161

release batch job 138running

from the desktop 131


Ind

ex

management tasks (continued)start database 140start dbaccess 140start event adapter 137start ITS server 141start R3 system 135start server 137stop database 140stop event adapter 137stop ITS server 141stop R3 system 135stop server 137

message server status monitor 116messages 235monitoring

attributes 110buffer 221extended memory 222heap memory 222long running work process 220OS/390 225OS/390 DB2 223OS collect 216page area 218performance 222roll area 217user 223work process 219work process dispatch queue 220

collectionsITS server 110server central 111server remote 111UNIX file systems 113, 120Windows NT file systems 113, 121

logging mode, configuring 285profile manager

application server 114database server 114distributed daemon monitors 115ITS monitors 115managed nodes 115R3 central instance monitors 116

R3 DB server central monitors profile 114R3 ITS monitors profile manager 115R3 managed nodes profile manager 115

monitoring (continued)R3 message server monitors profile 116R3 print monitors profile 115R3 SAP Router monitors profile 115R3 server autodiscovery monitors

profile 114R3 server central monitors profile 114R3 server remote monitors profile 114R3 UNIX file system monitors profile 116R3 Windows NT file system monitors

profile 116saplpd daemon 115saprouter daemon 115sources

application server status 117cancelled job 125file system 120long running work process 124OS/390 127, 128OS/390 DB2 129OS collect 127OS collect, application server 127OS collect, database server 128performance 119server central 111server remote 111storage areas 118summary 110user sessions 123work process 123work process dispatch queue 124

monitorsR/3 instrumentation

current event status, viewing 164overview 163Tivoli Manager for R/3 163

Nnotation

environment variables xxipath names xxitypeface xxi


Oobjects, R/3

creatingautomatic discovery for NT 58automatic discovery for UNIX 59manually 60result 64

deletingprocedure 68result 68

operational event classes 187OS/390

data sharingconfiguring automatic discovery 56considerations 78

monitoring 78, 127R/3 database objects 77R/3 release support 77R/3 transports 77

OS/390 DB2 monitoring source 129, 223OS/390 monitoring source 128, 225OS collect monitoring source

application server 127attributes 216database server 128

Ppage area monitoring source 218path names, notation xxiperformance, R/3, monitoring 119performance considerations, IDOC event

adapter 104performance monitoring source 222platform type checking 6process information, displaying 139profile manager

R3 App Server 114R3 Central Instance Monitors 116R3 DB Server 114R3 Distributed Daemon Monitors 115R3 ITS monitors 115R3 managed nodes monitors 115

RR/3 alert

CCMS-generated 204configuring 52event classes 184event slots 199wr3mib diagnostics 282wr3rfc diagnostics 283

R/3 environment with Tivoli 1R/3 instrumentation

deleting R/3 resources 159event classes 198hints and tips 165installing

procedure 156required role 154

instrumented components 157monitors

current event status, viewing 164overview 163Tivoli Manager for R/3 163

R/3 resourcesnavigating to 159

rule set, adding 157tasks

running 161troubleshooting 165uninstalling 164

R/3 objectscreating 53

automatic discovery for NT 58automatic discovery for UNIX 59manually 60result 64


where to create 54R/3 resources

navigating to in Tivoli Business SystemsManager 159

R/3 resources, R/3 instrumentation,deleting 159

R/3 syslogevent classes 191


Ind

ex

R/3 syslog (continued)event slots 201

R/3 systemconfiguring for alerts 52

R/3 transportscopying 47distributing the file package 46objects included 43

R3 App Server Monitors profile manager 114R3 App Server tasks

authorization 136cancel batch job 138cancel process 139display batch jobs 138display buffer information 138display OS/390 DB2 information 138display OS/390 information 138display OS collect information 138display process information 139display processes 139display roll page information 138release batch job 138start event adapter 137start server 137stop event adapter 137stop server 137

R3 central instance monitors profilemanager 116

R3 Configuration tasks library 36R3 DB Distributed Daemon Monitors profile

manager 115R3 DB server central monitors profile 114R3 DB Server Monitors profile manager 114R3 DB Server tasks

authorization 140start database 140start dbaccess 140stop database 140

R3 Internal tasks library 35R3 ITS Monitors profile manager 115R3 ITS Server tasks

authorization 141start ITS server 141stop ITS server 141

R3 List Maintenance tasks library 38

R3 managed nodes monitors profilemanager 115

R3 message server monitors profile 116R3 print monitors profile 115R3 SAP Router monitors profile 115R3 server autodiscovery monitors profile 114R3 server central monitors profile 114R3 server remote monitors profile 114R3 system tasks

start R3 system 135stop R3 system 135

R3 System tasksauthorization 135

R3 UNIX file system monitors profile 116R3 Windows NT file system monitors

profile 116R3AppServer 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 102R3ITSServer object

creatingprocedure 63result 67



R3ITSServer object (continued)description 29endpoint name 29tasks, pop-up menu 67

R3Mgr_uninstall22.pl command 22r3mibIID.conf file 88r3moniIID.conf file 89r3moniIID.evt file 89r3slogIID.cl file 96r3slogIID.conf file 95R3System object

creatingmanually 60result 64using automatic discovery 55



release batch job task 138remote function call (RFC)

configuring 71user ID authorization 50

remote monitors 110remove autodiscovery task 60requirements, installation

Manager for R/3 9RFC

user ID authorization 50roll area monitoring source 217rules

bidirectional communication 208closing harmless events 207correlation 213database status integration 213distributed monitoring 211duplicate event checking 207event correlation 208event server 209multi-region support 209Tivoli Business System Manager

Instrumentation 213Tivoli Enterprise Console event server 209

running a taskfrom the desktop 131

Ssap_discovery.cfg file 56SAP file access, enabling for Windows 73sap_gemevents.rls rule file 157SAPGUI

file packageconfiguring for versions 4.5B and


4.5B 144distributing 149log file 286

installationadministrator-named file package 6command execution 6components, optional 6configuring for versions 4.5B and


4.5B 144distributing 149R/3 releases supported 6

sappld daemon, monitoring 115saprouter daemon, monitoring 115security enhancements 7server

applicationcentral monitors profile 114display performance information 138monitoring status 117OS collect monitoring source 127remote monitors profile 114starting 137status monitor 114

databasecentral monitors profile 114monitors profile manager 114OS collect monitoring source 128starting 140


Ind

ex

server (continued)ITS

starting 141status monitor 115

message, status monitor 116status

correcting on the desktop 286shared memory windows, HP-UX 11,

requirements 75sources and attributes, monitoring

buffer 221extended memory 222heap memory 222long running work process 220OS/390 225OS/390 DB2 223OS collect 216page area 218performance 222roll area 217user 223work process 219work process dispatch queue 220

sourcing the environment 267start database task 140start dbaccess task 140start event adapter task 88, 137start exit routine for Windows 73start ITS server task 141start R3 system task 135start server task 137status

application server, determining 38correcting

on the desktop 286database server

determining 39extending 78

ITS server, determining 40status codes, IDOC 227status event classes 197status monitoring

application server 114ITS server 115message server 116

stop database task 140

stop event adapter task 88, 137stop exit routine for Windows 73stop ITS server task 141stop R3 system task 135stop server task 137stopping automatic discovery 60storage areas, monitoring 118subscriber lists, creating 70syntax conventions, command 171syslog, R/3

event classes 191event slots 201

syslog event adapterdescription 94events sent to event console

controlling 96events sent to TEC

default 95filtering events 107parameters


r3slogIID.cl fileadding entries 96description 94modifying 96

r3slogIID.conf file 94starting 137stopping 137

SysMandescription 3wr3mib_64 command 173wr3mib command 173

Ttask libraries

description 5R3 App Server tasks 136R3 Configuration tasks 36R3 DB Server tasks 140R3 Internal tasks 35R3 ITS Server tasks 141R3 list maintenance tasks 38


task libraries (continued)R3 System tasks 135

task server, Tivoli Business SystemsManager 153

tasksrunning

from the Tivoli Business Systems Managerworkstation 161

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 88stop event adapter 88

tasks, managementcancel batch job 138cancel process 139database server

start database 140start dbaccess 140stop database 140

display batch jobs 138display buffer information 138display OS/390 DB2 information 138display OS/390 information 138display OS collect information 138display process information 139display processes 139display roll page information 138ITS server

start ITS server 141stop ITS server 141

R/3 instrumentationR3Application component 161R3Database component 162R3ITSServer component 163R3System component 161

tasks, management (continued)R/3 system

start R3 system 135stop R3 system 135

release batch job 138running

from the desktop 131start event adapter 137start server 137stop event adapter 137stop server 137

Tivoli authentication package for Windows,enabling 74

Tivoli Business Systems Managerevent classes 198event enablement 153event handling 153overview 152server 152task server 153workstation

overview 152synchronizing with the desktop 158

Tivoli Business Systems ManagerInstrumentation for R/3 151

Tivoli Enterprise Console event serverconfiguring 14, 82rule base

bidirectional communication 208closing harmless events 207duplicate event checking 207event correlation 208event drill-down processing 207multi-region support 209

rules 209Tivoli management regions, configuring 10transports, R/3

copying 47distributing the file package 46objects included 43

troubleshootingdisplay OS collect information task 286environment, setting up 267error alerts 282event processing

wr3mib diagnostics 282


Ind

ex

troubleshooting (continued)event processing (continued)

wr3rfc diagnostics 283file system layout 287log files, location of 268monitor logging mode, configuring 285server status, correcting

on the desktop 286Tivoli Enterprise Console event

processing 280troubleshooting, R/3 instrumentation 165

Uuninstalling

Manager for R/3 22R/3 instrumentation 164

UNIX file systems, monitoringcollection 113how to use 120

upgradingapplication proxy 13Manager for R/3

from version 1.5 or 1.5.1 16from version 2.0 17from version 2.1 18

user ID, configuring for RFC access 50user interface options

desktop 8Tivoli Business System Manager 8

user monitoring source 223user sessions, R/3, monitoring 123

Vvariables, notation for xxi

WWindows

creating exit routines for 72enabling

automatic discovery 74SAP file access 73Tivoli authentication package 74

environment variable, setting 75start exit routine example 73

Windows NTfile systems, monitoring 113, 120, 121stop exit routine example 73

wlcftap command 74work process

cancelling 139displaying 139monitoring 123

work process dispatch queue, monitoring 124,220

work process monitoring source 219wr3mib_64 command 173wr3mib command 173wr3mib diagnostics 282wr3rfc command 175wr3rfc diagnostics 283wsettap command 74


Part Number: 5698ASA

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC31-8411-05

(1P)

P/N:

5698

ASA