Tivoli Manager for Message Queue Server User's Guide (April 1999)

Tivoli Manager for Message Queue Server User’s Guide ii Version 1.0 Tivoli Manager for Message Queue Server User's Guide (April 1999)

Copyright Notice Copyright  1999 by Tivoli Systems, 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, Tivoli Enterprise Console, Tivoli Management Framework, and Tivoli Global Enterprise Manager. Microsoft Windows, Windows NT, and the Microsoft logo are trademarks or registered trademarks of Microsoft Corporation. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. Notice 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 Systems’ 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 Manager for Message Queue Server: User’s Guide iii Tivoli Manager for Message Queue Server User's Guide (April 1999)

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 10504-1785 USA.

iv Version 1.0 Contents Tivoli Manager for Message Queue Server User's Guide (April 1999) Preface Chapter 1. Introducing Manager for Message Queue Server

Operations Management ...... 1-2 Event Management ...... 1-2 Event Filtering ...... 1-2 Task Libraries ...... 1-3 Integration with Tivoli Management Framework ...... 1-3 Administrator Authorization ...... 1-3 Enterprise Consoles ...... 1-4 Tivoli Distributed Monitoring ...... 1-4 Chapter 2. Planning for and Installing Manager for Message Queue Server

Where to Install Manager for MQS ...... 2-3 Pre-Installation Considerations ...... 2-5 NT Event Adapter Requirements ...... 2-5 Configuring Tivoli Management Regions ...... 2-5 Configuring TEC Event Servers ...... 2-6 Application Proxy Availability ...... 2-6 Installation Overview ...... 2-6 Installing the Application Proxy ...... 2-8

Tivoli Manager for Message Queue Server: User’s Guide v Contents

From the Desktop ...... 2-8 Using the winstall Command ...... 2-9 Using the Install Task ...... 2-9 Installing Manager for MQS ...... 2-9 From the Desktop ...... 2-10 Using the winstall Command ...... 2-12 Using the Discover and Install Tasks ...... 2-13 Chapter 3. Getting Started with Manager for Message Queue Server

Configuring Manager for MQS ...... 3-1 Assigning Authorization Roles ...... 3-2 Assigning TMR Roles to a Tivoli Administrator ...... 3-2 Assigning Resource Roles to a Tivoli Administrator ... 3-3 Managing Microsoft Message Queue Servers ...... 3-3 MSMQ Server Instances ...... 3-4 Creating MSMQ Server Instances ...... 3-5 Determining Server Status ...... 3-10 Deleting an MSMQ Server ...... 3-10 MSMQ Server Lists ...... 3-11 Chapter 4. Monitoring Microsoft Message Queue Servers

Listing the Monitors ...... 4-1 Understanding the Monitors ...... 4-5 Performance Monitors ...... 4-5 Predefined Monitors ...... 4-6 Additional MSMQ-specific Monitors ...... 4-7 Default Settings for Monitor Responses ...... 4-9 MSMQ Monitor Tasks ...... 4-9 Purge_Dead_LetterQ ...... 4-10 Restart_Services ...... 4-10 Chapter 5. Tasks to Manage Microsoft Message Queue Resources

Listing Tasks ...... 5-2

vi Version 1.0 Contents

Running Tasks ...... 5-2 MSMQ Server Tasks ...... 5-4 Server Information Tasks ...... 5-5 Server Management Tasks ...... 5-6 MSMQ Utility Tasks ...... 5-7 Configure ...... 5-7 Start_Debugging ...... 5-8 Stop_Debugging ...... 5-8 Start_Monitors ...... 5-9 Stop_Monitors ...... 5-9 Chapter 6. Managing Microsoft Message Queue Events

Configuring the Event Server ...... 6-2 Procedure for Configuring the Event Server ...... 6-3 Configuring an Event Console ...... 6-4 Configuring the NT Event Adapter ...... 6-5 Starting and Stopping the NT Event Adapter ...... 6-6 Monitoring the NT Event Adapter ...... 6-6 Filtering Events ...... 6-7 Chapter 7. Tivoli GEM Instrumentation

Understanding the Tivoli GEM Server ...... 7-2 Understanding the Tivoli GEM Console ...... 7-3 Tivoli GEM Instrumentation Event Handling ...... 7-3 Instrumented Components ...... 7-4 Instrumentation Files, Libraries, and Profiles ...... 7-5 Tasks ...... 7-6 Monitors ...... 7-7 Preparing to Install Tivoli GEM Instrumentation ...... 7-7 Tivoli Management Regions ...... 7-7 Administrators ...... 7-7 Installation Prerequisites ...... 7-8 Installing and Configuring Tivoli GEM Instrumentation Components ...... 7-8 Copying BDF, CDF, and Icon Files ...... 7-9 Installing the Java Development Kit ...... 7-9

Tivoli Manager for Message Queue Server: User’s Guide vii Contents

Creating User Groups and Logon IDs for the Tivoli GEM Console ...... 7-10 Setting Security for the Windows NT Operating System 7-11 Installing Tivoli GEM Instrumentation ...... 7-12 Chapter 8. Initializing Tivoli GEM Instrumentation

Configuring MSMQ Servers ...... 8-2 Subscribing to and Distributing the File Packages ...... 8-2 Subscribing to and Distributing the Heartbeat Monitor ... 8-2 Confirming Resource Discovery ...... 8-5 Chapter 9. Tivoli GEM Instrumentation Tasks and Monitors

Locating and Running Tasks ...... 9-1 Tivoli GEM Instrumentation Tasks ...... 9-1 Understanding MSMQ Server Aggregate Resources .. 9-4 Navigating to MSMQ Server Resources ...... 9-4 Using the Tear-Away Log ...... 9-7 Starting a Sample Task ...... 9-7 Monitors ...... 9-8 MSMQ Server Monitors ...... 9-8 MSSQLServer Monitors ...... 9-10 Monitor Operability ...... 9-10 Viewing Monitor Status ...... 9-11 Appendix A. Command Line Interface Commands Appendix B. Event Classes and Rules

Manager for Message Queue Server Event Classes .... B-1 Distributed Monitoring Events ...... B-1 NT Event Adapter Events ...... B-2 Rules for Manager for Message Queue Server Events ... B-4 NT Event Adapter Rules ...... B-5 Distributed Monitor (Sentry) Rules ...... B-5

viii Version 1.0 Contents

Tivoli GEM Instrumentation Distributed Monitoring (SENTRY) Rules ...... B-6 Appendix C. Business and Component Descriptions

Installing BDF, CDF, and Icon Files ...... C-2 Business and Component Description Files ...... C-2 Icon Files ...... C-3 Appendix D. Tivoli GEM Instrumentation Task Descriptions Appendix E. Instrumenting Connection Support to MSMQ Appendix F. Finding and Correcting Problems

Installation Hints ...... F-1 Hints on Using Tasks and Jobs from the Desktop ...... F-3 Hints on Running Tasks from the Tivoli GEM Console ... F-4 Hints on Using Monitors ...... F-5 Hints on Using the TEC ...... F-8 Hints on Using the Tivoli GEM Console ...... F-10 Icon State ...... F-13 Helpful Debugging Information ...... F-14 Tivoli GEM Server Database Corruption ...... F-15 Scheduling Monitors ...... F-15 Product Notes ...... F-15 Task Notes ...... F-16 Monitor Notes ...... F-16 Tivoli GEM Instrumentation Monitor Notes ...... F-17 Desktop Notes ...... F-17 Tivoli GEM Instrumentation Limitations, and Workarounds F-17 The APM_HEARTBEAT Event Is Not Generated .... F-17 Appendix G. Messages

Tivoli Manager for Message Queue Server: User’s Guide ix Contents

Glossary Index

x Version 1.0 Preface The Tivoli Manager for Message Queue Server User's Guide provides information about planning for, installing, and using the Tivoli Manager for Message Queue Server (Manager for MQS). Manager for MQS enables you to monitor the performance, disk usage, and status of the Microsoft Message Queue (MSMQ) server. In addition, Manager for MQS management tasks enable you to stop and start the MSMQ server, delete messages from dead letter queues, and display information on each endpoint. This guide describes the use of tasks and monitors that are provided with the Manager for MQS product.

Who Should Read This Guide This guide is for system administrators who monitor and manage MSMQ servers. The guide requires knowledge of Tivoli and MSMQ products and, optionally, the Tivoli Global Enterprise Manager (Tivoli GEM) product.

Prerequisite and Related Documents For hardware and software requirements, and other release information, refer to the Tivoli Manager for Message Queue Server Release Notes. Related documents include: ■ TME 10 Distributed Monitoring User's Guide ■ TME 10 Enterprise Console Adapter's Guide

Tivoli Manager for Message Queue Server: User’s Guide xi Preface

■ TME 10 Enterprise Console Rule Builder's Guide ■ TME 10 Enterprise Console User’s Guide ■ TME 10 Framework User's Guide ■ TME 10 Software Distribution User’s Guide Related documents for Tivoli Global Enterprise Manager Version 2 include: ■ Tivoli Global Enterprise Manager Installation and User's Guide ■ Tivoli Global Enterprise Manager Instrumentation Guide Note: Tivoli is in the process of changing product names. Products referred to in this manual may still be available under their old names, for example, TME 10 Enterprise Console instead of Tivoli Enterprise Console.

What This Guide Contains The Tivoli Manager for Message Queue Server User's Guide contains the following sections: ■ Chapter 1, “Introducing Manager for Message Queue Server” on page 1-1 Introduces the features and functions of Manager for MQS. ■ Chapter 2, “Planning for and Installing Manager for Message Queue Server” on page 2-1 Covers the planning for and installing of Manager for MQS. ■ Chapter 3, “Getting Started with Manager for Message Queue Server” on page 3-1 Covers the configuring of Manager for MQS. ■ Chapter 4, “Monitoring Microsoft Message Queue Servers” on page 4-1 Describes how to use the performance monitors that Manager for MQS provides. ■ Chapter 5, “Tasks to Manage Microsoft Message Queue Resources” on page 5-1

xii Version 1.0 Preface

Describes how to locate and use tasks that are provided by Manager for MQS. ■ Chapter 6, “Managing Microsoft Message Queue Events” on page 6-1 Contains information on configuring and using the NT event adapter to forward MSMQ server events to the Tivoli Enterprise Console (TEC) event server. ■ Chapter 7, “Tivoli GEM Instrumentation” on page 7-1 Covers the planning for and installing of Tivoli GEM instrumentation. ■ Chapter 8, “Initializing Tivoli GEM Instrumentation” on page 8-1 Covers the configuring and use of Tivoli GEM instrumentation. ■ Chapter 9, “Tivoli GEM Instrumentation Tasks and Monitors” on page 9-1 Describes Tivoli GEM tasks and monitors that become accessible for operational management of your MSMQ servers after the Tivoli GEM components have been successfully installed. ■ Appendix A, “Command Line Interface Commands” on page A-1 Contains a list of supported command line interface (CLI) commands that you can use to create, to change, and to view the attributes of MSMQ server instances. ■ Appendix B, “Event Classes and Rules” on page B-1 Contains a list of supported event source names and a map of the labels provided by the Windows NT event viewer and the Tivoli event display. ■ Appendix C, “Business and Component Descriptions” on page C-1

Tivoli Manager for Message Queue Server: User’s Guide xiii Preface

Describes the Tivoli GEM business description files and the Tivoli GEM component description files. ■ Appendix D, “Tivoli GEM Instrumentation Task Descriptions” on page D-1 Provides the field entries that are required when you run Tivoli GEM instrumentation tasks. ■ Appendix E, “Instrumenting Connection Support to MSMQ” on page E-1 Provides instructions on how to instrument products that provide connections to MSMQ. ■ Appendix F, “Finding and Correcting Problems” on page F-1 Provides installation tips, help on debugging problems, and typical symptoms and solutions. ■ Appendix G, “Messages” on page G-1 Contains a list of the messages that are generated by Manager for MQS.

Typeface Conventions The guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Commands, keywords, file names, authorization roles, URLs, or other information that you must use literally appear in bold. The names or titles of screen objects also appear in bold. Italics Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics. Bold Italics New terms appear in bold italics when they are defined in the text. Monospace Code examples, output, and system messages appear in a monospace font.

xiv Version 1.0 Preface

Documentation When you install Manager for MQS, files containing browsable and printable versions of the Tivoli Manager for Message Queue Server User's Guide (userguide.pdf and userguide.htm) are automatically placed in the %BINDIR%\..\generic_unix\TME\MSMQ\doc directory. In addition, the files are provided in the \DOC directory on the product's CD-ROM. Use Adobe Acrobat Reader to view or print the \DOC\pdf\userguide.pdf file. Point your browser to \DOC\html\userguide.htm to view the user's guide online.

Contacting Customer Support For support inside the United States for this or any other Tivoli product, contact Tivoli Customer Support in one of the following ways: ■ Send e-mail to [email protected] ■ Call 1-800-TIVOLI8 ■ Navigate our Web site at http://www.support.tivoli.com For support outside the United States, refer to your Customer Support Handbook for phone numbers in your country. The Customer Support Handbook is available online at http://www.support.tivoli.com. When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily.

Tivoli Manager for Message Queue Server: User’s Guide xv Preface

xvi Version 1.0 Introduction 1-1

Tivoli Enterprise Console (TEC): receives, filters, and forwards selected events to an event server for further processing. For more information, see “NT Event Adapter Requirements” on page 2-5. Tivoli Global Enterprise Manager (Tivoli GEM) and Tivoli GEM instrumentation: enables you to obtain a graphical topology display of the MSMQ servers, their statuses, and a list of tasks that can be run against each MSMQ server. For more information, see Chapter 7, “Tivoli GEM Instrumentation” on page 7-1. ■ Tivoli Manager for Message Queue Server (Manager for MQS) provides a centralized system management tool for the Microsoft Message Queue (MSMQ) services on the Tivoli platform. Manager for MQS facilitates the management of MSMQ servers on managed nodes and endpoints available on Tivoli Management Framework Version 3.6. The MSMQ server provides loosely coupled and reliable network communications services that are based on the message queuing model. MSMQ optionally supports transactions through Microsoft Transaction Service (MTS) and Microsoft Distributed Transaction Coordinator (MSDTC). MSMQ also provides connectivity to MQSeries by using Level 8 FalconMQ Bridge. Manager for MQS can be used with the following optional products: ■

Tivoli Manager for Message Queue Server: User’s Guide

for Message Queue Server Chapter 1. Introducing Manager Manager for MQS provides the following features that enable you to perform system management functions for MSMQ: ■ Tasks to control and automate MSMQ administrative activities on managed nodes and endpoints available on Tivoli Management Framework, Version 3.6 ■ A selection of monitors for key performance and availability statistics for MSMQ servers ■ Configuration files for the TEC event adapter for Windows NT (NT event adapter) to receive, filter, and forward selected events to the TEC

Operations Management This feature enables you to perform tasks such as starting and stopping servers, running utilities, and obtaining information about servers.

Event Management This feature enables you to monitor and retrieve MSMQ events from MSMQ servers. These events are converted to TEC event format and forwarded to a centralized event server for display and processing.

Event Filtering Manager for MQS utilizes an NT event adapter that enables you to specify events that you do not want forwarded to the event server. With this feature, you can prevent the TEC from being populated with harmless events, allowing you to focus on events of interest to your administrators.

1-2 Version 1.0 Introduction 1-3 resource Task Libraries . To start tasks, one or msmq_admin and msmq_senior , Authorizations - MSMQ resources are contained in a Tivoli policy region. Manager for MQS creates two new roles both of these roles must be assigned to an administrator. Enterprise consoles - TECs provide consolidated event displays for MSMQ events. TECs are configurable and can be created and configured for a number of MSMQ administrators and servers. Distributed monitoring - You can set up monitors to alert you about events concerning MSMQ resources. Configurable thresholds and responses enable you to actively monitor and automatically create various severity levels for event server events. Manager for MQS enables you to assign varying degrees of authorization to system administrators. For more information, see “Assigning Authorization Roles” on page 3-2. Tivoli Management Framework provides a powerful and flexible framework for developing a comprehensive management system. Manager for MQS integrates your MSMQ servers into this system. Integration with the Tivoli Management Framework provides many benefits, including: ■ Manager for MQS provides a set of tasks for operating and managing managed nodes and endpoints on an MSMQ server. ■ ■ Tivoli Manager for Message Queue Server: User’s Guide Administrator Authorization Framework Integration with Tivoli Management Task Libraries Enterprise Consoles

Enterprise Consoles The TECs provide consolidated event displays for the Message Queue Server events. The TECs are configurable and can be created and configured for any number of Message Queue Server administrators and servers.

Tivoli Distributed Monitoring You can set up monitors to alert you about events concerning Message Queue Server resources. Configurable thresholds and responses enable active monitoring and automatic creation of differing severity levels of TEC event server events.

1-4 Version 1.0 Planning and Installation 2-1

Tivoli Manager for Message Queue Server Release

for information on supported Tivoli software, prerequisite

running on a supported operating system. Refer to the Notes software and operating systems, and disk space requirements. configure the TEC event adapter for Windows NT(NT event adapter) packaged with the TEC. See “NT Event Adapter Requirements” on page 2-5. 2. Install the Application Proxy. 3. If you are using the Tivoli Enterprise Console (TEC), install and Managing Microsoft Message Queue (MSMQ) servers with Tivoli Manager for Message Queue Server (Manager for MQS) requires installation of the Manager for MQS and, optionally, Tivoli Global Enterprise Manager (Tivoli GEM) instrumentation if Tivoli GEM is installed. If Tivoli GEM is installed on your system, then refer to Chapter 7, “Tivoli GEM Instrumentation” on pageinformation regarding Tivoli GEM 7-1 instrumentation. for more Before installing Manager for MQS, you must prepare both your Tivoli and MSMQ server installations. This chapter describes how to install Manager for MQSand the following pre-installation tasks: 1. Ensure that all prerequisite software is installed and you are

Tivoli Manager for Message Queue Server: User’s Guide Queue Server Installing Manager for Message Chapter 2. Planning for and 4. If you manage MSMQ resources with Tivoli GEM, see Chapter 7, “Tivoli GEM Instrumentation” on page 7-1. 5. Configure the Tivoli Management Regions (TMRs) as described on page 2-5. 6. If you are using Tivoli Management Framework Endpoints and Gateways available on Tivoli Management Framework Version 3.6, ensure that they are properly configured and functional. For more information on endpoint gateways or endpoints, see Chapter 8, "TME 10 Endpoints and Gateways" in the TME 10 Framework Planning and Installation Guide, Version 3.6. You can install Manager for MQS on a TMR server and also on a managed node that contains an MSMQ server. This enables Manager for MQS commands and requests for information to be sent from Manager for MQS on the TMR server to the Manager for MQS on a managed node. The following figure shows a typical Manager for MQS environment.

With the additional installation of Tivoli GEM instrumentation, Tivoli GEM-specific tasks as well as MSMQ server tasks can be run from

2-2 Version 1.0 Planning and Installation 2-3 Manager for MQS is always installed on the TMR server. For interconnected TMRs, Manager for MQS must be installed on all the TMRs. Manager for MQS must also be installed on all managed nodes where MSMQ is installed. It must be installed on all gateways that have MSMQ running on Lightweight Client Framework/Tivoli Management Agent (LCF/TMA) endpoints or running on the gateway For more information on which tasks are instrumented by Tivoli GEM, see Chapter 9, “Tivoli GEM Instrumentation Tasks and Monitors” on page 9-1. the Tivoli GEM console. The following figure shows a typical Manager for MQS environment with Tivoli GEM instrumentation. Tivoli Manager for Message Queue Server: User’s Guide Where to Install Manager for MQS Where to Install Manager for MQS

itself. The Discover task can be used to identify endpoints that have MSMQ installed. The following figure shows a network containing gateways and endpoints.

The following scenarios identify where Manager for MQS must be installed: 1. MSMQ is installed on Endpoint 1 and Endpoint 2. ■ Install Manager for MQS on Gateway 1. ■ Install Manager for MQS on Gateway 2 when Gateway 2 is a backup for Gateway 1. 2. MSMQ is installed on Gateway 2 and the managed node. ■ Install Manager for MQS on Gateway 2 and the managed node. 3. MSMQ is installed on Endpoint 1 and Endpoint 3. ■ Install Manager for MQS on Gateway 1 and Gateway 2.

2-4 Version 1.0 Planning and Installation 2-5 NT event Pre-Installation Considerations on interconnected TMRs. must be shared Resources . The NT event adapter reads events that are generated on a NT event adapter requirements Tivoli management region configuration Event server configuration Application Proxy availability Configure the TMRs to include MSMQ servers as managed nodes before installing the Manager for MQS. Note: adapter Windows NT system, formats them, and forwards them to an event server for further processing. The Manager for MQS provides the configuration files and tasks that customize the NT event adapter, event server, and TEC to process MSMQ server events. The NT event adapter is packaged with the TEC product. It should be installed, configured, and operational on each MSMQ server-managed node or endpoint from which you want to receive events. This should be done prior to running the task to configure the NT event adapter on the server. For more information, see Chapter 6, Microsoft “Managing Message Queue Events” on page 6-1. ■ ■ ■ The MSMQ server issues event notifications to the Windows NT event logs to describe events that affect MSMQ server resources. The optional TEC product has an event adapter called the Before installing Manager for MQS, the following topics should be addressed: ■ Configuring Tivoli Management Regions NT Event Adapter Requirements Tivoli Manager for Message Queue Server: User’s Guide Pre-Installation Considerations Pre-Installation Considerations

Configuring TEC Event Servers You can configure an event server to automatically forward MSMQ server events to another event server. Configuring event servers in this manner enables you to manage many MSMQ server management servers from a single console, even if the management servers reside in different TMRs. For more information, see “Configuring the Event Server” on page 6-2 and the TME 10 Enterprise Console User's Guide.

Application Proxy Availability The Application Proxy provides a common set of services that are used by Manager for MQS. If the Application Proxy has not been installed (as part of another module), it must be installed before installing Manager for MQS. See “Installing the Application Proxy” on page 2-8 for installation instructions.

Installation Overview You can install Manager for MQS in three ways: ■ From the Tivoli desktop as described on page 2-10. ■ From the command line by using the winstall command as described on page 2-12. ■ By running the MSMQ Discover and Install tasks. The Discover task is provided to enable you to find which managed nodes or endpoints have MSMQ installed. The Install task can then use the output from the Discover task to install Manager for MQS on only those nodes that have MSMQ installed. To use this method, install Manager for MQS on the TMR server only. See “Using the Discover and Install Tasks” on page 2-13 for more information about this method. The install facility installs Manager for MQS and creates a Manager for MQS icon on the desktop. The following table shows the location of the installed components:

2-6 Version 1.0 Planning and Installation 2-7 √ Endpoint √ √ Gateway Endpoint Installation Overview administrator with at √ √ √ root Node Managed authority to install Manager for . √ √ TEC Event Server √ √ TMR Server install_product least MQS. You must be logged in as a Installed MSMQ server runs. If the MSMQ server is installed on endpoints, install Manager for MQS on the endpoint gateway. endpoint where the MSMQ server runs. GEM, see Chapter 7, “Tivoli GEM Instrumentation” on page 7-1 for installation requirements. saving the backup file with a different name from the previous backup. server in your TMR. Note: Backup the Tivoli database Component Application Proxy Manager for MQS NT event adapter 6. Install the NT event adapter on each managed node and 7. If you optionally manage MSMQ server resources with Tivoli 8. After installing Manager for MQS, backup the Tivoli database, 5. Install Manager for MQS on each managed node where the 4. Install Manager for MQS on the TMR server and on the event To install Manager for MQS: 1. Install all prerequisite Tivoli 2.software. Install the Application Proxy 3. if not already installed. Tivoli Manager for Message Queue Server: User’s Guide Installing the Application Proxy

Installing the Application Proxy If the Application Proxy has not been installed (as part of another module), it must be installed before installing Manager for MQS. The following sections describe the three methods that can be used to install the Application Proxy.

From the Desktop 1. From the menu bar, select Desktop → Install → Install Product to display the Install Product dialog. 2. Click the Select Media button 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 MQS CD-ROM. 4. Click the Set Path button. The File Browser dialog displays the contents of the specified media in the Files scrolling list. 5. Click the Set Media & Close button. The File Browser dialog is closed, and the Install Product dialog is displayed with Application Proxy 1.0 shown in the Select Product to Install scrolling list. 6. Select Application Proxy 1.0. 7. Select a target client on which to install the Application Proxy from the Available Clients scrolling list and then click the left arrow button. The selected client is moved to the Clients to Install On scrolling list. 8. Click the Install & Close button. The Product Install window is displayed, listing the actions that will be taken when you continue the installation process. 9. Click the Continue Install button to begin the Application Proxy installation process OR click the Cancel button to stop the process. When you elect to install, the Product Install window continues to display messages that show the progress of

2-8 Version 1.0 Planning and Installation 2-9 -n

task. Finished window. Install index_file

, from which the -i for more winstall

Product Install tmr_server -s Installing the Application Proxy APPLPRX.IND command. message. \APPLPRXY winstall button to close the specifies the machine name on which the Close specifies the path name of the CD-ROM image. specifies the name of the TMR server. TME 10 Framework Reference Manual specifies the index file, cdrom_path Application Proxy is to be installed. Application Proxy is to be installed. The machine name cannot be a Tivoli Management Framework Version 3.6 endpoint where an MSMQ server is installed; it should be the endpoint gateway name.

the installation. Successful installation is indicated by a product installation machine_name cdrom_path tmr_server index_file -n -i machine_name where: -c -s Refer to the 10. Click the The following sections describe the three methods that can be used to install Manager for MQS. Each method can be used to install Manager for MQS on the TMR server and, optionally, on any managed node. If the MSMQ server is installed on an endpoint, the Manager for MQS should be installed on the endpoint gateway. You can also install the Application Proxy by using the The following is the syntax and parameters for the command: winstall -c information about the See “Install Task” on page 2-14 for instructions. Using the Install Task Using the winstall Command Tivoli Manager for Message Queue Server: User’s Guide Installing Manager for MQS Installing Manager for MQS

5. Click the Set Media & Close button. The File Browser dialog is closed, and the Install Product dialog is displayed. The following products are listed in the Select Product to Install scrolling list:

2-10 Version 1.0 Planning and Installation 2-11 left arrow . Clients to Install Installing Manager for MQS scrolling list and then click the instrumentation. Install Manager for MQS before you install Tivoli GEM Tivoli Manager for Message Queue Server Tivoli Manager for Message Queue Server Tivoli GEM instrumentation for Microsoft MSMQ Version 1.0 Tivoli GEM instrumentation for Microsoft MSSQLServer Version 6.5 scrolling list. Available Clients ■ ■ ■ On button. The selected client is moved to the the Note: 6. Select 7. Select a target client on which to install Manager for MQS from Tivoli Manager for Message Queue Server: User’s Guide Installing Manager for MQS

Note: Install Manager for MQS on the TMR server, each managed node where the MSMQ server is installed, on the event server, and on the endpoint gateway. 8. Click the Install & Close button. The Product Install window is displayed, listing the actions that will be taken when you continue the installation process. 9. Click the Continue Install button to begin the Manager for MQS installation process OR click the Cancel button to stop the process. When you elect to install, 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. 10. Click the Close button to close the Product Install window. 11. Refresh the desktop by selecting View → Refresh from the menu bar. The desktop will display the Manager for MQS icon shown below.

Using the winstall Command The following is the syntax and parameters for the winstall command: winstall -c cdrom_path -s tmr_server -i index_file -n machine_name where: -c cdrom_path specifies the path name of the CD-ROM image. -s tmr_server specifies the name of the TMR server. -i index_file specifies the index file, MSMQ.IND, from which the Manager for MQS is to be installed.

2-12 Version 1.0 Planning and Installation , 2-13 Save and task. (Endpoint) Standard or Discover Discover for more Installing Manager for MQS section. No parameters are (ManagedNode) task, enable only the . command. Discover (Endpoint) winstall Output Format and task, a file with a list of endpoints (managed nodes specifies the machine name on which Manager for task. resource role. task can be run against any managed node or endpoint TME 10 Framework Reference Manual Install MQS is to be installed. The machine name cannot be a Tivoli Management Framework Version 3.6 endpoint where an MSMQ server is installed; it should be the endpoint gateway name. Install option in the option of the output dialog, save the output to a file on the tasks as described below. These tasks require at least the Discover (ManagedNode) by the machine_name 4. The type of endpoint must follow the name. The types are 1. The output will be appended to the file if it 2.already exists. The generated file can be edited by the administrator. 3. Comments (lines with a number sign (#) in column 1) are ignored per line. To create the file with the required. Run the task against all available endpoints. Using the to File TMR server. Notes: To create the file manually, use any text editor to list the endpoints; specifying one endpoint, followed by Output to discover if MSMQ is installed on the node. To run the The You can also install Manager for MQS by using the or endpoints that are currently running the MSMQ server) is required. This file can be created manually or by running the -n Install msmq_admin Refer to the information about the Discover Task Using the Discover and Install Tasks Tivoli Manager for Message Queue Server: User’s Guide Installing Manager for MQS

Install Task Run the Install task on the TMR server by using the following parameters: ■ CDROM Directory: location of the CD-ROM, for example, the location of the MSMQ.IND file ■ Endpoint Input File: use the endpoints list file created by the Discover task. Note: Ensure that the timeout parameter for the Install task is set sufficiently large because the runtime for this task is high. Complete the installation by running the Configure task as described in “Configure” on page 5-7.

2-14 Version 1.0 Getting Started 3-1

event adapter) as described on page 6-5.

or more Tivoli administrators as described on page 3-2. configure event handling before using Manager for MQS: a.b. Configure the event server as described on page 6-2. c. Configure the TEC as described on page 6-4. Configure the TEC event adapter for Windows NT (NT Complete the following steps to configure Manager for MQS: 1. Assign the Manager for MQS-specific authorization roles to one 2. If you are using the Tivoli Enterprise Console (TEC) product, This chapter describes how to configure Tivoli Manager for Message Queue Server (Manager for MQS). The management tasks and procedures used to configure Tivoli for a Microsoft Message Queue (MSMQ) server are also described. 3. Configure Tivoli for an MSMQ server as described on page 3-3.

Tivoli Manager for Message Queue Server: User’s Guide Configuring Manager for MQS Server Manager for Message Queue Chapter 3. Getting Started with Assigning Authorization Roles

Assigning Authorization Roles When you install Manager for MQS, two resource roles, msmq_senior and msmq_admin, are created. All tasks require at least one of these roles to be assigned to the Tivoli administrator that is running the task. In addition, some tasks require Tivoli authority as defined by TMR roles. A Tivoli administrator must have the required authority and must have been assigned one of the Manager for MQS resource roles to successfully run tasks and processes. A Tivoli administrator with a TMR senior role, and preferably a TMR super role, must be given the new msmq_senior resource role. Tivoli administrators who do not require TMR senior and super roles should be assigned the msmq_admin resource role. Tasks that require a TMR senior role and msmq_senior resource role include: ■ Configure_Event_Server ■ Configure_Event_Console ■ Configure_Event_Adapter The tasks that require a Tivoli administrator with at least the msmq_admin resource role include: ■ Tasks in the MSMQ server task library ■ Tasks in the MSMQ utility task library Manager for MQS authorization may be assigned as TMR roles or resource roles depending on local authorization requirements. Exit and restart the desktop for the newly assigned roles to take effect.

Assigning TMR Roles to a Tivoli Administrator To assign the TMR senior and super roles to a Tivoli administrator: 1. From the desktop, double-click on the Administrators icon to display the Administrators window. 2. Right-click on the desired Administrator icon and select Edit TMR Roles from the pop-up menu. The Set TMR Roles dialog is displayed.

3-2 Version 1.0 Getting Started 3-3 Edit icon to roles. msmq_senior scrolling list. or super icon and select or scrolling list by clicking scrolling list by clicking Administrators Resources senior Assigning Authorization Roles msmq_admin button. button. window. Administrator from the scrolling list, scrolling list, Current Roles Current Roles from the pop-up menu. Administrators Change and Close Available Roles Change and Close Available Roles Manager for MQS Select either or both of the Move them to the the left arrow button. Select either or both the roles. Move them to the the left arrow button. ■ ■ MSMQ server. For more information, see “Creating MSMQ Server Instances” on page 3-5. ■ display the ■ Resource Roles 4. Click the The following steps describe the procedures to manage your MSMQ environment with the Manager for MQS: 1. Create an MSMQ server instance on the desktop for each To add resource roles for a specific policy region to a Tivoli administrator: 1. From the desktop, double-click on the 3. From the 2. Right-click on the desired 5. Exit and restart the desktop. 5. Click the 3. Select 4. From the 6. Exit and restart the desktop. Assigning Resource Roles to a Tivoli Administrator Tivoli Manager for Message Queue Server: User’s Guide Managing Microsoft Message Queue Servers Managing Microsoft Message Queue Servers

2. Ensure that the MSMQ server is a subscriber to the desired profile manager lists. For more information, see “MSMQ Server Lists” on page 3-11. 3. Select and change MSMQ monitors and then distribute the monitors to selected endpoints. For more information, see Chapter 4, “Monitoring Microsoft Message Queue Servers” on page 4-1. You can then run any of the management tasks that are described in Chapter 5, “Tasks to Manage Microsoft Message Queue Resources” on page 5-1.

MSMQ Server Instances An MSMQ server instance can be used as a task endpoint and as a subscriber to a profile manager. An MSMQ server instance appears in lists where endpoints are displayed. For example, the new server instance name will appear in the Available to Become Subscribers list when looking at the subscribers for a profile manager. The name of the server instance is the name specified in the Server Alias Name field when the instance was created (see “Creating MSMQ Server Instances” on page 3-5). The name will have the format server AliasName (MSMQ). Tasks and monitors that will run against a MSMQ server instance should specify a target of the MSMQ endpoint instead of the managed node. Example 1: When the managed node is node1 and the server alias name specified is also node1, the following two target endpoints will exist: ■ node1 (ManagedNode) ■ node1 (MSMQ) Tasks and monitors that are run against a server should specify node1 (MSMQ) as the target endpoint. Note that adding both an MSMQ server instance and its managed node to the same list will cause the actions to be run twice. Example 2: When the endpoint is node2 and the server alias name specified is also node2, the following two target endpoints will exist:

3-4 Version 1.0 Getting Started 3-5 to display the icon to display the MSMQ window. → Create dialog. task. This is useful to quickly Manager for MQS Configure Managing Microsoft Message Queue Servers From the desktop. From the command line. This can be useful when you have many servers to create, and you want to specify information that is used to create the instance. See Appendix A, Interface “Command Commands” Line on page A-1 for a description of commands the that you can use to create, to display, and to update MSMQ server instances. By running the populate the policy region with server instances. Default information obtained from the server is used. See “Configure” on page 5-7 for more information. Create an MSMQ Server Policy Region: Manager for MQS node2 (endpoint) node2 (MSMQ) To create an instance from the desktop, follow these steps: 1. Double-click on the ■ ■ ■ Create an instance for each MSMQ server to be managed. An instance is represented as an icon in the Manager for MQS policy region on the desktop. The status of the server is indicated by the icon. The icon also provides a list of tasks that can be performed. You can create a MSMQ server instance in the following ways: ■ ■ 2. From the menu bar, select Creating an Instance from the Desktop Creating MSMQ Server Instances Tivoli Manager for Message Queue Server: User’s Guide Managing Microsoft Message Queue Servers

3. Complete the following text fields: Server Alias Name Name to be used for the server object and the label for the icon. The alias name does not have to match the actual server name. Valid characters for this name include letters, numbers, spaces, and underscores. Note: If the NT monitors package is installed, you may want the alias name to match the actual server name. This may prevent NT monitors from failing. Managed Node Name Name of an existing managed node where the server resides. If you are creating an MSMQ server instance on an endpoint, this can be the name of a managed node where the endpoint gateway resides for the endpoint.

3-6 Version 1.0 Getting Started 3-7

button to add the window. OK

and click the YES

Managing Microsoft Message Queue Servers MSMQ server as a subscriber to the profile manager for the version that is specified. Select Enter the name of an existing endpoint where the server resides. Version of the MSMQ server that this server is running. This value is used when subscribing the server to the profile manager for that version. Policy Region: Manager for MQS Endpoint Name A server object with class MSMQ that you can use as the target when running tasks and monitors against the server. For more information, see “MSMQ Server Instances” on page 3-4. An icon for the MSMQ server, identified by its alias name, in the MSMQ Server version Subscribe to the default profile manager? ■ Creating an MSMQ server instance produces: ■ Results of Creating an MSMQ Server Instance Tivoli Manager for Message Queue Server: User’s Guide Managing Microsoft Message Queue Servers

■ A pop-up menu that enables you to perform common tasks. If you start a task from the menu of an MSMQ server icon, the task runs on that server only. To display the MSMQ server pop-up menu, right-click on the desired MSMQ server icon in the Policy Region: Manager for MQS window. The tasks listed on the menu are described in the following section.

MSMQ Server Icon Tasks The pop-up task menu for an MSMQ server icon contains the following selections: Open Displays the profiles which have been distributed to this server. Properties Displays the managed node name, endpoint name, MSMQ server version, and status of this server instance. When started, if the MSMQ server service is running, then the status will be set to running. If the service is down, then the status will be set to stopped. If unable to verify the state of the service, then the status will be set to unknown. Start Services Runs the Start_Services task which starts the MSMQ service and the Distributed Transaction Coordinator (DTC) and Level 8 FalconMQ Bridge if they are installed. Stop Services Runs the Stop_Services task which stops the MSMQ service and the DTC and Level 8 FalconMQ Bridge if they are installed. Clear Alert Resets the icon state. If running the MSMQ server status monitor, the monitor will turn the icon red when the server is down. Clear Alert can reset the icon to a transparent

3-8 Version 1.0 Getting Started 3-9

Managing Microsoft Message Queue Servers

Stops all the MSMQ monitors on the server. This feature is not supported when the MSMQ server is on a Tivoli Management Framework, Version 3.6, LCF/TMA endpoint. Retrieves selected MSMQ data from the target server. See “MSMQ Server Tasks” on page 5-4 for the types information of displayed. Starts all the MSMQ monitors on the server. This feature is not supported when the MSMQ server is on a Tivoli Management Framework, Version 3.6, Lightweight Client Framework/Tivoli Management Agent (LCF/TMA) endpoint. background, which indicates that the server status is unknown. Returns the status of all the installed MSMQ services on the target server. Also returns the status of the DTC and Level 8 FalconMQ Bridge if they are installed. See “MSMQ Server Tasks” on page 5-4 for the possible values. status Starts the TECNTAdapter event adapter service. Stops the TECNTAdapter event adapter service. Display Server Status Display Server Info → → Start Event Adapter Tasks Stop Monitors Tasks Start Monitors Stop Event Adapter Tivoli Manager for Message Queue Server: User’s Guide Managing Microsoft Message Queue Servers

Determining Server Status The status of the server is reflected by the state of its icon.

Icon State Description Displayed with a green background when the server is active or running.

Displayed with a red background when the server is not running or is stopped.

Displayed with a transparent background when the server status is unknown. The server status is unknown if the state of the services cannot be verified.

Configure and distribute the MSMQ server status monitor for each server and specify that a TEC event is to be generated. This will ensure that your server icons reflect the current status of the servers. The MSMQ server status monitor verifies the state of the MSMQ server service. The server status is also updated when you: ■ Select Start Services or Stop Services from the pop-up menu of the MSMQ server icon. ■ Run the Start_Services or Stop_Services tasks.

Deleting an MSMQ Server Deleting an MSMQ server from a Manager for MQS policy region does not affect the server itself, but does remove the server information that is stored in the Tivoli database. Use the following procedure to delete an MSMQ server from the Manager for MQS policy region: 1. From the Policy Region: Manager for MQS window, select the desired MSMQ server icon.

3-10 Version 1.0 Getting Started 3-11 Available to remove the Delete to subscribe the MSMQ → Edit scrolling list and move them to the list by clicking the left arrow button. Managing Microsoft Message Queue Servers from the pop-up menu. the managed node or endpoint. For more information, not Set Subscriptions & Close see “MSMQ Server Instances” on page 3-4. subscriber, ensure that you specify the MSMQ server instance and When you select the MSMQ servers that are to be added as a to Become Subscribers Current Subscribers servers to the list. Subscribers MSMQ 1.0 servers selected MSMQ server from the policy region. MSMQ monitors 3. Click Follow these steps to subscribe servers to a profile manager: 1. Right-click on one of the profile managers and select 2. Select the desired MSMQ server instances from the ■ Note: 2. From the menu bar, select Manager for MQS automatically creates several profile managers to help you group servers for management. Each profile manager has a list of subscribers that enables you to run tasks and monitors against each server in that list. The following profile managers are initially created: ■ Subscribing Servers to a Profile Manager MSMQ Server Lists Tivoli Manager for Message Queue Server: User’s Guide 3-12 Version 1.0 Monitoring Message Queue Servers 4-1 icon. Profile . window is displayed. Manager for MQS icon. The MSMQ Monitors

window is displayed.

Policy Region: Manager for MQS The Manager Items added in the performance database Overall performance of MSMQ TME 10 Distributed Monitoring User's Guide MSMQ services 2. Double-click on the To list the monitors that are provided by MSMQ: 1. From the desktop, double-click on the ■ ■ Like any Tivoli Distributed Monitoring monitor, a MSMQ-specific monitor can be customized. For example, you may want to add more monitors to the default set. Additionally, you may want to set the severity or threshold of the monitors. For additional information, see the This chapter explains how to customize and use Microsoft Message Queue (MSMQ) monitors. The Tivoli Manager for Message Queue Server (Manager for MQS) provides several monitor collections to enable remote monitoring of: ■

Tivoli Manager for Message Queue Server: User’s Guide Listing the Monitors

Message Queue Servers Chapter 4. Monitoring Microsoft Listing the Monitors

3. From the Profiles group box, double-click on the MSMQ; 1.0 icon. The TME 10 Distributed Monitoring Profile Properties window is displayed.

4. Click the Add Monitor button to display the Add Monitor to TME 10 Distributed Monitoring Profile dialog.

4-2 Version 1.0 Monitoring Message Queue Servers 4-3 Monitoring , in the Listing the Monitors scrolling list. Select the area of the window. The MSMQ IS dialog is displayed. button to add the selected monitoring Monitor Arguments Monitoring Collections Edit Monitor Add Empty scrolling list. in the keep in mind that they are both space and case sensitive. When entering arguments directly from the keyboard, the available monitors by selecting a collection name such as MSMQ Sources monitor you want to add, such as displayed in the argument can be entered either directly into the text field from the keyboard or by selecting it from a list. To display the list, click the button to the right of the text field and select the argument. Note: source. The 5. Select the monitoring collection for which you want to display 6. When the selected monitor requires an argument, a text field is 7. Click the Tivoli Manager for Message Queue Server: User’s Guide Listing the Monitors

8. Enter the information in the Edit Monitor dialog's text fields, and then click the Change & Close button. The monitor is added, and the TME 10 Distributed Monitoring Profile Properties window is displayed. 9. To add another distributed monitoring monitor, repeat steps 4 through 7. To close the TME 10 Distributed Monitoring Profile Properties window, select Profile → Close from the menu bar and click Save & Exit in the Confirm dialog. 10. After you have added and edited the desired monitors, distribute the profiles to begin monitoring. To distribute the monitor profile:

4-4 Version 1.0 Monitoring Message Queue Servers 4-5 area of the Listing the Monitors Profiles window. area and drop the icon. Access to the server Errors returned to Application Replication requests received Replication requests sent Write requests sent Bytes in Journal Queue Bytes in Queue Messages in Journal Queue Profile Manager Subscribers Sync requests Sync replies a. Select the desired profile icon in the MSMQ IS ¹ ¹ ¹ ¹ ¹ ¹ ¹ MSMQ Queue ¹ ¹ ¹ Additional MSMQ-specific monitors b. Drag the icon over the desired subscriber icon in the Performance monitors Predefined monitors Manager for MQS supports all the performance counters that the MSMQ server provides. This enables you to monitor any of the available performance counters. For each of the monitoring sources in the following list, you can select a specific performance counter from a list of valid choices. Some of the sources may also have an instance argument that you can supply directly from the keyboard or select from a list. Manager for MQS provides performance monitors and counters for the following MSMQ monitoring sources: ■ ■ The list of monitors includes: ■ ■ ■ Performance Monitors Tivoli Manager for Message Queue Server: User’s Guide Understanding the Monitors Understanding the Monitors

¹ Messages in Queue ■ MSMQ Service ¹ IP Sessions ¹ IPX Sessions ¹ Incoming Messages/Sec ¹ MSMQ Incoming Messages ¹ MSMQ Outgoing Messages ¹ Outgoing Messages/Sec ¹ Sessions ¹ Total messages in all queues ¹ Total bytes in all queues ■ MSMQ Session ¹ Incoming Bytes ¹ Incoming Bytes/Sec ¹ Incoming Messages ¹ Incoming Messages/Sec ¹ Outgoing Bytes ¹ Outgoing Bytes/Sec ¹ Outgoing Messages ¹ Outgoing Messages/Sec Special functions are provided for the MSMQ Queue and the MSMQ Session performance counters. Because the instances can be dynamic, these functions are provided in addition to the ability to monitor a specific instance: ■ Sum of All Values ■ Average of All Values ■ Maximum of All Values

Predefined Monitors Several monitors are added to the MSMQ; 1.0 distributed monitoring profile. The additional monitors are: ■ MQ Server Status: used to update the state of the icon.

4-6 Version 1.0 Monitoring Message Queue Servers 4-7 Understanding the Monitors if the TEC event adapter for . up down StoreJournalPath StoreLogPath StorePersistentPath StoreReliablePath StoreJournalPath StoreLogPath StorePersistentPath StoreReliablePath

Generic Performance Monitor - Enables you to monitor an MSMQ performance counter by specifying the object, counter, and optionally, the instance for the performance counter. Free Disk Space Available - returns the amount of available space, in megabytes, on the volumes that are used by the MSMQ server. Parameters: ¹ ¹ ¹ ¹ Disk Usage by MSMQ server - returns the number of megabytes used for an MSMQ server directory. Parameters: ¹ ¹ ¹ ¹ Event Adapter Status - returns Generic Performance Monitor (process, % processor time, mqsvc) - displays the percentage of processor time that is used by the MSMQ service. Generic Performance Monitor (process, % processor time, q2qgw) - displays the percentage of processor time that is used by the Level 8 FalconMQ Bridge. Generic Performance Monitor (process, % processor time, msdtc) - displays the percentage of processor time that is used by the Microsoft Distributed Transaction Coordinator (DTC). Windows NT (NT event adapter) service, TECNTAdapter, is running; otherwise returns ■ Other MSMQ-specific monitors are: ■ ■ ■ ■ ■ ■ Additional MSMQ-specific Monitors Tivoli Manager for Message Queue Server: User’s Guide Understanding the Monitors

Note: Specify arguments exactly as they are defined including capitalization and spacing. ■ MQ Test - creates a test queue, sends or receives a message, then deletes the queue. ■ Special Queue Count - returns the number of messages on the selected queue. Parameters: Select a queue: ¹ Dead Letter ¹ Xact Dead Letter ¹ Journal ■ Special Queue Maximum Time - returns the oldest (in minutes) message in the selected queue. Parameters: Select a queue: ¹ Dead Letter ¹ Xact Dead Letter ¹ Journal ■ MQ Server Status - checks the status of the MSMQ server. Returns up if the server is running; otherwise returns down. To ensure that the server icon reflects the server's current status, toggle-on the Send Enterprise Console event checkbox in the Edit Monitor window for specific trigger conditions. A TEC rule has been defined to update the icon state that is based on the results of this monitor. See “Distributed Monitor (Sentry) Rules” on page B-5 for more information. ■ Distributed Transaction Coordinator Status - returns up if the DTC service is running; otherwise returns down. ■ FalconMQ Server Status - returns up if the Level 8 FalconMQ Bridge is running; otherwise returns down.

4-8 Version 1.0 Monitoring Message Queue Servers 4-9 TME 10 Understanding the Monitors . 20000000 1000000 button. Default settings are provided < <

Response Level: warning Trigger when: Monitor Schedule Time: 360 minutes Response Level: critical Trigger when: Monitor Schedule Time: 10 minutes Response Level: critical Trigger when: down Monitor Schedule Time: 30 minutes Response Level: warning Trigger when: > 1000 Add With Defaults Distributed Monitoring Users Guide For additional information on monitors, refer to the Special tasks are provided that can be started when a monitor has reached a threshold. MQ Test Free Disk Space Available for the following monitors: FalconMQ Server Status Several monitors have default settings for monitor responses in the MSMQ;1.0 distributed monitoring profile. This allows users to enter the requested monitor argument information (if any) and then to select the Default Settings for Monitor Responses Tivoli Manager for Message Queue Server: User’s Guide MSMQ Monitor Tasks MSMQ Monitor Tasks

Purge_Dead_LetterQ This task deletes all messages from the selected queue. Parameters: Select a queue: ■ Dead Letter ■ Xact Dead Letter ■ Journal Expiration Time (minutes) - Messages that have been in the queue for longer than the expiration time will be removed. The default setting is 1440 (24 hours). Note: In order for this task to work, the ID tmersvrd must have permissions to access the queue on the server. Use the MSMQ Explorer to give the tmersvrd read permissions.

Restart_Services This task will stop or start MSMQ and the DTC and Level 8 FalconMQ Bridge services if they are installed. Parameters: Stop RUNNING services - Select Yes or No. If you select Yes, all running services will be stopped and restarted. If you select No, all stopped services will be restarted. Note: Distributed Monitoring tasks run under the tmersrvd user ID which must be a member of the Administrator's group.

4-10 Version 1.0 Using Tasks and Jobs 5-1 job is a task with . Tivoli Management Framework User's from the pop-up menu to view information

Task Description . Tivoli Manager for Message Queue Server (Manager for MQS) includes a collection of tasks to help you perform functions that are related to managing Microsoft Message Queue (MSMQ) resources. Server tasks are contained within the server task library in the Manager for MQS policy region and are described in “MSMQ Server Tasks” on page 5-4. Utility tasks can be started library from and the are utility described task in “MSMQ Utility Tasks” on pageChapter 5-7. See 6, “Managing Microsoft Message Queue Events” on page 6-1 for a description of the tasks contained Enterprise within Console the (TEC) Tivoli task library. Jobs are provided for many of the tasks. A endpoints that are already defined When you start a task, you can specify the servers or other endpoints on which to run the task. Some tasks are provided on the pop-up menu for each server icon. Right-click on a server icon to display the icon’s pop-up menu. For more information, see “MSMQ Server Icon Tasks” on page 3-8. Select about the window’s text fields. For complete instructions on how to use tasks and jobs, refer to the

Guide

Tivoli Manager for Message Queue Server: User’s Guide Resources Microsoft Message Queue Chapter 5. Tasks to Manage Listing Tasks

Listing Tasks To list the tasks that are provided by Manager for MQS: 1. From the desktop, double-click on the Manager for MQS icon to display the Policy Region: Manager for MQS window. 2. To display the available MSMQ server tasks, double-click on the MSMQ Server Tasks icon. The Task Library: Server Tasks window is displayed.

Running Tasks To run a task: 1. Double-click on the task icon and complete the displayed Execute Task dialog. See “MSMQ Server Instances” on page 3-4 for more information about server instances.

5-2 Version 1.0 Using Tasks and Jobs 5-3 Configure Running Tasks button to start the task. A button to start the task. dialog, shown in the following dialog is presented, enter the information and Set & Execute Execute & Dismiss Configure Task Arguments figure, may display so that you can provide more information for the task. Not all tasks present this dialog. When a Task Arguments then click the 2. Click the Tivoli Manager for Message Queue Server: User’s Guide Running Tasks

A window showing the output from the task is displayed.

MSMQ Server Tasks Manager for MQS provides the following types of tasks for the MSMQ server:

5-4 Version 1.0 Using Tasks and Jobs 5-5 Target MSMQ server instance MSMQ server instance or or MSMQ Server Tasks Role msmq_senior msmq_senior msmq_admin msmq_admin . stopped - returns the status of all the installed - retrieves selected MSMQ data from the Task and Display_Server_Status Display_Server_Info Display_MSMQ_Info Display_Instances Start_Services Stop_Services Purge_Dead_LetterQ List_Dead_LetterQ running

is installed) – – Version – Log directory – Journal directory – Persistent directory – Reliable directory Falcon Bridge version (if Level 8 FalconMQ Bridge –– Windows NT version – Windows NT CSD version – System root Domain name MSMQ Server Environment ¹ Display_Server_Status MSMQ services on the target server. Also returns the status of the Distributed Transaction Coordinator (DTC) and Level 8 FalconMQ Bridge, if they are installed. Some possible status values are Display_Server_Info target server. The following information will be displayed: ¹ Task Type of Server information Server management ■ Tasks that provide server information include: ■ Server Information Tasks Tivoli Manager for Message Queue Server: User’s Guide MSMQ Server Tasks

■ Display_MSMQ_Info - retrieves selected MSMQ data from the target server. The following information can be displayed: ¹ Enterprise name and its Primary Enterprise Console (PEC) server ¹ Connections ¹ Machines ¹ Queues ¹ Sites ¹ Users ¹ All information types ■ Display_Instances - displays any existing instances of the MSMQ Queue and MSMQ Session performance monitors. Note: Only those queues currently being monitored will be displayed.

Server Management Tasks Tasks that enable you to manage servers include: ■ Start_Services - starts the MSMQ service and the Level 8 FalconMQ Bridge and DTC if they are installed. ■ Stop_Services - stops the MSMQ service and the Level 8 FalconMQ Bridge and DTC if they are installed. ■ Purge_Dead_LetterQ - deletes all messages from the selected queue. Parameters: Select a queue: ¹ Dead Letter ¹ Xact Dead Letter ¹ Journal Expiration Time (minutes) - Messages that have been in the queue for longer than the expiration time will be removed. The default setting is 1440 (24 hours).

5-6 Version 1.0 Using Tasks and Jobs 5-7 task Target MSMQ Server Tasks Configure MSMQ server instance MSMQ server instance MSMQ server instance MSMQ endpoint MSMQ endpoint MSMQ endpoint MSMQ endpoint is required to perform these tasks. task performs the following: - lists all the messages on the selected Configure msmq_senior Task or Dead Letter Xact Dead Letter Journal (see page 2-13) (see page 2-14 )

Retrieves the MSMQ server name and version. queue. The arrival time (in minutes) is displayed with the message label. Parameters: Select a queue: ¹ ¹ ¹ List_Dead_LetterQ Stop_Monitors Discover Install Configure Start_Debugging Stop_Debugging Start_Monitors automatically configures and creates an MSMQ server instance. When the managed node has the MSMQ server and Manager for MQS installed, the ■ For each managed node it is run against, the Manager for MQS provides utility tasks to help you manage MSMQ servers running on your managed nodes. A resource role of msmq_admin These tasks can be started from the MSMQ utility task library in the Manager for MQS policy region on the desktop. ■ Configure Tivoli Manager for Message Queue Server: User’s Guide MSMQ Utility Tasks MSMQ Utility Tasks

■ Creates an MSMQ server instance by using the server name as the server alias name. ■ Creates an icon for the MSMQ server instance. ■ When you have specified that the instance should be automatically subscribed to the default profile manager, it will add the subscription to the profile manager for that version. This task can initially populate the Manager for MQS policy region with server instances and can be run periodically to add new servers. See “Creating MSMQ Server Instances” on page 3-5 for more information about server instances. Notes: 1. When running this task, the execution mode must be set to serial. 2. To prevent any errors, ensure that the Manager for MQS has been installed on the managed node or gateway for an endpoint.

Start_Debugging This task turns on debug tracing for all the tasks and monitors shipped with Manager for MQS, including Tivoli GEM instrumentation tasks and monitors. A separate log file is written to a temporary directory for each task or monitor run while debug tracing is on. The directory is specified in the wtemp command. Tivoli GEM instrumentation log files are located in the wtemp/GEM_Instrumentation_Logs directory. This task helps to resolve problems when a task or monitor is not running properly.

Stop_Debugging This task turns off debug tracing for all the tasks and monitors shipped with the Manager for MQS, including Tivoli GEM instrumentation tasks and monitors.

5-8 Version 1.0 Using Tasks and Jobs 5-9 MSMQ Utility Tasks Management Framework, Version 3.6, Lightweight Client Framework/Tivoli Management Agent (LCF/TMA) endpoint. the TMR. Management Framework, Version 3.6, (LCF/TMA) endpoint. the Tivoli Management Region (TMR). 2. This task is not supported when the MSMQ server is on a Tivoli 1. This task does not change the status settings for the monitors at 2. This task is not supported when the MSMQ server is on a Tivoli 1. This task does not change the status settings for the monitors at This task stops all the monitors from the MSMQ collection that have been distributed to the server. The task stops only the monitor instances from this collection; other monitor instances on the server are not stopped. This task can quickly stop all of the Manager for MQS monitors when a server is down. Notes: This task starts all the monitors from the MSMQ collection that have been distributed to the server. The task starts only the monitor instances from this collection; other monitor instances on the server are not started. This task can quickly restart all of the Manager for MQS monitors after they have been stopped. Notes: Stop_Monitors Start_Monitors Tivoli Manager for Message Queue Server: User’s Guide 5-10 Version 1.0 Managing Message Queue Events 6-1 senior Target Event server Event server MSMQ server MSMQ server instance MSMQ server instance

is required to run these tasks. The following table Task

msmq_senior Configure_Event_Server Configure_Event_Console Configure_Event_Adapter Start_Event_Adapter Stop_Event_Adapter To work with MSMQ events at your TEC, you must configure both ends of the connection and configure the TEC: lists the context and target node for the tasks: or The Microsoft Message Queue (MSMQ) server issues event notifications to describe events that affect MSMQ resources. Tivoli Manager for Message Queue Server (Manager for MQS) utilizes the Tivoli Enterprise Console (TEC) event adapter for Windows NT (NT event adapter) to convert MSMQ events to the TEC format. Manager for MQS also provides a set of event classes that enable you to view and work with these events at your TEC. This chapter describes how to manage MSMQ events with tasks that are contained in the TEC task library. An authorization role of

Tivoli Manager for Message Queue Server: User’s Guide

Message Queue Events Chapter 6. Managing Microsoft 1. Configure the event server to recognize MSMQ events and the process rules concerning those events. Run the Configure_Event_Server task against the event server to be configured. 2. Configure an event console. Run the Configure_Event_Console task to assign the newly created event group to the appropriate event console. For more information, see “Configuring an Event Console” on page 6-4. 3. Configure the NT event adapter for each MSMQ server to receive its MSMQ events, convert them to the TEC format, and send them to the event server. For more information, see “Configuring the NT Event Adapter” on page 6-5.

Configuring the Event Server The Configure_Event_Server task configures an event server for Manager for MQS. When you run the task, it performs these actions: ■ Imports Manager for MQS event classes ■ Imports Tivoli Distributed Monitoring event classes if they are not already present ■ Imports the Manager for MQS rule set that provides automated responses to many events ■ Compiles the rule base to incorporate new classes and rules ■ Loads the new rule base ■ Creates a new event source (SENTRY) for Tivoli Distributed Monitoring if needed ■ Creates an event source (MSMQ) for MSMQ events ■ Creates a new event group that is called MSMQ Event Group ■ Updates the forwarding server location, if specified ■ Stops and restarts the event server to incorporate these changes You can configure more than one event server for each Tivoli Management Region (TMR). When you have multiple TMRs, you must configure at least one event server per TMR. The Manager for MQS includes a set of event classes and rules specific to MSMQ. Events received from NT event adapters are

6-2 Version 1.0 Managing Message Queue Events . 6-3 icon Task New (or MSMQ authority is window. task. task icon and senior Manager for MQS icon to display the dialog. Configuring the Event Server button to display the field. The default name is dialog. Execute Task Configure_Event_Server window. Configure_Event_Server MSMQ TEC Tasks Policy Region: Manager for MQS Execute & Dismiss required to run the A Tivoli administrator with at least global Library: TEC Tasks complete the displayed Configure_Event_Server to display the existing) Rule Base Name 3. Double-click on the 4. Click the 5. Enter the name for the new or existing rule base in the Perform the following steps to configure an event server: 1. From the desktop, double-click on the 2. Double-click the included in the MSMQ event group. To create this group and set up your event server to process MSMQ events, you should follow the steps in the next section. Note: Procedure for Configuring the Event Server Tivoli Manager for Message Queue Server: User’s Guide Configuring the Event Server

Note: You should not change the default rule base, so do not enter default in this field. 6. Enter the rule base to clone in the Rule Base to Clone (if new) field. If you are not creating a new rule base, leave this field blank. If you are creating a new rule base and you want to keep the current information, enter the current rule base name. The default value for this field is default. 7. Enter the path for the new rule base in the Path for new Rule Base (if new) field. The default value is /usr/tec_rules/msmq. If you are not creating a new rule base, leave this field blank. 8. When forwarding MSMQ event messages to another TEC, enter the name of the managed node to which events should be forwarded in the Managed Node to Forward Events (Optional) field. 9. Click the Set and Execute button to start the task. The Configure Event Server Output window displays the job status after the task is completed.

Configuring an Event Console The Configure_Event_Console task adds filters to the TEC and assigns groups. You are prompted for the name of the event console to be configured. The name is the same name as the event console that already exists on the administrator’s desktop. This task should be run after running the Configure_Event_Server task. After running the Configure_Event_Console task, start the TEC. Windows appear showing the newly added event groups and event sources.

6-4 Version 1.0 Managing Message Queue Events 6-5 Configuring an Event Console To receive MSMQ events, ensure that the NT event adapter is installed and operational on each node where the MSMQ server is running. Complete the installation of the adapter before running the task to configure the NT event adapter. The NT event adapter is packaged with the Tivoli Enterprise Console product. Tivoli Manager for Message Queue Server: User’s Guide Configuring the NT Event Adapter Configuring the NT Event Adapter

To configure the NT event adapter, run the Configure_Event_Adapter task for the managed nodes where the NT event adapter has been installed. This enables the NT event adapter for each MSMQ server to receive MSMQ events, convert them to a TEC format, and send them to the event server. Running this task: ■ Merges the message queuing event format file definitions with the existing NT event adapter format file. This is the file that defines the event format, event class, and the slot name and slot value pairs for each valid event. The message queuing event format file contains the definitions for the MSMQ events. The file's name is MSMQ_events.fmt and is located in the %BINDIR%\..\generic_unix\TME\MSMQ\TEC directory. ■ Stops and restarts the NT event adapter to incorporate the changes. See the TME 10 Enterprise Console Adapter's Guide for more information about the NT event adapter.

Starting and Stopping the NT Event Adapter Manager for MQS supplies tasks to stop and start the NT event adapter (TECNTAdapter) on the endpoint as follows: Start_Event_Adapter - Starts the NT event adapter service. Stop_Event_Adapter - Stops the NT event adapter service.

Monitoring the NT Event Adapter Manager for MQS provides the Event Adapter Status monitor to monitor the status of the NT event log adapter.

6-6 Version 1.0 Managing Message Queue Events 6-7 Filtering Events TME 10 Enterprise Console TME 10 Enterprise Console TME 10 Enterprise Console User's Guide describes the steps for building and . You can specify that the event is not to be forwarded from the managed node to the event server. In this case, you specify filter criteria in the NT event adapter configuration file. Filter criteria includes information about which events should be sent to the event server. Depending on the frequency of the harmless events, this option can save you some network traffic. The use of this file is described in the Adapter's Guide You can create new rules to exclude the event. When you do this, the event will be forwarded to the event server, but will be eliminated by the rules engine. The Rule Builder's Guide changing rules. You can exclude classes of events using the event console’s user interface. Refer to the for information. MSMQ events regarded as harmless or unlikely to require action can be suppressed from displaying on the TEC. The Tivoli Management Framework provides the following methods for you to filter out events that you do not want to see: ■ ■ ■ Tivoli Manager for Message Queue Server: User’s Guide Filtering Events 6-8 Version 1.0 GEM Instrumentation Installation 7-1

Queue Server (Tivoli GEM instrumentation) This chapter provides an overview of Tivoli GEM instrumentation. It also describes the installation prerequisites and the steps to install Tivoli GEM instrumentation. Tivoli GEM defines the concept of a business system to organize related applications. Tivoli GEM consists of a Tivoli GEM server that runs as an application on a managed node and a Tivoli GEM console running as a Java-based client. Tivoli GEM uses application instrumentation to get the necessary data to display and manipulate business systems such as MSMQ. Tivoli GEM instrumentation enables you to graphically monitor and control MSMQ server resources that reside on a Tivoli managed node. This concept is illustrated in the following figure: To manage Microsoft Message Queue (MSMQ) servers from the Tivoli Global Enterprise Manager (Tivoli GEM) console, you must install: 1. Tivoli Manager for Message 2.Queue Server (Manager for MQS) Tivoli GEM instrumentation for Tivoli Manager for Message

Tivoli Manager for Message Queue Server: User’s Guide

Instrumentation Chapter 7. Tivoli GEM Understanding the Tivoli GEM Server The Tivoli GEM server interacts with instrumented applications such as the Manager for MQS 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. This information creates and maintains a view of each business system's configuration and its availability.

7-2 Version 1.0 GEM Instrumentation Installation 7-3 Understanding the Tivoli GEM Server 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. Tivoli GEM Event Enablement must be installed and configured on the event server in order for Tivoli GEM events to be supported by the Tivoli Enterprise Console (TEC). The Tivoli GEM Event Enablement configuration includes defining the APM_HEARTBEAT, APM_THRESHOLD, and APM_CONNECTION_CHANGE event classes to TEC and defining the Tivoli GEM servers to which the Tivoli GEM events will be forwarded. Tivoli GEM instrumentation also includes TEC rules that forward all Manager for MQS monitor events to the Tivoli GEM server. The The Tivoli GEM console graphically displays the business system information from the Tivoli GEM server. The Tivoli GEM console: ■ ■ ■ 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 supports automatic aggregation as well as manual aggregation. Automatic aggregation is accomplished by the definition of component information tasks. Manual aggregation is accomplished by users dragging and dropping icons into aggregates which they define. The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable against 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. Tivoli Manager for Message Queue Server: User’s Guide Tivoli GEM Instrumentation Event Handling Understanding the Tivoli GEM Console Tivoli GEM Instrumentation Event Handling

gemmsmq rules must be defined in the current rule base. The MSMQ Configure_Event_Server task can be used to add the gemmsmq rules to the current rule base. See Appendix B, “Event Classes and Rules” on page B-1 for more information about event classes and rules. The Tivoli GEM server discovers the MSMQ components on receipt of heartbeat events. As the Tivoli GEM server receives monitor and status updates for the MSMQ business system, it updates the Tivoli GEM console.

Instrumented Components Tivoli GEM instrumentation includes instrumentation for two components: ■ MSMQ server ■ MSSQLServer (Microsoft SQL Server) 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 MSMQ server and MSSQLServer component instances based on the enterprise and site to which they belong. Each of the component instances will be automatically aggregated based on the enterprise and site in which it belongs. Thus the initial top-level view on the Tivoli GEM console will show enterprise container icons. Aggregates are depicted on the Tivoli GEM console view with a plus sign by their icon. Double-clicking an enterprise container icon will produce a view with the contained site container icons. Double-clicking a site container icon will produce a view with the contained MSMQ server and MSSQLServer component instances within that site. The instrumented aggregation is predefined in business system component, business system mapping, and software component description files that must be installed on the Tivoli GEM server. Component information tasks are required to support automatic aggregation. The Display_Enterprise and Display_Site tasks are component information tasks that have been defined for each component. These tasks return the enterprise name and site name for

7-4 Version 1.0 GEM Instrumentation Installation 7-5 Instrumented Components task, which is defined for the MSMQ Discover_Connections Successful installation of Tivoli GEM instrumentation creates task libraries, monitor collections, and file packages. The following is an overview of the resulting desktop structure: each component instance in a specific Application Management Specification (AMS)-defined format. The instrumentation also supports a two-way connection between the MSMQ component and the MSSQLServer component. There is only one MSMQ server and, at most, one MSSQLServer database on each target endpoint. The Tivoli GEM console will draw a line connecting each MSMQ icon to its associated MSSQLServer icon if the MSSQLServer exists. The instrumented connection is defined in the business system mapping and software component description files. The server component, returns the identification of the MSSQLServer component to which the MSMQ server is connected. If the MSSQLServer does not exist on the target endpoint, then no connection is returned. The MSSQLServer is always identified by the host name on which it resides. Tivoli Manager for Message Queue Server: User’s Guide Instrumentation Files, Libraries, and Profiles Instrumentation Files, Libraries, and Profiles

Top-Level Policy Region Applications_hostname-region

Policy Region PR_MSMQ_Default_hostname-region Task Libraries TL_MSMQ_1.0._Default_MSMQ_1.0._hostname-region TL_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region

Profile Managers PM_MSMQ_1.0. PM_MSMQ_1.0._Endpoint PM_MSSQLServer_6.5. PM_MSSQLServer_6.5._Endpoint

File Packages (containing instrumentation code) FP_MSMQ_1.0._Default_MSMQ_1.0._hostname-region FP_MSMQ_1.0._Default_MSMQ_1.0._hostname-region_Endpoint FP_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region FP_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region_Endpoint

Sentry Profiles (containing instrumentation monitors) SN_MSMQ_1.0._Default_MSMQ_1.0._hostname-region SN_MSMQ_1.0._Default_MSMQ_1.0._hostname-region_Endpoint SN_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region SN_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region_Endpoint

The file packages must be distributed to endpoints on which the MSMQ resources exist in order to have the instrumentation code available for local implementation.

Tasks The Tivoli GEM server furnishes the Tivoli GEM console with a set of tasks that are applicable against a component. The task menu appears on the console when a component icon is highlighted and the right-mouse button is clicked. The tasks enable Tivoli GEM users to perform actions on the component instance and have the task results returned to the Tivoli GEM console. The tasks that are supported for each component are defined in business system mapping and software

7-6 Version 1.0 GEM Instrumentation Installation 7-7 and Tasks is required. install_product msmq_admin Login Name authority is required for the user ID that you use To install Tivoli GEM instrumentation, at least authority is required. To start tasks from the Tivoli GEM console, msmq_senior to log on to the Tivoli GEM console. To run tasks and monitors to be forwarded to the Tivoli GEM server and the Tivoli GEM console, Tivoli Management Regions (TMRs) should be properly configured before installing Tivoli GEM instrumentation. Tivoli administrators need the following authorization roles: ■ Review the topics in the following sections before installing Tivoli GEM instrumentation. ■ 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. The monitor instance icon changes to a color that is based on the severity of the monitor events that are required for that monitor. See “Monitors” on page 9-8 for a list of supported monitors. component definition files that reside on the Tivoli GEM server. Installation of the Tivoli GEM instrumentation creates a task library for the MSMQ server and MSSQLServer instrumented components. Each task library contains the tasks that are supported from Tivoli GEM for that component. See “MSMQ Server Component Tasks” on page 9-2 for a list of Tivoli GEM instrumentation tasks. ■ Tivoli Management Regions Administrators Tivoli Manager for Message Queue Server: User’s Guide Instrumentation Preparing to Install Tivoli GEM Monitors Preparing to Install Tivoli GEM Instrumentation

Installation Prerequisites Before installing Tivoli GEM instrumentation, perform the following steps: ■ Ensure that all prerequisite software is installed and that you are running on a supported operating system. Refer to the Tivoli Global Enterprise Manager Release Notes for details about supported hardware and operating systems, prerequisite software, and disk space requirements. ■ Manager for MQS and the TEC must be installed and configured before installing Tivoli GEM instrumentation. See Chapter 2, “Planning for and Installing Manager for Message Queue Server” on page 2-1. ■ Install the Tivoli GEM server. ■ Install and configure Tivoli GEM Event Enablement on the event server so that the Tivoli GEM event classes are defined to the TEC and the events will be forwarded to the Tivoli GEM server. ■ Install the Tivoli GEM console.

Installing and Configuring Tivoli GEM Instrumentation Components The following table shows the location of the installed components:

7-8 Version 1.0 GEM Instrumentation Installation 7-9 1 √ Endpoint 1 √ √ Nodes Managed Target Nodes environment variables on all √ √ √ TMR Server √ √ CLASSPATH GEM Tivoli Server and x PATH Installed Component Tivoli GEM instrumentation is installed in one location and distributed to 1 Java Development Kit (JDK) 1.1. Instrumentation BDF, CDF, and icon files Instrumentation task libraries, monitor collections Manager for MQS Instrumentation file packages managed nodes and Lightweight Client Framework/Tivoli Management Agent (LCF/TMA) endpoints. Install the Java Development Kit (JDK) on the TMR server and all endpoints and managed nodes where Tivoli GEM instrumentation will be used. Do not install the Java Runtime Environment. To use JDK, you must set systems that have Tivoli GEM instrumentation. To install the JDK, perform the following steps: To install Tivoli GEM instrumentation, follow the steps in the remaining sections of this chapter. Copy the Tivoli GEM business description files (BDFs), component description files (CDFs), and icon files from the Manager for MQS CD-ROM to the Tivoli GEM server. For more information on these files and their destination directories, see Appendix C, “Business and Component Descriptions” on page C-1. Installing and Configuring Tivoli GEM Instrumentation Components Installing the Java Development Kit Copying BDF, CDF, and Icon Files Tivoli Manager for Message Queue Server: User’s Guide Installing and Configuring Tivoli GEM Instrumentation Components

1. Back up the Tivoli database. 2. Set the PATH and CLASSPATH variables: a. Add the JDK bin directory to the PATH variable, for example: PATH=....;\jdk1.1.6\bin. Note: jdk1.1.6 is the directory where JDK is installed. It may be different on your machine. b. Add the JDK classes.zip to the CLASSPATH variable, for example: CLASSPATH=\jdk1.1.6\lib\classes.zip. c. On Windows NT platforms, you can use the control panel to set the Path and CLASSPATH variables. Note that these variables are case sensitive. 3. For more information and access to JDK, point your browser to http://java.sun.com. 4. Stop and restart the Tivoli GEM server to incorporate the changes. See the Tivoli Manager for Message Queue Server Release Notes for more information about supported levels of JDK.

Creating User Groups and Logon IDs for the Tivoli GEM Console To log on to the Tivoli GEM console, the user ID and password must be defined on the managed node where the Tivoli GEM server is running. The Tivoli GEM console logon ID will be rejected unless it belongs to either the tsadmn (administrator) or tsuser (user) groups. ■ If the ID belongs to the administrator group, you can log on with administrator access. ■ If the ID belongs to the user group, you cannot log on with administrator access.

7-10 Version 1.0 GEM Instrumentation Installation 7-11 User → for NT servers). check box. Act as part of the Change/Show → . Administrative Tools → Groups list and select → . User Rights Right → . Programs → User Manager for Domains command to add the logon ID or IDs that will be Show Advanced User Rights (or Start Policies Security & Users admintool → Act as part of the operating system. Replace a process level token. Logon as a service. This is optional and only needs to be set if the Tivoli GEM server is run as an NT service. Manager operating system Characteristics of a Group ■ ■ Follow these instructions to set user rights: 1. Log on to an 2.ID with administrator authority. Click on If you are using Windows NT, additional security configuration steps are required; no additional security configuration is required for UNIX platforms. Add the following user rights to the user ID under which the Tivoli GEM server will run so that it will do the following: ■ Add the logon ID or IDs to the appropriate group or groups using SMIT Use the Use the User Manager applet to create the group or groups, then add the logon ID or IDs that will be used to sign on. used to sign onto the server. 3. Click on 5. Scroll through the 4. Check the Installing and Configuring Tivoli GEM Instrumentation Components SUN Solaris Windows NT AIX Setting Security for the Windows NT Operating System Tivoli Manager for Message Queue Server: User’s Guide Installing and Configuring Tivoli GEM Instrumentation Components

6. The Grant to list displays groups and users that are currently granted this right. If your target user ID is not listed, click on Add. 7. Click on Show Users. 8. Select the target user ID under which the Tivoli GEM server will run and click on Add. 9. Repeat this process for Replace a process level token. 10. If the Tivoli GEM server is going to be run as a service, repeat this process for Log on as a service. 11. Log off and log back on as the target ID for the user rights to take effect.

Installing Tivoli GEM Instrumentation Tivoli GEM instrumentation is installed in the PR_MSMQ_Default_hostname-region policy region which is within the Applications_hostname-region on the desktop. Install Tivoli GEM instrumentation (task libraries and monitor collections) on the TMR server. From the desktop, follow these steps: 1. Back up the Tivoli database. 2. From the menu bar, click Install → Install Product to display the Install Product dialog. 3. Click the Select Media button 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 Tivoli GEM instrumentation installation files in the Path Name text field. This should normally be the path to the Manager for MQS CD-ROM. 5. Click the Set Path button. The File Browser dialog displays the contents of the specified media in the Files scrolling list. 6. Click the Set Media & Close button. The Install Product dialog is displayed with the following products listed in the Select Product to Install scrolling list:

7-12 Version 1.0 GEM Instrumentation Installation 7-13 Clients to Install On scrolling list and click the left arrow . Available Clients Tivoli GEM Instrumentation for Microsoft MSMQ Tivoli Manager for Message Queue Server Tivoli GEM Instrumentation for Microsoft MSMQ Version 1.0 Tivoli GEM Instrumentation for Microsoft MSSQLServer Version 6.5 ■ ■ ■ button. The selections are listed in the Version 1.0 from the scrolling list. 7. Select 8. Click the targets on which to install Tivoli GEM instrumentation Installing and Configuring Tivoli GEM Instrumentation Components Tivoli Manager for Message Queue Server: User’s Guide Installing and Configuring Tivoli GEM Instrumentation Components

Note: Tivoli GEM instrumentation must be installed on the TMR server. 9. Click the Install & Close button. The Product Install window is displayed, listing the actions that will be taken when you complete the installation process. 10. Click the Continue Install button to begin the Tivoli GEM instrumentation installation process OR click the Cancel button to stop the process. When you elect to install, 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 the Close button. 12. Repeat steps 5 through 9 to install Tivoli GEM instrumentation for Microsoft MSSQLServer Version 6.5. 13. After installing Tivoli GEM instrumentation, backup the Tivoli database. After installation, Tivoli GEM instrumentation profile manager and task library icons appear in the Policy Region: PR_MSMQ_Default_tjevans-region window.

7-14 Version 1.0 GEM Instrumentation Installation 7-15 Installing and Configuring Tivoli GEM Instrumentation Components Tivoli Manager for Message Queue Server: User’s Guide 7-16 Version 1.0 GEM Instrumentation Initialization 8-1 task. See “Configuring MSMQ Configure

Servers” on page 8-2. “Subscribing to and Distributing the File Packages” on page 8-2. console, distribute the heartbeat monitors to the Tivoli target endpoints on which the MSMQ resources exist. See “Subscribing to and Distributing the Heartbeat Monitor” on page 8-2. authorization roles and login IDs. desktop using the 3. Distribute the Tivoli GEM instrumentation file packages. See 4. To discover MSMQ server resources on the Tivoli GEM This chapter also describes how to confirm Tivoli GEM discovery of MSMQ servers. 2. Configure Microsoft Message Queue (MSMQ) servers on the This chapter describes the following steps that you must perform before you can use Tivoli GEM instrumentation for Tivoli Manager for Message Queue Server (Tivoli GEM instrumentation): 1. Ensure that administrators are assigned the appropriate

Tivoli Manager for Message Queue Server: User’s Guide

Instrumentation Chapter 8. Initializing Tivoli GEM Configuring MSMQ Servers

Configuring MSMQ Servers Before doing Tivoli GEM instrumentation activities, run the Configure task from the Utility task library on the desktop to ensure configuration of all MSMQ servers.

Subscribing to and Distributing the File Packages Distribute the following Tivoli GEM instrumentation file packages to the Tivoli managed nodes that run MSMQ server resources:

FP_MSMQ_1.0._Default_MSMQ_1.0._hostname-region FP_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region

Distribute the following Tivoli GEM instrumentation file packages to the Lightweight Client Framework/Tivoli Management Agent (LCF/TMA) endpoints that run MSMQ server resources:

FP_MSMQ_1.0._Default_MSMQ_1.0._hostname-region_Endpoint FP_MSMQ_1.0._Default_MSSQLServer_6.5._hostname-region_Endpoint

If MSMQ server resources run on the TMR server, then distribute the file packages to the TMR server. Note: File packages are distributed to the managed nodes and endpoints where the monitors are distributed to the MSMQ endpoint. If the monitors are not distributed to the MSMQ endpoint, some monitors will not run correctly.

Subscribing to and Distributing the Heartbeat Monitor After you distribute the Tivoli GEM instrumentation file packages, distribute the heartbeat monitor and other monitors to all endpoints and managed nodes running MSMQ server. If MSMQ server resources run on the TMR server, then distribute the heartbeat

8-2 Version 1.0 GEM Instrumentation Initialization 8-3 -region -region_Endpoint -region -region_Endpoint hostname hostname hostname hostname window as shown below: Subscribing to and Distributing the Heartbeat Monitor Profile Manager SN_MSMQ_1.0._Default_MSSQLServer_6.5._ SN_MSMQ_1.0._Default_MSMQ_1.0._ SN_MSMQ_1.0._Default_MSMQ_1.0._ SN_MSMQ_1.0._Default_MSSQLServer_6.5._ To enable a heartbeat monitor for each MSMQ server and MSSQLServer, distribute the profiles that are listed above to the MSMQ endpoints. To subscribe and distribute the MSMQ server profiles to the MSMQ endpoints, do the following: 1. Double-click the desired profile manager icon to display a monitor to the TMR server. Tivoli GEM receives monitor status through TEC events that are forwarded to the Tivoli GEM server. The heartbeat monitor is added to the following profiles:

Tivoli Manager for Message Queue Server: User’s Guide Subscribing to and Distributing the Heartbeat Monitor

a. From the Profile Manager pull-down menu, select Subscribers. b. Ensure that your MSMQ endpoints are in the Current Subscribers list. Otherwise, select your target instances from the Available to become Subscribers scrolling list and transfer the entries to the Current Subscribers list. c. Click the Set Subscriptions & Close button. 2. To distribute the profile from the Profile Manager menu, select Distribute.

8-4 Version 1.0 GEM Instrumentation Initialization 8-5 from the pop-up menu. The profile is Subscribing to and Distributing the Heartbeat Monitor Distribute Now distributed. Observe the active Tivoli GEM console to ensure that MSMQ server and MSSQLServer icons are displayed as they are discovered. The heartbeat monitor for MSMQ servers and MSSQLServers sends a heartbeat event for each MSMQ server resource at an interval that is specified by the previously distributed heartbeat monitor. When the event server receives a heartbeat event, it forwards the event to the Tivoli GEM server, and an icon is displayed on the Tivoli GEM console. 3. Select Tivoli Manager for Message Queue Server: User’s Guide Confirming Resource Discovery 8-6 Version 1.0 Instrumentation Tasks and Monitors 9-1 described in and -region -region_Endpoint hostname hostname

PR_MSMQ_Default_ It is recommended that the Tivoli GEM instrumentation tasks be run from the Tivoli GEM console. When the Tivoli GEM instrumentation tasks are run from the desktop, the Instance_ID parameter must always be entered. To specify the Instance_ID for each task, enter the identifier of either a MSMQ server or MSSQLServer value in the following format: Tivoli GEM instrumentation tasks, in addition to Tivoli Manager for Message Queue Server (Manager for MQS) tasks, are contained in the PR_MSMQ_Default_ After you have successfully discovered Microsoft Message Queue (MSMQ) servers and MSSQLServers, you can use tasks and monitors to manage your MSMQ servers from the Tivoli GEM console. This chapter describes Tivoli GEM instrumentation tasks and monitors. “Instrumentation Files, Libraries, and Profiles” on page 7-5. On Tivoli the GEM console, you can run instrumented tasks from the MSMQ server and MSSQLServer icon's pop-up menu.

9 Tivoli GEM Instrumentation Tasks

Tivoli Manager for Message Queue Server: User’s Guide Locating and Running Tasks Monitors Instrumentation Instrumentation Tasks and Chapter 9. Tivoli GEM Locating and Running Tasks

MSMQ server: SINGLE_LOCAL_INSTANCE MSSQLServer: SINGLE_LOCAL_INSTANCE Note: The Manager for MQS tasks that are supported by Tivoli GEM do not require the Instance_ID parameter.

MSMQ Server Component Tasks Tivoli GEM instrumentation provides tasks on the pop-up menu available from each MSMQ server icon on the Tivoli GEM console. The following Tivoli GEM instrumentation tasks are supported by Tivoli GEM for the MSMQ server component: ■ Discover_Connections - reports the current connection a MSMQ server has with a MSSQLServer database. ■ Display_Enterprise - returns the enterprise name in which the MSMQ server resides. ■ Display_Site - returns the site name in which the MSMQ server resides. ■ Query_State - reports whether the MSMQ server is running, stopped, or uninstalled. ■ Query_Threshold_Settings - lists the current thresholds associated with a particular monitor. ■ Query_Thresholds - generates threshold events for the specified monitor. ■ Query_Values - reports the current values of the specified monitor. ■ Set_Polling_Interval - adjusts the frequency with which the specified monitor runs. ■ Set_Pulse - adjusts the frequency at which the heartbeat monitor runs. ■ Set_Thresholds - establishes thresholds for the specified monitor. The following subset of Manager for MQS tasks are also supported by Tivoli GEM for the MSMQ server component:

9-2 Version 1.0 Instrumentation Tasks and Monitors 9-3 Locating and Running Tasks - lists the current thresholds - adjusts the frequency with which the - returns the enterprise name in which the - generates threshold events for the specified - reports the current values of the specified - reports whether the MSSQLServer is running, - returns the site name in which the associated monitor. Query_Values monitor. Set_Polling_Interval specified monitor runs. stopped, or uninstalled. Query_Threshold_Settings associated with a particular monitor. Query_Thresholds MSSQLServer resides. Query_State associated MSSQLServer resides. Display_Site Display_Enterprise Display_Instances Display_Server_Status Display_Server_Info Display_MSMQ_Info List_Dead_LetterQ Purge_Dead_LetterQ Start_Monitors Stop_Monitors Start_Debugging Stop_Debugging Start_Services Stop_Services

■ ■ ■ ■ ■ ■ Tivoli GEM instrumentation provides the following tasks on the pop-up menu available from the MSSQLServer icon on the Tivoli GEM console: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ See Chapter 5, “Tasks to Manage Microsoft Message Queue Resources” on page 5-1 for more information about these tasks. MSSQLServer Component Tasks Tivoli Manager for Message Queue Server: User’s Guide Locating and Running Tasks

■ Set_Pulse - adjusts the frequency at which the heartbeat monitor runs. ■ Set_Thresholds - establishes thresholds for the specified monitor. ■ Start - starts the MSSQLServer database. ■ Stop - stops the MSSQLServer database.

Understanding MSMQ Server Aggregate Resources Icons representing aggregates of MSMQ server resources are automatically provided. An aggregate enterprise icon is the highest-level aggregate resource. Double-click any aggregate enterprise icon to display the aggregate site icons. Double-click an aggregate site icon to display the MSMQ server and MSSQLServer icons. When resources are not aggregated, the task may have timed out. You can also manually aggregate resources. Right-click on a resource icon and select Add to Aggregate. Select the aggregate to which you wish to add the resource. Note: If the MSMQ server is a router, then the icons will not be aggregated because the site and enterprise cannot be determined.

Navigating to MSMQ Server Resources On the Tivoli GEM console, you navigate from an aggregate enterprise icon to a specific MSMQ server and MSSQLServer icon. Right-click individual MSMQ server resources to access the pop-up menu from which you can select tasks and monitors. To locate a specific MSMQ server resource: 1. Display the Tivoli GEM Console.

9-4 Version 1.0 Instrumentation Tasks and Monitors 9-5 icon shown in the tree view. Locating and Running Tasks window is displayed showing a Middleware/DB tree view containing enterprise aggregates as GEM Manager for MQS Middleware/DB shown below. If the view is empty, ensure that you have distributed a profile that contains the heartbeat monitor to MSMQ server resources and that the MSMQ server and MSSQLServer are installed. For more information on distributing the heartbeat monitor, see “Subscribing to and Distributing the Heartbeat Monitor” on page 8-2. The 2. Double-click the Tivoli Manager for Message Queue Server: User’s Guide Locating and Running Tasks

3. Display the Middleware/DB aggregates by clicking on the box containing the + to the left of the icon. 4. To view MSMQ resources, double-click an aggregate icon such as Manager for MQS. The GEM - msmq_enterprise window is displayed containing an aggregate site icon such as msmq_site_new.

5. Double-click the aggregate site icon to view the MSMQ server and MSSQLServer icons in the GEM - msmq_site_new window.

9-6 Version 1.0 Instrumentation Tasks and Monitors 9-7 . Options Locating and Running Tasks button. window provides a progress report listing of . Tear Away Log GEM Log Start Server MSMQ server operations as they complete. In this example, the messages indicate that the MSMQ server has started. To perform a task such as starting a queue manager: 1. Right-click an MSMQ server icon. On the pop-up menu, select 2. The 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. Do the following: 1.2. From the Tivoli GEM console menu bar, select Click the Starting a Sample Task Using the Tear-Away Log Tivoli Manager for Message Queue Server: User’s Guide Locating and Running Tasks

Monitors Tivoli GEM Instrumentation provides support for MSMQ server and MSSQLServer monitors.

MSMQ Server Monitors Tivoli GEM Instrumentation installs new monitor collections (MSMQ_ and MSSQLServer_) and also provides support for all Manager for MQS-specific monitors. For more information on MSMQ server monitors, see Chapter 4, “Monitoring Microsoft Message Queue Servers” on page 4-1. Topology views on the Tivoli GEM console display status for the following events: ■ Tivoli GEM-specific Tivoli Enterprise Console (TEC) events, such as a heartbeat event ■ Threshold events showing status, such as the MQ Server Status monitor event sent by Manager for MQS-specific monitors.

9-8 Version 1.0 Instrumentation Tasks and Monitors 9-9 Monitors Event Adapter Status MQ Server Status FalconMQ Server Status Distributed Transaction Coordinator Status Free Disk Space Available Disk Usage by MSMQ Server Special Queue Count Special Queue Maximum Time MSMQ IS MSMQ Queue MSMQ Service MSMQ Session MQ Test The following Manager for MQS monitors are also supported by Tivoli GEM for the MSMQ server component: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ See “Understanding the Monitors” on page 4-5 for a these description monitors. of The state monitor monitors the status of the MSMQ server. By default, the state monitor is defined to issue a normal APM_THRESHOLD event when the application comes up and a fatal APM_THRESHOLD event when the application goes down. The event server logs the threshold event, forwards the event to the Tivoli GEM server, and the monitor icon changes color. Tivoli GEM instrumentation provides the heartbeat monitor to discover MSMQ servers. Use the profile manager to distribute the heartbeat monitor. After distribution, the heartbeat monitor issues an APM_HEARTBEAT event, at the specified interval, to the event server. The event server logs the heartbeat event and forwards the event to the Tivoli GEM server. The Tivoli GEM server discovers MSMQ server resources on receipt of a heartbeat event. Manager for MQS-Supported Monitors State Monitor Heartbeat Monitor Tivoli Manager for Message Queue Server: User’s Guide Monitors

MSSQLServer Monitors

Heartbeat Monitor The heartbeat monitor discovers MSSQLServer databases. The heartbeat monitor issues an APM_HEARTBEAT event, at the specified interval, to the event server. The TEC event server logs the heartbeat event and forwards the event to the Tivoli GEM server, which discovers MSSQLServer databases on receipt of the heartbeat event.

State Monitor The state monitor monitors the status of the database. By default, the state monitor is defined to issue a normal APM_THRESHOLD event when the database comes up and a fatal APM_THRESHOLD event when the database goes down. The event server logs the threshold event and forwards the event to the Tivoli GEM server. The Tivoli GEM console changes the color of the state monitor icon depending on the status of the APM_THRESHOLD event generated by the state monitor.

Monitor Operability Use the profile manager to distribute these monitors. You can use either the profile manager or the Set_Polling_Interval task to set the monitoring schedule for each monitor. You can use either the profile manager or the Set_Thresholds task to set the thresholds for each monitor. Tivoli GEM instrumentation includes a TEC rules which will forward all Manager for MQS monitor events to the Tivoli GEM server. When any of the above monitors specify 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.

9-10 Version 1.0 Instrumentation Tasks and Monitors 9-11 Monitors . Show as Details → View To view the status of Manager for MQS monitors that are supported by Tivoli GEM on the Tivoli GEM console, do the following: Double-click an icon for a specific MSMQ server resource to display a detailed view of monitors and their status as shown in the window below. From the menu bar, select Viewing Monitor Status Tivoli Manager for Message Queue Server: User’s Guide Monitors

9-12 Version 1.0 Command Line Interface Commands A-1 Purpose command.

Creates a MSMQ server instance Lists the attribute values of the specified MSMQ server instance Sets the attribute values of the specified MSMQ server instance wcrtmsmq This command creates a MSMQ server instance in the

Command wcrtmsmq wgetmsmq wsetmsmq NAME: wcrtmsmq PURPOSE: specified policy region. The arguments associated with the command enable you to set the initial properties of the server. This command is useful if you have several servers to manage and do not want to individually create them from the desktop. You can create a shell script to call the A description of each command follows.

Tivoli Manager for Message Queue Server (Manager for MQS) provides several commands that enable you to create, to change, and to view the attributes of Microsoft Message Queue (MSMQ) server instances from a command line. The following table lists the commands and their purpose:

Tivoli Manager for Message Queue Server: User’s Guide

Interface Commands Appendix A. Command Line Note: This command does not automatically subscribe the server instance to a profile manager; use the Tivoli wsub command to do this. See the Tivoli Management Framework User's Guide for more information about the wsub command. SYNOPSIS: wcrtmsmq –a server_alias –p policy-region –h managed_node –e endpoint –v { 10 } DESCRIPTION: Authorization: msmq_senior or msmq_admin Arguments: –a server_alias Specifies the alias name of the MSMQ server instance. –p policy-region Specifies the name of the policy region in which to create the MSMQ server instance. –h managed_node Specifies the managed node on which the MSMQ server resides. –e endpoint Specifies the endpoint on which the MSMQ server resides. –v { 10 } Specifies the version of the MSMQ server. SEE ALSO: wsetmsmq, wgetmsmq

NAME: wgetmsmq PURPOSE: This command shows the attributes of an MSMQ server instance. SYNOPSIS: wgetmsmq [–a] [–h] [–e] [–v] msmq_server_alias DESCRIPTION: Authorization: msmq_senior or msmq_admin Arguments:

A-2 Version 1.0 Command Line Interface Commands A-3 msmq_admin or new_server_alias msmq_server_alias

–a

This command updates a MSMQ server instance. Specifies the new alias name of the MSMQ server instance. The current server alias of the MSMQ server. Displays the server alias name of the MSMQ server instance. Displays the managed node name of the MSMQ server instance. Displays the endpoint name of the MSMQ server instance. The current server alias of the MSMQ server. Displays the version of the MSMQ server instance. new_server_alias

DESCRIPTION: Authorization: msmq_senior SYNOPSIS: wsetmsmq Arguments: –a msmq_server_alias SEE ALSO: wcrtmsmq, wgetmsmq NAME: wsetmsmq PURPOSE: –a –h –e –v msmq_server_alias SEE ALSO: wcrtmsmq, wsetmsmq Tivoli Manager for Message Queue Server: User’s Guide A-4 Version 1.0 Event Classes and Rules B-1

MSMQ_Monitors is a superclass definition for all MSMQ monitor events. The classes in the following table inherit from the MSMQ_Monitors superclass, and correspond to the distributed monitoring monitor names: Message queue server events can be received from Tivoli Distributed Monitoring monitors, or from the NT event adapter that forwards events that the Microsoft Message Queue (MSMQ) server application generates to the Tivoli Enterprise Console (TEC). This appendix contains a list of the event classes and rules that the Tivoli Manager for Message Queue Server (Manager for MQS) defines.

B Distributed Monitoring Events

Tivoli Manager for Message Queue Server: User’s Guide Classes Manager for Message Queue Server Event

Rules Appendix B. Event Classes and Manager for Message Queue Server Event Classes

Monitor Name TEC Baroc Class Name Event adapter status MSMQ_tecadup MSMQ server status MSMQ_serverup Generic performance MSMQ_perfmon Free disk space available MSMQ_diskavail MQ test MSMQ_MSMQtest Disk usage by MSMQ server MSMQ_diskusage Distributed Transaction Coordinator MSMQ_dtcup status FalconMQ server status MSMQ_falconup Special queue count MSMQ_MSMQdlqcnt Special queue maximum time MSMQ_MSMQdlqtim MSMQ IS MSMQ_MSMQ_IS MSMQ session MSMQ_MSMQ_session MSMQ service MSMQ_MSMQ_service MSMQ queue MSMQ_MSMQ_queue

NT Event Adapter Events MSMQ_Event is a superclass definition for all MSMQ events that are forwarded from the NT event adapter on the managed node. When the NT event adapter receives an event that is generated by the MSMQ server application, it maps fields in the MSMQ-generated event to TEC slots.

B-2 Version 1.0 Event Classes and Rules B-3 TEC Slots CRITICAL HARMLESS WARNING severity ■ ■ ■ category msg sid source (MSMQ) date (date+time) sub-origin host name origin id sub-source Manager for Message Queue Server Event Classes NT Event Fields Error Information Warning System identifier (SID) - User Computer Origin Event ID Source Type ■ ■ ■ Category Message Date + Time The following is an example of an MSMQ TEC event: Tivoli Manager for Message Queue Server: User’s Guide Manager for Message Queue Server Event Classes

MSMQ_Event; server_handle=1; date_reception=912711956; event_handle=1; source=MSMQ; sub_source=MSMQ; origin=9.37.64.101; sub_origin=N/A; hostname=tjevans; adapter_host=N/A; status=OPEN; administrator=''; acl=[ admin]; severity=HARMLESS; date='Dec 03 14:08:52 1998'; duration=0; msg='Initialization completed successfully.'; msg_catalog=none; msg_index=0; num_actions=0; credibility=0; repeat_count=0; cause_date_reception=0; cause_event_handle=0; category=1; eventType=N/A; id=2028; sid=N/A; END

Rules for Manager for Message Queue Server Events The TEC includes a rules engine that processes events according to a set of rules that are provided by applications or added by users. Manager for MQS supplies a default rule base, which is a set of rules that provide correlation of related events and give automated responses where possible. You can change these rules and also write rules that are tailored for your installation. See the TME 10 Enterprise

B-4 Version 1.0 Event Classes and Rules B-5 file. msmq_events.baroc msmq_monitors.baroc for more information on how to use the file contains a set of rules for the Removes duplicate MSMQ monitor events. Sets a timer on each harmless event to 15 minutes. A timer rule closes the event when the timer expires. Removes duplicate MSMQ events. Sets a timer on each harmless event to 15 minutes. A timer rule will close the event when the timer expires. Closes harmless events after 15 minutes. file contains a set of rules for the Rules for Manager for Message Queue Server Events msmq_monitors.rls msmq_events.rls The event processing rules that are provided with the Manager for MQS are: Rule Namedup_monitor_msmq Description timeharmless_monitor_msmq The MSMQ_monitors class of events that are sent from the monitors. This rule set uses the classes from the Console Rule Builder's Guide The TEC graphical rule editor. file. The event processing rules that are provided with the Manager for MQS are: Rule Namedup_msmq Description timeharmless_msmq timer_rule MSMQ_Event class of events that are sent from the NT event adapter. This rule set uses the classes from the Distributed Monitor (Sentry) Rules NT Event Adapter Rules Tivoli Manager for Message Queue Server: User’s Guide Rules for Manager for Message Queue Server Events

closeharmless_monitor_msmq Closes harmless events after 15 minutes. A sample rule is provided to show how to run a task from a monitor TEC event. This rule is in the msmq_monitors.rls file, but is commented out.

Tivoli GEM Instrumentation Distributed Monitoring (SENTRY) Rules The gemmsmq.rls file contains fourteen gemmsmq rules for the MSMQ_Monitors class of events that are sent from the monitors. The gemmsmq rules forward all MSMQ monitor events to the Tivoli GEM server. The TME 10 Enterprise Console Rule Builder’s Guide describes the steps for building and changing rules.

B-6 Version 1.0 Business and Component Descriptions C-1

Tasks that can initiate actions against an MSMQ server resource component Monitors that collect status information on an MSMQ server resource component ■ This appendix describes the Tivoli GEM business description files (BDFs) and component description files (CDFs) that are provided for Tivoli Manager for Message Queue Server (Manager for MQS). 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 message queue processing. It also includes performance measures that determine whether the business system is functioning properly. For example, a Microsoft Message Queue (MSMQ) server business system would include all the instances of MSMQ server resources and their associated MSSQLServer resources that are used in your network. The business system includes descriptions of: ■

Tivoli Manager for Message Queue Server: User’s Guide

Component Descriptions Appendix C. Business and Installing BDF, CDF, and Icon Files

Installing BDF, CDF, and Icon Files You can install the BDF, CDF, and icon files by doing one of the following: ■ 1. Copy the BDFs and CDFs in the /GEMFILES directory on the Manager for MQS CD-ROM to the following directories on the Tivoli GEM server: ¹ %BINDIR%\TDS\server\db\backup\appdefs ¹ %BINDIR%\TDS\server\db\current\appdefs 2. Copy all the icon files in the /GEMFILES directory on the Manager for MQS CD-ROM to the following directories on the Tivoli GEM server: ¹ %BINDIR%\TDS\server\db\backup\icons ¹ %BINDIR%\TDS\server\db\current\icons 3. Stop and restart the Tivoli GEM server so that the server parses the new BDFs and CDFs, obtaining the MSMQ business views, tasks, and monitor descriptions. Error messages appear in the %BINDIR%\TDS\server\log\ihsmessage.log file on the Tivoli GEM server. ■ If this is a new installation, the BDF, CDF, and icon files may be installed by loading the provided amp file as follows: 1. At the Tivoli GEM console, select File → Load New AMP. 2. Select the /GEMFILES/msmq.pkg amp file.

Business and Component Description Files Tivoli GEM instrumentation provides the following business description files and the following component description files: ■ Manager for MQS: Managerfor1_0Tivol.bsdf

C-2 Version 1.0 Business and Component Descriptions C-3 MSMQ1_0Microsoft.gdf Business and Component Description Files Enterprise aggregate icon Site aggregate icon MSMQ server icon MSMQ1_0Microsoft.bmdf MSSQLServer6_5Micros.bmdf MSMQ1_0Microsoft.cdf MSSQLServer6_5Micros.cdf

%BINDIR%\TDS\server\db\current\appdefs %BINDIR%\TDS\server\db\backup\appdefs %BINDIR%\TDS\server\db\current\icons %BINDIR%\TDS\server\db\backup\icons MSMQ System Business System Component: MSMQsystem1_0Microso.bcdf MSMQ Business System Mapping files for MSMQ servers and MSSQLServer databases: ¹ ¹ MSMQ Software Component files for MSMQ servers and MSSQLServer databases: ¹ ¹ MSMQ Global Description File:

The business description files must be copied into the following directories on the Tivoli GEM server: ■ ■ The icon files include the following: 16_enterprise.gif and 32_enterprise.gif 16_site.gif and 32_site.gif 16_msmq.gif and 32_msmq.gif The icon files must be copied into the following directories on the Tivoli GEM server: ■ ■ ■ ■ ■ ■ Tivoli Manager for Message Queue Server: User’s Guide Icon Files C-4 Version 1.0 GEM Instrumentation Task Descriptions D-1 , indicating whether the MSMQ server gone Description and Parameters , or down , up

The name of the monitor that you want to query. SINGLE_LOCAL_INSTANCE SINGLE_LOCAL_INSTANCE MonitorName Returns Gets the last threshold levels for the specified monitor. It then places the last threshold levels in the value fields of an APM_THRESHOLD event and sends that event. This task can be run by right-clicking on the selected monitor shown in the detailed monitor view. Parameters: Instance_ID resource is running, is down, or has been deleted. Parameters: Instance_ID

The following tables provide Tivoli GEM instrumentation task descriptions and their required field entries.

Task

Query_Thresholds Query_State Tivoli Manager for Message Queue Server: User’s Guide Descriptions Instrumentation Instrumentation Task Appendix D. Tivoli GEM Task Description and Parameters Query_Threshold_ Lists the current thresholds associated with a specified monitor. Settings Parameters: Instance_ID SINGLE_LOCAL_INSTANCE MonitorName The name of the monitor that you want to query. Query_Values Returns the last threshold value for the specified event. This includes manufacturer, product, version number, hostname, Internet Protocol (IP) address, MSMQ server resource ID such as host name, and monitor values. This task can be run by right-clicking on the selected monitor shown in the detailed monitor view. Parameters: Instance_ID SINGLE_LOCAL_INSTANCE MonitorName The name of the monitor that you want to query. Set_Polling_Interval Sets the polling interval for a monitor and redistributes the monitor. This task can be run by right-clicking on the selected monitor shown in the detailed monitor view. Parameters: Instance_ID SINGLE_LOCAL_INSTANCE MonitorName The name of the monitor that you want to query. Interval How often the monitor is run in minutes; in an integer such as 60.

D-2 Version 1.0 GEM Instrumentation Task Descriptions D-3 Description and Parameters = < <= = does not match matches normal informational warning severe critical fatal not equal changes to changes from crosses above crosses below > > The severity level of the monitor response that will be sent when the threshold condition is met. 0 1 2 3 4 5 2 3 4 5 6 7 8 9 10 11 The specific conditions that trigger response-level actions, such as: 0 1 The new value you want to set as the operator threshold. SEVERITY OPERATOR Defines the circumstances under which threshold events are sent to Tivoli GEM by the event server. Sets the VALUE, OPERATOR, and SEVERITY in the monitor. This task can be run by right-clicking on the selected monitor shown in the detailed monitor view. Parameters: VALUE Task Set_Thresholds Tivoli Manager for Message Queue Server: User’s Guide Task Description and Parameters Set_Thresholds Instance_ID (continued) SINGLE_LOCAL_INSTANCE MonitorName The name of the monitor that you want to query. ThresholdDefinition VALUE,OPERATOR,SEVERITY such as 1400,0,2. Note: When run from an icon instance on the Tivoli GEM console, you must enter the Monitor Name, select the Severity from the screen, and select the Operator from a pop-up menu. You must also enter a Value. Start Starts the MSSQLServer database. Parameters: Instance_ID SINGLE_LOCAL_INSTANCE Stop Stops the MSSQLServer database. Parameters: Instance_ID SINGLE_LOCAL_INSTANCE Set Pulse Sets the polling interval for the heartbeat monitor. Parameters: Instance_ID SINGLE_LOCAL_INSTANCE Discover_ Connections Only for MSMQ servers, returns the MSSQLServer that is a prerequisite for MSMQ. Parameters: primary_handle secondary_handle SINGLE_LOCAL_INSTANCE Connection_Type = MSSQL_DB The defined connection is of type MESSAGE. Connection_Direction = 3 3 indicates a 2–way connection.

D-4 Version 1.0 GEM Instrumentation Task Descriptions D-5 . must be followed with a parm1 Description and Parameters MonitorName > > hostname hostname SINGLE_LOCAL_INSTANCE SINGLE_LOCAL_INSTANCE < < - the name of the monitor that you want to query. This secondary_handle secondary_handle Returns the enterprise name in which the associated MSMQ server resides. This task is not supported on MSMQ routers. Parameters: primary_handle Returns the site name in which the associated MSMQ server resides. This task is not supported on MSMQ routers. Parameters: primary_handle required when you run Tivoli GEM instrumentation tasks from the desktop. GEM instrumentation tasks from the MSMQ server icon's pop-up menu on the Tivoli GEM console. require the Instance_ID parameter. 1. The Instance_ID parameter, which identifies the server, is 2. The Instance_ID parameter is not required when you run Tivoli 3. Manager for MQS tasks that are supported by Tivoli GEM do not comma and a space when you specify parameter is case sensitive. Several Tivoli GEM instrumentation tasks require a Monitor Name parameter. The parameter must be entered in the following format: MonitorName, parm1,parm2 where: MonitorName Notes: Task Display_Enterprise Display_Site Tivoli Manager for Message Queue Server: User’s Guide parm1 - case sensitive and must be enclosed in double-quotes if it contains spaces. When you specify parm2, parm1 must be followed by a comma and parm2, with no intervening spaces. parm2 - case sensitive. Monitor name and parameter values that you can enter include: ■ Event Adapter Status ■ MQ Server Status ■ FalconMQ Server Status ■ Distributed Transaction Coordinator Status ■ Free Disk Space Available Parameters: ¹ StoreJournalPath ¹ StoreLogPath ¹ StorePersistentPath ¹ StoreReliablePath ¹ ■ Disk Usage by MSMQ Server Parameters: ¹ StoreJournalPath ¹ StoreLogPath ¹ StorePersistentPath ¹ StoreReliablePath ¹ ■ MSMQ IS Parameters: ¹ Access to the server ¹ Errors returned to Application ¹ Replication requests received ¹ Replication requests sent ¹ Sync requests ¹ Sync replies ¹ Write requests sent ¹ ■ MSMQ Queue

D-6 Version 1.0 GEM Instrumentation Task Descriptions D-7 Incoming Bytes,@+ Incoming Bytes,@# Incoming Bytes,@> Incoming Bytes/Sec,@+ Incoming Bytes/Sec,@# Incoming Bytes/Sec,@> Incoming Messages,@+ Incoming Messages,@# Incoming Messages,@> IP Sessions IPX Sessions Incoming Messages/sec MSMQ Incoming Messages MSMQ Outgoing Messages Outgoing Messages/sec Sessions Total messages in all queues Total bytes in all queues Bytes in Journal Queue,@+ Bytes in Journal Queue,@# Bytes in Journal Queue,@> Bytes in Queue,@+ Bytes in Queue,@# Bytes in Queue,@> Messages in Journal Queue,@+ Messages in Journal Queue,@# Messages in Journal Queue,@> Messages in Queue,@+ Messages in Queue,@# Messages in Queue,@>

Parameters: ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ Parameters: ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ Parameters: ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ ¹ MSMQ Session MSMQ Service ■ ■ Tivoli Manager for Message Queue Server: User’s Guide ¹ Incoming Messages/Sec,@+ ¹ Incoming Messages/Sec,@# ¹ Incoming Messages/Sec,@> ¹ Outgoing Bytes,@+ ¹ Outgoing Bytes,@# ¹ Outgoing Bytes,@> ¹ Outgoing Bytes/Sec,@+ ¹ Outgoing Bytes/Sec,@# ¹ Outgoing Bytes/Sec,@> ¹ Outgoing Messages,@+ ¹ Outgoing Messages,@# ¹ Outgoing Messages,@> ¹ Outgoing Messages/Sec,@+ ¹ Outgoing Messages/Sec,@# ¹ Outgoing Messages/Sec,@> ¹ ■ MQ Test ■ Special Queue Count Parameters: ¹ DeadLetter ¹ XactDeadLetter ¹ Journal ¹ ■ Special Queue Maximum Time Parameters: ¹ DeadLetter ¹ XactDeadLetter ¹ Journal

D-8 Version 1.0 Instrumenting Connection Support E-1 Tivoli Global . is defined as:

conversational origin destination

is: → ← ←→ >, MSMQ:SINGLE_LOCAL_INSTANCE is the communication type 1 = 2 = 3 = hostname To create a relation, do the following: Define a Relation ("MSMQ", Communication[], direction) where: MSMQ direction Enterprise Manager Instrumentation Guide To instrument products that provide connections to MSMQ, you implement the relation in your component instrumentation. The following description provides only the values required for the Java Relation class. For more information, refer to the Communication array

[0] Hostname: [1] TCP/IP Address, MSMQ:SINGLE_LOCAL_INSTANCE Tivoli Manager for Message Queue Server: User’s Guide or

Connection Support to MSMQ Appendix E. Instrumenting E-2 Version 1.0 Finding and Correcting Problems F-1

installing Manager for MQS. This is especially important if Machine or server availability Operating system environment MSMQ server installation Manager for MQS configuration Targeting miscues Is there anything I should verify prior to installation to prepare for the Manager for MQS? These guidelines may help prevent difficulties when installing and configuring the Manager for MQS: What to do: Test Distributed Monitoring (Sentry), Software Distribution (Courier) (if using Tivoli GEM instrumentation), and the NT event adapters before ■ ■ ■ ■ This appendix covers some of the troubleshooting problems by answering your questions. Problems that you may encounter while using the Tivoli Manager for Message Queue Server (Manager for MQS) to manage a Microsoft Message Queue (MSMQ) installation can have many different causes such as: ■

Tivoli Manager for Message Queue Server: User’s Guide Installation Hints

Correcting Problems Appendix F. Finding and Installation Hints

you are installing Manager for MQS on a new Tivoli installation. Manager for MQS uses these core applications; if they are not working, Manager for MQS will not work either. At a minimum, you should be able to do the following: ■ Start a simple task. If you have TEC, then the easiest thing to do is to start one of the tasks in the TEC library. ■ Deploy some distributed monitoring monitors on the MSMQ server machines. Some basic NT monitors should be sufficient. Deploy monitors that send a pop-up dialog to the administrator. Also send a TEC event to ensure that the monitor is running and that the TEC receives distributed monitoring events. ■ Send events to the event server that uses the wpostemsg utility. After your basic Tivoli installation seems stable, then you are ready to install the Manager for MQS. ■ Backup your database on each machine where Manager for MQS will be installed. ■ Install the Manager for MQS. ■ Backup your database on each machine where Manager for MQS was installed. ■ Optionally, install Tivoli GEM instrumentation. ■ Backup your database on each machine where Tivoli GEM instrumentation was installed. Note: After the files are loaded onto the system from the installation media, an installation program is run to create the Manager for MQS policy region, MSMQ object class, tasks, jobs, and roles. The installation program creates a log file that is named %TMP%\msmq_init.log. %TMP% is the directory that is pointed to by the wtemp command. If the log file does not exist, the problem originated prior to starting the installation program. In this case, after the

F-2 Version 1.0 Finding and Correcting Problems F-3 from Installation Hints exist, the installation program was started. does Add an instance of the server on the desktop, creating an icon and a Tivoli object. Ensure that the newly created endpoint, server alias name (MSMQ), is added to the appropriate subscriber list. Rerun the job. Review the log file to determine the cause of the problem. The installation program can be run more than once. When the problem is resolved, run the installation program that is located in %BINDIR%\..\generic_unix\TME\MSMQ\msmq.init the command line. You do not need to restore the backup of the Tivoli database. problem has been corrected, reinstall the product from the installation media. If the log file MSMQ servers that are to be managed should be added as subscribers to the appropriate profile manager. The typical scenario should be to: ¹ ¹ ¹ The following information may help you solve problems encountered using tasks and jobs from the desktop: Why do I get a blank window when I run a job? Jobs are set up at installation time to create a convenient way to start tasks. When you run a job and an empty window is displayed, the job was run against a nonexistent endpoint. The typical cause of this error is that a job is run against a profile manager endpoint and the profile manager does not have any subscribers. Therefore, the job is not run against any node. What to do: ■ Tivoli Manager for Message Queue Server: User’s Guide Desktop Hints on Using Tasks and Jobs from the Hints on Using Tasks and Jobs from the Desktop

■ Run the task directly (instead of the job) and specify the appropriate endpoints. Why does a task fail with a permissions error? (MSMQ): The task failed to execute. (MSMQ): : no permission for ’MSMQ Server Tasks/Diagnostic_Logging-Set’ for operation ’run_task’ What to do: 1. Ensure that you assigned the resource roles msmq_senior or msmq_admin (or both) to the administrator that runs the task. See “Assigning Authorization Roles” on page 3-2 for more information. 2. After the resource roles have been assigned, stop and then restart the desktop so that the assigned roles will take effect.

Hints on Running Tasks from the Tivoli GEM Console The following information may help you solve problems encountered using tasks from the Tivoli GEM console. Why does a task fail with a permission error, such as: A reference to an object is not valid. The object no longer exists or is a disconnected TMR ? What to do: 1. Ensure that the Tivoli GEM server and the MSMQ server are in the same TMR or in connected TMRs with shared resources. ■ To verify connected TMRs from the desktop, select Desktop → TMR Connections → List Connections to view current connections. ■ To verify shared resources from the desktop, select Desktop → TMR Connections → Update Resources. This enables you to view available resources for remote TMRs and to select resources to update for sharing.

F-4 Version 1.0 Finding and Correcting Problems F-5 directory to Distribution from the pop-up PM_MSSQLServer_6.5. and task. Distribute to ALL Levels of Edit Properties checkboxes have been selected. Make subscribers’ profile an EXACT pull-down menu, select and Profile PM_MSMQ_1.0. Start_Debugging . Ensure that the Hints on Running Tasks from the Tivoli GEM Console menu. Defaults Subscribers COPY of this profile profile managers. %DBDIR%\tmp\GEM_instrumentation_logs determine the problem. 4. From the 2. Select each profile collection. 3. Right-click and select schedule of 10 minutes, to all MSMQ servers. This will ensure that all current MSMQ servers are discovered and that all MSMQ servers that were removed are deleted from the Tivoli GEM console. Reopen the Tivoli GEM client to view current MSMQ servers. Ensure that Distributed Monitoring has been installed on the managed node. Ensure that monitors are defined and enabled within the profile. Ensure that you distributed the monitors to the subscriber list. 1. Open the Turn on debugging and check the monitor logs as follows: 1. Run the 2. Look in the monitor log that is located in the Why are my monitors not running? What to do: If monitors do not seem to be running, do the following: ■ ■ ■ 2. Redistribute the heartbeat monitor, with a revised monitoring ■ Why is a non-MSMQ monitor not working? Tivoli Manager for Message Queue Server: User’s Guide Hints on Using Monitors Hints on Using Monitors

What to do: 1. Verify that a monitor is running: ■ Specify the following on the Edit Sentry Monitor window: ¹ Select a Response Level of always. ¹ Select Popup and select your administrator’s desktop. ¹ Set the monitoring schedule to 5 minutes. ■ Ensure that the monitoring profile has been distributed to the managed node. On the Distribute Profile window, ensure that the Make subscribers’ profile an EXACT COPY of this profile checkbox is selected. ■ Check the SentryStatus Notice Group to see if there have been problems in distributing the monitor. 2. When a pop-up dialog is displayed approximately every 5 minutes, then the monitor is running. Note that it may take a few minutes for the monitor to start running. Why aren’t the statuses of Manager for MQS monitors that are supported on the Tivoli GEM console displayed? What to do: 1. Verify that the Manager for MQS monitor has been distributed to the MSMQ server managed node and that a monitor response has been defined that sends a TEC event. 2. Verify that the APM_THRESHOLD and the MSMQ_Monitors classes have been defined for the event server. 3. Verify that the gemmsmq.rls and the interapp.rls rule bases have been installed on the event server. These rule bases enable the Manager for MQS monitor events to be displayed on the TEC and forwarded to the Tivoli GEM server: a. Enter the wlscurrb command to display the name of the active rule base. b. Enter the wlsrbclass active_rulebase_name command to list the defined event classes. Ensure that the

F-6 Version 1.0 Finding and Correcting Problems F-7 and command to , ensure that the gemmsmq.rls is not Hints on Using Monitors task to define the classes and active_rulebase_name

Tivoli Global Enterprise Manager command on the event server command and option to enable debugging . %BINDIR%\TDS\server\log\ihsmessage.log rule bases are defined. wlsrbrules wtdumprl TEC is configured to send events to the Tivoli GEM server. Refer to the interapp.rls Configure_Event_Server the rules. events tserver start -b and to have events logged to the Tivoli GEM server log. file to see if the Tivoli GEM server is receiving the threshold events. events but the Tivoli GEM server User's Guide list the defined rules. Ensure that the APM_THRESHOLD APM_THRESHOLD and MSMQ_Monitors classes are defined. d. When the needed classes or rules are not defined, run the TEC. If Manager for MQS monitor events are not displayed on the TEC, do the following: a. Run the b. Look for errors associated with the MSMQ_Monitors Tivoli GEM server. a. Ensure that the Tivoli GEM server was started with the b. Look in the c. When the TEC is receiving Manager for MQS monitor c. Enter the 4. Verify that Manager for MQS monitor events are reaching the 5. Verify that Manager for MQS monitor events are getting to the Tivoli Manager for Message Queue Server: User’s Guide Hints on Using the TEC

Hints on Using the TEC Why am I not seeing any events on the TEC? What to do: When you are not receiving events that you expect on your TEC, check the following: ■ MSMQ server endpoint ¹ Has the event adapter been installed and configured on the endpoint? – Ensure that the TECNTAdapter service is running. – Ensure that the ServerLocation value is set to the correct event server name. This field is set in the tecad_nt.conf file (on the TEC 2.6 NT adapter the file name is tecad_nt.con). – When running the TEC 3.1 NT event adapter, use the postemsg utility to send a message to the event server. On the server, enter the wtdumprl command to see if the message was sent. This verifies that the communication between the adapter and the server is operational. ¹ Ensure that the NT event log is not full. When the event log is full, no new events will be written to the log. Therefore, the adapter will not be receiving new events to forward to the event server. ■ Event Server ¹ Ensure that the event server is operational. ¹ Ensure that Manager for MQS classes and rules are installed and configured on the event server. 1. Enter the wlscurrb command to display the name of the active rule base. 2. Enter the wlsrbclass active_rulebase_name command to list the defined event classes. Ensure that the

F-8 Version 1.0 Finding and Correcting Problems F-9 task task to command and parsing_failed task has not been run. Hints on Using the TEC interapp.rls active_rulebase_name

command on the event server to Configure_Event_Server Configure_Event_Adapter rule bases are also defined. wtdumprl wlsrbrules Configure_Event_Server display the events in the reception log on the event server. information for the MSMQ server endpoint in this section. define the classes and the rules. not defined, configure Tivoli GEM Event Enablement. gemmsmq.rls not defined, run the to list the defined rules. Ensure that the msmq_events.rls and the msmq_monitors.rls rule bases are defined. If Tivoli GEM instrumentation is installed, ensure that the has not been run. This task loads the definitions for the MSMQ events into the NT event adapter. MSMQ_Event but still are not being processed, then the MSMQ_Event and MSMQ_Monitors classes are defined. If Tivoli GEM instrumentation is installed, ensure that the APM_HEARTBEAT and APM_THRESHOLD classes are also defined. NT_Base, then the – When the events are not in the list, see the previous The events are being received, but have a 5. If the Tivoli GEM enablement classes and rules are 4. If the required Manager for MQS classes or rules are Check to see if the events are being received at the event server. – Enter the – If the MSMQ events are coming over as class 3. Enter the message. – If the MSMQ events are coming over as class ¹ ¹ Tivoli Manager for Message Queue Server: User’s Guide Hints on Using the TEC

This task loads the definitions for the MSMQ events into the event server. ¹ The events are being received and are processed. Check the Event Groups that have been assigned to the TEC. If the MSMQ Event Group is not listed, then the console has not been set up to display the MSMQ events. Run the Configure_Event_Console task to assign the event group to the TEC. This can also be done manually from the desktop interface.

Hints on Using the Tivoli GEM Console Why isn’t an MSMQ server icon displayed on the Tivoli GEM console? What to do: ■ Verify that the Tivoli GEM business description files (BDFs) and the component description files (CDFs) have been installed in the %BINDIR%\TDS\server\db\current\appdefs directory on the Tivoli GEM server. Stop and restart the Tivoli GEM server so that the server parses the BDFs and CDFs. See Appendix C, “Business and Component Descriptions” on page C-1. Note: After you stop the Tivoli GEM server, you may want to delete the ihserror.log and ihsmessage.log files in the %BINDIR%\TDS\server\log directory. This enables you to see only new messages regarding the Tivoli GEM server when you restart it. You may also want to delete the files in the %BINDIR%\TDS\server\db\backup\datab and %BINDIR%\TDS\server\db\current\datab directories to refresh the topology database and rediscover all MSMQ server and MSSQLServer components. ■ Verify that the heartbeat monitor has been distributed to the MSMQ server instances.

F-10 Version 1.0 Finding and Correcting Problems F-11 list. command to Distribution . from the pop-up list includes MSMQ from the pop-up menu. PM_MSSQLServer_6.5. list. and Distribute to ALL Levels of Current Subscribers Edit Properties Subscribers checkboxes are selected. active_rulebase_name

command to display the name of the Make subscribers’ profile an EXACT pull-down menu, select Hints on Using the Tivoli GEM Console task to verify that the MSMQ server is Current Subscribers and Set Subscriptions & Close PM_MSMQ_1.0. Profile wlsrbclass wlscurrb . Ensure that the Available Subscribers Query_State list the defined event classes. Ensure that the APM_HEARTBEAT and the APM_THRESHOLD classes are defined. menu. Defaults Subscribers COPY of this profile active rule base. profile collections. server managed nodes. If the list does not include these managed nodes, do the following: a. Select the MSMQ server managed nodes from the with a monitoring schedule of 10 minutes for the initial MSMQ server discovery. b. Move them to the c. Select corresponding subscriber to distribute the profile. 3. From the 2. Enter the 1. Select the 2. Right-click and select 7. Ensure that the 4. Ensure that the heartbeat monitor is enabled and defined 5. Select each managed node 6.where an MSMQ server exists. Right-click and select running. Verify that the Tivoli GEM TEC classes and rules are installed: 1. Enter the 8. Select a profile collection and drag and drop it to the Run the ■ ■ Tivoli Manager for Message Queue Server: User’s Guide Hints on Using the Tivoli GEM Console

3. Enter the wlsrbrules active_rulebase_name command to list the defined rule bases. Ensure that the interapp.rls rule base is defined because this rule base forwards APM_HEARTBEAT events to the Tivoli GEM server. 4. When the needed classes or rules are not defined, configure the Tivoli GEM event enablement. ■ Verify that the APM_HEARTBEAT event is getting to the TEC. When the APM_HEARTBEAT event does not display on the TEC: 1. Enter the wtdumprl command on the event server. 2. wtdumprl will display the events in the reception log on the event server. 3. Look for errors associated with the APM_HEARTBEAT event. ■ Check the ihsttec.cfg file in the %BINDIR%\TDS\EventService directory to verify that the TEC event server has been configured to send events to the Tivoli GEM server. ■ Verify that the APM_HEARTBEAT event is getting to the Tivoli GEM server. 1. Start the Tivoli GEM server with the tserver start -b command and option to log events to the Tivoli GEM server log. 2. Look in the %BINDIR%\TDS\server\log\ihsmessage.log file to see if the Tivoli GEM server is receiving the heartbeat events. 3. When the TEC is receiving the APM_HEARTBEAT and APM_THRESHOLD events but the Tivoli GEM server is not, ensure that the TEC is configured to send events to the Tivoli GEM server. Refer to the Tivoli Global Enterprise Manager User's Guide. ■ Turn on Tivoli GEM instrumentation debugging and look for errors in the heartbeat log:

F-12 Version 1.0 Finding and Correcting Problems F-13 will not return file that is located in dumpis task. task, then run the Hints on Using the Tivoli GEM Console MSMQ_heartbeat.log task to restart the server status monitor. Stop_Monitors Start_Debugging %DBDIR%\tmp\GEM_Instrumentation_logs the directory for errors. Start_Monitors enterprise and site names. Thus the user must manually aggregate the icons by enterprise and site name. activity. Manually aggregate the icons or rerun the heartbeat when the system is not as busy so that automatic aggregation can take place. Ensure that the monitor has been enabled and has been distributed. Ensure that the event server is running. If you ran the 1. Run the 2. Look in the 2. The component information tasks timed-out due to high system Why is the icon color wrong? The icon color is updated when the server status monitor sends a TEC event. The monitor should always trigger an event for each of the four trigger conditions. What to do: ■ ■ ■ Why did the MSMQ server or MSSQLServer icon not aggregate? What to do: 1. If the MSMQ server is a router, then Tivoli Manager for Message Queue Server: User’s Guide Icon State Helpful Debugging Information

Helpful Debugging Information This section explains how to find log files for Manager for MQS. The Configure task writes output to a %TMP%\name.log file. %TMP% is the directory that is pointed to by the wtemp command. name represents a file name that is similar to the label of the task that produces the output. All other tasks and monitors will write output to separate log files if the Start_Debugging task has been run. For example: ■ The Display_Server_Status task writes output to the %TMP%\msmq_server_status.log file. ■ The Configure_Event_Server task writes output to the %TMP%\msmq_config_evtsvr.log file. ■ The Tivoli GEM instrumentation Query_State task places data on the MSMQ_java_querystate.log file that is located in the %TMP%\GEM_Instrumentation_Logs directory. See Start_Debugging and “Stop_Debugging” on page 5-8 for information on setting debug flags. Successful installation of Tivoli GEM instrumentation creates task libraries, monitor collections, and file packages. Installed instrumentation is stored in the %BINDIR%\..\generic_unix\TME\GEM\images\Microsoft\ MSMQ\V1_0_\Microsoft directory. The file packages must be distributed to Tivoli-managed nodes on which the MSMQ resources exist in order to have the instrumentation code available for local processing. The successful distribution of the file packages cause the instrumentation code to be installed in the %BINDIR%\..\generic_unix\TME\GEM\Microsoft\MSMQ\ V1_0_\ Microsoft directory.

F-14 Version 1.0 Finding and Correcting Problems F-15 TME directories. Do not and . Tivoli GEM Server Database Corruption . Number of applications Number of MSMQ servers Number of monitors running on the managed nodes where the MSMQ server resources reside Do not use intervals less than 5 minutes for a monitor in order to avoid an overload condition. For more information on adjusting the monitoring schedule of a profile, refer to the 10 Distributed Monitoring User's Guide %BINDIR%\TDS\server\db\backup\datab %BINDIR%\TDS\server\db\current\datab delete the directories. databases from the default databases to the current databases. This section contains important information about distribution, tasks, monitors, and the desktop. ■ ■ To avoid overloading event servers, use care when you adjust schedules for Tivoli GEM instrumentation monitors. Factors to consider include: ■ The Tivoli GEM databases are damaged or I want to refresh the Tivoli GEM console What to do: 1. Stop the Tivoli GEM 2.server. Erase all files in the current 3. Restart the Tivoli GEM server. This automatically copies the Tivoli Manager for Message Queue Server: User’s Guide Product Notes Scheduling Monitors Tivoli GEM Server Database Corruption Product Notes

Task Notes The following notes clarify the use of tasks with Manager for MQS: ■ When running the Configure task against more than one endpoint, the Execution Mode field must be set to serial. Execution mode is set on the Execute Task dialog. ■ If the Display_MSMQ_Info task ran successfully, but there was no data that met the criteria, an empty list will be displayed. ■ If the Configure_Event_Console task was not run against the event server, you will see the following error message: > /tmp/taskAAAa21183.BAT[3]: wlsassigneg: not found > + diagmsg Failed to assign MSMQ Event Group to... Rerun the task or job against the event server. ■ The Configure_Event_Server task always writes a log file named %TMP%\msmq_config_evtsvr.log, where %TMP% is the directory pointed to by the wtemp command. If any problems are encountered when running this task, review the log to help determine the problem. This task can be run more than once without having to restore the Tivoli database. Therefore, if you encounter a problem, rerun the task. If you specify a rule base name that exists, then it will be updated. If the Manager for MQS baroc files and rules have been loaded, the Configure_Event_Server task will delete and reload them to pick up any changes.

Monitor Notes When you enter arguments for monitors manually, it is important that you enter the arguments exactly. If a monitor fails because an argument is not valid, the only way to tell that it failed is by checking the monitor's debug log.

F-16 Version 1.0 Finding and Correcting Problems F-17 Product Notes must be followed . Revise the parm1 is specified, task. Look in logfile is specified. , with no intervening spaces. parm2 parm1 parm2 — the name of the monitor that you want to query. : Start_Debugging — case sensitive and must be enclosed in double-quotes if it — case sensitive. authorization on your monitor profile if you see the following message: On Windows NT, a problem can occur when the administrator does not have the authority to run the monitor. What to do Run the %DBDIR%\tmp\MSMQ-java_heartbeat.log The following sections describe limitations and workarounds that are associated with Tivoli GEM instrumentation. The appearance of the icons that are displayed within a Profile Manager is not updated. Tasks on menus that are accessed from subscriber icons will work, but icon appearance will remain the same as when the instance was added as a subscriber. This parameter is case sensitive and must be followed with a comma and a space when parm1 Several Tivoli GEM instrumentation tasks require a Monitor Name parameter. This parameter must be entered in the following format: MonitorName, parm1,parm2 where: MonitorName contains spaces. When by a comma and parm2 The APM_HEARTBEAT Event Is Not Generated Desktop Notes Tivoli GEM Instrumentation Monitor Notes Tivoli Manager for Message Queue Server: User’s Guide Workarounds Tivoli GEM Instrumentation Limitations, and Tivoli GEM Instrumentation Limitations, and Workarounds

get_oserv: insufficient authorization

1. From the TME 10 Distributed Monitoring Profile Properties window, select Edit. 2. Select Set User & Group ID. 3. Enter the user ID of the user who is running the monitor in the Remote user ID field. 4. Enter the domain name in the Remote group ID field. 5. Select Change & Close. 6. From the TME 10 Distributed Monitoring Profile Properties window, select Save. 7. Select Distribute to display the Distribute Profile dialog. 8. Select the All Levels of Subscribers button in the Distribute To: list. 9. Select the Make subscriber's profile an EXACT COPY of this profile button in the Distribute Will: list. 10. Select the versions of MSMQ servers you are NOT running in the Distribute To These Subscribers list. Click the right arrow button to move these MSMQ servers to the Don't Distribute To These Subscribers list. 11. Select Distribute & Close to redistribute the profile.

F-18 Version 1.0 Messages G-1 (ReturnCode) for host name. ?

Do not supply host name. Host name is obtained Seek your highest level of support. task produces return codes rather than textual mqtest.exe mqtest.exe

Started with Indicates a possible programming error. Discovery User Response: automatically. ABG10001E No queue registered messages. The return codes and their meanings are: 1.2. This node is not a New Technology (NT) machine. 3. Cannot find wntreg; SENTRY must be installed. 4. MSMQ not found. Environment that is not set up. ABG10000E Usage: mqtest Source: Cause: Source: Cause: User Response: Normal task output messages are not included here. See message catalogs for a complete listing of messages. The

Tivoli Manager for Message Queue Server: User’s Guide Appendix G. Messages ABG10002E Error starting receiver thread (ReturnCode) Source: mqtest.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10003E Cannot create queue (ReturnCode) Source: mqtest.exe Cause: MSMQ service or PEC is down. User Response: Start MSMQ service or check availability of PEC server.

ABG10004E Cannot retrieve format name (ReturnCode) Source: mqtest.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10005E Cannot open queue (ReturnCode) Source: mqtest.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10006E Receive message (ReturnCode) Source: mqtest.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

G-2 Version 1.0 Messages G-3 (ReturnCode) (ReturnCode) (ReturnCode) (ReturnCode) (ReturnCode) Seek your highest level of support. Seek your highest level of support. Seek your highest level of support. Seek your highest level of support. Seek your highest level of support. mqtest.exe mqtest.exe mqtest.exe mqtest.exe mqtest.exe Indicates a possible programming error. Indicates a possible programming error. Indicates a possible programming error. Indicates a possible programming error. Indicates a possible programming error. ABG10011E Send Message ABG10010E Format Name Source: Cause: User Response: ABG10009E Locate Next Source: Source: Cause: User Response: ABG10008E Locate Begin Source: Cause: User Response: Cause: User Response: Source: Cause: User Response: ABG10007E Cannot delete queue Tivoli Manager for Message Queue Server: User’s Guide ABG10020E Usage: mqdlq Source: mqdlq.exe Cause: Started with ? for host name. User Response: Do not supply host name. Host name is obtained automatically.

ABG10021E Cannot open queue (ReturnCode) Source: mqdlq.exe Cause: MSMQ service or PEC is down. User Response: Start MSMQ service or check availability of PEC server.

ABG10021E Cannot open queue (0XC00E0025) Source: mqdlq.exe Cause: The tasks do not have permissions to access the queue on the server. User Response: In order for tasks to work, the NT administrator and tmersvrd must have permissions to access the queue on the server. Use the MSMQ Explorer to give the NT administrator and tmersvrd read permissions. If the problem continues to occur and NT Server is not the Primary Domain Controller or Backup Domain Controller, you may need to provide the workstation administrator permissions to access the queue on the server.

ABG10022E Receive message (ReturnCode) Source: mqdlq.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

G-4 Version 1.0 Messages G-5 (ReturnCode) (ReturnCode) task. Supply valid parameters. Supply a valid instance name. See Seek your highest level of support. None Seek your highest level of support. perfc.exe perfc.exe mqdlq.exe mqdlq.exe mqdlq.exe OBJECTNAME and COUNTERNAME are required Instance name is required for certain performance counters. Indicates a possible programming error. No messages in Dead Letter queue to delete. Indicates a possible programming error. ABG10041E Error: instance name required for this counter Source: ABG10040E Usage: perfc Objectname Countername Source: Cause: parameters. User Response: Cause: User Response: Display_Instances ABG10025E Unable to get host properties Source: Cause: User Response: ABG10024I No more messages in Dead Letter queue Source: Cause: User Response: Source: Cause: User Response: ABG10023E Error: UuidToString failure Tivoli Manager for Message Queue Server: User’s Guide ABG10042E Error: Counter not available to be displayed Source: perfc.exe Cause: Some counters are defined but not available. User Response: Try another counter.

ABG10043E Error getting counter: check object, counter, or instance name Source: perfc.exe Cause: Parameters are not valid. User Response: Enter valid parameters. Note that parameters must be exact, and are both case- and space-sensitive.

ABG10044E Error returned from function Function — ReturnCode Source: perfc.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10050E Usage: perfn Objectname Source: perfn.exe Cause: OBJECTNAME is a required parameter. User Response: Supply a valid parameter.

ABG10054E Error returned from function Function — ReturnCode Source: perfc.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

G-6 Version 1.0 Messages G-7 (ReturnCode) (ReturnCode) (ReturnCode) FileName Seek your highest level of support. Supply valid file name. Supply valid service name. Supply valid file name. Enter valid parameters. Note that parameters must getcon.exe filever.exe getcon.exe filever.exe filever.exe Indicates a possible programming error. File name is not valid. Service name is not valid. File name is not valid. Parameters are not valid. Source: Cause: User Response: ABG10071E Error opening connection to the SCM Source: Cause: User Response: ABG10070E Usage: getcon servicename Source: Cause: User Response: ABG10062E Error querying file version ABG10061E Error opening file Source: Cause: User Response: ABG10060E Usage: filever Source: Cause: User Response: be exact, and are both case- and space-sensitive. Tivoli Manager for Message Queue Server: User’s Guide ABG10072E Service does not exist Source: getcon.exe Cause: Service name is not valid. User Response: Supply valid service name.

ABG10073E Error getting the service handle (ReturnCode) Source: getcon.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10074E Error querying the service status (ReturnCode) Source: getcon.exe Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG10080E Usage: showkey key path Source: showkey.exe Cause: KEY and PATH are required parameters. User Response: Supply valid parameters.

ABG10081E Unable to open subkey Source: showkey.exe Cause: Parameters are not valid. User Response: Supply valid parameters. Note that parameters must be exact, and are both case- and space-sensitive.

G-8 Version 1.0 Messages . G-9 D:/directory (ReturnCode) Supply valid parameters. Format is Check other messages. Seek your highest level of support. Seek your highest level of support. Only HKEY_LOCAL_MACHINE or drvsize.exe tasks showkey.exe showkey.exe showkey.exe Parameters are not valid. Explained in other messages. Showkey is not able to handle every type. Indicates a possible programming error. Parameters are not valid. ABG00102E Task failed Source: ABG10090E Error querying free disk space Source: Cause: User Response: Cause: User Response: ABG10084E Unable to close subkey Source: ABG10083E unknown type Source: Cause: User Response: Cause: User Response: ABG10082E invalid key Source: Cause: User Response: HKEY_CURRENT_USER are supported. Tivoli Manager for Message Queue Server: User’s Guide ABG00103I Task complete Source: tasks Cause: Informational User Response: None

ABG00104E Do not have access to needed utilities Source: tasks Cause: Possible installation error (files are removed). User Response: Check installation log files and restore files if needed.

ABG00105E Module for MSMQ must be installed in node Source: tasks Cause: Task run against managed code that does not have MSMQ installed. User Response: Install MSMQ.

ABG00106E Looking for utilities in directory: (Directory) Source: tasks Cause: Possible installation error (files are removed). User Response: Check installation log files and restore files if needed.

G-10 Version 1.0 Messages G-11 tasks tasks tasks tasks (ReturnCode) Stop_Services Stop_Services Stop_Services Stop_Services / / / / does not exist is stopped is already stopped Service Service Service None Rerun against valid endpoint. None Install MSMQ. Check for other messages. registry, task failed. tasks Informational Service does not exist on this endpoint. Informational Task run against managed node that does not have MSMQ Check for other messages. Cause: User Response: Source: Stop_Event_Adapter Source: Stop_Event_Adapter Source: Stop_Event_Adapter Cause: User Response: Cause: User Response: ABG00125I Service ABG00124I Service ABG00123E Service Source: Cause: installed. User Response: ABG00122E Error stopping service, ABG00108E Unable to retrieve MSMQ installation location from Source: Stop_Event_Adapter Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00126I Service Service is running, now stopping Source: Stop_Event_Adapter/Stop_Services tasks Cause: Informational User Response: None

ABG00127I Service Service status is Status; only RUNNING services may be stopped Source: Stop_Event_Adapter/Stop_Services tasks Cause: Informational User Response: None

ABG00128I No monitors currently distributed Source: Stop_Monitors/Start_Monitors tasks Cause: Informational User Response: None

ABG00129E Error stopping monitors, rc=ReturnCode Source: Stop_Monitors task Cause: Check log and return code. User Response: Correct problem and rerun.

ABG00130I Monitors stopped Source: Stop_Monitors task Cause: Informational User Response: None

G-12 Version 1.0 Messages G-13 command. tasks tasks ; only STOPPED net start Status (ReturnCode) Stop_Services Stop_Services task task / / status is is already running is stopped, now starting task Service Service Service None None None Correct problem and rerun. None services may be started Informational Informational Check log and return code from Informational Informational Source: Stop_Event_Adapter Source: Stop_Event_Adapter Cause: User Response: Cause: User Response: Source: Start_Event_Adapter Cause: Cause: User Response: ABG00135I Service ABG00134E Error starting service, Source: Start_Event_Adapter User Response: ABG00133I Service ABG00132I Service ABG00131I Debugging turned off Source: Stop_Monitors Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00136I Debugging turned on Source: Various tasks Cause: Informational User Response: None

ABG00137I Monitors started Source: Start_Monitors task Cause: Informational User Response: None

ABG00138E Error starting monitors, rc=ReturnCode Source: Start_Monitors task Cause: Check log and return code from wenblprb command. User Response: Correct problem and rerun.

ABG00139E Unable to retrieve event adapter installation location from registry Source: Configure_Event_Adapter task Cause: TEC NT adapter is not installed or registry error. User Response: Correct problem and rerun.

ABG00140E Cannot find tecad_nt.fmt Source: Configure_Event_Adapter task Cause: TEC NT adapter is not properly installed. User Response: Correct problem and rerun.

G-14 Version 1.0 Messages G-15 (ReturnCode) command. task task task task task nt_gencds FileName Seek your highest level of support. None None Seek your highest level of support. None Check return code from the Informational Informational Possible installation error with NT event adapter or the Informational User Response: ABG00145I Starting the adapter Source: Configure_Event_Adapter Source: Configure_Event_Adapter Cause: ABG00144I Stopping the adapter Source: Configure_Event_Adapter Cause: User Response: Cause: User Response: ABG00143E Error generating new tecad_nt.cds file: ABG00142I Removing: ABG00141E Cannot find nt_gencds.exe Source: Configure_Event_Adapter Source: Configure_Event_Adapter Cause: module. User Response: Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00146E Error starting the adapter (TECNTAdapter) Source: Configure_Event_Adapter task Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG00147I Log information written to FileName Source: Configure_Event_Adapter task Cause: Informational User Response: None

ABG00148I Locating files Source: Configure_Event_Adapter task Cause: Informational User Response: None

ABG00149I Generating new tecad_nt.cds file Source: Configure_Event_Adapter task Cause: Informational User Response: None

ABG00150I Configure EventConsole Complete! Source: Configure_Event_Console task Cause: Informational User Response: None

G-16 Version 1.0 Messages . . G-17 tasks tasks . are ... EventConsole EventConsole to FileName EventConsole to task task task EventGroupName already assigned to EventGroupName Check log for other messages. None None Run the task against the TEC server. None EventGroupName Ensure that task is run against the TEC Server. General failure. Informational Informational Task run against managed node that is not the TEC server Informational ABG00155I The last few lines of the log file Source: Configure_Event_Console ABG00154E Command Failed. Source: Configure_Event_Console/Configure_Event_Server Cause: User Response: Source: Configure_Event_Console/Configure_Event_Server Cause: User Response: ABG00153E Failed to assign Cause: User Response: ABG00152I Assigned ABG00151I Cause: User Response: Source: Configure_Event_Console Source: Configure_Event_Console Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00156I Rulebase rule base already exists, will update it. Clone rule base will be ignored. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00157I Rulebase rule base already exists, will update it. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00158I Clone rule base (Rulebase) exists! Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00159I Created Rulebase Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00160I Sentry classes already installed. Source: Configure_Event_Server task Cause: Informational User Response: None

G-18 Version 1.0 Messages G-19 . Rulebase rule base. Rulebase rule base to task task task task task to rule base. ClassFile Rulebase compiles successfully! CloneRulebase None None None None None Rulebase Informational Informational Informational Informational Informational Cause: User Response: Source: Configure_Event_Server ABG00166I Imported ABG00165I Copied ABG00164I Created Cause: User Response: ABG00162I Cause: User Response: ABG00161I Sentry classes have not been installed, adding them. Source: Configure_Event_Server Source: Configure_Event_Server Source: Configure_Event_Server Cause: User Response: Source: Configure_Event_Server Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00167I Stopped Event Server. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00168I Restarted Event Server. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00169I Configuring Event Server... Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00170I Rulefile is already in (Rulebase) rule base. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00171I Will delete and import it again to pick up any new rules. Source: Configure_Event_Server task Cause: Informational User Response: None

G-20 Version 1.0 Messages G-21 rule base. . task task task task task Rulebase event source. to rule base. event source already exists. Rulefile EventSource EventSource Rulebase None None None None None EventSource Informational Informational Informational Informational Informational Cause: User Response: Source: Configure_Event_Server Source: Configure_Event_Server Cause: User Response: ABG00176I Loaded Source: Configure_Event_Server ABG00175I Removed ABG00174I Cause: User Response: ABG00173I Created Cause: User Response: ABG00172I Imported Source: Configure_Event_Server Cause: User Response: Source: Configure_Event_Server Tivoli Manager for Message Queue Server: User’s Guide ABG00177I Copied rule callback script. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00178I Creating event group. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00179I The MSMQ Event Group created successfully. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00180I The MSMQ Event Group already exists. Source: Configure_Event_Server task Cause: Informational User Response: None

ABG00181E A rule base must be defined! Source: Configure_Event_Server task Cause: A rule base name was not entered in the Configure Event Server dialog. User Response: Rerun the task and supply a new or existing rule base name.

G-22 Version 1.0 Messages G-23 ) must already exist! task task task task Rulebase command. mkdir does not compile! Rerun the task and supply an existing rule base to Check for other diagnostic messages. Rerun the task and supply an existing rule base to Check the log for the rules that did not compile, Rulebase A new rule base was specified on the Configure Event Unable to issue The Rule Base to Clone entered on the Configure Event One or more rules in the rule base failed to compile. ABG00185E ABG00184E Cannot create new rule base path. Source: Configure_Event_Server Cause: Server dialog but no Rule Base to Clone was entered. User Response: clone or specify an existing rule base. ABG00183E Clone rule base ( Cause: User Response: ABG00182E Clone rule base must be defined! Source: Configure_Event_Server Source: Configure_Event_Server Cause: Server dialog does not exist. User Response: clone. Source: Configure_Event_Server Cause: User Response: correct the rules, and rerun the task. Tivoli Manager for Message Queue Server: User’s Guide ABG00186E Failed to create Rulebase rule base. Source: Configure_Event_Server task Cause: The wcrtrb command encountered a problem. User Response: Check the log for the error, correct it, and rerun the task.

ABG00187E Failed to copy CloneRulebase rule base to Rulebase. Source: Configure_Event_Server task Cause: The wcprb command encountered a problem. User Response: Check the log for the error, correct it, and rerun the task.

ABG00188E Failed to import Rulefile to Rulebase rule base. Source: Configure_Event_Server task Cause: The wimprbclass command encountered a problem. User Response: Check the log for the error, correct it, and rerun the task.

ABG00189E Failed to create EventSource event source. Source: Configure_Event_Server task Cause: The wcrtsrc command encountered a problem. User Response: Check the log for the error, correct it, and rerun the task.

G-24 Version 1.0 Messages G-25 event source. into Event Server task task task task EventSource Rulebase command encountered a problem. command encountered a problem. command encountered a problem. Check the log for the error, correct it, and rerun the Check for other diagnostic messages. Check the log for the error, correct it, and rerun the Check the log for the error, correct it, and rerun the wcrteg wdelsrc wloadrb The The The Possible installation problem. Cause: User Response: task. ABG00193E Failed to create event group. Source: Configure_Event_Server Source: Configure_Event_Server ABG00192E Failed to copy set icon script for msmq_monitors.rls Source: Configure_Event_Server Cause: ABG00191E Failed to load Cause: Cause: User Response: ABG00190E Failed to delete Source: Configure_Event_Server task. User Response: User Response: task. Tivoli Manager for Message Queue Server: User’s Guide ABG00194E Failed to add a filter to the event group. Source: Configure_Event_Server task Cause: The waddegflt command encountered a problem. User Response: Check the log for the error, correct it, and rerun the task.

ABG00195E Failed to restart Event Server. Please restart the event server from the desktop or command line. Source: Configure_Event_Server task Cause: The wstartesvr command encountered a problem. User Response: Restart the event server from the command line.

ABG00196E Failed to Stop Event Server. Event Server must be restarted before installation is complete! Source: Configure_Event_Server task Cause: The wstopesvr command encountered a problem. User Response: Stop (wstopesvr) and start (wstartesvr) the event server from the command line.

ABG00197E This host is not the TMR Event Server Source: Configure_Event_Server task Cause: The task was not run against the TMR event server. User Response: Rerun the task against the event server.

G-26 Version 1.0 Messages G-27 Directory (ReturnCode) already exists rule base directory: task Instance Rulebase task task task task command encountered a problem. None Seek your highest level of support. None None Check the log for the error, correct it, and rerun the wlsrb ManagedNode ManagedNode/Endpoint Informational Check return code. The Informational Informational Source: Configure User Response: ABG00202E Command wcrtmsmq/wcrtapx failed: User Response: ABG00201I Cannot create MSMQ instance for server name Cause: Cause: Source: Configure ABG00200I An MSMQ instance Cause: ABG00199I Cannot create MSMQ instance on Source: Configure User Response: Source: Configure User Response: ABG00198E error locating Cause: Cause: Source: Configure_Event_Server task. User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00203E Failed to subscribe ServerAlias to profile manager: ProfileManager. Source: Configure task Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG00204I Subscribed ServerAlias to profile manager: ProfileManager. Source: Configure task Cause: Informational User Response: None

ABG00205I Created MSMQ instance ServerAlias on ManagedNode/Endpoint. Source: Configure task Cause: Informational User Response: None

ABG00206E CDROM directory ((Directory)) invalid, MSMQ.IND not found Source: Install task Cause: Path name for CD-ROM location is not valid. User Response: Rerun with correct parameters.

G-28 Version 1.0 Messages G-29 because it already has ManagedNode not found ManagedNode ManagedNode FileName command Rerun with correct managed node name. Check other messages. Rerun with correct parameters. Check endpoint. None task task task task not defined module installed Attempt to create MSMQ instance on a manage node that is Explained by other messages. Path name or file name for input file is not valid. Endpoint not operational. Informational not running NT. User Response: Cause: Source: wcrtmsmq ABG00301E Create MSMQ method: managed node or endpoint Source: Install Cause: User Response: ABG00210I Not installing on ABG00209E Installation Failed on Source: Install Cause: User Response: ABG00208E Unable to contact ABG00207E Input file Source: Install Cause: User Response: Source: Install Cause: User Response: Tivoli Manager for Message Queue Server: User’s Guide ABG00302E Create MSMQ method: managed node or endpoint ManagedNode/Endpoint not found Source: wcrtmsmq command Cause: Attempt to create MSMQ instance on an unknown managed node. User Response: Rerun with correct managed node name.

ABG00303E Create MSMQ method: tmf_trans_begin failed Source: wcrtmsmq command Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

ABG00304E Create MSMQ method: MSMQ server name not defined Source: wcrtmsmq command Cause: No server name was provided. User Response: Rerun with correct parameters.

ABG00305E Create MSMQ method: tmf_trans_end failed Source: wcrtmsmq command Cause: Indicates a possible programming error. User Response: Seek your highest level of support.

G-30 Version 1.0 Messages G-31 . is already stopped. has been started. is already running. , is created by is not an NT-managed PolicyRegion MSMQServer MSMQServer MSMQServer MSMQServer ManagedNode command command command command command None None None None Rerun with correct managed node name. administrator in Policy Region node Attempt to start a server that is already running. Attempt to stop a server thats already stopped Informational Informational Attempt to create MSMQ instance on a manage node that is User Response: Source: wcrtmsmq User Response: User Response: Cause: Cause: Cause: Source: wcrtmsmq ABG00322I The MSMQ server Source: wcrtmsmq ABG00320E The MSMQ server ABG00318E The MSMQ server ABG00308I An MSMQ server, ABG00307E Managed node Source: wcrtmsmq User Response: Cause: Source: wcrtmsmq not running NT. User Response: Cause: Tivoli Manager for Message Queue Server: User’s Guide ABG00324I The MSMQ server MSMQServer has been stopped. Source: wcrtmsmq command Cause: Informational User Response: None

ABG00326E Unable to stop MSMQ server MSMQServer. Source: wcrtmsmq command Cause: Unknown; turn on debugging and check the log. User Response:

ABG00349E There is already a MSMQ instance on managed node ManagedNode. Source: wcrtmsmq command Cause: Attempt to create a 2nd MSMQ instance on a manage node. User Response: Rerun with correct managed node name.

ABG00359I The monitors for MSMQInstance have been started. Source: wcrtmsmq command Cause: Informational User Response: None

ABG00363E Unable to stop monitors for MSMQ server MSMQServer. Source: wcrtmsmq command Cause: Check notices for error messages. User Response: Correct the problem.

G-32 Version 1.0 Messages is G-33 PolicyRegion . MSMQServer is not a policy region. If . command command command command None Check the log. Correct the problem. Rerun with correct policy region name. PolicyRegion MSMQServer task for MSMQ server a policy region, it cannot be located. Please check the policy region name to ensure that it is spelled correctly. Informational Unknown; turn on debugging and rerun. Check notices for error messages Parameters are not valid. Source: wcrtmsmq User Response: Cause: Source: wcrtmsmq User Response: Cause: ABG00424E ABG00400I No monitors have been distributed to MSMQ server User Response: ABG00398E Error occurs while running Display_Server_Info ABG00395E Unable to stop Event Adapter for MSMQ server. Source: wcrtmsmq Cause: Source: wcrtmsmq User Response: Cause: Tivoli Manager for Message Queue Server: User’s Guide ABG00425I Usage wcrtmsg -a server_alias -p policy-region -h managed_node -e endpoint -v { 10 } Source: wcrtmsmq command Cause: Informational User Response: None

ABG00426E Create of MSMQ instance MSMQInstance has failed. Resource is not a managed resource of the policy region specified. Source: wcrtmsmq command Cause: Security error. User Response: Correct and rerun.

ABG00427E Create of MSMQ instance MSMQInstance has failed. Source: wcrtmsmq command Cause: Unable to create MSMQ instance. User Response: See other messages.

G-34 Version 1.0 Glossary

administrator. See Tivoli administrator. authentication. (1) In computer security, verification of the identity of a user or the user’s eligibility to access an object. (2) In computer security, verification that a message has not been altered or corrupted. (3) In computer security, a process used to verify the user of an information system or protected resources. B

Basic Recorder of Objects in C (BAROC). In the event server of the Tivoli Enterprise Console (TEC), the internal representation of the defined event classes. business description file (BDF). In a Tivoli environment, a generic name for any of these application description files: business system description file (BSDF), business system component description file (BCDF), and business system mapping description file (BMDF), and business subsystem description file (BSSDF).

Tivoli Manager for Message Queue Server: User’s Guide X-1 C

client. A computer system or process that requests a service of another computer system or process that is typically referred to as a server. Multiple clients may share access to a common server. component description file (CDF). In the context of the Application Management Specification (AMS), an application description file that contains information about a specific component in a management-ready application. Each management-ready application can contain multiple components, each of which is represented by one component description file. D

daemon. A program that runs unattended to perform a standard service. Some daemons are triggered automatically to perform their task; others operate periodically. E

endpoint. (1) In a Tivoli environment, a Tivoli client that is the ultimate recipient for any type of Tivoli operation. (2) In a Tivoli environment, a Tivoli service that runs on multiple operating systems and performs Tivoli operations on those systems, thereby enabling the Tivoli Management Framework to manage the systems as Tivoli clients. event. In a Tivoli environment, any significant change in the state of a system resource, network resource, or network application. An event can be generated for a problem, for the resolution of a problem, or for the successful completion of a task. Examples of events are: the normal starting and stopping of a process, the abnormal termination of a process, and the malfunctioning of a server. event adapter. In a Tivoli environment, software that converts events into a format that the Tivoli Enterprise Console can use and forwards the events to the event server. Using the Tivoli EIF, an organization can develop its own event adapters, tailored to its network environment and specific needs. event class. In the Tivoli Enterprise Console, a classification for an event that indicates the type of information that the event adapter will send to the event server.

X-2 Version 1.0 event console. In the Tivoli Enterprise Console, a graphical user interface (GUI) that enables system administrators to view and respond to dispatched events from the event server. event group. In the Tivoli Enterprise Console, a set of events that meet certain criteria. Each event group is represented by an icon on the event console. Tivoli administrators can monitor event groups that are relevant to their specific areas of responsibility. H

host. In a Tivoli environment, a computer that serves as a managed node for a profile distribution. I

instrumentation. In application or system software, either (a) monitoring functions that provide performance and other information to a management system or, (b) the use of monitoring functions to provide performance and other information to a management system. J

job. (1) In a Tivoli environment, a resource consisting of a task and its preconfigured execution parameters. Among other things, the execution parameters specify the set of hosts on which the job is to execute. (2) A unit of work defined by a user that is to be accomplished by a computer. Loosely, the term job is sometimes used to refer to a representation of a job. This representation may include a set of computer programs, files, and control statements to the operating system. M

managed node. (1) In a Tivoli environment, any managed resource on which the Tivoli Management Framework is installed. (2) In Internet communications, a workstation, server, or router that contains a network management agent. In the Internet Protocol (IP), the managed node usually contains a Simple Network Management Protocol (SNMP) agent.

Tivoli Manager for Message Queue Server: User’s Guide X-3 monitor. (1) A device that observes and records selected activities within a data processing system for analysis. Possible uses are to indicate significant departure from the norm, or to determine levels of utilization of particular functional units. (2) Software or hardware that observes, supervises, controls, or verifies operations of a system. P

policy region. (1) In a Tivoli environment, a group of managed resources that share one or more common policies. Tivoli administrators use policy regions to model the management and organizational structure of a network computing environment. The administrators can group similar resources, define access to and control the resources, and associate rules for governing the resources. The policy region contains resource types and the list of resources to be managed. A policy region is represented on the desktop by an icon that resembles a capitol building (dome icon). (2) When a Tivoli Management Region (TMR) is created, a policy region with the same name is also created. In this case, the TMR has only one policy region. However, in most cases, a Tivoli administrator creates other policy regions and subregions to represent the organization of the TMR. A TMR addresses the physical connectivity of resources whereas a policy region addresses the logical organization of resources. profile. (1) Data that describes the significant characteristics of a user, a group of users, or one or more computer resources. (2) In a Tivoli environment, a container for application-specific information about a particular type of resource. A Tivoli application specifies the template for its profiles; the template includes information about the resources that can be managed by that Tivoli application. A profile is created in the context of a profile manager; the profile manager links a profile to the Tivoli resource (for example, a managed node) that uses the information contained in the profile. A profile does not have any direct subscribers. profile manager. In a Tivoli environment, a container for profiles that links the profiles to a set of resources, called "subscribers." A profile manager can contain (a) profiles of multiple types or (b) multiple profiles of the same type. Tivoli administrators use profile managers to organize and distribute profiles. A profile manager is created in the context of a policy region and is a managed resource in a policy region. See also subscription list.

X-4 Version 1.0 R

rule. In the Tivoli Enterprise Console (TEC), a set of one or more logical statements that enable the event server to recognize relationships among events (event correlation) and to execute automated responses accordingly. rule base. In the Tivoli Enterprise Console (TEC), a set of rules and the event class definitions for which the rules are written. The TEC uses the rule base in managing events. An organization can create many rule bases, with each rule base fulfilling a different set of needs for network computing management. S

service. A Windows NT program that provides a specific function to applications. Services typically run in the background, without a user interface. subscription list. In a Tivoli environment, a list that identifies the subscribers to a profile manager. Including a profile manager on a subscription list (in effect, a list within a list) is a way of subscribing several resources simultaneously rather than adding each one individually. In Tivoli Plus modules, a profile manager functions as a subscription list. T

task. In a Tivoli environment, the definition of an action that must be routinely performed on various managed nodes throughout the network. A task defines the executables to be run when the task is executed, the authorization role required to execute the task, and the user or group name under which the task will execute. threshold. In software products, a value that defines a limit for a monitored condition. The monitored condition, the significance of the limit, and the particular software product’s response when the monitored condition reaches the specified threshold vary widely according to product. Tivoli administrator. In a Tivoli environment, a system administrator who has been authorized to perform systems management tasks and manage policy regions in one or more networks. Each Tivoli administrator is represented by an icon on the desktop.

Tivoli Manager for Message Queue Server: User’s Guide X-5 Tivoli desktop. In a Tivoli environment, the desktop that system administrators use to manage their network computing environment. Tivoli Distributed Monitoring. A Tivoli product that monitors system resources, initiates any necessary corrective actions, and informs system administrators of potential problems. Tivoli Distributed Monitoring consists of a group of monitors that are installed on each managed node that is to be monitored. It resolves some events on its own and may send others to the Tivoli Enterprise Console. Tivoli Enterprise Console (TEC). A Tivoli product that collects, processes, and automatically initiates corrective actions for system, application, network, and database events; it is the central control point for events from all sources. The Tivoli Enterprise Console provides a centralized, global view of the network computing environment; it uses distributed event monitors to collect information, a central event server to process information, and distributed event consoles to present information to system administrators. Tivoli environment. Pertaining to the suite of Tivoli applications that enable system administrators to manage their network computing enterprise according to the disciplines of availability management, deployment management, operations and administration, and security management. Tivoli Global Enterprise Manager (Tivoli GEM). A Tivoli product that allows system administrators to graphically monitor, control, and configure applications residing in distributed and host (S/390) environments and to use the concept of business systems management to organize related components, thereby providing a business perspective for management decisions. Tivoli GEM gives information technology staff a logical view of the computing environment; this view shows, at a glance, the status of the multiple applications that comprise the enterprise's business system, including application components, the relationships among and between components, and the flow of data between the applications. By providing this view from a business perspective, Tivoli GEM enables system administrators to quickly make determinations about the business impact of any component failure. Addressing technology problems from the business perspective greatly improves the effectiveness of system administrators and provides a higher level of service to users. Tivoli Management Agent (TMA). In the Tivoli environment, an agent that securely performs administrative operations. Tivoli Management Region (TMR). In a Tivoli environment, a TMR server and the set of clients that it serves. An organization can have more

X-6 Version 1.0 than one TMR. A TMR addresses the physical connectivity of resources whereas a policy region addresses the logical organization of resources. Tivoli GEM console. In the Tivoli Global Enterprise Manager and Tivoli NetView for OS/390, a Java-based graphical user interface that displays business system information from the Tivoli GEM server. The Tivoli GEM console displays each component as a separate icon or shape and draws lines between icons to denote links. It then uses color to indicate the status of each component and of the business system as a whole. As the Tivoli GEM server receives configuration and status updates for the business system, it updates the Tivoli GEM console. Therefore, the Tivoli GEM console always displays the real-time configuration and status of the business system. Tivoli GEM server. In Tivoli Global Enterprise Manager and Tivoli NetView for OS/390, a server that interacts with instrumented applications in a business system and provides information for display on the Tivoli GEM console. The Tivoli GEM server receives heartbeat events from instrumented applications or components and determines the business system in which a component belongs. The Tivoli GEM server also queries instrumented applications for related applications and for the status of its monitors. All of this information is used to create and maintain a view of each business system's configuration and availability on the Tivoli GEM console.

Tivoli Manager for Message Queue Server: User’s Guide X-7 X-8 Version 1.0 Index

A C admintool command 7-11 client, Tivoli GEM, hints for aggregate resources using F-10 navigating to specific resources 9-4 commands viewed on Tivoli GEM console 9-4 admintool 7-11 Application Proxy wcrtmsmq A-1 definition 2-6 wgetmsmq A-2 installation 2-8 winstall 2-12 attributes, MSMQ server wlscurrb F-6, F-8, F-11 displaying, wgetmsmq wlsrbclass F-6, F-8, F-11 command A-2 wlsrbrules F-7, F-9, F-12 updating, wsetmsmq command A-3 wsetmsmq A-3 authorization roles wtdumprl F-7, F-8, F-9, F-12 assigning wtemp F-2, F-14, F-16 for Manager for MQS 3-2 component description files for Tivoli GEM contents C-2 instrumentation 7-7 installing C-1 description 1-3 components, installed, location of Manager for MQS 2-6 Tivoli GEM instrumentation 7-8 B Configure task 5-7 business description files Configure_Event_Adapter task 6-5 contents C-2 Configure_Event_Console task 6-4 installing C-1 Configure_Event_Server task 6-2 business system description C-1

Tivoli Manager for Message Queue Server: User’s Guide X-9 configuring Display_Instances task 5-5, 9-2 event console 6-4 Display_MSMQ_Info task 5-5, 9-2 event server 2-6, 6-2 Display_Server_Info task 5-5, 9-2 NT event adapter 6-5 Display_Server_Status task 5-5, 9-2 configuring Manager for MQS Display_Site task 9-2, 9-3 authorization roles 3-2 distributed monitoring 1-3, 1-4 overview 3-1 Distributed Transaction Coordinator confirming server discovery on Tivoli Status monitor 4-7 GEM console 8-5 distributing the heartbeat monitor 8-2 console 1-3 TEC 1-4 Tivoli GEM 7-3 E event creating adapter, NT MSMQ server instance configuring 6-5 from desktop 3-5 requirements 2-5 wcrtmsmq command A-1 starting and stopping 6-6 classes D distributed monitoring B-1 data flow 2-2 MSMQ_Event B-2 database MSMQ_Monitors B-1 backup 7-14 NT event adapter B-2 corrupted, remedy F-15 console, configuring 6-4 debugging filtering 1-2, 6-7 helpful information F-14 flow 2-2 log files, location of F-14 management deleting an MSMQ server 3-10 adapter, configuring 6-5 determining server status 3-10 adapter, NT, starting and dialogs stopping 6-6 install product 2-7 authorization required 6-1 Discover task 2-13 console, configuring 6-4 Discover_Connections task 9-2 overview 6-1 discovery, server, on Tivoli GEM monitoring 6-6 console 8-5 rules B-5 Disk Usage by MSMQ Server Event Adapter Status monitor 4-7 monitor 4-7 event server Display_Enterprise task 9-2, 9-3 configuring 2-6, 6-2 hints for using F-8

X-10 Version 1.0 executing tasks Manager for MQS 5-2 H Tivoli GEM instrumentation 9-1, Heartbeat monitor 9-7 description, MSMQ server 9-9 description, MSSQLServer 9-10 distributing 8-2 F subscribing 8-2 FalconMQ Server Status monitor 4-7 features, product distributed monitoring 1-3, 1-4 I event display, consolidated 1-4 icon color F-13 event filtering 1-2 icon files integration with Tivoli Management contents C-2 Framework 1-3 installing C-1 authorization 1-3 Install task 2-14 monitoring, distributed 1-3, 1-4 installation task libraries 1-3 hints F-1 TEC 1-3, 1-4 options 2-6 field descriptions, tasks D-1 installing filtering events 1-2, 6-7 available clients 2-8, 2-11, 7-13 forwarding events to event server 2-6 Manager for MQS Free Disk Space Available monitor 4-7 administrator authorization 1-3 checklist 2-6 components, location of 2-6 G NT event adapter Generic Performance monitor 4-7 requirements 2-5 getting started procedure 2-10 with Manager for MQS Tivoli GEM instrumentation authorization roles, assigning 3-2 administrator authorization 7-7 configuring, overview 3-1 components, location of 7-8 instances, MSMQ 3-4 management regions 7-7 MSMQ server, creating 3-5 procedure 7-12 MSMQ server, deleting 3-10 instances, MSMQ 3-4 MSMQ server, managing 3-3 integration with Tivoli Management server status, determining 3-10 Framework with Tivoli GEM instrumentation event display 1-4 heartbeat monitor, subscribing and TEC 1-4 distributing 8-2 interconnected TMRs 2-5 resource discovery, confirming 8-5

Tivoli Manager for Message Queue Server: User’s Guide X-11 monitors (continued) J log files, location of F-14 Java Development Kit 7-9 MSMQ server Disk Usage by MSMQ L Server 4-7 libraries, task 1-3 Distributed Transaction List_Dead_LetterQ task 5-6, 9-2 Coordinator Status 4-7 listing tasks Event Adapter Status 4-7 Manager for MQS 5-2 FalconMQ Server Status 4-7 Tivoli GEM instrumentation 9-1 Free Disk Space Available 4-7 location of installed components Generic Performance 4-7 Manager for MQS 2-6 MQ Test 4-7 Tivoli GEM instrumentation 7-8 Mqsvc 4-6 log files, location of F-14 Msdtc 4-6 MSMQ IS 4-5 MSMQ Queue 4-5 M MSMQ Server Status 4-7 management MSMQ Service 4-6 regions, requirements 2-5 MSMQ Session 4-6 tasks Q2qgw 4-6 authorization required, Manager Special Queue Count 4-7 for MQS 5-4 Special Queue Maximum authorization required, Tivoli Time 4-7 GEM instrumentation 7-7 performance 4-5 listing 5-2 queue 4-7 log files, location of F-14 Tivoli GEM instrumentation (MSMQ overview 5-1 server) running 5-2, 9-1 Heartbeat 9-9 running from the desktop, hints for using F-5 hints F-3 Manager for MQS-supported 9-9 running from the Tivoli GEM scheduling F-15 console, hints F-4 State 9-9 monitoring, distributed 1-3, 1-4 thresholding 9-10 monitors Tivoli GEM instrumentation hints for using F-5 (MSSQLServer) listing Heartbeat 9-10 Manager for MQS 4-1 State 9-10 Tivoli GEM instrumentation 9-11

X-12 Version 1.0 MQ Test monitor 4-7 NT event adapter (continued) Mqsvc monitor 4-6 requirements 2-5 Msdtc monitor 4-6 starting and stopping 6-6 MSMQ instances 3-4 MSMQ IS monitor 4-5 MSMQ monitor tasks P performance counters 4-7 Purge_Dead_LetterQ 4-9 performance monitors Restart_Services 4-10 description 4-5 MSMQ Queue monitor 4-5 listing 4-1 MSMQ server planning for installation attributes event server 2-6 displaying, wgetmsmq overview 2-1 command A-2 management regions 2-5 updating, wsetmsmq NT event adapter 2-5 command A-3 TMR 2-5 creating product features from desktop 3-5 distributed monitoring 1-3, 1-4 wcrtmsmq command A-1 event display, consolidated 1-3, 1-4 deleting 3-10 event filtering 1-2 endpoints, MSMQ 3-4 integration with Tivoli Management icon pull-down tasks 3-8 Framework 1-3 instances, creating 3-5 authorization 1-3 managing 3-3 monitoring, distributed 1-3, 1-4 profile managers 3-11 task libraries 1-3 status, determining 3-10 TEC 1-3, 1-4 MSMQ Server Status monitor 4-7 profile managers, subscriber list 3-11 MSMQ Service monitor 4-6 Purge_Dead_LetterQ task 5-6, 9-2 MSMQ Session monitor 4-6 msmq_admin TMR role 1-3, 3-2 MSMQ_Event event class B-2 Q MSMQ_Monitors event class B-1 Q2qgw monitor 4-6 msmq_senior TMR role 1-3, 3-2 Query_State task 9-2, 9-3 multiple TMRs 2-5 Query_Threshold_Settings task 9-2, 9-3 N Query_Thresholds task 9-2, 9-3 Query_Values task 9-2, 9-3 NT event adapter configuring 6-5 Event Adapter Status monitor 4-7

Tivoli Manager for Message Queue Server: User’s Guide X-13 server, MSMQ (continued) R monitors requirements listing 4-1 administrator authorization performance 4-5 Manager for MQS 1-3 performance counters 4-7 Tivoli GEM instrumentation 7-7 profile manager 3-11 management regions 2-5 status, determining 3-10 NT event adapter 2-5 subscribing to a profile resource discovery on Tivoli GEM manager 3-11 console 8-5 server, MSSQLServer 7-4, 7-7, 7-14, resource roles 3-3 8-3, 8-5, 9-1, 9-2, 9-4 rules, event monitors 9-9 heartbeat monitor, subscribing and tasks 9-3 distributing 8-2 server, Tivoli GEM 7-2 Manager for MQS B-5 server, TMR 2-2 resource discovery, confirming 8-5 Set_Polling_Interval task 9-2, 9-3 running tasks Set_Pulse task 9-2, 9-3 Manager for MQS 5-2 Set_Thresholds task 9-2, 9-3 running from Tivoli GEM console, Special Queue Count monitor 4-7 recommended 9-1 Special Queue Maximum Time Tivoli GEM instrumentation 9-7 monitor 4-7 Start task 9-1, 9-3 S Start_Debugging task 5-8, 9-2 scheduling Tivoli GEM instrumentation Start_Event_Adapter task 6-6 monitors F-15 Start_Monitors task 5-9, 9-2 server, MSMQ Start_Services task 5-6, 9-2 attributes State monitor (MSMQ server) 9-9 displaying, wgetmsmq State monitor (MSSQLServer) 9-10 command A-2 Stop task 9-1, 9-3 updating, wsetmsmq Stop_Debugging task 5-8, 9-2 command A-3 Stop_Event_Adapter task 6-6 creating Stop_Monitors task 5-9, 9-2 from desktop 3-5 Stop_Services task 5-6, 9-2 wcrtmsmq command A-1 subscribing the heartbeat monitor 8-2 deleting 3-10 endpoints, MSMQ 3-4 T icon pull-down tasks 3-8 managing 3-3

X-14 Version 1.0 task libraries 1-3 tasks (continued) tasks Tivoli GEM instrumentation (MSMQ field descriptions D-1 server component) (continued) hints Display_Enterprise 9-2 running from the desktop F-3 Display_Instances 9-2 running from the Tivoli GEM Display_MSMQ_Info 9-2 console F-4 Display_Server_Info 9-2 listing 5-2 Display_Server_Status 9-2 log files, location of F-14 Display_Site 9-2 MSMQ server field descriptions D-1 authorization required 5-4 List_Dead_LetterQ 9-2 Display_Instances 5-5 Purge_Dead_LetterQ 9-2 Display_MSMQ_Info 5-5 Query_State 9-1, 9-2 Display_Server_Info 5-5 Query_Thresholds 9-1, 9-2 Display_Server_Status 5-5 Query_Values 9-1, 9-2 List_Dead_LetterQ 5-6 running 9-1, 9-7 Purge_Dead_LetterQ 5-6 Set_Polling_Interval 9-1, 9-2 Start_Services 5-6 Set_Pulse 9-2 Stop_Services 5-6 Set_Thresholds 9-1, 9-2 MSMQ TEC Start_Debugging 9-2 Configure_Event_Adapter 6-5 Start_Monitors 9-2 Configure_Event_Console 6-4 Start_Services 9-1, 9-2 Configure_Event_Server 6-2 Stop_Debugging 9-2 Start_Event_Adapter 6-6 Stop_Monitors 9-2 Stop_Event_Adapter 6-6 Stop_Services 9-1, 9-2 MSMQ utility Tivoli GEM instrumentation authorization required 5-7 (MSSQLServer component) Configure 5-7 Display_Enterprise 9-3 Discover 2-13 Display_Site 9-3 Install 2-14 Query_State 9-3 Start_Debugging 5-8 Query_Threshold_Settings 9-3 Start_Monitors 5-9 Query_Thresholds 9-3 Stop_Debugging 5-8 Query_Values 9-3 Stop_Monitors 5-9 Set_Polling_Interval 9-3 overview 5-1 Set_Pulse 9-3 running 5-2 Set_Thresholds 9-3 Tivoli GEM instrumentation (MSMQ Start 9-3 server component) Stop 9-3 Discover_Connections 9-2

Tivoli Manager for Message Queue Server: User’s Guide X-15 tear-away log 9-7 TMR (continued) TEC console 1-3, 1-4 server 2-2 Tivoli troubleshooting authorization 1-3 debugging information F-14 distributed monitoring 1-3, 1-4 hints enterprise console 1-3, 1-4 icon color F-13 framework, integration with installation F-1 authorization 1-3 monitors, using F-5 event display 1-3, 1-4 tasks and jobs, running from the overview 1-3 desktop F-3 TEC 1-3, 1-4 tasks and jobs, running from the Tivoli GEM console 7-3 Tivoli GEM console F-4 Tivoli GEM hints for using F-10 TEC, using F-8 Tivoli GEM instrumentation Tivoli GEM client, using F-10 event handling 7-3 log files F-14 initializing 8-1 installing authorization required 7-7 W wcrtmsmq command A-1 components 7-8 wgetmsmq command A-2 Java Development Kit 7-9 winstall command 2-12 overview 7-1 wlscurrb command F-6, F-8, F-11 procedure 7-12 wlsrbclass command F-6, F-8, F-11 instrumented components 7-4 wlsrbrules command F-7, F-9, F-12 management regions 7-7 wpostemsg F-2 monitors wsetmsmq command A-3 hints for using F-5 wtdumprl command F-7, F-8, F-9, scheduling F-15 F-12 supported Manager for MQS 9-9 wtemp command F-2, F-14, F-16 tasks field descriptions D-1 locating 9-1 running 9-1, 9-7 Tivoli GEM server 7-2 TMR multiple 2-5 requirements 2-5 roles msmq_admin 1-3, 3-2 msmq_senior 1-3, 3-2

X-16 Version 1.0

GC32-0313-00

/XRL/1

Table Definitions id File Page References

WQ9 QMM10UGP SCRIPT iii iii WQ10 QMM10UGP SCRIPT iii iii WQ11 QMM10UGP SCRIPT iii iii WQ12 QMM10UGP SCRIPT iii iii WQ13 QMM10UGP SCRIPT iii iii WQ14 QMM10UGP SCRIPT iii iii WQ15 QMM10UGP SCRIPT iii iii WQ16 QMM10UGP SCRIPT iii iii WQ17 QMM10UGP SCRIPT iii iii WQ18 QMM10UGP SCRIPT iii iii WQ19 QMM10UGP SCRIPT iii iii WQ20 QMM10UGP SCRIPT iii iv WQ24 QMM10UGP SCRIPT 2-6 2-7 WQ25 QMM10UGP SCRIPT 2-6 2-7 WQ26 QMM10UGP SCRIPT 2-6 2-7 WQ27 QMM10UGP SCRIPT 2-6 2-7 WQ36 QMM10UGP SCRIPT 3-10 3-10 WQ37 QMM10UGP SCRIPT 3-10 3-10 WQ38 QMM10UGP SCRIPT 3-10 3-10 WQ39 QMM10UGP SCRIPT 3-10 3-10 WQ45 QMM10UGP SCRIPT 5-4 5-5 WQ46 QMM10UGP SCRIPT 5-4 5-5 WQ47 QMM10UGP SCRIPT 5-4 5-5 WQ49 QMM10UGP SCRIPT 5-7 5-7 WQ50 QMM10UGP SCRIPT 5-7 5-7 WQ51 QMM10UGP SCRIPT 5-7 5-7 WQ52 QMM10UGP SCRIPT 5-7 5-7 WQ53 QMM10UGP SCRIPT 5-7 5-7 WQ54 QMM10UGP SCRIPT

/XRL/2

5-7 5-7 WQ55 QMM10UGP SCRIPT 5-7 5-7 WQ56 QMM10UGP SCRIPT 5-7 5-7 WQ63 QMM10UGP SCRIPT 6-1 6-1 WQ64 QMM10UGP SCRIPT 6-1 6-1 WQ65 QMM10UGP SCRIPT 6-1 6-1 WQ66 QMM10UGP SCRIPT 6-1 6-1 WQ67 QMM10UGP SCRIPT 6-1 6-1 WQ68 QMM10UGP SCRIPT 6-1 6-1 WQ75 QMM10UGP SCRIPT 7-5 7-6 WQ76 QMM10UGP SCRIPT 7-8 7-9 WQ77 QMM10UGP SCRIPT 7-8 7-9 WQ78 QMM10UGP SCRIPT 7-8 7-9 WQ79 QMM10UGP SCRIPT 7-8 7-9 WQ80 QMM10UGP SCRIPT 7-8 7-9 WQ81 QMM10UGP SCRIPT 7-8 7-9 WQ82 QMM10UGP SCRIPT 7-8 7-9 WQ85 QMM10UGP SCRIPT 8-2 8-2 WQ86 QMM10UGP SCRIPT 8-2 8-2 WQ87 QMM10UGP SCRIPT 8-3 8-3 WQ90 QMM10UGP SCRIPT A-1 A-1 WQ91 QMM10UGP SCRIPT A-1 A-1 WQ92 QMM10UGP SCRIPT A-1 A-1 WQ93 QMM10UGP SCRIPT A-1 A-1 WQ95 QMM10UGP SCRIPT B-1 B-2 WQ96 QMM10UGP SCRIPT B-1 B-2 WQ97 QMM10UGP SCRIPT B-1 B-2 WQ98 QMM10UGP SCRIPT B-1 B-2 WQ99 QMM10UGP SCRIPT B-1 B-2 WQ100 QMM10UGP SCRIPT B-1 B-2 WQ101 QMM10UGP SCRIPT B-1 B-2 WQ102 QMM10UGP SCRIPT

/XRL/3

B-1 B-2 WQ103 QMM10UGP SCRIPT B-1 B-2 WQ104 QMM10UGP SCRIPT B-1 B-2 WQ105 QMM10UGP SCRIPT B-1 B-2 WQ106 QMM10UGP SCRIPT B-1 B-2 WQ107 QMM10UGP SCRIPT B-1 B-2 WQ108 QMM10UGP SCRIPT B-1 B-2 WQ109 QMM10UGP SCRIPT B-1 B-2 WQ110 QMM10UGP SCRIPT B-2 B-3 WQ111 QMM10UGP SCRIPT B-2 B-3 WQ112 QMM10UGP SCRIPT B-2 B-3 WQ113 QMM10UGP SCRIPT B-2 B-3 WQ114 QMM10UGP SCRIPT B-2 B-3 WQ115 QMM10UGP SCRIPT B-2 B-3 WQ116 QMM10UGP SCRIPT B-2 B-3 WQ117 QMM10UGP SCRIPT B-2 B-3 WQ118 QMM10UGP SCRIPT B-2 B-3 WQ119 QMM10UGP SCRIPT B-2 B-3 WQ120 QMM10UGP SCRIPT B-2 B-3 WQ121 QMM10UGP SCRIPT B-2 B-3 WQ124 QMM10UGP SCRIPT D-1 D-1 WQ125 QMM10UGP SCRIPT D-1 D-1 WQ126 QMM10UGP SCRIPT D-1 D-1 WQ127 QMM10UGP SCRIPT D-1 D-2 WQ128 QMM10UGP SCRIPT D-1 D-2 WQ129 QMM10UGP SCRIPT D-1 D-2 WQ130 QMM10UGP SCRIPT D-1 D-3 WQ131 QMM10UGP SCRIPT D-1 D-4 WQ132 QMM10UGP SCRIPT D-1 D-4 WQ133 QMM10UGP SCRIPT D-1 D-4 WQ134 QMM10UGP SCRIPT D-1 D-4 WQ135 QMM10UGP SCRIPT

/XRL/4

D-1 D-4 WQ136 QMM10UGP SCRIPT D-1 D-5 WQ137 QMM10UGP SCRIPT D-1 D-5 WQ138 QMM10UGP SCRIPT E-1 E-1

Headings id File Page References

WQ21 QMM10UGP SCRIPT 1-1 Chapter 1, Introducing Manager for Message Queue Server xii WQ22 QMM10UGP SCRIPT 2-1 Chapter 2, Planning for and Installing Manager for Message Queue Server xii, 7-8 NTEAREQ QMM10UGP SCRIPT 2-5 NT Event Adapter Requirements 1-1, 2-1 TMRS QMM10UGP SCRIPT 2-5 Configuring Tivoli Management Regions 2-2 WQ23 QMM10UGP SCRIPT 2-6 Installation Overview APPROX QMM10UGP SCRIPT 2-8 Installing the Application Proxy 2-6 DESKINS QMM10UGP SCRIPT 2-10 From the Desktop 2-6 WINST QMM10UGP SCRIPT 2-12 Using the winstall Command 2-6 INSPROD QMM10UGP SCRIPT 2-13 Using the Discover and Install Tasks 2-6 WQ28 QMM10UGP SCRIPT 2-13 Discover Task 5-7 WQ29 QMM10UGP SCRIPT 2-14 Install Task 2-9, 5-7 WQ30 QMM10UGP SCRIPT 3-1 Chapter 3, Getting Started with Manager for Message Queue Server xii WQ31 QMM10UGP SCRIPT 3-2 Assigning Authorization Roles 1-3, 3-1, F-4 WQ32 QMM10UGP SCRIPT 3-3 Managing Microsoft Message Queue Servers 3-1 WQ33 QMM10UGP SCRIPT 3-4 MSMQ Server Instances 3-7, 3-11, 5-2 WQ34 QMM10UGP SCRIPT 3-5 Creating MSMQ Server Instances

/XRL/5

3-3, 3-4, 5-8 WQ35 QMM10UGP SCRIPT 3-8 MSMQ Server Icon Tasks 5-1 WQ40 QMM10UGP SCRIPT 3-11 MSMQ Server Lists 3-4 WQ41 QMM10UGP SCRIPT 4-1 Chapter 4, Monitoring Microsoft Message Queue Servers xii, 3-4, 9-8 WQ42 QMM10UGP SCRIPT 4-5 Understanding the Monitors 9-9 WQ43 QMM10UGP SCRIPT 5-1 Chapter 5, Tasks to Manage Microsoft Message Queue Resources xii, 3-4, 9-3 WQ44 QMM10UGP SCRIPT 5-4 MSMQ Server Tasks 3-9, 3-9, 5-1 WQ48 QMM10UGP SCRIPT 5-7 MSMQ Utility Tasks 5-1 WQ57 QMM10UGP SCRIPT 5-7 Configure 2-14, 3-5 WQ58 QMM10UGP SCRIPT 5-8 Start_Debugging F-14 WQ59 QMM10UGP SCRIPT 5-8 Stop_Debugging F-14 WQ60 QMM10UGP SCRIPT 5-9 Start_Monitors WQ61 QMM10UGP SCRIPT 5-9 Stop_Monitors WQ62 QMM10UGP SCRIPT 6-1 Chapter 6, Managing Microsoft Message Queue Events xiii, 2-5, 5-1 WQ69 QMM10UGP SCRIPT 6-2 Configuring the Event Server 2-6, 3-1 WQ70 QMM10UGP SCRIPT 6-4 Configuring an Event Console 3-1, 6-2 WQ71 QMM10UGP SCRIPT 6-5 Configuring the NT Event Adapter 3-1, 6-2 WQ72 QMM10UGP SCRIPT 6-6 Starting and Stopping the NT Event Adapter WQ73 QMM10UGP SCRIPT 7-1 Chapter 7, Tivoli GEM Instrumentation xiii, 1-1, 2-1, 2-2, 2-7 EVHAND QMM10UGP SCRIPT 7-3 Tivoli GEM Instrumentation Event Handling WQ74 QMM10UGP SCRIPT 7-5 Instrumentation Files, Libraries, and Profiles 9-1 RNNTSKS QMM10UGP SCRIPT 7-6 Tasks VIEWMNS QMM10UGP SCRIPT 7-7 Monitors PRERRQ QMM10UGP SCRIPT

/XRL/6

7-7 Preparing to Install Tivoli GEM Instrumentation WQ83 QMM10UGP SCRIPT 7-12 Installing Tivoli GEM Instrumentation WQ84 QMM10UGP SCRIPT 8-1 Chapter 8, Initializing Tivoli GEM Instrumentation xiii STEP1 QMM10UGP SCRIPT 8-2 Configuring MSMQ Servers 8-1 STEP2 QMM10UGP SCRIPT 8-2 Subscribing to and Distributing the File Packages 8-1 PROFIL2 QMM10UGP SCRIPT 8-2 Subscribing to and Distributing the Heartbeat Monitor 8-1, 9-5 CONFIRM QMM10UGP SCRIPT 8-5 Confirming Resource Discovery WQ88 QMM10UGP SCRIPT 9-1 Chapter 9, Tivoli GEM Instrumentation Tasks and Monitors xiii, 2-3 TAAASKS QMM10UGP SCRIPT 9-1 Locating and Running Tasks GMTASKS QMM10UGP SCRIPT 9-1 Tivoli GEM Instrumentation Tasks EXTASKS QMM10UGP SCRIPT 9-2 MSMQ Server Component Tasks 7-7 UNDAGGS QMM10UGP SCRIPT 9-4 Understanding MSMQ Server Aggregate Resources NAVAGGS QMM10UGP SCRIPT 9-4 Navigating to MSMQ Server Resources TEARAWY QMM10UGP SCRIPT 9-7 Using the Tear-Away Log SAMTASK QMM10UGP SCRIPT 9-7 Starting a Sample Task ALLMON QMM10UGP SCRIPT 9-8 Monitors 7-7 GEMMON1 QMM10UGP SCRIPT 9-9 Heartbeat Monitor EXMNTRS QMM10UGP SCRIPT 9-9 Manager for MQS-Supported Monitors USEMON QMM10UGP SCRIPT 9-11 Viewing Monitor Status WQ89 QMM10UGP SCRIPT A-1 Appendix A, Command Line Interface Commands xiii, 3-5 WQ94 QMM10UGP SCRIPT B-1 Appendix B, Event Classes and Rules xiii, 7-4 NTEAEV QMM10UGP SCRIPT B-2 NT Event Adapter Events DMRULES QMM10UGP SCRIPT B-5 Distributed Monitor (Sentry) Rules 4-8 WQ122 QMM10UGP SCRIPT C-1 Appendix C, Business and Component Descriptions xiii, 7-9, F-10 WQ123 QMM10UGP SCRIPT D-1 Appendix D, Tivoli GEM Instrumentation Task Descriptions xiv ICS QMM10UGP SCRIPT

/XRL/7

E-1 Appendix E, Instrumenting Connection Support to MSMQ xiv WQ139 QMM10UGP SCRIPT F-1 Appendix F, Finding and Correcting Problems xiv SCHEDD QMM10UGP SCRIPT F-15 Scheduling Monitors TASKNOT QMM10UGP SCRIPT F-16 Task Notes MONNOT QMM10UGP SCRIPT F-16 Monitor Notes DESKNOT QMM10UGP SCRIPT F-17 Desktop Notes GDFCT QMM10UGP SCRIPT F-17 Tivoli GEM Instrumentation Limitations, and Workarounds WQ140 QMM10UGP SCRIPT G-1 Appendix G, Messages xiv

Index Entries id File Page References

PROXY QMM10UGP SCRIPT i (1) Application Proxy APROXY QMM10UGP SCRIPT i (1) Application Proxy (2) installation 2-8 WQ1 QMM10UGP SCRIPT i (1) Application Proxy (2) definition 2-6 QMM307 QMM10UGP SCRIPT i (1) attributes, MSMQ server QMM308 QMM10UGP SCRIPT i (1) attributes, MSMQ server (2) displaying, wgetmsmq command A-2 QMM309 QMM10UGP SCRIPT i (1) attributes, MSMQ server (2) updating, wsetmsmq command A-3 AGGRESS QMM10UGP SCRIPT i (1) aggregate resources AGGRES1 QMM10UGP SCRIPT i (1) aggregate resources (2) viewed on Tivoli GEM console 9-4 AGGRES2 QMM10UGP SCRIPT i (1) aggregate resources (2) navigating to specific resources 9-4 QMM094 QMM10UGP SCRIPT i (1) authorization roles ADAUTH QMM10UGP SCRIPT i (1) authorization roles (2) description 1-3

/XRL/8

QMM447 QMM10UGP SCRIPT i (1) authorization roles (2) assigning i,i QMM095 QMM10UGP SCRIPT i (1) authorization roles (2) assigning (3) for Manager for MQS 3-2 QMM448 QMM10UGP SCRIPT i (1) authorization roles (2) assigning (3) for Tivoli GEM instrumentation 7-7 QMM586 QMM10UGP SCRIPT i (1) admintool command 7-11 QMM320 QMM10UGP SCRIPT i (1) business system description C-1 BDF1 QMM10UGP SCRIPT i (1) business description files QMM618 QMM10UGP SCRIPT i (1) business description files (2) installing C-1 QMM619 QMM10UGP SCRIPT i (1) business description files (2) contents C-2 CDF1 QMM10UGP SCRIPT i (1) component description files QMM620 QMM10UGP SCRIPT i (1) component description files (2) installing C-1 QMM621 QMM10UGP SCRIPT i (1) component description files (2) contents C-2 QMM287 QMM10UGP SCRIPT i (1) commands QMM288 QMM10UGP SCRIPT i (1) commands (2) wcrtmsmq A-1 QMM289 QMM10UGP SCRIPT i (1) commands (2) wgetmsmq A-2 QMM290 QMM10UGP SCRIPT i (1) commands (2) wsetmsmq A-3 QMM590 QMM10UGP SCRIPT i (1) commands (2) wtemp F-2, F-14, F-16 QMM591 QMM10UGP SCRIPT i (1) commands (2) wlscurrb F-6, F-8, F-11

/XRL/9

QMM592 QMM10UGP SCRIPT i (1) commands (2) wlsrbclass F-6, F-8, F-11 QMM593 QMM10UGP SCRIPT i (1) commands (2) wlsrbrules F-7, F-9, F-12 QMM594 QMM10UGP SCRIPT i (1) commands (2) wtdumprl F-7, F-8, F-9, F-12 QMM595 QMM10UGP SCRIPT i (1) commands (2) winstall 2-12 QMM596 QMM10UGP SCRIPT i (1) commands (2) admintool 7-11 QMM472 QMM10UGP SCRIPT i (1) client, Tivoli GEM, hints for using F-10 QMM144 QMM10UGP SCRIPT i (1) creating QMM299 QMM10UGP SCRIPT i (1) creating (2) MSMQ server instance i,i QMM300 QMM10UGP SCRIPT i (1) creating (2) MSMQ server instance (3) wcrtmsmq command A-1 QMM097 QMM10UGP SCRIPT i (1) creating (2) MSMQ server instance (3) from desktop 3-5 QMM265 QMM10UGP SCRIPT i (1) configuring QMM266 QMM10UGP SCRIPT i (1) configuring (2) event server 2-6, 6-2 QMM267 QMM10UGP SCRIPT i (1) configuring (2) event console 6-4 QMM268 QMM10UGP SCRIPT i (1) configuring (2) NT event adapter 6-5 QMM084 QMM10UGP SCRIPT i (1) configuring Manager for MQS QMM085 QMM10UGP SCRIPT i (1) configuring Manager for MQS (2) overview 3-1 QMM086 QMM10UGP SCRIPT i (1) configuring Manager for MQS (2) authorization roles

/XRL/10

3-2 CMDFL QMM10UGP SCRIPT i (1) data flow 2-2 CNSOLES QMM10UGP SCRIPT i (1) console TOPCON QMM10UGP SCRIPT i (1) console (2) Tivoli GEM 7-3 QMM484 QMM10UGP SCRIPT i (1) components, installed, location of QMM063 QMM10UGP SCRIPT i (1) components, installed, location of (2) Manager for MQS 2-6 QMM485 QMM10UGP SCRIPT i (1) components, installed, location of (2) Tivoli GEM instrumentation 7-8 QMM279 QMM10UGP SCRIPT i (1) Configure_Event_Adapter task 6-5 QMM281 QMM10UGP SCRIPT i (1) Configure_Event_Console task 6-4 QMM283 QMM10UGP SCRIPT i (1) Configure_Event_Server task 6-2 QMM451 QMM10UGP SCRIPT i (1) confirming server discovery on Tivoli GEM console 8-5 QMM519 QMM10UGP SCRIPT i (1) Configure task 5-7 QMM172 QMM10UGP SCRIPT i (1) Distributed Transaction Coordinator Status monitor 4-7 QMM452 QMM10UGP SCRIPT i (1) discovery, server, on Tivoli GEM console 8-5 QMM331 QMM10UGP SCRIPT i (1) Discover task 2-13 QMM550 QMM10UGP SCRIPT i (1) Discover_Connections task 9-2 QMM551 QMM10UGP SCRIPT i (1) Display_Enterprise task 9-2, 9-3 QMM552 QMM10UGP SCRIPT i (1) Display_Site task 9-2, 9-3 QMM249 QMM10UGP SCRIPT i (1) debugging QMM251 QMM10UGP SCRIPT i (1) debugging (2) helpful information F-14 QMM252 QMM10UGP SCRIPT i (1) debugging (2) log files, location of

/XRL/11

F-14 QMM207 QMM10UGP SCRIPT i (1) Display_Server_Status task 5-5, 9-2 QMM208 QMM10UGP SCRIPT i (1) Display_Server_Info task 5-5, 9-2 QMM209 QMM10UGP SCRIPT i (1) Display_MSMQ_Info task 5-5, 9-2 QMM504 QMM10UGP SCRIPT i (1) Display_Instances task 5-5, 9-2 QMM505 QMM10UGP SCRIPT i (1) Start_Services task 5-6, 9-2 QMM506 QMM10UGP SCRIPT i (1) Stop_Services task 5-6, 9-2 QMM507 QMM10UGP SCRIPT i (1) Purge_Dead_LetterQ task 5-6, 9-2 QMM508 QMM10UGP SCRIPT i (1) List_Dead_LetterQ task 5-6, 9-2 QMM119 QMM10UGP SCRIPT i (1) determining server status 3-10 QMM120 QMM10UGP SCRIPT i (1) deleting an MSMQ server 3-10 DBBCK QMM10UGP SCRIPT i (1) database DBBACK QMM10UGP SCRIPT i (1) database (2) backup 7-14 CORUPTD QMM10UGP SCRIPT i (1) database (2) corrupted, remedy F-15 DSUM QMM10UGP SCRIPT i (1) Disk Usage by MSMQ Server monitor 4-7 DMON QMM10UGP SCRIPT i (1) distributed monitoring 1-3, 1-3 QMM439 QMM10UGP SCRIPT i (1) distributing the heartbeat monitor 8-2 QMM173 QMM10UGP SCRIPT i (1) Event Adapter Status monitor 4-7 QMM348 QMM10UGP SCRIPT i (1) executing tasks QMM205 QMM10UGP SCRIPT i (1) executing tasks (2) Manager for MQS 5-2 QMM384 QMM10UGP SCRIPT i (1) executing tasks (2) Tivoli GEM instrumentation

/XRL/12

9-1, 9-7 QMM116 QMM10UGP SCRIPT i (1) instances, MSMQ 3-4 QMM009 QMM10UGP SCRIPT i (1) event QMM316 QMM10UGP SCRIPT i (1) event (2) rules B-5 QMM280 QMM10UGP SCRIPT i (1) event (2) console, configuring 6-4 QMM269 QMM10UGP SCRIPT i (1) event (2) adapter, NT i, i, i QMM050 QMM10UGP SCRIPT i (1) event (2) adapter, NT (3) requirements 2-5 QMM270 QMM10UGP SCRIPT i (1) event (2) adapter, NT (3) configuring 6-5 QMM271 QMM10UGP SCRIPT i (1) event (2) adapter, NT (3) starting and stopping 6-6 EVTCLAS QMM10UGP SCRIPT i (1) event (2) classes i, i, i, i QMM310 QMM10UGP SCRIPT i (1) event (2) classes (3) distributed monitoring B-1 QMM311 QMM10UGP SCRIPT i (1) event (2) classes (3) MSMQ_Monitors B-1 QMM312 QMM10UGP SCRIPT i (1) event (2) classes (3) NT event adapter B-2 QMM313 QMM10UGP SCRIPT i (1) event (2) classes (3) MSMQ_Event B-2 EVFILT QMM10UGP SCRIPT i (1) event (2) filtering 1-2, 6-7 EVTFL QMM10UGP SCRIPT

/XRL/13

i (1) event (2) flow 2-2 EVMGT QMM10UGP SCRIPT i (1) event (2) management i, i, i, i, i QMM258 QMM10UGP SCRIPT i (1) event (2) management (3) overview 6-1 QMM259 QMM10UGP SCRIPT i (1) event (2) management (3) authorization required 6-1 QMM262 QMM10UGP SCRIPT i (1) event (2) management (3) console, configuring 6-4 QMM263 QMM10UGP SCRIPT i (1) event (2) management (3) adapter, configuring 6-5 QMM264 QMM10UGP SCRIPT i (1) event (2) management (3) adapter, NT, starting and stopping 6-6 QMM524 QMM10UGP SCRIPT i (1) event (2) monitoring 6-6 QMM174 QMM10UGP SCRIPT i (1) FalconMQ Server Status monitor 4-7 QMM175 QMM10UGP SCRIPT i (1) Free Disk Space Available monitor 4-7 QMM323 QMM10UGP SCRIPT i (1) field descriptions, tasks D-1 FEATP QMM10UGP SCRIPT i (1) features, product QMM033 QMM10UGP SCRIPT i (1) features, product (2) distributed monitoring 1-3 QMM034 QMM10UGP SCRIPT i (1) features, product (2) monitoring, distributed 1-3 QMM025 QMM10UGP SCRIPT i (1) features, product (2) TEC 1-3 QMM016 QMM10UGP SCRIPT i (1) features, product (2) integration with Tivoli Management Framework

/XRL/14

i, 1-3 QMM021 QMM10UGP SCRIPT i (1) features, product (2) integration with Tivoli Management Framework (3) authorization 1-3, 1-3 QMM014 QMM10UGP SCRIPT i (1) features, product (2) task libraries 1-3 QMM010 QMM10UGP SCRIPT i (1) features, product (2) event filtering 1-2 FILEVT QMM10UGP SCRIPT i (1) filtering events 1-2, 6-7 FOREVT QMM10UGP SCRIPT i (1) forwarding events to event server 2-6 QMM176 QMM10UGP SCRIPT i (1) Generic Performance monitor 4-7 QMM122 QMM10UGP SCRIPT i (1) getting started QMM426 QMM10UGP SCRIPT i (1) getting started (2) with Tivoli GEM instrumentation i,i QMM428 QMM10UGP SCRIPT i (1) getting started (2) with Tivoli GEM instrumentation (3) heartbeat monitor, subscribing and distributing 8-2 QMM430 QMM10UGP SCRIPT i (1) getting started (2) with Tivoli GEM instrumentation (3) resource discovery, confirming 8-5 QMM123 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS i, i, i, i, i, i, i QMM124 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) configuring, overview 3-1 QMM125 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) authorization roles, assigning 3-2 QMM077 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) MSMQ server, managing 3-3 QMM078 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) MSMQ server, creating

/XRL/15

3-5 QMM079 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) instances, MSMQ 3-4 QMM080 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) server status, determining 3-10 QMM082 QMM10UGP SCRIPT i (1) getting started (2) with Manager for MQS (3) MSMQ server, deleting 3-10 HBEATM1 QMM10UGP SCRIPT i (1) Heartbeat monitor QMM436 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) distributing 8-2 QMM437 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) subscribing 8-2 WQ2 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) description, MSSQLServer 9-10 QMM438 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) description, MSMQ server 9-9 QMM500 QMM10UGP SCRIPT i (1) icon color F-13 QMM058 QMM10UGP SCRIPT i (1) interconnected TMRs 2-5 QMM520 QMM10UGP SCRIPT i (1) Install task 2-14 ICF1 QMM10UGP SCRIPT i (1) icon files QMM622 QMM10UGP SCRIPT i (1) icon files (2) installing C-1 QMM623 QMM10UGP SCRIPT i (1) icon files (2) contents C-2 QMM147 QMM10UGP SCRIPT i (1) installation QMM248 QMM10UGP SCRIPT i (1) installation (2) hints F-1 INSOPT QMM10UGP SCRIPT i (1) installation (2) options

/XRL/16

2-6 INSTALL QMM10UGP SCRIPT i (1) installing INAVCL QMM10UGP SCRIPT i (1) installing (2) available clients 2-8, 2-11, 7-13 INSMOD QMM10UGP SCRIPT i (1) installing (2) Manager for MQS i, i, i, i, i QMM070 QMM10UGP SCRIPT i (1) installing (2) Manager for MQS (3) procedure 2-10 QMM062 QMM10UGP SCRIPT i (1) installing (2) Manager for MQS (3) checklist 2-6 QMM068 QMM10UGP SCRIPT i (1) installing (2) Manager for MQS (3) administrator authorization 1-3 QMM065 QMM10UGP SCRIPT i (1) installing (2) Manager for MQS (3) components, location of 2-6 QMM047 QMM10UGP SCRIPT i (1) installing (2) Manager for MQS (3) NT event adapter requirements 2-5 INSTG1 QMM10UGP SCRIPT i (1) installing (2) Tivoli GEM instrumentation i, i, i, i QMM474 QMM10UGP SCRIPT i (1) installing (2) Tivoli GEM instrumentation (3) components, location of 7-8 QMM418 QMM10UGP SCRIPT i (1) installing (2) Tivoli GEM instrumentation (3) management regions 7-7 QMM419 QMM10UGP SCRIPT i (1) installing (2) Tivoli GEM instrumentation (3) administrator authorization 7-7 QMM421 QMM10UGP SCRIPT i (1) installing (2) Tivoli GEM instrumentation (3) procedure 7-12 JAVAKIT QMM10UGP SCRIPT i (1) Java Development Kit

/XRL/17

7-9 QMM253 QMM10UGP SCRIPT i (1) log files, location of F-14 LIBTSK QMM10UGP SCRIPT i (1) libraries, task 1-3 QMM477 QMM10UGP SCRIPT i (1) location of installed components QMM064 QMM10UGP SCRIPT i (1) location of installed components (2) Manager for MQS 2-6 QMM478 QMM10UGP SCRIPT i (1) location of installed components (2) Tivoli GEM instrumentation 7-8 QMM475 QMM10UGP SCRIPT i (1) listing tasks QMM204 QMM10UGP SCRIPT i (1) listing tasks (2) Manager for MQS 5-2 QMM476 QMM10UGP SCRIPT i (1) listing tasks (2) Tivoli GEM instrumentation 9-1 QMM314 QMM10UGP SCRIPT i (1) MSMQ_Monitors event class B-1 QMM178 QMM10UGP SCRIPT i (1) MQ Test monitor 4-7 QMM600 QMM10UGP SCRIPT i (1) Mqsvc monitor 4-6 QMM601 QMM10UGP SCRIPT i (1) Msdtc monitor 4-6 QMM602 QMM10UGP SCRIPT i (1) MSMQ IS monitor 4-5 QMM603 QMM10UGP SCRIPT i (1) MSMQ Queue monitor 4-5 QMM604 QMM10UGP SCRIPT i (1) MSMQ Service monitor 4-6 QMM605 QMM10UGP SCRIPT i (1) MSMQ Session monitor 4-6 WQ3 QMM10UGP SCRIPT i (1) MSMQ monitor tasks PDLQ QMM10UGP SCRIPT i (1) MSMQ monitor tasks (2) Purge_Dead_LetterQ 4-9 RSRV QMM10UGP SCRIPT i (1) MSMQ monitor tasks (2) Restart_Services 4-10 QMM315 QMM10UGP SCRIPT

/XRL/18

i (1) MSMQ_Event event class B-2 QMM117 QMM10UGP SCRIPT i (1) MSMQ instances 3-4 QMM098 QMM10UGP SCRIPT i (1) MSMQ server QMM301 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes i,i QMM305 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes (3) displaying, wgetmsmq command A-2 QMM306 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes (3) updating, wsetmsmq command A-3 QMM296 QMM10UGP SCRIPT i (1) MSMQ server (2) creating i,i QMM297 QMM10UGP SCRIPT i (1) MSMQ server (2) creating (3) from desktop 3-5 QMM298 QMM10UGP SCRIPT i (1) MSMQ server (2) creating (3) wcrtmsmq command A-1 QMM099 QMM10UGP SCRIPT i (1) MSMQ server (2) managing 3-3 QMM100 QMM10UGP SCRIPT i (1) MSMQ server (2) instances, creating 3-5 QMM101 QMM10UGP SCRIPT i (1) MSMQ server (2) icon pull-down tasks 3-8 QMM102 QMM10UGP SCRIPT i (1) MSMQ server (2) endpoints, MSMQ 3-4 QMM103 QMM10UGP SCRIPT i (1) MSMQ server (2) status, determining 3-10 QMM104 QMM10UGP SCRIPT i (1) MSMQ server (2) deleting 3-10 QMM105 QMM10UGP SCRIPT i (1) MSMQ server (2) profile managers

/XRL/19

3-11 QMM037 QMM10UGP SCRIPT i (1) monitoring, distributed 1-3 MANAGE QMM10UGP SCRIPT i (1) management QMM055 QMM10UGP SCRIPT i (1) management (2) regions, requirements 2-5 QMM222 QMM10UGP SCRIPT i (1) management (2) tasks i, i, i, i, i, i, i, i QMM464 QMM10UGP SCRIPT i (1) management (2) tasks (3) running from the desktop, hints F-3 QMM465 QMM10UGP SCRIPT i (1) management (2) tasks (3) running from the Tivoli GEM console, hints F-4 QMM255 QMM10UGP SCRIPT i (1) management (2) tasks (3) log files, location of F-14 QMM223 QMM10UGP SCRIPT i (1) management (2) tasks (3) listing 5-2 QMM224 QMM10UGP SCRIPT i (1) management (2) tasks (3) running 5-2, 9-1 QMM225 QMM10UGP SCRIPT i (1) management (2) tasks (3) authorization required, Manager for MQS 5-4 QMM495 QMM10UGP SCRIPT i (1) management (2) tasks (3) authorization required, Tivoli GEM instrumentation 7-7 QMM242 QMM10UGP SCRIPT i (1) management (2) tasks (3) overview 5-1 MEXA1 QMM10UGP SCRIPT i (1) msmq_admin TMR role 1-3, 3-2 MEXS1 QMM10UGP SCRIPT i (1) msmq_senior TMR role 1-3, 3-2 MNTRS QMM10UGP SCRIPT i (1) monitors

/XRL/20

WQ4 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i QMM160 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Special Queue Count 4-7 QMM161 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Generic Performance 4-7 QMM162 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Free Disk Space Available 4-7 QMM163 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Disk Usage by MSMQ Server 4-7 QMM164 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MQ Test 4-7 QMM166 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Event Adapter Status 4-7 QMM167 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Server Status 4-7 MSMQIS QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ IS 4-5 MSMQQ QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Queue 4-5 MSMQSRV QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Service 4-6 MSMQSES QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Session 4-6 MQSVC QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

/XRL/21

(3) Mqsvc 4-6 Q2QGW QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Q2qgw 4-6 MSDTC QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Msdtc 4-6 QMAX QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Special Queue Maximum Time 4-7 DTCSTAT QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Distributed Transaction Coordinator Status 4-7 FMQSTAT QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) FalconMQ Server Status 4-7 QMM405 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) i, i, i, i, i, i QMM466 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) hints for using F-5 QMM406 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) Heartbeat 9-9 QMM411 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) State 9-9 QMM412 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) Manager for MQS-supported 9-9 MONTHRE QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) thresholding 9-10 QMM408 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSMQ server) (3) scheduling F-15 WQ5 QMM10UGP SCRIPT

/XRL/22

i (1) monitors (2) Tivoli GEM instrumentation (MSSQLServer) i,i WQ6 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSSQLServer) (3) Heartbeat 9-10 WQ7 QMM10UGP SCRIPT i (1) monitors (2) Tivoli GEM instrumentation (MSSQLServer) (3) State 9-10 QMM257 QMM10UGP SCRIPT i (1) monitors (2) log files, location of F-14 QMM488 QMM10UGP SCRIPT i (1) monitors (2) listing i,i QMM151 QMM10UGP SCRIPT i (1) monitors (2) listing (3) Manager for MQS 4-1 QMM489 QMM10UGP SCRIPT i (1) monitors (2) listing (3) Tivoli GEM instrumentation 9-11 MNTRS1 QMM10UGP SCRIPT i (1) monitors (2) performance 4-5 QMM467 QMM10UGP SCRIPT i (1) monitors (2) hints for using F-5 QMM523 QMM10UGP SCRIPT i (1) monitors (2) queue 4-7, 4-7 MULTMRS QMM10UGP SCRIPT i (1) multiple TMRs 2-5 QMM051 QMM10UGP SCRIPT i (1) NT event adapter NTEASM QMM10UGP SCRIPT i (1) NT event adapter (2) Event Adapter Status monitor 4-7 QMM052 QMM10UGP SCRIPT i (1) NT event adapter (2) requirements 2-5 QMM272 QMM10UGP SCRIPT i (1) NT event adapter (2) configuring 6-5 QMM273 QMM10UGP SCRIPT i (1) NT event adapter

/XRL/23

(2) starting and stopping 6-6 QMM121 QMM10UGP SCRIPT i (1) profile managers, subscriber list 3-11 QMM038 QMM10UGP SCRIPT i (1) planning for installation QMM039 QMM10UGP SCRIPT i (1) planning for installation (2) overview i, i, i, 2-1 QMM048 QMM10UGP SCRIPT i (1) planning for installation (2) overview (3) NT event adapter 2-5 QMM053 QMM10UGP SCRIPT i (1) planning for installation (2) overview (3) management regions 2-5 QMM054 QMM10UGP SCRIPT i (1) planning for installation (2) overview (3) TMR 2-5 QMM059 QMM10UGP SCRIPT i (1) planning for installation (2) event server 2-6 PERFCM QMM10UGP SCRIPT i (1) performance counters 4-7 QMM152 QMM10UGP SCRIPT i (1) performance monitors PERFM QMM10UGP SCRIPT i (1) performance monitors (2) description 4-5 QMM154 QMM10UGP SCRIPT i (1) performance monitors (2) listing 4-1 PFEAT QMM10UGP SCRIPT i (1) product features QMM035 QMM10UGP SCRIPT i (1) product features (2) distributed monitoring 1-3 QMM036 QMM10UGP SCRIPT i (1) product features (2) monitoring, distributed 1-3 QMM017 QMM10UGP SCRIPT i (1) product features (2) integration with Tivoli Management Framework i, 1-3 QMM022 QMM10UGP SCRIPT i (1) product features (2) integration with Tivoli Management Framework (3) authorization 1-3, 1-3

/XRL/24

QMM027 QMM10UGP SCRIPT i (1) product features (2) TEC 1-3 QMM028 QMM10UGP SCRIPT i (1) product features (2) event display, consolidated 1-3 QMM015 QMM10UGP SCRIPT i (1) product features (2) task libraries 1-3 QMM011 QMM10UGP SCRIPT i (1) product features (2) event filtering 1-2 QMM606 QMM10UGP SCRIPT i (1) Q2qgw monitor 4-6 QMM339 QMM10UGP SCRIPT i (1) Query_State task 9-3 QMM553 QMM10UGP SCRIPT i (1) Query_Threshold_Settings task 9-2, 9-3 QMM572 QMM10UGP SCRIPT i (1) Query_Thresholds task 9-2, 9-3 QMM566 QMM10UGP SCRIPT i (1) Query_State task 9-2 QMM567 QMM10UGP SCRIPT i (1) Query_Values task 9-2, 9-3 QMM450 QMM10UGP SCRIPT i (1) resource discovery on Tivoli GEM console 8-5 QMM434 QMM10UGP SCRIPT i (1) rules, event QMM317 QMM10UGP SCRIPT i (1) rules, event (2) Manager for MQS B-5 QMM442 QMM10UGP SCRIPT i (1) rules, event (2) heartbeat monitor, subscribing and distributing 8-2 QMM449 QMM10UGP SCRIPT i (1) rules, event (2) resource discovery, confirming 8-5 QMM521 QMM10UGP SCRIPT i (1) resource roles 3-3 QMM480 QMM10UGP SCRIPT i (1) running tasks QMM206 QMM10UGP SCRIPT i (1) running tasks (2) Manager for MQS 5-2 QMM481 QMM10UGP SCRIPT i (1) running tasks

/XRL/25

(2) Tivoli GEM instrumentation 9-7 RUNCLII QMM10UGP SCRIPT i (1) running tasks (2) running from Tivoli GEM console, recommended 9-1 QMM043 QMM10UGP SCRIPT i (1) requirements QMM049 QMM10UGP SCRIPT i (1) requirements (2) NT event adapter 2-5 QMM057 QMM10UGP SCRIPT i (1) requirements (2) management regions 2-5 QMM482 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization i,i QMM069 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization (3) Manager for MQS 1-3 QMM483 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization (3) Tivoli GEM instrumentation 7-7 QMM607 QMM10UGP SCRIPT i (1) Special Queue Count monitor 4-7 QMM608 QMM10UGP SCRIPT i (1) Special Queue Maximum Time monitor 4-7 QMM610 QMM10UGP SCRIPT i (1) State monitor (MSMQ server) 9-9 QMM611 QMM10UGP SCRIPT i (1) State monitor (MSSQLServer) 9-10 QMM410 QMM10UGP SCRIPT i (1) scheduling Tivoli GEM instrumentation monitors F-15 QMM344 QMM10UGP SCRIPT i (1) Start task 9-1 QMM345 QMM10UGP SCRIPT i (1) Stop task 9-1 QMM274 QMM10UGP SCRIPT i (1) Start_Event_Adapter task 6-6 QMM275 QMM10UGP SCRIPT i (1) Stop_Event_Adapter task 6-6 QMM218 QMM10UGP SCRIPT i (1) Start_Debugging task 5-8, 9-2 QMM219 QMM10UGP SCRIPT i (1) Stop_Debugging task

/XRL/26

5-8, 9-2 QMM220 QMM10UGP SCRIPT i (1) Start_Monitors task 5-9, 9-2 QMM221 QMM10UGP SCRIPT i (1) Stop_Monitors task 5-9, 9-2 QMM554 QMM10UGP SCRIPT i (1) Set_Pulse task 9-2, 9-3 QMM568 QMM10UGP SCRIPT i (1) Set_Polling_Interval task 9-2, 9-3 QMM569 QMM10UGP SCRIPT i (1) Set_Thresholds task 9-2, 9-3 QMM570 QMM10UGP SCRIPT i (1) Start task 9-3 QMM571 QMM10UGP SCRIPT i (1) Stop task 9-3 QMM106 QMM10UGP SCRIPT i (1) server, MSMQ QMM302 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes i,i QMM303 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes (3) displaying, wgetmsmq command A-2 QMM304 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes (3) updating, wsetmsmq command A-3 QMM107 QMM10UGP SCRIPT i (1) server, MSMQ (2) managing 3-3 QMM294 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating i,i QMM108 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating (3) from desktop 3-5 QMM295 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating (3) wcrtmsmq command A-1 QMM109 QMM10UGP SCRIPT i (1) server, MSMQ (2) icon pull-down tasks 3-8 QMM110 QMM10UGP SCRIPT i (1) server, MSMQ

/XRL/27

(2) endpoints, MSMQ 3-4 QMM522 QMM10UGP SCRIPT i (1) server, MSMQ (2) subscribing to a profile manager 3-11 QMM111 QMM10UGP SCRIPT i (1) server, MSMQ (2) status, determining 3-10 QMM112 QMM10UGP SCRIPT i (1) server, MSMQ (2) deleting 3-10 QMM113 QMM10UGP SCRIPT i (1) server, MSMQ (2) profile manager 3-11 QMM168 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors i, i, i QMM170 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) listing 4-1 QMM171 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) performance 4-5 QMM177 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) performance counters 4-7 SQLSRV QMM10UGP SCRIPT i (1) server, MSSQLServer 7-4, 7-7, 7-14, 8-3, 8-5, 9-1, 9-1, 9-1, 9-2, 9-4, 9-4 SQLMON QMM10UGP SCRIPT i (1) server, MSSQLServer (2) monitors 9-9 SQLTSK QMM10UGP SCRIPT i (1) server, MSSQLServer (2) tasks 9-3 SERVSM QMM10UGP SCRIPT i (1) MSMQ Server Status monitor 4-7 SRVTMR QMM10UGP SCRIPT i (1) server, TMR 2-2 SRVTOP QMM10UGP SCRIPT i (1) server, Tivoli GEM 7-2 QMM440 QMM10UGP SCRIPT i (1) subscribing the heartbeat monitor 8-2 QMM473 QMM10UGP SCRIPT i (1) Tivoli GEM hints for using

/XRL/28

F-10 QMM615 QMM10UGP SCRIPT i (1) Tivoli GEM console 7-3 QMM616 QMM10UGP SCRIPT i (1) Tivoli GEM server 7-2 QMM617 QMM10UGP SCRIPT i (1) tear-away log 9-7 QMM324 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation GEMEVHD QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) event handling 7-3 GEMIC QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) instrumented components 7-4 GEMINIT QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) initializing 8-1 QMM422 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing i, i, i, i QMM423 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing (3) authorization required 7-7 QMM425 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing (3) procedure 7-12 WQ8 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing (3) components 7-8 INSTJDK QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing (3) Java Development Kit 7-9 QMM417 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) management regions 7-7 QMM413 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing i GINST2 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) installing (3) overview 7-1 QMM400 QMM10UGP SCRIPT

/XRL/29

i (1) Tivoli GEM instrumentation (2) monitors i, i, i QMM468 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) monitors (3) hints for using F-5 QMM402 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) monitors (3) supported Manager for MQS 9-9 QMM404 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) monitors (3) scheduling F-15 QMM325 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) tasks i, i, i QMM326 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) tasks (3) field descriptions D-1 QMM380 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) tasks (3) locating 9-1 QMM381 QMM10UGP SCRIPT i (1) Tivoli GEM instrumentation (2) tasks (3) running 9-1, 9-7 QMM243 QMM10UGP SCRIPT i (1) troubleshooting QMM455 QMM10UGP SCRIPT i (1) troubleshooting (2) hints i, i, i, i, i, i, i QMM456 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) tasks and jobs, running from the desktop F-3 QMM499 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) icon color F-13 QMM457 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) tasks and jobs, running from the Tivoli GEM console F-4 QMM458 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) monitors, using

/XRL/30

F-5 QMM459 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) TEC, using F-8 QMM460 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) Tivoli GEM client, using F-10 QMM244 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) installation F-1 QMM246 QMM10UGP SCRIPT i (1) troubleshooting (2) debugging information F-14 QMM247 QMM10UGP SCRIPT i (1) troubleshooting (2) log files F-14 QMM180 QMM10UGP SCRIPT i (1) tasks QMM461 QMM10UGP SCRIPT i (1) tasks (2) hints i,i QMM462 QMM10UGP SCRIPT i (1) tasks (2) hints (3) running from the desktop F-3 QMM463 QMM10UGP SCRIPT i (1) tasks (2) hints (3) running from the Tivoli GEM console F-4 QMM498 QMM10UGP SCRIPT i (1) tasks (2) field descriptions D-1 QMM327 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i, i QMM328 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) field descriptions D-1 QMM383 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) running 9-1, 9-7 QMM350 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_State

/XRL/31

9-1, 9-2 QMM351 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_Thresholds 9-1, 9-2 QMM352 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_Values 9-1, 9-2 QMM353 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Polling_Interval 9-1, 9-2 QMM354 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Thresholds 9-1, 9-2 QMM355 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Services 9-1, 9-2 QMM356 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Services 9-1, 9-2 QMM357 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Discover_Connections 9-2 QMM358 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Enterprise 9-2 QMM359 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Site 9-2 QMM360 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Pulse 9-2 QMM361 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Instances 9-2 QMM362 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Server_Status 9-2 QMM363 QMM10UGP SCRIPT

/XRL/32

i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Server_Info 9-2 QMM364 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_MSMQ_Info 9-2 QMM365 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) List_Dead_LetterQ 9-2 QMM366 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Purge_Dead_LetterQ 9-2 QMM367 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Monitors 9-2 QMM368 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Monitors 9-2 QMM369 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Debugging 9-2 QMM370 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Debugging 9-2 QMM531 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) i, i, i, i, i, i, i, i, i, i, i QMM532 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Display_Enterprise 9-3 QMM533 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Display_Site 9-3 QMM534 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_State 9-3 QMM535 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Threshold_Settings

/XRL/33

9-3 QMM536 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Thresholds 9-3 QMM537 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Values 9-3 QMM538 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Polling_Interval 9-3 QMM539 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Pulse 9-3 QMM540 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Thresholds 9-3 QMM541 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Start 9-3 QMM542 QMM10UGP SCRIPT i (1) tasks (2) Tivoli GEM instrumentation (MSSQLServer component) (3) Stop 9-3 QMM254 QMM10UGP SCRIPT i (1) tasks (2) log files, location of F-14 QMM181 QMM10UGP SCRIPT i (1) tasks (2) overview 5-1 QMM182 QMM10UGP SCRIPT i (1) tasks (2) listing 5-2 QMM183 QMM10UGP SCRIPT i (1) tasks (2) running 5-2 QMM184 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server i, i, i, i, i, i, i, i, i QMM185 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) authorization required 5-4 QMM186 QMM10UGP SCRIPT

/XRL/34

i (1) tasks (2) MSMQ server (3) Display_Server_Status 5-5 QMM187 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_Server_Info 5-5 QMM188 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_MSMQ_Info 5-5 QMM514 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_Instances 5-5 QMM515 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Start_Services 5-6 QMM516 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Stop_Services 5-6 QMM517 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Purge_Dead_LetterQ 5-6 QMM518 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) List_Dead_LetterQ 5-6 QMM198 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility i, i, i, i, i, i, i, i QMM199 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) authorization required 5-7 QMM200 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Start_Debugging 5-8 QMM201 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Stop_Debugging 5-8 QMM202 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Start_Monitors

/XRL/35

5-9 QMM203 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Stop_Monitors 5-9 QMM501 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Install 2-14 QMM502 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Configure 5-7 QMM503 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Discover 2-13 QMM530 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC i, i, i, i, i QMM284 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Server 6-2 QMM285 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Console 6-4 QMM278 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Adapter 6-5 QMM525 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Start_Event_Adapter 6-6 QMM526 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Stop_Event_Adapter 6-6 EVSRV QMM10UGP SCRIPT i (1) event server QMM469 QMM10UGP SCRIPT i (1) event server (2) hints for using F-8 EVSRV1 QMM10UGP SCRIPT i (1) event server (2) configuring 2-6, 6-2 TSKLIB QMM10UGP SCRIPT i (1) task libraries

/XRL/36

1-3 TCON QMM10UGP SCRIPT i (1) TEC console 1-3 TIVOLI QMM10UGP SCRIPT i (1) Tivoli QMM018 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with i, i, i, i QMM019 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) overview 1-3 QMM024 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) authorization 1-3, 1-3 QMM031 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) TEC 1-3 QMM032 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) event display 1-3 TMEAUT QMM10UGP SCRIPT i (1) Tivoli (2) authorization 1-3 TMEECON QMM10UGP SCRIPT i (1) Tivoli (2) enterprise console 1-3 TMEDMON QMM10UGP SCRIPT i (1) Tivoli (2) distributed monitoring 1-3, 1-3 TMR QMM10UGP SCRIPT i (1) TMR QMM056 QMM10UGP SCRIPT i (1) TMR (2) requirements 2-5 TMR1 QMM10UGP SCRIPT i (1) TMR (2) roles TMR1A QMM10UGP SCRIPT i (1) TMR (2) roles (3) msmq_admin 1-3, 3-2 TMR1B QMM10UGP SCRIPT i (1) TMR (2) roles (3) msmq_senior 1-3, 3-2 TMR2 QMM10UGP SCRIPT

/XRL/37

i (1) TMR (2) server 2-2 TMRSMUL QMM10UGP SCRIPT i (1) TMR (2) multiple 2-5 QMM379 QMM10UGP SCRIPT i (1) wpostemsg F-2 QMM291 QMM10UGP SCRIPT i (1) wcrtmsmq command A-1 QMM292 QMM10UGP SCRIPT i (1) wgetmsmq command A-2 QMM293 QMM10UGP SCRIPT i (1) wsetmsmq command A-3 QMM580 QMM10UGP SCRIPT i (1) wtemp command F-2, F-14, F-16 QMM581 QMM10UGP SCRIPT i (1) wlscurrb command F-6, F-8, F-11 QMM582 QMM10UGP SCRIPT i (1) wlsrbclass command F-6, F-8, F-11 QMM583 QMM10UGP SCRIPT i (1) wlsrbrules command F-7, F-9, F-12 QMM584 QMM10UGP SCRIPT i (1) wtdumprl command F-7, F-8, F-9, F-12 QMM585 QMM10UGP SCRIPT i (1) winstall command 2-12 WQX13 QMM10UGP SCRIPT i (1) console 1-3 WQX14 QMM10UGP SCRIPT i (1) Tivoli WQX15 QMM10UGP SCRIPT i (1) Tivoli (2) enterprise console 1-4 WQX16 QMM10UGP SCRIPT i (1) integration with Tivoli Management Framework WQX17 QMM10UGP SCRIPT i (1) integration with Tivoli Management Framework (2) TEC 1-4 WQX18 QMM10UGP SCRIPT i (1) integration with Tivoli Management Framework WQX19 QMM10UGP SCRIPT i (1) integration with Tivoli Management Framework (2) event display 1-4 WQX20 QMM10UGP SCRIPT i (1) TEC console 1-4 WQX21 QMM10UGP SCRIPT

/XRL/38

i (1) features, product WQX22 QMM10UGP SCRIPT i (1) features, product (2) TEC 1-4 WQX23 QMM10UGP SCRIPT i (1) product features WQX24 QMM10UGP SCRIPT i (1) product features (2) TEC 1-4 WQX25 QMM10UGP SCRIPT i (1) features, product WQX26 QMM10UGP SCRIPT i (1) features, product (2) event display, consolidated 1-4 WQX27 QMM10UGP SCRIPT i (1) product features WQX28 QMM10UGP SCRIPT i (1) product features (2) event display, consolidated 1-4 WQX29 QMM10UGP SCRIPT i (1) console WQX30 QMM10UGP SCRIPT i (1) console (2) TEC 1-4 WQX31 QMM10UGP SCRIPT i (1) Tivoli WQX32 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with WQX33 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) TEC 1-4 WQX34 QMM10UGP SCRIPT i (1) Tivoli WQX35 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with WQX36 QMM10UGP SCRIPT i (1) Tivoli (2) framework, integration with (3) event display 1-4 WQX37 QMM10UGP SCRIPT i (1) Tivoli WQX38 QMM10UGP SCRIPT i (1) Tivoli (2) distributed monitoring 1-4 WQX39 QMM10UGP SCRIPT i (1) distributed monitoring 1-4 WQX40 QMM10UGP SCRIPT i (1) monitoring, distributed 1-4 WQX41 QMM10UGP SCRIPT

/XRL/39

i (1) features, product WQX42 QMM10UGP SCRIPT i (1) features, product (2) distributed monitoring 1-4 WQX43 QMM10UGP SCRIPT i (1) product features WQX44 QMM10UGP SCRIPT i (1) product features (2) distributed monitoring 1-4 WQX45 QMM10UGP SCRIPT i (1) features, product WQX46 QMM10UGP SCRIPT i (1) features, product (2) monitoring, distributed 1-4 WQX47 QMM10UGP SCRIPT i (1) product features WQX48 QMM10UGP SCRIPT i (1) product features (2) monitoring, distributed 1-4 WQX51 QMM10UGP SCRIPT i (1) dialogs WQX52 QMM10UGP SCRIPT i (1) dialogs (2) install product 2-7

List Items id File Page References

SELARG QMM10UGP SCRIPT 4-3 6

/XRL/40

Processing Options

Runtime values: Document fileid ...... QMM10UGP SCRIPT Document type ...... USERDOC Document style ...... TIVOLI Profile ...... EDFPRF40 Service Level ...... 0032 SCRIPT/VS Release ...... 4.0.0 Date ...... 99.04.07 Time ...... 08:20:13 Device ...... PSA Number of Passes ...... 4 Index ...... YES SYSVAR G ...... INLINE SYSVAR X ...... YES

Formatting values used: Annotation ...... NO Cross reference listing ...... YES Cross reference head prefix only ...... NO Dialog ...... LABEL Duplex ...... YES DVCF conditions file ...... (none) DVCF value 1 ...... (none) DVCF value 2 ...... (none) DVCF value 3 ...... (none) DVCF value 4 ...... (none) DVCF value 5 ...... (none) DVCF value 6 ...... (none) DVCF value 7 ...... (none) DVCF value 8 ...... (none) DVCF value 9 ...... (none) Explode ...... NO Figure list on new page ...... YES Figure/table number separation ...... YES Folio-by-chapter ...... YES Head 0 body text ...... (none) Head 1 body text ...... Chapter Head 1 appendix text ...... Appendix Hyphenation ...... NO Justification ...... NO Language ...... ENGL Keyboard ...... 395 Layout ...... OFF Leader dots ...... YES Master index ...... (none) Partial TOC (maximum level) ...... 4 Partial TOC (new page after) ...... INLINE Print example id's ...... NO Print cross reference page numbers ...... YES Process value ...... (none) Punctuation move characters ...... , Read cross-reference file ...... (none) Running heading/footing rule ...... NONE Show index entries ...... NO Table of Contents (maximum level) ...... 3 Table list on new page ...... YES

/XRL/41

Title page (draft) alignment ...... RIGHT Write cross-reference file ...... (none)