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

Transcription

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

2

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

4 Tivoli Manager for R/3 User s Guide (September 2000) Copyright Notice Copyright 1997, 2000 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products 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 any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli, Manage. Anything. Anywhere., The Power To Manage. Anything. Anywhere., TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli, Tivoli Enterprise. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. R/3 is a trademark of SAP AG. Oracle is a registered trademark of Oracle Corporation. Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System s or IBM s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A.

5 Contents Preface... xiii Who Should Read This Guide... xiii Prerequisite and Related Documents... xiii What This Guide Contains... xiv Typeface Conventions.... xvi Accessing Online Documentation... xvi Accessing the Files on the Product CD... xvii Accessing the Files on the Tivoli Web Site... xvii Terminology... xvii Contacting Customer Support... xix Chapter 1. Introducing Manager for R/ Overview of the R/3 Environment with Tivoli... 1 Manager for R/3 Functions... 2 Availability Management... 3 Automatic Discovery Task Libraries... 5 Automated R/3 SAPGUI Installation... 5 Security Enhancements... 6 Extensibility... 7 R/3 Release and System Compatibility User Interface Options Integration with Tivoli Database Manager Products... 8 Chapter 2. Planning for and Installing Manager for R/3 9 Where to Install Manager for R/ Installation Requirements Tivoli Manager for R/3 User s Guide iii

6 Configuring Tivoli Management Regions Installing the Application Proxy Planning for TEC Event Server Configuration Installing Manager for R/ Upgrading to Version 2.1 from Version 1.5 or Upgrading to Version 2.1 from Version Installing Manager for R/3 Version Uninstalling Manager for R/ Chapter 3. Getting Started with Manager for R/ What Was Installed Manager for R/3 Object Endpoints Configuring Manager for R/ Assigning Authorization Roles Using Manager for R/3 Configuration Tasks R3 Configuration Tasks R3 List Maintenance Tasks Determining R/3 Application Server Status Determining R/3 Database Server Status Determining R/3 ITS Server Status Chapter 4. Configuring Each SAP R/3 System Moving R/3 Transports into an R/3 Landscape Distributing the R/3 ABAP File Package Copying the Transports Importing the Function Modules From the Command Line Using the Transport Management System Configuring User IDs for RFC Interface Access iv User s Guide Version 2.1

7 Configuring R/3 Application Server Profiles Chapter 5. Configuring Manager for R/ Creating R/3 Objects Deciding Where to Create R/3 Objects Creating R/3 Objects Using Automatic Discovery Stopping Automatic Discovery Creating an R/3 Object from the Desktop Results of Creating R/3 Objects Deleting an R/3 Object Result of Deleting an R/3 System Object Result of Deleting an R/3 Application Server Object Result of Deleting an R/3 Database Server Object Result of Deleting an R/3 ITS Server Object Creating Subscriber Lists Configuring a Remote Function Call Configuring Manager for R/3 for Windows NT Creating Exit Routines for Windows NT Enabling the Local Administrator for SAP File Access Enabling Automatic Discovery for Windows NT Enabling the Tivoli Authentication Package for Windows NT Setting the Environment Variable for Windows NT Configuring Manager for R/3 for HP-UX HP-UX bit Support HP-UX 11 Shared Memory Windows Configuring Manager for R/3 for OS/ R/3 Release Support R/3 Transports R/3 Database Objects with OS/ Tivoli Manager for R/3 User s Guide v

8 Data Sharing Monitoring the OS/390 System Extending Database Server Status Reporting Chapter 6. Managing R/3 Events Configuring the TEC Event Server Configuring an Event Console Configuring Event Adapters Displaying Event Adapter Information Starting and Stopping an Event Adapter Using the Alert Event Adapter Understanding How the Alert Event Adapter Works Controlling Alert Events Using the Syslog Event Adapter Controlling Syslog Events Example of Controlling Syslog Events Using the IDOC Event Adapter Understanding How the IDOC Event Adapter Works Viewing and Interpreting IDOC Events Controlling IDOC Events Performance Considerations Filtering Events Chapter 7. Monitoring R/3 Resources Monitoring Collections Monitoring Sources Attributes R3 ITS Server Monitors R3 Server Remote and R3 Server Central Monitors vi User s Guide Version 2.1

9 R3 UNIX and R3 Windows NT File System Monitors Default Profile Managers R3 App Server Monitors Profile Manager R3 DB Server Monitors Profile Manager R3 Distributed Daemon Monitors Profile Manager R3 Managed Nodes Monitors Profile Manager R3 ITS Monitors Profile Manager R3 Central Instance Monitors Profile Manager Using Monitoring Sources Using the Application Server Status Monitor Using the Storage Monitors Using the Performance Monitors Using the File System Monitors Using the User Monitor Using the Work Process Monitors Using the Cancelled Job Monitor Using OS Collect and OS/390 Monitors Chapter 8. Tasks for Managing R/3 Resources Running a Task R3 System Tasks Controlling the R/3 System R3 App Server Tasks Controlling Event Adapters Controlling Application Servers Displaying Application Server Performance Information Managing Batch Jobs Controlling R/3 Work Processes R3 DB Server Tasks Tivoli Manager for R/3 User s Guide vii

10 Controlling a Database Server Controlling dbaccess R3 ITS Server Tasks Controlling ITS Servers Chapter 9. Distributing SAPGUI Software Creating SAPGUI Software File Packages Creating SAPGUI File Packages for SAPGUI Versions Prior to 4.5B 140 Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later Distributing SAPGUI Software Chapter 10. Tivoli GEM Instrumentation Understanding the Tivoli GEM Server Understanding the Tivoli GEM Console Tivoli GEM Instrumentation Event Handling Instrumented Components Instrumentation Task Libraries Preparing to Install Manager for R/3 Instrumentation Tivoli Management Regions Administrators Installation Prerequisites Installing and Configuring Tivoli GEM Instrumentation for Manager for R/ Installing or Upgrading the Tivoli GEM Instrumentation Definition Files Installing the Tivoli GEM Instrumentation Task Libraries Adding the Tivoli GEM Instrumentation Rule Set Synchronizing the Tivoli GEM Console with the Desktop Understanding R/3 Aggregate Resources viii User s Guide Version 2.1

11 Navigating to R/3 Resources Tivoli GEM Instrumentation Tasks R3System Component Tasks R3Application Component Tasks R3Database Component Tasks R3ITSServer Component Tasks Using the Tear-Away Log Running a Task from the Tivoli GEM Console Supported Monitors Monitor Operability Viewing Monitor Status Instrumenting Tivoli GEM Connection Support to R/3 Components Instrumenting a Connection to an R3System Component Instrumenting a Connection to an R3Application Component Instrumenting a Connection to an R3ITSServer Component Instrumenting a Connection to an R3Database Component Uninstalling Tivoli GEM Instrumentation Task Libraries Appendix A. Command Line Interface Commands 167 Command Line Syntax SysMan and RFC Commands wr3mib wr3rfc Appendix B. Event Classes and Rules Event Classes R/3 Alert Event Classes R/3 Operational Event Classes R/3 Syslog Event Classes R/3 IDOC Event Classes Tivoli Manager for R/3 User s Guide ix

12 Distributed Monitoring Event Classes Status Event Classes Tivoli GEM Instrumentation Event Classes Tivoli GEM Event Classes Error Event Classes Alert Event Slots Syslog Event Slots IDOC Event Slots Cancelled Job Event Slots CCMS-Generated Alerts Rules for Manager for R/3 Events Duplicate Event Checking Automatic Closing of Harmless Events Automatic Drill-Down Bidirectional Communication Event Correlation Multi-Region Support Integration with Tivoli GEM Integration with Tivoli Database Manager Products TEC Event Server Rules Distributed Monitoring Rules Database Status Integration Rules Correlation Rule Tivoli GEM Instrumentation Distributed Monitoring Rules Appendix C. Remote and Central Monitoring Sources OS Collect Source Roll Area Source x User s Guide Version 2.1

13 Page Area Source Work Process Source Work Process Dispatch Queue Source Long Running Work Process Source Buffer Source Performance Source Heap Memory Source Extended Memory Source User Source OS/390 DB2 Source OS/390 Source Appendix D. IDOC Status Codes Appendix E. Function Module Authorization Appendix F. Messages Appendix G. Troubleshooting Setting Up the Environment Log Files Task Log Files Monitor Log Files Event Adapter Log Files Miscellaneous Log Files TEC Events Error Alerts Event Diagnostic Tools Configuring Monitor Logging Mode Tivoli Manager for R/3 User s Guide xi

14 SAPGUI File Package Distribution Icon State File System Layout Hints on Using Tivoli GEM Using the Tivoli GEM Console Tivoli GEM Icon State Tivoli GEM Server Database Corruption Business and Component Description Files Icon Files Index xii User s Guide Version 2.1

15 Preface The Tivoli Manager for R/3 User s Guide provides information about planning for, installing, and managing R/3 systems with Tivoli Manager for R/3 (Manager for R/3). This guide describes the tasks and monitors that Manager for R/3 provides. It also describes how to distribute SAPGUI software. Who Should Read This Guide This guide is for system administrators who monitor and manage R/3 systems. This guide requires knowledge of Tivoli management software, UNIX and Windows operating systems, databases, SAP R/3, and optionally, the Tivoli Global Enterprise Manager (Tivoli GEM), Tivoli Manager for DB2, and Tivoli Manager for Oracle products. Prerequisite and Related Documents For hardware and software requirements, and other release information, refer to the Tivoli Manager for R/3 Release Notes. Related documents include: TME 10 Framework User s Guide TME 10 Framework Planning and Installation Guide TME 10 Framework Reference Manual TME 10 Enterprise Console Rule Builder s Guide TME 10 Enterprise Console User s Guide TME 10 Enterprise Console Reference Manual TME 10 Enterprise Console Event Integration Facility Guide TME 10 Enterprise Console Adapters Guide TME 10 Distributed Monitoring User s Guide TME 10 Software Distribution User s Guide Tivoli Manager for R/3 User s Guide xiii

16 Related documents for Tivoli Global Enterprise Manager Version include: Tivoli Global Enterprise Manager Installation and User s Guide Tivoli Global Enterprise Manager Instrumentation Guide Tivoli Global Enterprise Manager Release Notes Related documents for Tivoli database manager products include: Tivoli Module for DB2 User s Guide Tivoli Module for DB2 Release Notes Tivoli Manager for Oracle User s Guide Tivoli Manager for Oracle Release Notes What This Guide Contains This User s Guide contains the following sections: Introducing Manager for R/3 on page 1 Describes the basic features and functions of Manager for R/3. Planning for and Installing Manager for R/3 on page 9 Describes installation requirements, how to install Manager for R/3, and how to uninstall Manager for R/3. Getting Started with Manager for R/3 on page 27 Describes the information you need to get started and provides an overview of the tasks you must complete before you can use Manager for R/3. Configuring Each SAP R/3 System on page 43 Describes how to prepare an R/3 system for use with Manager for R/3. Configuring Manager for R/3 on page 53 Describes how to create R/3 system objects and server objects so you can manage your R/3 systems, R/3 application servers, R/3 database servers, and R/3 ITS servers with Manager for R/3. xiv User s Guide Version 2.1

17 This chapter also describes how to configure a remote function call and contains information about platform-specific configuration tasks. Managing R/3 Events on page 81 Describes how to configure the TEC event server, event consoles, and Manager for R/3 Alert Event Adapter, Syslog Event Adapter, and IDOC Event Adapter. Monitoring R/3 Resources on page 105 Describes Manager for R/3 monitoring collections, profile managers, and profiles. Tasks for Managing R/3 Resources on page 127 Describes Manager for R/3 management tasks. Distributing SAPGUI Software on page 139 Describes how to create R/3 SAPGUI software file packages for distribution of the SAPGUI for the Windows NT, Windows 95/98, and UNIX operating systems. Tivoli GEM Instrumentation on page 147 Describes planning, installation, and configuration of Tivoli GEM instrumentation. It also describes the tasks and monitors that become accessible for managing R/3 after the Tivoli GEM components have been successfully installed. Command Line Interface Commands on page 167 Describes the supported command line interface (CLI) commands that you can use with Manager for R/3. Event Classes and Rules on page 179 Describes the TEC event classes and rules delivered with Manager for R/3, slot values for the events, and background information on R/3 alerts. Remote and Central Monitoring Sources on page 207 Describes the monitoring sources and their attributes for the R3 Server Remote Monitors and R3 Server Central Monitors collections. IDOC Status Codes on page 219 Tivoli Manager for R/3 User s Guide xv

18 Describes the IDOC status codes. Function Module Authorization on page 223 Contains a list of the function modules delivered with Manager for R/3 and the R/3 authorization required to run each module. Messages on page 227 Contains a list of the messages produced by Manager for R/3. Troubleshooting on page 255 Describes the diagnostic techniques for tasks, monitors, Tivoli GEM instrumentation, and SAPGUI distribution. This section describes diagnostic commands and product directories. Typeface Conventions This guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Italics Commands, keywords, flags, and other information that you must use literally appear in bold. Variables and new terms appear in italics. Words and phrases that are emphasized also appear in italics. Monospace Code examples, output, and system messages appear in a monospace font. Accessing Online Documentation Manager for R/3 documentation is available in the following online formats on both the Manager for R/3 CD and the Tivoli Web site: Portable Document Format (.pdf, which you can view or print using the Adobe Acrobat Reader). If you do not already have Adobe Acrobat Reader, you can obtain it for free by clicking the Get Acrobat Reader icon at the Adobe Web site, and following the steps that are provided. Hyptertext Markup Language (.htm), which you can view using your default Web browser. xvi User s Guide Version 2.1

19 Accessing the Files on the Product CD The.pdf and the.htm files, (sa21ug.pdf and sa21ug.htm) for the Tivoli Manager for R/3 User s Guide are available on the Manager for R/3 CD in the /DOC directory. Note: The Tivoli Manager for R/3 Release Notes document is not provided on the Manager for R/3 CD. Accessing the Files on the Tivoli Web Site The Tivoli Manager for R/3 User s Guide and the Tivoli Manager for R/3 Release Notes are available at the following location on the Tivoli Web site: Terminology You must be a registered user to access this Web site. If you have not registered, when the Username and Password Required prompt is displayed, click Cancel and follow the registration directions. The following R/3 terms are used throughout this document: ALE Application Link Enabling, the SAP communication level facililty for transferring IDOCs between R/3 systems. application server The component of an R/3 system that processes customer work requests. authorization profile Within an R/3 system, an authorization profile is a collection of authorization objects. An authorization profile, when assigned to an R/3 user, defines the functions that the user is allowed to perform. central instance The R/3 application server that is running the message server. database server The component of an R/3 system that handles database requests. Tivoli Manager for R/3 User s Guide xvii

20 function module An R/3 ABAP program that has a clearly defined interface and can be used in several programs. The function module library manages all function modules and provides search facilities in the development environment. IDOC Intermediate Document, an internal SAP self-defining data structure for the transfer of business objects in a well-defined manner. Internet Transaction Server (ITS server) The component of an R/3 system that provides an interface between the World Wide Web and the R/3 system. An ITS server consists of the following components: AGate The component that bridges an R/3 application server to a WGate. WGate The component that bridges an AGate to a standard Web server. A single-host ITS server configuration is one in which both the AGate and WGate components run on the same machine. A dual-host ITS server configuration is one in which the AGate and WGate components run on different machines. instance number A two-digit number identifying an R/3 application server, assigned when an R/3 administrator installed the R/3 application server. landscape A set of R/3 systems that share the same transport directory. RFC (remote function call) A protocol for invoking R/3 modules. SAPGUI SAP graphical user interface, the R/3 presentation software. SID (system identifier) The three-character name of an R/3 system. xviii User s Guide Version 2.1

21 transport file A set of ABAP objects to be imported into an R/3 system. For a complete glossary of Tivoli and related terms, refer to the glossary at the following Web site: Tivoli is in the process of changing product names. Products referenced in this manual might still be available under their old names, for example, TME 10 Module for DB2 instead of Tivoli Manager for DB2. Contacting Customer Support For support for this or any other Tivoli product, you can contact Tivoli Customer Support in one of the following ways: Visit our Web site at Send to support@tivoli.com Customers in the United States can also call TIVOLI8. International customers should consult the Web site for customer support telephone numbers. You can also review the Customer Support Handbook, which is available on our Web site at When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. Company identification information might also be needed to access various online services available on the Web site. The Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, redbooks, and Whitepapers. The Tivoli Manager for R/3 User s Guide xix

22 documentation sets for some product releases are available in both PDF and HTML formats. Translated documents are also available for some product releases. You can order documentation by at Please provide the part number or order number of the desired document; alternatively, you can provide the document s title, version number, and date of publication. We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways: Send to pubs@tivoli.com. Fill out our customer feedback survey at xx User s Guide Version 2.1

23 1 Introducing Manager for R/3 1. Introducing Manager for R/3 This chapter provides a brief overview of Tivoli Manager for R/3 as it relates to R/3 systems. It provides a summary of the product functions. Overview of the R/3 Environment with Tivoli A typical R/3 environment includes one or more R/3 systems, where each R/3 system consists of one database server and one or more application servers. The R/3 application servers can run on the UNIX and Windows NT operating systems. The database servers can run on the UNIX, Windows NT, and OS/390 operating systems. The typical Tivoli management environment consists of a Tivoli Management Region (TMR) server, a Tivoli Event Console (TEC) server, managed nodes, TMA endpoints, and gateways. Manager for R/3 operates at both the machine level and the R/3 system level: To manage at the machine level, Manager for R/3 uses monitors provided with the Tivoli Distributed Monitoring product. These monitors provide status on the machines and daemons. To manage at the R/3 system level, Manager for R/3 uses monitors, event adapters, and tasks provided with the Manager for R/3 product. Manager for R/3 represents each R/3 system and server as a Tivoli object. Each object is a special type of Tivoli endpoint that enables Manager for R/3 to distribute Tivoli Manager for R/3 User s Guide 1

24 monitors and tasks directly to the endpoint. As with any Tivoli endpoint, you can run a task against one or more application servers across the R/3 systems that the TMR server manages. For more information, see Manager for R/3 Object Endpoints on page 29. Manager for R/3 provides three event adapters that run on R/3 application servers. Two of these event adapters, the Alert Event Adapter and the Syslog Event Adapter, should be configured for each R/3 application server. The third event adapter, the IDOC Event Adapter, needs only to be configured for one R/3 application server in each R/3 system. R/3 application servers are the primary resources used by Manager for R/3 in managing the R/3 system. The application servers provide management information about themselves. In addition, the application servers are gateways for collecting R/3 database server information. Manager for R/3 obtains performance information about the R/3 database server through calls made to one of the R/3 application servers, which allows Manager for R/3 to gather database information for all platforms, including DB2 on OS/390. Manager for R/3 Functions Manager for R/3 makes it easier for you to manage SAP R/3 installations by providing the following features: Availability management Automatic discovery Task libraries Automated R/3 SAPGUI installation Security enhancements Extensibility R/3 release compatibility User interface options Integration with Tivoli database manager products 2 User s Guide Version 2.1

25 Availability Management With Manager for R/3, you can monitor and retrieve R/3 alert traps and R/3 syslog messages using the Alert Event Adapter and the Syslog Event Adapter, respectively. You can also monitor the transfer of business data from one R/3 system to another using the IDOC Event Adapter. With the monitoring collections, you can monitor R/3 application servers, Internet transaction servers (R/3 ITS servers), and R/3 file systems and daemons. When so configured, events are forwarded to a TEC event server for display and processing. You can use the filtering capabilities to send specific events to the TEC. Manager for R/3 determines the availability of R/3 servers from status events and represents server availability through the icon for each R/3 server. 1. Introducing Manager for R/3 R/3 Alert Event Adapter The R/3 Computing Center Management System (CCMS) contains an alert facility that monitors critical elements of the R/3 system and notifies administrators of potential problems. CCMS publishes some of this information through its R/3 System Management (SysMan) interface. Manager for R/3 provides a Tivoli Enterprise Console (TEC) event adapter for querying the R/3 SysMan interface and converting the R/3 alert traps into TEC events. R/3 Syslog Event Adapter Manager for R/3 provides a TEC event adapter that processes the R/3 syslog and converts new entries to TEC events. R/3 IDOC Event Adapter Manager for R/3 provides a TEC event adapter that monitors SAP Intermediate Documents (IDOCs) for error status codes and reports them as TEC events. R/3 systems use IDOCs to transfer business data between business systems. A business system can be an R/3 system or a customer application. Successful transfer of IDOCs is crucial to ensure that all R/3 systems are synchronized on the business data they are processing. Monitoring Collections Manager for R/3 supplies a set of monitoring collections that provide monitors for R/3 resources. These Tivoli Distributed Monitoring Tivoli Manager for R/3 User s Guide 3

26 collections provide a wide range of internal and external R/3 monitors, such as monitoring performance statistics from the R/3 SysMan, or monitoring internal R/3 buffer statistics by using the R/3 Remote Function Call (RFC) interface. Manager for R/3 also provides monitoring collections that provide monitors for R/3 ITS servers and R/3 file systems and daemons. You can configure the thresholds and responses to proactively monitor and create different severity levels of TEC events. See Monitoring R/3 Resources on page 105 for more information. Tivoli Enterprise Console (TEC) The TEC provides a consolidated event view for one or more R/3 systems, so that you can create and configure different views for any number of R/3 administrators and R/3 systems. TEC Event Server Rule Base The TEC event server rule base provides intelligent event processing and correlation. The Manager for R/3 TEC rule sets can be extended to meet local processing requirements. The Tivoli Enterprise Console Rule Builder s Guide describes a non-programming environment for extending the functionality of the rule sets. For example, you can easily automate the gathering of additional diagnostics for a specific event by specifying the trigger event and the desired task. The Manager for R/3 provides rules that enable these functions: Duplicate event checking Automatic closing of harmless events Automatic drill-down Bidirectional communication Event correlation Multi-region support Integration with Tivoli GEM Integration with Tivoli database manager products For more information, see Rules for Manager for R/3 Events on page User s Guide Version 2.1

27 Automatic Discovery Manager for R/3 provides an automatic discovery function that discovers existing R/3 systems and servers and creates the appropriate Tivoli objects. Manager for R/3 provides a task that enables you to configure when to run the automatic discovery function. For more information, see Creating R/3 Objects Using Automatic Discovery on page 55. Task Libraries Manager for R/3 provides a set of task libraries to assist in performing operational and administrative tasks. By using these tasks, you can start, stop, and display R/3 resources and configure Manager for R/3 to meet the unique needs of each R/3 system being managed. See R3 Configuration Tasks on page 36 and Tasks for Managing R/3 Resources on page 127 for more information about these tasks. Automated R/3 SAPGUI Installation The R/3 presentation software, usually known as the SAP graphical user interface (SAPGUI), runs on UNIX systems (with the Motif window manager), Windows NT systems, and Windows 95/98 systems. Manager for R/3 enables you to create a customized SAPGUI installation file package. The installation of the SAPGUI file package creates the necessary program groups and icons on the user's desktop. The following functions are provided: SAPGUI support for R/3 releases. For information about supported R/3 releases, refer to the Tivoli Manager for R/3 Release Notes. SAPGUI installation tasks specifically configured for each designated R/3 release. Installation of optional SAPGUI components. For example, you can configure a file package to include graphics, spreadsheet macros, and the remote function call components. Language selection Before and after installation processing, including: 1. Introducing Manager for R/3 Tivoli Manager for R/3 User s Guide 5

28 v v Free space checking. The amount of free space required is automatically calculated by the components selected. The target system is checked for adequate free space before the installation begins. Platform type checking. The Tivoli Software Distribution process automatically checks that the proper architecture or platform type is distributed to the endpoint. v Optional SAPGUI command execution. The SAPGUI installation dialogs provide for easy input of two SAPGUI installation commands. This makes it possible to easily enhance the SAPGUI installation scripts that allow remote file system mounting with a simple network command. Administrator-defined file package organization, which enables you to organize file packages by business requirements rather than by operating system or processor architecture types. For example, you can organize and distribute SAPGUI installation file packages by marketing, sales, or Computer Aided Design (CAD). Security Enhancements Security enhancements include policy region resource roles and secure external communication. Policy Region Resource Roles Manager for R/3 configures each R/3 system as its own policy region. In addition, Manager for R/3 uses three resource roles. Giving a Tivoli administrator these resource roles in a particular policy region authorizes the administrator to perform certain R/3 tasks. For additional information, see Assigning Authorization Roles on page 33. Providing Secure External Communication Using a configuration task, you can specify an R/3 user ID and password for each R/3 system. The Manager for R/3 uses this R/3 user ID and password for remote function call (RFC) processes. The password is stored in encrypted form. The Manager for R/3 access program obtains the user ID and password as needed to access the 6 User s Guide Version 2.1

29 RFC functions and the corresponding Advanced Business Application Programming (ABAP) function modules. Extensibility Extensibility is provided by the Tivoli Framework and Manager for R/3 tools, monitoring collections (see Monitoring Collections on page 3), and TEC event server rule sets (see TEC Event Server Rule Base on page 4). Tivoli Framework The Tivoli Framework and applications provide a comprehensive management system. Manager for R/3 implements the most important features of the Tivoli Framework and its applications while maintaining all of the extensibility of the object framework. 1. Introducing Manager for R/3 Manager for R/3 Tool Manager for R/3 provides a powerful tool in the wr3rfc program when run as a command. The wr3rfc runs the R/3 function modules that support the RFC interface. You can use this command to manage the R/3 environment. (See Command Line Interface Commands on page 167.) R/3 Release and System Compatibility Manager for R/3 supports multiple R/3 systems and releases. These systems can be at different R/3 release levels. Manager for R/3 also supports multiple R/3 releases for distribution of the SAPGUI software and multiple R/3 ITS server release levels. See the Tivoli Manager for R/3 Release Notes for the release levels that are supported. User Interface Options Tivoli software offers a choice of user interface options: Tivoli desktop or Tivoli GEM console. This document, in general, provides procedures and screen illustrations using the desktop. Using the Desktop The Tivoli desktop is a graphical user interface, or GUI. It provides a simple way to work with your resources and monitor their condition. Tivoli Manager for R/3 User s Guide 7

30 Using Tivoli GEM Tivoli Global Enterprise Manager (Tivoli GEM) provides a GUI that represents managed resources in a business-systems view. This alternative view gives administrators a way to view not only managed resources but their relationships with each other. (See Tivoli GEM Instrumentation on page 147.) Integration with Tivoli Database Manager Products If you have the Tivoli Manager for DB2 or the Tivoli Manager for Oracle installed, Manager for R/3 can update the status of the database server with the status of the database as reported by the Tivoli Manager for DB2 or Tivoli Manager for Oracle. 8 User s Guide Version 2.1

31 2 Planning for and Installing Manager for R/3 This chapter describes the requirements you must meet before you install Tivoli Manager for R/3. It describes how to install Manager for R/3, and it also describes how to uninstall Manager for R/3. If Tivoli GEM is installed, you can optionally install Tivoli GEM instrumentation. See Tivoli GEM Instrumentation on page 147. Where to Install Manager for R/3 Install Manager for R/3 on the following machines: The Tivoli Management Region (TMR) server The Tivoli Enterprise Console (TEC) event server that processes Manager for R/3 events Each managed node that runs an R/3 application server, R/3 ITS server components, R/3 database server, or R/3 SAPGUI installation server All gateways 2. Planning for and Installing Manager for R/3 Installation Requirements Before you install the Manager for R/3, you must meet the following requirements: 1. Ensure that you are running on a supported operating system and that you install all prerequisite software. Refer to the Tivoli Tivoli Manager for R/3 User s Guide 9

32 Manager for R/3 Release Notes for details about supported hardware and operating systems, prerequisite software, and disk space requirements. 2. Configure the Tivoli Management Regions (TMRs). See Configuring Tivoli Management Regions. 3. If you are running R/3 application servers on TMA endpoints, ensure that the TMA endpoints and gateways are properly configured and functional. Refer to the TME 10 Framework Planning and Installation Guide. 4. Ensure that the Application Proxy is installed. For information about the required level, refer to the Tivoli Manager for R/3 Release Notes. For installation instructions, see Installing the Application Proxy on page Configure the TEC event server. See Planning for TEC Event Server Configuration on page Optionally, if you manage R/3 resources with Tivoli GEM, see Tivoli GEM Instrumentation on page 147 for installation requirements. Also, ensure that the Tivoli GEM server is configured and the Tivoli GEM consoles are installed. 7. Optionally, if you want to extend Manager for R/3 database status reporting, install Tivoli Manager for DB2 or Tivoli Manager for Oracle. You can install Manager for DB2 or Manager for Oracle either before or after you install Manager for R/3. For more information, see Extending Database Server Status Reporting on page 78. Configuring Tivoli Management Regions Before installing the Manager for R/3, configure the TMR to contain the Tivoli server, the TEC event server, and the R/3 application servers and the R/3 database servers for the R/3 system. Because R/3 is normally configured with the database server and the application servers on the same LAN segment, this partitioning provides a good model for defining a TMR boundary. TMR boundaries are important because of the relationship with TEC event server boundaries; a TMR can have only one TEC event server. 10 User s Guide Version 2.1

33 You can manage multiple R/3 systems in a single TMR. These R/3 systems can be used for development, test, and production. However, because production systems are so critical to an enterprise s business, you should consider placing production systems in their own TMRs. When multiple R/3 systems are in the same TMR, events from all systems go to the same TEC event server. Separating production events from test and development events is another reason to put production systems in their own TMR. Refer to the TME 10 Framework User s Guide for more information about configuring TMRs. If you are planning to use Tivoli gateways to manage TMA endpoints and you are concerned about gateway failure, see Deciding Where to Create R/3 Objects on page 54 for additional planning information. Installing the Application Proxy The Application Proxy is an extension of the Tivoli Framework that provides a common set of services that are used by the Manager for R/3. This section describes how to install Application Proxy 1.1 if you do not already have it installed. This section also describes how to upgrade to Application Proxy 1.1 if you have Application Proxy 1.0 installed, and it describes how to install the required Application Proxy patch. The following table lists the context and authorization roles required to install or upgrade the Application Proxy: 2. Planning for and Installing Manager for R/3 Activity Context Required Roll Install or upgrade the Tivoli desktop install_product Application Proxy Install the Application Proxy patch Tivoli desktop install_product Installing Application Proxy Version 1.1 To install the Application Proxy for the first time, follow these steps: Tivoli Manager for R/3 User s Guide 11

34 1. From the Desktop menu, select Install > Install Product to display the Install Product dialog. 2. Click Select Media to display the File Browser dialog. This dialog enables you to specify the path to the installation media. 3. Enter the full path to the Application Proxy in the Path Name text field. The Application Proxy is located in the /APPLPRXY directory on the Manager for R/3 CD. 4. Click Set Path. The File Browser dialog displays the contents of 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 with ApplicationProxy, Version 1.1 listed in the Select Product to Install scrolling list. 6. Select ApplicationProxy, Version 1.1 in the Select Product to Install scrolling list. 7. Select the target clients on which you do not want to install the Application Proxy from the Clients to Install On list and click the right arrow button to move them to the Available Clients list. Note: Install the Application Proxy on the following machines: TMR server TEC event server Each managed node that runs an R/3 application server, R/3 database server, R/3 ITS server components, 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 the installation process. 9. Click Continue Install to perform the Application Proxy installation. The dialog displays messages showing the progress of the installation and when the installation is completed. 12 User s Guide Version 2.1

35 10. Click Close. 11. Install Application Proxy patch. See Installing the Application Proxy Patch. Upgrading to Application Proxy 1.1 To upgrade the Application Proxy from Version 1.0 to Version 1.1, install ApplicationProxy, Version 1.1 Upgrade as a patch. Follow these steps: 1. From the Desktop menu on the Tivoli desktop, select Install > Install Patch. The ApplicationProxy, Version 1.1 Upgrade is located in the /APXYUPGD directory on the Manager for R/3 CD. Note: Install the ApplicationProxy, Version 1.1 Upgrade on each machine on which you installed Application Proxy Install the required Application Proxy patch. See Installing the Application Proxy Patch. Installing the Application Proxy Patch To install the required Application Proxy patch, from the Desktop menu on the Tivoli desktop, select Install > Install Patch. The patch is located in the /APXYPTCH directory on the Manager for R/3 CD. For information about the Application proxy patch that is required, refer to the Tivoli Manager for R/3 Release Notes. Notes: 1. Install the Application Proxy patch on each machine on which you have installed or upgraded to Application Proxy Version If you installed Manager for R/3 before you installed the Application Proxy patch, you must restart the oserv on each machine on which the patch was installed to ensure that the patch takes effect. Planning for TEC Event Server Configuration For each configuration, the Manager for R/3 Alert Event Adapter, Syslog Event Adapter, and IDOC Event Adapter send their events to the configured TEC event server regardless of the TMR in which the 2. Planning for and Installing Manager for R/3 Tivoli Manager for R/3 User s Guide 13

36 TEC event server is located. For the alert event adapter, additional drill-down processing is performed. Drill-down processing sends events using either Tivoli object calls or the Tivoli wpostemsg command, depending on the type of endpoint originating the event. You can configure TEC event servers in several ways: One TMR and one TEC event server In this configuration, the TEC event server is defined in the TMR, and the TEC event server receives all events. Multiple TMRs and multiple TEC event servers In this configuration, each TMR is assumed to have its own TEC event server. Each TEC event server receives all events from its local TMR. Optionally, you can configure a TEC event server to automatically forward events to another TEC event server in another TMR. See Configuring the TEC Event Server on page 82. Multiple TMRs and one TEC event server In this configuration, one TEC event server receives events from all TMRs. Support for this configuration depends on the type of endpoints sending events to the TEC event server as follows: v v If you want to collect Manager for R/3 events only from managed nodes, you need to install the TEC product in every TMR even though the TEC event server will be active in only one TMR. Installing the TEC product in every TMR provides the infrastructure needed by Manager for R/3 to send events using Tivoli object calls. Resources must be shared between the TMRs. If you want to collect Manager for R/3 events only from TMA endpoints, you need to install the TEC product only in the TMR hosting the TEC event server. Resources must be shared between the TMRs, and the EventServer class must be registered in all TMRs not hosting the TEC event server. This configuration enables Manager for R/3 to send events using the wpostemsg command from the TMA endpoints. 14 User s Guide Version 2.1

37 Note: Collecting Manager for R/3 events to a single TMR from both managed nodes and TMA endpoints is not supported. Installing Manager for R/3 After meeting the requirements described in Installation Requirements on page 9, you can install Manager for R/3. To install Manager for R/3, do one of the following: If you have Manager for R/3 Version 1.5 or Version installed, see Upgrading to Version 2.1 from Version 1.5 or Note: Versions of Manager for R/3 prior to Version 1.5 are not supported. If you have Manager for R/3 Version 2.0 installed, see Upgrading to Version 2.1 from Version 2.0 on page 17. If you are installing Manager for R/3 for the first time, see Installing Manager for R/3 Version 2.1 on page 18. The following table lists the context and authorization role required to install or upgrade Manager for R/3: 2. Planning for and Installing Manager for R/3 Activity Context Required Roll Install or upgrade Tivoli desktop install_product Manager for R/3 Attention: Upgrading Manager for R/3 to Version 2.1 from a previous release replaces files and, therefore, all local code modifications that you have made will be lost. Before upgrading to Version 2.1, make a backup copy of your local changes. Upgrading to Version 2.1 from Version 1.5 or Because the Manager for R/3 product was restructured after Version 1.5.1, you cannot upgrade Manager for R/3 directly from Version 1.5 or Version to Version 2.1. To upgrade to Version 2.1, consider one of the following options: Tivoli Manager for R/3 User s Guide 15

38 If you want to preserve Version 1.5 or Version configuration data for managed nodes (RFC logon parameters, Alert Event Adapter parameters, and monitor profiles), do the following: 1. Back up the Tivoli database. 2. Install Manager for R/3 Version 2.0 and migrate configuration data as described in the Tivoli Manager for R/3 Release Notes for Version 2.0. You can obtain a copy of the Version 2.0 release notes from the Tivoli Customer Support Web site ( 3. Create Tivoli objects for your R/3 systems, R/3 application servers, and R/3 database servers as described in Chapter 5 of the Tivoli Manager for R/3 User s Guide, Version 2.0. You can obtain a copy of the Version 2.0 user s guide from the Tivoli Customer Support Web site ( 4. Back up the Tivoli database, saving the backup file with a different name than the previous backup file. 5. Upgrade to Version 2.1 as described in Upgrading to Version 2.1 from Version 2.0 on page Back up the Tivoli database, saving the backup file with a different name than the previous backup file. Do a fresh installation of Version 2.1 as follows: 1. Back up the Tivoli database. 2. Uninstall Manager for R/3 Version 1.5 or Version as described in the Tivoli Manager for R/3 Release Notes for Version You can obtain a copy of the Version release notes from the Tivoli Customer Support Web site ( 3. Install Version 2.1 as described in Installing Manager for R/3 Version 2.1 on page Back up the Tivoli database, saving the backup file with a different name than the previous backup file. 16 User s Guide Version 2.1

39 Upgrading to Version 2.1 from Version 2.0 To upgrade Manager for R/3 from Version 2.0 to Version 2.1, back up the Tivoli database and then install Tivoli Manager for R/3 Version 2.1 (Upgrade from Version 2.0) as a patch. Tivoli Manager for R/3 Version 2.1 (Upgrade from Version 2.0) is located in the /UPGRADE directory on the Manager for R/3 CD. Notes: 1. Install the upgrade on each machine on which you installed Manager for R/3 Version If you did not install Manager for R/3 Version 2.0 on all gateways, ensure that you install Manager for R/3 Version 2.1 on all gateways. 3. The Syslog Event Adapter that is installed with the upgrade patch requires the Version 2.1 transports. You can prepare your R/3 systems prior to installing the upgrade patch by installing the transports from the /ABAP directory on the Manager for R/3 CD. Install the transports similar to the procedure that is described in Moving R/3 Transports into an R/3 Landscape on page 44. If you upgrade to Version 2.1 without first installing the Version 2.1 transports, the Syslog event adapters will fail. 4. To receive IDOC events, configure the TEC to add the WR3IDOC event source as described in Configuring an Event Console on page For information about upgrading Tivoli GEM instrumentation from Version 2.0 to Version 2.1, see Upgrading the Tivoli GEM Instrumentation Task Libraries on page Planning for and Installing Manager for R/3 The upgrade patch completely upgrades Manager for R/3 Version 2.0 to Version 2.1, replacing all product files and updating R/3 system, R/3 application server, and R/3 database server objects. The upgrade also preserves the following configuration data: RFC logon parameters: v Client v User Tivoli Manager for R/3 User s Guide 17

40 v Password v Language Alert and Syslog event adapter parameters: v Host name of the TEC event server v TEC event server port number v Polling delay v Trace logging level v Error logging level Subscription lists Monitor profiles Notes: 1. The upgrade does not automatically distribute the monitors. You must distribute the monitors manually. 2. Because the Alert and Syslog event adapters are replaced, you must start the Alert and Syslog event adapters that are installed on UNIX. Alert and Syslog event adapters that are installed on Windows NT are automatically started. Installing Manager for R/3 Version 2.1 To install Manager for R/3, follow these steps: 1. Back up the Tivoli database. 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. This dialog enables you to specify the path to the installation media. 4. Enter the full path to the Manager for R/3 installation files in the Path Name text field. The Manager for R/3 files are located in the /PRODUCT directory on the Manager for R/3 CD. 18 User s Guide Version 2.1

41 5. Click Set Path. The File Browser dialog displays the contents of the specified media in the Files scrolling list. 2. Planning for and Installing Manager for R/3 6. Click Set Media & Close. The File Browser dialog is closed, and the Install Product dialog is displayed. The Tivoli Manager for R/3, Version 2.1 product is listed in the Select Product to Tivoli Manager for R/3 User s Guide 19

42 Install scrolling list. 7. Select Tivoli Manager for R/3, Version 2.1 in the Select Product to Install scrolling list. 8. Select the target clients on which you do not want to install Manager for R/3 from the Clients to Install On list and click the right arrow button to move them to the Available Clients list. Note: Manager for R/3 must be installed on the following machines: TMR server TEC event server Each managed node that runs an R/3 application server, R/3 database server, R/3 ITS server components, or R/3 SAPGUI installation server All gateways 20 User s Guide Version 2.1

43 9. Click Install & Close. The Product Install dialog is displayed, listing the actions that will be taken when you complete the installation process. 10. Click Continue Install to perform the Manager for R/3 installation. The Product Install dialog displays messages showing the progress of the installation and when the installation is completed. 11. Click Close. The desktop now displays the Manager for R3 policy region. 2. Planning for and Installing Manager for R/3 12. Back up the Tivoli database, saving the backup file with a different name than the previous backup file. Uninstalling Manager for R/3 To uninstall Manager for R/3, follow these steps: Tivoli Manager for R/3 User s Guide 21

44 Note: The create_uninstall_task.sh and R3Mgr_uninstall21.pl commands that are used in this procedure are installed with the Manager for R/3. If you do not find these scripts in the $BINDIR/../generic_unix/TME/SAPUNINST directory, get a copy of these scripts from the /UNINST directory on the Manager for R/3 CD. 1. If you are running automatic discovery, remove scheduled jobs for automatic discovery. Run the following tasks in the R3 Configuration Tasks library: Remove Autodiscovery for NT Remove Autodiscovery for UNIX 2. Create the Uninstall Manager for R/3 Version 2.1 task. Go to the $BINDIR/../generic_unix/TME/SAPUNINST directory on the TMR server and enter the following command: create_uninstall_task.sh Policy_Region_Name Where Policy_Region_Name is the name of an existing policy region in which you want to create the R3 Product Management Tasks library and the Uninstall Manager for R/3 Version 2.1 task. Because the Uninstall Manager for R/3 Version 2.1 task uninstalls Manager for R/3 policy regions and task libraries, enter the name of an existing policy region that is not part of the Manager for R/3 product. The create_uninstall_task.sh command creates the Uninstall Manager for R/3 Version 2.1 task that you can run on managed nodes and TMA endpoints to uninstall Manager for R/3. The command also creates the R3 Product Management Tasks library in the policy region you specify and adds the Uninstall Manager for R/3 Version 2.1 task to this task library. 3. Uninstall Manager for R/3 from the TMR server. Follow these steps: Note: To uninstall Manager for R/3, you must have Tivoli administrator authority. 22 User s Guide Version 2.1

45 a. Run the following command to check for and repair database inconsistencies: wchkdb -u Note any remaining inconsistencies. b. Go to the $BINDIR/../generic_unix/TME/SAPUNINST directory and enter one of the following commands: UNIX: R3Mgr_uninstall21.pl Windows NT: perl R3Mgr_uninstall21.pl The syntax for the R3Mgr_uninstall21.pl command is: R3Mgr_uninstall21.pl [ g] [ yes] g Uninstalls only Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1. yes Uninstalls the product without prompting for confirmation. 2. Planning for and Installing Manager for R/3 The R3Mgr_uninstall21.pl command stops Manager for R/3 event adapters and removes the following items from the TMR server: Policy regions Task libraries Monitoring collections Objects and object classes (R3System, R3AppServer, R3DBServer, and R3ITSServer) Profile managers Profiles Installed files Indicator collections Tivoli Manager for R/3 User s Guide 23

46 TEC sources (WR3MIB, WR3SLOG, and WR3IDOC) Tivoli GEM instrumentation installed files and task libraries Note: The R3Mgr_uninstall21.pl command does not remove the following items: Baroc classes TEC rules TEC event console filters ABAP transports Tivoli GEM instrumentation definition files from the Tivoli GEM server The R3 Product Management Tasks library, which contains the Uninstall Manager for R/3 Version 2.1 task The SAPUNINST directory Scheduled jobs for automatic discovery If you plan to reinstall Manager for R/3, you do not need to remove the listed items. If you do not plan to reinstall Manager for R/3 and you want to remove the listed items, you can manually remove the baroc classes, the TEC rules, the TEC event console filters, the R3 Product Management Tasks library, and the SAPUNINST directory. To view messages pertaining to the uninstall process, look in the R3Mgr_uninstall21.log file in one of the following directories: UNIX: /tmp Windows NT managed node: %DBDIR%\tmp Windows NT TMA endpoint: %LCF_DATDIR% 24 User s Guide Version 2.1

47 c. Run the following command to check for and repair database inconsistencies: wchkdb -u 4. Uninstall Manager for R/3 on the managed nodes and TMA endpoints. Run the Uninstall Manager for R/3 Version 2.1 task in the R3 Product Management Tasks library against the appropriate managed nodes and TMA endpoints. The following table describes the authorization role and target for the uninstall task: Task Role Target Uninstall Manager for R/3 Version 2.1 install_product Managed node and TMA endpoint The Uninstall Manager for R/3 Version 2.1 task stops Manager for R/3 event adapters and removes the following items from the managed nodes and TMA endpoints: Installed files Windows NT services for Manager for R/3 event adapters 2. Planning for and Installing Manager for R/3 Tivoli Manager for R/3 User s Guide 25

48 26 User s Guide Version 2.1

49 3 Getting Started with Manager for R/3 This chapter provides an overview of the steps you must complete to configure Manager for R/3, and it provides some important information about using Manager for R/3. This chapter also describes the required authorization roles and targets for Manager for R/3 configuration tasks. What Was Installed After installing Manager for R/3, the Manager for R3 policy region 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. Getting Started with Manager for R/3 Tivoli Manager for R/3 User s Guide 27

50 See Monitoring R/3 Resources on page 105 for information about the monitor profile managers. See Moving R/3 Transports into an R/3 Landscape on page 44 for information about the R3 Transports 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 Server Tasks, R3 ITS Server Tasks, and R3 System Tasks, see Tasks for Managing R/3 Resources on page 127. Open the Manager for R3 policy region icon to display the Policy Region: Manager for R3 window: The R3 Configuration policy region contains the following: 28 User s Guide Version 2.1

51 R3 System List profile manager The following task libraries: v R3 Configuration Tasks v R3 List Maintenance Tasks v R3 Internal Tasks See Using Manager for R/3 Configuration Tasks on page 35. Open the R3 Configuration policy region to display the Policy Region: R3 Configuration window: Manager for R/3 Object Endpoints R/3 system and server resource types are listed as available endpoints for tasks and monitors and can be used as subscribers to a profile manager. As endpoints and subscribers, these resource types appear in lists where endpoints are displayed and are to be selected. For example, the new endpoint name is displayed in the Available to Become Subscribers list when looking at the subscribers for a profile manager. The following table describes the icon, resource type, and endpoint name for each R/3 object: 3. Getting Started with Manager for R/3 Endpoint Icon Resource Type Endpoint Name R/3 system R3System SID_DBhostname Example: TV4_hound Tivoli Manager for R/3 User s Guide 29

52 Endpoint Icon Resource Type Endpoint Name R/3 application server R3AppServer hostname_sid_iid Example: hound_tv4_55 R/3 database server R/3 Internet transaction server R3DBServer R3ITSServer hostname_sid_db Example: hound_tv4_db For a single-host R/3 ITS server: hostname_viin_its Example: cedar_d02_its For the AGate component of a dual-host R/3 ITS server: hostname_viin_its-agate Example: elm_tv1_its-agate For the WGate component of a dual-host R/3 ITS server: hostname_viin_its-wgate Example: pine_d01_its-wgate Where: DBhostname Is the host name of the database server. hostname Is the host name of the application server, database server, or Internet transaction server (ITS server). Note: The host name of the ITS server can be the host name of the machine that is running both the AGate and WGate ITS server components (single-host ITS 30 User s Guide Version 2.1

53 SID IID VIIN server) or the host name of the machine that is running the AGate or the WGate component (dual-host ITS server). Is the three-character R/3 system identifier. Is the two-digit R/3 instance number. Is the virtual ITS instance name. If the SAP naming recommendation was followed when the R/3 ITS server was installed, the virtual ITS instance name is the SID of your R/3 system. Manager for R/3 tasks and monitors are designed to be distributed to a particular type of endpoint: managed node or TMA endpoint, R3System, R3AppServer, R3DBServer, or R3ITSServer. When you distribute a monitor or run a task, you must specify the correct type of endpoint. When you run a task from within the Manager for R3 policy region or from the R3 Configuration policy region, the Manager for R/3 lists only the appropriate type of endpoint in the Available Task Endpoints scrolling list on the Execute Task dialog. Configuring Manager for R/3 To configure the Manager for R/3, complete these steps: 1. Assign the Manager for R/3 authorization roles to one or more Tivoli administrators. See Assigning Authorization Roles on page If you are using the Tivoli Enterprise Console (TEC): a. Configure the TEC event server as described in Configuring the TEC Event Server on page 82. b. Create one or more event consoles if you have not already done so. Refer to the TME 10 Enterprise Console Reference Guide. 3. Configure each SAP R/3 system to be managed as described in Configuring Each SAP R/3 System on page Getting Started with Manager for R/3 Tivoli Manager for R/3 User s Guide 31

54 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 server you want to manage as described in Creating R/3 Objects on page Configure the event consoles as described in Configuring an Event Console on page Configure the RFC as described in Configuring a Remote Function Call on page Perform platform-specific configuration as appropriate. See the following: Configuring Manager for R/3 for Windows NT on page 72 Configuring Manager for R/3 for HP-UX 11 on page 75 Configuring Manager for R/3 for OS/390 on page Configure event adapters as described in Configuring Event Adapters on page Optionally, configure for extended database status reporting as described in Extending Database Server Status Reporting on page 78. You must have the Tivoli Manager for DB2 or the Tivoli Manager for Oracle installed to use this feature. 10. Back up the Tivoli database, saving the backup file with a different name than the previous backup file. After creating R/3 system objects, the Manager for R3 policy region contains a policy region icon for each R/3 system as shown in the 32 User s Guide Version 2.1

55 following figure: When R/3 application server, R/3 database server, and R/3 ITS server objects are created for an R/3 system, these objects reside in the appropriate R/3 system policy region. In addition, the R3 Configuration policy region will contain an App Server List profile manager for each R/3 system. Assigning Authorization Roles The Manager for R/3 uses three authorization roles: r3_user, r3_admin, and r3_senior. Each of the Manager for R/3 tasks require one of the Manager for R/3 authorization roles in addition to the basic Tivoli authorization roles of user, admin, or senior. 3. Getting Started with Manager for R/3 The Manager for R/3 tasks that require senior and r3_admin authorities include: Tivoli Manager for R/3 User s Guide 33

56 Tasks in the R3 Configuration Tasks library, except for the Configure Remote Function Call task and the Display Event Adapter Configuration Task The Create New Subscriber List task in the R3 List Maintenance Task library The Configure Remote Function Call task in the R3 Configuration Tasks library requires senior and r3_senior authorities. The Display Event Adapter task in the R3 Configuration Tasks library requires user and r3_user authorities. The r3_admin and r3_senior authorization roles affect only resources in the Manager for R3 and the R3 Configuration policy regions. You can assign the r3_admin and r3_senior authorization roles as global Tivoli roles or as resource roles for the Manager for R3 and the R3 Configuration policy regions. The Manager for R/3 tasks that require at least user and r3_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/3 system policy regions. You can assign the r3_user authorization role as a global Tivoli role or as a resource role for a specific R/3 system policy region. Let s look at an example for assigning authorization roles. Assume that you have three administrators: Senior, Prod, and Support and three R/3 systems: PRD (a production system), QA1 (a test system), and QA2 (a test system). You might assign Tivoli authorization roles to each administrator based on responsibilities as described in the following table: 34 User s Guide Version 2.1

57 Administrator Responsibilities Manager for R/3 Authorization Roles Senior Manage all R/3 systems Global r3_user, r3_admin, and r3_senior Prod Support Manage the production system and backup to the Support administrator Manage all test systems Global r3_user r3_admin resource role for the PRD policy region r3_user resource role for the QA1 policy region r3_user resource role for the QA2 policy region Using Manager for R/3 Configuration Tasks Manager for R/3 provides the following task libraries in the R3 Configuration policy region that contain tasks to help you configure Manager for R/3: R3 Configuration Tasks on page 36 R3 List Maintenance Tasks on page 38 Note: Manager for R/3 also contains an R3 Internal Tasks library in the R3 Configuration policy subregion. The tasks in this library support internal processing of Manager for R/3 functions and are not intended to be run by Tivoli administrators. Jobs are also provided for some tasks in the R3 Configuration Tasks and R3 List Maintenance Tasks libraries. A job is a task with the endpoint and other parameters already defined. Jobs provided for the tasks in the R3 Configuration Tasks and R3 List Maintenance Tasks libraries are set up to execute against the TMR server or TEC event server, as appropriate. 3. Getting Started with Manager for R/3 To locate the configuration tasks, follow these steps: Tivoli Manager for R/3 User s Guide 35

58 1. From the Manager for R3 policy region, open the R3 Configuration policy region icon to display the Policy Region: R3 Configuration window. 2. From the R3 Configuration policy region, do one of the following: Open the R3 Configuration Tasks library to display the configuration tasks and jobs. Open the R3 List Maintenance Tasks library to display the Create New Subscriber List task and job. R3 Configuration Tasks The R3 Configuration Tasks library contains the following tasks to help you configure the Manager for R/3: Tasks Role Target Configure Autodiscovery for NT. See Creating R/3 Objects Using Automatic Discovery on page 55. Configure Autodiscovery for UNIX. See Creating R/3 Objects Using Automatic Discovery on page 55. Configure Client Install. See Creating SAPGUI Software File Packages on page 139. Configure Event Adapter. See Configuring Event Adapters on page 86. Configure Event Console. See Configuring an Event Console on page 83. Configure Event Server. See Configuring the TEC Event Server on page 82. Configure Monitor Logging Mode. See Configuring Monitor Logging Mode on page 272. r3_admin r3_admin r3_admin r3_admin r3_admin r3_admin r3_admin Windows NT managed node or TMA endpoint UNIX managed node or TMA endpoint TMR server R3AppServer TEC event server TEC event server TMR server 36 User s Guide Version 2.1

59 Tasks Role Target Configure Remote Function Call. See Configuring a Remote Function Call on page 71. r3_senior R3System Configure SAPGUI Package. See Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later on page 143. Configure UNIX Client Install. See Creating SAPGUI Software File Packages on page 139. Configure Windows 95/98 Client Install. See Creating SAPGUI Software File Packages on page 139. Configure Windows NT Client Install. See Creating SAPGUI Software File Packages on page 139. Create RDBMS Manager Status Monitor. See Extending Database Server Status Reporting on page 78. Display Event Adapter Configuration. See Displaying Event Adapter Information on page 87. List Available SAPGUI Packages. See Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later on page 143. List SAPGUI Package Features. See Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later on page 143. r3_admin r3_admin r3_admin r3_admin r3_admin r3_user r3_admin r3_admin Managed node that is the R/3 SAPGUI installation server TMR server TMR server TMR server TMR server R3AppServer Managed node that is the R/3 SAPGUI installation server Managed node that is the R/3 SAPGUI installation server 3. Getting Started with Manager for R/3 Tivoli Manager for R/3 User s Guide 37

60 Tasks Role Target Remove Autodiscovery for NT. See Creating R/3 Objects Using Automatic Discovery on page 55. Remove Autodiscovery for UNIX. See Creating R/3 Objects Using Automatic Discovery on page 55. Send GEM Heartbeat. See Synchronizing the Tivoli GEM Console with the Desktop on page 154. r3_admin r3_admin r3_admin Windows NT managed node or TMA endpoint UNIX managed node or TMA endpoint R3System, R3AppServer, R3DBServer, or R3ITSServer R3 List Maintenance Tasks The R3 List Maintenance Tasks library contains the following task: Tasks Role Target Create New Subscriber List. See Creating Subscriber Lists on page 70. r3_admin TMR server Determining R/3 Application Server Status The R/3 application server icon reflects the status of the application server as follows: Icon State Description An application server icon displayed without a status indicator in the lower right corner indicates that the R/3 application server is up and is accepting R/3 logons. An application server icon with a yellow triangle containing an exclamation mark (!) in the lower right corner indicates that the R/3 application server is up but is not accepting R/3 logons. An application server icon with a yellow diamond containing a question mark (?) in the lower right corner indicates that the status of the R/3 application server is unknown. 38 User s Guide Version 2.1

61 Icon State Description An application icon with a red circle containing a minus sign ( ) in the lower right corner indicates that the R/3 application server is down. To ensure that an R/3 application server reflects its current status, you must manually distribute the R3 Server Autodiscovery Monitors profile, which is contained in the R3 App Server Monitors profile manager. The R3 Server Autodiscovery Monitors profile contains the Application Server Status monitor, which reports the status of the application server to which the profile is distributed. See R3 App Server Monitors Profile Manager on page 110. Determining R/3 Database Server Status The R/3 database server icon reflects the status of the database server as follows: Icon State Description A database server icon displayed without a status indicator in the lower right corner indicates that the R/3 database server is up. A database server icon with a yellow diamond containing a question mark (?) in the lower right corner indicates that the status of the R/3 database server is unknown. A database server icon with a red circle containing a minus sign ( ) in the lower right corner indicates that the R/3 database server is down. Down status is reported only if you are using Tivoli Manager for DB2 or Tivoli Manager for Oracle to extend database status reporting. 3. Getting Started with Manager for R/3 Manager for R/3 sets the status of the database server using the following methods: From the status of the R/3 application servers When the status of one R/3 application server is up, the status of the database server is reported as up. When the status of all R/3 Tivoli Manager for R/3 User s Guide 39

62 application servers in the R/3 system is unknown or down, the status of the database server is reported as unknown. Optionally, from the status of the database server as reported by the Tivoli Manager for DB2 or Tivoli Manager for Oracle If you have Tivoli Manager for DB2 or Tivoli Manager for Oracle installed, you can extend database server status reporting. See Extending Database Server Status Reporting on page 78. Manager for R/3 sets the status of the database server based on a Tivoli Manager for DB2 or Tivoli Manager for Oracle database server status event. The database server status event can report up or down status. Because there are potentially two methods by which Manager for R/3 sets database server status, Manager for R/3 reflects the last status that is reported. If you shut down an R/3 system, the R/3 application servers shut down first. This results in changing the database server status to unknown even if the R/3 system has not completely shut down. When the database server shuts down and then comes back up, the Tivoli Manager for DB2 or Tivoli Manager for 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 Monitors profile to each application server. See R3 App Server Monitors Profile Manager on page 110. Determining R/3 ITS Server Status The R/3 ITS server icon reflects the status of the R/3 ITS server as follows: Icon State Description An R/3 ITS server icon displayed without a status indicator in the lower right corner indicates that the status of the function represented by the icon is up. 40 User s Guide Version 2.1

63 Icon State Description An R/3 ITS server with a yellow diamond containing a question mark (?) in the lower right corner indicates that the status of the function represented by the icon is unknown. An R/3 ITS server icon with a red circle containing a minus sign ( ) in the lower right corner indicates that the status of the function represented by the icon is down. To ensure that an R/3 ITS server or R/3 ITS server component reflects its current status, you must configure and distribute the ITS Server Status monitor to each R/3 ITS server object. Use the R3 ITS Server Monitors profile, which is contained in the R3 ITS Monitors profile manager to distribute this monitor to each R/3 ITS server object. See R3 ITS Server Monitors on page Getting Started with Manager for R/3 Tivoli Manager for R/3 User s Guide 41

64 42 User s Guide Version 2.1

65 4 Configuring Each SAP R/3 System 4. Configuring Each SAP R/3 System After installing Manager for R/3, configure each SAP R/3 system that is to be managed so that Manager for R/3 can communicate with that system. The following procedures must be performed to enable this communication. These modifications will not adversely affect your R/3 installation. The configuration process requires the following: Moving R/3 Transports into an R/3 Landscape on page 44 Importing the Function Modules on page 47 Configuring User IDs for RFC Interface Access on page 49 Configuring R/3 Application Server Profiles on page 50 Note: Some of the R/3 tasks require that the operating system level sidadm R/3 logon be used. Tivoli Manager for R/3 User s Guide 43

66 Moving R/3 Transports into an R/3 Landscape Manager for R/3 provides several sets of transports. These transports contain the following objects: Base Transport OS/390 Extension (This transport must be installed after the Base transport.) Objects Development Class J8C1 Function Group J8C1 Function Group J8C2 Function Group J8C4 Function Group J8C5 Function Group J8C6 Function Group J8C8 Structure J_8C1_ALE1 Structure J_8C1_ALE2 Structure J_8C1_ALE3 Structure J_8C1_ALE4 Structure J_8C1_ALE5 Structure J_8C1_ALE6 Structure J_8C1_TIV1 Structure J_8C1_TIV2 Structure J_8C1_TIV3 Data Element J_8C1_C180 Function Group J8C3 Note: Refer to the Tivoli Manager for R/3 Release Notes for specific transport file names. You must move the transports to the transport directory in each R/3 landscape. To move the transports into an R/3 landscape, use one of the following methods: 44 User s Guide Version 2.1

67 Distribute the R3 ABAP file package. Software Distribution must be installed on the TMR server to use this method. Copy the transport files from the TMR server to the transport directory. Distributing the R/3 ABAP File Package To distribute the R3 ABAP file package to the appropriate R/3 application server directories, follow these steps: 1. From the Manager for R3 policy region, open the R3 Transports profile manager icon to display the Profile Manager window. 2. If you are distributing the R3 ABAP file package to TMA endpoints, follow these steps to change the R3 Transports profile manager from database mode to dataless mode: a. In the Profile Manager window, from the Edit menu, select Profile Manager to display the Edit Profile Manager dialog. b. Select Dataless Endpoint Mode. 4. Configuring Each SAP R/3 System Note: Refer to the TME 10 Framework User s Guide for more information about database mode and dataless mode profile managers. c. Click Change & Close. 3. Subscribe the appropriate managed nodes or TMA endpoints to the R3 Transports profile manager. In the Profile Manager window, from the Profile Manager menu, select Subscribers to display the Subscribers dialog. 4. Complete the Subscribers dialog, referring to the online help if you need additional information. 5. For UNIX, go to the next step. For Windows NT, edit the file package properties to modify the destination directory path. Follow these steps: a. Right-click the R3 ABAP FilePackage icon and select Properties to display the File Package Properties dialog. Tivoli Manager for R/3 User s Guide 45

68 b. From the Edit menu, select Platform-Specific Options > Windows NT Options to display the File Package Windows NT Options dialog. c. Change the destination directory path so that the ABAP file package is distributed to driveletter:/trans/, where driveletter maps to \\SAPGLOBALHOST\sapmnt. SAPGLOBALHOST represents the host name of the central instance. 6. Distribute the transports. From the Profile Manager window, right-click the R3 ABAP FilePackage icon and select Distribute from the pop-up menu to display the Distribute File Package dialog. 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 package will be distributed is as follows: UNIX: /usr/sap/trans Windows NT: driveletter:/trans/. The distribution process automatically sets the ownership of the files to the sapsys group. Copying the Transports To copy the transport files from the TMR server to the appropriate R/3 application server directories, follow these steps: 1. Locate the transport files in the cofiles and data subdirectories in the $BINDIR/../generic_unix/TME/SAP/2.2C/abap directory on the TMR server. 2. Copy the transport files to the application server that will be used to 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. 46 User s Guide Version 2.1

69 Ensure that the files are owned by the sapsys group. Importing the Function Modules Use one of the following methods to import the function modules: From the Command Line. Using the Transport Management System on page 48. This method applies to R/3 versions 4.0B and later only. From the Command Line To import the function modules from the command line, follow these steps: 1. Log on to the R/3 System s Central Instance as the R/3 administrator (sidadm) and change to the /usr/sap/trans/bin directory. 4. Configuring Each SAP R/3 System Note: The transport and correction system must be already configured and functioning. 2. Show the current contents of the transport buffer. Enter the following 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 for specific transport file names. 4. Verify the transport has been placed in the buffer. Enter the following command: tp showbuffer sid 5. Import the transport. Enter the following command: tp import TV1Kxxxxxx sid [u4] Tivoli Manager for R/3 User s Guide 47

70 Note: For R/3 releases prior to 4.0A, the u4 option should be specified. Starting with R/3 release 4.0A, the u4 option is no longer supported by SAP. 6. Verify the import. To do this, log into the R/3 Developer WorkBench and check the objects listed in the table in Moving R/3 Transports into an R/3 Landscape on page 44. If objects are not active, activate the objects. Note: An R/3 developer key is required to activate the objects. Using the Transport Management System For R/3 versions 4.0B and later, you can use the Transport Management System (TMS) to transport the function modules. To do this, 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 from the Transport menu, select Transport Management System. Note: The target system must be properly defined within a transport 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 the following: Double-click the target system. Select the target system and then from the Import Queue menu, select Display. The Import Queue screen is displayed. 4. Add the transport to the buffer. If the buffer already exists, go to the next step. If the buffer does not exist, do the following: 48 User s Guide Version 2.1

71 a. From the Extras menu, select Other requests > Add to display the Add Transport Request to Import Queue dialog. b. In the Transp. request field, enter the transport name that you want to add, such as TV1Kxxxxxx. Then, click the green check and click Yes on the confirmation dialog. Note: Refer to the Tivoli Manager for R/3 Release Notes for specific 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 Import Transport Request dialog. b. In the Target client field, select the target client from the drop-down list. c. Click the green check and click Yes on the confirmation dialog. 6. Verify the import. From the Request menu, select Display > Logs to display the Overview of transport logs window. If objects are not active, activate the objects. 4. Configuring Each SAP R/3 System Note: An R/3 developer key is required to activate the objects. Configuring User IDs for RFC Interface Access An R/3 user ID must be used to access the RFC interface. An existing user ID can be used, or a new one can be created. It is recommended that the user ID be a CPIC-only user. The user ID needs a set of authorizations to run the required function modules in the R/3 system. Required authorizations are available in the R/3 authorization profiles S_A.ADMIN and S_A.SYSTEM. Either one of these authorization profiles can be used for the user ID. Tivoli Manager for R/3 User s Guide 49

72 If you want to assign a more restrictive set of authorizations to the user ID, copy either the S_A.ADMIN or the S_A.SYSTEM authorization profile and remove all authorizations except the following: S_RZL_ALL S_BTCH_ALL S_ADMI_ALL S_RFC_ALL If you want to create the most restrictive authorization profiles, refer to Function Module Authorization on page 223 for information on the authorizations required by each Manager for R/3 function module. Note: Starting with R/3 3.1G, R/3 provides enhanced security control for the RFC interface. RFC security checking is enabled on a per R/3 application server basis. It is set in the instance profile by specifying auth/rfc_authority_check=1. For R/3 3.1G through 3.1I, the default is to not enable RFC security. For R/3 4.0A and later, the default is to enable RFC security. Configuring R/3 Application Server Profiles The R/3 application server instance profiles contain many customization settings for the R/3 application server. One of the configuration options you can set is the allocation of shared memory segments to shared memory pools. Manager for R/3 requires that segment key 13 be assigned to shared memory pool 10. This is the default allocation for R/3. This assignment is necessary to support proper functioning of the Alert Event Adapter and the automatic discovery function. You can check the allocation of segment key 13 by examining the R/3 application server instance profile. The instance profile can be displayed and maintained using transaction RZ10. The parameter 50 User s Guide Version 2.1

73 ipc/shm_psize_13 controls the pool allocation for segment key 13. This parameter must have a value of -10 to ensure that it is allocated to shared memory pool Configuring Each SAP R/3 System Tivoli Manager for R/3 User s Guide 51

74 52 User s Guide Version 2.1

75 5 Configuring Manager for R/3 This chapter describes how to create Tivoli objects for the R/3 systems, application servers, database servers, and Internet transaction servers (ITS servers) that you want to manage with Manager for R/3. This chapter also describes how to configure a remote function call (RFC), platform-specific configuration tasks, and how to extend R/3 database server status. Creating R/3 Objects To manage your R/3 environment with Manager for R/3, you must configure Tivoli for each R/3 system, R/3 application server, R/3 database server, and R/3 ITS server component that you want to manage. To do this, you must create an object for each R/3 system and server to be managed. You can create R/3 objects in the following ways: Use the automatic discovery function. See Creating R/3 Objects Using Automatic Discovery on page 55. From the desktop. You must create R/3 ITS server objects and R/3 database server objects, if the R/3 database server is not running on the same machine as an R/3 application server, using this method. See Creating an R/3 Object from the Desktop on page 60. Notes: 1. To ensure that an R/3 application server reflects its current status, you must manually distribute the R3 Server Autodiscovery 5. Configuring Manager for R/3 Tivoli Manager for R/3 User s Guide 53

76 Monitors profile, which is contained in the R3 App Server Monitors profile manager. The R3 Server Autodiscovery Monitors profile contains the Application Server Status monitor, which reports the status of the application server to which the profile is distributed. See R3 App Server Monitors Profile Manager on page Because the status of an R/3 database server is based on the status of the R/3 application servers, to ensure that an R/3 database server reflects its current status, you must manually distribute the Application Server Status monitor to the R/3 application servers. See R3 App Server Monitors Profile Manager on page 110. If you have the Tivoli Manager for DB2 or the Tivoli Manager for Oracle installed, you can extend the database status reporting. See Extending Database Server Status Reporting on page To ensure that an R/3 ITS server reflects its current status, you must configure and distribute the ITS Server Status monitor to each R/3 ITS server that you want to manage. For more information, see R3 ITS Server Monitors on page 106. Deciding Where to Create R/3 Objects This section provides information to help you decide where to create R/3 server objects in a TMA environment. R/3 system objects are created on the TMR server; they cannot be created elsewhere. R/3 server objects for R/3 servers that reside on managed nodes are created on the corresponding managed nodes; they cannot be created elsewhere. R/3 server objects for R/3 servers that reside on TMA endpoints, by default, are created on the managed node that hosts the TMA endpoint s current gateway. However, you can create the R/3 server objects for TMA endpoints on any managed node that you specify. If you create R/3 server objects for TMA endpoints on the default managed node, the R/3 server objects might be distributed across multiple managed nodes. If you are concerned about distributed R/3 server objects, you can adopt a consolidated approach by creating these R/3 server objects on the TMR server or on a high availability 54 User s Guide Version 2.1

77 managed node. With this approach, you can take steps to ensure that this managed node has the proper backup and recovery plans in case of failure. Manager for R/3 objects cannot be moved after the objects are created. If the managed node hosting a TMA endpoint s gateway fails, you will need to take recovery action. If possible, restore the managed node from a backup. If you cannot restore the managed node, you must delete the R/3 server objects for the affected TMA endpoints and then recreate the R/3 server objects on another managed node. Creating R/3 Objects Using Automatic Discovery The automatic discovery function checks for running R/3 application servers. For each application server found, the automatic discovery function creates an R3AppServer object and an R3System object, if they do not already exist. In addition, the automatic discovery function creates an R3DBServer object if an application server is running on the same machine as the database server. Notes: 1. If the application server is not running on the same machine as the database server, you can create the R3DBServer object manually. See Creating an R/3 Object from the Desktop on page The automatic discovery function does not find and create objects for each R/3 ITS server. You must create the R3ITSServer objects manually. See Creating an R/3 Object from the Desktop on page Configuring Manager for R/3 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 automatic discovery as described in Scheduling Automatic Discovery on page 57. Scheduling Automatic Discovery on page 57 describes how to schedule automatic discovery for both Windows NT and UNIX. Tivoli Manager for R/3 User s Guide 55

78 Configuring Automatic Discovery for Data Sharing When Manager for R/3 creates the R/3 application server objects within an R/3 system policy region, Manager for R/3 assigns the name of the policy region as SID_DBHostname. The values for SID and DBHostname are obtained from the R/3 application servers when they are discovered. In a data sharing environment, the R/3 application servers can report different database host names even though the R/3 application servers are in the same R/3 system. This is particularly true for OS/390. (For more information, see Data Sharing on page 77). For a data sharing environment, you can override the default processing of the automatic discovery function to force the R/3 application servers into an R/3 policy region named with the database host name of your choice. You do this by specifying the database host name for each R/3 system in the sap_discovery.cfg configuration file. The automatic discovery function uses the database host names specified in the sap_discovery.cfg configuration file when it creates the R/3 policy regions. A sample sap_discovery.cfg file is provided in the $BINDIR/../generic_unix/TME/SAP/sh directory on the TMR server. The format of the sap_discovery.cfg file is as follows: SID database_hostname Where SID is the three-character R/3 system identifier, and database_hostname is the host name of the database server that automatic discovery uses when it creates the R/3 system. To configure automatic discovery for data sharing, follow these steps: 1. Edit the $BINDIR/../generic_unix/TME/SAP/sh/sap_discovery.cfg file on the TMR server to specify the appropriate SIDs and the corresponding database host names. You can specify any or all of your SIDs, entering each SID and database host name on a separate line. The database host name should be no longer than eight alphanumeric characters. Use one or more spaces to separate the SID from the database host name. You can also add comments by placing a pound sign (#) in the first column of a 56 User s Guide Version 2.1

79 line. To specify the database host names for R/3 systems TV1 and TV4, you would edit the sap_discovery.cfg file as follows: TV1 puli TV4 hound 2. Distribute the sap_discovery.cfg file to each managed node and TMA endpoint on which you plan to run automatic discovery. You can use the file transfer protocol (FTP) or Tivoli Software Distribution to distribute the file. The sap_discovery.cfg file must reside in one of the following directories: Managed node: $BINDIR/../generic_unix/TME/SAP/sh TMA endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP/sh Note: The $LCF_BINDIR/../../generic_unix/TME/SAP/sh directory does not exist prior to running a Manager for R/3 task on the TMA endpoint. If you plan to use FTP to distribute the sap_discovery.cfg file prior to running automatic discovery, you must manually create the $LCF_BINDIR/../../generic_unix/TME/SAP/sh directory. If you plan to use Software Distribution to distribute the sap_discovery.cfg file, you do not need to create this directory. Software Distribution automatically creates this directory. 5. Configuring Manager for R/3 Scheduling Automatic Discovery To schedule the automatic discovery function to automatically discover your R/3 systems and servers and create R/3 objects, run one 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 a dialog in which you specify the interval at which to run the automatic discovery function. You can schedule automatic discovery to run one time immediately, or you can schedule automatic discovery to run later. The automatic discovery function runs at the Tivoli Manager for R/3 User s Guide 57

80 specified time and populates the desktop with the R/3 objects that are discovered. The time you specify refers to the time on the machine where the Configure Autodiscovery task is to be run. Also, for servers that are running on TMA endpoints, you can force automatic discovery to create the R/3 objects on any managed node rather than on the one hosting the current gateway. Notes: 1. In the Execute Task dialog, specify only Windows NT managed nodes or Windows NT TMA endpoints for the Configure Autodiscovery for NT task. Specify only UNIX managed nodes or UNIX TMA endpoints for the Configure Autodiscovery for UNIX task. 2. In the Execute Task dialog, specify Serial in the Execution Mode field 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 to change the scheduling interval, automatic discovery runs at the currently scheduled time and previously scheduled times are deleted. If your R/3 topology does not change, you might want to stop automatic discovery after your R/3 resources have been discovered. See Stopping Automatic Discovery on page 60. Scheduling Automatic Discovery for NT To schedule automatic discovery for Windows NT, run the Configure Autodiscovery for NT task. The Configure Autodiscovery for NT 58 User s Guide Version 2.1

81 dialog is displayed: To run automatic discovery one time immediately (automatic discovery will run within two minutes), leave all dialog fields empty. To schedule automatic discovery to run once at a specific time, enter a value in the Minute and Hour fields only. For more information about completing the dialog, refer to the online help. Scheduling Automatic Discovery for UNIX To schedule automatic discovery for UNIX, run the Configure Autodiscovery for UNIX task. The Configure Autodiscovery for UNIX dialog is displayed: 5. Configuring Manager for R/3 Tivoli Manager for R/3 User s Guide 59

82 To run automatic discovery one time immediately, leave all dialog fields empty. To schedule automatic discovery to run every day at a specific time, enter a value in the Minute and Hour fields only. For more information about completing the dialog, refer to the online help. Stopping Automatic Discovery To stop automatic discovery, run one of the following tasks in the R3 Configuration Tasks library: Remove Autodiscovery for NT Remove Autodiscovery for UNIX Run the task against the same endpoints on which you ran the Configure Autodiscovery task. Creating an R/3 Object from the Desktop This section describes how to create an R/3 system object, an R/3 application server object, an R/3 database server object, and an R/3 ITS server object from the desktop. For servers that are running on TMA endpoints, Manager for R/3 creates the R/3 object on the managed node hosting the current gateway. However, you can force the creation of the R/3 server object to be on any managed node by specifying the name of the managed node when you create the R/3 server object. You must create the R/3 system object before you can create a server object. Creating an R/3 System Object from the Desktop To create an R/3 system object from the desktop, from the Create menu from the Manager for R/3 Policy Region window, select 60 User s Guide Version 2.1

83 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 for R3 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/3 Database Hostname field. 5. Configuring Manager for R/3 Note: If your R/3 system resides on an OS/390 database host using data sharing, see Data Sharing on page 77 for more information about R/3 system policy region naming considerations. Creating an Application Server Object from the Desktop To create an R/3 application server object from the desktop, follow these steps: 1. From the Manager for R3 Policy Region window, open the appropriate R/3 system policy region to display the Policy Region window for the selected R/3 system. Tivoli Manager for R/3 User s Guide 61

84 2. From the Create menu, select R3AppServer to display the Create R/3 Application Server dialog. For information about completing the dialog, refer to the online help. This task creates an icon for the application server in the appropriate R/3 system policy region. Creating a Database Server Object from the Desktop To create an R/3 database server object from the desktop, follow these steps: 1. From the Manager for R3 Policy Region window, open the appropriate R/3 system policy region to display the Policy Region window for the selected R/3 system. 2. From the Create menu, select R3DBServer to display the Create R/3 Database Server dialog. For information about completing the dialog, refer to the online help. 62 User s Guide Version 2.1

85 This task creates an icon for the database server in the appropriate R/3 system policy region. Creating an ITS Server Object from the Desktop To create an R/3 ITS server object from the desktop, follow these steps. 1. From the Manager for R3 Policy Region window, open the appropriate R/3 system policy region to display the Policy Region window for the selected R/3 system. 2. From the Create menu, select R3ITSServer to display the Create R/3 ITS Server dialog. 5. Configuring Manager for R/3 You can create an R/3 ITS server that represents any of the following: A single-host R/3 ITS server (both the AGate and the WGate components run on the same machine) An individual component (AGate or WGate) of a dual-host R/3 ITS server (the AGate and the WGate components run on different machines) For information about completing the dialog, refer to the online help. This task creates an icon for the R/3 ITS server in the appropriate R/3 system policy region. Tivoli Manager for R/3 User s Guide 63

86 Results of Creating R/3 Objects This section describes the results of creating an R/3 system, an R/3 application server, an R/3 database server, and an R/3 ITS server object. Result of Creating an R/3 System Object When you create an R/3 system object, the following occurs: An icon for the R/3 system policy region is created in the Manager for R3 policy region. v v The icon represents an R3System resource type that can be used as the target when running tasks. See Manager for R/3 Object Endpoints on page 29. The icon has a pop-up menu that enables you to perform common tasks. If you execute a task from the pop-up menu on the R/3 system icon, the task executes on that R/3 system. The following table describes the tasks that are available from the pop-up menu: Task Open Properties Start R/3 System Description Opens the R/3 policy region. This is the default action. Displays the properties of this R/3 system, including the SID, R/3 release, database host name, database type and database release. See R3 System Tasks on page 131. Stop R/3 System The R/3 system is subscribed to the R3 System List profile manager. An App Server List profile manager is created in the R3 Configuration policy region. The App Server List profile manager is subscribed to the R3 App Server Monitors profile manager. 64 User s Guide Version 2.1

87 If Tivoli GEM instrumentation is installed, the object is added to the Tivoli GEM server database and an icon is created on the Tivoli GEM console. See Tivoli GEM Instrumentation on page 147. Result of Creating an R/3 Application Server Object When you create an R/3 application server object, the following occurs: An icon for the R/3 application server is created in the appropriate R/3 system policy subregion. v v The icon represents an R3AppServer resource type that can be used as the target when running tasks and monitors. See Manager for R/3 Object Endpoints on page 29. The icon has a pop-up menu that enables you to perform common tasks. If you execute a task from the pop-up menu on the R/3 application server icon, the task executes on that R/3 application server. The following table describes the tasks that are available from the pop-up menu: Task Description Open Displays the profiles that have been distributed to this R/3 application server. Properties Displays the properties of the R/3 application server including host name, the instance ID, the R/3 system name, and the state of the R/3 application server. This is the default action. Start SAPGUI Runs the SAPGUI from the R/3 application server to your desktop. On Windows NT, you must run this task from the same machine on which the R/3 application server is running. 5. Configuring Manager for R/3 Tivoli Manager for R/3 User s Guide 65

88 Task Start Application Server Description See R3 App Server Tasks on page 132. 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 The R3AppServer object is subscribed to the App Server List profile manager for the appropriate R/3 system. If Tivoli GEM instrumentation is installed, the object is added to the Tivoli GEM server database and an icon is created on the Tivoli GEM console. See Tivoli GEM Instrumentation on page 147. Result of Creating an R/3 Database Server Object When you create an R/3 database server object, the following occurs: An icon for the database server is created in the appropriate R/3 system policy subregion. v v The icon represents an R3DBServer resource type that can be used as the target when running tasks. See Manager for R/3 Object Endpoints on page 29. The icon has a pop-up menu that enables you to perform common tasks. If you execute a task from the pop-up menu on the R/3 database server icon, the task executes on that R/3 database server. The following table describes the tasks that are available from the pop-up menu: 66 User s Guide Version 2.1

89 Open Properties Task Start R/3 Database Server Stop R/3 Database Server Description Displays the profiles that have been distributed to this R/3 database server. Displays the properties of the database server including host name, database type, release, R/3 system, Manager for DB2 or Manager for Oracle object name, and state. This is the default action. See R3 DB Server Tasks on page 136. If Tivoli GEM instrumentation is installed, the object is added to the Tivoli GEM server database and an icon is created on the Tivoli GEM console. See Tivoli GEM Instrumentation on page 147. Result of Creating an R/3 ITS Server Object When 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/3 system policy subregion. v v The icon represents an R3ITSServer resource type that can be used as a subscriber for profile managers. See Manager for R/3 Object Endpoints on page 29. The icon has a pop-up menu that enables you to perform common tasks. If you execute a task from the pop-up menu on the R/3 ITS server icon, the task executes on that R/3 ITS server. The following table describes the tasks that are available from the pop-up menu: 5. Configuring Manager for R/3 Open Properties Task Description Displays the profiles that have been distributed to this R/3 ITS server. Displays the properties of the R/3 ITS server including the ITS server name, host name, R/3 system name, and status. This is the default action. Tivoli Manager for R/3 User s Guide 67

90 Task Start ITS Server Description See R3 ITS Server Tasks on page 137. Stop ITS Server The R3ITSServer object is subscribed to the R3 ITS Monitors profile manager. If Tivoli GEM instrumentation is installed, the object is added to the Tivoli GEM server database and an icon is created on the Tivoli GEM console. See Tivoli GEM Instrumentation on page 147. Deleting an R/3 Object Deleting an R/3 system, an R/3 application server, an R/3 database server, and an R/3 ITS server object does not affect the R/3 system or the server but removes the information about it that is stored in the Tivoli database. Before you can delete an R/3 system object, you must delete all server objects in that R/3 system policy region. To delete an R/3 object, follow these steps: 1. Stop all Application Server Status and ITS Server Status monitors in the appropriate R/3 system policy region. Attention: Deleting R/3 objects while status monitors are running against objects in an R/3 system can potentially corrupt the Tivoli database. For more information about this problem, refer to information about deleting R/3 objects 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 to delete and select the appropriate R/3 system, R/3 application server, R/3 database server, or R/3 ITS server icon. 3. From the Edit menu, select Delete to remove the selected object from the policy region. 4. Restart Application Server Status and ITS Server Status monitors as appropriate. 68 User s Guide Version 2.1

91 Result of Deleting an R/3 System Object When you delete an R/3 system object, the following occurs: The icon for the R/3 system is removed from the desktop. The R3System object is unsubscribed from all profile managers. The App Server List profile manager is removed. If Tivoli GEM instrumentation is installed, the object is deleted from the Tivoli GEM server database, and the icon is removed from the Tivoli GEM console. Result of Deleting an R/3 Application Server Object When you delete an R/3 application server object, the following occurs: The icon for the R/3 application server is removed from the desktop. The R3AppServer object is unsubscribed from all profile managers. Manager for R/3 event adapters are stopped, Windows NT services are removed, and the files associated with the event adapters are removed. If Tivoli GEM instrumentation for Manager for R/3 is installed, the object is deleted from the Tivoli GEM server database, and the icon is removed from the Tivoli GEM console. Result of Deleting an R/3 Database Server Object When you delete an R/3 database server object, the following occurs: The icon for the R/3 database server is removed from the desktop. The R3DBServer object is unsubscribed from all profile managers. If Tivoli GEM instrumentation for Manager for R/3 is installed, the object is deleted from the Tivoli GEM server database, and the icon is removed from the Tivoli GEM console. 5. Configuring Manager for R/3 Tivoli Manager for R/3 User s Guide 69

92 Result of Deleting an R/3 ITS Server Object When 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 profile managers. If Tivoli GEM instrumentation for Manager for R/3 is installed, the object is deleted from the Tivoli GEM server database, and the icon is removed from the Tivoli GEM console. Creating Subscriber Lists Manager for R/3 automatically creates the following lists in the R3 Configuration policy subregion: R3 System List, to which all R/3 system objects that have been defined to Manager for R/3 are subscribed. An application server list for each R/3 system labeled SID_DBhostname App Server List, to which all application server objects for the specified R/3 system that have been defined to Manager for R/3 are subscribed. These lists are subscriber-only profile managers and are updated automatically as resources are defined to Manager for R/3, whether by discovery or when you manually create R/3 system and R/3 application server objects. You can use these lists as target endpoints when you run tasks and monitors. All application server lists are automatically subscribed to the R3 App Server Monitors profile manager. See R3 App Server Monitors Profile Manager on page 110. You can also create your own subscriber lists. For example, you might want to create a list of all application servers across all R/3 systems in your environment. To create a new subscriber list, run the Create New Subscriber List job in the R3 List Maintenance Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) The Create New Subscriber List dialog is displayed in which you enter the name of the new subscriber list. 70 User s Guide Version 2.1

93 Configuring a Remote Function Call Manager for R/3 must connect to each managed R/3 system using the R/3 remote function call (RFC) to run certain tasks and monitors. The user ID that is used for this access was defined when the R/3 administrator configured the R/3 system. (See Configuring User IDs for RFC Interface Access on page 49). To use the RFC interface for a particular R/3 system, you must configure the RFC for that system in Tivoli. The Syslog Event Adapter and the IDOC Event Adapter use this configuration information. If you reconfigure an RFC, you must do the following: Rerun the Configure Event Adapter task for the appropriate Syslog Event Adapter or IDOC Event Adapter and then stop and start the event adapter to update the RFC configuration information. See Configuring Event Adapters on page 86. Redistribute the monitoring profiles to all R/3 application servers in the affected R/3 systems. To configure an R/3 RFC for each R/3 system, run the Configure Remote Function Call task in the R3 Configuration Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) This task displays the Configure Remote Function Call dialog. 5. Configuring Manager for R/3 For information about completing this dialog, refer to the online help. Tivoli Manager for R/3 User s Guide 71

94 Configuring Manager for R/3 for Windows NT This section describes how to configure Manager for R/3 if you are running R/3 in a Windows NT environment. Creating Exit Routines for Windows NT The start and stop database tasks for Windows NT rely on database-specific commands to fully implement their processing. Manager for R/3 does not provide these commands. Instead, Manager for R/3 provides database start and stop tasks that call user-supplied exit routines to start and stop the database. For start processing, you must create an exit routine called sap_start_db_exit.sh. The start exit routine must issue an appropriate command to start the database. For stop processing, you must create an exit routine called sap_stop_db_exit.sh. The stop exit routine must issue an appropriate command to stop the database. One copy of the exit routines is used for all R/3 database servers on the node. Both exit routines are expected to be in one of the following directories: Managed node: $BINDIR/../generic_unix/TME/SAP TMA endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP The Manager for R/3 database start and stop tasks pass two positional parameters to the exit routines: database type and the R/3 SID. Both parameters are character format. The routines should exit by writing a numeric return code to standard output. A return code of zero indicates successful completion. A non-zero return code indicates unsuccessful completion. Example of a Start Exit Routine for an Oracle Database The following is an example of a start exit routine for an Oracle database: #!/bin/sh echo 'Starting Service' E:/orant/Bin/oradim80.exe -STARTUP -SID $2 -STARTTYPE srvc echo 'Sleeping' sleep User s Guide Version 2.1

95 echo 'Starting Instance' E:/orant/Bin/oradim80 -STARTUP -SID $2 -STARTTYPE inst -USRPWD \ -PFILE E:\\orant\\Database\\init"$2".ora exit 0 Example of a Stop Exit Routine for an Oracle Database The following is an example of a stop exit routine for an Oracle database: #!/bin/sh echo 'Stopping Instance' E:/orant/Bin/oradim80.exe -SHUTDOWN -SID $2 -USRPWD -SHUTTYPE \ inst -SHUTMODE n & echo 'Sleeping' sleep 10 echo 'Stopping Service' E:/orant/Bin/oradim80.exe -SHUTDOWN -SID $2 -SHUTTYPE srvc exit 0 Enabling the Local Administrator for SAP File Access Manager for R/3 tasks that start and stop R/3 servers rely on SAP-provided programs in the SAP-provided directories. Access to these directories is controlled by membership in the SAP_<sid>_LocalAdmin group. 5. Configuring Manager for R/3 Manager for R/3 tasks are run as Administrator in a Windows NT environment. In a Windows NT domain, Administrator maps to each Windows NT local Administrator. To enable the Manager for R/3 tasks to run with the correct permissions, you must configure the local Administrator on each Windows NT application server to be a member of the SAP_<sid>_LocalAdmin group. Enabling Automatic Discovery for Windows NT For automatic discovery to work on Windows NT managed nodes, you must ensure that the SYSTEM user ID is added to the list of logins for the root Tivoli Administrator. This is because the automatic discovery function relies on the Windows NT at command to provide scheduling, and scheduled commands are run under the SYSTEM user ID. Refer to the appropriate Windows NT documentation for more information about the at command. Tivoli Manager for R/3 User s Guide 73

96 Enabling the Tivoli Authentication Package for Windows NT If you are running R/3 on Windows NT, you might have configured your R/3 installation to share file systems of the Central Instance with servers for Dialog instances. If your installation is configured in this way, then Tivoli must be configured for remote file access privileges for some of the Manager for R/3 tasks to gain access to the R/3 executables, in particular, for starting and stopping R/3 servers. Remote file access is configured into Tivoli through the Tivoli Authentication Package. The configuration is set during installation of the managed node or the TMA endpoint. To set remote file access after installation of the managed node or TMA endpoint, use the wsettap and wlcftap commands, respectively. Use one of the following commands to configure the Tivoli Authentication Package for use by the Administrator user after installation: Managed node: v wsettap -a -r Administrator v wsettap -a -r domain_name\administrator v wsettap -a -r domain_name\sidadm, where sid is the three-character R/3 system identifier. TMA endpoint: v wlcftap -a -r Administrator v wlcftap -a -r domain_name\administrator v wlcftap -a -r domain_name\sidadm, where sid is the three-character R/3 system identifier. For more information about the Tivoli Authentication Package, refer to the TME 10 Framework Planning and Installation Guide. For more information about the wsettap and wlcftap commands, refer to the TME 10 Framework Reference Manual. 74 User s Guide Version 2.1

97 Setting the Environment Variable for Windows NT To use the Manager for R/3 start and stop SAPGUI tasks, you must set an environment variable in the Windows NT system environment. The following environment variable enables Manager for R/3 to locate the needed R/3 files: TIV_SAPGUI_DIR Specifies the full path to the directory in which the SAP R/3 sapgui.exe file exists, as shown in this example: TIV_SAPGUI_DIR=F:\PC\NT\SAPGUI Configuring Manager for R/3 for HP-UX 11 Manager for R/3 supports R/3 running with HP-UX 11 enhancements. These enhancements include 64-bit support and shared memory windows. HP-UX bit Support Manager for R/3 supports R/3 systems running on HP-UX 11 in 64-bit mode. Manager for R/3 automatically detects if an R/3 system is running on a 64-bit mode system and automatically invokes the correct 32-bit or 64-bit programs as needed. HP-UX 11 Shared Memory Windows Shared memory windows on HP-UX 11 is superseded by 64-bit mode. However, if you are using shared memory windows, Manager for R/3 requires the following: The /etc/services.window file must contain entries that specify the application server name and the memory window in which the application server is to start. For example, the /etc/services.window file should contain entries similar to the following: peach_do1_ peach_do1_ The /usr/bin/setmemwindow and the /usr/bin/getmemwindow executables must exist on the HP-UX 11 machine. 5. Configuring Manager for R/3 Note: When an R/3 application server is moved from one shared memory environment to another, it is possible that R/3 shared Tivoli Manager for R/3 User s Guide 75

98 memory resources are not properly removed. One problem that results when this occurs is that the R/3 application server does not report syslog messages. To correct this problem, manually clean up the R/3 shared memory resources. To do this, follow these steps as described by SAP: 1. Stop the R/3 application server and enter the following command at the operating system command line: ipcs -am 2. Check the output for any remaining shared memory segments. You should find a memory segment that belongs to the user sidadm and is approximately 4 KB in size. Note the ID of this memory segment. 3. Remove the memory segment owned by sidadm. Enter the following 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 Manager for R/3 event adapters and monitors will work. For the Manager for R/3 start and stop R/3 system tasks to work, it is assumed that the SAP-provided start and stop scripts in the sidadm home directory have been modified to use the memory windowing setmemwindow and getmemwindow commands. Configuring Manager for R/3 for OS/390 This section describes considerations for using Manager for R/3 if you are running R/3 in an OS/390 environment. R/3 Release Support SAP 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 as the database. Manager for R/3-supported application server operating systems with an OS/390 database server are AIX and Windows NT. 76 User s Guide Version 2.1

99 R/3 Transports Manager for R/3 delivers transports for R/3. The base set provides all function modules needed to run the standard Manager for R/3 functions. An additional transport is provided for OS/390 that must be installed in your R/3 systems. The OS/390 transport provides the function modules to obtain OS/390 operating system information and OS/390 DB2 information. This transport is installed in the same manner as the base transport. For more information about the transports, see Moving R/3 Transports into an R/3 Landscape on page 44. During installation of the OS/390 transport, R/3 sets up default RFC destinations. R/3 automatically assigns the RFC destinations, and these destinations must be preserved for the Manager for R/3 function modules to obtain OS/390 information. The function modules delivered in the OS/390 transport rely on the R/3 saposcol and rfcoscol programs being installed on the OS/390 operating system. SAP delivers the saposcol and rfcoscol programs as part of the R/3 product, and SAP provides information about installing these programs. For installation information, refer to the SAP Online Service System. R/3 Database Objects with OS/390 Manager for R/3 does not provide direct support for managing resources on an OS/390 system and does not support the configuration of OS/390 database server objects. Therefore, Manager for R/3 will not automatically discover your R/3 database server, and you cannot create the R/3 database server object manually from the desktop. Also, Manager for R/3 does not support starting and stopping OS/390 database servers. Data Sharing OS/390 systems that use data sharing have a single database system that is accessed by multiple database machines. Because the R/3 application servers for the R/3 system are connected to different database machines, the R/3 application servers report different database host names even though the R/3 application servers are in the same R/3 system. 5. Configuring Manager for R/3 Tivoli Manager for R/3 User s Guide 77

100 In a data sharing environment, Manager for R/3 attempts to create multiple R/3 policy regions for the same R/3 system because Manager for R/3 creates R/3 system policy regions using the database host name as a qualifier. If you are using automatic discovery to create your R/3 objects, you must configure automatic discovery as described in Configuring Automatic Discovery for Data Sharing on page 56 so that Manager for R/3 uses a common database host name value. Configuring automatic discovery to use a common database host name prevents the creation of multiple R/3 policy regions. If you are creating your R/3 objects entirely from the desktop, you can select any database host name when you create the R/3 system object. Monitoring the OS/390 System Manager for R/3 provides Distributed Monitoring sources for obtaining OS/390 and OS/390 DB2 information. See Using OS Collect and OS/390 Monitors on page 123 for more information. Extending Database Server Status Reporting If you have Tivoli Manager for DB2 or Tivoli Manager for Oracle installed, you can extend Manager for R/3 database status reporting. This means that you can update the status of the database server with the status of the database as reported by the Manager for DB2 or Manager for Oracle. To enable extended database server status reporting, follow these steps: 1. Distribute a DB2 Instance Status or RDBMS State monitor. To do this, follow these steps: a. Add a properly configured database server status monitor to a Distributed Monitoring profile. Run the Create RDBMS Manager Status Monitor job in the R3 Configuration Tasks library. This job displays the Create RDBMS Manager Status 78 User s Guide Version 2.1

101 Monitor dialog. 5. Configuring Manager for R/3 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 has been updated with the appropriate Manager for DB2 instance objects or Manager for Oracle instance objects. c. Distribute the profile to the subscribers. Both database status monitors are configured to run every 15 minutes and to generate a TEC event that Manager for R/3 processes to update database server status. A TEC event is generated for each of the following response levels: Critical is set when the monitor returns Becomes unavailable. Tivoli Manager for R/3 User s Guide 79

102 Warning is set when the monitor returns Becomes available. 2. Configure the TEC event server to add the database status integration rules. To do this, clone the rule base that contains the Manager for DB2 or Manager for Oracle database status event class (DB2_status or OracleInstance_rdbmsstate, respectively). For information about how to configure the TEC event server, see Configuring the TEC Event Server on page 82. For information about the database status integration rules, see Database Status Integration Rules on page 204. Note: If you installed Manager for DB2 or Manager for Oracle after you configured the TEC event server, you must reconfigure the TEC event server to install the database status integration rules. To determine if extended database server status reporting is configured for an R/3 system, select Properties from the appropriate R3DBServer icon s pop-up menu. If the Properties dialog shows the Manager for DB2 or Manager for Oracle object name, then a connection has been established and extended database server status reporting is active. Note: The association between the Manager for DB2 or Manager for Oracle database server object and the Manager for R/3 database server object depends on both Manager for DB2 or Manager for Oracle and Manager for R/3 reporting the same value for the R/3 SID. Manager for R/3 sets the R/3 SID when you create the R/3 system object (see Creating R/3 Objects on page 53). 80 User s Guide Version 2.1

103 6 Managing R/3 Events Manager for R/3 supplies new event classes and rule sets to enable you to view and work with R/3 events at your Tivoli Enterprise Console (TEC). You can extend these classes and rule sets to provide further enhancement, automation, and intelligent processing. To work with R/3 events at your TEC console, you must configure the event console, the TEC event server, and the event adapters as described in the following steps: 1. Configure the TEC event server to recognize R/3 events and process rules concerning those events. Run the Configure Event Server task against the TEC event server to be configured. 2. Create one or more event consoles if you have not already done so. Refer to the TME 10 Enterprise Console Reference Guide. 3. Configure the event consoles. Run the Configure Event Console task to assign newly created event groups to the appropriate event consoles. 4. Configure event adapters as follows: Configure the Alert Event Adapter and the Syslog Event Adapter for each application server to process R/3 information and generate the appropriate TEC events. Configure the IDOC Event Adapter for one R/3 application server in each R/3 system to process intermediate document (IDOC) errors and generate the appropriate TEC events. 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 81

104 This chapter describes how to perform the event handling tasks, and it describes the following information that you should understand to use the event adapters: Using the Alert Event Adapter on page 88 Using the Syslog Event Adapter on page 91 Using the IDOC Event Adapter on page 96 Filtering Events on page 104 The following table describes the authorization role and target endpoint for the event handling tasks: Tasks Role Target Configure Event Adapter r3_admin R3AppServer Configure Event Console r3_admin TEC event server Configure Event Server r3_admin TEC event server Display Event Adapter r3_user R3AppServer Configuration Start Event Adapter r3_user R3AppServer Stop Event Adapter r3_user R3AppServer Configuring the TEC Event Server The Configure Event Server task configures a TEC event server for Manager for R/3 by importing new classes and rules, installing new event sources, compiling the new rule base, and then stopping and restarting the TEC event server. When integrating with Tivoli Manager for DB2 or Tivoli Manager for Oracle to update R/3 database server status (see Extending Database Server Status Reporting on page 78), it is necessary to include additional database integration rules. Similarly, when using Tivoli GEM instrumentation (see Tivoli GEM Instrumentation on page 147), it is necessary to include additional Tivoli GEM instrumentation event classes and rules in the TEC rule base. Running the Configure Event Server task after installing the Tivoli 82 User s Guide Version 2.1

105 Manager for DB2, the Tivoli Manager for Oracle, or Tivoli GEM instrumentation task libraries automatically performs these additional rule base updates. To configure a TEC event server, run the Configure Event Server job in the R3 Configuration Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) This job displays the Configure Event Server dialog. For information about completing the dialog, refer to the online help. Configuring an Event Console The Configure Event Console job adds filters to the event console and assigns the group and event sources. To configure an event console, run the Configure Event Console job in the R3 Configuration Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) This job displays the Configure 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 83

106 Event Console dialog. For information about completing the dialog, refer to the online help. When you open the TEC from the desktop, the Enterprise Console Event Groups dialog and the Enterprise Console Source Groups dialog are displayed. 84 User s Guide Version 2.1

107 To view all events that have passed the group filter criteria, open the event group. To view all events from all Manager for R/3 Syslog Event Adapters, all Alert Event Adapters, or all IDOC Event Adapters, open the WR3SLOG event source, WR3MIB event source, and WR3IDOC event source, respectively. Here is an example of the event log: 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 85

108 Configuring Event Adapters To configure either the Syslog Event Adapter, the Alert Event Adapter, or the IDOC Event Adapter, run the Configure Event Adapter task in the R3 Configuration Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) This task creates an event adapter. Notes: 1. If you reconfigure an event adapter, stop and start the appropriate event adapter to incorporate the changes. 2. Because IDOCs are system-wide resources, configure an IDOC Event Adapter on only one R/3 application server in each R/3 system. Configuring an IDOC Event Adapter on more than one R/3 application server in an R/3 system generates duplicate events for each IDOC. 86 User s Guide Version 2.1

109 The Configure Event Adapter task displays the Configure Event Adapter dialog. For information about completing the dialog, refer to the online help. Displaying Event Adapter Information To display the event adapter information, run the Display Event Adapter Configuration task in the R3 Configuration Tasks library. (See Using Manager for R/3 Configuration Tasks on page 35.) This task displays the Display Event Adapter Configuration dialog. To display the current configuration of an event adapter, select either Alert Adapter, Syslog Adapter, or IDOC Adapter. 6. Managing R/3 Events Starting and Stopping an Event Adapter Manager for R/3 provides the following tasks in the R3 App Server Tasks library to start and stop an event adapter: Tivoli Manager for R/3 User s Guide 87

110 Start Event Adapter Starts the specified event adapter. Stop Event Adapter Stops the specified event adapter. Using the Alert Event Adapter The Alert Event Adapter reports R/3 alerts by querying the R/3 SysMan interface for new entries and forwarding formatted events to the TEC. R/3 systems use alerts to report an occurrence of a situation that might require operator attention. Alerts can be generated in the following ways: Automatically based on predetermined criteria In response to the Basis Administrator setting threshold values against monitored measurements You can view the alerts that have occurred in an R/3 system through R/3 CCMS using transaction RZ03 or RZ20, depending on your R/3 release level. Understanding How the Alert Event Adapter Works To understand how the Alert Event Adapter works, you need to understand how R/3 alerts are processed and how this processing differs among R/3 releases. Alert Processing in R/3 Releases 3.0F, 3.1x, and 4.0x In R/3 releases 3.0F, 3.1x, and 4.0x, alerts are set and viewed in one way: using transaction RZ06 and transaction RZ03, respectively. About 40 different alerts can be set and viewed, and each alert represents a single occurrence of a problem. There is no historical record. The alert might have some information updated in CCMS, but once the alert is posted, it is not reposted. This level of alert reporting is referred to as 3.x alerts. To facilitate reporting of alerts to external systems, SAP provides an SNMP type of interface, called the SysMan interface. Because the SysMan interface is based on SNMP, the SysMan interface reports 88 User s Guide Version 2.1

111 traps. R/3 reports a trap at a level higher than the individual alerts. Traps are reported for the following summary levels of alerts: Operating System Enqueue Syslog Performance Buffers ABAP errors Roll/Page Trace Switch Other Alerts Dispatch Queue Database Note: The SysMan interface does not allow posting of an operating system trap by itself. Because the Alert Event Adapter uses the SysMan interface, the alerts that are visible to Manager for R/3 are the 40 alerts reported as 3.x alerts. Also, because SNMP traps are high level, more detailed information needs to be obtained to generate meaningful TEC events. Manager for R/3 provides TEC rules that initiate drill-down processing to obtain more detailed information. The detailed information is conveyed in a new TEC event. Both the original events and the drill-down events can be seen in the TEC reception log. When Manager for R/3 performs drill-down processing, Manager for R/3 TEC rules immediately close the original events. The resulting set of TEC events is listed in R/3 Operational Event Classes on page Managing R/3 Events The Alert Event Adapter is dependent on the R/3 design regarding when traps are posted. Like alerts, traps are posted only once, and they remain at that state until an alert severity changes or until the alert is closed. This means that alerts can occur in an R/3 system Tivoli Manager for R/3 User s Guide 89

112 without causing a new SysMan trap to be generated. For example, the Buffers category includes alerts for nine different buffers. If one buffer, such as CUA, gets a yellow alert, a trap is posted to the SysMan interface. If another buffer gets a yellow alert, both alerts can be seen in CCMS, but another SysMan trap is not generated for the second yellow buffer alert because a yellow buffer trap is already outstanding. Alert Processing in R/3 Release 4.5 In R/3 release 4.5, SAP introduced a new design for handling alerts: Monitoring Architecture. Monitoring Architecture is supported through transaction RZ20. Alerts are presented hierarchically. There are many more alert categories than in R/3 releases 3.0F, 3.1x, and 4.0x (3.x alerts), and there can be an alert history. This level of alerts is referred to as Alert monitor 4.0 (4.x alerts). Both 3.x and 4.x alert interfaces are available in CCMS. However, there is no implicit relationship between these two interfaces. These two interfaces are parallel alert interfaces, and thresholds and alerts in 3.x are unrelated to thresholds and alerts in 4.x. The CUA buffer, for example, can be alerted in one interface but not in the other interface. The 3.x interface continues to drive the SysMan interface as in R/3 releases 3.0F, 3.1x, and 4.0x, and the Alert Event Adapter reports the 3.x alerts but not the 4.x alerts. Bidirectional closing between TEC events and R/3 alerts is well synchronized just as in R/3 releases 3.0F, 3.1x, and 4.0x. Alert Processing in R/3 Release 4.6 In R/3 release 4.6, SAP removed the 3.x alert interface while retaining the SysMan interface. The 4.x alert interface of the Monitoring Architecture drives the SysMan interface. Using the 4.x alert interface has the following implications for the Alert Event Adapter: Not all 4.x alerts are posted as traps to the SysMan interface. Only 4.x alerts that correspond to 3.x alerts are posted. Posting of SysMan traps is dependent on Monitoring Architecture internal timing. This means that classes of traps are posted at different intervals than might be observed in earlier R/3 releases. 90 User s Guide Version 2.1

113 Closing of alerts must occur in the 4.x interface. Manager for R/3 bidirectional communication does not close 4.x alerts when closing an event from the TEC. This means that if you close an event in TEC, the trap is closed in R/3, but the same 4.x alert (if still open) causes the SysMan interface to regenerate the same TEC event. Because Monitoring Architecture has a history of alerts, closing the newest 4.x alert simply makes the next most recent alert in that class the new active open alert. If the corresponding trap is not already posted, it is posted with this next most recent alert. This reposting of old alerts occurs until all open alerts in that class are closed. A SysMan trap that indicates no problems only occurs when all alerts, including the history, are closed in the 4.x interface. Controlling Alert Events The Alert Event Adapter can generate many events. See Event Classes and Rules on page 179 for a listing of these events. To minimize the number of events that are sent to the TEC, you can filter these events at the Alert Event Adapter. To filter events, add filter statements to the r3mibiid.conf file, where IID represents the two-digit R/3 instance number. See Filtering Events on page 104. The r3mibiid.conf file is created after you run the Configure Event Adapter task and, therefore, exists only after you have run this task at least once for the specific R/3 application server. The r3mibiid.conf file is located in one of the following directories: Managed node: $BINDIR/TME/SAP/2.2C TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C 6. Managing R/3 Events Using the Syslog Event Adapter The Syslog Event Adapter processes the R/3 syslog and converts new entries into TEC events. Because the Syslog Event Adapter obtains syslog messages through the R/3 RFC interface, the Syslog Event Adapter must log on to the R/3 system. The Syslog Event Tivoli Manager for R/3 User s Guide 91

114 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. The Manager for R/3 provides two configuration files for the Syslog Event Adapter: r3slogiid.cl and r3slogiid.conf, where IID represents the two-digit R/3 instance number. These configuration files are created after you run the Configure Event Adapter task and, therefore, exist only after you have run this task at least once for the specific R/3 application server. The r3slogiid.cl and the r3slogiid.conf configuration files are located in one of the following directories: Managed node: $BINDIR/TME/SAP/2.2C TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C The configuration files are used as follows: r3slogiid.cl Defines the syslog events that are sent to the TEC. Events that are not defined in this file cause the Syslog Event Adapter to send events with event class SAP_SYSLOG_MSG. Modify the entries in the r3slogiid.cl file to customize the syslog events to be sent to the TEC or add new entries to this file to send additional syslog events to the TEC. See Modifying Entries in the r3slogiid.cl File on page 93 and Adding New Entries to the r3slogiid.cl File on page 94. r3slogiid.conf Contains TEC event filter statements. By default, all syslog events that are not specified in the r3slogiid.cl file are class SAP_SYSLOG_MSG and are filtered out. Only those events that are specified in the r3slogiid.cl configuration file are sent to the TEC. If you want to see all syslog events, comment out the Filter statement in the r3slogiid.conf file. See Filtering Events on page 104. The following table describes the syslog events that are defined in the r3slogiid.cl file and are sent to the TEC by default. You can use 92 User s Guide Version 2.1

115 the Syslog Event Adapter as shipped, or you can customize which syslog events are sent to TEC. See Controlling Syslog Events. Event Class Severity Syslog Message SAP_SYSLOG_A08 50 (critical) Main memory destroyed. SAP_SYSLOG_BY1 30 (warning) DB error &5. SAP_SYSLOG_BY2 30 (warning) Database &6 for &3. SAP_SYSLOG_BZ7 30 (warning) Storage request (&5&5 bytes) is too small 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 lock handler. SAP_SYSLOG_R0R 30 (warning) The connection was deactivated after a DB error. SAP_SYSLOG_R20 40 (minor) Insufficient shared memory. SAP_SYSLOG_R45 50 (critical) Shared memory destroyed. SAP_SYSLOG_US4 30 (warning) Maximum number of users reached. Controlling Syslog Events You can control the syslog events you want sent to the TEC in the following ways: Modifying Entries in the r3slogiid.cl File. Adding New Entries to the r3slogiid.cl File on page 94. Filtering Events on page 104. Modifying Entries in the r3slogiid.cl File To control the syslog events that are sent to the TEC, modify the entries in the r3slogiid.cl file. Entries for many syslog events are defined in the r3slogiid.cl file for your convenience. Most of the entries are commented. Commented lines are preceded by a semicolon (;). To send additional syslog events to the TEC, 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 93

116 uncomment the appropriate event entries. Similarly, if you do not want to send one of the default events to the TEC, do one of the following: Precede the appropriate event entry with a semicolon (;). Add filter criteria to the r3slogiid.conf file. See Filtering Events on page 104. Adding New Entries to the r3slogiid.cl File If you want to define additional syslog events to send to the TEC, add new syslog event entries to the r3slogiid.cl file in the following format: MessageID [Severity [Classname]] Where: MessageID Is the three-character ID that identifies the syslog message. The syslog message ID must be specified in uppercase letters. Severity Specifies 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). Classname Specifies the event class. This parameter is optional. If you do not specify an event class, the default class is 94 User s Guide Version 2.1

117 SAP_SYSLOG_msgID, where msgid is the three-character message ID. The SAP_SYSLOG_msgID event class conveys information about specific syslog messages. This event class is 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 file and define the event class similar to the event class definitions in the tecad_wr3slog.baroc file in the $BINDIR/../generic_unix/TME/SAP/baroc directory. If you need to create specific Syslog event classes by message ID, you should create event classes of the form SAP_SYSLOG_msgID. These event classes should be leaf classes of SAP_SYSLOG. Example of Controlling Syslog Events The following table provides examples of how you might control syslog events: To get this event... SAP_SYSLOG_msgID Set these controls... In the r3slogiid.cl file, SAP_SYSLOG_msgID is defined and 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 the following: Filter:Class=SAP_SYSLOG_msgID 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 95

118 To get this event... SAP_SYSLOG_MSG for syslog message, msgid, where msgid is the three-character syslog message ID. Set these controls... In the r3slogiid.cl file, SAP_SYSLOG_msgID is commented or not defined. In the r3slogiid.conf file, add one of the following: FilterMode=IN with one of the following Filter statements: Filter:Class=SAP_SYSLOG_MSG;r3SyslogMsgNumber=msgID The above Filter statement sends a SAP_SYSLOG_MSG class event only for syslog message, msgid. Or Filter:Class=SAP_SYSLOG_MSG The above Filter statement sends a SAP_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 for syslog message, msgid. Using the IDOC Event Adapter The IDOC Event Adapter enables you to monitor the transfer of business data using SAP Intermediate Documents (IDOCs). IDOCs are created in one R/3 system and are sent to one or more R/3 systems using Application Link Enabling (ALE) as the underlying communication facility, which often uses the R/3 RFC. By proactively managing the transfer of IDOCs, you can avoid the impact that can occur to business applications when business data, such as accounting codes and plant locations, is not synchronized across R/3 systems. 96 User s Guide Version 2.1

119 The IDOC Event Adapter monitors the R/3 system for changes in IDOC status and converts IDOC status changes to TEC events. The IDOC Event Adapter sends the following events to the TEC: A SAP_IDOC_STATUS event for each IDOC that is in a new error state since last reported. A harmless SAP_IDOC_STATUS event for each IDOC that was in a warning or error state when last reported and is now in a non-error state. This harmless event facilitates automatic closing of events in the TEC. A harmless SAP_IDOC_STATUS event is also sent for each IDOC when the IDOC expires. A SAP_IDOC_XMIT event for each RFC destination to which IDOCs failed transmission because of a transactional RFC communication problem. A SAP_IDOC_XMIT event is generated when an IDOC with a status code of 03 has transmission problems. Note: Status code 03 is a normal status that indicates that the IDOC was queued for transmission. A SAP_IDOC_STATUS event is not generated for this IDOC. Understanding How the IDOC Event Adapter Works The IDOC Event Adapter reports changes in IDOC status from one polling cycle to the next. IDOC status is identified by status codes, which are divided between outbound and inbound IDOCs. Outbound IDOCs (status codes 00 through 50) are those IDOCs sent by the specific R/3 system. Inbound IDOCs (status codes 51 through 74) are those IDOCs received by the specific R/3 system. For more information about IDOC status codes, see IDOC Status Codes on page Managing R/3 Events Upon startup, the IDOC Event Adapter analyzes all IDOCs and establishes a baseline from which to report subsequent errors. The IDOC Event Adapter does not generate any TEC events during the first polling cycle, and it does not generate events for IDOCs that have a non-error status from one polling cycle to the next. Tivoli Manager for R/3 User s Guide 97

120 Because the IDOC Event Adapter obtains IDOCs through the R/3 RFC interface, the IDOC Event Adapter must log on to the R/3 system. The IDOC Event Adapter uses the same R/3 user ID information that you specified when you configured an RFC. See Configuring a Remote Function Call on page 71. Viewing and Interpreting IDOC Events When you receive IDOC events, you will see TEC events (SAP_IDOC_STATUS and SAP_IDOC_XMIT events) as illustrated in the following TEC event log: Manager for R/3 reports the most current information about each IDOC by using TEC rules that close duplicate SAP_IDOC_STATUS events. A duplicate SAP_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 User s Guide Version 2.1

121 This means that when a duplicate SAP_IDOC_STATUS event is received from the same R/3 system for the same R/3 client and IDOC number, the first event is closed regardless of whether the IDOC status code changed or remained the same. Interpreting SAP_IDOC_STATUS Events The message area on the TEC can help you determine which SAP_IDOC_STATUS events are important. The message area contains the IDOC status code, the message type, partner system, and the IDOC message. After determining which events are important based on the IDOC status code, the message type can give you guidance about which application area is having the IDOC problem. Message types are defined in R/3. Depending on your organization s policies, you might need to act on an IDOC error based on the code and type, or you might need to provide this information to someone else. Many times, responding to an IDOC error requires that you or someone else log on to the R/3 system to take corrective action. You can use additional event slot values to determine which R/3 system to log on to and which IDOC to investigate. To determine the R/3 system, open the SAP_IDOC_STATUS event and look at the sub_source event slot, which contains the R/3 SID. To determine the IDOC that you need to investigate within this R/3 system, look at the r3client and r3idocnum event slots. These event slots uniquely identify the IDOC. Depending upon the type of IDOC error, the msg event slot might contain additional information that can help you correct the problem. Interpreting SAP_IDOC_XMIT Events The message area on the TEC provides information to help you determine the cause of the transmission problem associated with a SAP_IDOC_XMIT event. The message area shows the partner system to which the IDOC is sent, and it shows the number of IDOCs that have failed transmission in the last polling interval to this partner system. When you open a SAP_IDOC_XMIT event, you can find out additional information about the number of IDOCs that have been sent and the number of IDOCs that have failed transmission in the last polling interval and in the last 24 hours. 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 99

122 Controlling IDOC Events You can control the IDOC events to be sent to the TEC by modifying the r3idociid.conf file, where IID represents the two-digit R/3 instance number. The r3idociid.conf file is created after you run the Configure Event Adapter task and, therefore, exists only after you have run this task at least once for the specific R/3 application server. The r3idociid.conf file is located in one of the following directories: Managed node: $BINDIR/TME/SAP/2.2C TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C You can customize the r3idociid.conf file in the following ways: Add filter statements to minimize the number of events that are sent to the TEC by filtering the events at the IDOC Event Adapter. For more information, see Filtering Events on page 104. Modify the entries that control the following: v Number of days after which IDOCs with unchanged status expire (ABH_ExpirationDays). The default is 7 days. v Inbound status codes that are interpreted as error codes (ABH_InboundErrorCodes). Valid values are 51 through 74. The default inbound status codes are: 51, 52, 54, 56, 60, 61, 63, and 65. v Outbound status codes that are interpreted as error codes (ABH_OutboundErrorCodes). Valid values are 00 through 50. The default outbound status codes are: 02, 04, 05, 07, 09, 11, 15, 17, 20, 23, 25, 26, 27, 29, 34, 36, 37, and 40. The following entries in the r3idociid.conf file show the default values that the IDOC Event Adapter uses: ABH_ExpirationDays=7 ABH_InboundErrorCodes=51,52,54,56,60,61,63,65 ABH_OutboundErrorCodes=02,04,05,07,09,11,15,17,20,23,25,26,27,29,34,36,37, User s Guide Version 2.1

123 Notes: 1. Error codes must be specified in a comma-separated list without intervening spaces. 2. Both inbound and outbound error codes must be specified. If both inbound and outbound error codes are not specified or if the values specified are not valid or are not specified using the correct syntax, the IDOC Event Adapter uses the default values. 3. If you customize the r3idociid.conf file, stop and start the appropriate IDOC Event Adapter to incorporate the changes. Performance Considerations Because the performance of the IDOC Event Adapter is affected by many variables, it is not possible to provide precise guidelines for configuring your R/3 system, the IDOC Event Adapter, and your TEC event server. This section provides information to help you evaluate your environment so that you can determine a configuration that meets your needs. The factors that affect the performance of the IDOC 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 in the R/3 system. The R/3 system is able to resolve some IDOC errors automatically. For other IDOC errors, intervention is required. The IDOC Event Adapter does not find IDOC errors that are automatically resolved between IDOC Event Adapter polling intervals and, hence, does not generate TEC events. Thus, both ability of the R/3 system to automatically resolve IDOC errors and the IDOC Event Adapter polling interval affect the number and type of IDOC events that you see on your TEC console. 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 101

124 To set the optimum polling interval for the IDOC Event Adapter, you need to evaluate your R/3 system IDOC load, the expected number of IDOCs in error state at any time, the frequency at which you want notifications, and the load on your TEC event server. Consider the following situations: If your R/3 system automatically resolves many IDOC error situations, a low (one to two minutes) polling interval might cause you to get many TEC events for which you do not need to take action. In this case, setting the polling interval to a higher rate (5 to 15 minutes) can cause a higher percentage of IDOC events sent to TEC to be of the type that require your intervention. If you are concerned about seeing IDOC errors as soon as they occur, you might want to set a low polling interval (three to five minutes). If you need to be aware of IDOC errors on a less urgent basis, you can set a higher polling interval (30 minutes). Because the IDOC Event Adapter sends TEC events for pertinent IDOCs at each polling interval, if you have many IDOCs in your R/3 system, a higher polling interval can result in many IDOC events (several hundred or more) to be sent to your TEC event server at the same time. If you find that you have an excessive number of IDOC events and you are not interested in receiving IDOC events for specific status codes, you can customize the IDOC status codes that the IDOC Event Adapter considers as IDOC errors. For information about how to do this, see Controlling IDOC Events on page 100. By reducing the number of status codes that the IDOC Event Adapter considers as IDOC errors, you can directly affect the number of IDOC events that are sent to the TEC event server. The IDOC Event Adapter relies on an R/3 ABAP program to locate IDOC errors in your R/3 system. To work correctly, this program must read all the IDOCs in your R/3 system. If your R/3 system contains a very large number of IDOCs (hundreds of thousands or millions), then the processing time for this ABAP program will be 102 User s Guide Version 2.1

125 extended. You can decrease this processing time by implementing an IDOC archiving strategy for your R/3 systems. Using an archiving strategy enables you to keep the number of IDOCs in your R/3 system at a manageable level. The Tivoli test lab configured the IDOC Event Adapter to poll at five-minute intervals and to report the default set of IDOC error events. The R/3 system contained 104,000 IDOCs, 2000 of which were in an error state. The Tivoli test lab calculated the performance of the IDOC Event Adapter as follows: The ABAP program processed the R/3 IDOCs and located IDOC errors in seven seconds. The IDOC Event Adapter processed 2,000 IDOC errors and sent events to the TEC in ten seconds. The TEC event server processed the 2,000 IDOC events in 94 seconds. The Tivoli test lab calculated the performance of the IDOC Event Adapter 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. This machine had no other significant load. TEC event server v IntelliStation One 333 MHz processor 6. Managing R/3 Events Tivoli Manager for R/3 User s Guide 103

126 Filtering Events 256 MB RAM One 6.2 GB IDE disk Windows NT 4.0 TEC using the default rule base Oracle 7.xx as the RIM RDBMS The event load for the TEC event server was limited to the events from the IDOC Event Adapter. You might not want certain types of R/3 events to appear on your TEC consoles because you regard them as harmless or unlikely to require action. The TEC provides the following ways for you to filter out events that you do not want to view: You can specify that the event is not to be forwarded to the TEC event server. In this case, you specify filter criteria in one or more of the following configuration files: Event Adapter Alert Syslog IDOC Configuration File r3mibiid.conf r3slogiid.conf r3idociid.conf Here is an example of a Filter statement: FilterMode=OUT Filter:Class=SAP_ALERT_Trace;r3configDBName=TV5 Refer to the TME 10 Enterprise Console Adapter s Guide for more information. You can create new rules to exclude the event. In this case, the event is forwarded to the TEC event server, but it is eliminated by the rules engine. Refer to the TME 10 Enterprise Console Rule Builder s Guide for more information. 104 User s Guide Version 2.1

127 7 Monitoring R/3 Resources 7. Monitoring R/3 Resources This chapter describes the monitoring collections that Manager for R/3 provides to help you manage R/3 resources. This chapter also explains how to use and customize Manager for R/3 monitors. Like any Distributed Monitoring monitor, these R/3-specific monitors should be customized to meet the needs of your R/3 installation. For example, you might want to add monitors to the default set and specify the severity or threshold of the monitors. For additional information, refer to the TME 10 Distributed Monitoring User s Guide. Manager for R/3 monitors are specifically designed to work with object types provided with the Manager for R/3 product just as Distributed Monitoring monitors are designed to work with the standard Framework endpoints: managed nodes and TMA endpoints. Distribution of one product s monitors to another product s endpoints is not supported. This means that you cannot distribute Manager for R/3 monitors to managed nodes and TMA endpoints, and you cannot distribute Distributed Monitoring monitors to Manager for R/3 object endpoints. For example, you should distribute the application server status monitor to an R3AppServer object and not to a managed node or TMA endpoint. Tivoli Manager for R/3 User s Guide 105

128 Monitoring Collections Manager for R/3 provides the following monitoring collections 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 Sources Each monitoring collection contains a set of monitoring sources. Monitoring sources provide a logical grouping of the monitors to facilitate your monitor selection. Many of the monitoring sources provided for the server remote monitors and the server central monitors collections are common to both collections. Attributes A monitor must be defined to report one specific value. Many of the monitoring sources enable you to select the monitoring value to be reported by selecting an attribute. For example, the roll area source has attributes for roll area free space, roll area size, and roll area currently used. For each monitor defined, Distributed Monitoring provides graphical user interface tools to individually configure specific values for the monitor, such as the frequency at which the monitor should be run, one or more threshold levels, and actions to be taken at each threshold. R3 ITS Server Monitors The R3 ITS Server Monitors provide the ability to monitor the status of your R/3 ITS servers. The R3 ITS Server Monitors monitoring collection contains one monitoring source: ITS Server Status. You can use the R3 ITS Server Monitors profile contained in the R3 ITS Monitors profile manager to distribute this monitor. See R3 ITS Monitors Profile Manager on page User s Guide Version 2.1

129 R3 Server Remote and R3 Server Central Monitors The R3 Server monitors provide the ability to monitor aspects of your R/3 application servers and R/3 database servers. Manager for R/3 provides the R3 Server Remote and R3 Server Central monitoring collections, that reflect different monitoring implementations, for this purpose. Both monitoring collections contain a set of monitoring sources to support a wide range of monitor options. 7. Monitoring R/3 Resources Remote monitors and central monitors differ primarily in where the monitors run, not in what they monitor. Remote monitors are run on a target endpoint and monitor an application server on that endpoint. Central monitors run on the TMR server but monitor an R/3 application server on another endpoint. For central monitors to work, the monitoring implementation must provide remote communication capabilities rather than relying on Distributed Monitoring communication channels. Manager for R/3 is able to provide central monitors using R/3 remote function calls (RFCs). All of the server remote monitors run against an R3AppServer endpoint. This means that when you build a monitoring profile that includes server remote monitors, you must distribute that profile to an R3AppServer endpoint. The monitors will not run if they are distributed to any other endpoints. The server central monitors are distributed to the TMR server and communicate with an R/3 application server using an R/3 remote function call (RFC). You specify the R3AppServer endpoint as an attribute when you add the monitor. Manager for R/3 provides a list of valid R3AppServer objects from which to select when setting the attribute. The following table lists the monitoring sources, their corresponding monitoring collection, and a reference to the attributes that pertain to that source. Tivoli Manager for R/3 User s Guide 107

130 Source Roll Area Page Area Work Process Work Process Dispatch Queue Long Running Work Process CUA Menu and Text Buffer PRES Screen and Dynpro Buffer TTAB Table Description Buffer FTAB Field Catalog Buffer SNTAB Short NameTab Buffer IRBD Initial Records Buffer TABL Generic Key Buffer TABLP Single Key Buffer PXA Program Buffer OS Collect - Application Server R3 Server Remote Collection X X X X X X X X X X X X X X X R3 Server Central Collection X X X X X X X X X X X X Attribute Reference See Roll Area on page 209 See Page Area on page 210 See Work Process Source on page 211 See Work Process Dispatch Queue Source on page 212 See Long Running Work Process Source on page 212 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See Buffer on page 213 See OS Collect on page User s Guide Version 2.1

131 Source Application Server Status Dialog Performance Update Performance Batch Performance Spool Performance OS Collect - Database Server OS/390 R3 Server Remote Collection X X X X X R3 Server Central Collection X X Attribute Reference No attributes See Performance on page 214 See Performance on page 214 See Performance on page 214 See Performance on page 214 See OS Collect on page 208 See OS/390 on page 217 OS/390 DB2 See OS/390 DB2 X on page 215 Cancelled Job X No attributes Heap Memory X X See Heap Memory Source on page 214 Extended Memory X X See Extended Memory Source on page 214 User X X See User Source on page Monitoring R/3 Resources R3 UNIX and R3 Windows NT File System Monitors The R3 UNIX and Windows NT file system monitors provide the ability to monitor R/3 file systems on your R/3 application servers. These monitors are organized according to the underlying operating system. For more information, see Using the File System Monitors on page 116. Tivoli Manager for R/3 User s Guide 109

132 Default Profile Managers To facilitate immediate monitoring capabilities, Manager for R/3 provides a set of profile managers. These profile managers are available for application servers, database servers, ITS servers, and managed nodes. R3 App Server Monitors Profile Manager The R3 App Server Monitors profile manager contains the following application server profiles: R3 Server Remote Monitors Contains monitors for buffer quality for each of the different buffers, maximum percent used for roll and page areas, R/3 response time for different user processes, percent used and maximum percent used for extended memory, and status for the saposcol daemon. R3 Server Autodiscovery Monitors Contains the application server status monitor. This monitor returns the status of an R/3 application server. Distribute this profile to each R/3 application server to ensure that each R/3 application server reflects its current status. R3 Server Central Monitors Enables you to use monitors from the R3 Server Central Monitors collection. This profile is empty, and the only valid subscriber is the TMR server. Monitoring of remote machines is performed from the TMR by distributing the profile to this subscriber. R3 DB Server Monitors Profile Manager The R3 DB Server Monitors profile manager contains the R3 DB Server Central Monitors profile. This profile enables you to use monitors from the R3 Server Central monitoring collection, in particular, the monitors for OS/390 and for the database server. This profile is empty, and the only valid subscriber is the TMR server. Monitoring of the remote machines is performed from the TMR by distributing the profile to this subscriber. 110 User s Guide Version 2.1

133 R3 Distributed Daemon Monitors Profile Manager The R3 Distributed Daemon Monitors profile manager contains profiles that define monitors that report the status of critical R/3 processes. Subscribe the appropriate managed nodes and TMA endpoints to this profile manager. This profile manager contains the following profiles: R3 Windows NT Print Monitors Contains a monitor for reporting the status (up or down) of the saplpd daemon on Windows NT. R3 SAP Router Monitors Contains a monitor for reporting the status (up or down) of the saprouter daemon. R3 Managed Nodes Monitors Profile Manager The R3 Managed Nodes profile manager does not contain any default profiles and is provided so you can create monitor profiles from Distributed Monitoring collections. The default subscriber is the TMR server. Subscribe the appropriate managed nodes to this profile manager. Refer to the TME 10 Framework User s Guide for more information about creating a profile within a profile manager. R3 ITS Monitors Profile Manager The R3 ITS Monitors profile manager contains the R3 ITS Server Monitors profile. This profile enables you to use the ITS Server Status monitor, which is contained in the R3 ITS Server Monitors monitoring collection. The ITS Server Status monitor reports the status (up or down) of the R/3 ITS server and has no attributes. You must configure and distribute this monitor to each R3ITSServer object so that each R3ITSServer object reflects its current status. The R3ITSServer object can represent a single-host ITS server or the AGate or the WGate component of a dual-host ITS server. R3 Central Instance Monitors Profile Manager The R3 Central Instance profile manager contains the following profiles: R3 Message Server Monitors Contains a message server status monitor for UNIX. This 7. Monitoring R/3 Resources Tivoli Manager for R/3 User s Guide 111

134 monitor returns the status (up or down) of the R/3 message server daemon. The message server status monitor has no attributes. Because there is only one message server daemon in an R/3 system, distribute this profile to only the R/3 application server that is running the message server. Manager for R/3 ships a message server status monitor for UNIX and for Windows NT in different monitoring collections: R3 UNIX File System Monitors and R3 Windows NT File System Monitors. Manager for R/3 provides the R3 Message Server Monitors profile customized to run a message server status monitor for UNIX. If you want to run a message server status monitor for Windows NT only, replace the message server status monitor in the R3 Message Server Monitors profile with a message server status monitor for Windows NT. If you want to run a message server status monitor for both UNIX and Windows NT, either create a new profile that contains a message server status monitor for Windows NT or add a message server status monitor for Windows NT to the R3 Windows NT File System Monitors profile. R3 UNIX File System Monitors Contains monitors that report the percentage of space used, the percentage of inodes used, and the amount of free space in various R/3 UNIX directories. For more information, see Using the File System Monitors on page 116. Distribute this profile to each UNIX R/3 application server that has a unique file system. R3 Windows NT File System Monitors Contains monitors that report free space and space used on the logical disk on which various R/3 directories reside. For more information, see Using the File System Monitors on page 116. Distribute this profile to each Windows NT R/3 application server that has a unique file system. 112 User s Guide Version 2.1

135 Using Monitoring Sources The following topics provide additional information about using the Manager for R/3 monitoring sources: Using the Application Server Status Monitor Using the Storage Monitors on page 114 Using the Performance Monitors on page 115 Using the File System Monitors on page 116 Using the User Monitor on page 119 Using the Work Process Monitors on page 119 Using the Cancelled Job Monitor on page 121 Using OS Collect and OS/390 Monitors on page 123 Using the Application Server Status Monitor The Application Server Status monitor provides values that control the setting of the R3AppServer icon state on the desktop and the automatic closing of Manager for R/3 TEC events. Therefore, this monitor must be properly configured and must be distributed to all R/3 application servers for complete and accurate Manager for R/3 processing. You must manually distribute this monitor after creating the R3AppServer objects. 7. Monitoring R/3 Resources Manager for R/3 provides a correctly configured application server status monitor in the R3 Server Autodiscovery Monitors profile. This monitor supports the following response levels that correspond to each of the returned statuses: Critical level is set when the monitor returns Becomes unavailable. Reset level is set when the monitor returns Becomes available. Warning level is set when the monitor returns Becomes standby. Tivoli Manager for R/3 User s Guide 113

136 If you do not choose to use the provided Application Server Status monitor, create an Application Server Status monitor that complies with the following rules: Provides a unique response level for each of the monitor s returned statuses. Does not configure more than one response level for each of the monitor s returned statuses. Does not configure the always response level. The default Application Server Status monitor is configured to generate a TEC event for each of the response levels. These TEC events must be generated so that Manager for R/3 TEC rules can properly close Manager for R/3 events. The default monitor is also configured to run every minute. This interval can be changed; however, it is recommended that the monitoring interval does not exceed five minutes so that the application server status changes are reflected in a timely fashion. Because the Application Server Status monitor is key to Manager for R/3 processing, you should distribute this monitor to each R/3 application server being managed. The easiest way to distribute a correctly configured Application Server Status monitor is to distribute the R3 Server Autodiscovery Monitors profile to the R3 App Server List profile manager for each R/3 system. Manager for R/3 processing depends on the generation of a single event for each application server state change. In addition to configuring a unique response level for each of the monitor values, you must also ensure that only one copy of the monitor is distributed to each R/3 application server. Therefore, if you are distributing multiple monitoring profiles to an R/3 application server, ensure that there is only one Application Server Status monitor in all the monitoring profiles that you are distributing. Using the Storage Monitors Manager for R/3 provides monitors in the R3 Server Remote and R3 Server Central monitoring collections for many of the key storage areas in R/3 application servers. You can monitor critical values, 114 User s Guide Version 2.1

137 such as free space, used spaced, and percentages for many storage areas. The specific values that can be monitored depend on the particular storage area. You can monitor the following storage areas: Roll area Page area Extended memory Heap memory Buffers v CUA menu and text v FTAB field catalog v IRBD initial records v PRES screen and dynpro v PXA program v SNTAB short NameTab v TABL generic key v TABLP single key v TTAB table description 7. Monitoring R/3 Resources For a complete listing of the monitoring sources and how they relate to the R/3 system, see Remote and Central Monitoring Sources on page 207. Using the Performance Monitors Manager for R/3 provides monitors in the R3 Server Remote monitoring collection for monitoring the performance of key R/3 work processes. You can monitor performance values, such as wait time, response time, and frequency for the following work processes: Dialog Update Batch Spool Tivoli Manager for R/3 User s Guide 115

138 For a complete listing of the monitoring sources and how they relate to the R/3 system, see Remote and Central Monitoring Sources on page 207. Using the File System Monitors Manager for R/3 provides file system monitors that make it easier for you to monitor R/3 file systems than if you used Distributed Monitoring file system monitors. Many R/3 file systems have names that include the R/3 SID. For example, the transport directory is named /usr/sap/sid/trans. To monitor the transport directory using Distributed Monitoring monitors, you would need to create a monitoring profile for each SID, and you would need to ensure that you distributed the correct monitoring profile to the appropriate R/3 application server. Because Manager for R/3 file system monitors automatically substitute the SID based on the R/3 application server to which the monitoring profile is distributed, you can create one profile that you distribute to multiple R/3 application servers. Manager for R/3 provides two monitoring collections: R3 UNIX File System Monitors and R3 Windows NT File System Monitors that contain monitoring sources for various R/3 UNIX and Windows NT file systems, respectively. UNIX File System Monitors UNIX File System monitors enable you to monitor the following values for various R/3 UNIX file systems: Used % Returns the percentage of space used in the specified file system Inode Used % Returns the percentage of inodes used in the specified file system. Space Free Returns the amount of free space in KB in the specified file system. The name of each monitoring source includes the name of the file system followed by the monitor attribute, such as SAP Transport User s Guide Version 2.1

139 Used %, SAP Transport - Inode Used %, and SAP Transport - Space Free. The following table describes the file system name as it appears in the name of the monitoring source and the corresponding R/3 directory, where SID is the three-character R/3 system identifier: File System SAP Transport SAP Home SAP Mount SAP Executable SAP Profile SAP Global Oracle datan Oracle Oracle Reorg Oracle Archive DB2 DB2 Archive DB2 Log UNIX Directory /usr/sap/trans /usr/sap/sid /sapmnt/sid /sapmnt/sid/exe /sapmnt/sid/profile /sapmnt/sid/global /oracle/sid/sapdatan, where n represents a number from 1 through 20. Specify sapdata1 through sapdata20 in the Monitor Arguments section of the Add Monitor dialog. /oracle/sid /oracle/sid/sapreorg /oracle/sid/saparch /db2/sid /db2/sid/log_archive /db2/sid/log_dir 7. Monitoring R/3 Resources All of the UNIX file system monitors run against an R3AppServer endpoint. The monitors will not run if they are distributed to managed node endpoints. Use the R3 UNIX File System Monitors profile to distribute the UNIX file system monitors. For more information about the R3 UNIX File System Monitors profile, see R3 Central Instance Monitors Profile Manager on page 111. Windows NT File System Monitors Windows NT File System monitors enable you to monitor R/3 file system values. To locate and report on the file systems, the Windows Tivoli Manager for R/3 User s Guide 117

140 NT file system monitors rely on Windows NT registry keys and value names that are set when R/3 is installed using SAP installation tools. Note: If you have reconfigured your system or moved files after installing R/3, you must ensure that the Windows NT registry reflects your changes. You can monitor various R/3 Windows NT file systems for the following values: Used % Returns the percentage of space used on the logical disk on which the specified file system resides Space Free Returns the amount of free space in KB on the logical disk on which the specified file system resides The name of each monitoring source includes the name of the file system 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 in the name of the monitoring source, the corresponding R/3 directory, where SID is the three-character R/3 system identifier, and the value name that must exist in the Windows NT registry: File System Windows NT Directory Windows NT Value Name SAP Home...\usr\sap\SID ImagePath Oracle...\oracle\SID SAPDATA_HOME Oracle datan...\oracle\sid\sapdatan, where n represents a number from 1 through 20. Specify sapdata1 through sapdata20 in the Monitor Arguments section of the Add Monitor dialog. SAPDATAn Oracle Reorg...\oracle\SID\sapreorg SAPREORG Oracle Archive...\oracle\SID\saparch SAPARCH Oracle Backup...\oracle\SID\sapbackup SAPBACKUP 118 User s Guide Version 2.1

141 File System Windows NT Directory Windows NT Value Name Oracle Check...\oracle\SID\sapcheck SAPCHECK Oracle Statistics...\oracle\SID\sapstat SAPSTAT Oracle Trace...\oracle\SID\saptrace SAPTRACE Note: The ImagePath value name resides in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPSID_IID. The remaining value names reside in HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SID\Environment. 7. Monitoring R/3 Resources All of the Windows NT file system monitors run against an R3AppServer endpoint. Use the R3 Windows NT File System Monitors profile to distribute the Windows NT file system monitors. For more information about the R3 Windows NT File System Monitors profile, see R3 Central Instance Monitors Profile Manager on page 111. Using the User Monitor The User monitor reports the number of active user sessions on an R/3 application server. Because the User monitor counts its own session on an R/3 application server, the number reported is one more than the number of active user sessions displayed on the SAPGUI. You can configure the monitor to report all user sessions (the sum of all real terminal sessions and all APPC-TM terminal sessions) or user terminal sessions (all real terminal sessions). For more information about the User monitor and how it relates to the R/3 system, see User Source on page 215. Using the Work Process Monitors Manager for R/3 provides the following monitors in the R3 Server Remote monitoring collection that enable you to monitor R/3 work processes: Work Process Work Process Dispatch Queue Long Running Work Process Tivoli Manager for R/3 User s Guide 119

142 Using the Work Process Monitor The Work Process monitor enables you to monitor the states of various work processes, such as free, waiting, running, stopped, completed, or all states. The work processes you can monitor are: Dialog Update Enqueue Batch Spool Update2 All For more information about the Work Process monitor and how it relates to the R/3 system, see Work Process Source on page 211. Using the Work Process Dispatch Queue Monitor This monitor enables you to report the number of queued requests for 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 Queue monitor and how it relates to the R/3 system, see Work Process Dispatch Queue Source on page User s Guide Version 2.1

143 Using the Long Running Work Process Monitor The Long Running Work Process monitor enables you to monitor the various work processes within an R/3 application server for excessively long processing times. When you configure this monitor, you can specify the type of work process that you want to monitor and the time interval threshold that constitutes a long running state. This monitor reports the number of long running processes, and it also returns additional information that provides detailed information for up to three long running processes. The detailed information includes: Work process type Work process number Client Elapsed time User name Report name 7. Monitoring R/3 Resources When Distributed Monitoring pop-ups are used, the detailed information is available as additional information in the pop-up. When Distributed Monitoring TEC events are generated, the detailed information is available in the LONG_RUNNING_PROCESS_MONITOR event class in the info event slot. For more information about the Long Running Work Process monitor and how it relates to the R/3 system, see Long Running Work Process Source on page 212. Using the Cancelled Job Monitor The Cancelled Job monitor enables you to identify newly cancelled jobs, facilitates the reporting of detailed information about these cancelled jobs, and enables you to identify periods in which many batch jobs are being cancelled. Tivoli Manager for R/3 User s Guide 121

144 The Cancelled Job monitor does not require any configuration parameters. This monitor operates by looking at all cancelled jobs in the R/3 system. These jobs can include old jobs as well as newer jobs. Whenever cancelled jobs are found, this monitor determines if there are any jobs for which detailed information has not already been reported. If so, this monitor provides detailed information for one of the newly cancelled jobs. The Cancelled Job monitor reports the number of cancelled jobs for which the monitor has not previously reported detailed information. When this monitor reports a non-zero value, the monitor returns additional detailed information related to one cancelled job. The detailed information includes: Job name Job ID Job date When Distributed Monitoring pop-ups are used, this detailed information is available as additional information in the pop-up. When Distributed Monitoring TEC events are generated, this detailed information is available in the SAP_CANCELLED_JOB_MONITOR event class in the r3jobname, r3jobid, and r3jobdate event slots. If you want to track cancelled jobs, you can write TEC rules to process the TEC event, keying on the job name, for example. If you want to monitor for periods of high batch job failure, you can set thresholds against the reported value of the monitor. In both cases, you will need a general idea of the expected cancelled job rate to properly set the monitoring interval. As a recommendation, you should set your monitoring interval to be two to three times the rate at which you expect batch job failures. Because this monitor operates against all jobs in an R/3 system, you need to distribute the monitor to only one R/3 application server in the R/3 system. Use the R3 Central Instance profile manager to distribute this monitor (see R3 Central Instance Monitors Profile Manager on page 111). Distributing the Cancelled Job monitor to 122 User s Guide Version 2.1

145 multiple application servers in the same R/3 system can result in duplicate reporting of the same cancelled job. Because this monitor must look at all R/3 cancelled jobs, the performance of the monitor can be affected by the number of cancelled jobs in the R/3 system. This monitor can adequately process up to 300 cancelled jobs. Although it is not possible to provide a specific limit on the number of cancelled job that this monitor can process, this monitor might be able to process more than 300 cancelled jobs. 7. Monitoring R/3 Resources Note: The job limit applies to the number of cancelled jobs in the R/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 to keep the number of cancelled jobs to 300 or less. Using OS Collect and OS/390 Monitors Most of the monitors delivered with Manager for R/3 are intended to be run directly on the remote endpoints. Typically, these endpoints are the R/3 application server machines. The OS/390 and some of the OS Collect monitors do not fit this model. Because Manager for R/3 does not always have direct access to the R/3 database server, database monitoring information is collected indirectly using R/3 itself to provide the information. This section explains the differences between the OS/390 and OS Collect monitoring sources and how to use them. OS Collect - Application Server This source provides operating system monitors for an application server, as that information is reported in the R/3 system. These monitors collect their information by communicating directly with the application server. The communication with the application server can be either directly on the application server machine or it can be remotely from the TMR server. To use these monitors directly on the application server machine, follow these steps: 1. Add a monitor from the Server Remote Monitors collection within the R3 App Server Monitors profile manager. Tivoli Manager for R/3 User s Guide 123

146 2. Add a monitor using the OS Collect Application Server monitoring source. 3. Select the attribute you want to monitor. After you have added all monitors, distribute the profile to the appropriate application servers to begin monitoring. To use these monitors on the TMR server, follow these steps: 1. Add a monitor from the Server Central Monitors collection within the R3 App Server Monitors profile manager. 2. Add a monitor using the OS Collect - Application Server monitoring source. 3. Select the attribute you want to monitor and select the application server you want to monitor. After you have added all monitors, distribute the profile to the TMR server to begin monitoring. OS Collect - Database Server This source provides operating system monitors for a non-os/390 database server, as that information is reported in the R/3 system. These monitors collect their information through any application server connected to the R/3 database server. To use these monitors, follow these steps: 1. Add a monitor from the Server Central Monitors collection within 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 application server connected to the database server you want to monitor. After you have added all monitors, distribute the profile to the TMR server to begin monitoring. 124 User s Guide Version 2.1

147 OS/390 This source provides operating system monitors for an OS/390 database server, as that information is reported in the R/3 system. These monitors collect their information through any application server connected to the R/3 database server on the OS/390. To use these monitors, follow these steps: 1. Add a monitor from the Server Central Monitors collection within the R3 DB Server Monitors profile manager. 2. Add a monitor using the OS/390 source. 3. Select the attribute you want to monitor and select an application server connected to the database server you want to monitor. 7. Monitoring R/3 Resources After you have added all monitors, distribute the profile to the TMR server to begin monitoring. OS/390 DB2 The OS/390 DB2 monitoring source provides DB2 monitors for an OS/390 database server, as that information is reported in the R/3 system. These monitors collect their information through any application server connected to the R/3 database server on the OS/390. To use these monitors, follow these steps: 1. Add a monitor from the Server Central Monitors collection within the R3 DB Server Monitors profile manager. 2. Add a monitor using the OS/390 DB2 source. 3. Select the attribute you want to monitor and select an application server connected to the database server you want to monitor. After you have added all monitors, distribute the profile to the TMR server to begin monitoring. Tivoli Manager for R/3 User s Guide 125

148 126 User s Guide Version 2.1

149 8 Tasks for Managing R/3 Resources Manager for R/3 provides the following task libraries that include tasks to help you manage R/3 resources: R3 System Tasks R3 App Server Tasks R3 DB Server Tasks R3 ITS Server Tasks 8. Tasks for Managing R/3 Resources Running a Task This chapter describes the tasks contained within these task libraries. Note: Manager for R/3 also provides task libraries that contain configuration tasks to help you configure the Manager for R/3. See Using Manager for R/3 Configuration 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. To run a task, follow these steps: Tivoli Manager for R/3 User s Guide 127

150 1. From the desktop, open the Manager for R3 policy region to locate the R3 System Tasks, R3 App Server Tasks, R3 DB Server Tasks, 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 Task Library: R3 App Server Tasks window is displayed as a result of 128 User s Guide Version 2.1

151 double-clicking the R3 App Server Tasks icon. 8. Tasks for Managing R/3 Resources Tivoli Manager for R/3 User s Guide 129

152 3. Run the appropriate task to display the Execute Task dialog. 4. Complete the Execute Task dialog, referring to the online help if you need additional information. Specify the task endpoints as follows: For an R/3 system task, select an endpoint of type R3System, such as SID_DBhostname (R3System). For an R/3 application server task, select an endpoint of type R3AppServer, such as hostname_sid_iid (R3AppServer) For an R/3 database server task, select an endpoint of type R3DBServer, such as hostname_sid_db (R3DBServer). 130 User s Guide Version 2.1

153 For an R/3 ITS server task, select an endpoint of type R3ITSServer, such as hostname_viin_its (R3ITSServer). For more information, see Manager for R/3 Object Endpoints on page Click Execute and Dismiss to start the task. If the task requires arguments, a dialog is displayed. If a dialog is displayed, complete the dialog and then click Set and Execute to start the task. Note: Each dialog has a Help button that you can select to view information about the dialog s input fields. 8. Tasks for Managing R/3 Resources R3 System Tasks The R3 System Tasks library contains the following tasks to help you manage R/3 systems: Type of Task Tasks Role Target Controlling the R/3 System Start R/3 System Stop R/3 System r3_user R3System endpoint Controlling the R/3 System Manager for R/3 provides the following tasks in the R3 System Tasks library to control the R/3 system: Start R/3 System Starts the database server and all application servers in the specified R/3 system. Tivoli Manager for R/3 User s Guide 131

154 Stop R/3 System Stops the database server and all application servers in the specified R/3 system. The results of the task are displayed in an output dialog, and the statuses of the database and application servers are displayed on their icons. R3 App Server Tasks The R3 App Server Tasks library contains the following tasks to help you manage R/3 application servers: Type of Task Tasks Role Target Controlling Event Adapters on page 133 Controlling Application Servers on page 133 Displaying Application Server Performance Information on page 134 Start Event Adapter Stop Event Adapter Start Server Stop Server Display Buffer Information Display Roll Page Information Display OS Collect Information Display OS/390 Information Display OS/390 DB2 Information r3_user r3_user r3_user R3AppServer endpoint R3AppServer endpoint R3AppServer endpoint 132 User s Guide Version 2.1

155 Type of Task Tasks Role Target Managing Batch Jobs on page 134 Controlling R/3 Work Processes on page 135 Display Batch Jobs Cancel Batch Job Release Batch Job Display Work Processes Cancel Work Process r3_user r3_user R3AppServer endpoint R3AppServer endpoint Controlling Event Adapters Manager for R/3 provides the following tasks in the R3 App Server Tasks library to control event adapters: Start Event Adapter Starts the Alert Event Adapter, the Syslog Event Adapter, or the IDOC Event Adapter on the specified R/3 application server. Stop Event Adapter Stops the Alert Event Adapter, the Syslog Event Adapter, or the IDOC Event Adapter on the specified R/3 application server. 8. Tasks for Managing R/3 Resources A dialog is presented in which you specify which adapter to start or stop. Controlling Application Servers Manager for R/3 provides the following tasks in the R3 App Server Tasks library to control R/3 application servers: Start Server Starts the specified R/3 application server. Stop Server Stops the specified R/3 application server. Tivoli Manager for R/3 User s Guide 133

156 Note: The stop command output may sometimes report an error with awk. This is caused when the SAP-provided stopsap script is called while a Tivoli monitor is running. This error does not affect the complete shutdown processing of the R/3 application server. Displaying Application Server Performance Information The following tasks enable you to display application server information for various application server buffers, roll and page areas, and operating system metrics. These tasks display the same information that the Manager for R/3 monitors report, except for percentages which are calculated. For more information about the information that is returned, each task in the following list includes a reference to the appropriate Manager for R/3 monitor. Display Buffer Information. See Buffer Source on page 213. This task presents a dialog in which you can specify the R/3 buffer type. The default is PXA Program Buffer. Display Roll Page Information. See Roll Area Source on page 209 and Page Area Source on page 210. Display OS Collect Information. See OS Collect Source on page 208. Display OS/390 Information. See OS/390 Source on page 217. Display OS/390 DB2 Information. See OS/390 DB2 Source on page 215. Managing Batch Jobs Manager for R/3 provides the following tasks to enable you to manage R/3 batch jobs: Display Batch Jobs Displays the following information for R/3 batch jobs: Date Job name Job ID 134 User s Guide Version 2.1

157 Scheduled by Released by Status Class Cancel Batch Job Cancels a batch job that is active. A dialog is displayed in which you enter the name and the job ID of the job you want to cancel. Use the Display Batch Jobs task to determine the appropriate job name and job ID. Release Batch Job Releases and starts a scheduled batch job. A dialog is displayed in which you enter the name and job ID of the job you want to release. Use the Display batch jobs task to determine the appropriate job name and job ID. Controlling R/3 Work Processes Manager for R/3 provides the following tasks to help you manage R/3 work processes: Display Work Processes Displays information for R/3 processes that are running on the specified application server. R/3 process information includes the process ID, status, reason, and CPU time. A dialog is displayed in which you can specify if you want the CPU time for each process to be returned as part of the data. Cancel Work Process Cancels an R/3 process. A dialog is displayed in which you specify the process ID and if you want a core dump. Use the Display Work Processes task to determine the appropriate process ID. 8. Tasks for Managing R/3 Resources Tivoli Manager for R/3 User s Guide 135

158 R3 DB Server Tasks The R/3 DB Server Tasks library contains the following tasks to help you manage an R/3 database: Type of Task Tasks Role Target Controlling a Database Server Controlling dbaccess Start Database Stop Database r3_user R3DBServer endpoint Start dbaccess r3_user R3DBServer endpoint Controlling a Database Server Manager for R/3 provides the following tasks to control the R/3 database server: Start Database Starts the R/3 database server. Stop Database Stops the R/3 database server. Notes: 1. When starting or stopping a UNIX database server, the start and stop tasks log on as sidadm and use the utilities of an application server on the same machine. The database server must be running on the same machine as an R/3 application server. The stop processing also stops all SID-related application servers on the node. 2. Starting or stopping a Windows NT database server requires customer exit routines. For more information, see Creating Exit Routines for Windows NT on page 72. Controlling dbaccess The Start dbaccess task starts dbaccess on the specified database server. The status of the start dbaccess job is displayed in the Start dbaccess Output dialog, and the dbaccess xterm window is 136 User s Guide Version 2.1

159 displayed. You can use structured query language (SQL) commands to access the R/3 database. Press the Ctrl-W key combination for help. Note: This task is only supported with a Motif windows manager and an Informix database. R3 ITS Server Tasks The R3 ITS Server Tasks library contains the following tasks to help you manage R/3 ITS servers: Type of Task Tasks Role Target Controlling ITS Servers Start ITS Server Stop ITS Server r3_user R3ITSServer endpoint Controlling ITS Servers Manager for R/3 provides the following tasks in the R3 ITS Server Tasks library to control R/3 ITS servers: Start ITS Server Starts the R/3 ITS server. Stop ITS Server Stops the R/3 ITS server. 8. Tasks for Managing R/3 Resources If the R3ITSServer object to which the Start ITS Server or Stop ITS Server task is distributed represents a single-host ITS server configuration, both the AGate and WGate components are started or stopped. If the R3ITSServer object represents one gate of a dual-host ITS server configuration, the gate (AGate or WGate) represented by the R3ITSServer object is started or stopped. Tivoli Manager for R/3 User s Guide 137

160 138 User s Guide Version 2.1

161 9 Distributing SAPGUI Software This chapter describes how to create SAPGUI software file packages for distribution of the SAPGUI for Windows NT, Windows 95/98, and UNIX, and it describes how to distribute SAPGUI software file packages. Note: The tasks to create SAPGUI software file packages create profile managers and profiles as a result of their processing. For these actions to succeed, the administrator running these tasks must also have the Tivoli super role. Creating SAPGUI Software File Packages The method you choose to create SAPGUI software file packages depends upon the version of the SAPGUI software you want to distribute. Follow one of these procedures: For Windows NT and Windows 95/98 SAPGUI versions prior to 4.5B and for all UNIX SAPGUI versions, see Creating SAPGUI File Packages for SAPGUI Versions Prior to 4.5B on page Distributing SAPGUI Software Note: Software Distribution must be installed on the TMR server. For Windows NT and Windows 95/98 SAPGUI versions 4.5B and later, see Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later on page 143. Tivoli Manager for R/3 User s Guide 139

162 Note: Software Distribution must be installed on the R/3 SAPGUI installation server, and SAP requires that the R/3 SAPGUI installation server resides on a Windows NT machine. Creating SAPGUI File Packages for SAPGUI Versions Prior to 4.5B You can create various file packages with different options and configurations. Each file package is identified by the name you specify when you create the file package. You can configure SAPGUI file packages by using either a reference installation or by using an R/3 native installation. To perform a reference installation, you first install and configure a copy of the SAPGUI. Files in this reference copy are distributed directly to the endpoints. An R/3 native installation assumes that the SAPGUI CD-ROM image is available on the target systems and installs directly on the target from the CD-ROM, using R/3 installation tools and procedures. To create SAPGUI software file packages for distribution of the SAPGUI for Windows NT and Windows 95/98 prior to Version 4.5B and for all UNIX versions, follow these steps: 1. From the Tivoli desktop, open the Manager for R3 policy region to display the Policy Region: Manager for R3 window. 2. Open the R3 Configuration policy region to display the Policy Region: R3 Configuration window. 3. Open the R3 Configuration Tasks library to display the configuration tasks. 4. Run one of the following tasks or jobs: Configure Client Install This is a reference copy installation. You must manually install one SAP client with the R/3 SAPGUI and copy the files to the TMR server before executing this job. For Windows NT and Windows 95/98 installations, you must copy the DLLs to a subdirectory named dll under the directory in which the source code resides. 140 User s Guide Version 2.1

163 The AFTER script creates entries on the Windows NT and the Windows 95/98 Start menus for sapgui.exe, saplogon.exe, and sapicon.exe. On Windows NT targets, the AFTER script will be able to find the location of the sapgui.exe, saplogon.exe, and sapicon.exe executables regardless of where they exist within the source code. On Windows 95/98 targets, you must place these executables at the root of the directory in which the source code resides. Configure UNIX Client Install This is an R/3 native installation. Configure Windows 95/98 Client Install This is an R/3 native installation. Configure Windows NT Client Install This is an R/3 native installation. The platform-specific Configure Client Install dialog is displayed. For example, the following dialog is displayed as a result of 9. Distributing SAPGUI Software Tivoli Manager for R/3 User s Guide 141

164 running the Configure Windows NT Client Install task. For information about completing the dialog, refer to the online help. When you create a SAPGUI software file package, a new profile manager is created in the R3 Configuration policy region that is labeled Install Clients (ConfigurationName), where ConfigurationName is the name you associated with the file package when you created the file package. The profile manager contains the file package for the specified configuration. For reference installations, the file package includes BEFORE and AFTER programs and the directory from which the SAPGUI installation will be copied. For native installations, the file package includes BEFORE and AFTER programs. The SAPGUI installation CD from SAP must be accessible on the target machine. If you are distributing the SAPGUI to several machines in one distribution, you 142 User s Guide Version 2.1

165 can choose to mount the SAPGUI CD on a network shared drive. If you need to mount the SAPGUI CD during installation, you should consider using the optional command fields on the platform-specific Configure Client Install dialog. Creating SAPGUI File Packages for Windows SAPGUI Versions 4.5B and Later For Windows NT and Windows 95/98 SAPGUI version 4.5B and and later, SAPGUI file packages are created on an R/3 SAPGUI installation server using R/3 tools and procedures. Manager for R/3 provides tasks that enable you to determine the appropriate file package to distribute and a task that enables you to create a file package which, when distributed, installs the SAPGUI software. Because these tasks run against the SAPGUI installation server, the SAPGUI installation server must be defined as a managed node and Manager for R/3 must be installed on the SAPGUI installation server. To create SAPGUI file packages for distribution of the SAPGUI for Windows NT and Windows 95/98, follow these steps: 1. Optionally, determine the names of the file packages that are available on the R/3 SAPGUI installation server. If you know the exact name of the file package you want to distribute, proceed to step 2 on page 144. Otherwise, run the List Available SAPGUI File Packages task in the R3 Configurations Task library to display the Listing of Available Packages dialog. 9. Distributing SAPGUI Software The task output lists the names the SAPGUI file packages for the selected version. Tivoli Manager for R/3 User s Guide 143

166 2. Optionally, determine the details about a SAPGUI file package. If you know which file package you want to distribute, proceed to step 3. Otherwise, run the List SAPGUI Package Features task in the R3 Configuration Tasks library to display the Package Features dialog. For information about completing the dialog, refer to the online help. The task output lists the details about the specified file package. 3. Create the SAPGUI file package for distribution. Run the Configure SAPGUI Package task in the R3 Configuration Tasks library to display the Install Package dialog. 144 User s Guide Version 2.1

167 For information about completing the dialog, refer to the online help. A profile manager named SAPGUI Installation Server Packages is created, if it does not already exist, in the R3 Configuration policy region. This profile manager contains the SAPGUI file package you created. The file package contains only an AFTER program that initiates installation of the SAPGUI file package from the installation server. Each file package you create is identified by the name of the SAPGUI file package you specified when you created the file package. Distributing SAPGUI Software You perform the SAPGUI installations by distributing the file package to the subscribers you specified. For native installations on UNIX, the installation is performed by calling the car program. Each selectable SAPGUI option corresponds to a car file that will be unpacked during installation. For native installations of SAPGUI versions prior to 4.5B on Windows NT and Windows 95/98, the installation is performed by calling the SAP-provided sapsetup program. Note: For Windows 95/98 installations, the sapsetup program returns control to the installation AFTER program before sapsetup actually completes its processing. If errors occur in the sapsetup program on Windows 95/98, these errors will not be reported back to Tivoli during the file package distribution. For installations of SAPGUI versions 4.5B and later on Windows NT and Windows 95/98, the installation is performed by using SAP-provided tools to install the SAPGUI file package from an installation server. 9. Distributing SAPGUI Software Note: Depending on the configuration of the SAPGUI installation server, you might be restricted to installing the Tivoli Manager for R/3 User s Guide 145

168 SAPGUI file package on a machine that is in the same NT domain as the SAPGUI installation server. Before distributing the file packages, ensure that the subscriber list for the profile manager has been updated with the appropriate endpoints or subscriber lists. Double-click the appropriate file package profile manager to display the Profile Manager window. From the Profile Manager menu, select Subscribers and complete the Subscribers dialog. After you have set the subscribers for the profile manager, follow these steps to distribute the file package: 1. Open the appropriate profile manager to display the Profile Manager window. 2. If you are distributing the file package to TMA endpoints, follow these steps to change the file package profile manager from database mode to dataless mode: a. From the Profile Manager window, from the Edit menu, select Profile Manager to display the Edit Profile Manager dialog. b. Select Dataless Endpoint Mode. Then click Change & Close. Note: Refer to the TME 10 Framework User s Guide for more information about database mode and dataless mode profile managers. 3. Right-click the file package icon and select Distribute from the pop-up menu. 4. Complete the Distribute File Package dialog, referring to the online help for additional information. For more information, refer to the TME 10 Software Distribution User s Guide. 146 User s Guide Version 2.1

169 10 Tivoli GEM Instrumentation 10. Tivoli GEM Instrumentation You can optionally manage R/3 resources from the Tivoli GEM console. To do this, you must install the following: 1. Tivoli Manager for R/3, Version 2.1 (Manager for R/3) 2. Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 (Tivoli GEM instrumentation) This chapter provides an overview of Tivoli GEM instrumentation and describes the installation prerequisites and the steps to install Tivoli GEM instrumentation. It also describes how to uninstall Tivoli GEM instrumentation. For more information about Tivoli GEM, refer to the Tivoli GEM product documentation. Tivoli GEM defines the concept of a business system to organize related applications. A business system includes all the applications that together perform a business function, such as R/3 processing. It also includes performance measures that determine whether the business system is functioning properly. For example, an R/3 business system would include all the instances of the R/3 system, R/3 ITS server resources, R/3 application server resources, and their associated database server resources. The business system includes the following: Tasks that can initiate actions against an R3System, an R3Application, an R3Database, and an R3ITSServer component instance Tivoli Manager for R/3 User s Guide 147

170 Monitors that report status information about R3Application, R3Database, and R3ITSServer resource components Tivoli GEM consists of a Tivoli GEM server that runs as an application on a managed node and a Tivoli GEM console. Tivoli GEM uses application instrumentation to get the necessary data to display and manipulate business systems, such as R/3. Tivoli GEM instrumentation enables you to graphically monitor and control R/3 resources that reside on a Tivoli managed node or TMA endpoint. Understanding the Tivoli GEM Server The Tivoli GEM server interacts with instrumented applications, such as the Manager for R/3, to provide information for display on the Tivoli GEM console. The Tivoli GEM server is the recipient of heartbeat events from instrumented application components and determines the business system to which a component belongs. The Tivoli GEM server also queries instrumented applications for related components and the status of their monitors. Using this information, Tivoli GEM creates and maintains a view of the configuration of each business system and the availability of the business system. The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable for a component. These tasks appear in context-sensitive menus on the Tivoli GEM console. The Tivoli GEM server also stores files on behalf of the Tivoli GEM console, including icons, backgrounds, help files, log files, customization views, and settings. Understanding the Tivoli GEM Console The Tivoli GEM console graphically displays the business system information from the Tivoli GEM server. The Tivoli GEM console does the following: Displays each component as a separate icon. Draws lines between icons to denote links. Uses color to indicate the status of each component and the status of the entire business system. 148 User s Guide Version 2.1

171 As the Tivoli GEM server receives status updates pertaining to the business systems, it updates the Tivoli GEM console, enabling you to view the real-time status of the business system. Tivoli GEM supports aggregation, which is a logical grouping of instances of the same or different component types. Tivoli GEM instrumentation provides for the automatic aggregation of all R/3 component instances based on the system to which they belong. Thus the initial top-level view on the Tivoli GEM console shows system aggregate icons. Aggregates are depicted on the Tivoli GEM console view with a plus sign by their icon. Opening a system aggregate produces a view with the contained R3System, R3Application, R3Database, and R3ITSServer component instances within that system aggregate. The instrumented aggregation is predefined in business system component, business system mapping, and software component description files. 10. Tivoli GEM Instrumentation Tivoli GEM Instrumentation Event Handling The Tivoli GEM server discovers the R/3 components upon receipt of heartbeat events. As the Tivoli GEM server receives monitor and status updates for the R/3 business system, it updates the Tivoli GEM console. Tivoli GEM Event Enablement must be installed and configured on the TEC event server for Tivoli GEM events to be supported by the Tivoli Enterprise Console (TEC). Configuring Tivoli GEM Event Enablement includes defining the APM_HEARTBEAT and APM_THRESHOLD event classes to TEC and defining the Tivoli GEM servers to which the Tivoli GEM events will be forwarded. You must also add the Tivoli GEM instrumentation rule set to the current rule set. See Adding the Tivoli GEM Instrumentation Rule Set on page 154. Tivoli Manager for R/3 User s Guide 149

172 Instrumented Components Tivoli GEM instrumentation includes instrumentation for the components which correspond to each Manager for R/3 object as described in the following table: Manager for R/3 Instrumentation Component R3System R3Application R3Database R3ITSServer Manager for R/3 Object R3System R3AppServer R3DBServer R3ITSServer Instrumentation Task Libraries Successful installation of Tivoli GEM instrumentation creates task libraries that are visible on the Tivoli desktop. The following is an overview of the resulting desktop structure: Top-Level Policy Region Applications_Hostname-region Policy Region PR_SAPR3_Default_Hostname-region Task Libraries TL_SAPR3_2.1._Default_R3System_2.1._Hostname-region TL_SAPR3_2.1._Default_R3Application_2.1._Hostname-region TL_SAPR3_2.1._Default_R3Database_2.1._Hostname-region TL_SAPR3_2.1._Default_R3ITSServer_2.1._Hostname-region Note: Hostname is the host name of the TMR server. Preparing to Install Manager for R/3 Instrumentation Review the topics in the following sections before installing Tivoli GEM instrumentation. Tivoli Management Regions Tivoli Management Regions (TMRs) should be properly configured before installing Tivoli GEM instrumentation. 150 User s Guide Version 2.1

173 Administrators Tivoli administrators need the following authorization roles: To install Tivoli GEM instrumentation, install_product authority is required. To start tasks from the Tivoli GEM console, r3_user authority is required for the user ID that you use to log on to the Tivoli GEM console. Installation Prerequisites 10. Tivoli GEM Instrumentation Before installing Tivoli GEM instrumentation, you must install and configure Framework, TEC, Manager for R/3, and Tivoli GEM. The TEC event server must be running in each TMR in which Tivoli GEM instrumentation is installed. Installing and Configuring Tivoli GEM Instrumentation for Manager for R/3 The following table shows the location of the installed components: Installed Component Instrumentation definition files Instrumentation task libraries Target Nodes Tivoli GEM TMR server Server X X To install Tivoli GEM instrumentation, follow the steps in the remaining sections of this chapter. Installing or Upgrading the Tivoli GEM Instrumentation Definition Files If you are installing the Tivoli GEM instrumentation definition files for the first time or if you have Tivoli GEM instrumentation Version 2.0 installed and are upgrading to Version 2.1, you must load the new applications management package (AMP) file. To do this, from Tivoli Manager for R/3 User s Guide 151

174 the Tivoli GEM console File menu, select Load New AMP. Then select /GEMFILES/sapr3_21.pkg from the Manager for R/3 CD. Installing the Tivoli GEM Instrumentation Task Libraries Install the Tivoli GEM instrumentation task libraries from the Tivoli desktop. Do one of the following: If you have Tivoli GEM instrumentation Version 2.0 installed, see Upgrading the Tivoli GEM Instrumentation Task Libraries. If you are installing Tivoli GEM instrumentation for the first time, see Installing the Tivoli GEM Instrumentation Task Libraries. Upgrading the Tivoli GEM Instrumentation Task Libraries To upgrade the Tivoli GEM instrumentation task libraries from Version 2.0 to Version 2.1, back up the Tivoli database. Then, install Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 (Upgrade from Version 2.0) from the Tivoli desktop as a patch. Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 (Upgrade from Version 2.0) is located in the /UPGD_GEM directory on the Manager for R/3 CD. The upgrade patch replaces Version 2.0 task libraries with Version 2.1 task libraries. After installing the upgrade patch, delete Version 2.0 objects from the Tivoli GEM console and run the Send GEM Heartbeat task in the R3 Configuration Tasks library to synchronize the Tivoli GEM console with the Manager for R/3 objects on the desktop. Installing the Tivoli GEM Instrumentation Task Libraries To install the Tivoli GEM instrumentation task libraries, follow these steps from the Tivoli desktop: 1. Back up the Tivoli database. 2. From the Install menu, click Install Product to display the Install Product dialog. 3. Click Select Media to display the File Browser dialog, from which you specify the path to the installation media. 152 User s Guide Version 2.1

175 4. Enter the full path to the Tivoli GEM instrumentation installation files in the Path Name text field. The Tivoli GEM instrumentation files are located in the /GEMIMAGE directory on the Manager for R/3 CD. 5. Click Set Path. The File Browser dialog displays the contents of the specified media in the Files scrolling list. 6. Click Set Media & Close. The Install Product dialog is displayed with Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 listed in the Select Product to Install scrolling list. 10. Tivoli GEM Instrumentation 7. Select Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version Click the targets on which you do not want to install Tivoli GEM instrumentation from the Clients to Install On list and Tivoli Manager for R/3 User s Guide 153

176 click the right arrow button to move them to the Available Clients list. Install the Tivoli GEM instrumentation task libraries on the TMR server. 9. Click Install & Close. The Product Install window is displayed, listing the actions that will be taken when you complete the installation process. 10. Click Continue Install to begin the installation process. The Product Install window continues to display messages that show the progress of the installation. Successful installation is indicated by a Finished product installation message. 11. Click Close. 12. After installing the Tivoli GEM instrumentation task libraries, backup the Tivoli database. The Tivoli GEM instrumentation task libraries are installed in the PR_SAPR3_Default_Hostname-region policy region which is within the Applications_Hostname-region on the desktop. Adding the Tivoli GEM Instrumentation Rule Set The Tivoli GEM instrumentation rule file, sap_gemevents.rls, includes TEC rules that forward all Manager for R/3 monitor events to the Tivoli GEM server. To add the sap_gemevents.rls to the current rule set, use the Manager for R/3 Configure Event Server task. See Configuring the TEC Event Server on page 82. Note: If you ran the Configure Event Server task before you installed Tivoli GEM instrumentation, you must run the Configure Event Server task again to install the sap_gemevents.rls rule file. Synchronizing the Tivoli GEM Console with the Desktop The Tivoli GEM console is synchronized with the Manager for R/3 objects on the desktop. When an R/3 object is created, a heartbeat event is automatically sent to the TEC event server. The TEC event server forwards the event to the Tivoli GEM server, and an icon is 154 User s Guide Version 2.1

177 displayed on the Tivoli GEM console. If the Tivoli GEM console becomes unsynchronized with the desktop, run the Send GEM Heartbeat task in the R3 Configuration Tasks library (see Using Manager for R/3 Configuration Tasks on page 35) against the appropriate R3System, R3AppServer, R3DBServer, and R3ITSServer objects. The Send GEM Heartbeat task sends a heartbeat event to the Tivoli GEM server for each R/3 resource, and an icon is created on the Tivoli GEM console, if needed. The Tivoli GEM console might not be synchronized with the desktop if the Tivoli GEM server was down when the R/3 object was created, if you installed Tivoli GEM instrumentation after you created the R/3 objects, or if the Tivoli GEM databases are erased. Understanding R/3 Aggregate Resources Icons representing aggregates of R/3 resources are automatically provided on the Tivoli GEM console. A Manager for R/3 icon is the highest-level aggregate resource. 10. Tivoli GEM Instrumentation Double-click the Manager for R/3 icon to display the R/3 system aggregate icons. Double-click an R/3 system aggregate icon to display the R/3 system, R/3 application server, R/3 database server, and R/3 ITS server icons. Resources might not be aggregated if the internal aggregation tasks timed out. To manually aggregate resources, right-click a resource icon and select Add to Aggregate. Select the aggregate to which you want to add the resource. Alternatively, you can synchronize the resources from the Tivoli desktop. See Synchronizing the Tivoli GEM Console with the Desktop on page 154. Navigating to R/3 Resources On the Tivoli GEM console, you navigate from an R/3 system aggregate icon to a specific R/3 system, R/3 application server, R/3 database server, and R/3 ITS server icon. Right-click individual R/3 resources to access the pop-up menu from which you can select tasks. Tivoli Manager for R/3 User s Guide 155

178 To locate a specific R/3 resource: 1. Open the Tivoli GEM Console. 2. Expand the Applications icon displayed in the tree view. The Applications window is displayed containing the Manager for R/3 icon as shown in the following figure. If the view is empty, ensure that you have created R/3 objects. 3. Display the R/3 system aggregate icons by double-clicking the box containing the + on the Manager for R/3 icon. 156 User s Guide Version 2.1

179 4. Open the R/3 system aggregate icon to view the R/3 system, R/3 application servers, R/3 database server, and R/3 ITS server icons. 10. Tivoli GEM Instrumentation Tivoli GEM Instrumentation Tasks The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable against a component. To display the task menu, highlight and right-click a component icon. The tasks enable Tivoli GEM users to perform actions on the component instance and to return task results to the Tivoli GEM console. The tasks that are supported for each component are defined in business system mapping and software component definition files that reside on the Tivoli GEM server. Installation of Tivoli GEM instrumentation creates a task library for the R3System, the R3Application, the R3Database, and the R3ITSServer instrumented components. Each task library contains the tasks that are supported from Tivoli GEM for that component. R3System Component Tasks Tivoli GEM supports the following subset of Manager for R/3 tasks for the R3System component: Tivoli Manager for R/3 User s Guide 157

180 Start_System Stop_System See R3 System Tasks on page 131 for more information about these tasks. R3Application Component Tasks The following Tivoli GEM instrumentation task is available for the R3Application component: Query_State reports whether the R/3 application server is up (running and accepting R/3 logons), standby, or down (not running, or running and not accepting R/3 logons). Tivoli GEM also supports the following subset of 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 132 for more information about these tasks. R3Database Component Tasks Tivoli GEM supports the following subset of Manager for R/3 tasks for the R3Database component: Query_State reports whether the R/3 database server is up, unknown, or down. Tivoli GEM also supports the following subset of Manager for R/3 tasks for the R3Database component: Start_Database 158 User s Guide Version 2.1

181 Stop_Database See R3 DB Server Tasks on page 136 for more information about these tasks. R3ITSServer Component Tasks Tivoli GEM supports the following Manager for R/3 tasks for the R3ITSServer component: Query_State reports whether the R/3 ITS server is up, unknown, or down. Tivoli GEM also supports the following subset of Manager for R/3 tasks for the R3ITSServer component: 10. Tivoli GEM Instrumentation Start_ITS_Server Stop_ITS_Server See R3 ITS Server Tasks on page 137 for more information about these tasks. Using the Tear-Away Log Before starting a task, open the tear-away log provided by the Tivoli GEM console. The log provides current messages that show the progress of tasks you run. To open the tear-away log, from the Options menu, select Tear Away Log. Running a Task from the Tivoli GEM Console Tivoli GEM instrumentation tasks, in addition to Manager for R/3 tasks, are contained in the task libraries in the PR_SAPR3_Default_hostname-region policy region as described in Instrumentation Task Libraries on page 150. On the Tivoli GEM console, you can run instrumented tasks from the pop-up menu for the R/3 system, the R/3 application server, the R/3 database server, and the R/3 ITS server icons. Note: Tivoli GEM instrumentation tasks that are contained in the task libraries but are not listed on the pop-up menu for an icon support the internal processing of Tivoli GEM functions and are not intended to be run by Tivoli GEM users. To run a task from the Tivoli GEM console, follow these steps: Tivoli Manager for R/3 User s Guide 159

182 1. Right-click an icon, such as an R/3 application server icon. From the pop-up menu, select the appropriate task, such as Display_Work_Processes. 2. In this example, the GEM Log window provides information about the R/3 work processes. Supported Monitors The Tivoli GEM console displays an icon for each monitor instance that is supported. The monitor instance icon changes color based on the severity of the monitor events received for that monitor. The R/3 application server, R/3 database server, or R/3 ITS server icon changes color based on the aggregate of the monitor status. Tivoli GEM instrumentation supports the following Manager for R/3 monitors 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 160 User s Guide Version 2.1

183 Update Performance Batch Performance Spool Performance OS Collect - Application Server See Remote and Central Monitoring Sources on page 207 for more information. 10. Tivoli GEM Instrumentation Tivoli GEM instrumentation also supports the Database Server Status and ITS Server Status monitors for the R3Database and R3ITSServer components, respectively. Monitor Operability Tivoli GEM instrumentation includes a TEC rule that forwards all Manager for R/3 monitor events to the Tivoli GEM server. When a supported monitor specifies that a TEC event be sent when a threshold is exceeded, that monitor event will be forwarded to the Tivoli GEM server from the TEC. The Tivoli GEM console displays an icon for each monitor instance that is supported. If a monitor supports multiple arguments, then each argument (or combination of arguments) defines an instance. A pop-up menu is available from each monitor instance icon, which contains the Query_Thresholds task. This task sends a monitor event to TEC that contains the last monitor event status if the monitor had been triggered. Viewing Monitor Status To view the status of supported monitors on the Tivoli GEM console, expand an icon for a specific R/3 server resource to display Tivoli Manager for R/3 User s Guide 161

184 the monitor status window. Instrumenting Tivoli GEM Connection Support to R/3 Components To instrument components that provide connections to R3System, R3Application, R3Database, or R3ITSServer components, you must instrument the connection in your component instrumentation. The following description provides the values required to define a connection from applications, such as MQSeries, to R3System, R3Application, R3ITSServer, or R3Database components. For more information, refer to the Tivoli Global Enterprise Manager Instrumentation Guide. To create a connection to an R/3 component, define the following parameters in the Application Management Specification (AMS)-specified format: Connection type Connection direction Communication object information (origin/suborigin name value pair that matches the information in the origin/suborigin slots of the component heartbeat to which the initiator wants to connect) Note: For a copy of the AMS, point your Web browser to: 162 User s Guide Version 2.1

185 Instrumenting a Connection to an R3System Component The R/3System component supports the following parameters: Connection type: R3System Connection direction: 3 < > conversational 10. Tivoli GEM Instrumentation (origin, suborigin): v v v (0=R3System=SAPR3, 0=R3System=instance_label) (1=TCPIPAddress, 0=R3System=instance_label) (2=Hostname, 0=R3System=instance_label) Where instance_label is in the format SID_DBhostname (SID is the three-character R/3 system identifier, and DBhostname is the host name of the database server). Example: To connect a component to R/3 system TV4_dbserv, define a discover connections task that returns the following string: (AMS_DC"R3System",3,"0=R3System=SAPR3","0=R3System=TV4_dbserv",,) Instrumenting a Connection to an R3Application Component The R3Application component supports the following parameters: Connection type: R3Application Connection direction: 3 < > conversational (origin, suborigin): v v v (0=R3Application=SAPR3, 0=R3Application=instance_label) (1=TCPIPAddress, 0=R3Application=instance_label) (2=Hostname, 0=R3Application=instance_label) Tivoli Manager for R/3 User s Guide 163

186 Example: Where instance_label is in the format Hostname_SID_IID (Hostname is the host name of the application server, SID is the three-character R/3 system identifier, and IID is the two-digit R/3 instance number. To connect a component to R/3 application server harrier_tv4_60, define a discover connections task that returns the following string: (AMS_DC"R3Application",3,"0=R3Application=SAPR3", "0=R3Application=harrier_TV4_60",,) Instrumenting a Connection to an R3ITSServer Component The R3ITSServer component supports the following parameters: Connection type: R3ITSServer Connection direction: 3 < > conversational (origin, suborigin): v v v (0=R3ITSServer=SAPR3, 0=R3ITSServer=instance_label) (1=TCPIPAddress, 0=R3ITSServer=instance_label) (2=Hostname, 0=R3ITSServer=instance_label) Where instance_label is in the format Hostname_VIIN_ITS (Hostname is the host name of the R/3 ITS server, and VIIN is the virtual ITS instance name. Example: To connect a component to R/3 ITS server tcasstev_tmc_its, define a discover connections task that returns the following string: (AMS_DC"R3ITSServer",3,"0=R3ITSServer=SAPR3", "0=R3ITSServer=tcasstev_TMC_ITS",,) Instrumenting a Connection to an R3Database Component The R3Database component supports the following parameters: Connection type: R3Database 164 User s Guide Version 2.1

187 Connection direction: 3 < > conversational (origin, suborigin): v (0=R3Database=SAPR3, 0=R3Database=instance_label) v (1=TCPIPAddress, 0=R3Database=instance_label) v (2=Hostname, 0=R3Database=instance_label) Where instance_label is in the format Hostname_SID_DB (Hostname is the host name of the R/3 database server, and SID is the three-character R/3 system identifier. 10. Tivoli GEM Instrumentation Example: To connect a component to R/3 database server hound_tv4_db, define a discover connections task that returns the following string: (AMS_DC"R3Database",3,"0=R3Database=SAPR3", "0=R3Database=hound_TV4_DB",,) Uninstalling Tivoli GEM Instrumentation Task Libraries To uninstall Tivoli GEM instrumentation Version 2.1 task libraries, go to the $BINDIR/../generic_unix/TME/SAPUNINST directory on the TMR server and enter the following command: R3Mgr_uninstall21.pl g Note: Optionally, use the yes parameter to uninstall Tivoli GEM instrumentation task libraries without being prompted for confirmation. The R3Mgr_uninstall21.pl g command uninstalls the Tivoli GEM instrumentation task libraries but does not remove the definition files from the Tivoli GEM server or clean up the Tivoli GEM server. Tivoli Manager for R/3 User s Guide 165

188 166 User s Guide Version 2.1

189 A Command Line Interface Commands Manager for R/3 uses the wr3mib and wr3rfc commands to support its internal processing. These commands can be run directly from a command line to support diagnostic processing as described in Troubleshooting on page 255. This appendix describes the Manager for R/3 commands and their syntax. Command Line Syntax The commands in this appendix use the following special characters to define the command syntax: [] Identifies an optional argument. Arguments not enclosed in brackets are required.... Indicates that you can specify multiple values for the previous argument. Indicates mutually exclusive information. You can use the argument to the left of the separator or the argument to the right of the separator. You cannot use both arguments in a single use of the command. {} Delimits a set of mutually exclusive arguments when one of the arguments is required. If the arguments are optional, they are enclosed in brackets ([ ]). For example: Tivoli Manager for R/3 User s Guide 167 A. Command Line Interface Commands

190 wr3mib a [ C Class] [ S Severity] [ n systemnumber] The a flag is the only required argument for this version of the wr3mib command. The brackets around the other arguments indicate that 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 arguments are optional. SysMan and RFC Commands The following table lists the Manager for R/3 commands and their purposes: Command wr3mib wr3rfc Purpose Reads the SysMan for monitoring information. Provides remote execution of R/3 function modules. 168 User s Guide Version 2.1

191 wr3mib Reads 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 as the wr3mib command. Synopsis wr3mib { 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 Description The wr3mib command reads the SysMan and reports the information to stdout. Arguments f Prints all SysMan information. a Prints the SysMan alert table. Optional parameters for the a argument include: C Class Specifies the alert class number to filter. For more information, see R/3 Alert Event Classes on page 180. S Severity Specifies the alert severity number (0 to 3) to filter. n systemnumber Specifies the instance number to filter. The default is all systems. c Prints the SysMan configuration table. p Prints the SysMan performance table. Tivoli Manager for R/3 User s Guide 169 A. Command Line Interface Commands

192 s Prints the SysMan system table. d Writes debug information to stderr. n systemnumber Specifies the R/3 instance number. Only one systemnumber is permitted. P PerfAttr Specifies the performance attribute character (F = Frequency, R = Resp, W = Wait). The T argument must be used with this argument. T ServType Specifies the performance attribute type number (1 for dialog, 2 for update, 3 for batch, or 4 for spool). t iterations polling_delay Prints SysMan trap information, where iterations specifies the number of times to query the SysMan and polling_delay specifies the amount of time between iterations. If you do not enter a value for iterations, the default is infinite. You must specify a value for iterations if you want to specify a value for polling_delay. The default for polling_delay is 60 seconds. 170 User s Guide Version 2.1

193 wr3rfc Provides remote execution of SAP R/3 function modules. Synopsis wr3rfc [-d -c -u -p -l t -h -s -g -x -D -C -?] rfc_interface [arg]... Description Manager for R/3 includes a program that enables you to write simple ASCII control files to interface with R/3 RFC, rather than having to write C programs to accomplish this task. This capability greatly simplifies this task and reduces the time that is required to execute SAP modules from outside the SAP system. The wr3rfc command reads two ASCII files: a configuration file and an rfc_interface file. It is recommended that the configuration file contain only command line arguments and the rfc_interface file contain only stanza labels and keywords. The configuration file and rfc_interface file can specify any of the command line arguments for the wr3rfc command except the following 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 is encountered. Tivoli Manager for R/3 User s Guide 171 A. Command Line Interface Commands

194 CLI Parameter Name The wr3rfc command uses information from the rfc_interface file to populate the appropriate data structures for the RFC API calls. Notes: 1. A sample configuration file, wr3rfc_cfg.txt, is provided in one of the following directories: Managed node: $BINDIR/../generic_unix/TME/SAP/2.2C/rfc TMA endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP/2.2C/rfc 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 line and configuration file entries. For example, -dparm is equivalent to -d parm and DESTINATION=PARM is equivalent to DESTINATION = 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 remote function call parameters listed in the following table, see Configuring User IDs for RFC Interface Access on page 49. The configuration file and command line interface allow any of the following parameters: Configuration File Parameter Name COMMAND OPTIONS: Description Indicates the start of stanzas. d DESTINATION= The 3-character R/3 system ID. c CLIENT= Specifies the 3-digit client sign-on data. u USER= Specifies the user ID. p PASSWORD= Specifies the unencrypted password. l LANGUAGE= Specifies the single-character language identifier. E is English. 172 User s Guide Version 2.1

195 CLI Parameter Name Configuration File Parameter Name Description 2 or 3 MODE= CLI values are 2 or 3. The default is 3, which is R/3 mode. 2 specifies CPIC mode. The MODE parameter value is also2or3. t TRACE= Controls tracing of an R/3 remote function call (RFC). YES turns tracing on. NO turns tracing off. The output of this trace is a file named dev_rfc. The file is in the working directory of the wr3rfc program. h HOSTNAME= The target host. Enter a target host name such as myhost. s SYSTEMNUMBER= Specifies the R/3 server instance number (00..96). g GATEWAYHOST= Specifies the gateway host. If the g argument is not used, the h argument is used. x GATEWAYSERVICE= Specifies the TCP/IP service of the gateway. The default is sapgwnn, where NN is the system number that is specified with the s argument. C Command line entry only. Specifies the configuration file. The default is./.wr3rfc_cfg. D Command line entry only. Specifies the debug level: 1. High level processing 2. Lower level processing 3. Configuration file parsing? Command line entry only. Displays help for the wr3rfc command. Stanzas in the rfc_interface file include: Tivoli Manager for R/3 User s Guide 173 A. Command Line Interface Commands

196 Stanza Keywords Description MODULE Required. This is the name of the R/3 function module such as J_8C1_BUFFER_NAMES. EXPORT PARAMETER: IMPORT PARAMETER: NAME LENGTH VALUE TYPE NAME TYPE LENGTH FORMAT Represents a stanza identifier. All export parameter stanzas should precede the first import parameter or import table stanza. Note: The maximum number of export parameters you can specify is 64. Defines a single field such as EXPORT1, sent to the RFC program. The value of length is greater than or equal to the length of the parameter to be exported to R/3. For LENGTH of TYPX, LENGTH is equal to the number of characters entered. Every two characters are converted to one byte for R/3. Defines the value of the field being exported. Specifies the data type of the NAME value. Allowable types include: [TYPC TYPNUM TYPX TYPP TYPINT TYPINT1 TYPINT2 TYPFLOAT TYPDATE TYPTIME ]. Represents a stanza identifier. Note: The maximum number of import parameters you can specify is 64. Defines a single field such as IMPORT1, returned from the RFC program. Specifies the data type of the NAME value. Allowable types include: [TYPC TYPNUM TYPX TYPP TYPINT TYPINT1 TYPINT2 TYPFLOAT TYPDATE TYPTIME ]. Defines the length of the field being imported, such as 250. Possible values are VERBOSE (print output in the form: keyword=value) or RESULT (print output in the form: value). 174 User s Guide Version 2.1

197 Stanza Keywords Description IMPORT TABLE: Stanza identifier: 1. IMPORT TABLE has to be the last stanza in the command file. 2. Only one import table stanza is supported. Function modules that export multiple tables are not supported by the wr3rfc program. TABLENAME Defines the table such as IMPTA1, returned from the RFC program. This name must correspond to the table name in the R/3 function module. NAME Defines the name to represent a column field in the table. Columns with different data types are supported. TYPE Defines the data type of the NAME value. Allowable types include: [TYPC TYPNUM TYPX TYPP TYPINT TYPINT1 TYPINT2 TYPFLOAT TYPDATE TYPTIME ]. LENGTH The CLNT data type in R/3 tables should be entered as TYPC in the cmd file. Specifies the length of the table column returned from the RFC program, such as 250, with the following rules: 1. LENGTH keyword is not needed for data types TYPINT, TYPINT1, TYPINT2, TYPFLOAT, TYPDATE, and TYPTIME. 2. For LENGTH of TYPX, LENGTH equals the number of bytes of data. When displayed, each byte is represented as two characters. Examples The following example runs the command specified in the RfcFile command file on system TV1 on SAP system number 00 on host tron: wr3rfc -h tron -d TV1 -s 00 RfcFile This example uses the configuration file (./.wr3rfc_cfg): Tivoli Manager for R/3 User s Guide 175 A. Command Line Interface Commands

198 COMMAND OPTIONS: CLIENT = 000 USER = SAP* PASSWORD = LANGUAGE = E MODE = 3 TRACE = NO # These are for CPIC only #GATEWAYHOST = gatehost #GATEWAYSERVICE = sapgw00 This example uses the rfc_interface file: COMMAND OPTIONS: MODULE = TH_WPINFO EXPORT PARAMETER: NAME = SRV_NAME TYPE = TYPC LENGTH = 20 EXPORT PARAMETER: NAME = WITH_CPU TYPE = TYPX LENGTH = 1 IMPORT TABLE: TABLENAME = WPLIST NAME = WP_NO TYPE = TYPC LENGTH = 2 NAME = WP_ITYPE TYPE = TYPC LENGTH = 3 NAME = WP_PID TYPE = TYPC LENGTH = 8 NAME = WP_ISTATUS TYPE = TYPINT1 NAME = WP_STATUS TYPE = TYPC LENGTH = 7 NAME = WP_IWAIT TYPE = TYPINT1 NAME = WP_WAITING TYPE = TYPC LENGTH = 5 NAME = WP_SEM TYPE = TYPC LENGTH = 2 NAME = WP_IRESTRT TYPE = TYPINT1 NAME = WP_RESTART 176 User s Guide Version 2.1

199 TYPE = TYPC LENGTH = 4 NAME = WP_DUMPS TYPE = TYPC LENGTH = 2 NAME = WP_CPU TYPE = TYPC LENGTH = 8 NAME = WP_ELTIME TYPE = TYPC LENGTH = 6 NAME = WP_MANDT TYPE = TYPC LENGTH = 3 NAME = WP_BNAME TYPE = TYPC LENGTH = 12 NAME = WP_REPORT TYPE = TYPC LENGTH = 40 NAME = WP_IACTION TYPE = TYPINT1 NAME = WP_ACTION TYPE = TYPC LENGTH = 25 NAME = WP_TABLE TYPE = TYPC LENGTH = 30 NAME = WP_SERVER TYPE = TYPC LENGTH = 20 NAME = WP_WAITINF TYPE = TYPC LENGTH = 40 NAME = WP_WAITTIM TYPE = TYPC LENGTH = 8 Tivoli Manager for R/3 User s Guide 177 A. Command Line Interface Commands

200 178 User s Guide Version 2.1

201 B Event Classes and Rules Event Classes This appendix contains information about the TEC event classes delivered with Manager for R/3, new slot values for these events, and background information on R/3 alerts. It also contains information about the rules that Manager for R/3 provides. Manager for R/3 provides a set of TEC event classes. These event classes are categorized according to their origin and usage. The event classes that are provided are: R/3 Alert Event Classes These event classes arise from alerts placed by R/3 onto its SysMan interface. Events for these classes are generated by the Alert Event Adapter. R/3 Operational Event Classes These event classes represent all the events that result from R/3 SysMan events after drill-down processing is performed. R/3 Syslog Event Classes These event classes represent events that result from processing the R/3 syslog. R/3 IDOC Event Classes These event classes represent events that result from processing R/3 IDOCs. Distributed Monitoring Event Classes Tivoli Manager for R/3 User s Guide 179 B. Event Classes and Rules

202 These event classes are associated with the Manager for R/3 monitors. Special Event Classes These event classes support internal Manager for R/3 processing. R/3 Alert Event Classes These event classes correspond to alerts placed by R/3 on its SysMan interface. R/3 identifies its alerts by an R/3 alert class. The Alert Event Adapter reads R/3 alerts and converts them to TEC events of the appropriate event classes. Additional information on R/3 alerts is provided in CCMS-Generated Alerts on page 197. The R/3 Alert Event Classes, the R/3 Alert Class, and a description of the R/3 alert are described in the following table: Event Class R/3 Alert Class Description SAP_ALERT_StateChange 1 A change occurred in the operation mode of the 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 been generated. SAP_ALERT_SlogFreq 11 An excessive number of events have been written to the R/3 syslog. SAP_ALERT_Buf 12 An R/3 buffer problem has been detected. SAP_ALERT_Enqueue 13 The enqueue table or its name directory is filling up. SAP_ALERT_Rollpag 14 Either the paging or roll area is overflowing to disk. SAP_ALERT_Trace 15 Either an SQL or ABAP trace has been turned on. SAP_ALERT_DpQueue 16 The length of a dispatch queue has been exceeded. SAP_ALERT_PerfDia 20 A dialog work process has experienced excessive response time or excessive wait time. 180 User s Guide Version 2.1

203 Event Class R/3 Alert Class Description SAP_ALERT_PerfUpd 21 An update work process has experienced excessive response time or excessive wait time. SAP_ALERT_PerfBtc 22 A batch work process has experienced excessive response time or excessive wait time. SAP_ALERT_PerfSpo 23 A spool work process has experienced excessive response time or excessive wait time. SAP_ALERT_AbapUpd 30 An error has occurred in an ABAP update process. SAP_ALERT_AbapErr 31 An error has occurred in an ABAP dialog or background process. SAP_ALERT_AbapSql 32 An SQL error has occurred in an ABAP program, possibly indicating a database problem. SAP_ALERT_DbIndcs 41 A required index is missing in the database. This is triggered when a discrepancy is detected during periodic comparison of the physical database with the logical model stored in R/3. SAP_ALERT_DbFreSp 42 The database is filling up. This is triggered based on a periodic check and forecast of the growth rate. SAP_ALERT_DbArcSt 43 There is not enough space in the database archive 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 profiles directory does not match the profile in the database. SAP_ALERT_GenP5 55 General alert class. No specific meaning identified. Tivoli Manager for R/3 User s Guide 181 B. Event Classes and Rules

204 Event Class R/3 Alert Class Description SAP_ALERT_GenP6 56 General alert class. No specific meaning identified. SAP_ALERT_GenP7 57 General alert class. No specific meaning identified. SAP_ALERT_GenP8 58 General alert class. No specific meaning identified. SAP_ALERT_GenP9 59 General alert class. No specific meaning identified. SAP_ALERT_GenP10 60 General alert class. No specific meaning identified. SAP_ALERT_GenP11 61 General alert class. No specific meaning identified. SAP_ALERT_GenP12 62 General alert class. No specific meaning identified. SAP_ALERT_GenP13 63 General alert class. No specific meaning identified. SAP_ALERT_GenP14 64 General alert class. No specific meaning identified. SAP_ALERT_GenP15 65 For Oracle databases, optimizing statistics are not being collected. R/3 Operational Event Classes R/3 Operational Event Classes represent the set of events that you might see on the TEC console as a result of the Manager for R/3 processing alerts from the R/3 SysMan interface. These events contain both the events from drill-down processing and the events from R/3 that do not require drill-down processing. The following table describes these event classes (when the event results from drill-down processing, the description refers to the original R/3 event): 182 User s Guide Version 2.1

205 Event Class SAP_ALERT_ABAP_ERR SAP_ALERT_ABAP_SQL SAP_ALERT_ABAP_VB SAP_ALERT_BUFF_CUA SAP_ALERT_BUFF_DBST SAP_ALERT_BUFF_FTAB SAP_ALERT_BUFF_IRBD SAP_ALERT_BUFF_PRES SAP_ALERT_BUFF_PXA SAP_ALERT_BUFF_SNTAB SAP_ALERT_BUFF_TABL SAP_ALERT_BUFF_TABLP SAP_ALERT_BUFF_TTAB SAP_ALERT_DB_ARCSTUCK SAP_ALERT_DB_BACKUP SAP_ALERT_DB_FREESPC SAP_ALERT_DB_INDICES Tivoli Manager for R/3 User s Guide Description This event results from drill-down of SAP_ALERT_AbapErr. This event results from drill-down of SAP_ALERT_AbapSql. This event results from drill-down of SAP_ALERT_AbapUpd. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_Buf. This event results from drill-down of SAP_ALERT_DbArcSt. This event results from drill-down of SAP_ALERT_DbBckup. This event results from drill-down of SAP_ALERT_DbFreSp. This event results from drill-down of SAP_ALERT_DbIndcs. 183 B. Event Classes and Rules

206 Event Class SAP_ALERT_DB_OPTMSTAT SAP_ALERT_DPQU_BTC SAP_ALERT_DPQU_DIA SAP_ALERT_DPQU_ENQ SAP_ALERT_DPQU_SPO SAP_ALERT_DPQU_V2 SAP_ALERT_DPQU_VB SAP_ALERT_ENQU_ENQ SAP_ALERT_GENP_03 SAP_ALERT_GENP_04 SAP_ALERT_GENP_05 SAP_ALERT_GENP_06 SAP_ALERT_GENP_07 SAP_ALERT_GENP_08 SAP_ALERT_GENP_09 SAP_ALERT_GENP_10 Description This event results from drill-down of SAP_ALERT_GenP15. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_DpQueue. This event results from drill-down of SAP_ALERT_Enqueue. This event results from drill-down of SAP_ALERT_GenP3. This event usually indicates that SAPMSSYS_RSALSUP5 was disabled. This event results from drill-down of SAP_ALERT_GenP4. This event usually indicates that a profile was not maintained. This event results from drill-down of SAP_ALERT_GenP5. This event results from drill-down of SAP_ALERT_GenP6. This event results from drill-down of SAP_ALERT_GenP7. This event results from drill-down of SAP_ALERT_GenP8. This event results from drill-down of SAP_ALERT_GenP9. This event results from drill-down of SAP_ALERT_GenP User s Guide Version 2.1

207 Event Class SAP_ALERT_GENP_11 SAP_ALERT_GENP_12 SAP_ALERT_GENP_13 SAP_ALERT_GENP_14 SAP_ALERT_GENP_15 SAP_ALERT_GENP_ARCH SAP_ALERT_GENP_SPO SAP_ALERT_OSCO_FILE SAP_ALERT_OSCO_LOAD SAP_ALERT_OSCO_PAGE SAP_ALERT_OSCO_SWAP SAP_ALERT_PERF_BTC SAP_ALERT_PERF_DIA SAP_ALERT_PERF_ENQ SAP_ALERT_PERF_SPO SAP_ALERT_PERF_V2 SAP_ALERT_PERF_VB SAP_ALERT_RLPG_PAG Tivoli Manager for R/3 User s Guide Description This event results from drill-down of SAP_ALERT_GenP11. This event results from drill-down of SAP_ALERT_GenP12. This event results from drill-down of SAP_ALERT_GenP13. This event results from drill-down of SAP_ALERT_GenP14. This event results from drill-down of SAP_ALERT_GenP15. This event results from drill-down of SAP_ALERT_Arch. This event results from drill-down of SAP_ALERT_Spo. Operating system file space threshold has been exceeded. Operating system load average thresholds have been exceeded. Operating system paging thresholds have been exceeded. Operating system swap thresholds have been exceeded. This event results from drill-down of SAP_ALERT_PerfBtc. This event results from drill-down of SAP_ALERT_PerfDia. Performance thresholds for the enqueue process have been exceeded. This event results from drill-down of SAP_ALERT_PerfSpo. This event results from drill-down of SAP_ALERT_PerfUpd. This event results from drill-down of SAP_ALERT_PerfUpd. This event results from drill-down of SAP_ALERT_Rollpag. 185 B. Event Classes and Rules

208 Event Class SAP_ALERT_RLPG_ROL SAP_ALERT_SAPsysDown SAP_ALERT_SAPsysUp SAP_ALERT_SLOG_FREQ SAP_ALERT_SLOG_ID SAP_ALERT_StateChange SAP_ALERT_TRSW_TRSW Description This event results from drill-down of SAP_ALERT_Rollpag. This event comes directly from the Alert Event Adapter. This event comes directly from the Alert Event Adapter. This event results from drill-down of SAP_ALERT_SlogFreq. This event results from drill-down of SAP_ALERT_SlogId. This event comes directly from Alert Event Adapter. This event results from drill-down of SAP_ALERT_Trace. R/3 Syslog Event Classes R/3 syslog event classes represent events from processing the R/3 syslog. SAP_SYSLOG is a superclass definition for all syslog event classes. Syslog event classes have the following format: SAP_SYSLOG_MsgID, where MsgID is the three-character message ID of the syslog message that generated the event. Syslog event classes are provided for all syslog events provided in the tecad_wr3slog.cl file, whether or not the events are sent to TEC. See Using the Syslog Event Adapter on page 91. The following table describes the syslog event classes: Event Class Syslog Message SAP_SYSLOG_A05 No memory available. SAP_SYSLOG_A07 Timeout. SAP_SYSLOG_A08 Main memory destroyed. SAP_SYSLOG_AB0 Run time error $$$$. SAP_SYSLOG_AB1 Short dump $$$$ generated for error $$$$. SAP_SYSLOG_B15 Memory area too small. 186 User s Guide Version 2.1

209 Event Class SAP_SYSLOG_B24 SAP_SYSLOG_B33 SAP_SYSLOG_BB2 SAP_SYSLOG_BS2 SAP_SYSLOG_BV3 SAP_SYSLOG_BV4 SAP_SYSLOG_BY1 SAP_SYSLOG_BY2 SAP_SYSLOG_BY3 SAP_SYSLOG_BY4 SAP_SYSLOG_BYL SAP_SYSLOG_BYM SAP_SYSLOG_BYO SAP_SYSLOG_BZ7 SAP_SYSLOG_BZ8 SAP_SYSLOG_BZW SAP_SYSLOG_D01 Syslog Message No memory available for table $$$$ in the table buffer. Inconsistency in table $$$$ in DB interface. Inconsistent buffer &5&5. The synchronization module cannot allocate temporary auxiliary memory. SQL error &5 occurred (poss. network pros.?) Work process is stopped. Work process is in reconnect status. DB error &5. Database &6 for &3. DB error &6 accessing table &5&5. DB error &6 at &3 access to table &5&5. Database error &5 requires intervention by the database administrator. SQL error &5 (possibly a network error); WP in reconnect status. Deadlock occurred. Storage request (&5&5 bytes) is too small for the record (&5&5 bytes). Output buffer (&5&5 bytes) is too small for the record (&5&5 bytes). Error &5 during compression/decompression (&5&5). 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 $$$$. Tivoli Manager for R/3 User s Guide 187 B. Event Classes and Rules

210 Event Class Syslog Message 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 (Spool administration). 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&5 reset. 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. 188 User s Guide Version 2.1

211 Event Class Syslog Message 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 range buffer. 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. Tivoli Manager for R/3 User s Guide 189 B. Event Classes and Rules

212 Event Class SAP_SYSLOG_S0B Syslog Message Maximum no. $$$$ of requests per CPI-C connection reached. 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 Classes R/3 IDOC event classes, which are described in the following table, represent events from processing IDOCs. The SAP_IDOC_STATUS event class conveys information about specific IDOCs and IDOC status codes. This event class is designed as a leaf class of the SAP_IDOC event class, which contains all the event slot definitions. If you need to create specific IDOC event classes by status code, you should create event classes of the form SAP_IDOC_xx, where xx is the two-digit status code. These event classes should be leaf classes of the SAP_IDOC event class. Event Class SAP_IDOC_STATISTICS SAP_IDOC_STATUS Description This event is generated when the number of IDOC events to be sent to TEC reaches the 500 limit, when enabled. This event is generated for IDOCs that have changed status since the last polling cycle. 190 User s Guide Version 2.1

213 Event Class SAP_IDOC_XMIT Description This event is generated when IDOC transmission fails due to an ALE/RFC communication problem. Distributed Monitoring Event Classes Each monitoring source contained in the Manager for R/3 monitoring collections has an associated event class. These event classes are used when TEC events are generated automatically from received Distributed Monitoring monitors. These event classes and their associated monitoring sources are listed in the following table: Event Class BATCH_SERVICE_MONITOR DIALOG_SERVICE_MONITOR FIELD_DESC_BUFFER_MONITOR GENERIC_KEY_BUFFER_MONITOR INITIAL_RECORDS_BUFFER_MONITOR LONG_RUNNING_PROCESS_MONITOR MENU_BUFFER_MONITOR OS_COLLECT_APSRVR_MONITOR OS_COLLECT_DBSRVR_MONITOR OS390_COLLECT_MONITOR OS390_DB2_MONITOR PAGE_AREA_MONITOR PROGRAM_BUFFER_MONITOR ROLL_AREA_MONITOR SAP_CANCELLED_JOB_MONITOR SAP_EXTENDED_MEMORY_MONITOR SAP_FILESYSTEM_MONITOR SAP_HEAP_MEMORY_MONITOR SAP_USER_MONITOR Tivoli Manager for R/3 User s Guide Monitoring Source Batch Performance Dialog Performance FTAB Field Catalog Buffer TABL Generic Key Buffer IRBD Initial Records Buffer Long running process CUA Menu and Text Buffer OS Collect - Application Server OS Collect - Database Server OS/390 OS/390 DB2 Page Area PXA Program Buffer Roll Area Cancelled Job Extended Memory R3 UNIX File Systems and R3 Windows NT File Systems monitoring sources Heap Memory User 191 B. Event Classes and Rules

214 Event Class SCREEN_BUFFER_MONITOR SHORT_NTAB_BUFFER_MONITOR SINGLE_RECORD_BUFFER_MONITOR SPOOL_SERVICE_MONITOR TABLE_DEF_BUFFER_MONITOR UPDATE_SERVICE_MONITOR WORK_PROCESS_DISPATCH_QUEUE_MONITOR WORK_PROCESS_MONITOR Monitoring Source PRES Screen and Dynpro Buffer SNTAB Short NameTab Buffer TABLP Single Key Buffer Spool Performance TTAB Table Description Buffer Update Performance Work process dispatch queue Work process Status Event Classes The status event classes are described in the following table: Event Class APSRVR_STATUS_MONITOR SAP_DAEMON_MONITOR SAP_ITS_STATUS_MONITOR Description This event is generated when application server status changes. This event is generated when message server status changes. This event is generated when ITS server status changes. Tivoli GEM Instrumentation Event Classes The Tivoli GEM instrumentation event classes are described in the following table: Event Class SAP_APM_HEARTBEAT SAP_APM_THRESHOLD Description This event is generated when an R/3 object is created. This event is generated when the status of an R/3 database server or R/3 ITS server changes. Tivoli GEM Event Classes The Tivoli GEM event classes are described in the following table: 192 User s Guide Version 2.1

215 Event Class APM_HEARTBEAT APM_THRESHOLD Description This event is generated when an R/3 object is created. This event is generated when a Manager for R/3 monitor exceeds the threshold. Error Event Classes The error event classes support internal Manager for R/3 processing. These event classes and their descriptions are listed in the following table: Event Class AMS_WR3MIB_PROCESS_ALERT R3MGR_RFC_ERROR_IDOC SAP_SYSLOG_RFC_ERROR Description This event is generated whenever the alert control or alert reader routines encounter an error. This event results from a communication error between the IDOC Event Adapter and the R/3 system. This event results from a communication error between the Syslog Event Adapter and the R/3 system. Alert Event Slots The Manager for R/3 event classes listed under R/3 Alert Event Classes, R/3 Operational Event Classes, and the event class AMS_WR3MIB_PROCESS_ALERT contain a set of slots that contain information pertinent to the R/3 server being monitored. These slot values are available for use in TEC rules. The following table describes the event slots: Slot r3alertactionstring Tivoli Manager for R/3 User s Guide Description A text string that contains an R/3 recommended action for the alert. Typically, this slot contains a logon string by which an administrator can launch a SAPGUI session to the affected application server. 193 B. Event Classes and Rules

216 Slot r3alertagenthostname r3alertclass r3alertmsgstring r3alertnumber r3alertsapname r3alertseverity r3alertsystemnumber r3alerttimestamp Description The name of the host on which the alert occurred. Typically, database alerts are generated by R/3 instances that are not necessarily run on the database host. The numeric value used by SAP to identify the alert on the SysMan interface. A text string from R/3 that provides more descriptive information for the alert. The alert number as presented by R/3. The SID of the R/3 system in which the alert was generated. The severity of the alert, as reported by R/3. The application server instance number. The timestamp of the alert, as reported by R/3. The timestamp is in UTC format (number of seconds elapsed since 1970). r3configdbhostname The host name of the database server for this R/3 system. r3configdbname The SID of the R/3 system in which the alert was generated. r3configinstancenamestring The application server profile name; for example, DVEBMGS30. Syslog Event Slots The Manager for R/3 event classes described in R/3 Syslog Event Classes on page 186 contain a set of event slots that provide information about the syslog event. The following table describes these event slots: Event Slot r3syslogmsgnumber r3syslogdate r3syslogtime Description The three-character message ID from the syslog. The date that the message was written in the syslog. The time that the message was written in the syslog. 194 User s Guide Version 2.1

217 Event Slot r3sysloginstancename r3syslogtask r3syslogclient r3sysloguser r3syslogtxcode r3syslogmsgtext Description The hostname_sid_iid of the R/3 application server. The R/3 task running that is associated with the message that was written in the syslog. The three-digit client number associated with the syslog message. The R/3 user ID associated with the syslog message. The R/3 transaction code associated with the syslog message. A text string that provides more descriptive information about the syslog entry. IDOC Event Slots The Manager for R/3 event classes described in R/3 IDOC Event Classes on page 190 contain a set of event slots that provide information about the IDOC event. The following table describes the event slots for the SAP_IDOC event class: msg r3client r3idocmsg r3idocnum r3idocstatus r3idocstacod Event Slot Tivoli Manager for R/3 User s Guide Description The concatenated values of the r3idocstatus, r3messagetype, r3partnernumber, and r3idocmsg event slots. The three-digit R/3 client number. A text string that contains the IDOC message. This slot contains information from the R/3 fields STAPA1 through STAPA4. Note: The combination of the R/3 fields STAPA1 through STAPA4 can generate a maximum string length of 270 characters. Because TEC limits this event slot to a maximum of 255 characters, the R/3 information can be truncated in some circumstances. The 16-digit R/3 IDOC number. The two-digit R/3 IDOC status code. The eight-character R/3 IDOC status code. 195 B. Event Classes and Rules

218 Event Slot r3idocdirection r3partnernumber r3messagetype r3senderidocnum Description A one-character field that indicates whether the IDOC was inbound or outbound in this R/3 system; 1 = outbound, 2 = inbound. The logical system identifier of the R/3 system to which this R/3 system is communicating. The six-character IDOC message type. The 16-digit IDOC number of the sending R/3 system. The following table describes the event slots for the SAP_IDOC_XMIT event class: Event Slot r3logicaldestination r3inttotal r3intfailed r3intfailedratio r324htotal r324hfailed r324hfailedratio Description The logical system identifier of the R/3 system to which this R/3 system is communicating. The total number of IDOCs processed to this destination in the last polling cycle. The number of failed IDOCs processed to this destination in the last polling interval. The two-digit integer representing the percentage of failed IDOC transmissions in the last polling interval. The total number of IDOCs processed to this destination in the last 24-hour period. The total number of failed IDOCs processed to this destination in the last 24-hour period. The two-digit integer representing the percentage of failed IDOC transmissions to this destination in the last 24-hour period. Cancelled Job Event Slots The SAP_CANCELLED_JOB_MONITOR event class contains a set of slots that contain information pertinent to the cancelled R/3 job. The following table describes these event slots: 196 User s Guide Version 2.1

219 Event Slot r3jobname r3jobid r3jobdate Description The name of the cancelled R/3 job. The ID associated with the cancelled R/3 job. The date that the R/3 job was scheduled. CCMS-Generated Alerts The Computing Center Management System (CCMS) monitors the R/3 application, the operating system, and the database. The R/3 alert monitors operate from a set of predefined thresholds, some of which are user-configurable. The thresholds refer to a 15-minute running average of the values. CCMS also generates alerts for abends in ABAP/4 programs and for messages written to the syslog. Additionally, application programs can report an alert in a general-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 configuring alerts for system CPU time greater than 10% to 20% (probable swapping) and idle CPU time at 0% (probable looping program). Load Average (1-, 5- and 15-minute averages): SAP recommends configuring alerts for a load average of more than 3 processes in the run queue (probable CPU bottleneck). v Memory utilization Physical memory free/available: SAP recommends configuring alerts for less than 10 MB of physical memory free. Pages out: SAP recommends configuring alerts for more than zero pages swapped out per second. Tivoli Manager for R/3 User s Guide 197 B. Event Classes and Rules

220 v Swap utilization Available swap space: A critical alert is generated when there is no swap space available. Note: Operating system alerts do not actually cause traps to be generated by the R/3 SysMan interface. However, the Manager for R/3 does forward key operating system events to the TEC event server. Database Alerts v v Missing indices: An alert is generated when a missing index is detected. This is done through a periodic comparison of the physical database schema with the logical data model that is stored in R/3. Database free space: Free space is checked on tablespaces and dbspaces and an alert is generated when these spaces are filling. The R/3 system maintains a growth history and can predict the growth rate based on this history. v Database log directory: An alert is generated when there is insufficient space to archive the database. R/3 Alerts v v Response time: This applies to dialog processes and refers to the time between when a dialog step is received by R/3 and when a response is returned. Because dialog processes use an asynchronous update model, the response time should be fairly consistent across a broad mix of transaction types. Wait time: This refers to the time that a request waits in the dispatcher queue for an available work process to service it. On average, wait time should be less than 1% of response time for a transaction. A high wait time indicates that not enough work processes are available or that the system is overloaded. Response- and wait-time thresholds can be separately configured for each instance of an application server. 198 User s Guide Version 2.1

221 v v v v v Enqueue management table: The enqueue table (used for managing locks) is kept in memory. If the enqueue table fills up, the system can no longer set any locks and a critical alert is generated. System log messages: Messages that are written to syslog by R/3 can generate alerts. It is possible to specify filters that indicate which messages, based on the message ID, should generate alerts and which messages should not generate alerts. Buffers: Alerts are generated if the directory of objects stored in the buffer becomes too full, if there is insufficient free space in a buffer, or if the quality of a buffer is too low. Roll/Paging: The roll buffer stores the user runtime environment between processing periods in a work process. If the roll buffer becomes full, an alert is generated and the user runtime environment will have to be rolled to a file. If the paging area becomes full, a file is allocated for paging. These event trigger critical alerts when the roll buffer or page area is 95% full. Trace: If tracing is turned on, it generates an alert to indicate a performance degradation. Rules for Manager for R/3 Events The TEC includes a rules engine that processes events according to a set of rules that are provided by Tivoli products or added by users. Manager for R/3 supplies a default rule base, which is a set of rules that provides correlation of related events and gives automated responses where possible. You can extend these rules by writing rules that are tailored for your installation. Refer to the TME 10 Enterprise Console Rule Builder s Guide. Manager for R/3 rules provide these functions: Duplicate event checking Automatic closing of harmless events Automatic drill-down Tivoli Manager for R/3 User s Guide 199 B. Event Classes and Rules

222 Bidirectional communication Event correlation Multi-region support Integration with Tivoli GEM Integration with Tivoli database manager products Duplicate Event Checking By design, the R/3 SysMan, and therefore the R/3 alert event adapter, generates an event only when one of the alert classes changes from one state to another (for example, from green to yellow or from yellow to red). An event is also generated when an alert class decreases in severity (for example, from yellow to green), either when the administrator resets the alert from the CCMS Alert Monitor or when the condition corrects itself. Manager for R/3 provides a rule that automatically closes duplicate events when a new event is received, which is effective for all of the R/3 alert classes. A duplicate event is defined as an event of the same event class in which designated slot values are identical. Automatic Closing of Harmless Events Typically, TEC users do not want the TEC console populated with harmless events. However, it is valuable to display a harmless event for a period of time when the event is generated as a result of a self-correcting condition. To permit this, a rule is provided that automatically closes harmless R/3 alerts after 60 seconds. Automatic Drill-Down When the TEC event server rule base receives certain R/3 SysMan events, it automatically runs an R/3 function module through the RFC interface. The R/3 function module obtains additional and more specific internal CCMS information about the alert. For example, when the TEC event server receives the R/3 SysMan buffer alert, it automatically runs a special function module supplied with Manager for R/3 to identify the specific buffer that is having a problem. 200 User s Guide Version 2.1

223 Bidirectional Communication By converting R/3 alerts into R/3 internal alerts, the TEC event server rule base can use the RFC interface to control R/3 alerts from the TEC. For example, closing or acknowledging an R/3 internal alert from the TEC automatically causes the R/3 alert to be reset or acknowledged in the appropriate R/3 application server. Event Correlation The TEC event server rule base correlates certain types of events and takes the appropriate action. For example, the TEC event server rule base automatically resets R/3 buffer alerts for 35 minutes after receiving an R/3 state change event. Event correlation relieves the administrator from handling expected buffer quality alerts during the state transition. Another example is the ability to identify when an R/3 server becomes unavailable and to automatically drop events that are no longer relevant. When a monitored server initially fails, many events that are indicative of the server failure can arrive and can cause event flooding at a console. When a server is offline, event correlation can associate subsequent events related to that server and can discard them as not relevant. Event correlation helps to remove these events and alleviate such flooding situations. Multi-Region Support Optionally, you can use the TEC event server rule base to forward events from multiple TMRs. Then, a single administrator can monitor a large number of R/3 systems in different TMRs. Integration with Tivoli GEM Optionally, you can manage R/3 resources from the Tivoli GEM console (see Tivoli GEM Instrumentation on page 147). Manager for R/3 provides rules that forward Manager for R/3 monitor events to the Tivoli GEM server and synchronize the Tivoli GEM console with the Manager for R/3 objects on the desktop. Integration with Tivoli Database Manager Products If you have the Tivoli Manager for DB2 or Tivoli Manager for Oracle installed, you can optionally extend database status reporting Tivoli Manager for R/3 User s Guide 201 B. Event Classes and Rules

224 (see Extending Database Server Status Reporting on page 78). Manager for R/3 provides rules that set the status of the database server from the Tivoli Manager for DB2 or Tivoli Manager for Oracle database status event. TEC Event Server Rules The sap_tecad.rls file contains the following TEC event server rules: Rule Name ack_sap_alert close_sap_alert convert_mib_to_internal_alert drop_new_harmless drop_r3mgr_rfc_error_idoc_event dup_all_sap_idoc_event dup_r3mgr_rfc_error_event dup_sap_event forward_sap_events harmless_set_timer harmless_still_open Description Acknowledges R/3 alerts when the corresponding events are acknowledged. Closes R/3 alerts when the corresponding events are closed. Performs drill-down event processing. When the TEC event server receives certain R/3 SysMan events, the R/3 function module obtains more detailed event information. The original event is closed, and only the drill-down event is displayed. Immediately closes internal harmless events and harmless R/3 application server monitor events. Removes the IDOC RFC error event when an IDOC event is received. Removes duplicate IDOC events. Removes duplicate IDOC RFC error events and keeps the original RFC error event. Removes duplicate events. Forwards events to an alternate TEC event server. Sets a timer on each harmless event. The timer is set to 60 seconds. A timer rule will close the event when the timer expires. Closes harmless events after 60 seconds. reset_certain_events_on_statechange Discards buffer alerts when they occur within 35 minutes of an R/3 operational mode switch. reset_syslog_alert Immediately resets syslog events. sapsysdown_clone_appstatus_event Creates an event of class APSRVR_STATUS_MONITOR when an application server s status is down. 202 User s Guide Version 2.1

225 Rule Name sapsysup_clone_appstatus_event sapsysup_read_all_internal_alerts Description Creates an event of class APSRVR_STATUS_MONITOR when an application server s status is up. Gets all existing R/3 alerts when an application server s status changes from down to up. Distributed Monitoring Rules The sap_monitor.rls file contains the following monitor rules: Rule Name ack_sap_sentry_alert close_sap_sentry_alert drop_sentry_events_on_sentry_sysup dup_its_down dup_its_up dup_sap_cancelled_job_event dup_sap_its_down dup_sap_its_up dup_sap_monitor_event dup_sap_system_down dup_sap_system_up sap_extract_job1 sap_extract_job2 Tivoli Manager for R/3 User s Guide Description Closes duplicate events corresponding to an acknowledged event. Closes duplicate events corresponding to a closed event. Removes events that occur within 35 minutes of an R/3 application server coming up. Closes duplicate ITS server status down events. Closes duplicate ITS server status up events. Removes duplicate cancelled job events. Locates duplicate ITS server status down events, increments the count on the existing event, and removes the received event. Locates duplicate ITS server status up events, increments the count on the existing event, and removes the received event. Removes duplicate events. Removes duplicate R/3 application server status down events. Removes duplicate R/3 application server status up events. Assigns the name of the cancelled job to the R3JobName event slot and the ID of the cancelled job to the R3JobID event slot. Assigns the date that the job was scheduled to the R3JobDate event slot. 203 B. Event Classes and Rules

226 Rule Name sap_system_down sap_system_up Description Closes all outstanding open events for an application server when the R/3 application server status changes from up to down. Closes all outstanding open events for an application server when the application server status changes from down to up. sap_system_down_no_more_sentries Removes events when the corresponding R/3 application server is down. sentry_daemon_or_application_down Closes all outstanding open events when the status of the Distributed Monitoring application changes from up to down. sentry_daemon_or_application_up Closes all outstanding open events when the status of the Distributed Monitoring application changes from down to up. sentry_host_down Closes all outstanding open events when the status of the Distributed Monitoring host machine changes from up to down. sentry_host_up Closes all outstanding open events when the status of the Distributed Monitoring host machine changes from down to up. set_r3sapname_slot Assigns the value of the R/3 system label to the sub_source event slot and assigns the value of the R/3 application server name to the sub_origin event slot. Database Status Integration Rules The sap_mgr_db2.rls file contains the following rule: Rule Name db2_status_event Description Sets the status of the database server from the Manager for DB2 database status event. The sap_mgr_oracle.rls file contains the following rule: 204 User s Guide Version 2.1

227 Rule Name oracle_status_event Description Sets the status of the database server from the Manager for Oracle database status event. Correlation Rule The sap_default.rls file contains the following correlation rule: Rule Name drop_sentry_events_on_statechange Description Removes Distributed Monitoring events when they occur within 35 minutes of the R/3 application server status changing from down to up. Tivoli GEM Instrumentation Distributed Monitoring Rules The sap_gemevents.rls file contains the following rules for processing events that are sent from the Manager for R/3 monitors: Rule Name r3_gemevents_rule1 r3_gemevents_rule2 r3_gemevents_rule3 r3_gemevents_rule4 Description Forwards Manager for R/3 monitor events to the Tivoli GEM server. Forwards R/3 application server status events to the Tivoli GEM server. Changes the SAP_APM_HEARTBEAT event to the APM_HEARTBEAT event and forwards the event to the Tivoli GEM server. Changes the SAP_APM_THRESHOLD event to the APM_THRESHOLD event and forwards the event to the Tivoli GEM server. Tivoli Manager for R/3 User s Guide 205 B. Event Classes and Rules

228 206 User s Guide Version 2.1

229 C Remote and Central Monitoring Sources This appendix describes the monitoring sources and attributes contained in the R3 Server Remote Monitors and the R3 Server Central Monitors collections. The table headings have the following meanings: Attribute Description of the monitor as initially seen when creating a monitor. Keyword Description of the monitor after it has been configured. R/3 Reference A mapping of the monitored value to its R/3 equivalent. The reference 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 it means. Note: The Application Server Status, ITS Server Status, and the Cancelled Job monitoring sources do not have attributes. Tivoli Manager for R/3 User s Guide 207 C. Remote and Central Monitoring Sources

230 OS Collect Source The OS Collect Application Server and OS Collect Database Server sources include the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference CPU Utilization user USER_CPU_UTIL st06 / CPU utilization user % (%) CPU Utilization SYSTEM_CPU_UTIL st06 / CPU utilization system % system (%) CPU Utilization idle IDLE_CPU_UTIL st06 / CPU utilization idle % (%) System Calls per SYSTEM_CALLS_SEC st06 / System calls/sec second 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 (15 min) Context switches per second LOAD15_AVG CONTEXT_SWITCH_SEC st06 / Load average 15 min (rounded) 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 in KB_PAGED_IN_SEC st06 / Kb paged in/sec per second Kilobytes paged out KB_PAGED_OUT_SEC st06 / Kb paged out/sec per second Configured swap CONFIG_SWAP st06 / Configured swap kb space size Free swap space FREE_SWAP st06 / Free in swap-space kb 208 User s Guide Version 2.1

231 Attribute Keyword R/3 Reference Maximum swap space MAX_SWAP st06 / Maximum swap-space kb Actual swap space SIZE_SWAP st06 / Actual swap-space kb size Disk utilization (%) DISK_UTILIZATION st06 / Disk Utilization Disk average wait DISK_WAIT_TIME st06 / Disk Avg wait time ms time Disk kilobytes DISK_DATA_TRANSFER_SEC st06 / Disk Kb transferred/sec transferred per second Disk response time DISK_RESPONSE_TIME st06 / Disk Response time ms Disk average queue DISK_QUEUE_LENGTH st06 / Disk Queue length Disk average service DISK_SERVICE_TIME st06 / Disk Avg service time ms time Disk operations per DISK_OPERATIONS_SEC st06 / Disk Operations/sec second LAN packets in per LAN_PACKETS_IN_SEC LAN Packets in/sec second LAN packets out per LAN_PACKETS_OUT_SEC LAN Packets out/sec second LAN collisions per LAN_COLLISIONS_SEC LAN Collisions second LAN packet in errors per second LAN_PACKET_IN_ERRORS_SEC LAN Errors in/sec LAN packet out errors LAN_PACKET_OUT_ERRORS_SEC LAN Errors out/sec per second Note: Disk values apply to the disk with the highest response time at the last sampling period. Roll Area Source The Roll Area source includes the following attributes and their keyword equivalents: Tivoli Manager for R/3 User s Guide 209 C. Remote and Central Monitoring Sources

232 Attribute Keyword R/3 Reference Roll Area Free Space Roll Area Percent Free ROLL_AREA_FREE ROLL_AREA_PERCENT_FREE Not directly available. ROLL_AREA_SIZE minus ROLL_CURRENTLY_USED Not directly available. ROLL_AREA_FREE divided by ROLL_AREA_SIZE Roll Area Shared ROLL_AREA_SHARED_MEMORY st02 / Roll area / In memory (Kb) Memory Roll Area Size ROLL_AREA_SIZE Not directly available. Total size of roll area Roll Currently Used ROLL_CURRENTLY_USED st02 / Roll area / Current use (Kb) Roll Area Percent Used ROLL_AREA_PERCENT_USED Not directly available. ROLL_AREA_USED divided by ROLL_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 by ROLL_AREA_SIZE Page Area Source The Page Area source includes the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference Page Area Free Space PAGE_AREA_FREE Not directly available. PAGE_AREA_SIZE minus PAGE_CURRENTLY_USED Page Area Percent Free Page Area Shared Memory PAGE_AREA_PERCENT_FREE PAGE_AREA_SHARED_MEMORY Not directly available. PAGE_AREA_FREE divided by PAGE_AREA_SIZE st02 / Paging area / In memory (Kb) 210 User s Guide Version 2.1

233 Attribute Keyword R/3 Reference Page Area Size PAGE_AREA_SIZE Not directly available. Total size of page area. Page Currently Used PAGE_CURRENTLY_USED st02 / Page area / Current use (Kb) Page Area Percent Used PAGE_AREA_PERCENT_USED Not directly available. PAGE_AREA_USED divided by PAGE_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 by PAGE_AREA_SIZE Work Process Source The Work Process source includes the following attributes and their keyword 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 Attribute 2 Keyword R/3 Reference Free Free sm50 / Status Waiting Waiting sm50 / Status Running Running sm50 / Status Stopped Stopped sm50 / Status Completed Completed sm50 / Status Tivoli Manager for R/3 User s Guide 211 C. Remote and Central Monitoring Sources

234 Attribute 2 Keyword R/3 Reference ******* ******* sm50 / Status All All sm50 / Status Work Process Dispatch Queue Source The Work Process Dispatch Queue source includes the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference 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 Source The Long Running Work Process source includes the following attributes and their keyword equivalents: Attribute 1 Keyword R/3 Reference 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 212 User s Guide Version 2.1

235 Attribute 2 Keyword R/3 Reference Threshold in seconds Specified threshold value sm51 / elapsed time Buffer Source Buffer sources include the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference 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 Entries Percent PERCENT_FREE_DIR_ENTRIES Not directly available. FREE_DIR_ENTRIES divided by MAX_DIR_ENTRIES. Free Memory FREE_MEMORY st02 / Free space (Kb) Free Memory Percent PERCENT_FREE_MEMORY Not directly available. FREE_MEMORY divided by AVAILABLE_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 Directory Entries USED_DIR_ENTRIES st02 / Directory entries - Used Tivoli Manager for R/3 User s Guide 213 C. Remote and Central Monitoring Sources

236 Attribute Keyword R/3 Reference Used Directory Entries Percent PERCENT_USED_DIR_ENTRIES Not directly available. USED_DIR_ENTRIES divided by MAX_DIR_ENTRIES Used Memory USED_MEMORY st02 / Size - Used Used Memory Percent PERCENT_USED_MEMORY Not directly available. USED_MEMORY divided by AVAILABLE_MEMORY Performance Source Performance sources include the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference Frequency per minute FREQUENCY al01 / Performance - Count Response Time in RESPONSE al01 / Performance - Avg. Resp. milliseconds Wait Time in milliseconds WAIT al01 / Performance - Avg. Wait Heap Memory Source The Heap Memory source includes the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference Heap Currently Used HEAP_CURRENTLY_USED st02 / Heap Memory / Current use (Kb) Heap Max Used HEAP_MAX_USED st02 / Max use (Kb) Extended Memory Source The Extended Memory source includes the following attributes and their keyword equivalents: 214 User s Guide Version 2.1

237 Attribute Keyword R/3 Reference Extended EXTENDED_CURRENTLY_USED st02 / Current use (Kb) Currently Used Extended Max EXTENDED_MAX_USED st02 / Maximum use (Kb) Used Extended % Used EXTENDED_PERCENT_USED st02 / Extended Memory / Current use (%) Extended Free Space Extended Percent Free Extended Max Percent Used EXTENDED_FREE_SPACE EXTENDED_PERCENT_FREE EXTENDED_MAX_PERCENT_USED Not directly available. Total size of extended memory minus Extended Currently Used. Not directly available. Extended Free Space divided by total size of extended memory. Not directly available. Extended Max Used divided by total size of extended memory. User Source The User source includes the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference All Sessions USER_TERMINAL_SESSIONS sm04 / Total sessions User Terminal Sessions USER_TERMINAL_SESSIONS sm04 / Total non-appc-tm sessions OS/390 DB2 Source OS/390 DB2 source includes the following attributes and their keyword equivalents: Note: The R/3 reference in the following table applies to R/3 releases 3.1x to 4.0. Tivoli Manager for R/3 User s Guide 215 C. Remote and Central Monitoring Sources

238 Attribute Keyword R/3 Reference Active pages of buffer pool with maximum active MAX_ACTIVE_BP_PAGES st04 / Max active pages (%) Hit ratio of buffer pool with minimum hit ratio MIN_BP_HIT_RATIO st04 / Min hit ratio (%) Buffer Pool 0 hit ratio BP0_HIT_RATIO st04 / Buffer Pool Activity / BP0 Hit Ratio (%) Buffer Pool 2 hit ratio BP2_HIT_RATIO st04 / Buffer Pool Activity / BP2 Hit Ratio (%) Buffer Pool 3 hit ratio BP3_HIT_RATIO st04 / Buffer Pool Activity / BP3 Hit Ratio (%) 32K Buffer Pool hit ratio Buffer Pool shortage - any active pool Hiper pool concern - any active pool Buffer Pool 0 maximum active pages Buffer Pool 2 maximum active pages Buffer Pool 3 maximum active pages 32K Buffer Pool maximum active pages BP32K_HIT_RATIO st04 / Buffer Pool Activity / BP32K Hit Ratio (%) BP_SHORTAGE BP_HIPER BP0_MAX_ACTIVE_PAGES BP2_MAX_ACTIVE_PAGES BP3_MAX_ACTIVE_PAGES BP32K_MAX_ACTIVE_PAGES st04 / Buffer pool shortage st04 / Hiper pool concerns Not directly available. Can be seen as Max active pages (%) when this buffer is the one with the highest active pages. Not directly available. Can be seen as Max active pages (%) when this buffer is the one with the highest active pages. Not directly available. Can be seen as Max active pages (%) when this buffer is the one with the highest active pages. Not directly available. Can be seen as Max active pages (%) when this buffer is the one with the highest active pages. Deadlocks DEADLOCKS st04 / Deadlocks Lock Suspensions LOCK_SUSPENSIONS st04 / Suspensions 216 User s Guide Version 2.1

239 Attribute Keyword R/3 Reference Lock Timeouts LOCK_TIMEOUTS st04 / Timeouts Failures due to EDM pool full EDM_POOL_FULL_FAILURES st04 / EDM pool full EDM pool utilization (%) Dynamic cache hit ratio Number of times MAXKEEPD was exceeded Indication of deferred close threshold reached EDM_POOL_IN_USE DYN_CACHE_HIT_RATIO MAXKEEPD_EXCEEDED CLOSE_THRESHOLD_REACHED st04 / EDM pool / Pages in use (%) st04 / Dynamic Statement Cache / Hit ratio (%) st04 / MAXKEEPD exceeded st04 / Deferred close threshold reached Commits COMMITS st04 / Commits Rollbacks ROLLBACKS st04 / Rollbacks Checkpoints CHECKPOINTS st04 / Checkpoints OS/390 Source OS/390 source includes the following attributes and their keyword equivalents: Attribute Keyword R/3 Reference CPU Utilization (%) CPU_UTIL os07 / Avg. Processor Utili. CPU Utilization - SYSTEM_CPU_UTIL os07 / MVS CPU Utilization system (%) 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 per PAGE_INS_PRIVATE_SEC os07 / Priv. pages paged in/s second Pages Out of Private per second PAGE_OUTS_PRIVATE_SEC os07 / Priv. pages paged out/s Tivoli Manager for R/3 User s Guide 217 C. Remote and Central Monitoring Sources

240 Attribute Keyword R/3 Reference Pages to Expanded PAGES_TO_EXPSTOR_SEC os07 / Pages to exp. storage Storage per second Pages from Expanded PAGES_FROM_EXPSTOR_SEC os07 / Pages from exp. storage Storage per second Blocked pages paged BLOCKED_PAGES_PAGED_IN os07 / Blocked pages paged in in Blocks paged in BLOCKS_PAGED_IN os07 / Blocks paged in Unused interval count UNUSED_INTERVAL_COUNT os07 / High UIC count Available frames in EXPSTOR_AVAILABLE_FRAMES os07 / Avail. exp. stor. slots expanded storage Migration age MIGRATION_AGE os07 / Migration age Total available frames TOTAL_AVAILABLE_FRAMES os07 / No. of available frames 218 User s Guide Version 2.1

241 D IDOC Status Codes This appendix describes the IDOC status codes and the corresponding TEC event severities. For more detailed information about IDOC status codes, refer to the appropriate SAP documentation. Note: Harmless events are generated only if the specific IDOC was in an error state in the previous polling cycle. Otherwise, no events are generated. The following table describes outbound IDOC status codes that generate TEC events: Outbound IDOCs Code Error Event Severity SAP Meaning 02 Yes Error Error passing data to port 03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK 04 Yes Error Control information of EDI subsystem 05 Yes Error Translation 06 No Harmless Translation 07 Yes Error Syntax check 08 No Harmless Syntax check Tivoli Manager for R/3 User s Guide 219 D. IDOC Status Codes

242 Outbound IDOCs Code Error Event Severity SAP Meaning 09 Yes Error Interchange handling 10 No Harmless Interchange handling 11 Yes Error Dispatch 12, 13, No Harmless OK Yes Warning Interchange acknowledgement negative 16 No Harmless Functional acknowledgement 17 Yes Warning Functional acknowledgement negative 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 EDI subsystem 25 Yes Warning Processing despite syntax error 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 which was edited 34 Yes Error Error in control record of IDOC 36 Yes Error Timeout error; electronic signature not performed 37 Yes Error IDOC added incorrectly 38 No Harmless IDOC archived 220 User s Guide Version 2.1

243 Outbound IDOCs Code Error Event Severity SAP Meaning 39 No Harmless Receive confirmed 40 Yes Error Application document not created in target system 41 No Harmless Application document created in target document The following table describes the inbound IDOC status codes that generate TEC events: Inbound IDOCs Code Error Event Severity SAP Meaning 51, 52 Yes Error Posting error 53 No Harmless Posting successful 54 Yes Error Error during formal application check 55 No Harmless Formal application check 56 Yes Error IDOC with error added 60 Yes Error Syntax error 61 Yes Warning Processing despite syntax error 62 No Harmless IDOC passed to application 63 Yes Error Error passing IDOC to application 64 No Harmless IDOC ready to be passed to application 65 Yes Error ALE error 68 No Harmless IDOC is marked for deletion 70 No Harmless Original of an IDOC which was edited 73 No Harmless IDOC archived Tivoli Manager for R/3 User s Guide 221 D. IDOC Status Codes

244 222 User s Guide Version 2.1

245 E Function Module Authorization This appendix contains a list of the function modules delivered with Manager for R/3. For each function module, the R/3 authorizations required for that module are given. The authorizations list the authorization object referenced followed by the field values required for the function module. The references to the S_RFC authorization object are only necessary for R/3 Releases 3.1G and later that have the RFC security check enabled. J_8C1_ALERT_CONTROL S_RZL_ADM, ACTVT=03 S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16 J_8C1_ALERT_READER S_RZL_ADM, ACTVT=01 S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16 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 S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16 J_8C1_BUFFER_NAMES S_RZL_ADM, ACTVT=03 Tivoli Manager for R/3 User s Guide 223 E. Function Module Authorization

246 S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16 J_8C1_DISPLAY_BATCH S_BTCH_ADM, BTCADMIN=Y S_RFC, TYPE=FUGR, RFC_NAME=J8C5, ACTVT=16 J_8C1_EMHM_INFO S_RZL_ADM, ACTVT=03 S_RFC, TYPE=FUGR, RFC_NAME=J8C8, ACTVT=16 J_8C1_MODIFY_JOB S_BTCH_ADM, BTCADMIN=Y S_BTCH_JOB, JOBACTION=RELE S_RFC, TYPE=FUGR, RFC_NAME=J8C5, ACTVT=16 J_8C1_MODIFY_PROCESS S_ADMI_FCD, S_ADMI_FCD=PADM S_RFC, TYPE=FUGR, RFC_NAME=J8C5, ACTVT=16 J_8C1_DISPLAY_PROCESS S_RFC, TYPE=FUGR, RFC_NAME=J8C5, ACTVT=16 J_8C1_IDOCS_MONITOR S_RFC, TYPE=FUGR, RFC_NAME=J8C6, ACTVT=16 J_8C1_PROC_MONITORS S_RFC, TYPE=FUGR, RFC_NAME=J8C5, ACTVT=16 J_8C1_SYSLOG_READER S_RFC, TYPE=FUGR, RFC_NAME=J8C4, ACTVT=16 J_8C1_OS_COLLECT S_RFC, TYPE=FUGR, RFC_NAME=J8C2, ACTVT=16 J_8C1_OS390_COLLECT S_RFC, TYPE=FUGR, RFC_NAME=J8C3, ACTVT=16 J_8C1_OS390_DB2 224 User s Guide Version 2.1

247 S_RFC, TYPE=FUGR, RFC_NAME=J8C3, ACTVT=16 J_8C1_ROLL_PAGE_SIZES S_RZL_ADM, ACTVT=03 S_RFC, TYPE=FUGR, RFC_NAME=J8C1, ACTVT=16 J_8C1_SYSLOG_TXTS S_RFC, TYPE=FUGR, RFC_NAME=J8C8, ACTVT=16 J_8C1_USER_INFO S_RZL_ADM, ACTVT=03 S_RFC, TYPE=FUGR, RFC_NAME=J8C8, ACTVT=16 Tivoli Manager for R/3 User s Guide 225 E. Function Module Authorization

248 226 User s Guide Version 2.1

249 F Messages This appendix describes Manager for R/3 messages. ABH0001I &1 The last few lines of the log file &2 are... Explanation: This message precedes the display of a set of lines from the end of the appropriate log. This message is always preceded by a separate error message indicating 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 failing command 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 required parameters. ABH0501E &1 The Distributed Monitoring application must be installed on this TMR server. Explanation: The Configure Event Server task was run on a TMR server that does not have Distributed Monitoring installed. The Configure Event Server task requires Distributed Monitoring. User Response: Install Distributed Monitoring on the TMR server. F. Messages Tivoli Manager for R/3 User s Guide 227

250 ABH0502E &1 Rulebase &2 must already exist. Explanation: The Configure Event Server task attempted to clone the specified rule 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 Universal classes 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. User Response: None. ABH0505W &1 Distributed Monitoring Universal Monitor Collection is not available. Explanation: The Configure Event Server task determined that the Distributed Monitoring Universal monitor collection cannot be accessed. User Response: None. ABH0506E &1 Distributed Monitoring Universal Monitor Collection has not been installed. Explanation: The Configure Event Server task determined that the Distributed Monitoring Universal monitor collection has not been installed. The Configure Event 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 classes have 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. This message is always preceded by ABH0507W. 228 User s Guide Version 2.1

251 User Response: None. ABH0509W &1 Distributed Monitoring classes have not been installed. Explanation: The Configure Event Server task determined that the Distributed Monitoring classes have not been installed. User Response: None. The Distributed Monitoring classes will be automatically installed. ABH0510I &1 Installing Distributed Monitoring classes, &2. Explanation: The Configure Event Server task is installing the Distributed Monitoring classes. This message is always preceded by message ABH0509W. User Response: None. ABH0511E &1 Distributed Monitoring rules have not been installed. Explanation: The Configure Event Server task determined that the Distributed Monitoring rules have not been installed. The Configure Event Server task requires these 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. User Response: Contact Tivoli Customer Support. ABH0513I &1 Rulebase, &2, created successfully. Explanation: The rule base compiler successfully compiled rule base &2. User Response: None. ABH0514E ABH0515E &1 Rulebase, &2, creation failed. Explanation: The Configure Event Server task could not create rule base &2. User Response: Contact Tivoli Customer Support. &1 Failed to copy rulebase &2 to rulebase &3. Explanation: The Configure Event Server task could not copy rule base &2 to rule base &3. F. Messages Tivoli Manager for R/3 User s Guide 229

252 User Response: Contact Tivoli Customer Support. ABH0516E &1 Failed to import &2 to rulebase &3. Explanation: The Configure Event Server task could not import rule base &2 to rule base &3. User Response: Contact Tivoli Customer Support. ABH0517E &1 Failed to create event source &2. Explanation: The Configure Event Server task could not create new event source &2. User Response: Contact Tivoli Customer Support. ABH0518E &1 Failed to delete event source &2. Explanation: The Configure Event Server task could not delete the old event source &2. User Response: Contact Tivoli Customer Support. ABH0519E &1 Failed to load rulebase &2. Explanation: The Configure Event Server task could not load rule base &2. User Response: Contact Tivoli Customer Support. ABH0520E &1 Failed to start event server. Explanation: The Configure Event Server task could not restart the event server. User Response: Contact Tivoli Customer Support. ABH0521E &1 Failed to stop event server. Event server must be restarted. Explanation: The Configure Event Server task could not stop the event server. User Response: Contact Tivoli Customer Support. ABH0522E &1 This host is not the TEC Event Server. Explanation: The Configure Event Server task was distributed to a host that is not the TEC event server. User Response: Distribute the task to the TEC event server. 230 User s Guide Version 2.1

253 ABH0523E &1 Can not find directory for rulebase &2. Explanation: The Configure Event Server task was not able to find the directory for rule base &2. User Response: Contact Tivoli Customer Support. ABH0524I &1 Removed old event group &2. Explanation: The Configure Event Console task successfully removed old event group &2. User Response: None. ABH0525E &1 Failed to remove old event group &2. Explanation: The Configure Event Console task could not remove the old event group &2. User Response: Contact Tivoli Customer Support. ABH0526I &1 Created new event group &2. Explanation: The Configure Event Console task successfully created new event group &2. User Response: None. ABH0527E &1 Failed to create new event group &2. Explanation: The Configure Event Console task could not create the new event group &2. User Response: Contact Tivoli Customer Support. 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. User Response: None. ABH0529E &1 Failed to assign event group &2 to event console &3. Explanation: The Configure Event Console task could not assign event group &2 to event console &3. User Response: Contact Tivoli Customer Support. F. Messages Tivoli Manager for R/3 User s Guide 231

254 ABH0530E &1 Event console &2 does not exist. Explanation: The event console named &2 that was supplied to the Configure Event 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. User Response: Contact Tivoli Customer Support. ABH0532E &1 Subscriber list &2 already exists. Explanation: The subscriber list name supplied to the Create Subscriber List task already 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 to communicate with R/3 using the remote function call. The wr3rfc program failed with 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 this application server. ABH0534I &1 Current &2 event adapter configuration for application server &3. Explanation: This message displays the event adapter configuration parameters as a result of running the Display Event Adapter Configuration task. User Response: None. ABH0535I &1 Polling Delay = &2. Explanation: This message displays the value for the polling delay parameter as a result of running the Display Event Adapter Configuration task. User Response: None. 232 User s Guide Version 2.1

255 ABH0536I &1 Event Server Port Number = &2. Explanation: This message displays the value for the event server port number parameter as a result of running the Display Event Adapter Configuration. User Response: None. ABH0537I &1 Hostname of the Event Server = &2. Explanation: This message displays the value for the event server hostname parameter as a result of running the Display Event Adapter Configuration task. User Response: None. 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 event adapter that has not been configured. User Response: Run the Configure Event Adapter task to configure the event adapter 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 the ID 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 the home directory for the ID was not found. User Response: Ensure the sidadm user ID exists and that its home directory is available on the machine on which you want to run the task. ABH0542E ABH0543E &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, but the profile was not found in the home directory for the administrator. User Response: Ensure the sidadm user profile is in the user home directory. &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. Messages Tivoli Manager for R/3 User s Guide 233

256 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 Windows NT machine. However, the required start exit routine, sap_start_db_exit.sh, was not found. User Response: Ensure the start exit routine exists and is in the correct directory. For more information, see Creating Exit Routines for Windows NT on page 72. ABH0546E &1 Program dbaccess failed with return code &2. Explanation: The start dbaccess task could not complete properly. The return code is &2. If another error message precedes this message, the return code might have been generated by that error. If no other error message precedes this message, the return 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 and functioning correctly. ABH0547E &1 Program wruntask failed with return code &2 while trying to execute &3 task. Explanation: The Tivoli wruntask command was attempted but failed. The task it was trying to run was &3. The return code from the wruntask command was &2. User Response: Contact Tivoli Customer Support. ABH0548I &1 Task &2 has finished with the following output: &3. Explanation: A task has completed successfully. The task name is &2. The standard output is &3. User Response: None. ABH0550E &1 The database stop command &2 was not found. Explanation: The Stop Database task on Windows NT requires a user-supplied stop exit routine, sap_stop_db_exit.sh. User Response: Create the sap_stop_db_exit.sh stop exit routine as described in Creating Exit Routines for Windows NT on page User s Guide Version 2.1

257 ABH0551E &1 The file sap_stop_db_exit.sh was not found. Explanation: The stop database task was run for a database on a Windows NT machine. However, the required stop exit routine, sap_stop_db_exit.sh, was not found. User Response: Ensure the stop exit routine exists and is in the correct directory. For more information, see Creating Exit Routines for Windows NT on page 72. ABH0553I &1 Processing completed without error. Explanation: The cancel action completed without any errors being reported. User Response: None. ABH0554E &1 Processing completed with an error, return code = &2. Explanation: task failed. The Cancel Batch Job, Release Batch Job, or Cancel Work Process Possible return codes and their meanings for the Cancel Batch Job task are as follows: 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 RFC interface access has the proper authorization. The required authorization is for object S_BTCH_ADM with BTCADMIN=Y. Possible return codes and their meanings for the Release Batch Job task are as follows: 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 being released. 21 Insufficient authorization. Ensure that the R/3 user ID configured for RFC access has the proper authorization. The required authorization is for the object S_BTCH_ADM and the Batch Administrator ID field needs to be set 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. Messages Tivoli Manager for R/3 User s Guide 235

258 access has the proper authorization. The required authorization is for the object S_ADMI_FCD and the System Administration Function field contains 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 SAPGUI executable was not found on the machine on which the task was run. User Response: Ensure that the SAPGUI executable is available on the target machine, and set up the environment so that the executable can be found. ABH0559E The Configure Remote Function Call task has not been run for this R/3 system. Explanation: To configure the Syslog Event Adapter or the IDOC Event Adapter, you must first configure the remote function call (RFC) for the corresponding R/3 system. User Response: Run the Configure Remote Function Call task in the R3 Configuration Tasks library against the appropriate R/3 system object. For more information, 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. User Response: Contact Tivoli Customer Support. ABH0561E Alert Control script failed with al_typ or al_styp not set. The R/3 alert class is &1. Explanation: User Response: An environmenet variable was not set. Contact Tivoli Customer Support. ABH0562E &1 Unexpected object class name. Explanation: The Send GEM Heartbeat task was not run against a valid object. This task should be run against R3AppServer, R3DBServer, R3ITSServer, and R3System objects only. User Response: Run the task against a valid object. 236 User s Guide Version 2.1

259 ABH0563E &1 Could not start the schedule service. Explanation: The Windows NT schedule service was not running. The Configure Autodiscovery for NT task tried to start the schedule service but failed. User Response: Do one of the following: Ensure that the user ID that the Configure Autodiscovery for NT task uses has the authority to start the schedule service. Configure the Windows NT service so that the schedule service is running. ABH0564E &1 Error in time value. Explanation: The value entered in the minute or hour field is not valid. Valid values for the minute field are 0 through 59. Valid values for the hour field are 0 through 23. User Response: fields. Run the task again and enter a valid value in the minute and hour 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 the date field are 1 through 31. User Response: Run the task again and enter a valid value in the date field. ABH0566E &1 Please enter the TMR region name. Explanation: The TMR name was not provided. User Response: Start the program again specifying the TMR name. ABH0567E &1 Error setting the at command. Explanation: The Configure Autodiscovery task for NT failed because it could not schedule 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 the proper authority. User Response: Ensure that the sidadm has the authority to stop the database. F. Messages Tivoli Manager for R/3 User s Guide 237

260 ABH0569E &1 Management object for database server, &2, does not exist. Request can not be completed. Explanation: server object. The start or stop database task cannot find the specified database User Response: Ensure that the R3DBServer object has been created. If you are starting or stopping a UNIX database server, the database server must reside on the same machine as an R/3 application server. If you are using an OS/390 database server, you can ignore this message. Manager for R/3 does not start or stop an OS/390 database server. ABH0569I &1 Management object for database server, &2, does not exist. Database server may still be running. Explanation: stopped. The database server object does not exist and, therefore, cannot be User Response: Either create the R3DBServer object, or stop the database server manually 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 /tmp directory on the TEC event server, a rules trace of the current rule set, if available, and contact Tivoli Customer Support. ABH0571I &1 Event adapter action complete. Explanation: The start or stop event adapter task has completed. User Response: None. ABH0572E &1 Event adapter action error. Return code = &2. Explanation: This message produces return codes related to the Alert Event Adapter, Syslog Event Adapter, or IDOC Event Adapter. Possible return codes and their meanings are: 27 No unique name. The Alert Event Adapter, Syslog Event Adapter, or IDOC Event Adapter is not named r3mibiid, r3slogiid, or r3idociid, respectively. If you are using Manager for R/3 event adapter tasks, contact Tivoli Customer Support. 30 Windows NT only. The Alert Event Adapter, the Syslog Event Adapter, or the IDOC Event Adapter has been invoked with a value other than 238 User s Guide Version 2.1

261 install, start, stop, or remove. If you are using Manager for R/3 event adapter tasks, contact Tivoli Customer Support. 31 Windows NT only. The Alert Event Adapter, the Syslog Event Adapter, or the IDOC Event Adapter has been invoked without a value. The event adapter should be invoked with one of the following values: install, start, stop, or remove. If you are using Manager for R/3 event adapter tasks, contact Tivoli Customer Support. 41 Unable to open the event adapter log file. On UNIX, check the /tmp directory for space. On Windows NT, check the %SYSTEMROOT%\temp directory for space. If the temp directory does not exist, check the directory where the event adapter executable resides: Managed node: $BINDIR/TME/SAP/2.2C TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C 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 any application servers in the R/3 shared memory. User Response: Ensure that the application servers are running. If you are running the Configure Autodiscovery Task for NT, make sure that the user ID that ran the task has the authority to read the R/3 shared memory. Also, make sure that the R/3 application server profiles are properly configured. See Configuring R/3 Application Server Profiles on page 50. ABH0574E &1 Clone AppServer Status Monitor failed because the input event is incorrect. Explanation: The data in the event is corrupted, and the shell script specified by &1 cannot determine the event type. User Response: Obtain the log file for the &1 shell script, which is located on the machine that is running the TEC, and call Tivoli Customer Support. ABH0575E ABH0576E &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 you want to distribute. &1 File &2 does not exist. Explanation: A required file was not found on the SAPGUI installation server. F. Messages Tivoli Manager for R/3 User s Guide 239

262 User Response: Verify that the SAPGUI installation server is properly installed. If the problem persists, contact Tivoli Customer Support. ABH0577E &1 File package &2 does not exist. Enter package name exactly as shown in the 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 from the List Available SAPGUI File Packages task. Run the task again and enter the exact SAPGUI file package name in the dialog. ABH0578E &1 The command failed. Explanation: An error occurred while running the Configure SAPGUI Package task. 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 the problem 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 Install Package dialog. User Response: Run the task again and enter the exact SAPGUI file package name. Use the List Available SAPGUI File Packages task to determine the names of the 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 not entered in the dialog. User Response: Run the task again and enter the machine name of the R/3 SAPGUI installation server. ABH0581E &1 You must provide the shared directory name of where NetSetup.exe is located. Explanation: The shared path name where the NetSetup.exe executable is located on the SAPGUI installation server was not entered in the dialog. User Response: Run the task again and enter the shared path name where the NetSetup.exe executable is located. 240 User s Guide Version 2.1

263 ABH0582I &1 The file packages available for installation are: Explanation: This message is produced by the List Available SAPGUI File Packages task, and it lists the names of the SAPGUI file packages that exist on the R/3 SAPGUI installation server. User Response: None. ABH0583I &1 The file package was created successfully. Explanation: This message indicates that the SAPGUI file package was created successfully. User Response: None. ABH0584E &1 Software Distribution must be installed on the SAPGUI installation server. Explanation: To create a SAPGUI software package for distribution, Software Distribution must be installed on the R/3 SAPGUI installation server. User Response: Install Software Distribution on the R/3 SAPGUI installation server and run the task again. ABH0585I &1 Imported &2 to rulebase &3. Explanation: This message is produced by the Configure Event Server task. This messages lists the rule file &2 that is imported into rule base &3. User Response: None. ABH0586E &1 Profile creation failed: &2. Explanation: Manager for R/3 could not create monitoring profile &2. User Response: Contact Tivoli Customer Support. ABH0587E ABH0588E &1 Adding of monitor to profile failed. Explanation: This message is issued by the Create RDBMS Manager Status Monitor task. Manager for R/3 could not add the database status monitor to the monitoring profile. User Response: Contact Tivoli Customer Support. &1 Setting of remote user and group IDs failed. Explanation: The user ID and group ID could not be set for the monitoring profile that was created. F. Messages Tivoli Manager for R/3 User s Guide 241

264 User Response: Contact Tivoli Customer Support. 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 indicates that the value entered for the month is not valid. User Response: Run the Configure Autodiscovery task again and specify a value from 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 the DB2 instance name. User Response: Contact Tivoli Customer Support. ABH0592E &1 Adapter &2 has not been configured. Explanation: This message is issued when the Start Adapter task has been executed against an R/3 application server that does not have a configured event adapter. User Response: Configure the appropriate event adapter (Alert Event Adapter, Syslog Event Adapter, or IDOC Event Adapter), and run the Start Adapter task again. ABH0593W &1 Management object for database server, &2, does not exist. Database server may not be started. Attempting to start application servers... Explanation: The database server object does not exist and, therefore, cannot be started. Manager for R/3 will attempt to start the application servers. However, if the database server is not running, the attempt to start the application servers will fail. User Response: Either create the R3DBServer object, or start the database server manually before running the start R/3 system task. 242 User s Guide Version 2.1

265 ABH3001E No memory to create tables. Explanation: Insufficient memory is available to put output information into a table. User Response: Contact your system administrator. ABH3002E Open failed for command file &1. Explanation: file). The wr3rfc program could not open the command file (rfc_interface User Response: Create a command file as described in Command Line Interface Commands on page 167. If the file already exists, change permissions so that the file can be read. ABH3003E Exceeded number of export parameters accepted by &1. Explanation: There are too many command line (or configuration file) arguments for this command file. You have entered more export parameters than are specified in the command file. User Response: Delete the extra export parameters, then run the command again. ABH3004E Parameter &1 exceeds defined length. Explanation: The length of the export parameter is greater than the specified length of the parameter. User Response: Change the length parameter so that it is greater than or equal to the 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 are correct. See Command Line Interface Commands on page 167. ABH3006E ItCreate failed for importing table. Explanation: There is not enough memory available to create an internal structure for the size and shape of the table requested. User Response: Perform the remote function call from a system with more available memory. If the problem persists, contact your system administrator. F. Messages Tivoli Manager for R/3 User s Guide 243

266 ABH3007E Itfree failed for importing table. Explanation: An attempt to free up memory by deleting all rows from a table failed. User Response: Perform the remote function call from a system with more available memory. If the problem persists, contact your system administrator. ABH3008E Install Structure error. Explanation: R/3 could not create an internal structure for the specified heterogeneous table. User Response: Contact Tivoli Customer Support. 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. User Response: Contact Tivoli Customer Support. ABH3013E In RfcReceive. Explanation: An internal error in retrieving information from R/3 has occurred. User Response: Contact Tivoli Customer Support. ABH3014E In RfcCall. Explanation: This function calls an ABAP/4 function module via RFC. It can 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. 244 User s Guide Version 2.1

267 ABH3015E Incorrect line: &1. Explanation: The line is not valid for the command file or configuration file. User Response: For valid line formats, see Command Line Interface Commands on page 167. ABH3016E Exceeded maximum number of input parameters. Explanation: Exceeded the limit of 64 input or import parameters. User Response: Specify 64 or fewer input parameters. ABH3017E Exceeded maximum number of output parameters. Explanation: Exceeded the maximum of 64 output parameters that are allowed to be specified. User Response: Specify 64 or fewer output parameters. ABH3018E Only one IMPORT TABLE allowed. Explanation: You can import only one table at a time. User Response: Change the command file so that it requests only one table. ABH3019E Malloc failed. Explanation: Memory allocation failed for the remote function call on the user s system. User Response: Contact your system administrator. ABH3020E Incorrect mode: &1. Explanation: The mode indicated in the command line or the configuration file is not correct. Valid values for mode are 2 and 3, which correspond to RFC_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 configuration file is not correct. Valid values for trace are: YES and NO. User Response: Specify a valid trace value. F. Messages Tivoli Manager for R/3 User s Guide 245

268 ABH3022E Incorrect type: &1. Explanation: The value of the TYPE field in the command file is not correct. Valid values are: TYPC, TYPNUM, TYPX, TYPP, TYPINT, TYPINT1, TYPINT2, TYPFLOAT, TYPDATE, TYPTIME. User Response: Specify a valid value in the TYPE field in the command file. ABH3023E Incorrect format: &1. Explanation: The value of the FORMAT field in the command file is not correct. Valid entries for FORMAT are RESULT and VERBOSE. User Response: Specify a valid value in the FORMAT field in the command file. ABH3024E Export parameter &1 must have a length specified. Explanation: The fields, TYPC, TYPNUM, TYPX, and TYPP, within the EXPORT PARAMETER stanza must have a value specified in the LENGTH field. User Response: Enter a value in the LENGTH field in the command file for the parameter to be exported. ABH3025E Export parameter &1 contains an incorrect type &2. Explanation: The specified export parameter does not have a valid value in the TYPE field. Valid types are: TYPC, TYPNUM, TYPX, TYPP, TYPINT, TYPINT1, TYPINT2, TYPFLOAT, TYPDATE, TYPTIME. User Response: Specify a valid type in the TYPE field in the command file (rfc_interface file). ABH3026E Import parameter &1 must have a length specified. Explanation: The fields, TYPC, TYPNUM, TYPX, and TYPP, within the IMPORT PARAMETER stanza must have a LENGTH field specified. User Response: Enter a value in the LENGTH field in the command file for the parameter 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. 246 User s Guide Version 2.1

269 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 not correct. 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 RFC API. User Response: Contact Tivoli Customer Support. 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 -s argument. -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. F. Messages Tivoli Manager for R/3 User s Guide 247

270 User Response: For the command line syntax, see Command Line Interface Commands on page 167. ABH3500-ABH3699 Explanation: Messages numbered ABH3500 through ABH3699 are written to a log 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 name in 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 in something 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 in something 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. User Response: Contact Tivoli Customer Support. ABH4506E Create r3appserver: endpoint &1 not found. Explanation: The TMA endpoint name specified in the dialog is not valid. User Response: Specify a valid TMA endpoint name in the dialog. 248 User s Guide Version 2.1

271 ABH4507E Create r3appserver: SAP R/3 hostname not set. Explanation: The R/3 host name was not entered in dialog. User Response: Enter the R/3 host name in the dialog. ABH4508E Create r3appserver: managed node &1 not found. Explanation: The managed node name specified in the dialog is not valid. User Response: Specify a valid managed node name in the dialog. ABH4509E Create r3appserver: must specify managed node or endpoint. Explanation: A managed node or endpoint name was not specified in the dialog. User Response: Specify either a managed node name or a TMA endpoint name in the dialog. ABH4514E Create r3appserver: tmr_trans_begin failed. Explanation: The transaction to create the R3AppServer object failed to begin. User Response: Contact Tivoli Customer Support. ABH4515E Create r3appserver: tmf_trans_end failed. Explanation: The transaction to create the R3AppServer object failed to end. User Response: Contact Tivoli Customer Support. ABH4516E Create r3dbserver: R3 database server hostname not set. Explanation: The R/3 database server host name was not set. User Response: Contact Tivoli Customer Support. ABH4517E ABH4518E Create r3dbserver: r3system OID is nil. Explanation: An attempt was made to create an R3DBServer object in something other than an R/3 system policy region. User Response: Create the R3DBServer object in an R/3 system policy region. Create r3dbserver: r3system &1 not found. Explanation: An attempt was made to create the R3DBServer object in something other than an R/3 system policy region. F. Messages Tivoli Manager for R/3 User s Guide 249

272 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. User Response: Contact Tivoli Customer Support. ABH4520E Create r3dbserver: endpoint &1 not found. Explanation: The TMA endpoint name specified in dialog is not valid. User Response: Run the task again and specify a valid TMA endpoint name in the dialog. 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 the dialog. ABH4522E Create r3dbserver: must specify managed node or endpoint. Explanation: The managed node name or TMA endpoint name was not specified in the dialog. User Response: Run the task again and specify either the managed node name or the TMA endpoint name in the dialog. ABH4526E Create r3dbserver: tmf_trans_begin failed. Explanation: The transaction to create the R3DBServer object failed to begin. User Response: Contact Tivoli Customer Support. ABH4527E Create r3dbserver: tmf_trans_end failed. Explanation: The transaction to create the R3DBServer object failed to end. User Response: Contact Tivoli Customer Support. 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. 250 User s Guide Version 2.1

273 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. User Response: Contact Tivoli Customer Support. ABH4531E Create r3system: R/3 system ID not set. Explanation: The R/3 system ID was not specified in the dialog. User Response: Specify the R/3 system ID in the dialog. ABH4532E There is already a r3system with the name &1. Explanation: Manager for R/3 is trying to create an R/3 system that already exists. User Response: Contact Tivoli Customer Support. ABH4533E Only one instance of the R/3 system properties dialog is allowed to be active at a time. The dialog is currently being used by &1 on &2. Explanation: User Response: The R/3 system properties dialog is already open. 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. User Response: Contact Tivoli Customer Support. ABH4535E ABH4801E Create r3system: tmf_trans_end failed. Explanation: The transaction to create the R/3 system failed to end. User Response: Contact Tivoli Customer Support. Create R3ITSServer: R3 ITS Server Host Name not set. Explanation: When creating an R/3 ITS server, the host name was not set. User Response: Contact Tivoli Customer Support. F. Messages Tivoli Manager for R/3 User s Guide 251

274 ABH4803E Create R3ITSServer: R3System OID is nil. Explanation: An attempt was made to create the R3ITSServer object in a policy region 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 policy region other than an R/3 system policy region. User Response: Create the R3ITSServer object in an R/3 system policy region. ABH4805E Create R3ITSServer: End Point &1 not found. Explanation: The TMA endpoint name specified in the dialog is not valid. User Response: Run the task again and specify a valid TMA endpoint name. ABH4806E Create R3ITSServer: managed node &1 not found. Explanation: The managed node name specified in the dialog is not valid. User Response: Run the task again and specify a valid managed node name. ABH4807E Create R3ITSServer: Must specify Managed Node or Endpoint. Explanation: A managed node or TMA endpoint name was not specified in the dialog. User Response: Run the task again and specify a managed node name or a TMA endpoint name. ABH4808E Create R3ITSServer: tmf_trans_begin failed. Explanation: The transaction to create the R3ITSServer object failed to begin. User Response: Contact Tivoli Customer Support. ABH4809E Create R3ITSServer: tmf_trans_end failed. Explanation: The transaction to create the R3ITSServer object failed to end. User Response: Contact Tivoli Customer Support. 252 User s Guide Version 2.1

275 ABH4810E Only one instance of the R/3 ITS Server Properties dialog is allowed to be active at a time. The dialog is currently being used by &1 on &2. Explanation: User Response: The R/3 ITS server properties dialog is already open. Close the R/3 ITS server properties dialog. ABH4811E Create R3ITSServer: R3 ITS Server Name not set. Explanation: The R/3 ITS server name was not specified in the dialog. User Response: Run the task again and specify the R/3 ITS server name. ABH6600E R3Mgr_uninstall21.pl [ g] [ yes] Explanation: The syntax used for the R3Mgr_uninstall21.pl command was not valid. Use the g option to uninstall Tivoli GEM instrumentation only. Use the yes option to continue the uninstall process without prompts. User Response: syntax. Run the R3Mgr_uninstall21.pl command again using the correct ABH6602E Cannot open log file &1. Explanation: User Response: The specified log file could not be opened. Do the following: 1. Ensure that there is available space in the /tmp on UNIX or the %TMP% directory on Windows NT. 2. Verify the file permissions. 3. Run the uninstall command again. ABH6603I Continuing to uninstall Tivoli Manager for R/3... Explanation: This message is issued when you confirm that you want to uninstall Tivoli Manager for R/3. User Response: None. ABH6604I Exiting uninstall at user request... Explanation: This message is issued when you cancel uninstalling Tivoli Manager for R/3. User Response: None. F. Messages Tivoli Manager for R/3 User s Guide 253

276 ABH6606I &1 This will uninstall the Tivoli Manager for R/3 Version 2.1. You should back up your Tivoli database before uninstalling Manager for R/3. Do you want to continue? Enter y to continue or n to quit. Explanation: This is a reminder to back up the Tivoli database before running the R3Mgr_uninstall21.pl command. User Response: Do one of the following: 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. 2. Back up the Tivoli database. 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 the R3Mgr_uninstall21.pl command. The uninstall process continues without prompting for a confirmation. User Response: None. ABH6647I Uninstalling GEM Instrumentation only... Explanation: This message is issued when the g parameter is specified with the R3Mgr_uninstall21.pl command. The R3Mgr_uninstall21.pl g command uninstalls Tivoli GEM instrumentation only. User Response: None. 254 User s Guide Version 2.1

277 G Troubleshooting This chapter describes diagnostic information and tools available with Manager for R/3. This chapter includes the following topics: Setting Up the Environment Log Files on page 256 TEC Events on page 268 Configuring Monitor Logging Mode on page 272 SAPGUI File Package Distribution on page 273 Icon State on page 273 File System Layout on page 273 Hints on Using Tivoli GEM on page 274 Setting Up the Environment To use the diagnostic tools (wr3mib and wr3rfc), you should set up the environment to ensure that shared libraries are available. Setting up the environment also makes it easier to locate Manager for R/3 log files. To set up the environment, enter one of the following commands at the command prompt: On a UNIX managed node, enter one of the following commands: v For non-c shells: Tivoli Manager for R/3 User s Guide. /etc/tivoli/setup_env.sh 255 G. Troubleshooting

278 Log Files v For C shell: source /etc/tivoli/setup_env.csh On a UNIX TMA endpoint, enter one of the following commands: v For non-c shells: v. /etc/tivoli/lcf/x/lcf_env.sh For C shell: source /etc/tivoli/lcf/x/lcf_env.csh On a Windows NT managed node, enter: %SYSTEMROOT%\system32\drivers\etc\Tivoli\setup_env.cmd On a Windows NT TMA endpoint, enter: %SYSTEMROOT%\tivoli\lcf\x\lcf_env.cmd Note: For TMA endpoints, replace x with 1 for the first TMA endpoint installed on the machine, replace x with 2 for the second TMA endpoint installed on the machine, and so forth. Knowing where to look for information, such as task output and log files, can be key to solving a problem. This section describes where to find various Manager for R/3 log files. Task Log Files The following table describes the log file that is associated with each Manager for R/3 task. The task log files are located in one of the following directories: UNIX: /tmp Windows NT managed node: %DBDIR%\tmp Windows NT TMA endpoint: %LCF_DATDIR% Task Alert Control (internal task) Log File SID_DBhostname_sap_alert_control_IID.log 256 User s Guide Version 2.1

279 Task Alert Reader (internal task) Cancel Batch Job Cancel Work Process Configure Autodiscovery for NT Configure Autodiscovery for UNIX Log File SID_DBhostname_sap_alert_reader_IID.log SID_DBhostname_sap_cancel_job.sh_IID.log SID_DBhostname_sap_cancel_process.sh_IID.log sap_at.log sap_crontab.log Configure Client Install sap_ci_config.log Configure Event For the Alert Event Adapter: Adapter SID_DBhostname_sap_config_adapter_MIBIID.log For the IDOC Event Adapter: SID_DBhostname_sap_config_adapter_IDOCIID.log For the Syslog Event Adapter: SID_DBhostname_sap_config_adapter_SLOGIID.log Configure Event sap_tec_config.log Console Configure Event Server sap_eventserver_config.log Configure Monitor Logging 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 Remote SID_DBhostname_sap_config_rfc.log Function Call Configure SAPGUI sap_sapgui_inst.log Package Configure UNIX Client sap_unix_ci_config.log Install Configure Windows sap_w95_ci_config.log 95/98 Client Install Tivoli Manager for R/3 User s Guide 257 G. Troubleshooting

280 Task Configure Windows NT Client Install Create New Subscriber List Create RDBMS Manager Status Monitor Display Batch Jobs Display Buffer Information Display Event Adapter Configuration Display OS Collect Information Display OS390 DB2 Information Display OS390 Information Display Roll Page Information Display Work Processes List Available SAPGUI Packages List SAPGUI Package Features Release Batch Job Remove Autodiscovery for NT Log File sap_nt_ci_config.log sap_create_subscriberlist.log sap_create_rdbms_mgr_profile.sh_pid.log, where PID is the process ID. SID_DBhostname_sap_display_batch.sh_IID.log SID_DBhostname_sap_display_buffer_info_IID.log For the Alert Event Adapter: SID_DBhostname_sap_adapter_infoMIB_IID.log For the IDOC Event Adapter: SID_DBhostname_sap_adapter_infoIDOC_IID.log For the Syslog Event Adapter: SID_DBhostname_sap_adapter_infoSLOG_IID.log SID_DBhostname_sap_display_OSCollect_info_IID.log SID_DBhostname_sap_display_OS390_DB2_info_IID.log SID_DBhostname_sap_display_OS390_info_IID.log SID_DBhostname_sap_display_roll_page_info_IID.log SID_DBhostname_sap_display_process.sh_IID.log sap_sapgui_display_packs.log sap_sapgui_pack_features.log SID_DBhostname_sap_release_job.sh_IID.log sap_unat.log 258 User s Guide Version 2.1

281 Task Remove Autodiscovery for UNIX Replace Event Adapter (internal task) Send GEM Heartbeat Set Remote Monitor Debug Mode (internal task) Start Database Start Event Adapter Start ITS Server Start R/3 System Start Server Start dbaccess Stop Database Log File sap_uncrontab.log Tivoli Manager for R/3 User s Guide SID_DBhostname_sap_replace_adapter_IID.log SID_DBhostname_sap_gem_heartbeat.log 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 SID_DBhostname_sap_start_db.log For the Alert Event Adapter: SID_DBhostname_sap_start_r3mib_IID.log For the IDOC Event Adapter: SID_DBhostname_sap_start_r3idoc_IID.log For the Syslog Event Adapter: SID_DBhostname_sap_start_r3slog_IID.log 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 SID_DBhostname_sap_start.log SID_DBhostname_sap_start_server_IID.log SID_DBhostname_sap_start_dbaccess.log SID_DBhostname_sap_stop_db.log 259 G. Troubleshooting

282 Task Stop Event Adapter Stop ITS Server Stop R/3 System Stop Server Log File For the Alert Event Adapter: SID_DBhostname_sap_stop_r3mib_IID.log For the IDOC Event Adapter: SID_DBhostname_sap_stop_r3idoc_IID.log For the Syslog Event Adapter: SID_DBhostname_sap_stop_r3slog_IID.log For a single-host R/3 ITS server: SID_DBhostname_sap_stop_itsVIINSINGLE.log For the AGate component: SID_DBhostname_sap_stop_itsVIINDUALAG.log For the WGate component: SID_DBhostname_sap_stop_itsVIINDUALWG.log SID_DBhostname_sap_stop.log SID_DBhostname_sap_stop_serverIID.log Monitor Log Files The following table describes the log file that is associated with each Manager for R/3 monitor. The monitor log files are located in one of the following directories: UNIX: /tmp Windows NT managed node: %DBDIR%\tmp Windows NT TMA endpoint: %LCF_DATDIR% Monitoring Source Application Server Status Batch Performance Log File SID_DBhostname_IID_app_server_monitor.log SID_DBhostname_IID_batch_monitor.log 260 User s Guide Version 2.1

283 Monitoring Source Log File CUA Menu and Text For the central monitor: Buffer 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 - SID_DBhostname_IID_db2archivedirinode_monitor.log Inode Used % DB2 Archive - SID_DBhostname_IID_db2archivedirfree_monitor.log Space Free DB2 Archive - Used SID_DBhostname_IID_db2archivedirpct_monitor.log % DB2 Log - Inode SID_DBhostname_IID_db2logdirinode_monitor.log Used % DB2 Log - Space SID_DBhostname_IID_db2logdirfree_monitor.log Free DB2 Log - Used % SID_DBhostname_IID_db2logdirpct_monitor.log Dialog Performance SID_DBhostname_IID_dialog_monitor.log Extended Memory For the central monitor: hostname_sid_iid_extended_monitor.log For the remote monitor: SID_DBhostname_IID_extendedmem_monitor.log FTAB Field Catalog For the central monitor: Buffer hostname_sid_iid_fielddesc_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_ftab_monitor.log Tivoli Manager for R/3 User s Guide 261 G. Troubleshooting

284 Monitoring Source Heap Memory IRBD Initial Records Buffer ITS Server Status Long Running Work Process Message Server Status OS Collect - Application Server OS Collect - Database Server OS/390 OS/390 DB2 Oracle - Inode Used % Oracle - Space Free Oracle - Used % Log File For the central monitor: hostname_sid_iid_heap_monitor.log For the remote monitor: SID_DBhostname_IID_heapmem_monitor.log For the central monitor: hostname_sid_iid_initrecs_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_irbd_monitor.log For a single-host R/3 ITS server: SID_DBhostname_VIIN_SINGLE_itsstatus_monitor.log For the AGate component: SID_DBhostname_VIIN_DUALAG_itsstatus_monitor.log For the WGate component: SID_DBhostname_VIIN_DUALWG_itsstatus_monitor.log SID_DBhostname_IID_longrunning_monitor.log SID_DBhostname_IID_messageserver_monitor.log For the central monitor: hostname_sid_iid_oscollectaps_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_oscollectaps.log hostname_sid_iid_oscollectdbs_buffer_monitor.log hostname_sid_iid_oshostcollect_buffer_monitor.log hostname_sid_iid_oshostdb2_buffer_monitor.log SID_DBhostname_IID_oracledirinode_monitor.log SID_DBhostname_IID_oracledirfree_monitor.log SID_DBhostname_IID_oracledirpct_monitor.log 262 User s Guide Version 2.1

285 Monitoring Source Log File Oracle Archive - SID_DBhostname_IID_oraclearchivedirinode_monitor.log Inode Used % Oracle Archive - SID_DBhostname_IID_oraclearchivedirfree_monitor.log Space Free Oracle Archive - SID_DBhostname_IID_oraclearchivedirpct_monitor.log Used % Oracle Backup - SID_DBhostname_IID_oraclebkpdirfree_monitor.log Space Free Oracle Backup - SID_DBhostname_IID_oraclebkpdirpct_monitor.log Used % Oracle Check - SID_DBhostname_IID_oraclechkdirfree_monitor.log Space Free Oracle Check - Used SID_DBhostname_IID_oraclechkdirpct_monitor.log % Oracle Reorg - SID_DBhostname_IID_oraclereorgdirinode_monitor.log Inode Used % Oracle Reorg - SID_DBhostname_IID_oraclereorgdirfree_monitor.log Space Free Oracle Reorg - Used SID_DBhostname_IID_oraclereorgdirpct_monitor.log % Oracle Statistics - SID_DBhostname_IID_oraclestatfree_monitor.log Space Free Oracle Statistics - SID_DBhostname_IID_oraclestatdirpct_monitor.log Used % Oracle Trace - Space SID_DBhostname_IID_oracletrcdirfree_monitor.log Free Oracle Trace - Used SID_DBhostname_IID_oracletrcdirpct_monitor.log % Oracle datan - SID_DBhostname_IID_oraclesubdirinode_monitor.log Inodes Used % Oracle datan - Space SID_DBhostname_IID_oraclesubdirfree_monitor.log Free Oracle datan - Used SID_DBhostname_IID_oraclesubdirpct_monitor.log % Tivoli Manager for R/3 User s Guide 263 G. Troubleshooting

286 Monitoring Source PRES Screen and Dynpro Buffer PXA Program Buffer Page Area Roll Area SAP Executable - Inode Used % SAP Executable - Space Free SAP Executable - Used % SAP Global - Inode Used % SAP Global - Space Free SAP Global - Used % SAP Home - Inode Used % Log File For the central monitor: hostname_sid_iid_screen_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_pres_monitor.log For the central monitor: hostname_sid_iid_program_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_pxa_monitor.log For the central monitor: hostname_sid_iid_page_area_monitor.log For the remote monitor: SID_DBhostname_IID_pagearea_monitor.log For the central monitor: hostname_sid_iid_roll_area_monitor.log For the server monitor: SID_DBhostname_IID_rollarea_monitor.log SID_DBhostname_IID_sapexedirinode_monitor.log SID_DBhostname_IID_sapexedirfree_monitor.log SID_DBhostname_IID_sapexedirpct_monitor.log SID_DBhostname_IID_sapglobaldirinode_monitor.log SID_DBhostname_IID_sapglobaldirpct_monitor.log SID_DBhostname_IID_sapglobaldirpct_monitor.log SID_DBhostname_IID_saphomedirinode_monitor.log 264 User s Guide Version 2.1

287 Monitoring Source SAP Home - Space Free SAP Home - Used % SAP Mount - Inode Used % SAP Mount - Space Free SAP Mount - Used % SAP Profile - Inode Used % SAP Profile - Space Free SAP Profile - Used % SAP Transport - Inode Used % SAP Transport - Space Free SAP Transport - Used % SNTAB Short NameTab Buffer Spool Performance TABL Generic Key Buffer Log File Tivoli Manager for R/3 User s Guide SID_DBhostname_IID_saphomedirfree_monitor.log SID_DBhostname_IID_saphomedirpct_monitor.log SID_DBhostname_IID_sapmountdirinode_monitor.log SID_DBhostname_IID_sapmountdirfree_monitor.log SID_DBhostname_IID_sapmountdirpct_monitor.log SID_DBhostname_IID_sapprofiledirinode_monitor.log SID_DBhostname_IID_sapprofiledirfree_monitor.log SID_DBhostname_IID_sapprofiledirpct_monitor.log SID_DBhostname_IID_saptraninode_monitor.log SID_DBhostname_IID_saptranfree_monitor.log SID_DBhostname_IID_saptranpct_monitor.log For the central monitor: hostname_sid_iid_shortntab_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_sntab_monitor.log SID_DBhostname_IID_spool_monitor.log For the central monitor: hostname_sid_iid_generickey_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_tabl_monitor.log 265 G. Troubleshooting

288 Monitoring Source TABLP Single Key Buffer TTAB Table Description Buffer Update Performance User Work Process Work Process Dispatch Queue Log File For the central monitor: hostname_sid_iid_singlerec_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_tablp_monitor.log For the central monitor: hostname_sid_iid_tabledef_buffer_monitor.log For the remote monitor: SID_DBhostname_IID_ttab_monitor.log SID_DBhostname_IID_update_monitor.log For the central monitor: hostname_sid_iid_user_monitor.log For the remote monitor: SID_DBhostname_IID_user_monitor.log SID_DBhostname_IID_workprocess_monitor.log SID_DBhostname_IID_process_dsp_q_monitor.log Event Adapter Log Files The following table describes the log file that is associated with each Manager for R/3 event adapter. The event adapter log files are located in one of the following directories: UNIX: /tmp Windows NT: %SYSTEMROOT%\temp, where %SYSTEMROOT% is the drive where Windows NT is installed, usually C: If the \temp directory is not found, the event adapter log files are written in one of the following directories: v v Managed node: %BINDIR%\TME\SAP\2.2C TMA endpoint: %LCF_BINDIR%\..\TME\SAP\2.2C 266 User s Guide Version 2.1

289 Event Adapter Alert Event Adapter IDOC Event Adapter Syslog Event Adapter Log File r3mibiid.log r3idociid.log r3slogiid.log Miscellaneous Log Files The following table describes miscellaneous log files, such as the log files associated with uninstalling Manager for R/3 and TEC scripts. Log Type Function Log Name R3Mgr_uninstall21.pl Manager for R/3 R3Mgr_uninstall21.log uninstall sap_alert_control_cb.sh TEC script sap_alert_control_cb.log sap_alert_reader_cb.sh TEC script sap_alert_reader_cb.log sap_gemhbfwd.sh TEC script sap_gemhbfwd.log sap_gemtecfwd.sh TEC script sap_gemtecfwd.log sap_gemthfwd.sh TEC script sap_gemthfwd.log sap_set_r3db_state.sh TEC script sap_set_r3db_state.log sap_sysupdown_clone_event.sh TEC script sap_sysupdown_clone_event.log Notes: 1. The R3Mgr_uninstall21.log is located in one of the following directories: UNIX: /tmp Windows NT managed node: %DBDIR%\tmp Windows NT TMA endpoint: %LCF_DATDIR% 2. Logs related to TEC scripts are located in one of the following directories on the TEC event server: UNIX: /tmp Windows NT managed node: %DBDIR%\tmp Tivoli Manager for R/3 User s Guide 267 G. Troubleshooting

290 TEC Events All Manager for R/3 alert events originate from the alert event adapter. The r3mibiid program reads the R/3 SysMan interface for a managed R/3 application server. R/3 provides information about R/3 alerts through the SysMan interface. The r3mibiid program captures each R/3 alert, converts it to a TEC event, and forwards the event to the TEC event server. TEC event processing is illustrated in the following diagram: The Manager for R/3 provides a set of rules that are run on the TEC event server. These rules will determine if the event is generic or specific. Generic events are high-level indications of a problem. More information about the alert is available inside of the R/3 system. For these events, the Manager for R/3 will perform drill-down processing to gather the more detailed information. In doing this, the original event will be discarded. Specific events contain all information in the event and are forwarded directly to the TEC event consoles. The drill-down process begins with the TEC rules calling the sap_alert_reader_cb.sh script. This script runs on the TEC event server machine. Like tasks, this script automatically generates a log file in the /tmp directory. This log file is called sap_alert_reader_cb.log. The sap_alert_reader_cb.sh script triggers the running of a task on the remote R3AppServer. The remote task is sap_alert_reader.sh. 268 User s Guide Version 2.1

291 This task also automatically creates a log file. This log file is contained in the /tmp directory of the machine on which the R/3 application server resides. This log file is called sap_alert_reader.log. The sap_alert_reader.sh script calls the wr3rfc program to actually connect to the R/3 application server. The wr3rfc program logs on to the R/3 application server and runs a function module J_8C1_ALERT_READER. If the drill-down is successful, a more detailed event is returned to the TEC event server by the sap_alert_reader.sh script. This more detailed TEC event is forwarded to the TEC event consoles. Error Alerts Errors in the sap_alert_reader_cb.sh and the sap_alert_reader.sh scripts will often generate a special error TEC event to the TEC event server. These events are of class AMS_WR3MIB_PROCESS_ALERT. If one of these events occurs, check the sap_alert_reader_cb.log and sap_alert_reader.log files for additional diagnostic information. Event Diagnostic Tools The processing flow for event generation involves many steps. You can debug these steps individually to facilitate problem determination. In particular, you can run the wr3mib and wr3rfc programs from the command line to determine if the wr3mib and wr3rfc programs are working correctly. wr3mib (r3mibiid) Diagnostics The first step in diagnosing event problems is to ensure that programs can communicate with the R/3 application server. To do this, 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 Go to one of the following directories: Managed node: $BINDIR/TME/SAP/2.2C Tivoli Manager for R/3 User s Guide 269 G. Troubleshooting

292 TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C 4. Run the following commands to determine if basic interfacing to the R/3 SysMan is working and getting information back from the 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 the wr3mib_64 command. The wr3mib_64 command uses the same syntax as the wr3mib command. If information is returned for all these commands, the interface is working correctly. If information is not being returned for one or more of these commands, the R/3 application might have had its shared memory segments reassigned. For information about R/3 memory segment assignments, see Configuring R/3 Application Server Profiles on page 50 and Configuring Manager for R/3 for HP-UX 11 on page 75. Then, contact Tivoli customer support. The r3mibiid program can have tracing enabled when running as a TEC event adapter daemon. To turn on this debug 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 on page 256. wr3rfc Diagnostics You can also run the wr3rfc program directly from the command line. Several levels of diagnostics can be performed. The most basic test is to ensure that the wr3rfc program is communicating with the R/3 application server. The following command tests this connection: wr3rfc -u userid -c client -p password -l language -d SID -h ManagedNode -s InstanceNumber J_8C1_BUFFER_NAMES.TXT 270 User s Guide Version 2.1

293 The meanings of each of these parameters is explained in wr3rfc on page 171. You will need to substitute values for the userid, client, password, language, SID, ManagedNode, and InstanceNumber parameters. This command lists the R/3 buffer names. The wr3rfc program and the J_8C1* files that the wr3rfc program references are installed in different directories. To facilitate diagnostic testing, it is recommended to copy these files into a common directory such as /tmp. The wr3rfc program is located in one of the following directories: Managed node: $BINDIR/TME/SAP/2.2C TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C The J_8C1* files are located in one of the following directories: Managed node: $BINDIR/../generic_unix/TME/SAP/2.2C/rfc TMA endpoint: $LCF_BINDIR/../../generic_unix/TME/SAP/2.2C/rfc To see additional detail, use the wr3rfc command with the debug option 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 diagnostic information. Level one (-D 1) prints status information on the R/3 communication steps to standard error output. Level two (-D 2) provides a step-by-step detailed status beginning after the parsing of the RFC file. Level three (-D 3) is a full step-by-step status of program execution including the parsing of the RFC file. The J_8C1_BUFFER_NAMES function module is provided as a basic test of the Manager for R/3 RFC functionality. Tivoli Manager for R/3 User s Guide 271 G. Troubleshooting

294 Configuring Monitor Logging Mode Manager for R/3 provides a method for turning on monitor trace for 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 monitor trace is enabled, each monitor running on the target R3AppServer or R3ITSServer object creates a log file. See Log Files on page 256. The log files are reused for each running of the monitor, so information is overwritten as the monitors are redispatched. To determine the cause of a problem with a monitor, enable monitor trace and examine the appropriate log file. To enable monitor trace, run the Configure Monitor Logging Mode job in the R3 Configuration Tasks library in the R3 Configuration policy subregion. The Configure Monitor Logging Mode dialog is displayed: For information about completing the dialog, refer to the online help. The monitors for buffers, roll area, page area, work process, work process dispatch queues, long running process, cancelled job, user, heap memory, extended memory, OS Collect, OS/390, and OS/390 DB2 rely on the wr3rfc program. If these monitors are failing, refer to diagnostic techniques for wr3rfc as explained in wr3rfc Diagnostics on page User s Guide Version 2.1