Tivoli Manager for Message Queue Server User’s Guidepublib.boulder.ibm.com/tividd/td/qmm/qmm10ugp/en_US/PDF/qmm1… · Manager for Message Queue Server (Manager for MQS). Manager

Tivoli Manager for Message Queue ServerUser’s Guide

Version 1.0ii

Tivoli Manager for MessageQueue Server User's Guide (April1999)Copyright NoticeCopyright 1999 by Tivoli Systems, an IBM Company, including this documentation and all software. All rightsreserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for TivoliProducts to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted,transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means,electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of TivoliSystems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of anymachine-readable documentation for your own use, provided that each such reproduction shall carry the TivoliSystems copyright notice. No other rights under copyright are granted without prior written permission of TivoliSystems. The document is not intended for production and is furnished “as is” without warranty of any kind. Allwarranties on this document are hereby disclaimed including the warranties of merchantability and fitness fora particular purpose. Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subjectto restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe 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 MicrosoftCorporation.UNIX is a registered trademark in the United States and other countries licensed exclusively through X/OpenCompany Limited.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they willbe available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices 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 functionallyequivalent product, program, or service can be used instead of the referenced product, program, or service. Theevaluation and verification of operation in conjunction with other products, except those expressly designated byTivoli 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, inwriting, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785USA.

Version 1.0iv

ContentsTivoli Manager for Message Queue ServerUser's Guide (April 1999)

Preface

Chapter 1. Introducing Manager for MessageQueue Server

Operations Management . . . . . . . . . . . . . . . . . . . . . .1-2Event Management . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Event Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Task Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3Integration with Tivoli Management Framework . . . . . . . 1-3 Administrator Authorization . . . . . . . . . . . . . . . . . . . . 1-3Enterprise Consoles . . . . . . . . . . . . . . . . . . . . . . . . .1-4Tivoli Distributed Monitoring . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 2. Planning for and InstallingManager for Message Queue Server

Where to Install Manager for MQS . . . . . . . . . . . . . . . . 2-3Pre-Installation Considerations . . . . . . . . . . . . . . . . . .2-5

NT Event Adapter Requirements . . . . . . . . . . . . . . . 2-5Configuring Tivoli Management Regions . . . . . . . . . . 2-5Configuring TEC Event Servers . . . . . . . . . . . . . . . . 2-6Application Proxy Availability . . . . . . . . . . . . . . . . . . 2-6

Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . .2-6Installing the Application Proxy . . . . . . . . . . . . . . . . . . 2-8

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

Contents

From the Desktop . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Using the winstall Command . . . . . . . . . . . . . . . . . . 2-9Using the Install Task . . . . . . . . . . . . . . . . . . . . . . . 2-9

Installing Manager for MQS . . . . . . . . . . . . . . . . . . . . 2-9From the Desktop . . . . . . . . . . . . . . . . . . . . . . . . 2-10Using the winstall Command . . . . . . . . . . . . . . . . . 2-12Using the Discover and Install Tasks . . . . . . . . . . . . 2-13

Chapter 3. Getting Started with Manager forMessage Queue Server

Configuring Manager for MQS . . . . . . . . . . . . . . . . . . . 3-1Assigning Authorization Roles . . . . . . . . . . . . . . . . . . . 3-2

Assigning TMR Roles to a Tivoli Administrator . . . . . . 3-2Assigning Resource Roles to a Tivoli Administrator . . . 3-3

Managing Microsoft Message Queue Servers . . . . . . . . . 3-3MSMQ Server Instances . . . . . . . . . . . . . . . . . . . . . 3-4Creating MSMQ Server Instances . . . . . . . . . . . . . . . 3-5Determining Server Status . . . . . . . . . . . . . . . . . . . 3-10Deleting an MSMQ Server . . . . . . . . . . . . . . . . . . . 3-10MSMQ Server Lists . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4. Monitoring Microsoft MessageQueue Servers

Listing the Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Understanding the Monitors . . . . . . . . . . . . . . . . . . . . 4-5

Performance Monitors . . . . . . . . . . . . . . . . . . . . . . .4-5Predefined Monitors . . . . . . . . . . . . . . . . . . . . . . . .4-6Additional MSMQ-specific Monitors . . . . . . . . . . . . . . 4-7Default Settings for Monitor Responses . . . . . . . . . . . 4-9

MSMQ Monitor Tasks . . . . . . . . . . . . . . . . . . . . . . . . 4-9Purge_Dead_LetterQ . . . . . . . . . . . . . . . . . . . . . .4-10Restart_Services . . . . . . . . . . . . . . . . . . . . . . . . .4-10

Chapter 5. Tasks to Manage MicrosoftMessage Queue Resources

Listing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

Version 1.0vi

Contents

Running Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2MSMQ Server Tasks . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Server Information Tasks . . . . . . . . . . . . . . . . . . . . 5-5Server Management Tasks . . . . . . . . . . . . . . . . . . . 5-6

MSMQ Utility Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7Start_Debugging . . . . . . . . . . . . . . . . . . . . . . . . . .5-8Stop_Debugging . . . . . . . . . . . . . . . . . . . . . . . . . .5-8Start_Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9Stop_Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9

Chapter 6. Managing Microsoft MessageQueue Events

Configuring the Event Server . . . . . . . . . . . . . . . . . . . 6-2Procedure for Configuring the Event Server . . . . . . . . 6-3

Configuring an Event Console . . . . . . . . . . . . . . . . . . . 6-4Configuring the NT Event Adapter . . . . . . . . . . . . . . . . 6-5Starting and Stopping the NT Event Adapter . . . . . . . . . 6-6Monitoring the NT Event Adapter . . . . . . . . . . . . . . . . . 6-6Filtering Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

Chapter 7. Tivoli GEM InstrumentationUnderstanding the Tivoli GEM Server . . . . . . . . . . . . . . 7-2Understanding the Tivoli GEM Console . . . . . . . . . . . . . 7-3Tivoli GEM Instrumentation Event Handling . . . . . . . . . . 7-3Instrumented Components . . . . . . . . . . . . . . . . . . . . .7-4Instrumentation Files, Libraries, and Profiles . . . . . . . . . 7-5Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7Preparing to Install Tivoli GEM Instrumentation . . . . . . . . 7-7

Tivoli Management Regions . . . . . . . . . . . . . . . . . . . 7-7Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-7Installation Prerequisites . . . . . . . . . . . . . . . . . . . . .7-8

Installing and Configuring Tivoli GEM InstrumentationComponents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8

Copying BDF, CDF, and Icon Files . . . . . . . . . . . . . . 7-9Installing 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 TivoliGEM Console . . . . . . . . . . . . . . . . . . . . . . . . . .7-10

Setting Security for the Windows NT Operating System 7-11Installing Tivoli GEM Instrumentation . . . . . . . . . . . . 7-12

Chapter 8. Initializing Tivoli GEMInstrumentation

Configuring MSMQ Servers . . . . . . . . . . . . . . . . . . . . 8-2Subscribing to and Distributing the File Packages . . . . . . 8-2Subscribing to and Distributing the Heartbeat Monitor . . . 8-2Confirming Resource Discovery . . . . . . . . . . . . . . . . . . 8-5

Chapter 9. Tivoli GEM Instrumentation Tasksand Monitors

Locating and Running Tasks . . . . . . . . . . . . . . . . . . . . 9-1Tivoli GEM Instrumentation Tasks . . . . . . . . . . . . . . . 9-1Understanding MSMQ Server Aggregate Resources . . 9-4Navigating to MSMQ Server Resources . . . . . . . . . . . 9-4Using the Tear-Away Log . . . . . . . . . . . . . . . . . . . . 9-7Starting a Sample Task . . . . . . . . . . . . . . . . . . . . . . 9-7

Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8MSMQ Server Monitors . . . . . . . . . . . . . . . . . . . . . . 9-8MSSQLServer Monitors . . . . . . . . . . . . . . . . . . . .9-10Monitor Operability . . . . . . . . . . . . . . . . . . . . . . . .9-10Viewing Monitor Status . . . . . . . . . . . . . . . . . . . . . 9-11

Appendix A. Command Line InterfaceCommands

Appendix B. Event Classes and RulesManager for Message Queue Server Event Classes . . . . B-1

Distributed Monitoring Events . . . . . . . . . . . . . . . . . . B-1NT Event Adapter Events . . . . . . . . . . . . . . . . . . . . B-2

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

Version 1.0viii

Contents

Tivoli GEM Instrumentation Distributed Monitoring(SENTRY) Rules . . . . . . . . . . . . . . . . . . . . . . . . .B-6

Appendix C. Business and ComponentDescriptions

Installing BDF, CDF, and Icon Files . . . . . . . . . . . . . . C-2Business and Component Description Files . . . . . . . . . C-2Icon Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3

Appendix D. Tivoli GEM Instrumentation TaskDescriptions

Appendix E. Instrumenting ConnectionSupport to MSMQ

Appendix F. Finding and Correcting ProblemsInstallation Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-1Hints on Using Tasks and Jobs from the Desktop . . . . . . F-3Hints on Running Tasks from the Tivoli GEM Console . . . F-4Hints on Using Monitors . . . . . . . . . . . . . . . . . . . . . . . F-5Hints on Using the TEC . . . . . . . . . . . . . . . . . . . . . . . F-8Hints on Using the Tivoli GEM Console . . . . . . . . . . . . F-10Icon State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-13Helpful Debugging Information . . . . . . . . . . . . . . . . . . F-14Tivoli GEM Server Database Corruption . . . . . . . . . . . F-15Scheduling Monitors . . . . . . . . . . . . . . . . . . . . . . . .F-15Product Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-15

Task Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-16Monitor Notes . . . . . . . . . . . . . . . . . . . . . . . . . . .F-16Tivoli GEM Instrumentation Monitor Notes . . . . . . . . F-17Desktop Notes . . . . . . . . . . . . . . . . . . . . . . . . . .F-17

Tivoli GEM Instrumentation Limitations, and Workarounds F-17The APM_HEARTBEAT Event Is Not Generated . . . . F-17

Appendix G. Messages

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

Contents

Glossary

Index

Version 1.0x

PrefaceThe Tivoli Manager for Message Queue Server User's Guideprovidesinformation about planning for, installing, and using the TivoliManager for Message Queue Server (Manager for MQS).

Manager for MQS enables you to monitor the performance, diskusage, and status of the Microsoft Message Queue (MSMQ) server.In addition, Manager for MQS management tasks enable you to stopand 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 providedwith the Manager for MQS product.

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

Prerequisite and Related DocumentsFor hardware and software requirements, and other releaseinformation, refer to the Tivoli Manager for Message Queue ServerRelease 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 2include:

■ 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. Productsreferred to in this manual may still be available under theirold names, for example, TME 10 Enterprise Console insteadof Tivoli Enterprise Console.

What This Guide ContainsThe Tivoli Manager for Message Queue Server User's Guidecontainsthe 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 MessageQueue Server” on page 2-1

Covers the planning for and installing of Manager for MQS.

■ Chapter 3, “Getting Started with Manager for Message QueueServer” on page 3-1

Covers the configuring of Manager for MQS.

■ Chapter 4, “Monitoring Microsoft Message Queue Servers” onpage 4-1

Describes how to use the performance monitors that Managerfor MQS provides.

■ Chapter 5, “Tasks to Manage Microsoft Message QueueResources” on page 5-1

Version 1.0xii

Preface

Describes how to locate and use tasks that are provided byManager for MQS.

■ Chapter 6, “Managing Microsoft Message Queue Events” onpage 6-1

Contains information on configuring and using the NT eventadapter to forward MSMQ server events to the Tivoli EnterpriseConsole (TEC) event server.

■ Chapter 7, “Tivoli GEM Instrumentation” on page 7-1

Covers the planning for and installing of Tivoli GEMinstrumentation.

■ Chapter 8, “Initializing Tivoli GEM Instrumentation” onpage 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 becomeaccessible for operational management of your MSMQ serversafter the Tivoli GEM components have been successfullyinstalled.

■ Appendix A, “Command Line Interface Commands” onpage A-1

Contains a list of supported command line interface (CLI)commands that you can use to create, to change, and to view theattributes 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 ofthe labels provided by the Windows NT event viewer and theTivoli event display.

■ Appendix C, “Business and Component Descriptions” onpage C-1

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

Preface

Describes the Tivoli GEM business description files and theTivoli 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 TivoliGEM instrumentation tasks.

■ Appendix E, “Instrumenting Connection Support to MSMQ” onpage E-1

Provides instructions on how to instrument products that provideconnections to MSMQ.

■ Appendix F, “Finding and Correcting Problems” on page F-1

Provides installation tips, help on debugging problems, andtypical symptoms and solutions.

■ Appendix G, “Messages” on page G-1

Contains a list of the messages that are generated by Managerfor MQS.

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

Bold Commands, keywords, file names, authorizationroles, URLs, or other information that you must useliterally appear in bold. The names or titles of screenobjects also appear in bold.

Italics Variables and values that you must provide appear initalics. Words and phrases that are emphasized alsoappear in italics.

Bold Italics New terms appear in bold italics when they aredefined in the text.

Monospace Code examples, output, and system messages appearin a monospace font.

Version 1.0xiv

Preface

DocumentationWhen you install Manager for MQS, files containing browsable andprintable versions of the Tivoli Manager for Message Queue ServerUser's Guide (userguide.pdf and userguide.htm) are automaticallyplaced in the %BINDIR%\..\generic_unix\TME\MSMQ\docdirectory.

In addition, the files are provided in the \DOC directory on theproduct'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 SupportFor support inside the United States for this or any other Tivoliproduct, contact Tivoli Customer Support in one of the followingways:

■ 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 SupportHandbook for phone numbers in your country. The Customer SupportHandbook is available online at http://www.support.tivoli.com.

When you contact Tivoli Customer Support, be prepared to provideidentification information for your company so that support personnelcan assist you more readily.

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

Preface

Version 1.0xvi

Intro

du

ction

1 Chapter 1. Introducing Managerfor Message Queue Server

Tivoli Manager for Message Queue Server (Manager for MQS)provides a centralized system management tool for the MicrosoftMessage Queue (MSMQ) services on the Tivoli platform. Managerfor MQS facilitates the management of MSMQ servers on managednodes and endpoints available on Tivoli Management FrameworkVersion 3.6.

The MSMQ server provides loosely coupled and reliable networkcommunications services that are based on the message queuingmodel. MSMQ optionally supports transactions through MicrosoftTransaction Service (MTS) and Microsoft Distributed TransactionCoordinator (MSDTC). MSMQ also provides connectivity toMQSeries by using Level 8 FalconMQ Bridge.

Manager for MQS can be used with the following optional products:

■ Tivoli Enterprise Console (TEC): receives, filters, and forwardsselected events to an event server for further processing. Formore information, see “NT Event Adapter Requirements” onpage 2-5.

■ Tivoli Global Enterprise Manager (Tivoli GEM) and TivoliGEM instrumentation: enables you to obtain a graphicaltopology display of the MSMQ servers, their statuses, and a listof tasks that can be run against each MSMQ server. For moreinformation, see Chapter 7, “Tivoli GEM Instrumentation” onpage 7-1.

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

Manager for MQS provides the following features that enable you toperform system management functions for MSMQ:

■ Tasks to control and automate MSMQ administrative activitieson managed nodes and endpoints available on TivoliManagement Framework, Version 3.6

■ A selection of monitors for key performance and availabilitystatistics for MSMQ servers

■ Configuration files for the TEC event adapter for Windows NT(NT event adapter) to receive, filter, and forward selected eventsto the TEC

Operations ManagementThis feature enables you to perform tasks such as starting andstopping servers, running utilities, and obtaining information aboutservers.

Event ManagementThis feature enables you to monitor and retrieve MSMQ events fromMSMQ servers. These events are converted to TEC event format andforwarded to a centralized event server for display and processing.

Event FilteringManager for MQS utilizes an NT event adapter that enables you tospecify events that you do not want forwarded to the event server.With this feature, you can prevent the TEC from being populatedwith harmless events, allowing you to focus on events of interest toyour administrators.

Version 1.01-2

Intro

du

ction

Task Libraries

Task LibrariesManager for MQS provides a set of tasks for operating and managingmanaged nodes and endpoints on an MSMQ server.

Integration with Tivoli ManagementFramework

Tivoli Management Framework provides a powerful and flexibleframework for developing a comprehensive management system.Manager for MQS integrates your MSMQ servers into this system.Integration with the Tivoli Management Framework provides manybenefits, including:

■ Authorizations - MSMQ resources are contained in a Tivolipolicy region. Manager for MQS creates two new resourceroles, msmq_senior and msmq_admin. To start tasks, one orboth of these roles must be assigned to an administrator.

■ Enterprise consoles - TECs provide consolidated event displaysfor MSMQ events. TECs are configurable and can be createdand configured for a number of MSMQ administrators andservers.

■ Distributed monitoring - You can set up monitors to alert youabout events concerning MSMQ resources. Configurablethresholds and responses enable you to actively monitor andautomatically create various severity levels for event serverevents.

Administrator AuthorizationManager for MQS enables you to assign varying degrees ofauthorization to system administrators. For more information, see“Assigning Authorization Roles” on page 3-2.


Enterprise Consoles

Enterprise ConsolesThe TECs provide consolidated event displays for the Message QueueServer events. The TECs are configurable and can be created andconfigured for any number of Message Queue Server administratorsand servers.

Tivoli Distributed MonitoringYou can set up monitors to alert you about events concerningMessage Queue Server resources. Configurable thresholds andresponses enable active monitoring and automatic creation ofdiffering severity levels of TEC event server events.

Version 1.01-4

Plan

nin

g an

d In

stallation

2Chapter 2. Planning for andInstalling Manager for MessageQueue Server

Managing Microsoft Message Queue (MSMQ) servers with TivoliManager for Message Queue Server (Manager for MQS) requiresinstallation of the Manager for MQS and, optionally, Tivoli GlobalEnterprise Manager (Tivoli GEM) instrumentation if Tivoli GEM isinstalled. If Tivoli GEM is installed on your system, then refer toChapter 7, “Tivoli GEM Instrumentation” on page 7-1 for moreinformation regarding Tivoli GEM instrumentation.

Before installing Manager for MQS, you must prepare both yourTivoli and MSMQ server installations. This chapter describes how toinstall Manager for MQSand the following pre-installation tasks:

1. Ensure that all prerequisite software is installed and you arerunning on a supported operating system.

Refer to the Tivoli Manager for Message Queue Server ReleaseNotes for information on supported Tivoli software, prerequisitesoftware and operating systems, and disk space requirements.

2. Install the Application Proxy.

3. If you are using the Tivoli Enterprise Console (TEC), install andconfigure the TEC event adapter for Windows NT(NT eventadapter) packaged with the TEC. See “NT Event AdapterRequirements” on page 2-5.


4. If you manage MSMQ resources with Tivoli GEM, seeChapter 7, “Tivoli GEM Instrumentation” on page 7-1.

5. Configure the Tivoli Management Regions (TMRs) as describedon page 2-5.

6. If you are using Tivoli Management Framework Endpoints andGateways available on Tivoli Management Framework Version3.6, ensure that they are properly configured and functional. Formore information on endpoint gateways or endpoints, seeChapter 8, "TME 10 Endpoints and Gateways" in the TME 10Framework Planning and Installation Guide, Version 3.6.

You can install Manager for MQS on a TMR server and also on amanaged node that contains an MSMQ server. This enables Managerfor MQS commands and requests for information to be sent fromManager for MQS on the TMR server to the Manager for MQS on amanaged node. The following figure shows a typical Manager forMQS environment.

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

Version 1.02-2

Plan

nin

g an

d In

stallation

the Tivoli GEM console. The following figure shows a typicalManager for MQS environment with Tivoli GEM instrumentation.

For more information on which tasks are instrumented by TivoliGEM, see Chapter 9, “Tivoli GEM Instrumentation Tasks andMonitors” on page 9-1.

Where to Install Manager for MQSManager for MQS is always installed on the TMR server. Forinterconnected TMRs, Manager for MQS must be installed on all theTMRs.

Manager for MQS must also be installed on all managed nodes whereMSMQ is installed. It must be installed on all gateways that haveMSMQ running on Lightweight Client Framework/TivoliManagement Agent (LCF/TMA) endpoints or running on the gateway


Where to Install Manager for MQS

itself. The Discover task can be used to identify endpoints that haveMSMQ installed.

The following figure shows a network containing gateways andendpoints.

The following scenarios identify where Manager for MQS must beinstalled:

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

3. MSMQ is installed on Endpoint 1 and Endpoint 3.

■ Install Manager for MQS on Gateway 1 and Gateway 2.

Version 1.02-4

Plan

nin

g an

d In

stallation

Pre-Installation Considerations

Pre-Installation ConsiderationsBefore installing Manager for MQS, the following topics should beaddressed:

■ NT event adapter requirements■ Tivoli management region configuration■ Event server configuration■ Application Proxy availability

NT Event Adapter RequirementsThe MSMQ server issues event notifications to the Windows NTevent logs to describe events that affect MSMQ server resources.

The optional TEC product has an event adapter called the NT eventadapter. The NT event adapter reads events that are generated on aWindows NT system, formats them, and forwards them to an eventserver for further processing.

The Manager for MQS provides the configuration files and tasks thatcustomize the NT event adapter, event server, and TEC to processMSMQ server events.

The NT event adapter is packaged with the TEC product. It should beinstalled, configured, and operational on each MSMQ server-managednode or endpoint from which you want to receive events. This shouldbe done prior to running the task to configure the NT event adapteron the server. For more information, see Chapter 6, “ManagingMicrosoft Message Queue Events” on page 6-1.

Configuring Tivoli Management RegionsConfigure the TMRs to include MSMQ servers as managed nodesbefore installing the Manager for MQS.

Note: Resources must be shared on interconnected TMRs.


Pre-Installation Considerations

Configuring TEC Event ServersYou can configure an event server to automatically forward MSMQserver events to another event server. Configuring event servers inthis manner enables you to manage many MSMQ server managementservers from a single console, even if the management servers residein different TMRs.

For more information, see “Configuring the Event Server” onpage 6-2 and the TME 10 Enterprise Console User's Guide.

Application Proxy AvailabilityThe Application Proxy provides a common set of services that areused by Manager for MQS. If the Application Proxy has not beeninstalled (as part of another module), it must be installed beforeinstalling Manager for MQS. See “Installing the Application Proxy”on page 2-8 for installation instructions.

Installation OverviewYou 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 asdescribed on page 2-12.

■ By running the MSMQ Discover and Install tasks. TheDiscover task is provided to enable you to find which managednodes or endpoints have MSMQ installed. The Install task canthen use the output from the Discover task to install Managerfor MQS on only those nodes that have MSMQ installed. Touse this method, install Manager for MQS on the TMR serveronly. See “Using the Discover and Install Tasks” on page 2-13for more information about this method.

The install facility installs Manager for MQS and creates a Managerfor MQS icon on the desktop. The following table shows the locationof the installed components:

Version 1.02-6

Plan

nin

g an

d In

stallation

Installation Overview

To install Manager for MQS:

1. Install all prerequisite Tivoli software.

2. Install the Application Proxy if not already installed.

3. Backup the Tivoli database.

4. Install Manager for MQS on the TMR server and on the eventserver in your TMR.

Note: You must be logged in as a root administrator with atleast install_product authority to install Manager forMQS.

5. Install Manager for MQS on each managed node where theMSMQ server runs. If the MSMQ server is installed onendpoints, install Manager for MQS on the endpoint gateway.

6. Install the NT event adapter on each managed node andendpoint where the MSMQ server runs.

7. If you optionally manage MSMQ server resources with TivoliGEM, see Chapter 7, “Tivoli GEM Instrumentation” onpage 7-1 for installation requirements.

8. After installing Manager for MQS, backup the Tivoli database,saving the backup file with a different name from the previousbackup.

InstalledComponent

TMRServer

TECEventServer

ManagedNode

EndpointGateway Endpoint

Application Proxy √ √ √ √

Manager for MQS √ √ √ √

NT event adapter √ √


Installing the Application Proxy

Installing the Application ProxyIf the Application Proxy has not been installed (as part of anothermodule), it must be installed before installing Manager for MQS. Thefollowing sections describe the three methods that can be used toinstall the Application Proxy.

From the Desktop1. 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 Browserdialog. This dialog enables you to specify the path to theinstallation media.

3. Enter the full path to the Application Proxy in the Path Nametext field. The Application Proxy is located in the /applprxydirectory on the Manager for MQS CD-ROM.

4. Click the Set Path button. The File Browser dialog displays thecontents of the specified media in the Files scrolling list.

5. Click the Set Media & Close button. The File Browser dialogis closed, and the Install Product dialog is displayed withApplication Proxy 1.0 shown in the Select Product to Installscrolling list.

6. Select Application Proxy 1.0.

7. Select a target client on which to install the Application Proxyfrom the Available Clients scrolling list and then click the leftarrow button. The selected client is moved to the Clients toInstall On scrolling list.

8. Click the Install & Close button. The Product Install windowis displayed, listing the actions that will be taken when youcontinue the installation process.

9. Click the Continue Install button to begin the ApplicationProxy installation process OR click the Cancel button to stopthe process. When you elect to install, the Product Installwindow continues to display messages that show the progress of

Version 1.02-8

Plan

nin

g an

d In

stallation

Installing the Application Proxy

the installation. Successful installation is indicated by a Finished

product installation message.

10. Click the Close button to close the Product Install window.

Using the winstall CommandThe following is the syntax and parameters for the winstallcommand:

winstall -c cdrom_path\APPLPRXY -s tmr_server -i index_file -nmachine_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, APPLPRX.IND , from which theApplication Proxy is to be installed.

-n machine_name specifies the machine name on which theApplication Proxy is to be installed. The machine namecannot be a Tivoli Management Framework Version 3.6endpoint where an MSMQ server is installed; it should bethe endpoint gateway name.

Refer to the TME 10 Framework Reference Manual for moreinformation about the winstall command.

Using the Install TaskYou can also install the Application Proxy by using the Install task.See “Install Task” on page 2-14 for instructions.

Installing Manager for MQSThe following sections describe the three methods that can be used toinstall Manager for MQS. Each method can be used to installManager for MQS on the TMR server and, optionally, on anymanaged node. If the MSMQ server is installed on an endpoint, theManager for MQS should be installed on the endpoint gateway.


Installing Manager for MQS

From the Desktop1. From the menu bar, select Desktop → Install → Install

Product to display the Install Product dialog.


3. Enter the full path to the Manager for MQS in the Path Nametext field. This should normally be the path to the Manager forMQS CD-ROM.


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

Version 1.02-10

Plan

nin

g an

d In

stallation


■ Tivoli Manager for Message Queue Server■ Tivoli GEM instrumentation for Microsoft MSMQ Version

1.0■ Tivoli GEM instrumentation for Microsoft MSSQLServer

Version 6.5

6. Select Tivoli Manager for Message Queue Server.

Note: Install Manager for MQS before you install Tivoli GEMinstrumentation.

7. Select a target client on which to install Manager for MQS fromthe Available Clients scrolling list and then click the left arrowbutton. The selected client is moved to the Clients to InstallOn scrolling list.



Note: Install Manager for MQS on the TMR server, eachmanaged node where the MSMQ server is installed, onthe event server, and on the endpoint gateway.

8. Click the Install & Close button. The Product Install windowis displayed, listing the actions that will be taken when youcontinue the installation process.

9. Click the Continue Install button to begin the Manager forMQS installation process OR click the Cancel button to stop theprocess. When you elect to install, the Product Install windowcontinues to display messages that show the progress of theinstallation. 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 themenu bar. The desktop will display the Manager for MQS iconshown below.

Using the winstall CommandThe following is the syntax and parameters for the winstallcommand:

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 theManager for MQS is to be installed.

Version 1.02-12

Plan

nin

g an

d In

stallation


-n machine_name specifies the machine name on which Manager forMQS is to be installed. The machine name cannot be aTivoli Management Framework Version 3.6 endpointwhere an MSMQ server is installed; it should be theendpoint gateway name.

Refer to the TME 10 Framework Reference Manual for moreinformation about the winstall command.

Using the Discover and Install TasksYou can also install Manager for MQS by using the Discover andInstall tasks as described below. These tasks require at least themsmq_admin resource role.

Discover TaskThe Discover task can be run against any managed node or endpointto discover if MSMQ is installed on the node.

To run the Install task, a file with a list of endpoints (managed nodesor endpoints that are currently running the MSMQ server) is required.This file can be created manually or by running the Discover task.

To create the file manually, use any text editor to list the endpoints;specifying one endpoint, followed by (ManagedNode) or (Endpoint),per line.

To create the file with the Discover task, enable only the StandardOutput option in the Output Format section. No parameters arerequired. Run the task against all available endpoints. Using the Saveto File option of the output dialog, save the output to a file on theTMR server.

Notes:

1. The output will be appended to the file if it already exists.2. The generated file can be edited by the administrator.3. Comments (lines with a number sign (#) in column 1) are ignored

by the Install task.4. The type of endpoint must follow the name. The types are

(ManagedNode) and (Endpoint).



Install TaskRun the Install task on the TMR server by using the followingparameters:

■ CDROM Directory: location of the CD-ROM, for example, thelocation of the MSMQ.IND file

■ Endpoint Input File: use the endpoints list file created by theDiscover task.

Note: Ensure that the timeout parameter for the Install task is setsufficiently large because the runtime for this task is high.

Complete the installation by running the Configure task as describedin “Configure” on page 5-7.

Version 1.02-14

Gettin

g S

tarted

3Chapter 3. Getting Started withManager for Message QueueServer

This chapter describes how to configure Tivoli Manager for MessageQueue Server (Manager for MQS). The management tasks andprocedures used to configure Tivoli for a Microsoft Message Queue(MSMQ) server are also described.

Configuring Manager for MQSComplete the following steps to configure Manager for MQS:

1. Assign the Manager for MQS-specific authorization roles to oneor more Tivoli administrators as described on page 3-2.

2. If you are using the Tivoli Enterprise Console (TEC) product,configure event handling before using Manager for MQS:

a. Configure the event server as described on page 6-2.b. Configure the TEC as described on page 6-4.c. Configure the TEC event adapter for Windows NT (NT

event adapter) as described on page 6-5.

3. Configure Tivoli for an MSMQ server as described on page 3-3.


Assigning Authorization Roles

Assigning Authorization RolesWhen 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 theTivoli administrator that is running the task. In addition, some tasksrequire Tivoli authority as defined by TMR roles. A Tivoliadministrator must have the required authority and must have beenassigned one of the Manager for MQS resource roles to successfullyrun tasks and processes.

A Tivoli administrator with a TMR senior role, and preferably aTMR super role, must be given the new msmq_senior resource role.Tivoli administrators who do not require TMR senior and super rolesshould be assigned the msmq_admin resource role. Tasks thatrequire 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 themsmq_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 orresource roles depending on local authorization requirements. Exitand restart the desktop for the newly assigned roles to take effect.

Assigning TMR Roles to a Tivoli AdministratorTo assign the TMR senior and super roles to a Tivoli administrator:

1. From the desktop, double-click on the Administrators icon todisplay the Administrators window.

2. Right-click on the desired Administrator icon and select EditTMR Roles from the pop-up menu. The Set TMR Roles dialogis displayed.

Version 1.03-2

Gettin

g S

tarted

Assigning Authorization Roles

3. From the Available Roles scrolling list,

■ Select either or both of the senior or super roles.■ Move them to the Current Roles scrolling list by clicking

the left arrow button.

4. Click the Change and Close button.

5. Exit and restart the desktop.

Assigning Resource Roles to a Tivoli AdministratorTo add resource roles for a specific policy region to a Tivoliadministrator:

1. From the desktop, double-click on the Administrators icon todisplay the Administrators window.

2. Right-click on the desired Administrator icon and select EditResource Roles from the pop-up menu.

3. Select Manager for MQS from the Resources scrolling list.

4. From the Available Roles scrolling list,

■ Select either or both the msmq_admin or msmq_seniorroles.

■ Move them to the Current Roles scrolling list by clickingthe left arrow button.

5. Click the Change and Close button.

6. Exit and restart the desktop.

Managing Microsoft Message Queue ServersThe following steps describe the procedures to manage your MSMQenvironment with the Manager for MQS:

1. Create an MSMQ server instance on the desktop for eachMSMQ server. For more information, see “Creating MSMQServer Instances” on page 3-5.


Managing Microsoft Message Queue Servers

2. Ensure that the MSMQ server is a subscriber to the desiredprofile manager lists. For more information, see “MSMQ ServerLists” on page 3-11.

3. Select and change MSMQ monitors and then distribute themonitors to selected endpoints. For more information, seeChapter 4, “Monitoring Microsoft Message Queue Servers” onpage 4-1. You can then run any of the management tasks thatare described in Chapter 5, “Tasks to Manage MicrosoftMessage Queue Resources” on page 5-1.

MSMQ Server InstancesAn MSMQ server instance can be used as a task endpoint and as asubscriber to a profile manager. An MSMQ server instance appears inlists where endpoints are displayed.

For example, the new server instance name will appear in theAvailable to Become Subscribers list when looking at thesubscribers for a profile manager. The name of the server instance isthe name specified in the Server Alias Name field when the instancewas 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 instanceshould specify a target of the MSMQ endpoint instead of themanaged node.

Example 1: When the managed node is node1 and the server aliasname specified is also node1, the following two target endpoints willexist:

■ 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 MSMQserver instance and its managed node to the same list will cause theactions to be run twice.

Example 2: When the endpoint is node2 and the server alias namespecified is also node2, the following two target endpoints will exist:

Version 1.03-4

Gettin

g S

tarted


■ node2 (endpoint)■ node2 (MSMQ)

Creating MSMQ Server InstancesCreate an instance for each MSMQ server to be managed. Aninstance is represented as an icon in the Manager for MQS policyregion on the desktop. The status of the server is indicated by theicon. The icon also provides a list of tasks that can be performed.

You can create a MSMQ server instance in the following ways:

■ From the desktop.

■ From the command line. This can be useful when you havemany servers to create, and you want to specify information thatis used to create the instance. See Appendix A, “Command LineInterface Commands” on page A-1 for a description of thecommands that you can use to create, to display, and to updateMSMQ server instances.

■ By running the Configure task. This is useful to quicklypopulate the policy region with server instances. Defaultinformation obtained from the server is used. See “Configure”on page 5-7 for more information.

Creating an Instance from the DesktopTo create an instance from the desktop, follow these steps:

1. Double-click on the Manager for MQS icon to display thePolicy Region: Manager for MQS window.

2. From the menu bar, select Create → MSMQ to display theCreate an MSMQ Server dialog.



3. Complete the following text fields:

Server Alias Name

Name to be used for the server object and the labelfor the icon. The alias name does not have to matchthe actual server name. Valid characters for thisname include letters, numbers, spaces, andunderscores.

Note: If the NT monitors package is installed, youmay want the alias name to match the actualserver name. This may prevent NT monitorsfrom failing.

Managed Node Name

Name of an existing managed node where the serverresides. If you are creating an MSMQ server instanceon an endpoint, this can be the name of a managednode where the endpoint gateway resides for theendpoint.

Version 1.03-6

Gettin

g S

tarted


Endpoint Name

Enter the name of an existing endpoint where theserver resides.

MSMQ Server version

Version of the MSMQ server that this server isrunning. This value is used when subscribing theserver to the profile manager for that version.

Subscribe to the default profile manager?

Select YES and click the OK button to add theMSMQ server as a subscriber to the profile managerfor the version that is specified.

Results of Creating an MSMQ Server InstanceCreating an MSMQ server instance produces:

■ A server object with class MSMQ that you can use as the targetwhen running tasks and monitors against the server. For moreinformation, see “MSMQ Server Instances” on page 3-4.

■ An icon for the MSMQ server, identified by its alias name, inthe Policy Region: Manager for MQS window.



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

MSMQ Server Icon TasksThe pop-up task menu for an MSMQ server icon contains thefollowing selections:

Open

Displays the profiles which have been distributed to thisserver.

Properties

Displays the managed node name, endpoint name, MSMQserver version, and status of this server instance. Whenstarted, if the MSMQ server service is running, then thestatus will be set to running. If the service is down, thenthe status will be set to stopped. If unable to verify thestate of the service, then the status will be set to unknown.

Start Services

Runs the Start_Services task which starts the MSMQservice 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 MSMQservice and the DTC and Level 8 FalconMQ Bridge ifthey are installed.

Clear Alert

Resets the icon state. If running the MSMQ server statusmonitor, the monitor will turn the icon red when the serveris down. Clear Alert can reset the icon to a transparent

Version 1.03-8

Gettin

g S

tarted


background, which indicates that the server status isunknown.

Tasks → Display Server Info

Retrieves selected MSMQ data from the target server. See“MSMQ Server Tasks” on page 5-4 for the types ofinformation displayed.

Tasks → Display Server Status

Returns the status of all the installed MSMQ services onthe target server. Also returns the status of the DTC andLevel 8 FalconMQ Bridge if they are installed. See“MSMQ Server Tasks” on page 5-4 for the possible statusvalues.

Start Monitors

Starts all the MSMQ monitors on the server. This featureis not supported when the MSMQ server is on a TivoliManagement Framework, Version 3.6, Lightweight ClientFramework/Tivoli Management Agent (LCF/TMA)endpoint.

Stop Monitors

Stops all the MSMQ monitors on the server. This featureis not supported when the MSMQ server is on a TivoliManagement Framework, Version 3.6, LCF/TMAendpoint.

Start Event Adapter

Starts the TECNTAdapter event adapter service.

Stop Event Adapter

Stops the TECNTAdapter event adapter service.



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

Configure and distribute the MSMQ server status monitor for eachserver and specify that a TEC event is to be generated. This willensure that your server icons reflect the current status of the servers.The MSMQ server status monitor verifies the state of the MSMQserver service.

The server status is also updated when you:

■ Select Start Services or Stop Services from the pop-up menuof the MSMQ server icon.

■ Run the Start_Services or Stop_Services tasks.

Icon State Description

Displayed with a green background when theserver is active or running.

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

Displayed with a transparent backgroundwhen the server status is unknown. Theserver status is unknown if the state of theservices cannot be verified.

Deleting an MSMQ ServerDeleting an MSMQ server from a Manager for MQS policy regiondoes not affect the server itself, but does remove the serverinformation that is stored in the Tivoli database. Use the followingprocedure to delete an MSMQ server from the Manager for MQSpolicy region:

1. From the Policy Region: Manager for MQS window, selectthe desired MSMQ server icon.

Version 1.03-10

Gettin

g S

tarted


2. From the menu bar, select Edit → Delete to remove theselected MSMQ server from the policy region.

MSMQ Server ListsManager for MQS automatically creates several profile managers tohelp you group servers for management. Each profile manager has alist of subscribers that enables you to run tasks and monitors againsteach server in that list. The following profile managers are initiallycreated:

■ MSMQ 1.0 servers■ MSMQ monitors

Note: When you select the MSMQ servers that are to be added as asubscriber, ensure that you specify the MSMQ server instanceand not the managed node or endpoint. For more information,see “MSMQ Server Instances” on page 3-4.

Subscribing Servers to a Profile ManagerFollow these steps to subscribe servers to a profile manager:

1. Right-click on one of the profile managers and selectSubscribers from the pop-up menu.

2. Select the desired MSMQ server instances from the Availableto Become Subscribers scrolling list and move them to theCurrent Subscribers list by clicking the left arrow button.

3. Click Set Subscriptions & Close to subscribe the MSMQservers to the list.


Version 1.03-12

Mo

nito

ring

Messag

e Qu

eue S

ervers

4 Chapter 4. Monitoring MicrosoftMessage Queue Servers

This chapter explains how to customize and use Microsoft MessageQueue (MSMQ) monitors. The Tivoli Manager for Message QueueServer (Manager for MQS) provides several monitor collections toenable remote monitoring of:

■ MSMQ services■ Items added in the performance database■ Overall performance of MSMQ

Like any Tivoli Distributed Monitoring monitor, a MSMQ-specificmonitor can be customized. For example, you may want to add moremonitors to the default set. Additionally, you may want to set theseverity or threshold of the monitors. For additional information, seethe TME 10 Distributed Monitoring User's Guide.

Listing the MonitorsTo list the monitors that are provided by MSMQ:

1. From the desktop, double-click on the Manager for MQS icon.The Policy Region: Manager for MQS window is displayed.

2. Double-click on the MSMQ Monitors icon. The ProfileManager window is displayed.


Listing the Monitors

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

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

Version 1.04-2

Mo

nito

ring

Messag

e Qu

eue S

ervers


5. Select the monitoring collection for which you want to displaythe available monitors by selecting a collection name such asMSMQ in the Monitoring Collections scrolling list. Select themonitor you want to add, such as MSMQ IS , in the MonitoringSources scrolling list.

6. When the selected monitor requires an argument, a text field isdisplayed in the Monitor Arguments area of the window. Theargument can be entered either directly into the text field fromthe keyboard or by selecting it from a list. To display the list,click the button to the right of the text field and select theargument.

Note: When entering arguments directly from the keyboard,keep in mind that they are both space and case sensitive.

7. Click the Add Empty button to add the selected monitoringsource. The Edit Monitor dialog is displayed.



8. Enter the information in the Edit Monitor dialog's text fields,and then click the Change & Close button. The monitor isadded, and the TME 10 Distributed Monitoring ProfileProperties window is displayed.

9. To add another distributed monitoring monitor, repeat steps 4through 7. To close the TME 10 Distributed MonitoringProfile Properties window, select Profile → Close from themenu bar and click Save & Exit in the Confirm dialog.

10. After you have added and edited the desired monitors, distributethe profiles to begin monitoring. To distribute the monitorprofile:

Version 1.04-4

Mo

nito

ring

Messag

e Qu

eue S

ervers


a. Select the desired profile icon in the Profiles area of theProfile Manager window.

b. Drag the icon over the desired subscriber icon in theSubscribers area and drop the icon.

Understanding the MonitorsThe list of monitors includes:

■ Performance monitors■ Predefined monitors■ Additional MSMQ-specific monitors

Performance MonitorsManager for MQS supports all the performance counters that theMSMQ server provides. This enables you to monitor any of theavailable performance counters. For each of the monitoring sources inthe following list, you can select a specific performance counter froma list of valid choices. Some of the sources may also have an instanceargument that you can supply directly from the keyboard or selectfrom a list.

Manager for MQS provides performance monitors and counters forthe following MSMQ monitoring sources:

■ MSMQ IS

¹ Access to the server¹ Errors returned to Application¹ Replication requests received¹ Replication requests sent¹ Sync requests¹ Sync replies¹ Write requests sent

■ MSMQ Queue

¹ Bytes in Journal Queue¹ Bytes in Queue¹ Messages in Journal Queue


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 MSMQSession performance counters. Because the instances can be dynamic,these functions are provided in addition to the ability to monitor aspecific instance:

■ Sum of All Values■ Average of All Values■ Maximum of All Values

Predefined MonitorsSeveral monitors are added to the MSMQ; 1.0 distributed monitoringprofile. The additional monitors are:

■ MQ Server Status: used to update the state of the icon.

Version 1.04-6

Mo

nito

ring

Messag

e Qu

eue S

ervers


■ Generic Performance Monitor (process, % processor time,mqsvc) - displays the percentage of processor time that is usedby the MSMQ service.

■ Generic Performance Monitor (process, % processor time,q2qgw) - displays the percentage of processor time that is usedby the Level 8 FalconMQ Bridge.

■ Generic Performance Monitor (process, % processor time,msdtc) - displays the percentage of processor time that is usedby the Microsoft Distributed Transaction Coordinator (DTC).

Additional MSMQ-specific MonitorsOther MSMQ-specific monitors are:

■ Free Disk Space Available - returns the amount of availablespace, in megabytes, on the volumes that are used by theMSMQ server.

Parameters:

¹ StoreJournalPath¹ StoreLogPath¹ StorePersistentPath¹ StoreReliablePath

■ Disk Usage by MSMQ server - returns the number of megabytesused for an MSMQ server directory.

Parameters:

¹ StoreJournalPath¹ StoreLogPath¹ StorePersistentPath¹ StoreReliablePath

■ Event Adapter Status - returns up if the TEC event adapter forWindows NT (NT event adapter) service, TECNTAdapter, isrunning; otherwise returns down.

■ Generic Performance Monitor - Enables you to monitor anMSMQ performance counter by specifying the object, counter,and optionally, the instance for the performance counter.



Note: Specify arguments exactly as they are defined includingcapitalization 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 theselected 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:


■ MQ Server Status - checks the status of the MSMQ server.Returnsup 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 theEdit Monitor window for specific trigger conditions. A TECrule has been defined to update the icon state that is based onthe results of this monitor. See “Distributed Monitor (Sentry)Rules” on page B-5 for more information.

■ Distributed Transaction Coordinator Status - returns up if theDTC service is running; otherwise returns down.

■ FalconMQ Server Status - returns up if the Level 8 FalconMQBridge is running; otherwise returns down.

Version 1.04-8

Mo

nito

ring

Messag

e Qu

eue S

ervers


Default Settings for Monitor ResponsesSeveral monitors have default settings for monitor responses in theMSMQ;1.0 distributed monitoring profile. This allows users to enterthe requested monitor argument information (if any) and then toselect the Add With Defaults button. Default settings are providedfor the following monitors:

FalconMQ Server Status

Monitor Schedule Time: 10 minutesResponse Level: criticalTrigger when: down

MQ Test

Monitor Schedule Time: 30 minutesResponse Level: warningTrigger when: > 1000

Free Disk Space Available

Monitor Schedule Time: 360 minutesResponse Level: criticalTrigger when: < 1000000Response Level: warningTrigger when: < 20000000

For additional information on monitors, refer to the TME 10Distributed Monitoring Users Guide.

MSMQ Monitor TasksSpecial tasks are provided that can be started when a monitor hasreached a threshold.


MSMQ Monitor Tasks

Purge_Dead_LetterQThis 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 forlonger than the expiration time will be removed. The default settingis 1440 (24 hours).

Note: In order for this task to work, the ID tmersvrd must havepermissions to access the queue on the server. Use theMSMQ Explorer to give the tmersvrd read permissions.

Restart_ServicesThis task will stop or start MSMQ and the DTC and Level 8FalconMQ Bridge services if they are installed.

Parameters:

Stop RUNNING services - Select Yes or No. If you select Yes, allrunning services will be stopped and restarted. If you select No, allstopped services will be restarted.

Note: Distributed Monitoring tasks run under the tmersrvd user IDwhich must be a member of the Administrator's group.

Version 1.04-10

Usin

g T

asks and

Job

s

5Chapter 5. Tasks to ManageMicrosoft Message QueueResources

Tivoli Manager for Message Queue Server (Manager for MQS)includes a collection of tasks to help you perform functions that arerelated to managing Microsoft Message Queue (MSMQ) resources.Server tasks are contained within the server task library in theManager for MQS policy region and are described in “MSMQ ServerTasks” on page 5-4. Utility tasks can be started from the utility tasklibrary and are described in “MSMQ Utility Tasks” on page 5-7. SeeChapter 6, “Managing Microsoft Message Queue Events” onpage 6-1 for a description of the tasks contained within the TivoliEnterprise Console (TEC) task library.

Jobs are provided for many of the tasks. A job is a task withendpoints that are already defined.

When you start a task, you can specify the servers or other endpointson which to run the task. Some tasks are provided on the pop-upmenu for each server icon. Right-click on a server icon to display theicon’s pop-up menu. For more information, see “MSMQ Server IconTasks” on page 3-8.

Select Task Description from the pop-up menu to view informationabout the window’s text fields. For complete instructions on how touse tasks and jobs, refer to the Tivoli Management Framework User'sGuide.


Listing Tasks

Listing TasksTo list the tasks that are provided by Manager for MQS:

1. From the desktop, double-click on the Manager for MQS iconto display the Policy Region: Manager for MQS window.

2. To display the available MSMQ server tasks, double-click onthe MSMQ Server Tasks icon. The Task Library: ServerTasks window is displayed.

Running TasksTo run a task:

1. Double-click on the task icon and complete the displayedExecute Task dialog. See “MSMQ Server Instances” onpage 3-4 for more information about server instances.

Version 1.05-2

Usin

g T

asks and

Job

s

Running Tasks

2. Click the Execute & Dismiss button to start the task. AConfigure Task Arguments dialog, shown in the followingfigure, may display so that you can provide more informationfor the task. Not all tasks present this dialog. When a ConfigureTask Arguments dialog is presented, enter the information andthen click the Set & Execute button to start the task.


Running Tasks

A window showing the output from the task is displayed.

MSMQ Server TasksManager for MQS provides the following types of tasks for theMSMQ server:

Version 1.05-4

Usin

g T

asks and

Job

s

MSMQ Server Tasks

Type ofTask Task Role Target

Serverinformation

Display_Server_Status Display_Server_Info Display_MSMQ_Info Display_Instances

msmq_admin ormsmq_senior

MSMQserverinstance

Servermanagement

Start_Services Stop_Services Purge_Dead_LetterQ List_Dead_LetterQ

msmq_admin ormsmq_senior

MSMQserverinstance

Server Information TasksTasks that provide server information include:

■ Display_Server_Status - returns the status of all the installedMSMQ services on the target server. Also returns the status ofthe Distributed Transaction Coordinator (DTC) and Level 8FalconMQ Bridge, if they are installed. Some possible statusvalues are running and stopped.

■ Display_Server_Info - retrieves selected MSMQ data from thetarget server. The following information will be displayed:

¹ Environment

– Windows NT version– Windows NT CSD version– System root– Domain name

¹ MSMQ Server

– Version– Log directory– Journal directory– Persistent directory– Reliable directory– Falcon Bridge version (if Level 8 FalconMQ Bridge

is installed)


MSMQ Server Tasks

■ Display_MSMQ_Info - retrieves selected MSMQ data from thetarget 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 theMSMQ Queue and MSMQ Session performance monitors.

Note: Only those queues currently being monitored will bedisplayed.

Server Management TasksTasks that enable you to manage servers include:

■ Start_Services - starts the MSMQ service and the Level 8FalconMQ Bridge and DTC if they are installed.

■ Stop_Services - stops the MSMQ service and the Level 8FalconMQ Bridge and DTC if they are installed.

■ Purge_Dead_LetterQ - deletes all messages from the selectedqueue.

Parameters:

Select a queue:


Expiration Time (minutes) - Messages that have been in thequeue for longer than the expiration time will be removed. Thedefault setting is 1440 (24 hours).

Version 1.05-6

Usin

g T

asks and

Job

s

MSMQ Server Tasks

■ List_Dead_LetterQ - lists all the messages on the selectedqueue. The arrival time (in minutes) is displayed with themessage label.

Parameters:

Select a queue:


MSMQ Utility TasksManager for MQS provides utility tasks to help you manage MSMQservers running on your managed nodes. A resource role ofmsmq_admin or msmq_senior is required to perform these tasks.These tasks can be started from the MSMQ utility task library in theManager for MQS policy region on the desktop.

Task Target

Discover (see page 2-13) MSMQ server instance

Install (see page 2-14 ) MSMQ server instance

Configure MSMQ server instance

Start_Debugging MSMQ endpoint

Stop_Debugging MSMQ endpoint

Start_Monitors MSMQ endpoint

Stop_Monitors MSMQ endpoint

ConfigureFor each managed node it is run against, the Configure taskautomatically configures and creates an MSMQ server instance.When the managed node has the MSMQ server and Manager forMQS installed, the Configure task performs the following:

■ Retrieves the MSMQ server name and version.


MSMQ Utility Tasks

■ Creates an MSMQ server instance by using the server name asthe server alias name.

■ Creates an icon for the MSMQ server instance.

■ When you have specified that the instance should beautomatically subscribed to the default profile manager, it willadd the subscription to the profile manager for that version.

This task can initially populate the Manager for MQS policy regionwith server instances and can be run periodically to add new servers.See “Creating MSMQ Server Instances” on page 3-5 for moreinformation 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 beeninstalled on the managed node or gateway for an endpoint.

Start_DebuggingThis task turns on debug tracing for all the tasks and monitorsshipped with Manager for MQS, including Tivoli GEMinstrumentation tasks and monitors. A separate log file is written to atemporary directory for each task or monitor run while debug tracingis on. The directory is specified in the wtemp command. Tivoli GEMinstrumentation log files are located in thewtemp/GEM_Instrumentation_Logs directory.

This task helps to resolve problems when a task or monitor is notrunning properly.

Stop_DebuggingThis task turns off debug tracing for all the tasks and monitorsshipped with the Manager for MQS, including Tivoli GEMinstrumentation tasks and monitors.

Version 1.05-8

Usin

g T

asks and

Job

s

MSMQ Utility Tasks

Start_MonitorsThis task starts all the monitors from the MSMQ collection that havebeen distributed to the server. The task starts only the monitorinstances from this collection; other monitor instances on the serverare not started. This task can quickly restart all of the Manager forMQS monitors after they have been stopped.

Notes:

1. This task does not change the status settings for the monitors atthe Tivoli Management Region (TMR).

2. This task is not supported when the MSMQ server is on a TivoliManagement Framework, Version 3.6, Lightweight ClientFramework/Tivoli Management Agent (LCF/TMA) endpoint.

Stop_MonitorsThis task stops all the monitors from the MSMQ collection that havebeen distributed to the server. The task stops only the monitorinstances from this collection; other monitor instances on the serverare not stopped. This task can quickly stop all of the Manager forMQS monitors when a server is down.

Notes:

1. This task does not change the status settings for the monitors atthe TMR.

2. This task is not supported when the MSMQ server is on a TivoliManagement Framework, Version 3.6, (LCF/TMA) endpoint.


Version 1.05-10

Man

agin

g M

essage Q

ueu

e Even

ts

6 Chapter 6. Managing MicrosoftMessage Queue Events

The Microsoft Message Queue (MSMQ) server issues eventnotifications to describe events that affect MSMQ resources. TivoliManager for Message Queue Server (Manager for MQS) utilizes theTivoli Enterprise Console (TEC) event adapter for Windows NT (NTevent adapter) to convert MSMQ events to the TEC format. Managerfor MQS also provides a set of event classes that enable you to viewand work with these events at your TEC.

This chapter describes how to manage MSMQ events with tasks thatare contained in the TEC task library. An authorization role of senioror msmq_senior is required to run these tasks. The following tablelists the context and target node for the tasks:

To work with MSMQ events at your TEC, you must configure bothends of the connection and configure the TEC:

Task Target

Configure_Event_Server Event server

Configure_Event_Console Event server

Configure_Event_Adapter MSMQ server

Start_Event_Adapter MSMQ server instance

Stop_Event_Adapter MSMQ server instance


1. Configure the event server to recognize MSMQ events and theprocess rules concerning those events. Run theConfigure_Event_Server task against the event server to beconfigured.

2. Configure an event console. Run the Configure_Event_Consoletask to assign the newly created event group to the appropriateevent console. For more information, see “Configuring an EventConsole” on page 6-4.

3. Configure the NT event adapter for each MSMQ server toreceive its MSMQ events, convert them to the TEC format, andsend them to the event server. For more information, see“Configuring the NT Event Adapter” on page 6-5.

Configuring the Event ServerThe Configure_Event_Server task configures an event server forManager 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 TivoliManagement Region (TMR). When you have multiple TMRs, youmust configure at least one event server per TMR.

The Manager for MQS includes a set of event classes and rulesspecific to MSMQ. Events received from NT event adapters are

Version 1.06-2

Man

agin

g M

essage Q

ueu

e Even

ts

Configuring the Event Server

included in the MSMQ event group. To create this group and set upyour event server to process MSMQ events, you should follow thesteps in the next section.

Note: A Tivoli administrator with at least global senior authority isrequired to run the Configure_Event_Server task.

Procedure for Configuring the Event ServerPerform the following steps to configure an event server:

1. From the desktop, double-click on the Manager for MQS iconto display the Policy Region: Manager for MQS window.

2. Double-click the MSMQ TEC Tasks icon to display the TaskLibrary: TEC Tasks window.

3. Double-click on the Configure_Event_Server task icon andcomplete the displayed Execute Task dialog.

4. Click the Execute & Dismiss button to display theConfigure_Event_Server dialog.

5. Enter the name for the new or existing rule base in the New (orexisting) Rule Base Name field. The default name is MSMQ .


Configuring the Event Server

Note: You should not change the default rule base, so do notenterdefault 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 fieldblank. If you are creating a new rule base and you want to keepthe current information, enter the current rule base name. Thedefault value for this field is default.

7. Enter the path for the new rule base in the Path for new RuleBase (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, enterthe name of the managed node to which events should beforwarded in the Managed Node to Forward Events(Optional) field.

9. Click the Set and Execute button to start the task. TheConfigure Event Server Output window displays the job statusafter the task is completed.

Configuring an Event ConsoleThe Configure_Event_Console task adds filters to the TEC andassigns groups. You are prompted for the name of the event consoleto be configured. The name is the same name as the event consolethat already exists on the administrator’s desktop. This task should berun 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 eventsources.

Version 1.06-4

Man

agin

g M

essage Q

ueu

e Even

ts

Configuring an Event Console

Configuring the NT Event AdapterTo receive MSMQ events, ensure that the NT event adapter isinstalled and operational on each node where the MSMQ server isrunning. Complete the installation of the adapter before running thetask to configure the NT event adapter. The NT event adapter ispackaged with the Tivoli Enterprise Console product.


Configuring the NT Event Adapter

To configure the NT event adapter, run theConfigure_Event_Adapter task for the managed nodes where theNT event adapter has been installed. This enables the NT eventadapter for each MSMQ server to receive MSMQ events, convertthem to a TEC format, and send them to the event server. Runningthis task:

■ Merges the message queuing event format file definitions withthe existing NT event adapter format file. This is the file thatdefines the event format, event class, and the slot name and slotvalue pairs for each valid event. The message queuing eventformat file contains the definitions for the MSMQ events. Thefile'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 thechanges.

See the TME 10 Enterprise Console Adapter's Guide for moreinformation about the NT event adapter.

Starting and Stopping the NT Event AdapterManager for MQS supplies tasks to stop and start the NT eventadapter (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 AdapterManager for MQS provides the Event Adapter Status monitor tomonitor the status of the NT event log adapter.

Version 1.06-6

Man

agin

g M

essage Q

ueu

e Even

ts

Filtering Events

Filtering EventsMSMQ events regarded as harmless or unlikely to require action canbe suppressed from displaying on the TEC. The Tivoli ManagementFramework provides the following methods for you to filter outevents that you do not want to see:

■ You can specify that the event is not to be forwarded from themanaged node to the event server. In this case, you specify filtercriteria in the NT event adapter configuration file. Filter criteriaincludes information about which events should be sent to theevent server. Depending on the frequency of the harmlessevents, this option can save you some network traffic. The useof this file is described in the TME 10 Enterprise ConsoleAdapter's Guide.

■ You can create new rules to exclude the event. When you dothis, the event will be forwarded to the event server, but will beeliminated by the rules engine. The TME 10 Enterprise ConsoleRule Builder's Guidedescribes the steps for building andchanging rules.

■ You can exclude classes of events using the event console’s userinterface. Refer to the TME 10 Enterprise Console User's Guidefor information.


Version 1.06-8

GE

M In

strum

entatio

n In

stallation

7 Chapter 7. Tivoli GEMInstrumentation

To manage Microsoft Message Queue (MSMQ) servers from theTivoli Global Enterprise Manager (Tivoli GEM) console, you mustinstall:

1. Tivoli Manager for Message Queue Server (Manager for MQS)

2. Tivoli GEM instrumentation for Tivoli Manager for MessageQueue Server (Tivoli GEM instrumentation)

This chapter provides an overview of Tivoli GEM instrumentation. Italso describes the installation prerequisites and the steps to installTivoli GEM instrumentation.

Tivoli GEM defines the concept of a business system to organizerelated applications. Tivoli GEM consists of a Tivoli GEM server thatruns as an application on a managed node and a Tivoli GEM consolerunning as a Java-based client. Tivoli GEM uses applicationinstrumentation to get the necessary data to display and manipulatebusiness systems such as MSMQ.

Tivoli GEM instrumentation enables you to graphically monitor andcontrol MSMQ server resources that reside on a Tivoli managednode. This concept is illustrated in the following figure:


Understanding the Tivoli GEM ServerThe Tivoli GEM server interacts with instrumented applications suchas the Manager for MQS to provide information for display on theTivoli GEM console. The Tivoli GEM server is the recipient ofheartbeat events from instrumented application components anddetermines the business system to which a component belongs. TheTivoli GEM server also queries instrumented applications for relatedcomponents and the status of their monitors. This information createsand maintains a view of each business system's configuration and itsavailability.

Version 1.07-2

GE

M In

strum

entatio

n In

stallation

Understanding the Tivoli GEM Server

The Tivoli GEM server furnishes the Tivoli GEM console with a setof tasks that are applicable against a component. These tasks appearin context-sensitive menus on the Tivoli GEM console. The TivoliGEM server also stores files on behalf of the Tivoli GEM console,including icons, backgrounds, help files, log files, customizationviews, and settings.

Understanding the Tivoli GEM ConsoleThe Tivoli GEM console graphically displays the business systeminformation from the Tivoli GEM server. The Tivoli GEM console:

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

As the Tivoli GEM server receives status updates pertaining to thebusiness systems, it updates the Tivoli GEM console, enabling you toview the real-time status of the business system.

Tivoli GEM supports aggregation, which is a logical grouping ofinstances of the same or different component types. Tivoli GEMsupports automatic aggregation as well as manual aggregation.Automatic aggregation is accomplished by the definition ofcomponent information tasks. Manual aggregation is accomplished byusers dragging and dropping icons into aggregates which they define.

Tivoli GEM Instrumentation Event HandlingTivoli GEM Event Enablement must be installed and configured onthe event server in order for Tivoli GEM events to be supported bythe Tivoli Enterprise Console (TEC). The Tivoli GEM EventEnablement configuration includes defining the APM_HEARTBEAT,APM_THRESHOLD, and APM_CONNECTION_CHANGE eventclasses to TEC and defining the Tivoli GEM servers to which theTivoli GEM events will be forwarded.

Tivoli GEM instrumentation also includes TEC rules that forward allManager for MQS monitor events to the Tivoli GEM server. The


Tivoli GEM Instrumentation Event Handling

gemmsmq rules must be defined in the current rule base. The MSMQConfigure_Event_Server task can be used to add the gemmsmqrules to the current rule base. See Appendix B, “Event Classes andRules” on page B-1 for more information about event classes andrules.

The Tivoli GEM server discovers the MSMQ components on receiptof heartbeat events. As the Tivoli GEM server receives monitor andstatus updates for the MSMQ business system, it updates the TivoliGEM console.

Instrumented ComponentsTivoli GEM instrumentation includes instrumentation for twocomponents:

■ MSMQ server■ MSSQLServer (Microsoft SQL Server)

Tivoli GEM supports aggregation, which is a logical grouping ofinstances of the same or different component types. Tivoli GEMinstrumentation provides for the automatic aggregation of all MSMQserver and MSSQLServer component instances based on theenterprise and site to which they belong. Each of the componentinstances will be automatically aggregated based on the enterprise andsite in which it belongs. Thus the initial top-level view on the TivoliGEM console will show enterprise container icons. Aggregates aredepicted on the Tivoli GEM console view with a plus sign by theiricon. Double-clicking an enterprise container icon will produce aview with the contained site container icons. Double-clicking a sitecontainer icon will produce a view with the contained MSMQ serverand MSSQLServer component instances within that site. Theinstrumented aggregation is predefined in business system component,business system mapping, and software component description filesthat must be installed on the Tivoli GEM server.

Component information tasks are required to support automaticaggregation. The Display_Enterprise and Display_Site tasks arecomponent information tasks that have been defined for eachcomponent. These tasks return the enterprise name and site name for

Version 1.07-4

GE

M In

strum

entatio

n In

stallation

Instrumented Components

each component instance in a specific Application ManagementSpecification (AMS)-defined format. The instrumentation alsosupports a two-way connection between the MSMQ component andthe MSSQLServer component. There is only one MSMQ server and,at most, one MSSQLServer database on each target endpoint. TheTivoli GEM console will draw a line connecting each MSMQ icon toits associated MSSQLServer icon if the MSSQLServer exists. Theinstrumented connection is defined in the business system mappingand software component description files.

The Discover_Connections task, which is defined for the MSMQserver component, returns the identification of the MSSQLServercomponent to which the MSMQ server is connected. If theMSSQLServer does not exist on the target endpoint, then noconnection is returned. The MSSQLServer is always identified by thehost name on which it resides.

Instrumentation Files, Libraries, and ProfilesSuccessful installation of Tivoli GEM instrumentation creates tasklibraries, monitor collections, and file packages. The following is anoverview of the resulting desktop structure:


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 theMSMQ resources exist in order to have the instrumentation codeavailable for local implementation.

TasksThe Tivoli GEM server furnishes the Tivoli GEM console with a setof tasks that are applicable against a component. The task menuappears on the console when a component icon is highlighted and theright-mouse button is clicked. The tasks enable Tivoli GEM users toperform actions on the component instance and have the task resultsreturned to the Tivoli GEM console. The tasks that are supported foreach component are defined in business system mapping and software

Version 1.07-6

GE

M In

strum

entatio

n In

stallation

Tasks

component definition files that reside on the Tivoli GEM server.Installation of the Tivoli GEM instrumentation creates a task libraryfor the MSMQ server and MSSQLServer instrumented components.Each task library contains the tasks that are supported from TivoliGEM for that component. See “MSMQ Server Component Tasks” onpage 9-2 for a list of Tivoli GEM instrumentation tasks.

MonitorsThe Tivoli GEM console displays an icon for each monitor instancethat is supported. If a monitor supports multiple arguments, then eachargument (or combination of arguments) defines an instance. Themonitor instance icon changes to a color that is based on the severityof the monitor events that are required for that monitor. See“Monitors” on page 9-8 for a list of supported monitors.

Preparing to Install Tivoli GEMInstrumentation

Review the topics in the following sections before installing TivoliGEM instrumentation.

Tivoli Management RegionsTivoli Management Regions (TMRs) should be properly configuredbefore installing Tivoli GEM instrumentation.

AdministratorsTivoli administrators need the following authorization roles:

■ To install Tivoli GEM instrumentation, at least install_productauthority is required.

■ To start tasks from the Tivoli GEM console, msmq_admin andmsmq_senior authority is required for the user ID that you useto log on to the Tivoli GEM console.

■ To run tasks and monitors to be forwarded to the Tivoli GEMserver and the Tivoli GEM console, Login Name is required.


Preparing to Install Tivoli GEM Instrumentation

Login Name is the user ID that you use to log on to the MSMQmanaged nodes and the Tivoli GEM server-managed nodes.

Installation PrerequisitesBefore installing Tivoli GEM instrumentation, perform the followingsteps:

■ Ensure that all prerequisite software is installed and that you arerunning on a supported operating system. Refer to the TivoliGlobal Enterprise Manager Release Notesfor details aboutsupported hardware and operating systems, prerequisite software,and disk space requirements.

■ Manager for MQS and the TEC must be installed andconfigured before installing Tivoli GEM instrumentation. SeeChapter 2, “Planning for and Installing Manager for MessageQueue Server” on page 2-1.

■ Install the Tivoli GEM server.

■ Install and configure Tivoli GEM Event Enablement on theevent server so that the Tivoli GEM event classes are defined tothe TEC and the events will be forwarded to the Tivoli GEMserver.

■ Install the Tivoli GEM console.

Installing and Configuring Tivoli GEMInstrumentation Components

The following table shows the location of the installed components:

Version 1.07-8

GE

M In

strum

entatio

n In

stallation

Installing and Configuring Tivoli GEM Instrumentation Components

To install Tivoli GEM instrumentation, follow the steps in theremaining sections of this chapter.

InstalledComponent

Target Nodes

TivoliGEMServer

TMRServer

ManagedNodes

Endpoint

Java DevelopmentKit (JDK) 1.1.x

√ √ √

Instrumentation BDF,CDF, and icon files

√

Instrumentation tasklibraries, monitorcollections

√

Manager for MQS √ √ √

Instrumentation filepackages

1 1

1 Tivoli GEM instrumentation is installed in one location and distributed tomanaged nodes and Lightweight Client Framework/Tivoli Management Agent(LCF/TMA) endpoints.

Copying BDF, CDF, and Icon FilesCopy the Tivoli GEM business description files (BDFs), componentdescription files (CDFs), and icon files from the Manager for MQSCD-ROM to the Tivoli GEM server.

For more information on these files and their destination directories,see Appendix C, “Business and Component Descriptions” onpage C-1.

Installing the Java Development KitInstall the Java Development Kit (JDK) on the TMR server and allendpoints and managed nodes where Tivoli GEM instrumentation willbe used. Do not install the Java Runtime Environment. To use JDK,you must set PATH and CLASSPATH environment variables on allsystems that have Tivoli GEM instrumentation.

To install the JDK, perform the following steps:



1. Back up the Tivoli database.

2. Set the PATH and CLASSPATH variables:

a. Add the JDK bin directory to the PATH variable, forexample: PATH=....;\jdk1.1.6\bin.

Note: jdk1.1.6 is the directory where JDK is installed. Itmay be different on your machine.

b. Add the JDK classes.zip to the CLASSPATH variable, forexample: CLASSPATH=\jdk1.1.6\lib\classes.zip.

c. On Windows NT platforms, you can use the control panelto set the Path and CLASSPATH variables. Note thatthese variables are case sensitive.

3. For more information and access to JDK, point your browser tohttp://java.sun.com.

4. Stop and restart the Tivoli GEM server to incorporate thechanges.

See the Tivoli Manager for Message Queue Server Release Notes formore information about supported levels of JDK.

Creating User Groups and Logon IDs for the TivoliGEM Console

To log on to the Tivoli GEM console, the user ID and password mustbe defined on the managed node where the Tivoli GEM server isrunning.

The Tivoli GEM console logon ID will be rejected unless it belongsto either the tsadmn (administrator) or tsuser (user) groups.

■ If the ID belongs to the administrator group, you can log onwith administrator access.

■ If the ID belongs to the user group, you cannot log on withadministrator access.

Version 1.07-10

GE

M In

strum

entatio

n In

stallation


Windows NTUse the User Manager applet to create the group or groups, then addthe logon ID or IDs that will be used to sign on.

AIXAdd the logon ID or IDs to the appropriate group or groups usingSMIT → Security & Users → Groups → Change/ShowCharacteristics of a Group.

SUN SolarisUse the admintool command to add the logon ID or IDs that will beused to sign onto the server.

Setting Security for the Windows NT Operating SystemIf you are using Windows NT, additional security configuration stepsare required; no additional security configuration is required forUNIX platforms.

Add the following user rights to the user ID under which the TivoliGEM server will run so that it will do the following:

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

Follow these instructions to set user rights:

1. Log on to an ID with administrator authority.

2. Click on Start→ Programs → Administrative Tools → UserManager (or User Manager for Domains for NT servers).

3. Click on Policies → User Rights.

4. Check the Show Advanced User Rights check box.

5. Scroll through the Right list and select Act as part of theoperating system.



6. The Grant to list displays groups and users that are currentlygranted this right. If your target user ID is not listed, click onAdd.

7. Click on Show Users.

8. Select the target user ID under which the Tivoli GEM serverwill 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, repeatthis process for Log on as a service.

11. Log off and log back on as the target ID for the user rights totake effect.

Installing Tivoli GEM InstrumentationTivoli GEM instrumentation is installed in thePR_MSMQ_Default_hostname-region policy region which is withinthe Applications_hostname-region on the desktop.

Install Tivoli GEM instrumentation (task libraries and monitorcollections) 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 displaythe Install Product dialog.


4. Enter the full path to the Tivoli GEM instrumentationinstallation files in the Path Name text field. This shouldnormally be the path to the Manager for MQS CD-ROM.


6. Click the Set Media & Close button. The Install Productdialog is displayed with the following products listed in theSelect Product to Install scrolling list:

Version 1.07-12

GE

M In

strum

entatio

n In

stallation


■ Tivoli Manager for Message Queue Server■ Tivoli GEM Instrumentation for Microsoft MSMQ Version

1.0■ Tivoli GEM Instrumentation for Microsoft MSSQLServer

Version 6.5

7. Select Tivoli GEM Instrumentation for Microsoft MSMQVersion 1.0.

8. Click the targets on which to install Tivoli GEM instrumentationfrom the Available Clients scrolling list and click the left arrowbutton. The selections are listed in the Clients to Install Onscrolling list.



Note: Tivoli GEM instrumentation must be installed on theTMR server.

9. Click the Install & Close button. The Product Install windowis displayed, listing the actions that will be taken when youcomplete the installation process.

10. Click the Continue Install button to begin the Tivoli GEMinstrumentation installation process OR click the Cancel buttonto stop the process. When you elect to install, the ProductInstall window continues to display messages that show theprogress of the installation. Successful installation is indicatedby a Finished product installation message.

11. Click the Close button.

12. Repeat steps 5 through 9 to install Tivoli GEM instrumentationfor Microsoft MSSQLServer Version 6.5.

13. After installing Tivoli GEM instrumentation, backup the Tivolidatabase.

After installation, Tivoli GEM instrumentation profile manager andtask library icons appear in the Policy Region:PR_MSMQ_Default_tjevans-region window.

Version 1.07-14

GE

M In

strum

entatio

n In

stallation



Version 1.07-16

GE

M In

strum

entatio

n In

itialization

8Chapter 8. Initializing Tivoli GEMInstrumentation

This chapter describes the following steps that you must performbefore you can use Tivoli GEM instrumentation for Tivoli Managerfor Message Queue Server (Tivoli GEM instrumentation):

1. Ensure that administrators are assigned the appropriateauthorization roles and login IDs.

2. Configure Microsoft Message Queue (MSMQ) servers on thedesktop using the Configure task. See “Configuring MSMQServers” on page 8-2.

3. Distribute the Tivoli GEM instrumentation file packages. See“Subscribing to and Distributing the File Packages” onpage 8-2.

4. To discover MSMQ server resources on the Tivoli GEMconsole, distribute the heartbeat monitors to the Tivoli targetendpoints on which the MSMQ resources exist. See“Subscribing to and Distributing the Heartbeat Monitor” onpage 8-2.

This chapter also describes how to confirm Tivoli GEM discovery ofMSMQ servers.


Configuring MSMQ Servers

Configuring MSMQ ServersBefore doing Tivoli GEM instrumentation activities, run theConfigure task from the Utility task library on the desktop to ensureconfiguration of all MSMQ servers.

Subscribing to and Distributing the FilePackages

Distribute the following Tivoli GEM instrumentation file packages tothe Tivoli managed nodes that run MSMQ server resources:

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

If MSMQ server resources run on the TMR server, then distribute thefile packages to the TMR server.

Note: File packages are distributed to the managed nodes andendpoints where the monitors are distributed to the MSMQendpoint. If the monitors are not distributed to the MSMQendpoint, some monitors will not run correctly.

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

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

Subscribing to and Distributing theHeartbeat Monitor

After you distribute the Tivoli GEM instrumentation file packages,distribute the heartbeat monitor and other monitors to all endpointsand managed nodes running MSMQ server. If MSMQ serverresources run on the TMR server, then distribute the heartbeat

Version 1.08-2

GE

M In

strum

entatio

n In

itialization

Subscribing to and Distributing the Heartbeat Monitor

monitor to the TMR server. Tivoli GEM receives monitor statusthrough TEC events that are forwarded to the Tivoli GEM server.

The heartbeat monitor is added to the following profiles:

To enable a heartbeat monitor for each MSMQ server andMSSQLServer, distribute the profiles that are listed above to theMSMQ endpoints.

To subscribe and distribute the MSMQ server profiles to the MSMQendpoints, do the following:

1. Double-click the desired profile manager icon to display aProfile Manager window as shown below:

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



a. From the Profile Manager pull-down menu, selectSubscribers.

b. Ensure that your MSMQ endpoints are in the CurrentSubscribers list. Otherwise, select your target instancesfrom the Available to become Subscribers scrolling listand 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, selectDistribute .

Version 1.08-4

GE

M In

strum

entatio

n In

itialization


3. Select Distribute Now from the pop-up menu. The profile isdistributed.

Confirming Resource DiscoveryObserve the active Tivoli GEM console to ensure that MSMQ serverand MSSQLServer icons are displayed as they are discovered.

The heartbeat monitor for MSMQ servers and MSSQLServers sends aheartbeat event for each MSMQ server resource at an interval that isspecified by the previously distributed heartbeat monitor. When theevent server receives a heartbeat event, it forwards the event to theTivoli GEM server, and an icon is displayed on the Tivoli GEMconsole.


Version 1.08-6

Instru

men

tation

Tasks an

d M

on

itors

9 Chapter 9. Tivoli GEMInstrumentation Tasks andMonitors

After you have successfully discovered Microsoft Message Queue(MSMQ) servers and MSSQLServers, you can use tasks and monitorsto manage your MSMQ servers from the Tivoli GEM console. Thischapter describes Tivoli GEM instrumentation tasks and monitors.

Locating and Running TasksTivoli GEM instrumentation tasks, in addition to Tivoli Manager forMessage Queue Server (Manager for MQS) tasks, are contained inthe PR_MSMQ_Default_hostname-region andPR_MSMQ_Default_hostname-region_Endpoint described in“Instrumentation Files, Libraries, and Profiles” on page 7-5. On theTivoli GEM console, you can run instrumented tasks from theMSMQ server and MSSQLServer icon's pop-up menu.

Tivoli GEM Instrumentation TasksIt is recommended that the Tivoli GEM instrumentation tasks be runfrom the Tivoli GEM console. When the Tivoli GEM instrumentationtasks are run from the desktop, the Instance_ID parameter mustalways be entered.

To specify the Instance_ID for each task, enter the identifier of eithera MSMQ server or MSSQLServer value in the following format:


Locating and Running Tasks

MSMQ server: SINGLE_LOCAL_INSTANCE MSSQLServer:SINGLE_LOCAL_INSTANCE

Note: The Manager for MQS tasks that are supported by TivoliGEM do not require the Instance_ID parameter.

MSMQ Server Component TasksTivoli GEM instrumentation provides tasks on the pop-up menuavailable from each MSMQ server icon on the Tivoli GEM console.The following Tivoli GEM instrumentation tasks are supported byTivoli GEM for the MSMQ server component:

■ Discover_Connections - reports the current connection aMSMQ server has with a MSSQLServer database.

■ Display_Enterprise - returns the enterprise name in which theMSMQ server resides.

■ Display_Site - returns the site name in which the MSMQ serverresides.

■ Query_State - reports whether the MSMQ server is running,stopped, or uninstalled.

■ Query_Threshold_Settings - lists the current thresholdsassociated with a particular monitor.

■ Query_Thresholds - generates threshold events for the specifiedmonitor.

■ Query_Values - reports the current values of the specifiedmonitor.

■ Set_Polling_Interval - adjusts the frequency with which thespecified monitor runs.

■ Set_Pulse - adjusts the frequency at which the heartbeat monitorruns.

■ Set_Thresholds - establishes thresholds for the specifiedmonitor.

The following subset of Manager for MQS tasks are also supportedby Tivoli GEM for the MSMQ server component:

Version 1.09-2

Instru

men

tation

Tasks an

d M

on

itors


■ 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

See Chapter 5, “Tasks to Manage Microsoft Message QueueResources” on page 5-1 for more information about these tasks.

MSSQLServer Component TasksTivoli GEM instrumentation provides the following tasks on thepop-up menu available from the MSSQLServer icon on the TivoliGEM console:

■ Display_Enterprise - returns the enterprise name in which theassociated MSSQLServer resides.

■ Display_Site - returns the site name in which the associatedMSSQLServer resides.

■ Query_State - reports whether the MSSQLServer is running,stopped, or uninstalled.

■ Query_Threshold_Settings - lists the current thresholdsassociated with a particular monitor.

■ Query_Thresholds - generates threshold events for the specifiedmonitor.

■ Query_Values - reports the current values of the specifiedmonitor.

■ Set_Polling_Interval - adjusts the frequency with which thespecified monitor runs.



■ Set_Pulse - adjusts the frequency at which the heartbeat monitorruns.

■ Set_Thresholds - establishes thresholds for the specifiedmonitor.

■ Start - starts the MSSQLServer database.

■ Stop - stops the MSSQLServer database.

Understanding MSMQ Server Aggregate ResourcesIcons representing aggregates of MSMQ server resources areautomatically provided. An aggregate enterprise icon is thehighest-level aggregate resource.

Double-click any aggregate enterprise icon to display the aggregatesite icons.

Double-click an aggregate site icon to display the MSMQ server andMSSQLServer icons.

When resources are not aggregated, the task may have timed out.You can also manually aggregate resources. Right-click on a resourceicon and select Add to Aggregate. Select the aggregate to which youwish to add the resource.

Note: If the MSMQ server is a router, then the icons will not beaggregated because the site and enterprise cannot bedetermined.

Navigating to MSMQ Server ResourcesOn the Tivoli GEM console, you navigate from an aggregateenterprise icon to a specific MSMQ server and MSSQLServer icon.Right-click individual MSMQ server resources to access the pop-upmenu from which you can select tasks and monitors.

To locate a specific MSMQ server resource:

1. Display the Tivoli GEM Console.

Version 1.09-4

Instru

men

tation

Tasks an

d M

on

itors


2. Double-click the Middleware/DB icon shown in the tree view.

The GEM Manager for MQS window is displayed showing aMiddleware/DB tree view containing enterprise aggregates asshown below. If the view is empty, ensure that you havedistributed a profile that contains the heartbeat monitor toMSMQ server resources and that the MSMQ server andMSSQLServer are installed. For more information ondistributing the heartbeat monitor, see “Subscribing to andDistributing the Heartbeat Monitor” on page 8-2.



3. Display the Middleware/DB aggregates by clicking on the boxcontaining the + to the left of the icon.

4. To view MSMQ resources, double-click an aggregate icon suchas Manager for MQS.

The GEM - msmq_enterprise window is displayed containingan aggregate site icon such as msmq_site_new.

5. Double-click the aggregate site icon to view the MSMQ serverand MSSQLServer icons in the GEM - msmq_site_newwindow.

Version 1.09-6

Instru

men

tation

Tasks an

d M

on

itors


Using the Tear-Away LogBefore starting a task, open the tear-away log provided by the TivoliGEM console. The log provides current messages that show theprogress of tasks you run. Do the following:

1. From the Tivoli GEM console menu bar, select Options.2. Click the Tear Away Log button.

Starting a Sample TaskTo perform a task such as starting a queue manager:

1. Right-click an MSMQ server icon. On the pop-up menu, selectStart Server.

2. The GEM Log window provides a progress report listing ofMSMQ server operations as they complete. In this example, themessages indicate that the MSMQ server has started.



MonitorsTivoli GEM Instrumentation provides support for MSMQ server andMSSQLServer monitors.

MSMQ Server MonitorsTivoli GEM Instrumentation installs new monitor collections(MSMQ_ and MSSQLServer_) and also provides support for allManager for MQS-specific monitors. For more information onMSMQ server monitors, see Chapter 4, “Monitoring MicrosoftMessage Queue Servers” on page 4-1.

Topology views on the Tivoli GEM console display status for thefollowing events:

■ Tivoli GEM-specific Tivoli Enterprise Console (TEC) events,such as a heartbeat event

■ Threshold events showing status, such as the MQ Server Statusmonitor event sent by Manager for MQS-specific monitors.

Version 1.09-8

Instru

men

tation

Tasks an

d M

on

itors

Monitors

Heartbeat MonitorTivoli GEM instrumentation provides the heartbeat monitor todiscover MSMQ servers. Use the profile manager to distribute theheartbeat monitor.

After distribution, the heartbeat monitor issues anAPM_HEARTBEAT event, at the specified interval, to the eventserver. The event server logs the heartbeat event and forwards theevent to the Tivoli GEM server. The Tivoli GEM server discoversMSMQ server resources on receipt of a heartbeat event.

State MonitorThe state monitor monitors the status of the MSMQ server. Bydefault, the state monitor is defined to issue a normalAPM_THRESHOLD event when the application comes up and a fatalAPM_THRESHOLD event when the application goes down. Theevent server logs the threshold event, forwards the event to the TivoliGEM server, and the monitor icon changes color.

Manager for MQS-Supported MonitorsThe following Manager for MQS monitors are also supported byTivoli GEM for the MSMQ server component:

■ Event Adapter Status■ MQ Server Status■ FalconMQ Server Status■ Distributed Transaction Coordinator Status■ Free Disk Space Available■ Disk Usage by MSMQ Server■ MSMQ IS■ MSMQ Queue■ MSMQ Service■ MSMQ Session■ MQ Test■ Special Queue Count■ Special Queue Maximum Time

See “Understanding the Monitors” on page 4-5 for a description ofthese monitors.


Monitors

MSSQLServer Monitors

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

State MonitorThe state monitor monitors the status of the database. By default, thestate monitor is defined to issue a normal APM_THRESHOLD eventwhen the database comes up and a fatal APM_THRESHOLD eventwhen the database goes down. The event server logs the thresholdevent and forwards the event to the Tivoli GEM server. The TivoliGEM console changes the color of the state monitor icon dependingon the status of the APM_THRESHOLD event generated by the statemonitor.

Monitor OperabilityUse the profile manager to distribute these monitors. You can useeither the profile manager or the Set_Polling_Interval task to set themonitoring schedule for each monitor. You can use either the profilemanager or the Set_Thresholds task to set the thresholds for eachmonitor.

Tivoli GEM instrumentation includes a TEC rules which will forwardall Manager for MQS monitor events to the Tivoli GEM server.When any of the above monitors specify that a TEC event be sentwhen a threshold is exceeded, that monitor event will be forwarded tothe Tivoli GEM server from the TEC. The Tivoli GEM consoledisplays an icon for each monitor instance that is supported. If amonitor supports multiple arguments, then each argument (orcombination of arguments) defines an instance.

Version 1.09-10

Instru

men

tation

Tasks an

d M

on

itors

Monitors

Viewing Monitor StatusTo view the status of Manager for MQS monitors that are supportedby Tivoli GEM on the Tivoli GEM console, do the following:

Double-click an icon for a specific MSMQ server resource to displaya detailed view of monitors and their status as shown in the windowbelow. From the menu bar, select View → Show as Details.


Monitors

Version 1.09-12

Co

mm

and

Lin

e Interface C

om

man

ds

A Appendix A. Command LineInterface Commands

Tivoli Manager for Message Queue Server (Manager for MQS)provides several commands that enable you to create, to change, andto view the attributes of Microsoft Message Queue (MSMQ) serverinstances from a command line.

The following table lists the commands and their purpose:

A description of each command follows.

NAME: wcrtmsmq

PURPOSE: This command creates a MSMQ server instance in thespecified policy region. The arguments associated with the commandenable you to set the initial properties of the server. This command isuseful if you have several servers to manage and do not want toindividually create them from the desktop. You can create a shellscript to call the wcrtmsmq command.

Command Purpose

wcrtmsmq Creates a MSMQ server instance

wgetmsmq Lists the attribute values of the specified MSMQ serverinstance

wsetmsmq Sets the attribute values of the specified MSMQ serverinstance

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

Note: This command does not automatically subscribe the serverinstance to a profile manager; use the Tivoli wsub commandto do this. See the Tivoli Management Framework User'sGuide for more information about the wsub command.

SYNOPSIS: wcrtmsmq –a server_alias –p policy-region –hmanaged_node –e endpoint –v { 10 }

DESCRIPTION:

Authorization: msmq_senior or msmq_admin

Arguments:

–a server_aliasSpecifies the alias name of the MSMQ server instance.

–p policy-regionSpecifies the name of the policy region in which to createthe MSMQ server instance.

–h managed_nodeSpecifies the managed node on which the MSMQ serverresides.

–e endpointSpecifies the endpoint on which the MSMQ serverresides.

–v { 10 } Specifies the version of the MSMQ server.

SEE ALSO: wsetmsmq, wgetmsmq

NAME: wgetmsmq

PURPOSE: This command shows the attributes of an MSMQserver instance.

SYNOPSIS: wgetmsmq [–a] [–h] [–e] [–v] msmq_server_alias

DESCRIPTION:


Arguments:

Version 1.0A-2

Co

mm

and

Lin

e Interface C

om

man

ds

–a Displays the server alias name of the MSMQ serverinstance.

–h Displays the managed node name of the MSMQ serverinstance.

–e Displays the endpoint name of the MSMQ serverinstance.

–v Displays the version of the MSMQ server instance.

msmq_server_aliasThe current server alias of the MSMQ server.

SEE ALSO: wcrtmsmq, wsetmsmq

NAME: wsetmsmq

PURPOSE: This command updates a MSMQ server instance.

SYNOPSIS: wsetmsmq –a new_server_alias msmq_server_alias

DESCRIPTION:


Arguments:

–a new_server_aliasSpecifies the new alias name of the MSMQ serverinstance.

msmq_server_aliasThe current server alias of the MSMQ server.

SEE ALSO: wcrtmsmq, wgetmsmq

Tivoli Manager for Message Queue Server: User’s Guide A-3

Version 1.0A-4

Even

t Classes an

d R

ules

BAppendix B. Event Classes andRules

This appendix contains a list of the event classes and rules that theTivoli Manager for Message Queue Server (Manager for MQS)defines.

Manager for Message Queue Server EventClasses

Message queue server events can be received from Tivoli DistributedMonitoring monitors, or from the NT event adapter that forwardsevents that the Microsoft Message Queue (MSMQ) server applicationgenerates to the Tivoli Enterprise Console (TEC).

Distributed Monitoring EventsMSMQ_Monitors is a superclass definition for all MSMQ monitorevents. The classes in the following table inherit from theMSMQ_Monitors superclass, and correspond to the distributedmonitoring monitor names:

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

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 Coordinatorstatus

MSMQ_dtcup

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 EventsMSMQ_Event is a superclass definition for all MSMQ events that areforwarded from the NT event adapter on the managed node.

When the NT event adapter receives an event that is generated by theMSMQ server application, it maps fields in the MSMQ-generatedevent to TEC slots.

Version 1.0B-2

Even

t Classes an

d R

ules


The following is an example of an MSMQ TEC event:

NT Event Fields TEC Slots

Date + Time date (date+time)

User sub-origin

Computer host name

Origin origin

Event ID id

Source sub-source

Type

■ Error■ Information■ Warning

severity

■ CRITICAL■ HARMLESS■ WARNING

Category category

Message msg

System identifier (SID) sid

- source (MSMQ)



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 QueueServer Events

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

Version 1.0B-4

Even

t Classes an

d R

ules

Rules for Manager for Message Queue Server Events

Console Rule Builder's Guidefor more information on how to use theTEC graphical rule editor.

NT Event Adapter RulesThe msmq_events.rls file contains a set of rules for theMSMQ_Event class of events that are sent from the NT eventadapter. This rule set uses the classes from the msmq_events.barocfile.

The event processing rules that are provided with the Manager forMQS are:

Rule Name Description

dup_msmqRemoves duplicate MSMQ events.

timeharmless_msmqSets a timer on each harmless event to 15minutes. A timer rule will close the event whenthe timer expires.

timer_ruleCloses harmless events after 15 minutes.

Distributed Monitor (Sentry) RulesThe msmq_monitors.rls file contains a set of rules for theMSMQ_monitors class of events that are sent from the monitors. Thisrule set uses the classes from the msmq_monitors.baroc file.

The event processing rules that are provided with the Manager forMQS are:

Rule Name Description

dup_monitor_msmqRemoves duplicate MSMQ monitor events.

timeharmless_monitor_msmqSets a timer on each harmless event to 15minutes. A timer rule closes the event when thetimer expires.


Rules for Manager for Message Queue Server Events

closeharmless_monitor_msmqCloses harmless events after 15 minutes.

A sample rule is provided to show how to run a task from a monitorTEC event. This rule is in the msmq_monitors.rls file, but iscommented out.

Tivoli GEM Instrumentation Distributed Monitoring(SENTRY) Rules

The gemmsmq.rls file contains fourteen gemmsmq rules for theMSMQ_Monitors class of events that are sent from the monitors. Thegemmsmq rules forward all MSMQ monitor events to the TivoliGEM server.

The TME 10 Enterprise Console Rule Builder’s Guidedescribes thesteps for building and changing rules.

Version 1.0B-6

Bu

siness an

d C

om

po

nen

t Descrip

tion

s

C Appendix C. Business andComponent Descriptions

This appendix describes the Tivoli GEM business description files(BDFs) and component description files (CDFs) that are provided forTivoli Manager for Message Queue Server (Manager for MQS).

Tivoli GEM defines the concept of a business system to organizerelated applications. A business system includes all the applicationsthat together perform a business function, such as message queueprocessing. It also includes performance measures that determinewhether the business system is functioning properly.

For example, a Microsoft Message Queue (MSMQ) server businesssystem would include all the instances of MSMQ server resourcesand their associated MSSQLServer resources that are used in yournetwork. The business system includes descriptions of:

■ Tasks that can initiate actions against an MSMQ server resourcecomponent

■ Monitors that collect status information on an MSMQ serverresource component

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

Installing BDF, CDF, and Icon Files

Installing BDF, CDF, and Icon FilesYou can install the BDF, CDF, and icon files by doing one of thefollowing:

■

1. Copy the BDFs and CDFs in the /GEMFILES directoryon the Manager for MQS CD-ROM to the followingdirectories 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 onthe Manager for MQS CD-ROM to the followingdirectories 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 serverparses the new BDFs and CDFs, obtaining the MSMQbusiness views, tasks, and monitor descriptions. Errormessages appear in the%BINDIR%\TDS\server\log\ihsmessage.log file on theTivoli GEM server.

■ If this is a new installation, the BDF, CDF, and icon files maybe installed by loading the provided amp file as follows:

1. At the Tivoli GEM console, select File → Load NewAMP .

2. Select the /GEMFILES/msmq.pkg amp file.

Business and Component Description FilesTivoli GEM instrumentation provides the following businessdescription files and the following component description files:

■ Manager for MQS: Managerfor1_0Tivol.bsdf

Version 1.0C-2

Bu

siness an

d C

om

po

nen

t Descrip

tion

s

Business and Component Description Files

■ MSMQ System Business System Component:MSMQsystem1_0Microso.bcdf

■ MSMQ Business System Mapping files for MSMQ servers andMSSQLServer databases:

¹ MSMQ1_0Microsoft.bmdf¹ MSSQLServer6_5Micros.bmdf

■ MSMQ Software Component files for MSMQ servers andMSSQLServer databases:

¹ MSMQ1_0Microsoft.cdf¹ MSSQLServer6_5Micros.cdf

■ MSMQ Global Description File: MSMQ1_0Microsoft.gdf

The business description files must be copied into the followingdirectories on the Tivoli GEM server:

■ %BINDIR%\TDS\server\db\current\appdefs■ %BINDIR%\TDS\server\db\backup\appdefs

Icon FilesThe icon files include the following:

16_enterprise.gif and 32_enterprise.gifEnterprise aggregate icon

16_site.gif and 32_site.gifSite aggregate icon

16_msmq.gif and 32_msmq.gifMSMQ server icon

The icon files must be copied into the following directories on theTivoli GEM server:

■ %BINDIR%\TDS\server\db\current\icons■ %BINDIR%\TDS\server\db\backup\icons

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

Version 1.0C-4

GE

M In

strum

entatio

n T

ask Descrip

tion

s

D Appendix D. Tivoli GEMInstrumentation TaskDescriptions

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

Task Description and Parameters

Query_State Returns up, down, or gone, indicating whether the MSMQ serverresource is running, is down, or has been deleted.

Parameters:

Instance_ID

SINGLE_LOCAL_INSTANCE

Query_Thresholds Gets the last threshold levels for the specified monitor. It then placesthe last threshold levels in the value fields of anAPM_THRESHOLD event and sends that event. This task can berun by right-clicking on the selected monitor shown in the detailedmonitor view.

Parameters:

Instance_ID


MonitorNameThe name of the monitor that you want to query.

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


Query_Threshold_Settings

Lists the current thresholds associated with a specified monitor.

Parameters:

Instance_ID



Query_Values Returns the last threshold value for the specified event. Thisincludes manufacturer, product, version number, hostname, InternetProtocol (IP) address, MSMQ server resource ID such as host name,and monitor values. This task can be run by right-clicking on theselected monitor shown in the detailed monitor view.

Parameters:

Instance_ID



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 shownin the detailed monitor view.

Parameters:

Instance_ID



IntervalHow often the monitor is run in minutes; in an integer such as60.

Version 1.0D-2

GE

M In

strum

entatio

n T

ask Descrip

tion

s


Set_Thresholds Defines the circumstances under which threshold events are sent toTivoli GEM by the event server. Sets the VALUE, OPERATOR,and SEVERITY in the monitor. This task can be run byright-clicking on the selected monitor shown in the detailed monitorview.

Parameters:

VALUEThe new value you want to set as the operator threshold.

OPERATORThe specific conditions that trigger response-level actions, suchas:

0 >1 >=2 <3 <=4 =5 not equal6 changes to7 changes from8 crosses above9 crosses below10 matches11 does not match

SEVERITYThe severity level of the monitor response that will be sentwhen the threshold condition is met.

0 normal1 informational2 warning3 severe4 critical5 fatal



Set_Thresholds(continued)

Instance_ID



ThresholdDefinitionVALUE,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 fromthe screen, and select the Operator from a pop-up menu.You must also enter a Value.

Start Starts the MSSQLServer database.

Parameters:

Instance_ID


Stop Stops the MSSQLServer database.

Parameters:

Instance_ID


Set Pulse Sets the polling interval for the heartbeat monitor.

Parameters:

Instance_ID


Discover_ Connections Only for MSMQ servers, returns the MSSQLServer that is aprerequisite for MSMQ.

Parameters:

primary_handle<hostname>

secondary_handleSINGLE_LOCAL_INSTANCE

Connection_Type = MSSQL_DBThe defined connection is of type MESSAGE.

Connection_Direction = 33 indicates a 2–way connection.

Version 1.0D-4

GE

M In

strum

entatio

n T

ask Descrip

tion

s


Display_Site Returns the site name in which the associated MSMQ server resides.This task is not supported on MSMQ routers.

Parameters:



Display_Enterprise Returns the enterprise name in which the associated MSMQ serverresides. This task is not supported on MSMQ routers.

Parameters:



Notes:

1. The Instance_ID parameter, which identifies the server, isrequired when you run Tivoli GEM instrumentation tasks fromthe desktop.

2. The Instance_ID parameter is not required when you run TivoliGEM instrumentation tasks from the MSMQ server icon's pop-upmenu on the Tivoli GEM console.

3. Manager for MQS tasks that are supported by Tivoli GEM do notrequire the Instance_ID parameter.

Several Tivoli GEM instrumentation tasks require a Monitor Nameparameter. The parameter must be entered in the following format:MonitorName, parm1,parm2

where:

MonitorName - the name of the monitor that you want to query. Thisparameter is case sensitive. MonitorName must be followed with acomma and a space when you specify parm1.


parm1 - case sensitive and must be enclosed in double-quotes if itcontains spaces. When you specify parm2, parm1 must be followedby 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

Version 1.0D-6

GE

M In

strum

entatio

n T

ask Descrip

tion

s

Parameters:¹ 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,@>¹

■ MSMQ Service

Parameters:¹ 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

Parameters:¹ Incoming Bytes,@+¹ Incoming Bytes,@#¹ Incoming Bytes,@>¹ Incoming Bytes/Sec,@+¹ Incoming Bytes/Sec,@#¹ Incoming Bytes/Sec,@>¹ Incoming Messages,@+¹ Incoming Messages,@#¹ Incoming Messages,@>


¹ 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

Version 1.0D-8

Instru

men

ting

Co

nn

ection

Su

pp

ort

E Appendix E. InstrumentingConnection Support to MSMQ

To instrument products that provide connections to MSMQ, youimplement the relation in your component instrumentation. Thefollowing description provides only the values required for the JavaRelation class. For more information, refer to the Tivoli GlobalEnterprise Manager Instrumentation Guide.

To create a relation, do the following:

Define a Relation ("MSMQ", Communication[], direction)

where:

MSMQ is the communication type

direction is:

1 = → origin2 = ← destination3 = ←→ conversational

Communication array is defined as:

[0] Hostname:<hostname>, MSMQ:SINGLE_LOCAL_INSTANCE

or

[1] TCP/IP Address, MSMQ:SINGLE_LOCAL_INSTANCE

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

Version 1.0E-2

Fin

din

g an

d C

orrectin

g P

rob

lems

F Appendix F. Finding andCorrecting Problems

Problems that you may encounter while using the Tivoli Manager forMessage Queue Server (Manager for MQS) to manage a MicrosoftMessage Queue (MSMQ) installation can have many different causessuch as:

■ Machine or server availability■ Targeting miscues■ Operating system environment■ MSMQ server installation■ Manager for MQS configuration

This appendix covers some of the troubleshooting problems byanswering your questions.

Installation HintsIs there anything I should verify prior to installation to preparefor the Manager for MQS?

These guidelines may help prevent difficulties when installing andconfiguring the Manager for MQS:

What to do:

Test Distributed Monitoring (Sentry), Software Distribution (Courier)(if using Tivoli GEM instrumentation), and the NT event adaptersbefore installing Manager for MQS. This is especially important if

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

Installation Hints

you are installing Manager for MQS on a new Tivoli installation.Manager for MQS uses these core applications; if they are notworking, Manager for MQS will not work either. At a minimum, youshould be able to do the following:

■ Start a simple task. If you have TEC, then the easiest thing todo is to start one of the tasks in the TEC library.

■ Deploy some distributed monitoring monitors on the MSMQserver 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 andthat 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 readyto install the Manager for MQS.

■ Backup your database on each machine where Manager forMQS will be installed.

■ Install the Manager for MQS.

■ Backup your database on each machine where Manager forMQS was installed.

■ Optionally, install Tivoli GEM instrumentation.

■ Backup your database on each machine where Tivoli GEMinstrumentation was installed.

Note:

After the files are loaded onto the system from the installationmedia, an installation program is run to create the Managerfor MQS policy region, MSMQ object class, tasks, jobs, androles. The installation program creates a log file that is named%TMP%\msmq_init.log . %TMP% is the directory that ispointed to by the wtemp command.

If the log file does not exist, the problem originated prior tostarting the installation program. In this case, after the

Version 1.0F-2

Fin

din

g an

d C

orrectin

g P

rob

lems

Installation Hints

problem has been corrected, reinstall the product from theinstallation media.

If the log file does exist, the installation program was started.Review the log file to determine the cause of the problem.The installation program can be run more than once. Whenthe problem is resolved, run the installation program that islocated in%BINDIR%\..\generic_unix\TME\MSMQ\msmq.init fromthe command line. You do not need to restore the backup ofthe Tivoli database.

Hints on Using Tasks and Jobs from theDesktop

The following information may help you solve problems encounteredusing 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 starttasks. When you run a job and an empty window is displayed, the jobwas run against a nonexistent endpoint. The typical cause of thiserror is that a job is run against a profile manager endpoint and theprofile manager does not have any subscribers. Therefore, the job isnot run against any node.

What to do:

■ MSMQ servers that are to be managed should be added assubscribers to the appropriate profile manager. The typicalscenario should be to:

¹ Add an instance of the server on the desktop, creating anicon and a Tivoli object.

¹ Ensure that the newly created endpoint, server alias name(MSMQ), is added to the appropriate subscriber list.

¹ Rerun the job.


Hints on Using Tasks and Jobs from the Desktop

■ Run the task directly (instead of the job) and specify theappropriate endpoints.

Why does a task fail with a permissions error?

<server> (MSMQ): The task failed to execute. <server> (MSMQ):<date>: 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 ormsmq_admin (or both) to the administrator that runs the task.See “Assigning Authorization Roles” on page 3-2 for moreinformation.

2. After the resource roles have been assigned, stop and thenrestart the desktop so that the assigned roles will take effect.

Hints on Running Tasks from the Tivoli GEMConsole

The following information may help you solve problems encounteredusing tasks from the Tivoli GEM console.

Why does a task fail with a permission error, such as:Areference 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 inthe same TMR or in connected TMRs with shared resources.

■ To verify connected TMRs from the desktop, selectDesktop → TMR Connections → List Connections toview current connections.

■ To verify shared resources from the desktop, selectDesktop → TMR Connections → Update Resources.This enables you to view available resources for remoteTMRs and to select resources to update for sharing.

Version 1.0F-4

Fin

din

g an

d C

orrectin

g P

rob

lems

Hints on Running Tasks from the Tivoli GEM Console

2. Redistribute the heartbeat monitor, with a revised monitoringschedule of 10 minutes, to all MSMQ servers. This will ensurethat all current MSMQ servers are discovered and that allMSMQ servers that were removed are deleted from the TivoliGEM console. Reopen the Tivoli GEM client to view currentMSMQ servers.

Hints on Using MonitorsWhy are my monitors not running?

What to do:

If monitors do not seem to be running, do the following:

■ Ensure that Distributed Monitoring has been installed on themanaged node.

■ Ensure that monitors are defined and enabled within the profile.

■ Ensure that you distributed the monitors to the subscriber list.

1. Open the PM_MSMQ_1.0. and PM_MSSQLServer_6.5.profile managers.

2. Select each profile collection.

3. Right-click and select Edit Properties from the pop-upmenu.

4. From the Profile pull-down menu, select DistributionDefaults. Ensure that the Distribute to ALL Levels ofSubscribers and Make subscribers’ profile an EXACTCOPY of this profile checkboxes have been selected.

■ Turn on debugging and check the monitor logs as follows:

1. Run the Start_Debugging task.

2. Look in the monitor log that is located in the%DBDIR%\tmp\GEM_instrumentation_logs directory todetermine the problem.

Why is a non-MSMQ monitor not working?


Hints on Using Monitors

What to do:

1. Verify that a monitor is running:

■ Specify the following on the Edit Sentry Monitorwindow:

¹ 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 tothe managed node. On the Distribute Profile window,ensure that the Make subscribers’ profile an EXACTCOPY of this profile checkbox is selected.

■ Check the SentryStatus Notice Group to see if there havebeen problems in distributing the monitor.

2. When a pop-up dialog is displayed approximately every 5minutes, then the monitor is running. Note that it may take afew minutes for the monitor to start running.

Why aren’t the statuses of Manager for MQS monitors that aresupported on the Tivoli GEM console displayed?

What to do:

1. Verify that the Manager for MQS monitor has been distributedto the MSMQ server managed node and that a monitor responsehas been defined that sends a TEC event.

2. Verify that the APM_THRESHOLD and the MSMQ_Monitorsclasses have been defined for the event server.

3. Verify that the gemmsmq.rls and the interapp.rls rule baseshave been installed on the event server. These rule bases enablethe Manager for MQS monitor events to be displayed on theTEC and forwarded to the Tivoli GEM server:

a. Enter the wlscurrb command to display the name of theactive rule base.

b. Enter the wlsrbclass active_rulebase_name command tolist the defined event classes. Ensure that the

Version 1.0F-6

Fin

din

g an

d C

orrectin

g P

rob

lems

Hints on Using Monitors

APM_THRESHOLD and MSMQ_Monitors classes aredefined.

c. Enter the wlsrbrules active_rulebase_name command tolist the defined rules. Ensure that the gemmsmq.rls andinterapp.rls rule bases are defined.

d. When the needed classes or rules are not defined, run theConfigure_Event_Server task to define the classes andthe rules.

4. Verify that Manager for MQS monitor events are reaching theTEC. If Manager for MQS monitor events are not displayed onthe TEC, do the following:

a. Run the wtdumprl command on the event server

b. Look for errors associated with the MSMQ_Monitorsevents

5. Verify that Manager for MQS monitor events are getting to theTivoli GEM server.

a. Ensure that the Tivoli GEM server was started with thetserver start -b command and option to enable debuggingand to have events logged to the Tivoli GEM server log.

b. Look in the %BINDIR%\TDS\server\log\ihsmessage.logfile to see if the Tivoli GEM server is receiving thethreshold events.

c. When the TEC is receiving Manager for MQS monitorevents but the Tivoli GEM server is not, ensure that theTEC is configured to send events to the Tivoli GEMserver. Refer to the Tivoli Global Enterprise ManagerUser's Guide.


Hints on Using the TEC

Hints on Using the TECWhy 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 theendpoint?

– Ensure that the TECNTAdapter service is running.

– Ensure that the ServerLocation value is set to thecorrect event server name. This field is set in thetecad_nt.conf file (on the TEC 2.6 NT adapter thefile name is tecad_nt.con).

– When running the TEC 3.1 NT event adapter, use thepostemsg utility to send a message to the eventserver. On the server, enter the wtdumprl commandto see if the message was sent. This verifies that thecommunication between the adapter and the server isoperational.

¹ Ensure that the NT event log is not full. When the eventlog is full, no new events will be written to the log.Therefore, the adapter will not be receiving new events toforward to the event server.

■ Event Server

¹ Ensure that the event server is operational.

¹ Ensure that Manager for MQS classes and rules areinstalled and configured on the event server.

1. Enter the wlscurrb command to display the name ofthe active rule base.

2. Enter the wlsrbclass active_rulebase_name commandto list the defined event classes. Ensure that the

Version 1.0F-8

Fin

din

g an

d C

orrectin

g P

rob

lems


MSMQ_Event and MSMQ_Monitors classes aredefined. If Tivoli GEM instrumentation is installed,ensure that the APM_HEARTBEAT andAPM_THRESHOLD classes are also defined.

3. Enter the wlsrbrules active_rulebase_name commandto list the defined rules. Ensure that themsmq_events.rls and the msmq_monitors.rls rulebases are defined. If Tivoli GEM instrumentation isinstalled, ensure that the interapp.rls andgemmsmq.rls rule bases are also defined.

4. If the required Manager for MQS classes or rules arenot defined, run the Configure_Event_Server task todefine the classes and the rules.

5. If the Tivoli GEM enablement classes and rules arenot defined, configure Tivoli GEM EventEnablement.

¹ Check to see if the events are being received at the eventserver.

– Enter the wtdumprl command on the event server todisplay the events in the reception log on the eventserver.

– When the events are not in the list, see the previousinformation for the MSMQ server endpoint in thissection.

¹ The events are being received, but have a parsing_failed

message.

– If the MSMQ events are coming over as classNT_Base, then the Configure_Event_Adapter taskhas not been run. This task loads the definitions forthe MSMQ events into the NT event adapter.

– If the MSMQ events are coming over as classMSMQ_Event but still are not being processed, thenthe Configure_Event_Server task has not been run.



This task loads the definitions for the MSMQ eventsinto the event server.

¹ The events are being received and are processed.

Check the Event Groups that have been assigned to theTEC. If the MSMQ Event Group is not listed, then theconsole has not been set up to display the MSMQ events.Run the Configure_Event_Console task to assign theevent group to the TEC. This can also be done manuallyfrom the desktop interface.

Hints on Using the Tivoli GEM ConsoleWhy isn’t an MSMQ server icon displayed on the Tivoli GEMconsole?

What to do:

■ Verify that the Tivoli GEM business description files (BDFs)and the component description files (CDFs) have been installedin the %BINDIR%\TDS\server\db\current\appdefs directoryon the Tivoli GEM server. Stop and restart the Tivoli GEMserver so that the server parses the BDFs and CDFs. SeeAppendix C, “Business and Component Descriptions” onpage C-1.

Note: After you stop the Tivoli GEM server, you may want todelete the ihserror.log and ihsmessage.log files in the%BINDIR%\TDS\server\log directory. This enablesyou to see only new messages regarding the Tivoli GEMserver when you restart it. You may also want to deletethe files in the%BINDIR%\TDS\server\db\backup\datab and%BINDIR%\TDS\server\db\current\datab directoriesto refresh the topology database and rediscover allMSMQ server and MSSQLServer components.

■ Verify that the heartbeat monitor has been distributed to theMSMQ server instances.

Version 1.0F-10

Fin

din

g an

d C

orrectin

g P

rob

lems

Hints on Using the Tivoli GEM Console

1. Select the PM_MSMQ_1.0. and PM_MSSQLServer_6.5.profile collections.

2. Right-click and select Edit Properties from the pop-upmenu.

3. From the Profile pull-down menu, select DistributionDefaults. Ensure that the Distribute to ALL Levels ofSubscribers and Make subscribers’ profile an EXACTCOPY of this profile checkboxes are selected.

4. Ensure that the heartbeat monitor is enabled and definedwith a monitoring schedule of 10 minutes for the initialMSMQ server discovery.

5. Select each managed node where an MSMQ server exists.

6. Right-click and select Subscribers from the pop-up menu.

7. Ensure that the Current Subscribers list includes MSMQserver managed nodes. If the list does not include thesemanaged nodes, do the following:

a. Select the MSMQ server managed nodes from theAvailable Subscribers list.

b. Move them to the Current Subscribers list.

c. Select Set Subscriptions & Close.

8. Select a profile collection and drag and drop it to thecorresponding subscriber to distribute the profile.

■ Run the Query_State task to verify that the MSMQ server isrunning.

■ Verify that the Tivoli GEM TEC classes and rules are installed:

1. Enter the wlscurrb command to display the name of theactive rule base.

2. Enter the wlsrbclass active_rulebase_name command tolist the defined event classes. Ensure that theAPM_HEARTBEAT and the APM_THRESHOLD classesare defined.



3. Enter the wlsrbrules active_rulebase_name command tolist the defined rule bases. Ensure that the interapp.rls rulebase is defined because this rule base forwardsAPM_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 theTEC:

1. Enter the wtdumprl command on the event server.

2. wtdumprl will display the events in the reception log onthe event server.

3. Look for errors associated with the APM_HEARTBEATevent.

■ Check the ihsttec.cfg file in the%BINDIR%\TDS\EventService directory to verify that theTEC event server has been configured to send events to theTivoli GEM server.

■ Verify that the APM_HEARTBEAT event is getting to theTivoli GEM server.

1. Start the Tivoli GEM server with the tserver start -bcommand and option to log events to the Tivoli GEMserver log.

2. Look in the %BINDIR%\TDS\server\log\ihsmessage.logfile to see if the Tivoli GEM server is receiving theheartbeat events.

3. When the TEC is receiving the APM_HEARTBEAT andAPM_THRESHOLD events but the Tivoli GEM server isnot, ensure that the TEC is configured to send events tothe Tivoli GEM server. Refer to the Tivoli GlobalEnterprise Manager User's Guide.

■ Turn on Tivoli GEM instrumentation debugging and look forerrors in the heartbeat log:

Version 1.0F-12

Fin

din

g an

d C

orrectin

g P

rob

lems


1. Run the Start_Debugging task.

2. Look in the MSMQ_heartbeat.log file that is located inthe %DBDIR%\tmp\GEM_Instrumentation_logsdirectory for errors.

Icon StateWhy did the MSMQ server or MSSQLServer icon not aggregate?

What to do:

1. If the MSMQ server is a router, then dumpis will not returnenterprise and site names. Thus the user must manuallyaggregate the icons by enterprise and site name.

2. The component information tasks timed-out due to high systemactivity. Manually aggregate the icons or rerun the heartbeatwhen the system is not as busy so that automatic aggregationcan take place.

Why is the icon color wrong?

The icon color is updated when the server status monitor sends aTEC event. The monitor should always trigger an event for each ofthe four trigger conditions.

What to do:

■ Ensure that the monitor has been enabled and has beendistributed.

■ Ensure that the event server is running.

■ If you ran the Stop_Monitors task, then run theStart_Monitors task to restart the server status monitor.


Helpful Debugging Information

Helpful Debugging InformationThis 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 thatproduces the output. All other tasks and monitors will write output toseparate log files if the Start_Debugging task has been run. Forexample:

■ 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 dataon 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 forinformation on setting debug flags.

Successful installation of Tivoli GEM instrumentation creates tasklibraries, monitor collections, and file packages. Installedinstrumentation 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 onwhich the MSMQ resources exist in order to have the instrumentationcode available for local processing. The successful distribution of thefile packages cause the instrumentation code to be installed in the%BINDIR%\..\generic_unix\TME\GEM\Microsoft\MSMQ\V1_0_\ Microsoft directory.

Version 1.0F-14

Fin

din

g an

d C

orrectin

g P

rob

lems

Tivoli GEM Server Database Corruption

Tivoli GEM Server Database CorruptionThe Tivoli GEM databases are damaged or I want to refresh theTivoli GEM console.

What to do:

1. Stop the Tivoli GEM server.

2. Erase all files in the current%BINDIR%\TDS\server\db\backup\datab and%BINDIR%\TDS\server\db\current\datab directories. Do notdelete the directories.

3. Restart the Tivoli GEM server. This automatically copies thedatabases from the default databases to the current databases.

Scheduling MonitorsTo avoid overloading event servers, use care when you adjustschedules for Tivoli GEM instrumentation monitors. Factors toconsider include:

■ 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 orderto avoid an overload condition. For more information onadjusting the monitoring schedule of a profile, refer to the TME10 Distributed Monitoring User's Guide.

Product NotesThis section contains important information about distribution, tasks,monitors, and the desktop.


Product Notes

Task NotesThe following notes clarify the use of tasks with Manager for MQS:

■ When running the Configure task against more than oneendpoint, 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 wasno data that met the criteria, an empty list will be displayed.

■ If the Configure_Event_Console task was not run against theevent 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 filenamed %TMP%\msmq_config_evtsvr.log, where %TMP% isthe directory pointed to by the wtemp command. If anyproblems are encountered when running this task, review the logto help determine the problem. This task can be run more thanonce without having to restore the Tivoli database. Therefore, ifyou encounter a problem, rerun the task. If you specify a rulebase name that exists, then it will be updated. If the Managerfor MQS baroc files and rules have been loaded, theConfigure_Event_Server task will delete and reload them topick up any changes.

Monitor NotesWhen you enter arguments for monitors manually, it is important thatyou enter the arguments exactly. If a monitor fails because anargument is not valid, the only way to tell that it failed is bychecking the monitor's debug log.

Version 1.0F-16

Fin

din

g an

d C

orrectin

g P

rob

lems

Product Notes

Tivoli GEM Instrumentation Monitor NotesSeveral Tivoli GEM instrumentation tasks require a Monitor Nameparameter. This parameter must be entered in the following format:

MonitorName, parm1,parm2

where:

MonitorName — the name of the monitor that you want to query.This parameter is case sensitive and must be followed with a commaand a space when parm1 is specified.

parm1 — case sensitive and must be enclosed in double-quotes if itcontains spaces. When parm2 is specified,parm1 must be followedby a comma and parm2, with no intervening spaces.

parm2 — case sensitive.

Desktop NotesThe appearance of the icons that are displayed within a ProfileManager is not updated. Tasks on menus that are accessed fromsubscriber icons will work, but icon appearance will remain the sameas when the instance was added as a subscriber.

Tivoli GEM Instrumentation Limitations, andWorkarounds

The following sections describe limitations and workarounds that areassociated with Tivoli GEM instrumentation.

The APM_HEARTBEAT Event Is Not GeneratedOn Windows NT, a problem can occur when the administratordoes not have the authority to run the monitor.

What to do:

Run the Start_Debugging task. Look in logfile%DBDIR%\tmp\MSMQ-java_heartbeat.log . Revise theauthorization on your monitor profile if you see the followingmessage:


Tivoli GEM Instrumentation Limitations, and Workarounds

get_oserv: insufficient authorization

1. From the TME 10 Distributed Monitoring Profile Propertieswindow, select Edit .

2. Select Set User & Group ID.

3. Enter the user ID of the user who is running the monitor in theRemote 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 Propertieswindow, select Save.

7. Select Distribute to display the Distribute Profile dialog.

8. Select the All Levels of Subscribers button in the DistributeTo: list.

9. Select the Make subscriber's profile an EXACT COPY ofthis profile button in the Distribute Will: list.

10. Select the versions of MSMQ servers you are NOT running inthe Distribute To These Subscribers list. Click the right arrowbutton to move these MSMQ servers to the Don't Distribute ToThese Subscribers list.

11. Select Distribute & Close to redistribute the profile.

Version 1.0F-18

Messag

es

G Appendix G. Messages

Normal task output messages are not included here. See messagecatalogs for a complete listing of messages.

The Discovery task produces return codes rather than textualmessages. The return codes and their meanings are:

1. This node is not a New Technology (NT) machine.2. Cannot find wntreg; SENTRY must be installed.3. MSMQ not found.4. Environment that is not set up.

ABG10000E Usage: mqtest

Source: mqtest.exe

Cause: Started with ? for host name.

User Response: Do not supply host name. Host name is obtainedautomatically.

ABG10001E No queue registered (ReturnCode)

Source: mqtest.exe

Cause: Indicates a possible programming error.

User Response: Seek your highest level of support.

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

ABG10002E Error starting receiver thread (ReturnCode)

Source: mqtest.exe



ABG10003E Cannot create queue (ReturnCode)

Source: mqtest.exe

Cause: MSMQ service or PEC is down.

User Response: Start MSMQ service or check availability of PECserver.

ABG10004E Cannot retrieve format name (ReturnCode)

Source: mqtest.exe



ABG10005E Cannot open queue (ReturnCode)

Source: mqtest.exe



ABG10006E Receive message (ReturnCode)

Source: mqtest.exe



Version 1.0G-2

Messag

es

ABG10007E Cannot delete queue (ReturnCode)

Source: mqtest.exe



ABG10008E Locate Begin (ReturnCode)

Source: mqtest.exe



ABG10009E Locate Next (ReturnCode)

Source: mqtest.exe



ABG10010E Format Name (ReturnCode)

Source: mqtest.exe



ABG10011E Send Message (ReturnCode)

Source: mqtest.exe




ABG10020E Usage: mqdlq

Source: mqdlq.exe

Cause: Started with ? for host name.

User Response: Do not supply host name. Host name is obtainedautomatically.

ABG10021E Cannot open queue (ReturnCode)

Source: mqdlq.exe

Cause: MSMQ service or PEC is down.

User Response: Start MSMQ service or check availability of PECserver.

ABG10021E Cannot open queue (0XC00E0025)

Source: mqdlq.exe

Cause: The tasks do not have permissions to access the queue onthe server.

User Response: In order for tasks to work, the NT administratorand tmersvrd must have permissions to access the queue on theserver. Use the MSMQ Explorer to give the NT administrator andtmersvrd read permissions. If the problem continues to occur and NTServer is not the Primary Domain Controller or Backup DomainController, you may need to provide the workstation administratorpermissions to access the queue on the server.

ABG10022E Receive message (ReturnCode)

Source: mqdlq.exe



Version 1.0G-4

Messag

es

ABG10023E Error: UuidToString failure (ReturnCode)

Source: mqdlq.exe



ABG10024I No more messages in Dead Letter queue

Source: mqdlq.exe

Cause: No messages in Dead Letter queue to delete.

User Response: None

ABG10025E Unable to get host properties (ReturnCode)

Source: mqdlq.exe



ABG10040E Usage: perfc Objectname Countername

Source: perfc.exe

Cause: OBJECTNAME and COUNTERNAME are requiredparameters.

User Response: Supply valid parameters.

ABG10041E Error: instance name required for this counter

Source: perfc.exe

Cause: Instance name is required for certain performance counters.

User Response: Supply a valid instance name. SeeDisplay_Instances task.


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, orinstance name

Source: perfc.exe

Cause: Parameters are not valid.

User Response: Enter valid parameters. Note that parameters mustbe exact, and are both case- and space-sensitive.

ABG10044E Error returned from function Function — ReturnCode

Source: perfc.exe



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



Version 1.0G-6

Messag

es

ABG10060E Usage: filever FileName

Source: filever.exe


User Response: Enter valid parameters. Note that parameters mustbe exact, and are both case- and space-sensitive.

ABG10061E Error opening file (ReturnCode)

Source: filever.exe

Cause: File name is not valid.

User Response: Supply valid file name.

ABG10062E Error querying file version (ReturnCode)

Source: filever.exe

Cause: File name is not valid.

User Response: Supply valid file name.

ABG10070E Usage: getcon servicename

Source: getcon.exe

Cause: Service name is not valid.

User Response: Supply valid service name.

ABG10071E Error opening connection to the SCM (ReturnCode)

Source: getcon.exe




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



ABG10074E Error querying the service status (ReturnCode)

Source: getcon.exe



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


User Response: Supply valid parameters. Note that parameters mustbe exact, and are both case- and space-sensitive.

Version 1.0G-8

Messag

es

ABG10082E invalid key

Source: showkey.exe


User Response: Only HKEY_LOCAL_MACHINE orHKEY_CURRENT_USER are supported.

ABG10083E unknown type

Source: showkey.exe

Cause: Showkey is not able to handle every type.


ABG10084E Unable to close subkey

Source: showkey.exe



ABG10090E Error querying free disk space (ReturnCode)

Source: drvsize.exe


User Response: Supply valid parameters. Format is D:/directory .

ABG00102E Task failed

Source: tasks

Cause: Explained in other messages.

User Response: Check other messages.


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

ABG00105E Module for MSMQ must be installed in node

Source: tasks

Cause: Task run against managed code that does not have MSMQinstalled.

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

Version 1.0G-10

Messag

es

ABG00108E Unable to retrieve MSMQ installation location fromregistry, task failed.

Source: tasks

Cause: Task run against managed node that does not have MSMQinstalled.

User Response: Install MSMQ.

ABG00122E Error stopping service, (ReturnCode)

Source: Stop_Event_Adapter/Stop_Services tasks

Cause: Check for other messages.

User Response: Check for other messages.

ABG00123E Service Service does not exist


Cause: Service does not exist on this endpoint.

User Response: Rerun against valid endpoint.

ABG00124I Service Service is already stopped



User Response: None

ABG00125I Service Service is stopped



User Response: None


ABG00126I Service Service is running, now stopping



User Response: None

ABG00127I Service Service status is Status; only RUNNINGservices may be stopped



User Response: None

ABG00128I No monitors currently distributed

Source: Stop_Monitors/Start_Monitors tasks


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



User Response: None

Version 1.0G-12

Messag

es

ABG00131I Debugging turned off



User Response: None

ABG00132I Service Service is already running



User Response: None

ABG00133I Service Service is stopped, now starting



User Response: None

ABG00134E Error starting service, (ReturnCode)

Source: Start_Event_Adapter task

Cause: Check log and return code from net start command.


ABG00135I Service Service status is Status; only STOPPEDservices may be started

Source: Start_Event_Adapter task


User Response: None


ABG00136I Debugging turned on

Source: Various tasks


User Response: None

ABG00137I Monitors started

Source: Start_Monitors task


User Response: None

ABG00138E Error starting monitors, rc=ReturnCode

Source: Start_Monitors task

Cause: Check log and return code from wenblprb command.


ABG00139E Unable to retrieve event adapter installation locationfrom registry

Source: Configure_Event_Adapter task

Cause: TEC NT adapter is not installed or registry error.


ABG00140E Cannot find tecad_nt.fmt


Cause: TEC NT adapter is not properly installed.


Version 1.0G-14

Messag

es

ABG00141E Cannot find nt_gencds.exe


Cause: Possible installation error with NT event adapter or themodule.


ABG00142I Removing: FileName



User Response: None

ABG00143E Error generating new tecad_nt.cds file: (ReturnCode)


Cause: Check return code from the nt_gencds command.


ABG00144I Stopping the adapter



User Response: None

ABG00145I Starting the adapter



User Response: None


ABG00146E Error starting the adapter (TECNTAdapter)




ABG00147I Log information written to FileName



User Response: None

ABG00148I Locating files



User Response: None

ABG00149I Generating new tecad_nt.cds file



User Response: None

ABG00150I Configure EventConsole Complete!

Source: Configure_Event_Console task


User Response: None

Version 1.0G-16

Messag

es

ABG00151I EventGroupName already assigned to EventConsole.



User Response: None

ABG00152I Assigned EventGroupName to EventConsole.



User Response: None

ABG00153E Failed to assign EventGroupName to EventConsole.Ensure that task is run against the TEC Server.


Cause: Task run against managed node that is not the TEC server

User Response: Run the task against the TEC server.

ABG00154E Command Failed.

Source: Configure_Event_Console/Configure_Event_Server tasks

Cause: General failure.

User Response: Check log for other messages.

ABG00155I The last few lines of the log file FileName are ...

Source: Configure_Event_Console/Configure_Event_Server tasks


User Response: None


ABG00156I Rulebase rule base already exists, will update it.Clone rule base will be ignored.

Source: Configure_Event_Server task


User Response: None

ABG00157I Rulebase rule base already exists, will update it.



User Response: None

ABG00158I Clone rule base (Rulebase) exists!



User Response: None

ABG00159I Created Rulebase



User Response: None

ABG00160I Sentry classes already installed.



User Response: None

Version 1.0G-18

Messag

es

ABG00161I Sentry classes have not been installed, adding them.



User Response: None

ABG00162I Rulebase compiles successfully!



User Response: None

ABG00164I Created Rulebase rule base.



User Response: None

ABG00165I Copied CloneRulebase rule base to Rulebase.



User Response: None

ABG00166I Imported ClassFile to Rulebase rule base.



User Response: None


ABG00167I Stopped Event Server.



User Response: None

ABG00168I Restarted Event Server.



User Response: None

ABG00169I Configuring Event Server...



User Response: None

ABG00170I Rulefile is already in (Rulebase) rule base.



User Response: None

ABG00171I Will delete and import it again to pick up any newrules.



User Response: None

Version 1.0G-20

Messag

es

ABG00172I Imported Rulefile to Rulebase rule base.



User Response: None

ABG00173I Created EventSource event source.



User Response: None

ABG00174I EventSource event source already exists.



User Response: None

ABG00175I Removed EventSource.



User Response: None

ABG00176I Loaded Rulebase rule base.



User Response: None


ABG00177I Copied rule callback script.



User Response: None

ABG00178I Creating event group.



User Response: None

ABG00179I The MSMQ Event Group created successfully.



User Response: None

ABG00180I The MSMQ Event Group already exists.



User Response: None

ABG00181E A rule base must be defined!


Cause: A rule base name was not entered in the Configure EventServer dialog.

User Response: Rerun the task and supply a new or existing rulebase name.

Version 1.0G-22

Messag

es

ABG00182E Clone rule base must be defined!


Cause: A new rule base was specified on the Configure EventServer dialog but no Rule Base to Clone was entered.

User Response: Rerun the task and supply an existing rule base toclone or specify an existing rule base.

ABG00183E Clone rule base (Rulebase) must already exist!


Cause: The Rule Base to Clone entered on the Configure EventServer dialog does not exist.

User Response: Rerun the task and supply an existing rule base toclone.

ABG00184E Cannot create new rule base path.


Cause: Unable to issue mkdir command.

User Response: Check for other diagnostic messages.

ABG00185E Rulebase does not compile!


Cause: One or more rules in the rule base failed to compile.

User Response: Check the log for the rules that did not compile,correct the rules, and rerun the task.


ABG00186E Failed to create Rulebase rule base.


Cause: The wcrtrb command encountered a problem.

User Response: Check the log for the error, correct it, and rerun thetask.

ABG00187E Failed to copy CloneRulebase rule base to Rulebase.


Cause: The wcprb command encountered a problem.


ABG00188E Failed to import Rulefile to Rulebase rule base.


Cause: The wimprbclass command encountered a problem.


ABG00189E Failed to create EventSource event source.


Cause: The wcrtsrc command encountered a problem.


Version 1.0G-24

Messag

es

ABG00190E Failed to delete EventSource event source.


Cause: The wdelsrc command encountered a problem.


ABG00191E Failed to load Rulebase into Event Server


Cause: The wloadrb command encountered a problem.


ABG00192E Failed to copy set icon script for msmq_monitors.rls


Cause: Possible installation problem.

User Response: Check for other diagnostic messages.

ABG00193E Failed to create event group.


Cause: The wcrteg command encountered a problem.



ABG00194E Failed to add a filter to the event group.


Cause: The waddegflt command encountered a problem.


ABG00195E Failed to restart Event Server. Please restart theevent server from the desktop or command line.


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 berestarted before installation is complete!


Cause: The wstopesvr command encountered a problem.

User Response: Stop (wstopesvr) and start (wstartesvr) the eventserver from the command line.

ABG00197E This host is not the TMR Event Server


Cause: The task was not run against the TMR event server.

User Response: Rerun the task against the event server.

Version 1.0G-26

Messag

es

ABG00198E error locating Rulebase rule base directory: Directory


Cause: The wlsrb command encountered a problem.


ABG00199I Cannot create MSMQ instance onManagedNode/Endpoint

Source: Configure task


User Response: None

ABG00200I An MSMQ instance Instance already exists



User Response: None

ABG00201I Cannot create MSMQ instance for server nameManagedNode



User Response: None

ABG00202E Command wcrtmsmq/wcrtapx failed: (ReturnCode)


Cause: Check return code.



ABG00203E Failed to subscribe ServerAlias to profile manager:ProfileManager.




ABG00204I Subscribed ServerAlias to profile manager:ProfileManager.



User Response: None

ABG00205I Created MSMQ instance ServerAlias onManagedNode/Endpoint.



User Response: None

ABG00206E CDROM directory ((Directory)) invalid, MSMQ.INDnot found

Source: Install task

Cause: Path name for CD-ROM location is not valid.

User Response: Rerun with correct parameters.

Version 1.0G-28

Messag

es

ABG00207E Input file FileName not found


Cause: Path name or file name for input file is not valid.


ABG00208E Unable to contact ManagedNode


Cause: Endpoint not operational.

User Response: Check endpoint.

ABG00209E Installation Failed on ManagedNode


Cause: Explained by other messages.

User Response: Check other messages.

ABG00210I Not installing on ManagedNode because it already hasmodule installed



User Response: None

ABG00301E Create MSMQ method: managed node or endpointnot defined

Source: wcrtmsmq command

Cause: Attempt to create MSMQ instance on a manage node that isnot running NT.

User Response: Rerun with correct managed node name.


ABG00302E Create MSMQ method: managed node or endpointManagedNode/Endpoint not found


Cause: Attempt to create MSMQ instance on an unknown managednode.


ABG00303E Create MSMQ method: tmf_trans_begin failed




ABG00304E Create MSMQ method: MSMQ server name notdefined


Cause: No server name was provided.


ABG00305E Create MSMQ method: tmf_trans_end failed




Version 1.0G-30

Messag

es

ABG00307E Managed node ManagedNode is not an NT-managednode


Cause: Attempt to create MSMQ instance on a manage node that isnot running NT.


ABG00308I An MSMQ server, MSMQServer, is created byadministrator in Policy Region PolicyRegion.



User Response: None

ABG00318E The MSMQ server MSMQServer is already running.


Cause: Attempt to start a server that is already running.

User Response: None

ABG00320E The MSMQ server MSMQServer is already stopped.


Cause: Attempt to stop a server thats already stopped

User Response: None

ABG00322I The MSMQ server MSMQServer has been started.



User Response: None


ABG00324I The MSMQ server MSMQServer has been stopped.



User Response: None

ABG00326E Unable to stop MSMQ server MSMQServer.


Cause: Unknown; turn on debugging and check the log.

User Response:

ABG00349E There is already a MSMQ instance on managednode ManagedNode.


Cause: Attempt to create a 2nd MSMQ instance on a manage node.


ABG00359I The monitors for MSMQInstance have been started.



User Response: None

ABG00363E Unable to stop monitors for MSMQ serverMSMQServer.


Cause: Check notices for error messages.

User Response: Correct the problem.

Version 1.0G-32

Messag

es

ABG00395E Unable to stop Event Adapter for MSMQ server.


Cause: Check notices for error messages

User Response: Correct the problem.

ABG00398E Error occurs while running Display_Server_Infotask for MSMQ server MSMQServer.


Cause: Unknown; turn on debugging and rerun.

User Response: Check the log.

ABG00400I No monitors have been distributed to MSMQ serverMSMQServer.



User Response: None

ABG00424E PolicyRegion is not a policy region. IfPolicyRegion isa policy region, it cannot be located. Please check thepolicy region name to ensure that it is spelled correctly.



User Response: Rerun with correct policy region name.


ABG00425I Usage wcrtmsg -a server_alias -p policy-region -hmanaged_node -e endpoint -v { 10 }



User Response: None

ABG00426E Create of MSMQ instance MSMQInstance has failed.Resource is not a managed resource of the policyregion specified.


Cause: Security error.

User Response: Correct and rerun.

ABG00427E Create of MSMQ instance MSMQInstance has failed.


Cause: Unable to create MSMQ instance.

User Response: See other messages.

Version 1.0G-34

Glossary

A

administrator . See Tivoli administrator.

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

B

Basic Recorder of Objects in C (BAROC). In the event server of theTivoli Enterprise Console (TEC), the internal representation of the definedevent classes.

business description file (BDF). In a Tivoli environment, a generic namefor any of these application description files: business system description file(BSDF), business system component description file (BCDF), and businesssystem mapping description file (BMDF), and business subsystemdescription 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 anothercomputer system or process that is typically referred to as a server. Multipleclients may share access to a common server.

component description file (CDF). In the context of the ApplicationManagement Specification (AMS), an application description file thatcontains information about a specific component in a management-readyapplication. Each management-ready application can contain multiplecomponents, 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; othersoperate periodically.

E

endpoint. (1) In a Tivoli environment, a Tivoli client that is the ultimaterecipient for any type of Tivoli operation. (2) In a Tivoli environment, aTivoli service that runs on multiple operating systems and performs Tivolioperations on those systems, thereby enabling the Tivoli ManagementFramework to manage the systems as Tivoli clients.

event. In a Tivoli environment, any significant change in the state of asystem resource, network resource, or network application. An event can begenerated for a problem, for the resolution of a problem, or for thesuccessful completion of a task. Examples of events are: the normal startingand stopping of a process, the abnormal termination of a process, and themalfunctioning of a server.

event adapter. In a Tivoli environment, software that converts events intoa format that the Tivoli Enterprise Console can use and forwards the eventsto the event server. Using the Tivoli EIF, an organization can develop itsown event adapters, tailored to its network environment and specific needs.

event class. In the Tivoli Enterprise Console, a classification for an eventthat indicates the type of information that the event adapter will send to theevent server.

Version 1.0X-2

event console. In the Tivoli Enterprise Console, a graphical user interface(GUI) that enables system administrators to view and respond to dispatchedevents from the event server.

event group. In the Tivoli Enterprise Console, a set of events that meetcertain criteria. Each event group is represented by an icon on the eventconsole. Tivoli administrators can monitor event groups that are relevant totheir specific areas of responsibility.

H

host. In a Tivoli environment, a computer that serves as a managed nodefor a profile distribution.

I

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

J

job. (1) In a Tivoli environment, a resource consisting of a task and itspreconfigured execution parameters. Among other things, the executionparameters specify the set of hosts on which the job is to execute. (2) A unitof 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, andcontrol statements to the operating system.

M

managed node. (1) In a Tivoli environment, any managed resource onwhich the Tivoli Management Framework is installed. (2) In Internetcommunications, a workstation, server, or router that contains a networkmanagement agent. In the Internet Protocol (IP), the managed node usuallycontains a Simple Network Management Protocol (SNMP) agent.


monitor . (1) A device that observes and records selected activities within adata processing system for analysis. Possible uses are to indicate significantdeparture from the norm, or to determine levels of utilization of particularfunctional 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 resourcesthat share one or more common policies. Tivoli administrators use policyregions to model the management and organizational structure of a networkcomputing environment. The administrators can group similar resources,define access to and control the resources, and associate rules for governingthe resources. The policy region contains resource types and the list ofresources to be managed. A policy region is represented on the desktop byan icon that resembles a capitol building (dome icon). (2) When a TivoliManagement Region (TMR) is created, a policy region with the same nameis also created. In this case, the TMR has only one policy region. However,in most cases, a Tivoli administrator creates other policy regions andsubregions to represent the organization of the TMR. A TMR addresses thephysical connectivity of resources whereas a policy region addresses thelogical organization of resources.

profile . (1) Data that describes the significant characteristics of a user, agroup of users, or one or more computer resources. (2) In a Tivolienvironment, a container for application-specific information about aparticular type of resource. A Tivoli application specifies the template for itsprofiles; the template includes information about the resources that can bemanaged by that Tivoli application. A profile is created in the context of aprofile manager; the profile manager links a profile to the Tivoli resource(for example, a managed node) that uses the information contained in theprofile. A profile does not have any direct subscribers.

profile manager. In a Tivoli environment, a container for profiles thatlinks the profiles to a set of resources, called "subscribers." A profilemanager can contain (a) profiles of multiple types or (b) multiple profiles ofthe same type. Tivoli administrators use profile managers to organize anddistribute profiles. A profile manager is created in the context of a policyregion and is a managed resource in a policy region. See also subscriptionlist.

Version 1.0X-4

R

rule. In the Tivoli Enterprise Console (TEC), a set of one or more logicalstatements that enable the event server to recognize relationships amongevents (event correlation) and to execute automated responses accordingly.

rule base. In the Tivoli Enterprise Console (TEC), a set of rules and theevent class definitions for which the rules are written. The TEC uses the rulebase in managing events. An organization can create many rule bases, witheach rule base fulfilling a different set of needs for network computingmanagement.

S

service. A Windows NT program that provides a specific function toapplications. Services typically run in the background, without a userinterface.

subscription list. In a Tivoli environment, a list that identifies thesubscribers to a profile manager. Including a profile manager on asubscription list (in effect, a list within a list) is a way of subscribing severalresources simultaneously rather than adding each one individually. In TivoliPlus modules, a profile manager functions as a subscription list.

T

task. In a Tivoli environment, the definition of an action that must beroutinely performed on various managed nodes throughout the network. Atask defines the executables to be run when the task is executed, theauthorization role required to execute the task, and the user or group nameunder which the task will execute.

threshold. In software products, a value that defines a limit for amonitored condition. The monitored condition, the significance of the limit,and the particular software product’s response when the monitored conditionreaches the specified threshold vary widely according to product.

Tivoli administrator . In a Tivoli environment, a system administrator whohas been authorized to perform systems management tasks and managepolicy regions in one or more networks. Each Tivoli administrator isrepresented by an icon on the desktop.


Tivoli desktop. In a Tivoli environment, the desktop that systemadministrators use to manage their network computing environment.

Tivoli Distributed Monitoring . A Tivoli product that monitors systemresources, initiates any necessary corrective actions, and informs systemadministrators of potential problems. Tivoli Distributed Monitoring consistsof a group of monitors that are installed on each managed node that is to bemonitored. It resolves some events on its own and may send others to theTivoli 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 forevents from all sources. The Tivoli Enterprise Console provides acentralized, global view of the network computing environment; it usesdistributed event monitors to collect information, a central event server toprocess information, and distributed event consoles to present information tosystem administrators.

Tivoli environment. Pertaining to the suite of Tivoli applications thatenable system administrators to manage their network computing enterpriseaccording to the disciplines of availability management, deploymentmanagement, operations and administration, and security management.

Tivoli Global Enterprise Manager (Tivoli GEM) . A Tivoli product thatallows system administrators to graphically monitor, control, and configureapplications residing in distributed and host (S/390) environments and to usethe concept of business systems management to organize relatedcomponents, thereby providing a business perspective for managementdecisions. Tivoli GEM gives information technology staff a logical view ofthe computing environment; this view shows, at a glance, the status of themultiple applications that comprise the enterprise's business system,including application components, the relationships among and betweencomponents, and the flow of data between the applications. By providingthis view from a business perspective, Tivoli GEM enables systemadministrators to quickly make determinations about the business impact ofany component failure. Addressing technology problems from the businessperspective greatly improves the effectiveness of system administrators andprovides a higher level of service to users.

Tivoli Management Agent (TMA). In the Tivoli environment, an agentthat securely performs administrative operations.

Tivoli Management Region (TMR). In a Tivoli environment, a TMRserver and the set of clients that it serves. An organization can have more

Version 1.0X-6

than one TMR. A TMR addresses the physical connectivity of resourceswhereas a policy region addresses the logical organization of resources.

Tivoli GEM console. In the Tivoli Global Enterprise Manager and TivoliNetView for OS/390, a Java-based graphical user interface that displaysbusiness system information from the Tivoli GEM server. The Tivoli GEMconsole displays each component as a separate icon or shape and draws linesbetween icons to denote links. It then uses color to indicate the status ofeach component and of the business system as a whole. As the Tivoli GEMserver receives configuration and status updates for the business system, itupdates the Tivoli GEM console. Therefore, the Tivoli GEM console alwaysdisplays the real-time configuration and status of the business system.

Tivoli GEM server . In Tivoli Global Enterprise Manager and TivoliNetView for OS/390, a server that interacts with instrumented applicationsin a business system and provides information for display on the TivoliGEM console. The Tivoli GEM server receives heartbeat events frominstrumented applications or components and determines the business systemin which a component belongs. The Tivoli GEM server also queriesinstrumented applications for related applications and for the status of itsmonitors. All of this information is used to create and maintain a view ofeach business system's configuration and availability on the Tivoli GEMconsole.


Version 1.0X-8

Index

Aadmintool command 7-11aggregate resources

navigating to specific resources 9-4viewed on Tivoli GEM console 9-4

Application Proxydefinition 2-6installation 2-8

attributes, MSMQ serverdisplaying, wgetmsmq

command A-2updating, wsetmsmq command A-3

authorization rolesassigning

for Manager for MQS 3-2for Tivoli GEM

instrumentation 7-7description 1-3

Bbusiness description files

contents C-2installing C-1

business system description C-1

Cclient, Tivoli GEM, hints for

using F-10commands

admintool 7-11wcrtmsmq A-1wgetmsmq A-2winstall 2-12wlscurrb F-6, F-8, F-11wlsrbclass F-6, F-8, F-11wlsrbrules F-7, F-9, F-12wsetmsmq A-3wtdumprl F-7, F-8, F-9, F-12wtemp F-2, F-14, F-16

component description filescontents C-2installing C-1

components, installed, location ofManager for MQS 2-6Tivoli GEM instrumentation 7-8

Configure task 5-7Configure_Event_Adapter task 6-5Configure_Event_Console task 6-4Configure_Event_Server task 6-2


configuringevent console 6-4event server 2-6, 6-2NT event adapter 6-5

configuring Manager for MQSauthorization roles 3-2overview 3-1

confirming server discovery on TivoliGEM console 8-5

console 1-3TEC 1-4Tivoli GEM 7-3

creatingMSMQ server instance

from desktop 3-5wcrtmsmq command A-1

Ddata flow 2-2database

backup 7-14corrupted, remedy F-15

debugginghelpful information F-14log files, location of F-14

deleting an MSMQ server 3-10determining server status 3-10dialogs

install product 2-7Discover task 2-13Discover_Connections task 9-2discovery, server, on Tivoli GEM

console 8-5Disk Usage by MSMQ Server

monitor 4-7Display_Enterprise task 9-2, 9-3

Display_Instances task 5-5, 9-2Display_MSMQ_Info task 5-5, 9-2Display_Server_Info task 5-5, 9-2Display_Server_Status task 5-5, 9-2Display_Site task 9-2, 9-3distributed monitoring 1-3, 1-4Distributed Transaction Coordinator

Status monitor 4-7distributing the heartbeat monitor 8-2

Eevent

adapter, NTconfiguring 6-5requirements 2-5starting and stopping 6-6

classesdistributed monitoring B-1MSMQ_Event B-2MSMQ_Monitors B-1NT event adapter B-2

console, configuring 6-4filtering 1-2, 6-7flow 2-2management

adapter, configuring 6-5adapter, NT, starting and

stopping 6-6authorization required 6-1console, configuring 6-4overview 6-1

monitoring 6-6rules B-5

Event Adapter Status monitor 4-7event server

configuring 2-6, 6-2hints for using F-8

Version 1.0X-10

executing tasksManager for MQS 5-2Tivoli GEM instrumentation 9-1,

9-7

FFalconMQ Server Status monitor 4-7features, product

distributed monitoring 1-3, 1-4event display, consolidated 1-4event filtering 1-2integration with Tivoli Management

Framework 1-3authorization 1-3

monitoring, distributed 1-3, 1-4task libraries 1-3TEC 1-3, 1-4

field descriptions, tasks D-1filtering events 1-2, 6-7forwarding events to event server 2-6Free Disk Space Available monitor 4-7

GGeneric Performance monitor 4-7getting started

with Manager for MQSauthorization roles, assigning 3-2configuring, overview 3-1instances, MSMQ 3-4MSMQ server, creating 3-5MSMQ server, deleting 3-10MSMQ server, managing 3-3server status, determining 3-10

with Tivoli GEM instrumentationheartbeat monitor, subscribing and

distributing 8-2resource discovery,

confirming 8-5

HHeartbeat monitor

description, MSMQ server 9-9description, MSSQLServer 9-10distributing 8-2subscribing 8-2

Iicon color F-13icon files

contents C-2installing C-1

Install task 2-14installation

hints F-1options 2-6

installingavailable clients 2-8, 2-11, 7-13Manager for MQS

administrator authorization 1-3checklist 2-6components, location of 2-6NT event adapter

requirements 2-5procedure 2-10

Tivoli GEM instrumentationadministrator authorization 7-7components, location of 7-8management regions 7-7procedure 7-12

instances, MSMQ 3-4integration with Tivoli Management

Frameworkevent display 1-4TEC 1-4

interconnected TMRs 2-5


JJava Development Kit 7-9

Llibraries, task 1-3List_Dead_LetterQ task 5-6, 9-2listing tasks

Manager for MQS 5-2Tivoli GEM instrumentation 9-1

location of installed componentsManager for MQS 2-6Tivoli GEM instrumentation 7-8

log files, location of F-14

Mmanagement

regions, requirements 2-5tasks

authorization required, Managerfor MQS 5-4

authorization required, TivoliGEM instrumentation 7-7

listing 5-2log files, location of F-14overview 5-1running 5-2, 9-1running from the desktop,

hints F-3running from the Tivoli GEM

console, hints F-4monitoring, distributed 1-3, 1-4monitors

hints for using F-5listing

Manager for MQS 4-1Tivoli GEM

instrumentation 9-11

monitors (continued)log files, location of F-14MSMQ server

Disk Usage by MSMQServer 4-7

Distributed TransactionCoordinator Status 4-7

Event Adapter Status 4-7FalconMQ Server Status 4-7Free Disk Space Available 4-7Generic Performance 4-7MQ Test 4-7Mqsvc 4-6Msdtc 4-6MSMQ IS 4-5MSMQ Queue 4-5MSMQ Server Status 4-7MSMQ Service 4-6MSMQ Session 4-6Q2qgw 4-6Special Queue Count 4-7Special Queue Maximum

Time 4-7performance 4-5queue 4-7Tivoli GEM instrumentation (MSMQ

server)Heartbeat 9-9hints for using F-5Manager for MQS-supported 9-9scheduling F-15State 9-9thresholding 9-10

Tivoli GEM instrumentation(MSSQLServer)

Heartbeat 9-10State 9-10

Version 1.0X-12

MQ Test monitor 4-7Mqsvc monitor 4-6Msdtc monitor 4-6MSMQ instances 3-4MSMQ IS monitor 4-5MSMQ monitor tasks

Purge_Dead_LetterQ 4-9Restart_Services 4-10

MSMQ Queue monitor 4-5MSMQ server

attributesdisplaying, wgetmsmq

command A-2updating, wsetmsmq

command A-3creating


deleting 3-10endpoints, MSMQ 3-4icon pull-down tasks 3-8instances, creating 3-5managing 3-3profile managers 3-11status, determining 3-10

MSMQ Server Status monitor 4-7MSMQ Service monitor 4-6MSMQ Session monitor 4-6msmq_admin TMR role 1-3, 3-2MSMQ_Event event class B-2MSMQ_Monitors event class B-1msmq_senior TMR role 1-3, 3-2multiple TMRs 2-5

NNT event adapter

configuring 6-5Event Adapter Status monitor 4-7

NT event adapter(continued)requirements 2-5starting and stopping 6-6

Pperformance counters 4-7performance monitors

description 4-5listing 4-1

planning for installationevent server 2-6overview 2-1

management regions 2-5NT event adapter 2-5TMR 2-5

product featuresdistributed monitoring 1-3, 1-4event display, consolidated 1-3, 1-4event filtering 1-2integration with Tivoli Management

Framework 1-3authorization 1-3

monitoring, distributed 1-3, 1-4task libraries 1-3TEC 1-3, 1-4

profile managers, subscriber list 3-11Purge_Dead_LetterQ task 5-6, 9-2

QQ2qgw monitor 4-6Query_State task 9-2, 9-3Query_Threshold_Settings task 9-2,

9-3Query_Thresholds task 9-2, 9-3Query_Values task 9-2, 9-3


Rrequirements

administrator authorizationManager for MQS 1-3Tivoli GEM instrumentation 7-7

management regions 2-5NT event adapter 2-5

resource discovery on Tivoli GEMconsole 8-5

resource roles 3-3rules, event

heartbeat monitor, subscribing anddistributing 8-2

Manager for MQS B-5resource discovery, confirming 8-5

running tasksManager for MQS 5-2running from Tivoli GEM console,

recommended 9-1Tivoli GEM instrumentation 9-7

Sscheduling Tivoli GEM instrumentation

monitors F-15server, MSMQ

attributesdisplaying, wgetmsmq

command A-2updating, wsetmsmq

command A-3creating


deleting 3-10endpoints, MSMQ 3-4icon pull-down tasks 3-8managing 3-3

server, MSMQ(continued)monitors

listing 4-1performance 4-5performance counters 4-7

profile manager 3-11status, determining 3-10subscribing to a profile

manager 3-11server, MSSQLServer 7-4, 7-7, 7-14,

8-3, 8-5, 9-1, 9-2, 9-4monitors 9-9tasks 9-3

server, Tivoli GEM 7-2server, TMR 2-2Set_Polling_Interval task 9-2, 9-3Set_Pulse task 9-2, 9-3Set_Thresholds task 9-2, 9-3Special Queue Count monitor 4-7Special Queue Maximum Time

monitor 4-7Start task 9-1, 9-3Start_Debugging task 5-8, 9-2Start_Event_Adapter task 6-6Start_Monitors task 5-9, 9-2Start_Services task 5-6, 9-2State monitor (MSMQ server) 9-9State monitor (MSSQLServer) 9-10Stop task 9-1, 9-3Stop_Debugging task 5-8, 9-2Stop_Event_Adapter task 6-6Stop_Monitors task 5-9, 9-2Stop_Services task 5-6, 9-2subscribing the heartbeat monitor 8-2

T

Version 1.0X-14

task libraries 1-3tasks

field descriptions D-1hints

running from the desktop F-3running from the Tivoli GEM

console F-4listing 5-2log files, location of F-14MSMQ server

authorization required 5-4Display_Instances 5-5Display_MSMQ_Info 5-5Display_Server_Info 5-5Display_Server_Status 5-5List_Dead_LetterQ 5-6Purge_Dead_LetterQ 5-6Start_Services 5-6Stop_Services 5-6

MSMQ TECConfigure_Event_Adapter 6-5Configure_Event_Console 6-4Configure_Event_Server 6-2Start_Event_Adapter 6-6Stop_Event_Adapter 6-6

MSMQ utilityauthorization required 5-7Configure 5-7Discover 2-13Install 2-14Start_Debugging 5-8Start_Monitors 5-9Stop_Debugging 5-8Stop_Monitors 5-9

overview 5-1running 5-2Tivoli GEM instrumentation (MSMQ

server component)Discover_Connections 9-2

tasks (continued)Tivoli GEM instrumentation (MSMQ

server component)(continued)Display_Enterprise 9-2Display_Instances 9-2Display_MSMQ_Info 9-2Display_Server_Info 9-2Display_Server_Status 9-2Display_Site 9-2field descriptions D-1List_Dead_LetterQ 9-2Purge_Dead_LetterQ 9-2Query_State 9-1, 9-2Query_Thresholds 9-1, 9-2Query_Values 9-1, 9-2running 9-1, 9-7Set_Polling_Interval 9-1, 9-2Set_Pulse 9-2Set_Thresholds 9-1, 9-2Start_Debugging 9-2Start_Monitors 9-2Start_Services 9-1, 9-2Stop_Debugging 9-2Stop_Monitors 9-2Stop_Services 9-1, 9-2

Tivoli GEM instrumentation(MSSQLServer component)

Display_Enterprise 9-3Display_Site 9-3Query_State 9-3Query_Threshold_Settings 9-3Query_Thresholds 9-3Query_Values 9-3Set_Polling_Interval 9-3Set_Pulse 9-3Set_Thresholds 9-3Start 9-3Stop 9-3


tear-away log 9-7TEC console 1-3, 1-4Tivoli

authorization 1-3distributed monitoring 1-3, 1-4enterprise console 1-3, 1-4framework, integration with

authorization 1-3event display 1-3, 1-4overview 1-3TEC 1-3, 1-4

Tivoli GEM console 7-3Tivoli GEM hints for using F-10Tivoli GEM instrumentation

event handling 7-3initializing 8-1installing

authorization required 7-7components 7-8Java Development Kit 7-9overview 7-1procedure 7-12

instrumented components 7-4management regions 7-7monitors

hints for using F-5scheduling F-15supported Manager for MQS 9-9

tasksfield descriptions D-1locating 9-1running 9-1, 9-7

Tivoli GEM server 7-2TMR

multiple 2-5requirements 2-5roles

msmq_admin 1-3, 3-2msmq_senior 1-3, 3-2

TMR (continued)server 2-2

troubleshootingdebugging information F-14hints

icon color F-13installation F-1monitors, using F-5tasks and jobs, running from the

desktop F-3tasks and jobs, running from the

Tivoli GEM console F-4TEC, using F-8Tivoli GEM client, using F-10

log files F-14

Wwcrtmsmq command A-1wgetmsmq command A-2winstall command 2-12wlscurrb command F-6, F-8, F-11wlsrbclass command F-6, F-8, F-11wlsrbrules command F-7, F-9, F-12wpostemsg F-2wsetmsmq command A-3wtdumprl command F-7, F-8, F-9,

F-12wtemp command F-2, F-14, F-16

Version 1.0X-16

GC32-0313-00

/XRL/1

Table Definitions

id File Page References

WQ9 QMM10UGP SCRIPT iii iiiWQ10 QMM10UGP SCRIPT iii iiiWQ11 QMM10UGP SCRIPT iii iiiWQ12 QMM10UGP SCRIPT iii iiiWQ13 QMM10UGP SCRIPT iii iiiWQ14 QMM10UGP SCRIPT iii iiiWQ15 QMM10UGP SCRIPT iii iiiWQ16 QMM10UGP SCRIPT iii iiiWQ17 QMM10UGP SCRIPT iii iiiWQ18 QMM10UGP SCRIPT iii iiiWQ19 QMM10UGP SCRIPT iii iiiWQ20 QMM10UGP SCRIPT iii ivWQ24 QMM10UGP SCRIPT 2-6 2-7WQ25 QMM10UGP SCRIPT 2-6 2-7WQ26 QMM10UGP SCRIPT 2-6 2-7WQ27 QMM10UGP SCRIPT 2-6 2-7WQ36 QMM10UGP SCRIPT 3-10 3-10WQ37 QMM10UGP SCRIPT 3-10 3-10WQ38 QMM10UGP SCRIPT 3-10 3-10WQ39 QMM10UGP SCRIPT 3-10 3-10WQ45 QMM10UGP SCRIPT 5-4 5-5WQ46 QMM10UGP SCRIPT 5-4 5-5WQ47 QMM10UGP SCRIPT 5-4 5-5WQ49 QMM10UGP SCRIPT 5-7 5-7WQ50 QMM10UGP SCRIPT 5-7 5-7WQ51 QMM10UGP SCRIPT 5-7 5-7WQ52 QMM10UGP SCRIPT 5-7 5-7WQ53 QMM10UGP SCRIPT 5-7 5-7WQ54 QMM10UGP SCRIPT

/XRL/2

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

/XRL/3

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

/XRL/4

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

Headings


WQ21 QMM10UGP SCRIPT1-1 Chapter 1, Introducing Manager for Message Queue Server

xiiWQ22 QMM10UGP SCRIPT

2-1 Chapter 2, Planning for and Installing Manager for Message QueueServer

xii, 7-8NTEAREQ QMM10UGP SCRIPT

2-5 NT Event Adapter Requirements 1-1, 2-1TMRS QMM10UGP SCRIPT

2-5 Configuring Tivoli Management Regions 2-2WQ23 QMM10UGP SCRIPT 2-6 Installation OverviewAPPROX QMM10UGP SCRIPT

2-8 Installing the Application Proxy 2-6DESKINS QMM10UGP SCRIPT

2-10 From the Desktop 2-6WINST QMM10UGP SCRIPT

2-12 Using the winstall Command 2-6INSPROD QMM10UGP SCRIPT

2-13 Using the Discover and Install Tasks 2-6WQ28 QMM10UGP SCRIPT 2-13 Discover Task 5-7WQ29 QMM10UGP SCRIPT 2-14 Install Task 2-9, 5-7WQ30 QMM10UGP SCRIPT

3-1 Chapter 3, Getting Started with Manager for Message Queue Server xiiWQ31 QMM10UGP SCRIPT

3-2 Assigning Authorization Roles1-3, 3-1, F-4

WQ32 QMM10UGP SCRIPT3-3 Managing Microsoft Message Queue Servers

3-1WQ33 QMM10UGP SCRIPT

3-4 MSMQ Server Instances3-7, 3-11, 5-2

WQ34 QMM10UGP SCRIPT3-5 Creating MSMQ Server Instances

/XRL/5

3-3, 3-4, 5-8WQ35 QMM10UGP SCRIPT

3-8 MSMQ Server Icon Tasks 5-1WQ40 QMM10UGP SCRIPT

3-11 MSMQ Server Lists 3-4WQ41 QMM10UGP SCRIPT

4-1 Chapter 4, Monitoring Microsoft Message Queue Serversxii, 3-4, 9-8

WQ42 QMM10UGP SCRIPT4-5 Understanding the Monitors

9-9WQ43 QMM10UGP SCRIPT

5-1 Chapter 5, Tasks to Manage Microsoft Message Queue Resourcesxii, 3-4, 9-3

WQ44 QMM10UGP SCRIPT5-4 MSMQ Server Tasks

3-9, 3-9, 5-1WQ48 QMM10UGP SCRIPT

5-7 MSMQ Utility Tasks 5-1WQ57 QMM10UGP SCRIPT 5-7 Configure 2-14, 3-5WQ58 QMM10UGP SCRIPT 5-8 Start_Debugging F-14WQ59 QMM10UGP SCRIPT 5-8 Stop_Debugging F-14WQ60 QMM10UGP SCRIPT 5-9 Start_MonitorsWQ61 QMM10UGP SCRIPT 5-9 Stop_MonitorsWQ62 QMM10UGP SCRIPT

6-1 Chapter 6, Managing Microsoft Message Queue Eventsxiii, 2-5, 5-1

WQ69 QMM10UGP SCRIPT6-2 Configuring the Event Server

2-6, 3-1WQ70 QMM10UGP SCRIPT

6-4 Configuring an Event Console 3-1, 6-2WQ71 QMM10UGP SCRIPT

6-5 Configuring the NT Event Adapter 3-1, 6-2WQ72 QMM10UGP SCRIPT

6-6 Starting and Stopping the NT Event AdapterWQ73 QMM10UGP SCRIPT

7-1 Chapter 7, Tivoli GEM Instrumentationxiii, 1-1, 2-1, 2-2, 2-7

EVHAND QMM10UGP SCRIPT7-3 Tivoli GEM Instrumentation Event Handling

WQ74 QMM10UGP SCRIPT7-5 Instrumentation Files, Libraries, and Profiles

9-1RNNTSKS QMM10UGP SCRIPT 7-6 TasksVIEWMNS QMM10UGP SCRIPT 7-7 MonitorsPRERRQ QMM10UGP SCRIPT

/XRL/6

7-7 Preparing to Install Tivoli GEM InstrumentationWQ83 QMM10UGP SCRIPT

7-12 Installing Tivoli GEM InstrumentationWQ84 QMM10UGP SCRIPT

8-1 Chapter 8, Initializing Tivoli GEM Instrumentation xiiiSTEP1 QMM10UGP SCRIPT

8-2 Configuring MSMQ Servers 8-1STEP2 QMM10UGP SCRIPT

8-2 Subscribing to and Distributing the File Packages 8-1PROFIL2 QMM10UGP SCRIPT

8-2 Subscribing to and Distributing the Heartbeat Monitor 8-1, 9-5CONFIRM QMM10UGP SCRIPT

8-5 Confirming Resource DiscoveryWQ88 QMM10UGP SCRIPT

9-1 Chapter 9, Tivoli GEM Instrumentation Tasks and Monitors xiii, 2-3TAAASKS QMM10UGP SCRIPT

9-1 Locating and Running TasksGMTASKS QMM10UGP SCRIPT

9-1 Tivoli GEM Instrumentation TasksEXTASKS QMM10UGP SCRIPT

9-2 MSMQ Server Component Tasks 7-7UNDAGGS QMM10UGP SCRIPT

9-4 Understanding MSMQ Server Aggregate ResourcesNAVAGGS QMM10UGP SCRIPT

9-4 Navigating to MSMQ Server ResourcesTEARAWY QMM10UGP SCRIPT

9-7 Using the Tear-Away LogSAMTASK QMM10UGP SCRIPT

9-7 Starting a Sample TaskALLMON QMM10UGP SCRIPT 9-8 Monitors 7-7GEMMON1 QMM10UGP SCRIPT 9-9 Heartbeat MonitorEXMNTRS QMM10UGP SCRIPT

9-9 Manager for MQS-Supported MonitorsUSEMON QMM10UGP SCRIPT

9-11 Viewing Monitor StatusWQ89 QMM10UGP SCRIPT

A-1 Appendix A, Command Line Interface Commands xiii, 3-5WQ94 QMM10UGP SCRIPT

B-1 Appendix B, Event Classes and Rules xiii, 7-4NTEAEV QMM10UGP SCRIPT

B-2 NT Event Adapter EventsDMRULES QMM10UGP SCRIPT

B-5 Distributed Monitor (Sentry) Rules 4-8WQ122 QMM10UGP SCRIPT

C-1 Appendix C, Business and Component Descriptionsxiii, 7-9, F-10

WQ123 QMM10UGP SCRIPTD-1 Appendix D, Tivoli GEM Instrumentation Task Descriptions

xivICS QMM10UGP SCRIPT

/XRL/7

E-1 Appendix E, Instrumenting Connection Support to MSMQ xivWQ139 QMM10UGP SCRIPT

F-1 Appendix F, Finding and Correcting Problems xivSCHEDD QMM10UGP SCRIPT F-15 Scheduling MonitorsTASKNOT QMM10UGP SCRIPT F-16 Task NotesMONNOT QMM10UGP SCRIPT F-16 Monitor NotesDESKNOT QMM10UGP SCRIPT F-17 Desktop NotesGDFCT QMM10UGP SCRIPT

F-17 Tivoli GEM Instrumentation Limitations, and WorkaroundsWQ140 QMM10UGP SCRIPT

G-1 Appendix G, Messages xiv

Index Entries


PROXY QMM10UGP SCRIPT i (1) Application ProxyAPROXY QMM10UGP SCRIPT i (1) Application Proxy (2) installation 2-8WQ1 QMM10UGP SCRIPT i (1) Application Proxy (2) definition 2-6QMM307 QMM10UGP SCRIPT

i (1) attributes, MSMQ serverQMM308 QMM10UGP SCRIPT

i (1) attributes, MSMQ server(2) displaying, wgetmsmq command

A-2QMM309 QMM10UGP SCRIPT

i (1) attributes, MSMQ server(2) updating, wsetmsmq command

A-3AGGRESS QMM10UGP SCRIPT i (1) aggregate resourcesAGGRES1 QMM10UGP SCRIPT i (1) aggregate resources

(2) viewed on Tivoli GEM console 9-4AGGRES2 QMM10UGP SCRIPT i (1) aggregate resources

(2) navigating to specific resources 9-4QMM094 QMM10UGP SCRIPT i (1) authorization rolesADAUTH QMM10UGP SCRIPT i (1) authorization roles (2) description 1-3

/XRL/8

QMM447 QMM10UGP SCRIPT i (1) authorization roles (2) assigning i, iQMM095 QMM10UGP SCRIPT i (1) authorization roles (2) assigning

(3) for Manager for MQS 3-2QMM448 QMM10UGP SCRIPT i (1) authorization roles (2) assigning

(3) for Tivoli GEM instrumentation 7-7QMM586 QMM10UGP SCRIPT i (1) admintool command 7-11QMM320 QMM10UGP SCRIPT

i (1) business system description C-1BDF1 QMM10UGP SCRIPT

i (1) business description filesQMM618 QMM10UGP SCRIPT

i (1) business description files (2) installing C-1QMM619 QMM10UGP SCRIPT

i (1) business description files (2) contents C-2CDF1 QMM10UGP SCRIPT

i (1) component description filesQMM620 QMM10UGP SCRIPT

i (1) component description files (2) installing C-1QMM621 QMM10UGP SCRIPT

i (1) component description files (2) contents C-2QMM287 QMM10UGP SCRIPT i (1) commandsQMM288 QMM10UGP SCRIPT i (1) commands (2) wcrtmsmq A-1QMM289 QMM10UGP SCRIPT i (1) commands (2) wgetmsmq A-2QMM290 QMM10UGP SCRIPT i (1) commands (2) wsetmsmq A-3QMM590 QMM10UGP SCRIPT i (1) commands (2) wtemp

F-2, F-14, F-16QMM591 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-11QMM593 QMM10UGP SCRIPT i (1) commands (2) wlsrbrules

F-7, F-9, F-12QMM594 QMM10UGP SCRIPT i (1) commands (2) wtdumprl

F-7, F-8, F-9, F-12QMM595 QMM10UGP SCRIPT i (1) commands (2) winstall 2-12QMM596 QMM10UGP SCRIPT i (1) commands (2) admintool 7-11QMM472 QMM10UGP SCRIPT

i (1) client, Tivoli GEM, hints for using F-10QMM144 QMM10UGP SCRIPT i (1) creatingQMM299 QMM10UGP SCRIPT i (1) creating

(2) MSMQ server instance i, iQMM300 QMM10UGP SCRIPT i (1) creating

(2) MSMQ server instance (3) wcrtmsmq command A-1QMM097 QMM10UGP SCRIPT i (1) creating

(2) MSMQ server instance (3) from desktop 3-5QMM265 QMM10UGP SCRIPT i (1) configuringQMM266 QMM10UGP SCRIPT i (1) configuring (2) event server 2-6, 6-2QMM267 QMM10UGP SCRIPT i (1) configuring (2) event console 6-4QMM268 QMM10UGP SCRIPT i (1) configuring

(2) NT event adapter 6-5QMM084 QMM10UGP SCRIPT

i (1) configuring Manager for MQSQMM085 QMM10UGP SCRIPT

i (1) configuring Manager for MQS (2) overview 3-1QMM086 QMM10UGP SCRIPT

i (1) configuring Manager for MQS (2) authorization roles

/XRL/10

3-2CMDFL QMM10UGP SCRIPT i (1) data flow 2-2CNSOLES QMM10UGP SCRIPT i (1) consoleTOPCON QMM10UGP SCRIPT i (1) console (2) Tivoli GEM 7-3QMM484 QMM10UGP SCRIPT

i (1) components, installed, location ofQMM063 QMM10UGP SCRIPT

i (1) components, installed, location of(2) Manager for MQS

2-6QMM485 QMM10UGP SCRIPT

i (1) components, installed, location of(2) Tivoli GEM instrumentation

7-8QMM279 QMM10UGP SCRIPT i (1) Configure_Event_Adapter task 6-5QMM281 QMM10UGP SCRIPT i (1) Configure_Event_Console task 6-4QMM283 QMM10UGP SCRIPT i (1) Configure_Event_Server task 6-2QMM451 QMM10UGP SCRIPT

i (1) confirming server discovery on Tivoli GEM console 8-5QMM519 QMM10UGP SCRIPT i (1) Configure task 5-7QMM172 QMM10UGP SCRIPT

i (1) Distributed Transaction Coordinator Status monitor 4-7QMM452 QMM10UGP SCRIPT

i (1) discovery, server, on Tivoli GEM console 8-5QMM331 QMM10UGP SCRIPT i (1) Discover task 2-13QMM550 QMM10UGP SCRIPT i (1) Discover_Connections task 9-2QMM551 QMM10UGP SCRIPT i (1) Display_Enterprise task 9-2, 9-3QMM552 QMM10UGP SCRIPT i (1) Display_Site task 9-2, 9-3QMM249 QMM10UGP SCRIPT i (1) debuggingQMM251 QMM10UGP SCRIPT i (1) debugging (2) helpful information F-14QMM252 QMM10UGP SCRIPT i (1) debugging

(2) log files, location of

/XRL/11

F-14QMM207 QMM10UGP SCRIPT i (1) Display_Server_Status task 5-5, 9-2QMM208 QMM10UGP SCRIPT i (1) Display_Server_Info task 5-5, 9-2QMM209 QMM10UGP SCRIPT i (1) Display_MSMQ_Info task 5-5, 9-2QMM504 QMM10UGP SCRIPT i (1) Display_Instances task 5-5, 9-2QMM505 QMM10UGP SCRIPT i (1) Start_Services task 5-6, 9-2QMM506 QMM10UGP SCRIPT i (1) Stop_Services task 5-6, 9-2QMM507 QMM10UGP SCRIPT i (1) Purge_Dead_LetterQ task 5-6, 9-2QMM508 QMM10UGP SCRIPT i (1) List_Dead_LetterQ task 5-6, 9-2QMM119 QMM10UGP SCRIPT

i (1) determining server status 3-10QMM120 QMM10UGP SCRIPT

i (1) deleting an MSMQ server 3-10DBBCK QMM10UGP SCRIPT i (1) databaseDBBACK QMM10UGP SCRIPT i (1) database (2) backup 7-14CORUPTD QMM10UGP SCRIPT i (1) database (2) corrupted, remedy F-15DSUM QMM10UGP SCRIPT

i (1) Disk Usage by MSMQ Server monitor 4-7DMON QMM10UGP SCRIPT i (1) distributed monitoring 1-3, 1-3QMM439 QMM10UGP SCRIPT

i (1) distributing the heartbeat monitor 8-2QMM173 QMM10UGP SCRIPT

i (1) Event Adapter Status monitor 4-7QMM348 QMM10UGP SCRIPT i (1) executing tasksQMM205 QMM10UGP SCRIPT i (1) executing tasks

(2) Manager for MQS 5-2QMM384 QMM10UGP SCRIPT i (1) executing tasks

(2) Tivoli GEM instrumentation

/XRL/12

9-1, 9-7QMM116 QMM10UGP SCRIPT i (1) instances, MSMQ 3-4QMM009 QMM10UGP SCRIPT i (1) eventQMM316 QMM10UGP SCRIPT i (1) event (2) rules B-5QMM280 QMM10UGP SCRIPT i (1) event (2) console, configuring 6-4QMM269 QMM10UGP SCRIPT i (1) event (2) adapter, NT

i, i, iQMM050 QMM10UGP SCRIPT i (1) event (2) adapter, NT (3) requirements 2-5QMM270 QMM10UGP SCRIPT i (1) event (2) adapter, NT (3) configuring 6-5QMM271 QMM10UGP SCRIPT i (1) event (2) adapter, NT

(3) starting and stopping 6-6EVTCLAS QMM10UGP SCRIPT i (1) event (2) classes

i, i, i, iQMM310 QMM10UGP SCRIPT i (1) event (2) classes (3) distributed monitoring B-1QMM311 QMM10UGP SCRIPT i (1) event (2) classes (3) MSMQ_Monitors B-1QMM312 QMM10UGP SCRIPT i (1) event (2) classes

(3) NT event adapter B-2QMM313 QMM10UGP SCRIPT i (1) event (2) classes (3) MSMQ_Event B-2EVFILT QMM10UGP SCRIPT i (1) event (2) filtering 1-2, 6-7EVTFL QMM10UGP SCRIPT

/XRL/13

i (1) event (2) flow 2-2EVMGT QMM10UGP SCRIPT i (1) event (2) management

i, i, i, i, iQMM258 QMM10UGP SCRIPT i (1) event (2) management (3) overview 6-1QMM259 QMM10UGP SCRIPT i (1) event (2) management (3) authorization required 6-1QMM262 QMM10UGP SCRIPT i (1) event (2) management (3) console, configuring 6-4QMM263 QMM10UGP SCRIPT i (1) event (2) management (3) adapter, configuring 6-5QMM264 QMM10UGP SCRIPT i (1) event (2) management

(3) adapter, NT, starting and stopping 6-6QMM524 QMM10UGP SCRIPT i (1) event (2) monitoring 6-6QMM174 QMM10UGP SCRIPT

i (1) FalconMQ Server Status monitor 4-7QMM175 QMM10UGP SCRIPT

i (1) Free Disk Space Available monitor 4-7QMM323 QMM10UGP SCRIPT

i (1) field descriptions, tasks D-1FEATP QMM10UGP SCRIPT i (1) features, productQMM033 QMM10UGP SCRIPT i (1) features, product (2) distributed monitoring 1-3QMM034 QMM10UGP SCRIPT i (1) features, product (2) monitoring, distributed 1-3QMM025 QMM10UGP SCRIPT i (1) features, product (2) TEC 1-3QMM016 QMM10UGP SCRIPT i (1) features, product

(2) integration with Tivoli Management Framework

/XRL/14

i, 1-3QMM021 QMM10UGP SCRIPT i (1) features, product

(2) integration with Tivoli Management Framework (3) authorization 1-3, 1-3QMM014 QMM10UGP SCRIPT i (1) features, product (2) task libraries 1-3QMM010 QMM10UGP SCRIPT i (1) features, product (2) event filtering 1-2FILEVT QMM10UGP SCRIPT i (1) filtering events 1-2, 6-7FOREVT QMM10UGP SCRIPT

i (1) forwarding events to event server 2-6QMM176 QMM10UGP SCRIPT

i (1) Generic Performance monitor 4-7QMM122 QMM10UGP SCRIPT i (1) getting startedQMM426 QMM10UGP SCRIPT i (1) getting started

(2) with Tivoli GEM instrumentation i, iQMM428 QMM10UGP SCRIPT i (1) getting started

(2) with Tivoli GEM instrumentation(3) heartbeat monitor, subscribing and distributing

8-2QMM430 QMM10UGP SCRIPT i (1) getting started

(2) with Tivoli GEM instrumentation(3) resource discovery, confirming


(2) with Manager for MQSi, i, i, i, i, i, i

QMM124 QMM10UGP SCRIPT i (1) getting started

(2) with Manager for MQS (3) configuring, overview 3-1QMM125 QMM10UGP SCRIPT i (1) getting started

(2) with Manager for MQS(3) authorization roles, assigning


(2) with Manager for MQS(3) MSMQ server, managing


(2) with Manager for MQS(3) MSMQ server, creating

/XRL/15


(2) with Manager for MQS (3) instances, MSMQ 3-4QMM080 QMM10UGP SCRIPT i (1) getting started

(2) with Manager for MQS(3) server status, determining


(2) with Manager for MQS(3) MSMQ server, deleting

3-10HBEATM1 QMM10UGP SCRIPT i (1) Heartbeat monitorQMM436 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) distributing 8-2QMM437 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) subscribing 8-2WQ2 QMM10UGP SCRIPT i (1) Heartbeat monitor (2) description, MSSQLServer 9-10QMM438 QMM10UGP SCRIPT i (1) Heartbeat monitor

(2) description, MSMQ server 9-9QMM500 QMM10UGP SCRIPT i (1) icon color F-13QMM058 QMM10UGP SCRIPT i (1) interconnected TMRs 2-5QMM520 QMM10UGP SCRIPT i (1) Install task 2-14ICF1 QMM10UGP SCRIPT i (1) icon filesQMM622 QMM10UGP SCRIPT i (1) icon files (2) installing C-1QMM623 QMM10UGP SCRIPT i (1) icon files (2) contents C-2QMM147 QMM10UGP SCRIPT i (1) installationQMM248 QMM10UGP SCRIPT i (1) installation (2) hints F-1INSOPT QMM10UGP SCRIPT i (1) installation (2) options

/XRL/16

2-6INSTALL QMM10UGP SCRIPT i (1) installingINAVCL QMM10UGP SCRIPT i (1) installing (2) available clients

2-8, 2-11, 7-13INSMOD QMM10UGP SCRIPT i (1) installing

(2) Manager for MQSi, i, i, i, i

QMM070 QMM10UGP SCRIPT i (1) installing

(2) Manager for MQS (3) procedure 2-10QMM062 QMM10UGP SCRIPT i (1) installing

(2) Manager for MQS (3) checklist 2-6QMM068 QMM10UGP SCRIPT i (1) installing

(2) Manager for MQS (3) administrator authorization 1-3QMM065 QMM10UGP SCRIPT i (1) installing

(2) Manager for MQS(3) components, location of

2-6QMM047 QMM10UGP SCRIPT i (1) installing

(2) Manager for MQS(3) NT event adapter requirements

2-5INSTG1 QMM10UGP SCRIPT i (1) installing

(2) Tivoli GEM instrumentationi, i, i, i

QMM474 QMM10UGP SCRIPT i (1) installing

(2) Tivoli GEM instrumentation(3) components, location of

7-8QMM418 QMM10UGP SCRIPT i (1) installing

(2) Tivoli GEM instrumentation (3) management regions 7-7QMM419 QMM10UGP SCRIPT i (1) installing

(2) Tivoli GEM instrumentation (3) administrator authorization 7-7QMM421 QMM10UGP SCRIPT i (1) installing

(2) Tivoli GEM instrumentation (3) procedure 7-12JAVAKIT QMM10UGP SCRIPT

i (1) Java Development Kit

/XRL/17


i (1) log files, location of F-14LIBTSK QMM10UGP SCRIPT i (1) libraries, task 1-3QMM477 QMM10UGP SCRIPT

i (1) location of installed componentsQMM064 QMM10UGP SCRIPT

i (1) location of installed components(2) Manager for MQS


i (1) location of installed components(2) Tivoli GEM instrumentation

7-8QMM475 QMM10UGP SCRIPT i (1) listing tasksQMM204 QMM10UGP SCRIPT i (1) listing tasks

(2) Manager for MQS 5-2QMM476 QMM10UGP SCRIPT i (1) listing tasks

(2) Tivoli GEM instrumentation 9-1QMM314 QMM10UGP SCRIPT

i (1) MSMQ_Monitors event class B-1QMM178 QMM10UGP SCRIPT

i (1) MQ Test monitor 4-7QMM600 QMM10UGP SCRIPT i (1) Mqsvc monitor 4-6QMM601 QMM10UGP SCRIPT i (1) Msdtc monitor 4-6QMM602 QMM10UGP SCRIPT

i (1) MSMQ IS monitor 4-5QMM603 QMM10UGP SCRIPT

i (1) MSMQ Queue monitor 4-5QMM604 QMM10UGP SCRIPT

i (1) MSMQ Service monitor 4-6QMM605 QMM10UGP SCRIPT

i (1) MSMQ Session monitor 4-6WQ3 QMM10UGP SCRIPT

i (1) MSMQ monitor tasksPDLQ QMM10UGP SCRIPT

i (1) MSMQ monitor tasks (2) Purge_Dead_LetterQ 4-9RSRV QMM10UGP SCRIPT

i (1) MSMQ monitor tasks (2) Restart_Services 4-10QMM315 QMM10UGP SCRIPT

/XRL/18

i (1) MSMQ_Event event class B-2QMM117 QMM10UGP SCRIPT i (1) MSMQ instances 3-4QMM098 QMM10UGP SCRIPT i (1) MSMQ serverQMM301 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes i, iQMM305 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes

(3) displaying, wgetmsmq command A-2QMM306 QMM10UGP SCRIPT i (1) MSMQ server (2) attributes

(3) updating, wsetmsmq command A-3QMM296 QMM10UGP SCRIPT i (1) MSMQ server (2) creating i, iQMM297 QMM10UGP SCRIPT i (1) MSMQ server (2) creating (3) from desktop 3-5QMM298 QMM10UGP SCRIPT i (1) MSMQ server (2) creating (3) wcrtmsmq command A-1QMM099 QMM10UGP SCRIPT i (1) MSMQ server (2) managing 3-3QMM100 QMM10UGP SCRIPT i (1) MSMQ server (2) instances, creating 3-5QMM101 QMM10UGP SCRIPT i (1) MSMQ server

(2) icon pull-down tasks 3-8QMM102 QMM10UGP SCRIPT i (1) MSMQ server (2) endpoints, MSMQ 3-4QMM103 QMM10UGP SCRIPT i (1) MSMQ server (2) status, determining 3-10QMM104 QMM10UGP SCRIPT i (1) MSMQ server (2) deleting 3-10QMM105 QMM10UGP SCRIPT i (1) MSMQ server (2) profile managers

/XRL/19

3-11QMM037 QMM10UGP SCRIPT i (1) monitoring, distributed 1-3MANAGE QMM10UGP SCRIPT i (1) managementQMM055 QMM10UGP SCRIPT i (1) management (2) regions, requirements 2-5QMM222 QMM10UGP SCRIPT i (1) management (2) tasks

i, i, i, i, i, i, i, iQMM464 QMM10UGP SCRIPT i (1) management (2) tasks

(3) running from the desktop, hints F-3QMM465 QMM10UGP SCRIPT i (1) management (2) tasks

(3) running from the Tivoli GEM console, hints F-4QMM255 QMM10UGP SCRIPT i (1) management (2) tasks

(3) log files, location of F-14QMM223 QMM10UGP SCRIPT i (1) management (2) tasks (3) listing 5-2QMM224 QMM10UGP SCRIPT i (1) management (2) tasks (3) running 5-2, 9-1QMM225 QMM10UGP SCRIPT i (1) management (2) tasks

(3) authorization required, Manager for MQS 5-4QMM495 QMM10UGP SCRIPT i (1) management (2) tasks

(3) authorization required, Tivoli GEM instrumentation 7-7QMM242 QMM10UGP SCRIPT i (1) management (2) tasks (3) overview 5-1MEXA1 QMM10UGP SCRIPT

i (1) msmq_admin TMR role 1-3, 3-2MEXS1 QMM10UGP SCRIPT

i (1) msmq_senior TMR role 1-3, 3-2MNTRS 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, iQMM160 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Special Queue Count 4-7QMM161 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Generic Performance 4-7QMM162 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Free Disk Space Available 4-7QMM163 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Disk Usage by MSMQ Server 4-7QMM164 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MQ Test 4-7QMM166 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Event Adapter Status 4-7QMM167 QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) MSMQ Server Status 4-7MSMQIS QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ IS 4-5MSMQQ QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Queue 4-5MSMQSRV QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Service 4-6MSMQSES QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) MSMQ Session 4-6MQSVC QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

/XRL/21

(3) Mqsvc 4-6Q2QGW QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Q2qgw 4-6MSDTC QMM10UGP SCRIPT i (1) monitors (2) MSMQ server (3) Msdtc 4-6QMAX QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Special Queue Maximum Time 4-7DTCSTAT QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) Distributed Transaction Coordinator Status 4-7FMQSTAT QMM10UGP SCRIPT i (1) monitors (2) MSMQ server

(3) FalconMQ Server Status 4-7QMM405 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-5QMM406 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSMQ server) (3) Heartbeat 9-9QMM411 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSMQ server) (3) State 9-9QMM412 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSMQ server)(3) Manager for MQS-supported

9-9MONTHRE QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSMQ server) (3) thresholding 9-10QMM408 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSMQ server) (3) scheduling F-15WQ5 QMM10UGP SCRIPT

/XRL/22

i (1) monitors(2) Tivoli GEM instrumentation (MSSQLServer)

i, iWQ6 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSSQLServer) (3) Heartbeat 9-10WQ7 QMM10UGP SCRIPT i (1) monitors

(2) Tivoli GEM instrumentation (MSSQLServer) (3) State 9-10QMM257 QMM10UGP SCRIPT i (1) monitors

(2) log files, location of F-14QMM488 QMM10UGP SCRIPT i (1) monitors (2) listing i, iQMM151 QMM10UGP SCRIPT i (1) monitors (2) listing

(3) Manager for MQS 4-1QMM489 QMM10UGP SCRIPT i (1) monitors (2) listing

(3) Tivoli GEM instrumentation 9-11MNTRS1 QMM10UGP SCRIPT i (1) monitors (2) performance 4-5QMM467 QMM10UGP SCRIPT i (1) monitors

(2) hints for using F-5QMM523 QMM10UGP SCRIPT i (1) monitors (2) queue 4-7, 4-7MULTMRS QMM10UGP SCRIPT i (1) multiple TMRs 2-5QMM051 QMM10UGP SCRIPT

i (1) NT event adapterNTEASM QMM10UGP SCRIPT

i (1) NT event adapter(2) Event Adapter Status monitor


i (1) NT event adapter (2) requirements 2-5QMM272 QMM10UGP SCRIPT

i (1) NT event adapter (2) configuring 6-5QMM273 QMM10UGP SCRIPT

i (1) NT event adapter

/XRL/23

(2) starting and stopping 6-6QMM121 QMM10UGP SCRIPT

i (1) profile managers, subscriber list 3-11QMM038 QMM10UGP SCRIPT

i (1) planning for installationQMM039 QMM10UGP SCRIPT

i (1) planning for installation (2) overview

i, i, i, 2-1QMM048 QMM10UGP SCRIPT

i (1) planning for installation (2) overview

(3) NT event adapter 2-5QMM053 QMM10UGP SCRIPT

i (1) planning for installation (2) overview (3) management regions 2-5QMM054 QMM10UGP SCRIPT

i (1) planning for installation (2) overview (3) TMR 2-5QMM059 QMM10UGP SCRIPT

i (1) planning for installation (2) event server 2-6PERFCM QMM10UGP SCRIPT i (1) performance counters 4-7QMM152 QMM10UGP SCRIPT i (1) performance monitorsPERFM QMM10UGP SCRIPT i (1) performance monitors (2) description 4-5QMM154 QMM10UGP SCRIPT i (1) performance monitors (2) listing 4-1PFEAT QMM10UGP SCRIPT i (1) product featuresQMM035 QMM10UGP SCRIPT i (1) product features (2) distributed monitoring 1-3QMM036 QMM10UGP SCRIPT i (1) product features (2) monitoring, distributed 1-3QMM017 QMM10UGP SCRIPT i (1) product features

(2) integration with Tivoli Management Framework i, 1-3QMM022 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-3QMM028 QMM10UGP SCRIPT i (1) product features

(2) event display, consolidated 1-3QMM015 QMM10UGP SCRIPT i (1) product features (2) task libraries 1-3QMM011 QMM10UGP SCRIPT i (1) product features (2) event filtering 1-2QMM606 QMM10UGP SCRIPT i (1) Q2qgw monitor 4-6QMM339 QMM10UGP SCRIPT i (1) Query_State task 9-3QMM553 QMM10UGP SCRIPT i (1) Query_Threshold_Settings task 9-2, 9-3QMM572 QMM10UGP SCRIPT i (1) Query_Thresholds task 9-2, 9-3QMM566 QMM10UGP SCRIPT i (1) Query_State task 9-2QMM567 QMM10UGP SCRIPT i (1) Query_Values task 9-2, 9-3QMM450 QMM10UGP SCRIPT

i (1) resource discovery on Tivoli GEM console 8-5QMM434 QMM10UGP SCRIPT i (1) rules, eventQMM317 QMM10UGP SCRIPT i (1) rules, event

(2) Manager for MQS B-5QMM442 QMM10UGP SCRIPT i (1) rules, event

(2) heartbeat monitor, subscribing and distributing 8-2QMM449 QMM10UGP SCRIPT i (1) rules, event

(2) resource discovery, confirming 8-5QMM521 QMM10UGP SCRIPT i (1) resource roles 3-3QMM480 QMM10UGP SCRIPT i (1) running tasksQMM206 QMM10UGP SCRIPT i (1) running tasks

(2) Manager for MQS 5-2QMM481 QMM10UGP SCRIPT i (1) running tasks

/XRL/25

(2) Tivoli GEM instrumentation 9-7RUNCLII QMM10UGP SCRIPT i (1) running tasks

(2) running from Tivoli GEM console, recommended 9-1QMM043 QMM10UGP SCRIPT i (1) requirementsQMM049 QMM10UGP SCRIPT i (1) requirements

(2) NT event adapter 2-5QMM057 QMM10UGP SCRIPT i (1) requirements (2) management regions 2-5QMM482 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization i, iQMM069 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization

(3) Manager for MQS 1-3QMM483 QMM10UGP SCRIPT i (1) requirements (2) administrator authorization

(3) Tivoli GEM instrumentation 7-7QMM607 QMM10UGP SCRIPT

i (1) Special Queue Count monitor 4-7QMM608 QMM10UGP SCRIPT

i (1) Special Queue Maximum Time monitor 4-7QMM610 QMM10UGP SCRIPT

i (1) State monitor (MSMQ server) 9-9QMM611 QMM10UGP SCRIPT

i (1) State monitor (MSSQLServer) 9-10QMM410 QMM10UGP SCRIPT

i (1) scheduling Tivoli GEM instrumentation monitors F-15QMM344 QMM10UGP SCRIPT i (1) Start task 9-1QMM345 QMM10UGP SCRIPT i (1) Stop task 9-1QMM274 QMM10UGP SCRIPT i (1) Start_Event_Adapter task 6-6QMM275 QMM10UGP SCRIPT i (1) Stop_Event_Adapter task 6-6QMM218 QMM10UGP SCRIPT i (1) Start_Debugging task 5-8, 9-2QMM219 QMM10UGP SCRIPT i (1) Stop_Debugging task

/XRL/26

5-8, 9-2QMM220 QMM10UGP SCRIPT i (1) Start_Monitors task 5-9, 9-2QMM221 QMM10UGP SCRIPT i (1) Stop_Monitors task 5-9, 9-2QMM554 QMM10UGP SCRIPT i (1) Set_Pulse task 9-2, 9-3QMM568 QMM10UGP SCRIPT i (1) Set_Polling_Interval task 9-2, 9-3QMM569 QMM10UGP SCRIPT i (1) Set_Thresholds task 9-2, 9-3QMM570 QMM10UGP SCRIPT i (1) Start task 9-3QMM571 QMM10UGP SCRIPT i (1) Stop task 9-3QMM106 QMM10UGP SCRIPT i (1) server, MSMQQMM302 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes i, iQMM303 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes

(3) displaying, wgetmsmq command A-2QMM304 QMM10UGP SCRIPT i (1) server, MSMQ (2) attributes

(3) updating, wsetmsmq command A-3QMM107 QMM10UGP SCRIPT i (1) server, MSMQ (2) managing 3-3QMM294 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating i, iQMM108 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating (3) from desktop 3-5QMM295 QMM10UGP SCRIPT i (1) server, MSMQ (2) creating (3) wcrtmsmq command A-1QMM109 QMM10UGP SCRIPT i (1) server, MSMQ

(2) icon pull-down tasks 3-8QMM110 QMM10UGP SCRIPT i (1) server, MSMQ

/XRL/27

(2) endpoints, MSMQ 3-4QMM522 QMM10UGP SCRIPT i (1) server, MSMQ

(2) subscribing to a profile manager 3-11QMM111 QMM10UGP SCRIPT i (1) server, MSMQ (2) status, determining 3-10QMM112 QMM10UGP SCRIPT i (1) server, MSMQ (2) deleting 3-10QMM113 QMM10UGP SCRIPT i (1) server, MSMQ (2) profile manager 3-11QMM168 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors

i, i, iQMM170 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) listing 4-1QMM171 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) performance 4-5QMM177 QMM10UGP SCRIPT i (1) server, MSMQ (2) monitors (3) performance counters 4-7SQLSRV 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-4SQLMON QMM10UGP SCRIPT i (1) server, MSSQLServer (2) monitors 9-9SQLTSK QMM10UGP SCRIPT i (1) server, MSSQLServer (2) tasks 9-3SERVSM QMM10UGP SCRIPT

i (1) MSMQ Server Status monitor 4-7SRVTMR QMM10UGP SCRIPT i (1) server, TMR 2-2SRVTOP QMM10UGP SCRIPT

i (1) server, Tivoli GEM 7-2QMM440 QMM10UGP SCRIPT

i (1) subscribing the heartbeat monitor 8-2QMM473 QMM10UGP SCRIPT

i (1) Tivoli GEM hints for using

/XRL/28

F-10QMM615 QMM10UGP SCRIPT

i (1) Tivoli GEM console 7-3QMM616 QMM10UGP SCRIPT

i (1) Tivoli GEM server 7-2QMM617 QMM10UGP SCRIPT i (1) tear-away log 9-7QMM324 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentationGEMEVHD QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) event handling 7-3GEMIC QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) instrumented components 7-4GEMINIT QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) initializing 8-1QMM422 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing

i, i, i, iQMM423 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing (3) authorization required 7-7QMM425 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing (3) procedure 7-12WQ8 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing (3) components 7-8INSTJDK QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing

(3) Java Development Kit 7-9QMM417 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) management regions 7-7QMM413 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing iGINST2 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) installing (3) overview 7-1QMM400 QMM10UGP SCRIPT

/XRL/29

i (1) Tivoli GEM instrumentation (2) monitors

i, i, iQMM468 QMM10UGP SCRIPT


(3) hints for using F-5QMM402 QMM10UGP SCRIPT


(3) supported Manager for MQS 9-9QMM404 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) monitors (3) scheduling F-15QMM325 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) tasks

i, i, iQMM326 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) tasks (3) field descriptions D-1QMM380 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) tasks (3) locating 9-1QMM381 QMM10UGP SCRIPT

i (1) Tivoli GEM instrumentation (2) tasks (3) running 9-1, 9-7QMM243 QMM10UGP SCRIPT i (1) troubleshootingQMM455 QMM10UGP SCRIPT i (1) troubleshooting (2) hints

i, i, i, i, i, i, iQMM456 QMM10UGP SCRIPT i (1) troubleshooting (2) hints

(3) tasks and jobs, running from the desktop F-3QMM499 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) icon color F-13QMM457 QMM10UGP SCRIPT i (1) troubleshooting (2) hints

(3) tasks and jobs, running from the Tivoli GEM console F-4QMM458 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) monitors, using

/XRL/30

F-5QMM459 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) TEC, using F-8QMM460 QMM10UGP SCRIPT i (1) troubleshooting (2) hints

(3) Tivoli GEM client, using F-10QMM244 QMM10UGP SCRIPT i (1) troubleshooting (2) hints (3) installation F-1QMM246 QMM10UGP SCRIPT i (1) troubleshooting (2) debugging information F-14QMM247 QMM10UGP SCRIPT i (1) troubleshooting (2) log files F-14QMM180 QMM10UGP SCRIPT i (1) tasksQMM461 QMM10UGP SCRIPT i (1) tasks (2) hints i, iQMM462 QMM10UGP SCRIPT i (1) tasks (2) hints

(3) running from the desktop F-3QMM463 QMM10UGP SCRIPT i (1) tasks (2) hints

(3) running from the Tivoli GEM console F-4QMM498 QMM10UGP SCRIPT i (1) tasks (2) field descriptions D-1QMM327 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-1QMM383 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) running 9-1, 9-7QMM350 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_State

/XRL/31

9-1, 9-2QMM351 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_Thresholds 9-1, 9-2QMM352 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Query_Values 9-1, 9-2QMM353 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Polling_Interval 9-1, 9-2QMM354 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Thresholds 9-1, 9-2QMM355 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Services 9-1, 9-2QMM356 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Services 9-1, 9-2QMM357 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Discover_Connections 9-2QMM358 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Enterprise 9-2QMM359 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Site 9-2QMM360 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Set_Pulse 9-2QMM361 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Instances 9-2QMM362 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_Server_Status 9-2QMM363 QMM10UGP SCRIPT

/XRL/32

i (1) tasks(2) Tivoli GEM instrumentation (MSMQ server component)

(3) Display_Server_Info 9-2QMM364 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Display_MSMQ_Info 9-2QMM365 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) List_Dead_LetterQ 9-2QMM366 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Purge_Dead_LetterQ 9-2QMM367 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Monitors 9-2QMM368 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Monitors 9-2QMM369 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Start_Debugging 9-2QMM370 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSMQ server component) (3) Stop_Debugging 9-2QMM531 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-3QMM533 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Display_Site 9-3QMM534 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_State 9-3QMM535 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Threshold_Settings

/XRL/33

9-3QMM536 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Thresholds 9-3QMM537 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Query_Values 9-3QMM538 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Polling_Interval 9-3QMM539 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Pulse 9-3QMM540 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Set_Thresholds 9-3QMM541 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Start 9-3QMM542 QMM10UGP SCRIPT i (1) tasks

(2) Tivoli GEM instrumentation (MSSQLServer component) (3) Stop 9-3QMM254 QMM10UGP SCRIPT i (1) tasks

(2) log files, location of F-14QMM181 QMM10UGP SCRIPT i (1) tasks (2) overview 5-1QMM182 QMM10UGP SCRIPT i (1) tasks (2) listing 5-2QMM183 QMM10UGP SCRIPT i (1) tasks (2) running 5-2QMM184 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server

i, i, i, i, i, i, i, i, iQMM185 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) authorization required 5-4QMM186 QMM10UGP SCRIPT

/XRL/34

i (1) tasks (2) MSMQ server (3) Display_Server_Status 5-5QMM187 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_Server_Info 5-5QMM188 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_MSMQ_Info 5-5QMM514 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Display_Instances 5-5QMM515 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Start_Services 5-6QMM516 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Stop_Services 5-6QMM517 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) Purge_Dead_LetterQ 5-6QMM518 QMM10UGP SCRIPT i (1) tasks (2) MSMQ server (3) List_Dead_LetterQ 5-6QMM198 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility

i, i, i, i, i, i, i, iQMM199 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) authorization required 5-7QMM200 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Start_Debugging 5-8QMM201 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Stop_Debugging 5-8QMM202 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Start_Monitors

/XRL/35

5-9QMM203 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Stop_Monitors 5-9QMM501 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Install 2-14QMM502 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Configure 5-7QMM503 QMM10UGP SCRIPT i (1) tasks (2) MSMQ utility (3) Discover 2-13QMM530 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC

i, i, i, i, iQMM284 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Server 6-2QMM285 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Console 6-4QMM278 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Configure_Event_Adapter 6-5QMM525 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Start_Event_Adapter 6-6QMM526 QMM10UGP SCRIPT i (1) tasks (2) MSMQ TEC (3) Stop_Event_Adapter 6-6EVSRV QMM10UGP SCRIPT i (1) event serverQMM469 QMM10UGP SCRIPT i (1) event server

(2) hints for using F-8EVSRV1 QMM10UGP SCRIPT i (1) event server (2) configuring 2-6, 6-2TSKLIB QMM10UGP SCRIPT i (1) task libraries

/XRL/36

1-3TCON QMM10UGP SCRIPT i (1) TEC console 1-3TIVOLI QMM10UGP SCRIPT i (1) TivoliQMM018 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration withi, i, i, i

QMM019 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) overview 1-3QMM024 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) authorization 1-3, 1-3QMM031 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) TEC 1-3QMM032 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) event display 1-3TMEAUT QMM10UGP SCRIPT i (1) Tivoli (2) authorization 1-3TMEECON QMM10UGP SCRIPT i (1) Tivoli (2) enterprise console 1-3TMEDMON QMM10UGP SCRIPT i (1) Tivoli (2) distributed monitoring 1-3, 1-3TMR QMM10UGP SCRIPT i (1) TMRQMM056 QMM10UGP SCRIPT i (1) TMR (2) requirements 2-5TMR1 QMM10UGP SCRIPT i (1) TMR (2) rolesTMR1A QMM10UGP SCRIPT i (1) TMR (2) roles (3) msmq_admin 1-3, 3-2TMR1B QMM10UGP SCRIPT i (1) TMR (2) roles (3) msmq_senior 1-3, 3-2TMR2 QMM10UGP SCRIPT

/XRL/37

i (1) TMR (2) server 2-2TMRSMUL QMM10UGP SCRIPT i (1) TMR (2) multiple 2-5QMM379 QMM10UGP SCRIPT i (1) wpostemsg F-2QMM291 QMM10UGP SCRIPT i (1) wcrtmsmq command A-1QMM292 QMM10UGP SCRIPT i (1) wgetmsmq command A-2QMM293 QMM10UGP SCRIPT i (1) wsetmsmq command A-3QMM580 QMM10UGP SCRIPT i (1) wtemp command

F-2, F-14, F-16QMM581 QMM10UGP SCRIPT i (1) wlscurrb command

F-6, F-8, F-11QMM582 QMM10UGP SCRIPT i (1) wlsrbclass command

F-6, F-8, F-11QMM583 QMM10UGP SCRIPT i (1) wlsrbrules command

F-7, F-9, F-12QMM584 QMM10UGP SCRIPT i (1) wtdumprl command

F-7, F-8, F-9, F-12QMM585 QMM10UGP SCRIPT i (1) winstall command 2-12WQX13 QMM10UGP SCRIPT i (1) console 1-3WQX14 QMM10UGP SCRIPT i (1) TivoliWQX15 QMM10UGP SCRIPT i (1) Tivoli (2) enterprise console 1-4WQX16 QMM10UGP SCRIPT

i (1) integration with Tivoli Management FrameworkWQX17 QMM10UGP SCRIPT

i (1) integration with Tivoli Management Framework (2) TEC 1-4WQX18 QMM10UGP SCRIPT

i (1) integration with Tivoli Management FrameworkWQX19 QMM10UGP SCRIPT

i (1) integration with Tivoli Management Framework (2) event display 1-4WQX20 QMM10UGP SCRIPT i (1) TEC console 1-4WQX21 QMM10UGP SCRIPT

/XRL/38

i (1) features, productWQX22 QMM10UGP SCRIPT i (1) features, product (2) TEC 1-4WQX23 QMM10UGP SCRIPT i (1) product featuresWQX24 QMM10UGP SCRIPT i (1) product features (2) TEC 1-4WQX25 QMM10UGP SCRIPT i (1) features, productWQX26 QMM10UGP SCRIPT i (1) features, product

(2) event display, consolidated 1-4WQX27 QMM10UGP SCRIPT i (1) product featuresWQX28 QMM10UGP SCRIPT i (1) product features

(2) event display, consolidated 1-4WQX29 QMM10UGP SCRIPT i (1) consoleWQX30 QMM10UGP SCRIPT i (1) console (2) TEC 1-4WQX31 QMM10UGP SCRIPT i (1) TivoliWQX32 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration withWQX33 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) TEC 1-4WQX34 QMM10UGP SCRIPT i (1) TivoliWQX35 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration withWQX36 QMM10UGP SCRIPT i (1) Tivoli

(2) framework, integration with (3) event display 1-4WQX37 QMM10UGP SCRIPT i (1) TivoliWQX38 QMM10UGP SCRIPT i (1) Tivoli (2) distributed monitoring 1-4WQX39 QMM10UGP SCRIPT i (1) distributed monitoring 1-4WQX40 QMM10UGP SCRIPT i (1) monitoring, distributed 1-4WQX41 QMM10UGP SCRIPT

/XRL/39

i (1) features, productWQX42 QMM10UGP SCRIPT i (1) features, product (2) distributed monitoring 1-4WQX43 QMM10UGP SCRIPT i (1) product featuresWQX44 QMM10UGP SCRIPT i (1) product features (2) distributed monitoring 1-4WQX45 QMM10UGP SCRIPT i (1) features, productWQX46 QMM10UGP SCRIPT i (1) features, product (2) monitoring, distributed 1-4WQX47 QMM10UGP SCRIPT i (1) product featuresWQX48 QMM10UGP SCRIPT i (1) product features (2) monitoring, distributed 1-4WQX51 QMM10UGP SCRIPT i (1) dialogsWQX52 QMM10UGP SCRIPT i (1) dialogs (2) install product 2-7

List Items


SELARG QMM10UGP SCRIPT 4-3 6

/XRL/40

Processing Options

Runtime values:Document fileid .................................................................................................. QMM10UGP SCRIPTDocument type ................................................................................................... USERDOCDocument style ................................................................................................... TIVOLIProfile ................................................................................................................. EDFPRF40Service Level ...................................................................................................... 0032SCRIPT/VS Release ........................................................................................... 4.0.0Date ..................................................................................................................... 99.04.07Time .................................................................................................................... 08:20:13Device ................................................................................................................. PSANumber of Passes ............................................................................................... 4Index ................................................................................................................... YESSYSVAR G ........................................................................................................ INLINESYSVAR X ........................................................................................................ YES

Formatting values used:Annotation .......................................................................................................... NOCross reference listing ........................................................................................ YESCross reference head prefix only ....................................................................... NODialog ................................................................................................................. LABELDuplex ................................................................................................................ YESDVCF 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 ............................................................................................................... NOFigure list on new page ..................................................................................... YESFigure/table number separation .......................................................................... YESFolio-by-chapter ................................................................................................. YESHead 0 body text ................................................................................................ (none)Head 1 body text ................................................................................................ ChapterHead 1 appendix text ......................................................................................... AppendixHyphenation ........................................................................................................ NOJustification ......................................................................................................... NOLanguage ............................................................................................................ ENGLKeyboard ............................................................................................................ 395Layout ................................................................................................................. OFFLeader dots ......................................................................................................... YESMaster index ....................................................................................................... (none)Partial TOC (maximum level) ........................................................................... 4Partial TOC (new page after) ............................................................................ INLINEPrint example id's ............................................................................................... NOPrint cross reference page numbers ................................................................... YESProcess value ...................................................................................................... (none)Punctuation move characters ............................................................................. .,Read cross-reference file .................................................................................... (none)Running heading/footing rule ............................................................................ NONEShow index entries ............................................................................................. NOTable of Contents (maximum level) .................................................................. 3Table list on new page ....................................................................................... YES

/XRL/41

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