ibm tivoli monitoring for databases: microsoft sql server...

IBM Tivoli Monitoring for Databases: Microsoft SQLServer

User’s GuideVersion 5.1.1

SC23-4853-00

��

NoteBefore using this information and the product it supports, read the information in Appendix G, “Notices”, on page 141.

First Edition (March 2003)

This edition applies to version 5.1.1 of IBM Tivoli Monitoring for Databases: Microsoft SQL Server and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2003. All rights reserved. US Government UsersRestricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this guide . . . . . . . . . . . vWho should read this guide . . . . . . . . . vWhat this guide contains . . . . . . . . . . vPublications . . . . . . . . . . . . . . vi

IBM Tivoli Monitoring for Databases: MicrosoftSQL Server library . . . . . . . . . . . viRelated publications . . . . . . . . . . viiAccessing publications online . . . . . . . viiiOrdering publications . . . . . . . . . viii

Accessibility . . . . . . . . . . . . . . viiiContacting software support . . . . . . . . viiiConventions used in this book . . . . . . . . ix

Typeface conventions . . . . . . . . . . ixOperating system-dependent variables and paths ix

Chapter 1. Overview . . . . . . . . . 1Understanding IBM Tivoli Monitoring . . . . . . 1Overview of extensions to the Tivoli environment . . 8Tivoli administrators. . . . . . . . . . . . 9Authorization roles . . . . . . . . . . . . 9Microsoft SQL Server endpoints . . . . . . . . 9Using the desktop or CLI. . . . . . . . . . 10

Chapter 2. Getting startedquick-reference guide . . . . . . . . 11

Chapter 3. Setting up IBM TivoliMonitoring for Databases: MicrosoftSQL Server . . . . . . . . . . . . . 13Starting the Tivoli environment . . . . . . . . 13Setting authorization roles . . . . . . . . . 15Subscribing to notice groups. . . . . . . . . 17Specifying the managed resource types in a policyregion . . . . . . . . . . . . . . . . 19Registering servers using Discovery . . . . . . 22Registering database servers manually . . . . . 26

Chapter 4. Setting up IBM TivoliMonitoring . . . . . . . . . . . . . 29Suggested guidelines for setting up your resourcemodels . . . . . . . . . . . . . . . . 29Creating profile managers and profiles . . . . . 30Subscribing resources to profile managers . . . . 32Adding default resource models to profiles . . . . 33Distributing profiles from the desktop . . . . . 34Distributing profiles using MDist2 . . . . . . . 36Rerunning failed profile distributions . . . . . . 38

Chapter 5. Working with IBM TivoliMonitoring for Databases: MicrosoftSQL Server . . . . . . . . . . . . . 41Viewing server properties . . . . . . . . . 41Editing server properties . . . . . . . . . . 42

Starting a server . . . . . . . . . . . . . 44Shutting down a server . . . . . . . . . . 49

Chapter 6. Working with tasks and jobs 57Running a task . . . . . . . . . . . . . 58Customizing a task . . . . . . . . . . . . 61Creating a job . . . . . . . . . . . . . 62Running a job . . . . . . . . . . . . . 65Scheduling a job . . . . . . . . . . . . . 66

Chapter 7. Viewing resource modelresults with the IBM Tivoli MonitoringWeb Health Console . . . . . . . . . 71Understanding resource health . . . . . . . . 71Connecting the IBM Tivoli Monitoring Web HealthConsole. . . . . . . . . . . . . . . . 72

Chapter 8. Customizing resourcemodels. . . . . . . . . . . . . . . 73Overview of IBM Tivoli Monitoring . . . . . . 73Customizing indications . . . . . . . . . . 74Adding custom resource models to profiles. . . . 76Adding or removing built-in actions . . . . . . 77Editing a built-in action . . . . . . . . . . 79Specifying tasks for an event . . . . . . . . 81Sending a notice to administrators when an eventoccurs . . . . . . . . . . . . . . . . 83Customizing parameters . . . . . . . . . . 84Creating scheduling rules. . . . . . . . . . 85Customizing the scheduling monitoring period . . 87Customizing data logging information . . . . . 89Managing profiles and resource models at endpoints 91Managing IBM Tivoli Monitoring gateways. . . . 92Determining which resource models have beendistributed to endpoints . . . . . . . . . . 93Determining which resource models are running onendpoints . . . . . . . . . . . . . . . 94

Chapter 9. Enabling IBM TivoliMonitoring for Databases: MicrosoftSQL Server for Tivoli Enterprise DataWarehouse . . . . . . . . . . . . . 95Overview . . . . . . . . . . . . . . . 95

Control server . . . . . . . . . . . . 95Central data warehouse . . . . . . . . . 96Data marts . . . . . . . . . . . . . 96Report interface . . . . . . . . . . . . 96

Tivoli Enterprise Data Warehouse reports . . . . 97Accessing the IBM Console . . . . . . . . . 98Creating an IBM Console user . . . . . . . . 98Assigning roles to a user . . . . . . . . . . 99Creating a user group . . . . . . . . . . 100Assigning users to a user group . . . . . . . 100Assigning user groups to a data mart . . . . . 101

iii

Running reports . . . . . . . . . . . . 101Scheduling reports to run automatically . . . . 102Modifying default settings for reports . . . . . 102Creating reports . . . . . . . . . . . . 103IBM Tivoli Monitoring for Databases: MicrosoftSQL Server data marts and reports . . . . . . 104

Appendix A. Authorization roles quickreference . . . . . . . . . . . . . 107

Appendix B. Setting up TivoliEnterprise Console . . . . . . . . . 109Overview of Tivoli Enterprise Console . . . . . 109Configuring Tivoli Enterprise Console to work withIBM Tivoli Monitoring for Databases: MicrosoftSQL Server . . . . . . . . . . . . . . 110Viewing events in Tivoli Enterprise Console . . . 114

Appendix C. Integrating with TivoliBusiness Systems Manager . . . . . 117Understanding Tivoli Business Systems Manager 117Integrating IBM Tivoli Monitoring for Databases:Microsoft SQL Server into Tivoli Business SystemsManager . . . . . . . . . . . . . . . 118Integrating IBM Tivoli Monitoring for Databases:Microsoft SQL Server with Tivoli Business SystemsManager . . . . . . . . . . . . . . . 118

Configuring the Tivoli Enterprise Console eventserver . . . . . . . . . . . . . . . . 119Discovering resources for Tivoli Business SystemsManager . . . . . . . . . . . . . . . 120Working with Tivoli Business Systems Manager 121Uninstalling IBM Tivoli Monitoring for Databases:Microsoft SQL Server integration from TivoliBusiness Systems Manager . . . . . . . . . 121

Appendix D. Problem determination 123Frequently asked questions . . . . . . . . . 123

Resource models . . . . . . . . . . . 123Connectivity and authorization . . . . . . 124Miscellaneous . . . . . . . . . . . . 125

Appendix E. Messages . . . . . . . 129

Appendix F. Accessibility . . . . . . 139Using assistive technologies . . . . . . . . 139Magnifying what is displayed on the screen . . . 139Documentation in accessible formats . . . . . 139Using alternative text. . . . . . . . . . . 140

Appendix G. Notices . . . . . . . . 141Trademarks . . . . . . . . . . . . . . 143

Index . . . . . . . . . . . . . . . 145

iv IBM Tivoli Monitoring for Databases: Microsoft SQL Server: User’s Guide

About this guide

The IBM Tivoli Monitoring for Databases: Microsoft SQL Server User’s Guide describeshow to use the IBM Tivoli Monitoring for Databases: Microsoft SQL Serversoftware to manage Microsoft SQL Server resources with Tivoli Enterprisesoftware. In addition to the configuration material, this guide also provides aproblem determination section to provide assistance when troubleshooting.

Who should read this guideThis book is for system administrators and database administrators. It explains theconcepts you should know to use the IBM Tivoli Monitoring for Databases:Microsoft SQL Server product. It contains information about database managementusing this product and how IBM Tivoli Monitoring for Databases: Microsoft SQLServer is integrated into the Tivoli environment.

Readers should be familiar with the following:v Windows ® or UNIX® operating systemsv Tivoli environmentv Microsoft SQL Server database administration

What this guide containsThis guide contains the following sections:v Chapter 1, “Overview”, on page 1

Provides an overview of IBM Tivoli Monitoring for Databases: Microsoft SQLServer features, its extensions to other Tivoli products, authorization roles, andthe Microsoft SQL Server database as an endpoint.

v Chapter 2, “Getting started quick-reference guide”, on page 11Provides an overview of the setup tasks for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server, including cross-references to additionalinformation.

v Chapter 3, “Setting up IBM Tivoli Monitoring for Databases: Microsoft SQLServer”, on page 13Provides procedures for subscribing to notice groups, adding managed resourcetypes to a policy region, and discovering and registering databases.

v Chapter 4, “Setting up IBM Tivoli Monitoring”, on page 29Provides procedures for setting up IBM Tivoli Monitoring to work with IBMTivoli Monitoring for Databases: Microsoft SQL Server.

v Chapter 5, “Working with IBM Tivoli Monitoring for Databases: Microsoft SQLServer”, on page 41Provides procedures for opening a database endpoint, viewing and editingdatabase properties, starting and shutting down a database, checking the state ofthe database, and viewing events in the Tivoli Enterprise Console product.

v Chapter 6, “Working with tasks and jobs”, on page 57Provides procedures for customizing the standard IBM Tivoli Monitoring forDatabases: Microsoft SQL Server tasks and creating and scheduling jobs.

v Chapter 7, “Viewing resource model results with the IBM Tivoli Monitoring WebHealth Console”, on page 71

v

Provides procedures for setting up Web Health Console to work with IBM TivoliMonitoring for Databases: Microsoft SQL Server.

v Chapter 8, “Customizing resource models”, on page 73Provides procedures for subscribing and distributing a monitoring collectionprofile, and determining which resource models have been distributed to anendpoint.

v Chapter 9, “Enabling IBM Tivoli Monitoring for Databases: Microsoft SQL Serverfor Tivoli Enterprise Data Warehouse”, on page 95Provides information about setting up IBM Tivoli Monitoring for Databases:Microsoft SQL Server to work with Tivoli Enterprise Data Warehouse.

v Appendix A, “Authorization roles quick reference”, on page 107Summarizes required authorization roles and activities and outlines where tofind additional information about these roles in this manual.

v Appendix B, “Setting up Tivoli Enterprise Console”, on page 109Provides procedures for integrating the Tivoli Enterprise Console® with IBMTivoli Monitoring for Databases: Microsoft SQL Server.

v Appendix C, “Integrating with Tivoli Business Systems Manager”, on page 117Describes how to set up Tivoli Business Systems Manager, and how to use it tomanage Microsoft SQL Server resources.

v Appendix D, “Problem determination”, on page 123Provides information about troubleshooting and frequently asked questions forIBM Tivoli Monitoring for Databases: Microsoft SQL Server.

v Appendix E, “Messages”, on page 129Provides information about error messages for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server.

v Appendix F, “Accessibility”, on page 139Provides information about accessibility requirements and standards met withIBM Tivoli Monitoring for Databases: Microsoft SQL Server.

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Databases:Microsoft SQL Server library and related documents. It also describes how toaccess Tivoli publications online, and how to order Tivoli publications.

IBM Tivoli Monitoring for Databases: Microsoft SQL Serverlibrary

The following guides are available in the IBM Tivoli Monitoring for Databases:Microsoft SQL Server library:v IBM Tivoli Monitoring for Databases: Installation and Setup Guide, SC23-4854

Describes how to install and configure IBM Tivoli Monitoring for Databases:Microsoft SQL Server.

v IBM Tivoli Monitoring for Databases: Microsoft SQL Server User’s Guide, SC23-4853Describes how to use IBM Tivoli Monitoring for Databases: Microsoft SQLServer.

v IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide,SC23-4852Provides detailed information about individual tasks and resource models.

v IBM Tivoli Monitoring for Databases Release Notes, SC23-4851

vi IBM Tivoli Monitoring for Databases: Microsoft SQL Server: User’s Guide

Describes product features and provides information about the latest changes tothe installation requirements and procedures. The release notes also describeknown limitations related to installation and explain how to work around eachlimitation.

v IBM Tivoli Monitoring for Databases: Microsoft SQL Server Limitations andWorkarounds, SC23-4850Provides the latest information about known product limitations andworkarounds. To ensure that the information is the latest available, thisdocument is provided only on the Web and is updated on a regular basis. Youcan access the Limitations and Workarounds document through the IBM TivoliMonitoring for Databases: Microsoft SQL Server link on the Tivoli InformationCenter Web site:http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

v IBM Tivoli Monitoring for Databases: Microsoft SQL Server Warehouse EnablementGuide, SC23-4849Describes the warehouse enablement pack for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server. It covers installing and configuring thewarehouse pack and the data flow and data structures used by the warehousepack.

Related publicationsTo use the information in this book effectively, you must have some prerequisiteknowledge, which you can find in the following books:v Tivoli Management Framework User’s Guide

Provides detailed information about profiles and profile management.v Tivoli Management Framework Planning and Installation Guide

Provides detailed information about server and hardware requirements.v Tivoli Management Framework Reference Guide

Provides additional information about command line commands, such as thewinstall command.

v Tivoli Enterprise Installation Guide, Version 3.7

Provides more detailed information about using the Tivoli Enterprise Console(TEC) and using SIS to install the IBM Tivoli Monitoring for Databases:Microsoft SQL Server software.

The following documents also provide useful information:v Server Administrator’s Guide

Provides information about administering the Microsoft SQL Server server forthe relevant version of Microsoft SQL Server.

v Server Concepts Manual

Provides general information about the Microsoft SQL Server and how it worksfor the relevant version of Microsoft SQL Server.

v Server SQL Reference

Provides descriptions of the structured query language (SQL) used to manageinformation in Microsoft SQL Server databases for the relevant version ofMicrosoft SQL Server.

The Tivoli Glossary includes definitions for many of the technical terms related toTivoli software. The Tivoli Glossary is available, in English only, at the followingWeb site:

About this guide vii

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm

Accessing publications onlineThe documentation CD contains the publications that are in the product library.The format of the publications is PDF, HTML, or both. Refer to the readme file onthe CD for instructions on how to access the documentation.

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Software InformationCenter Web site. The Tivoli Software Information Center is located at the followingWeb address:


Click the IBM Tivoli Monitoring for Databases: Microsoft SQL Server link toaccess the product library.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print window. This option is availablewhen you click File → Print. Fit to page ensures that the full dimensions of aletter-sized page print on the paper that you are using.

Ordering publicationsYou can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For additional information, see the Appendix F, “Accessibility”, on page 139.

Contacting software supportIf you have a problem with any Tivoli product, refer to the following IBM SoftwareSupport Web site:

http://www.ibm.com/software/sysmgmt/products/support/

viii IBM Tivoli Monitoring for Databases: Microsoft SQL Server: User’s Guide

http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm




http://www.ibm.com/software/tivoli/order-lit/

http://www.ibm.com/software/sysmgmt/products/support/

If you want to contact software support, see the IBM Software Support Guide at thefollowing Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv Information you must have before contacting IBM Software Support

Conventions used in this bookThis book uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

Typeface conventionsThis guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip, and Operating system considerations)

v Column headings in a tablev Keywords and parameters in text

Italic

v Citations (titles of books, diskettes, and CDs)v Words defined in textv Emphasis of words (words as words)v Letters as lettersv New terms in text (except in a definition list)v Variables and values you must provide

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Operating system-dependent variables and pathsThis book uses the UNIX convention for specifying environment variables and fordirectory notation.

About this guide ix

http://techsupport.services.ibm.com/guides/handbook.html

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

x IBM Tivoli Monitoring for Databases: Microsoft SQL Server: User’s Guide

Chapter 1. Overview

The IBM Tivoli Monitoring for Databases: Microsoft SQL Server softwarecomplements existing tools for Microsoft SQL Server and adds features so you canmanage and monitor a large number of Microsoft SQL Server servers in adistributed environment. This software concentrates on those tasks that are definedand deployed by generic methods. It reduces the complexity of managing largedistributed database environments and frees administrators to concentrate on thenon-generic issues associated with each of the individual databases.

This software enables you to manage and monitor Microsoft SQL Servers byproviding extensions to Tivoli Management Framework, IBM Tivoli Monitoring,and the Tivoli Enterprise Console. It includes the ITMMicrosoftSQLServerTaskslibrary and resource models. These tasks and resource models enable you tomanage distributed Microsoft SQL Server computing resources effectively and withthe granularity that you need.

Using the IBM Tivoli Monitoring for Databases: Microsoft SQL Server software,you can accomplish the following tasks:v Automate repetitive DBA tasks, which enables you to define simple tasks once

and perform them on multiple databases and instances in a single action.v Use the resource models to monitor Microsoft SQL Server availability and

performance.v Alert administrators to Microsoft SQL Server performance problems or serious

errors and failures.v Create customized resource models using the provided Common Information

Model classes provided by IBM Tivoli Monitoring for Databases: Microsoft SQLServer.

v Integrate with the Tivoli Enterprise Console to provide event correlation todetermine the severity and relationship of system events and define rules forautomated event responses.

v Integrate with Tivoli Enterprise Data Warehouse to view environmental data fortroubleshooting and performance tuning.

v Integrate with Tivoli Business Systems Manager to monitor potential problems inyour environment.

Understanding IBM Tivoli MonitoringThis section describes the main concepts required for understanding how to set upand use resource models. A resource model captures and returns information, suchas server availability, about a resource or software application in the Tivolimanagement environment. IBM Tivoli Monitoring uses resource models to monitorand manage resources at distributed systems. A managed resource is a databaseobject that represents a hardware, software, or data entity that you manageaccording to policies set up in a Tivoli environment. Managed resources caninclude physical and logical disks, CPUs, memory, printers, processes, and services.A distributed system is the service that monitors resources, compares data frommonitored resources against configured thresholds, and runs automated responsesin a Tivoli environment. A threshold is a named property with a user-defined value.

1

Typically, the value specified for a threshold represents a significant level of aperformance-related entity, which, if exceeded, a system administrator might wantto know about.

ActionsYou can associate one or more recovery actions with a specific event. Theseactions are automatically triggered when the event occurs and, typically,are used for restoring satisfactory system service level. Each time an eventoccurs, the system provides a notification of the event, triggers a recoveryaction to restore satisfactory conditions and, if the action is successful,provides a notification that the action was performed. Actions areassociated with the execution of a CIM method or the execution of aprogram. Associate actions with indications when modifying an existingresource model using this software, or when creating a new resourcemodel with the IBM Tivoli Monitoring Workbench.

AttributesResource model attributes are string or numeric values that qualify events.A resource model receives attributes when it is created. In IBM TivoliMonitoring for Databases: Microsoft SQL Server, you do not add, delete, ormodify attributes that are in the default resource models. When you createa new resource model with the IBM Tivoli Monitoring Workbench, youqualify an event by specifying relevant attributes according to theinformation you want the resource model to monitor. For example, anevent might indicate insufficient disk space. When you specify attributes,such as disk name or available disk space, the resource model generates amore precise indication of the problem. For each resource model, several ofthe attributes are designated as keys.

Cycles When a resource model runs on an endpoint, it gathers data at regularintervals, called cycles; the duration of a cycle is the cycle time, which isdisplayed in seconds. A resource model with a cycle time of 60 secondsgathers data every 60 seconds. Each of the resource models specifies adefault cycle time that you can modify when you define the resourcemodel. At each cycle, the resource model collects data, analyzes it,generates the events, and triggers specified actions. The data collected is asnapshot of the status of the resources specified in the resource model.

Gathering Historical Data componentThe Gathering Historical Data component uses data collected by specificIBM Tivoli Monitoring resource models to populate a database on theTivoli server where it is installed. The collected data is aggregated every 24hours and added to the IBM Tivoli Monitoring database. You use thisresource model data to analyze key system metrics and plan networkgrowth.

For more information about gathering historical data, see the followingpublications:v IBM Tivoli Monitoring Warehouse Enablement Pack: Implementation Guide

v Enabling an Application for Tivoli Enterprise Data Warehouse

Heartbeat functionIn addition to the monitoring processes described above, IBM TivoliMonitoring operates a heartbeat function, that monitors basic system statusat endpoints attached to the gateway where it is enabled. Events are sentto the Tivoli Business Systems Manager (provided that the Tivoli BusinessSystems Manager Adapter component is installed at the gateway), theTivoli Enterprise Console, and the IBM Tivoli Monitoring Notice Group.

2 IBM Tivoli Monitoring for Databases: Microsoft SQL Server: User’s Guide

Indications and eventsAn indication is generated when the state of a given resource meetsspecified criteria. By itself, an indication does not trigger a specific action.When you define an event, you must specify under what conditions acertain number of indications are aggregated into that event. You alsospecify whether these indications must be consecutive, or whether thesequence can be interrupted by one or more monitoring cycles that do notregister an indication. When indications are aggregated, the resource modelgenerates an event. The cycles during which no indication is generated arecalled holes. An event can indicate that there is a problem in the resourcestate, trigger an action and, if enabled, send a notification to the TivoliEnterprise Console server or to the Tivoli Business Systems Manager.

IndicationsEach resource model generates an indication in a given cycle basedon the settings defined for it. A single occurrence of an indicationdoes not always represent a problem, but the persistence ofindications might. The resource model measures the persistence ofthe indications and aggregates them according to yourspecifications, or how you define settings for occurrences andholes. If the persistence of an indication meets the specifiednumber of occurrences, the resource model generates an event.Indications can be generated in any one of the followingcircumstances:v When a single threshold is exceeded. For example, in the

Windows® Process resource model, the Process High CPUindication is generated when the High CPU Usage threshold isexceeded (for any process that has a non-zero process ID).

v When a combination of two or more thresholds are exceeded.For example, in the Windows Logical Disk resource model aHigh Read Bytes per Second indication is generated when boththe following thresholds are exceeded:– The amount of bytes transferred per second (being written or

read) exceeds the High Bytes per Second threshold.– The percentage of time that the selected disk drive spends

making read or write requests exceeds the High PercentUsage threshold.

v When a combination of other factors change. For example, in theWindows Process resource model the Process Handle Leakindication is generated when a process is losing memory. Thereis no threshold for this indication. The resource model comparesthe number of handles of the five processes with the mosthandles in consecutive cycles. If the number of handles hasincreased, the indication is generated.

Occurrences and holesOccurrences and holes record whether or not an indication occursduring the cycle for a specific resource model. An occurrence is acycle during which at least one threshold is exceeded and anindication occurs for a given resource model. A hole is a cycleduring which an indication does not occur for a given resourcemodel. A hole means none of the conditions that generate anindication were met, but it does not necessarily mean that nothresholds were exceeded. For example, in the Windows LogicalDisk resource model a High Read Bytes per Second indication is

Chapter 1. Overview 3

not created when the percentage disk time is higher than the HighPercent Usage threshold, provided that the Low Disk Spacethreshold is exceeded.

EventsAn event verifies the persistence of an indication by eliminatingunrepresentative peaks and troughs for the indication. Forexample, a process that generates the Process High CPU indicationin one cycle might not threaten other processes if the high usage isnot repeated. However, an indication that persists over severalcycles is more likely to be a problem. In this way, an event definesthe significant number of consecutive occurrences of the indication.

When you define an event, you can specify how many consecutiveholes in the sequence of consecutive occurrences are permitted.Specifying how many consecutive holes are permitted during theaccumulation of the consecutive occurrences enables you tocontinue the counting of consecutive occurrences if one or twocycles fall below the threshold.

An event is an aggregation of a defined number of consecutiveoccurrences during which there can be a defined number ofconsecutive holes. An event is generated only when theaggregation algorithm detects three consecutive occurrences.

The following examples illustrate what happens if you define anevent as three occurrences and two holes. 1 represents anoccurrence and 0 represents a hole.v 0 1 0 1 0 0 1

Because fewer than three holes exist between each of the threeoccurrences, the three occurrences are consecutive. Therefore, thesequence represents an event.

v 1 0 0 1 0 0 1If each occurrence is followed by the maximum specified holeswithin seven cycles, an event is triggered.

v 1 0 0 1 0 0 0If the algorithm counts two consecutive occurrences and thenobserves three consecutive holes (more holes than that allowedin the definition of an event for this example) it sets the count ofoccurrences to zero. See Table 1.

Table 1. Counting occurrences

Sequence Count of occurrences

1 0 0 1

1 0 0 1 2

1 0 0 1 0 2

1 0 0 1 0 0 2

1 0 0 1 0 0 0 0

The snapshots of the CPU usage obtained by the resource modelare shown in Table 2 on page 5. The first row shows the cyclenumber and the second the percentage of CPU usage.


Table 2. High CPU Usage percentages over 12 cycles: holes and occurrences

Cycle 1 2 3 4 5 6 7 8 9 10 11 12

CPU% 55 73 54 63 68 42 50 70 90 55 70 80

Occurrenceor hole

H O H O O H H O O H O O

Occurrencecount

0 1 1 2 3 3 0 1 2 2 3 4

Cycles that exceed the threshold are occurrences and are shown inbold type. The other cycles are holes.

For this example, an event is created for this indication if there arefour consecutive occurrences with only one hole permitted. Thefinal row in Table 2 shows the count that the resource model makesof the consecutive occurrences. The count is set to zero at the 7thcycle snapshot because the resource model has encountered twoconsecutive holes. In this example, an event is triggered in the 12thcycle. The count is then set to zero and the process continues.

While defining an event, you can also indicate if you want thesystem to notify the Tivoli Enterprise Console server, or the TivoliBusiness Systems Manager, that an event was generated. You canchange these selections later, after you include the resource in anIBM Tivoli Monitoring profile. You can also define the degree ofseverity and the message that specifies the notification of the event.

Clearing eventsWhen you enable clearing events, resource models close eventswhen the causes of the events are removed. Clearing events areprocessed by the Tivoli Business Systems Manager server. Clearingevents have a severity of harmless, regardless of the severity of theoriginal event, but have the same event ID as the original event.For example, a service stops and the Tivoli Enterprise Consoleserver receives an event notifying it of this problem. Until theservice restarts, the problem is still present on the endpoint, butIBM Tivoli Monitoring does not send any further eventnotifications to the Tivoli Enterprise Console server. If the clearingevent function is enabled when the service restarts, a clearing eventis sent to the Tivoli Enterprise Console server, thereby closing theoriginal event. The clearing event itself does not normally appearon the server, because its only function is to clear the original errorevent.

Note: Correlated events cannot be cleared.

Monitoring of events and indicationsYou can specify what events are sent to the Tivoli EnterpriseConsole® server, the Web Health Console, and Tivoli BusinessSystems Manager.

Tivoli Enterprise Console serverYou can view events through the Tivoli Enterprise Consoleserver if you have compiled and loaded the required BasicRecorder of Objects in C (BAROC) files on the server. Theevent contains a set of properties that can help you identify


the problem. For example, the information in theProcessHandleLeak event includes the following values:v Current Process IDv Number of handles allocated to the processv Name of the process

Clearing events can also be processed by the TivoliEnterprise Console server. If the default procedure is usedto enable the monitoring of events, the Tivoli EnterpriseConsole server uses the clearing event to close theassociated error event. However, if you choose not toinstall the clearing events rule in the default procedure, theclearing event is displayed as a separate entity with thesame ID as the original error event.

Web Health ConsoleThe Web Health Console, an optional part of IBM TivoliMonitoring, obtains events and indications from endpoints.The Web Health Console displays the health of eachpotential problem as a numeric value between 100 (perfecthealth) and zero (with zero meaning that the conditions forthe corresponding event have been met). Intermediatevalues show the percentage of occurrences currentlyregistered relative to the total number of occurrencesneeded to trigger an event. For example, Table 3 is basedon Table 2 on page 5, but additionally shows the healthpercentage:

Table 3. High CPU Usage percentages over 12 cycles: health

Cycle 1 2 3 4 5 6 7 8 9 10 11 12

CPU% 55 73 54 63 68 42 50 70 90 55 70 80

Occurrenceor Hole

H O H O O H H O O H O O

OccurrenceCount

0 1 1 2 3 3 0 1 2 2 3 4

Health (%) 100 75 75 50 25 25 100 75 50 50 25 0

In this example, the health percentage changes in steps of25% because 4 occurrences are required to trigger an event.If the indication requires 5 occurrences, the healthpercentage changes by steps of 20%.

Tivoli Business Systems Manager

Events can also be sent to the Tivoli Business SystemsManager if you install the Tivoli Business Systems ManagerAdapter on the endpoint gateways you are monitoring. Seethe Tivoli Business Systems Manager documentation formore information.

Tivoli Business Systems Manager uses the clearing event toclose the associated error event.

LoggingFor any endpoint, you can log the data collected by a resource model andwrite it to a local database. Use the History View on the Web HealthConsole to view the logged data. You can choose to store raw oraggregated data.


ParametersParameters represent instances of system activity that you want yourresource model to monitor, such as ports, port states, and disk spaceavailability. You use parameters to set thresholds for your resource model,beyond which you do not want your monitored system to exceed or fallbelow. Parameters can be numeric or string values (unlike thresholds thatare numeric only).

Parameters can be numeric or string values that you can view in the TivoliMonitoring Workbench windows. You can choose one among the followinglists when you specify the parameters:v Boolean Listv Choice Listv String Listv Numeric List

Some resource models have one or more parameters. For example, theWindows Parametric TCP/IP Ports resource model uses parameters thatcontain lists of ports and port states that you want to monitor.

ProfilesIBM Tivoli Monitoring is a profile-based application that runs in a Tivolienvironment. Different profiles can be defined containing differentselections of resource models. All aspects of existing profiles can bemodified, including the addition, deletion and customization of resourcemodels. You can distribute multiple profiles to each endpoint.

Recovery actionsFor any event, recovery actions can be run automatically, such as built-inactions (for Windows) or tasks. The actions take positive steps to remedythe situation, ensuring that information about the event is distributed tothe appropriate authorities or entities.

Built-in actionsCertain events can have one or more built-in actions predefined forthem. An action can be either the execution of a CIM class methodor the execution of a program. Both type of actions can beimplemented only through the IBM Tivoli Monitoring Workbench.For example, an event that detects the failure of a service can beset up to restart that service. Thus, without any humanintervention, IBM Tivoli Monitoring detects the failure of a serviceand automatically restarts it. Built-in actions are defined by defaultas part of an event, but can be removed. They have the same eventID as the event that they are designed to correct.

Tasks For each event you can select one or more tasks to be performedwhen the event is triggered. The tasks that are triggered by an IBMTivoli Monitoring event can access the event name and eventthresholds of the triggering event by accessing the environmentvariables.

Resource modelsIBM Tivoli Monitoring provides predefined resource models that accessspecific performance data from the system at runtime. For example, theProcess resource model gathers data about processes running on thesystem. The resource models process the data they collect using analgorithm that determines whether or not the system is performing toexpectations. You can use default values to collect performance data or


customize the resource models to match specific requirements in yourenvironment. Distributing resource models using default values enablesyou to begin monitoring immediately to obtain useful data concerningyour enterprise. When you become more familiar with the monitoringprocess and feedback, you can choose to customize the resource modelinformation.

SchedulingIBM Tivoli Monitoring contains a scheduling feature that enables you todetermine a period within which monitoring takes place and specificscheduling rules. The monitoring period is determined by defining a fromand a to date.

The scheduling rules enable you to define time periods on specificweekdays during which monitoring takes place. Any number of rules canbe defined, allowing you to set up a complex pattern of resourcemonitoring for a profile, covering the time periods important to you.

The scheduled times are always interpreted as local times, enabling you toset up a single rule that monitors the same local time period in differenttime zones. For example, if you want to monitor morning activities in oneof several time zones, a single rule defining the monitoring period ofbetween 08:00 and 13:00 is interpreted locally in each of the time zones, sothat you monitor the same relative period.

All event and activity times that are reported from endpoints or gatewaysare also logged in the local time of the originating system from where theyoriginated.

ThresholdsEach resource model defines one or more thresholds. Each threshold has adefault numeric value that you can change when you define the profile.The monitoring algorithm written in the script determines how theresource model uses a threshold. The following are examples of how aresource model can use thresholds:v A threshold value might represent a limit that, if not met, indicates an

unsatisfactory resource state. For example, if you want the system tonotify you when disk space drops under 70%, set the threshold value to70 to generate an indication each time your disk space is less than 70%.

v Some threshold values control the scope of what the resource modelmonitors. For example, the Windows Process resource model uses theMaximum Processes threshold to limit the number of processesmonitored for the highest usage of CPU. Thus, if you set the MaximumProcesses threshold to 5, the resource model only reports on the fivehighest CPU-using processes.

You can add a description for each threshold in the Threshold windowexplaining what each value measures and how it is used within themonitoring algorithm.

Overview of extensions to the Tivoli environmentIBM Tivoli Monitoring for Databases: Microsoft SQL Server is fully integrated intothe Tivoli environment. You should already be familiar with the concepts of theTivoli environment as outlined in the Tivoli Management Framework User’s Guide.


Tivoli administratorsTivoli administrators are system or database administrators who have theauthorization to perform system or database management tasks using the Tivolimanagement environment. Each administrator or group of administrators isrepresented by an icon on the Tivoli desktop.

The IBM Tivoli Monitoring for Databases: Microsoft SQL Server product fullyintegrates into Tivoli security. To perform Microsoft SQL Server administrationfunctions, administrators must have authorization roles for both IBM TivoliMonitoring for Databases: Microsoft SQL Server and Tivoli ManagementFramework.

Authorization rolesAuthorization roles determine the range of actions an administrator can perform.You assign roles to administrators so they can perform system or databasemanagement tasks. A role may be over the entire Tivoli management region or over aspecific set of resources, such as those contained in a policy region. Super, senior,admin, and user are examples of standard authorization roles.

The IBM Tivoli Monitoring for Databases: Microsoft SQL Server product also addsthe following authorization roles:

mssqlserver_dbaThis role provides the ability to create, delete, start or stop anMSSQLServer object. An administrator with the mssqlserver_dba role canperform all IBM Tivoli Monitoring for Databases: Microsoft SQL Serveroperations on an Microsoft SQL Server server.

mssqlserver_userThis role provides read-only access to a limited set of IBM TivoliMonitoring for Databases: Microsoft SQL Server operations. Anadministrator with the mssqlserver_user role can view the properties of adatabase and open an Microsoft SQL Server database icon.

For information about managing IBM Tivoli Monitoring profiles, see the IBM TivoliMonitoring for Databases: Microsoft SQL Server User’s Guide.

Each IBM Tivoli Monitoring for Databases: Microsoft SQL Server operation has arequired authorization role for execution. This user’s guide documents the contextand authorization role required for each operation in the following manner:

Activity Context Required Role

Add or remove a managed resource typefor a policy region

Policy region senior

Microsoft SQL Server endpointsIn the Tivoli environment, an endpoint is any resource that can be managed. In IBMTivoli Monitoring for Databases: Microsoft SQL Server, the endpoints are managednodes, database servers, and databases. Each endpoint type has a name:v Managed node: Managed Node

v Database server: MSSQLServer

v Database: MSSQLDatabase


Icons on the desktop represent endpoints. The following table shows an exampleof a server icon:

Microsoft SQL Server server icon

You can subscribe server endpoints to profiles within profile managers in the sameway as any other managed resource.

Using the desktop or CLIIn many cases, this manual provides procedures for executing from either thedesktop or the command line interface (CLI). You can choose to use the desktop orgraphical user interface (GUI) when you want to take advantage of visual inputprompting, which includes drop-down lists of options, and the defaults providedby options, such as the Notify TEC button. Use the command line interface whenyou want to create scripts, set tasks to respond to resource models, and rapidlyenter commands.


Chapter 2. Getting started quick-reference guide

This chapter provides a quick-reference table of the setup procedures you mustperform before you can use IBM Tivoli Monitoring for Databases: Microsoft SQLServer. The table below includes cross-references to places where you can findadditional information about each of these procedures.

Table 4. Quick-reference information for getting started with IBM Tivoli Monitoring for Databases: Microsoft SQLServer

Goal Refer to

Starting

1. Access the Tivoli environment so you canmanage and monitor your databaseenvironment.

“Starting the Tivoli environment” on page 13

Setting up administrators to use the software

2. Authorize persons to have the roles theyneed for managing resources in theproduct.

Note: You must assign both Tivoli andMicrosoft SQL Server authorization roles toadministrators in the policy regions that youwant them to administer.

“Setting authorization roles” on page 15.

Appendix A, “Authorization roles quick reference”, on page 107lists the authorization roles required for each procedure.

Use the Edit Default Policies window in an IBM Tivoli Monitoringprofile to set the user and group IDs for the profile.

See the Tivoli Management Framework User’s Guide to learn how toassign authorization roles to Tivoli administrators.

3. Subscribe additional administrators to theappropriate notice groups.

“Subscribing to notice groups” on page 17.

Setting managed resource types

4. Add MicrosoftSQLServer as a managedresource type for the policy regions inwhich you want to manage Microsoft SQLServer databases.

“Specifying the managed resource types in a policy region” on page19.

5. Set the Tmw2KProfile option as amanaged resource for the policy region (ifyou have not already done so) so you cancreate IBM Tivoli Monitoring profiles.

“Creating profile managers and profiles” on page 30.

Registering servers

6. Run the DiscoverMSSQLServers task tofind and register servers.

—OR—

Register servers manually.

“Registering servers using Discovery” on page 22.

—OR—

“Registering database servers manually” on page 26

Setting up monitoring profiles and tasks

7. Set up customized tasks. “Customizing a task” on page 61.

8. Set up and schedule jobs from tasks. Chapter 6, “Working with tasks and jobs”, on page 57

Also see the IBM Tivoli Monitoring for Databases: Microsoft SQLServer Reference Guide for more information about tasks.

11

Table 4. Quick-reference information for getting started with IBM Tivoli Monitoring for Databases: Microsoft SQLServer (continued)

Goal Refer to

9. Set up the resource models that you wantto run:v Set up the suggested resource models

and run them for a period of time.v Remove any resource models that are

not necessary for your environment.

Chapter 8, “Customizing resource models”, on page 73.

Also see the IBM Tivoli Monitoring for Databases: Microsoft SQLServer Reference Guide for more information about resource models.

(Optional) View daily reports in the Web Health Console

View statistics regarding your environment inthe Web Health Console.

Chapter 7, “Viewing resource model results with the IBM TivoliMonitoring Web Health Console”, on page 71

(Optional) Create historical reports in the Tivoli Enterprise Data Warehouse

Configure Tivoli Enterprise Data Warehouse toview environmental data for troubleshootingand performance tuning.

Chapter 9, “Enabling IBM Tivoli Monitoring for Databases:Microsoft SQL Server for Tivoli Enterprise Data Warehouse”, onpage 95

(Optional) Connecting to Tivoli Enterprise Console

Set up Tivoli Enterprise Console so you canview activity reports for your environment.

Appendix B, “Setting up Tivoli Enterprise Console”, on page 109.

(Optional) Connecting to the Tivoli Business Systems Manager

Set up Tivoli Business Systems Manager sothat you can monitor potential problems inyour environment.

Appendix C, “Integrating with Tivoli Business Systems Manager”,on page 117.


Chapter 3. Setting up IBM Tivoli Monitoring for Databases:Microsoft SQL Server

This chapter provides the general setup procedures for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server.

The following is an overview table of the setup procedures that you must performto use the IBM Tivoli Monitoring for Databases: Microsoft SQL Server product:

Table 5. IBM Tivoli Monitoring for Databases: Microsoft SQL Server setup guidelines

Goal Refer to

1. Starting the Tivoli environment “Starting the Tivoli environment” on page 13

2. Setting authorization roles “Setting authorization roles” on page 15

3. Subscribing to notice groups “Subscribing to notice groups” on page 17

4. Specifying the Microsoft SQL Server managed resource typesso that you can create the resource objects that are managedby the IBM Tivoli Monitoring for Databases: Microsoft SQLServer product

“Specifying the managed resource types in apolicy region” on page 19

5. Registering databases using Discovery to automaticallycreate multiple database objects in a policy region.

“Registering servers using Discovery” on page 22

6. Registering a database manually through either the Tivolicommand line or desktop to create multiple database objectsin a policy region.

“Registering database servers manually” on page26

Starting the Tivoli environment

ObjectiveTo access the Tivoli environment so you can use the monitoring functions of IBMTivoli Monitoring for Databases: Microsoft SQL Server.

Background informationYou can access the Tivoli desktop or the Tivoli command line interface to managethe operations and functions of IBM Tivoli Monitoring for Databases: MicrosoftSQL Server.

The Tivoli desktop is a user interface that provides point-and-click access to IBMTivoli Monitoring for Databases: Microsoft SQL Server. The Tivoli desktop providesa central control point for you to organize, manage, and monitor operations.

The Tivoli command line interface (CLI) enables you to enter commands from thekeyboard. You can use these commands in shell scripts and with system utilitiessuch as the UNIX cron utility. For more information about using commands, referthe Tivoli Management Framework Reference Manual.

Required authorization roleadmin

Before you beginNone

13

When you finishNone

ProcedureYou can perform this procedure from either the Tivoli command line or thedesktop.

Command line: Use one of the following two methods to access the Tivolicommand line interface, depending on whether you use a Windows NT or UNIXoperating system:v Windows NT/2000

1. Log on to a Windows NT managed node or Tivoli management regionserver.

2. Click Start in the Windows task bar to display the Start menu.3. Click Programs from the Start menu.4. Click Command Prompt to open the command prompt window.5. Enter the following command to run the environment initialization and setup

script:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

—OR—v UNIX

1. Log on to a UNIX managed node or Tivoli management region server.2. Run the environment initialization and setup script.

– If you are using the Bourne, Korn, or bash shell, run the followingcommand:. /etc/Tivoli/setup_env.sh

– If you are using the C shell, run the following command:source /etc/Tivoli/setup_env.csh

Desktop: Use one of the following methods to log onto the Tivoli desktop:v Windows NT/2000

1. Click Start in the Windows task bar.2. Select Programs.3. Select Tivoli to display the Tivoli pop-up menu.4. Select Tivoli to display the Tivoli login screen.5. Type values in the following fields of the login screen:

Host MachineSpecifies the host name of the Tivoli management region serverwhere the Tivoli desktop should connect.

Log In AsSpecifies the login name to the Tivoli management region server.

PasswordSpecifies the password for the specified login name.

6. Click OK to display the Tivoli desktop.

—OR—v UNIX

Enter the tivoli command.


Additional information: See the Tivoli Management Framework Reference Manual formore information on this command.

Setting authorization roles

ObjectiveTo authorize persons to have the roles they need to manage resources in IBMTivoli Monitoring for Databases: Microsoft SQL Server.

Background informationWhen you authorize roles for the persons who use the product, they can performoperations and access the resources that their jobs require. For example, anadministrator needs the following roles, depending on the required responsibilities:

admin Authorizes the administration of Microsoft SQL Server databases.

mssqlserver_dbaThis role provides the ability to query and update a database. Anadministrator with the mssqlserver_dba role can perform all IBM TivoliMonitoring for Databases: Microsoft SQL Server operations on an MicrosoftSQL Server database.

mssqlserver_userThe user role has less access and fewer capabilities in IBM TivoliMonitoring for Databases: Microsoft SQL Server. This role providesread-only access to a limited set of IBM Tivoli Monitoring for Databases:Microsoft SQL Server operations. An administrator with themssqlserver_user role can view the properties of a database and open anMicrosoft SQL Server database icon.

Required authorization rolesenior


When you finishYou must restart the desktop to enable the changes in this procedure to take effect.

You can add managed resources (objects) to a policy region. See “Specifying themanaged resource types in a policy region” on page 19 for more information onworking with various types of managed resources.


Command Line: Use the wsetadmin command to set or change resourceauthorization roles. See the Tivoli Management Framework Reference Manual for moreinformation.

Desktop:

1. Open the Tivoli desktop using one of the methods described in“Starting theTivoli environment” on page 13.

2. Double-click the Administrators icon to display the collection of iconsrepresenting the defined Tivoli administrators.

Chapter 3. Setting up IBM Tivoli Monitoring for Databases: Microsoft SQL Server 15

3. Right-click the existing administrator whose role you want to modify to accessthe drop-down menu.

4. Select Edit Resource Roles to display the Set Resource Roles window.

5. Select a resource for which you want to set the administrators role from theResources list.Additional Information: The roles listed in the Available Roles and CurrentRoles list depend on the particular applications installed.

6. Add or remove one or more roles for one or more selected resources as follows:v Add Roles

a. Do one of the following to add roles for resources:– Select one or more roles from those shown in the Available Roles

scrolling list, and click the left-arrow button.


The selected roles move from the Available Roles scrolling list to theCurrent Roles scrolling list.—OR—

– Double-click an entry in the Available Roles scrolling list to move itautomatically to the Current Roles scrolling list.

Note: Moving a role from one list to another moves only the selectedroles temporarily to the Current Roles or Available Rolesscrolling lists.

b. Click Change after moving each role.Additional Information: The Set Resource Roles window remains displayeduntil you click Close or Change & Close.

c. Click Change & Close to add all of the selected roles for theadministrator and return to the Administrators window.

v Remove Roles

a. Do one of the following to remove roles for resources:– Select one or more roles from those shown in the Current Roles

scrolling list, and click the right-arrow button.The selected roles move from the Current Roles scrolling list to theAvailable Roles scrolling list.—OR—

– Double-click an entry in the Current Roles scrolling list to move itautomatically to the Available Roles scrolling list.

Note: Moving a role from one list to another only moves the selectedroles temporarily to the Current Roles or Available Rolesscrolling lists.

b. Click Change after moving each role.Additional Information: The Set Resource Roles window remains displayeduntil you click Close or Change & Close.

c. Click Change & Close to add all of the selected roles for theadministrator and return to the Administrators window.

Subscribing to notice groups

ObjectiveTo assign administrators to notice groups so you can enable them to receivemessages about database activity.

Background informationWhen you install IBM Tivoli Monitoring for Databases: Microsoft SQL Server, itcreates several notice groups. The software automatically subscribes the rootadministrator to the Microsoft SQL Server notice group during installation. TheMicrosoft SQL Server notice group records Microsoft SQL Server managementactivity and contains messages generated by Microsoft SQL Server administratoractivity. The notices include registering and removing endpoints and stopping andstarting databases.

For additional information about notice group subscriptions, see the TivoliManagement Framework User’s Guide.




When you finishNone


Command line: Use the wsetadmin command with the –n option to subscribeadministrators to notice groups from the command line. Use the –N option tounsubscribe administrators.

The following example subscribes administrator Steve Callahan to the MicrosoftSQL Server notice group:wsetadmin -n “Microsoft SQL Server” “Steve Callahan”

For more information about this command, see the Tivoli Management FrameworkReference Manual.

Desktop:

1. Double-click the Administrators icon to display the Administrators window.2. Right-click on the administrator icon to which you want to subscribe to the

notice groups to display the Administrators icon pop-up menu.3. Select Edit Notice Group Subscriptions to display the Set Notice Groups

window.

Additional Information: The following groups display:

Current Notice GroupsDisplays the notice groups to which the administrator is currentlysubscribed.

Available Notice GroupsDisplays the notice groups to which the administrator can subscribe.

4. Do one of the following to move a notice group from Available to Current:


v Double-click on a notice group from the Available Notice Group list.—OR—

v Do the following:a. Select one or more notice groups from the Available Notice Groups list.b. Click the left arrow button to move your selection to the Current Notice

Groups list.

5. Optional: Remove a notice group subscription by doing the following:a. Choose one or more of the notice groups in the Current Notice Groups list.b. Click the right arrow button to move the notice groups into the Available

Notice Groups list.6. Click Change & Close to save the changes and return to the Administrators

window.

Specifying the managed resource types in a policy region

ObjectiveTo define the managed resource types that are available in a policy region so youcan create the resource objects to manage the resources with the IBM TivoliMonitoring for Databases: Microsoft SQL Server product.

Background informationA managed resource is any hardware or software entity that can be viewed ormanaged from the Tivoli desktop. Examples of managed resource types include:v MicrosoftSQLServerv Task libraryv Profile manager

A policy region is a collection of Microsoft SQL Server resources, such as databasesor servers, that share one or more common policies. By grouping similar resourcesinto policy hierarchies that reflect your organization, you can customize IBM TivoliMonitoring for Databases: Microsoft SQL Server to maintain and manage yourMicrosoft SQL Server resources. For example, you can create a policy region namedNorth_America that distinguishes the location, department, or group of resources.


Each policy region maintains a list of managed resource types that are valid forthat policy region. Before you can create an instance of a managed resource (suchas a server) in a policy region, you must add the managed resource type to thislist. You can add or remove managed resource types at any time.

When you add a managed resource type to a policy region, the software does thefollowing:v Assigns a default policy to the managed resource when you first add it to a

policy region.v Adds the managed resource type to the policy region’s Create menu so that you

can create new instances of the managed resource in the policy region.


Before you beginNone.

When you finishNone


Command line: Use the wgetpr and wsetpr commands to examine and changethe managed resource types in a policy region.

To assign the policy used in a policy region, enable or disable policy validation, oradd or remove a managed resource in a policy region, use the wsetpr command.The partial CLI syntax is as follows:

Adding a Managed Resource

wsetpr[–d default_pol][–v validation_pol][–E | –e]resourceregion

where:

–d default_polSpecifies the label of the default policy to be used for the managedresource.

–v validation_polSpecifies the label of the validation policy to be used for the managedresource.

–E Displays policy validation.

–e Enables policy validation.

resourceSpecifies the managed resource type.

region Specifies the label of the target policy region.


Deleting a Managed Resource

wsetpr [–r] resource region

where:

–r Removes the specified resource from the policy region.

resourceSpecifies the managed resource type.

region Specifies the label of the target policy region.

Examples

The following example lists all of the managed resources in the DefaultRegionpolicy region:wgetpr @PolicyRegion:DefaultRegionMicrosoftSQLServerSQLDiscoveryProfileManagerTaskLibrary

The following example adds the TaskLibrary resource to the Engineering policyregion:wsetpr TaskLibrary @PolicyRegion:Engineering

The following example enables policy validation for the TaskLibrary resource inthe Engineering policy region. The default policy is BasicTaskLibrary and thevalidation policy is BasicTaskLibrary.wsetpr -d BasicTaskLibrary -v BasicTaskLibrary -e TaskLibrary@Engineering

For more information about these commands, see the Tivoli Management FrameworkReference Manual.

Desktop:

1. Open the Tivoli desktop.2. Double-click the policy region that contains the IBM Tivoli Monitoring for

Databases: Microsoft SQL Server resource to display the Policy Region window.3. Click Properties to display the Properties drop-down menu.


4. Click Managed Resources from the Properties drop-down menu to display theSet Managed Resources window.

Additional Information: The following lists display:

Current ResourcesDisplays the current managed resource types for the policy region.

Available ResourcesDisplays the managed resource types that are available to add to thepolicy region.

5. Do one of the following to move a resource from Available to Current:v Double-click the managed resource type.

—OR—v Do the following:

a. Click on the a resource from the Available Resources list.b. Click the left arrow button to move your selection to the Current

Resources list.6. Optional: Remove a managed resource from the policy region by doing the

following:a. Choose one or more managed resources from the Current Resources list.b. Click the right arrow button to move the managed resource into the

Available Resources list.7. Click Set & Close to save the changes and return to the policy region window.

Registering servers using Discovery

ObjectiveTo create objects that represent the server in the Tivoli environment so you canmanage them with IBM Tivoli Monitoring for Databases: Microsoft SQL Server.

Background informationYou must register a server before you can manage it in the Tivoli environment. Theserver you want to register must be installed on a host that is an endpoint in theTivoli environment. Discovery searches for Microsoft SQL Servers in your localTivoli management region. If Discovery finds a Microsoft SQL Server that Tivolidoes not already manage, it automatically creates a Microsoft SQL Server object onthe Tivoli desktop. Discovery automatically assigns default properties to each


server based on information found in the registry entries. Discovery ignores theserver state, so it does not matter whether a server is in an up or down state.

Using Discovery to register servers in large environments can require a long timeperiod. The greater the number of endpoints against which you run Discovery, thelonger the time period to complete Discovery. System performance and networkspeed are also factors that determine the amount of time required for serverregistration. If you have a large or slow environment, you might consider runningDiscovery multiple times on subsets of endpoints.

Discovery finds and registers all servers listed in the registry on the specifiedendpoints. The registry lists Microsoft SQL Servers, typically located in thefollowing keys:v For Microsoft SQL Server version 7: SOFTWARE\\Microsoft\\MSSQLServerv For a default instance on Microsoft SQL Server version 2000:

SOFTWARE\\Microsoft\\MSSQLServerv For a named instance on Microsoft SQL Server version 2000:

SOFTWARE\\Microsoft\\Microsoft SQL Server

If the registry key for a server was deleted, that server is not discovered orregistered.

Required authorization rolemssqlserver_dba, mssqlserver_user, or senior

Before you beginAll endpoints require Tivoli Management Framework, version 3.7.1 before runningDiscovery.

Discovery automatically obtains the default property values from the Windows NTregistry and assigns them to each server as based information found in the registryentries. Table 6 lists each database property and the value assigned by Discovery.

Table 6. Server properties

Property Description

Name The server name defined in the registry key

Home The server home directory defined in the registry key

SQL ServerAccount

A check box used to indicate whether to use database authentication or aWindows domain. By default, the box is unchecked.

Username The Username is not defined in the registry key. You must specify a username in the Set Properties window. See “Editing server properties” onpage 42 for instructions.

Password The Password is not defined in the registry key. You must specify apassword in the Set Properties window. See “Editing server properties”on page 42 for instructions.

Version The server version (v7, or 2k) defined in the registry key

When you finishAfter Discovery completes, the specified policy region displays each discoveredserver. You can then subscribe the database to profiles in profile managers in thesame way as any other managed resource.


Table 7.

Note: You must configure the User Name and Password of each registered Microsoft SQLServer. If you do not configure the User Name and Password you cannot properly managethe server.

You can configure the User Name and Password using one of the following:v The MSSQLAuthentication task

Use this task to configure the User Name and Password for more than oneMicrosoft SQL Server at a time. See the MSSQLAuthentication task in the IBMTivoli Monitoring for Databases: Microsoft SQL Server Reference Guide for moreinformation. See Chapter 6, “Working with tasks and jobs”, on page 57 forinstructions on how to run a task.

v The Edit Properties windowThis window enables you to configure the User Name and Password oneMicrosoft SQL Server at a time. The Edit Properties window is often usedfollowing a manual registration of a Microsoft SQL Server. See “Editing serverproperties” on page 42 for instructions on editing database properties. See“Registering database servers manually” on page 26 for more information onmanually registering a Microsoft SQL Server.

ProcedureYou can perform this procedure from the Tivoli desktop only.

Desktop:

1. Open the Tivoli desktop.2. Double-click the policy region where you want to run Discovery to display

the Policy Region window.3. Double-click the MicrosoftSQLServerTasks task library to display the Task

Library: Microsoft SQL Server Tasks window.4. Double-click the DiscoverMSSQLServers job to display the

DiscoverMSSQLServers window.


5. Click Endpoints to display the Select Endpoints window.

6. Select one or more endpoints from the Choose one or more list.7. Click Set & Close to confirm your selections, close the Endpoints window and

return to the DiscoverMSSQLServers window.8. (Optional) Click Proxy Managed Nodes to select a proxy managed node. A

proxy managed node contains the MicrosoftSQLServer object for the MicrosoftSQL Servers being discovered. If no proxy managed node is specified, the taskuses the managed node (gateway) currently defined for the endpoints.

9. Select a proxy manage node from the list.10. Click Set & Close to confirm your selection, close the Select a Proxy Managed

Node window and return to the DiscoverMSSQLServers window.11. Click Set & Execute to run the DiscoverMSSQLServers job and display the

DiscoverMSSQLServers Output window.

Note: Running Discovery in large–scale environments might not return thetask screen for some time. You can verify the task is working in theTivoli management environment where database icons display as theyare discovered.

12.

13. Do one of the following:v Click Close to close the DiscoverMSSQLServers Output window.

—OR—v Click Save to File and complete the following steps to save the job output:

a. Type the name of the managed node in the On Host text field.

Note: The host computer must be a Tivoli Management Enterpriseclient.


b. Type the full path to the file in the Output File text field.c. Click Save & Close.

14. Configure the discovered servers with the appropriate authentication type,user name, and password. See “Editing server properties” on page 42 forinstructions.

Registering database servers manually

ObjectiveTo manually register a single server so you can manage it in the Tivolienvironment.

Background informationYou must register a server before you can manage it from the Tivoli desktop.Registering the server creates it as an object on the Tivoli desktop. The databasesever you want to register must be installed on a host that is an endpoint in theTivoli environment. After you register the server, it displays as an endpoint in thepolicy region. You can register servers in two ways:v Manually, using the Tivoli command line or desktop

—OR—v Automatically, using Discovery as described in “Registering servers using

Discovery” on page 22

Using Discovery is typically faster, but you might prefer to manually register adatabase in the following circumstances:v You want to register only one or two database servers and you already know the

database properties.v You want to register a specific server on an endpoint that has multiple databases

(Discovery registers all databases on an endpoint).v You need to change most of the default database properties provided by

Discovery.

Required authorization rolemssqlserver_dba or mssqlserver_user

Before you beginTivoli software must be installed on the endpoint machine that contains theMicrosoft SQL Server database before registering a database.

When you finishAfter you manually register a Microsoft SQL Server, the specified policy regiondisplays the discovered server. You can then subscribe the database to profiles inprofile managers in the same way as any other managed resource.

Note: You must configure the User Name and Password of each registeredMicrosoft SQL Server. If you do not configure the User Name and Passwordyou cannot properly manage the server.

You can configure the User Name and Password using one of the following:v The MSSQLAuthentication task

Use this task to configure the User Name and Password for more than oneMicrosoft SQL Server at a time. See the MSSQLAuthentication task in the IBMTivoli Monitoring for Databases: Microsoft SQL Server Reference Guide for moreinformation. See Chapter 6, “Working with tasks and jobs”, on page 57 forinstructions on how to run a task.


v The Edit Properties windowThis window enables you to configure the User Name and Password oneMicrosoft SQL Server at a time. The Edit Properties window is often usedfollowing a manual registration of a Microsoft SQL Server. See “Editing serverproperties” on page 42 for instructions on editing database properties. See“Registering database servers manually” on page 26 for more information onmanually registering a Microsoft SQL Server.


Command line: You can use the command line to register a server with thewmregsvr command. The CLI syntax is:

wmregsvr -e <Endpoint>-s <ServerName>-h <Home>[-m <ProxyNode>]-u <Username>-p <Password>-v {v7 | 2k}[-d]-r <PolicyRegion>

where:

Endpoint<Endpoint> is the label of the endpoint.

ServerName<ServerName> is the name of the server on the endpoint you want toregister.

Home <Home> is the home directory of the Microsoft SQL Server.

ProxyNode<ProxyNode> is the name of the managed node to be used as the proxyhost.

Username<Username> is the username used to access the Microsoft SQL Server.

Password<Password> specifies the password to use with the specified username.

v7/2k Specifies the version of the server.

Note: You must specify the correct version of the server. The wmregsvrcommand does not produce an immediate error if the specifiedversion is not valid. Incorrect version numbers eventually result intask and resource model errors.

–d Specifies to use Microsoft SQL Server account authentication, not Windowsaccount authentication.

Policy Region<PolicyRegion> is the policy region in which to register the server.

Desktop:


1. Double-click the Monitoring for SQL Server policy region from the Tivolidesktop to display the Policy Region: Monitoring for Microsoft SQL Serverwindow.

2. Select Create from the menu to display the Create drop-down menu.3. Select Microsoft SQL Server to display the Create window.

where:4. Type the following information into the text boxes:

Name Specify the name of the server on the endpoint you want to register.

Home Specify the home (or directory) where the MicrosoftSQLServer isinstalled.

SQL Server AccountSelect the SQL Server Account check box for the resource model to useMicrosoftSQLServer authentication. If you do not check the box, theresource model uses Windows Domain/Local authentication. When theUsername format is DOMAIN\USER, the Username is authenticatedwith DOMAIN. If the ’DOMAIN\’ is excluded in the Username textbox, the resource model uses the local Windows system forauthentication.

UsernameSpecify a user name with access to the MicrosoftSQLServer you wish toregister.

PasswordSpecify the password of the MicrosoftSQLServer to be registered.

VersionSpecify the server version (v7, or 2k) defined in the registry key.

EndpointSpecify the name of the endpoint in which to register the databaseservers.

Proxy Managed NodeSpecify the managed node upon which you want the proxy object toreside.

5. Click Create to save the changes and close the Create window.


Chapter 4. Setting up IBM Tivoli Monitoring

This chapter provides a suggested order and the required procedures for setting upIBM Tivoli Monitoring.

Suggested guidelines for setting up your resource modelsTable 8 provides guidelines for the order to set up monitoring information and therequired procedures for setting up IBM Tivoli Monitoring. When you become morefamiliar with IBM Tivoli Monitoring, you will discover additional ways of workingwith resource models that meet the needs of your environment.

Note: For additional or advanced information on IBM Tivoli Monitoring in theTivoli environment, see the IBM Tivoli Monitoring User’s Guide.

Table 8. Monitoring resources and applications guidelines

Goal See

1. Set up profile managers and profiles to organize your resourcemodels. This makes the distribution of resource models moreefficient. You might need to set up multiple profile managers andprofiles within the profile managers to meet the needs of yourenvironment.

“Creating profile managers and profiles” onpage 30

2. Subscribe endpoints (MicrosoftSQLServer, and database objects)to the profile manager. This determines which resources receive aprofile when the profile is distributed. Profiles contain resourcemodels to run against the endpoints (see Step 3).

“Subscribing resources to profile managers”on page 32

3. Populate each profile in a profile manager with resource modelsfor the resource that you want to monitor. Include resourcemodels with the default values or customize the default values tomeet the needs of your environment.

“Adding default resource models to profiles”on page 33

4. For each resource model in your profile, do the following:v Determine how the resource model generates an event by

specifying the settings for each indication for that resourcemodel.

v Specify if you want to customize the resource modelparameters to optimize the monitoring process.

v Specify if you want the monitoring to occur at specific timeperiods on selected days.

“Customizing indications” on page 74

“Customizing parameters” on page 84

“Customizing the scheduling monitoringperiod” on page 87

5. For each profile in your profile manager, do the following:v Specify the subscribers that you want to distribute the

monitoring profile to and distribute the profile.v Specify the subscribers that you want to distribute the

monitoring profile to while using MDist2.v Determine if you must rerun any failed distributions.

“Distributing profiles from the desktop” onpage 34

“Distributing profiles using MDist2” on page36

“Rerunning failed profile distributions” onpage 38

29

Table 8. Monitoring resources and applications guidelines (continued)

Goal See

6. To maintain your profiles and resource models, do the following:v Determine if you want to clear the recovery actions of an

event.v Determine if you want to reinstate the recovery actions of an

event.v Specify if you want to manage profiles and resource models

after they are distributed to endpoints.v Specify if you want to manage IBM Tivoli Monitoring on

gateways.v Determine which resource models were distributed to an

endpoint.v Determine the specific resource models that are running on

each endpoint.v Use the IBM Tivoli Monitoring Web Health Console, Tivoli

Enterprise Console, Tivoli Enterprise Data Warehouse, or TivoliBusiness Systems Manager to view the information beingmonitored by your resource models

“Adding or removing built-in actions” onpage 77

“Managing profiles and resource models atendpoints” on page 91

“Managing IBM Tivoli Monitoring gateways”on page 92

“Determining which resource models havebeen distributed to endpoints” on page 93

“Determining which resource models arerunning on endpoints” on page 94

Creating profile managers and profiles

ObjectiveTo create profile managers and profiles to organize and distribute your resourcemodels more efficiently.

Background informationA monitoring profile is a group of defined resource models that you can distribute(download or push) to a subscribed (marked to receive) managed resource in aprofile manager.

In addition to activating default resource models, profile managers and profiles cangroup resources to enable simultaneous monitoring of multiple resources. You canhierarchically organize the profile managers. The profile manager is the top level ofthe organization and contains profiles that contain resource models. Servers arethen subscribed to the profile managers, which enable the monitoring informationto be channeled to those resources.

You can create an unlimited number of profile managers, but it is recommendedthat they reflect some logical or functional grouping of resources or the business’sorganizational structure. For example, profile managers could be labeled Sales andMarketing, Administration and Finance, and Operations to reflect a businessorganization.


Before you beginSet up the Tmw2kProfile managed resource types. Refer to the IBM TivoliMonitoring User’s Guide for information.

When you finishAdd resource models to the profile. See “Adding default resource models toprofiles” on page 33 or “Adding custom resource models to profiles” on page 76.



Command line:

1. Use the wcrtprfmgr command to create a profile manager.Additional Information: For example, to create a profile manager called ProfMgr2in the TestRegion policy region, enter the following command:wcrtprfmgr @PolicyRegion:TestRegion ProfMgr2

2. Optional: Use the wsetpm command to make the policy manager operate indataless mode. For example, to make the profile manager ProfMgr2 dataless,enter the following command:wsetpm -d @ProfileManager:ProfMgr2

where:

-d Specifies that the profile manager operates in a dataless mode.3. Use the wcrtprf command to create a profile. For example, to create a profile

called MarketingProf2 in the ProfMgr2 profile manager, enter the followingcommand:wcrtprf @ProfileManager:ProfMgr2 MarketingProfile MarketingProf2

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual.

Desktop:

1. Open the Policy Region window by double-clicking the policy region icon.2. Select Create → Profile Manager to open the Create Profile Manager window.3. Type a unique name in the Name/Icon Label text box.4. Optional : Select the Dataless Endpoint Mode check box to create the profile

manager in dataless mode.5. Click the Create & Close button to close the Create Profile Manager window.

Additional Information: In the following example, the policy region contains twoprofile manager icons, Manufacturing and Operations. The Manufacturingprofile manager is defined as dataless (the feathers under the Manufacturingprofile manager indicates that it is a dataless profile manager).

6. Double-click the profile manager icon to open the Profile Manager window.7. Select Create → Profile to open the Create Profile window.

Chapter 4. Setting up IBM Tivoli Monitoring 31

8. Type a unique name for the profile in the Name/Icon text box.9. Select the Tmw2kProfile resource from the Type list.

10. Click Create & Close.Additional Information: An icon for the new profile is displayed in the Profilesarea of the Profile Manager window.

Subscribing resources to profile managers

ObjectiveTo add managed resources to a monitoring profile so administrators can definewhich resource to monitor.

Background informationSubscribing resources to a profile manager determines which resources receive aprofile when the profile is distributed. IBM Tivoli Monitoring uses the list ofsubscribers to determine which systems are monitored. To add a subscriber to adistributed monitoring profile, you must add the subscriber to the profile manager.

Note: Resources can also be subscribed to profiles from the IBM Tivoli MonitoringProfile window. See “Distributing profiles from the desktop” on page 34.


Before you beginCreate a monitoring profile with monitoring sources. See “Creating profilemanagers and profiles” on page 30 for information.

When you finishDistribute the monitoring profile to the subscribed resource. See “Distributingprofiles from the desktop” on page 34 for information.


Command line: Use the wsub command to add subscribers to the profilemanager. For example, to add a server called Sample@bburns as a subscriber tothe profile manager DatabaseMonitors, enter the following command:wsub @ProfileManager:DatabaseMonitors @PolicyRegionName:Sample@bburns

For additional information about these commands, see the Tivoli ManagementFramework Reference Manual.

Desktop:

1. Open the Policy Region window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.

2. Double-click a profile manager icon to open the Profile Manager window.3. Select Profile Manager → Subscribers to open the Subscribers window.4. Select the subscribers to receive the profile distribution from the Available to

become Subscribers scrolling list.5. Click the left-arrow button to move the selected subscribers to the Current

Subscribers scrolling list.


6. Click Set Subscriptions & Close to add the subscribers.Additional Information: Subscribers are displayed in the Subscribers field of theProfile Manager window.

Adding default resource models to profiles

ObjectiveTo add a resource model to a profile using its default values to run the resourcemodel immediately.

Background informationA resource model captures and returns information about a resource or application.You set up resource models in profiles and distribute them to endpoints. Eachresource model monitors multiple resources. Choose the resource models to add toa profile based on the resources you want to monitor. Adding one or more of theseresource models to a profile allows you to begin monitoring resources immediately.

Put all of the resource models that you are going to distribute to the sameendpoint in a single profile because the distribution occurs on a per-profile basis.


Before you beginv Create a profile manager and profile. See “Creating profile managers and

profiles” on page 30 for information.v Add subscribers to a profile manager. See “Subscribing resources to profile

managers” on page 32 for information.v See the IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide

for detailed information about each resource model.

When you finishDistribute the profile. See “Distributing profiles from the desktop” on page 34.


Command line: Use the wdmeditprf command to add a default resource model toa profile.

Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon to open the profile manager.d. Double-click the profile icon to which you want to add a customized

resource model.2. Click Add With Defaults to open the Add Resource Models to Profile window.3. Select the resource model category from the Category drop-down list.4. Select the resource model you want from the Resource Model drop-down list.5. Click Add & Close to add the resource model to the IBM Tivoli Monitoring

Profile.


Distributing profiles from the desktop

ObjectiveTo distribute profiles to specified subscribers.

Background informationYou can distribute profiles to the following groups:

Next level of subscribersDistributes the profile only to the subscribers named in the Distribute toThese Subscribers: scrolling list of the Distribute Profile window. Thisoption does not distribute to subscribers at lower levels of the hierarchy.Perform the distribution process from profile managers at more than onelevel to reach all the profile endpoints if a profile manager with subscribersresides at the next lower level.

All levels of subscribersDistributes the profile to all subscribers in the hierarchy. Consider thefollowing example. You have a profile in which a dataless profile manageris subscribed to a profile manager, and the dataless profile manager has asubscribed endpoint. If you distribute to the next level of subscribers, theprofile manager distributes the profile only to the dataless profile manager.If you distribute to all levels of subscribers, the profile manager distributesthe profile to the dataless profile manager and to the endpoint.

Select this option if you want to distribute a profile in which your resourceis the only subscriber.


Before you beginv Ensure that the Java run-time environment (JRE) is running on each endpoint.

See the IBM Tivoli Monitoring for Databases: Installation and Setup Guide.v Create a profile manager and profile. See “Creating profile managers and


managers” on page 32 for information.v Add a resource model to a profile. See “Adding default resource models to

profiles” on page 33 and“Adding custom resource models to profiles” on page 76for information.

v See the IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guidefor detailed information about each resource model.

When you finishNone.

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Open the IBM Tivoli Monitoring Profile window by doing the following:

a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon you want to open the Profile Manager

window.d. Double-click the profile you want to distribute to open the IBM Tivoli

Monitoring Profile window.


2. Click Profile → Distribute. The Distribute Profile window opens.3. Select one of the Distribute To options based on the following descriptions:

Next level of subscribersDistributes the profile only to the subscribers named in the Distributeto These Subscribers: scrolling list of the Distribute Profile window.This selection does not distribute to subscribers at lower levels of thehierarchy. Perform the distribution process from profile managers atmore than one level to reach all the profile endpoints if a profilemanager with subscribers resides at the next lower level.

All levels of subscribersDistributes the profile to all subscribers in the hierarchy. Consider thefollowing example. You have a profile in which a dataless profilemanager is subscribed to a profile manager, and the dataless profilemanager has a subscribed endpoint. If you distribute to the next levelof subscribers, the profile manager distributes the profile only to thedataless profile manager. If you distribute to all levels of subscribers,the profile manager distributes the profile to the dataless profilemanager and to the endpoint.

Select this option if you want to distribute a profile in which yourresource is the only subscriber.

4. Select Make each subscriber’s profile an EXACT COPY of this profile fromthe Distribution Will options.Additional Information: This option overwrites the subscriber’s profile with anexact copy of the profile that you are distributing.

Note: Always select the Make each subscriber’s profile an EXACT COPY ofthis profile option when you distribute a profile to a Tivoli EnterpriseConsole endpoint. Do not select the Preserve modifications insubscriber’s copies of the profile option.

5. Select the subscribers to receive the profile using the following steps:a. Select the list of subscribers that you want to distribute the profile to from

the Do Not Distribute to These Subscribers scrolling list.b. Click the left arrow to move the subscribers to the Distribute to These

Subscribers scrolling list.

Note: Make sure that each subscriber in the Distribute to These Subscribersscrolling list is either a profile manager or a supported Tivolimanagement agent endpoint. IBM Tivoli Monitoring does not supportother types of endpoints.

6. Click one of the following:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profilewindow, saves the settings you made, and returns to the IBM TivoliMonitoring Profile window.

DistributeDistributes the profile immediately, saves the settings you made, andleaves the Distribute Profile window open.

ScheduleSchedules the distribution of the profile with the Tivoli Scheduler. Fordetails about using the Tivoli Scheduler, refer to the Tivoli ManagementFramework User’s Guide.


Distributing profiles using MDist2

ObjectiveTo circulate copies of the monitoring profile to subscribers while using MDist2 sothat administrators and users can activate the monitoring process.

Background informationIBM Tivoli Monitoring uses Multiplexed Distribution (MDist2) to performasynchronous profile data transfers through a hierarchy of repeaters. MDist2returns a sequence of responses containing the distribution status from eachendpoint to the application initiating the distribution. These responses are sentback to IBM Tivoli Monitoring in a log file, on the MDist2 command line, orthrough the MDist2 GUI.

IBM Tivoli Monitoring uses the following MDist2 functions:

Asynchronous deliveryIBM Tivoli Monitoring submits a distribution request and immediatelyreceives a distribution identifier and confirmation that the distribution is inprogress. MDist2 uses the callback function to send the final distributionstatus for each endpoint when it completes each endpoint distributioninstead of waiting until all endpoints are distributed.

Assured deliveryAssures that distributed profiles are delivered to the endpoints when thereare network interruptions, computer shutdowns, or disconnectedendpoints. Assured delivery tries to reestablish the connections until it iseither successful or the distribution time expires. The distribution begins atthe point where it was interrupted.

Check-point and restartAssures that an interrupted data stream resumes from the last successfulcheckpoint. You do not have to resend all the IBM Tivoli MonitoringProfile data when the distribution resumes, but only the data that was notsent when the interruption occurred.

Data deportingStores segments of the profile at a depot close to the endpoint so theendpoints can retrieve the data from the depot instead of from the sourcehost. This reduces network traffic and speeds up the distribution.





profiles” on page 33 and“Adding custom resource models to profiles” on page 76for information.


When you finishNone



Command line: Use the wdmdistrib command to distribute the profile to thesubscribers of the profile manager. For example, to distribute the default profileDBManager-DBMSMonProfile to an instance endpoint labeled inst1@bburns,enter the following command:wdmdistrib @Tmw2kProfile:DBManager-DBMSMonProfile \@MicrosoftSQLServer:inst1@bburns

This command updates subscriber databases and configuration files. If nosubscriber is specified, wdmdistrib updates all subscribers. The syntax variesdepending on the version of Tivoli management region that you installed. Refer tothe IBM Tivoli Monitoring documentation for more information about thewdmdistrib command.

Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon you want to open the Profile Manager

window.d. Double-click the profile you want to distribute to open the IBM Tivoli

Monitoring Profile window.2. Select Profile → Distribute to display the Distribute Profile window.3. Select one of the Distribute To options based on the following descriptions:

v Next Level of Subscribers Distributes the profile only to the subscribersnamed in the Distribute to These Subscribers: scrolling list of the DistributeProfile window. This selection does not distribute to subscribers at lowerlevels of the hierarchy. Perform the distribution process from profilemanagers at more than one level to reach all the profile endpoints if a profilemanager with subscribers resides at the next lower level.

v All Levels of Subscribers Distributes the profile to all subscribers in thehierarchy. Consider the following example. You have a profile in which adataless profile manager is subscribed to a profile manager, and the datalessprofile manager has a subscribed endpoint. If you distribute to the next levelof subscribers, the profile manager distributes the profile only to the datalessprofile manager. If you distribute to all levels of subscribers, the profilemanager distributes the profile to the dataless profile manager and to theendpoint.Select this option if you want to distribute a profile in which your resource isthe only subscriber.

4. Select one of the Distribute Will options based on the following descriptions:v Preserve modifications in subscribers’ copy of the profile retains changes to

existing monitors in each copy of the profile. If you edit the configuration ofa monitor in the subscriber’s copy, those changes are written to every copy ofthat profile.

v Make subscribers’ profile an EXACT COPY of this profile overwrites thesubscriber’s profile with an exact copy of the profile being distributed.

5. Verify that the Distribute To These Subscribers list includes only thosesubscribers to receive the profile. Use the left and right arrows to move selectedsubscribers between lists.


6. Click Distribute & Close to begin the distribution and close the DistributeProfile window.

7. Optional : Schedule when the distribution will occur by completing thefollowing steps:a. Click the Schedule button to display the Add Scheduled Job window.b. Set the job options as needed or See “Customizing the scheduling

monitoring period” on page 87 for more information.c. Click Schedule Job & Close to set the schedule.

8. Click Distribute & Close to begin the distribution and close the DistributeProfile window.

9. Select Profile → Close to close the IBM Tivoli Monitoring Profile window.

Rerunning failed profile distributions

ObjectiveTo verify that the distribution to an endpoint failed so that you can rerun thedistribution for the failed endpoint.

Background informationWhen a distribution fails, IBM Tivoli Monitoring creates a profile manager thatcontains the endpoint subscribers that failed.

When you successfully redistribute profiles, the software deletes the profilemanager that it created for the failed distribution. A wholly or partiallyunsuccessful redistribution retains the profile manager containing only thesubscribers that were unsuccessful in the redistribution. Continue the process ofcorrecting the errors and retrying the distribution until the profile is successfullydistributed to all endpoints.



When you finishNone


Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.

2. Select View → Refresh from the Policy Region window to see the new profilemanagers.

3. Review the new profile manager names to determine and correct the cause ofthe failure. The following profile manager names are derived from a faileddistribution:v The failed distribution creates the following profile manager name due to a

Bad_Interpreter error:OriginalProfileName_Push_Failed_Bad_Interpreter


where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

The AMW089E error message is displayed at this point, indicatingthat the resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX-T endpoint.

v The failed distribution creates the following profile manager name due toany other error:OriginalProfileName_Distribution_Failed

where:

OriginalProfileNameThe name of the profile that you were distributing when the erroroccurred.

4. Subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile.

Note: This can be done only if the profile manager used for the originaldistribution was not a dataless endpoint.

5. Distribute the original profile to the failed endpoints by selecting these profilemanagers as the target for the distribution. You can also edit the profilemanagers to delete an endpoint from a group of failed endpoints beforeretrying the distribution.


Chapter 5. Working with IBM Tivoli Monitoring for Databases:Microsoft SQL Server

After you finish setting up the components of IBM Tivoli Monitoring forDatabases: Microsoft SQL Server, you are ready to manage and monitor MicrosoftSQL Server databases.

Table 9 provides an overview of the procedures covered in this chapter.

Table 9. Procedures for working with IBM Tivoli Monitoring for Databases: Microsoft SQLServer

Goal Refer to

1. View server properties so you can verifyserver information.

“Viewing server properties” on page 41

2. Modify the server information so you canconfigure the server properties.

“Editing server properties” on page 42

3. Start a server so you can use the server and itsservices.

“Starting a server” on page 44

4. Stop the server operations so you can performother tasks with the server stopped.

“Shutting down a server” on page 49

Viewing server properties

ObjectiveTo display server properties so you can review server information.

Background informationThe View Properties option displays the following information about the server:

Table 10. Server properties


Name The name of the server on the endpoint you want to register. The servername is defined in the registry key. For registry key locations, see page23.

Home The server home directory defined in the registry key. For registry keylocations, see page 23.

SQL ServerAccount

A check box used to indicate whether to use database authentication or aWindows domain. By default, the box is unchecked.

Username The user name is not defined in the registry key. You must specify a username in the Set Properties window. See “Editing server properties” onpage 42 for instructions.

Password The password is not defined in the registry key. You must specify apassword in the Set Properties window. See “Editing server properties”on page 42 for instructions.

Version The server version (v7 or 2k) defined in the registry key. For registry keylocations, see page 23.

Endpoint The name of the endpoint in which to register the database servers.

41

Table 10. Server properties (continued)


Proxy ManagedNode

The managed node upon which you want the proxy object to reside.

Required authorization rolemssqlserver_dba or mssqlserver_user


When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Open the Tivoli desktop.2. Double-click the Monitoring for Microsoft SQL Server policy region to display

the Policy Region: Monitoring for Microsoft SQL Server window.3. Right-click the server icon to display the server drop-down menu.

4. Select View Properties from the server drop-down menu to display the ViewProperties window.Additional Information: Click Help for a description of the properties or seeTable 10 on page 41.

5. Click Cancel to close the View Properties window.

Editing server properties

ObjectiveTo open the server property window so you can change the logon details for acurrently registered server.

Background informationYou can use the Edit Properties option to change the logon details for a currentlyregistered server when the current logon is no longer valid. Upon completion ofthis procedure, the properties window displays the user ID but does not displaythe password.


Required authorization rolemssqlserver_dba and senior


When you finishNone


Command line: You can use the command line to edit server properties with thewmchregsvr command. The CLI syntax is:

wmchregsvr[-h <Home>][-u <Username>][-p <Password>][-v {v7 | 2k}][{-d | -o}]SQLServer

where:

Home <Home> is the home directory of the Microsoft SQL Server.

Username<Username> is the username used to access the Microsoft SQL Server.

Password<Password> specifies the password to use with the specified username.

v7/2k Specifies the version of the server.

–d/-o Specifies the authentication method. –d uses Microsoft SQL Server accountauthentication. –o uses Windows account authentication.

Desktop:

1. Open the Tivoli desktop.2. Double-click the Monitoring for Microsoft SQL Server icon to display the

Policy Region: Monitoring for Microsoft SQL Server window.3. Right-click the server icon to display the server drop-down menu.

Chapter 5. Working with IBM Tivoli Monitoring for Databases: Microsoft SQL Server 43

4. Select Edit Properties from the server pop-up menu to display the EditProperties window.

Additional Information: The Name, Endpoint, and Proxy Managed Node fieldscannot be updated.

5. Type the server home directory defined in the registry key in the Home field.6. Specify a user authentication method by doing one of the following to the

SQL Server Account check box:v Check the check box to use Microsoft SQL Server authentication.

—OR—v Leave the check box unchecked to use the Windows domain/local

authentication. By default, the check box is not checked.7. Do one of the following in the Username field:

v Leave this field blank.—OR—

v Type a user name with access to the server.8. Do one of the following in the Password field:

v If you specified a Username, type the corresponding password in thePassword field.—OR—

v If you did not specify a Username, leave this field blank.9. Click the Version down-arrow to select the server version (7 or 2000) defined

in the registry key.10. Do one of the following:

v Click Update to save the changes and close the window.—OR—

v Click Cancel to cancel any changes and close the window.

Starting a server

ObjectiveTo start a Microsoft SQL Server from the Tivoli desktop so you can use or edit theserver.


Background informationStarting a Microsoft SQL Server starts or continues the following Microsoft SQLServer services on a specified endpoint:v Microsoft SQL Server Service (Database engine)v ServerAgent (SQL server agent)v MSDTC (Microsoft Distributed Transaction Coordinator)v Microsoft Search (Microsoft search service — for Microsoft SQL Server 2000

only)

You can start services independently. The Continue option restarts services thatwere paused.

Starting a server utilizes the StartMSSQLServerServices task. For moreinformation on tasks, see the IBM Tivoli Monitoring for Databases: Microsoft SQLServer Reference Guide.

You can perform this procedure using one of the following methods:v Run the StartMSSQLServerServices task from the

ITMMicrosoftSQLServerTasks library from the command line interface.v Right-click menu from the server object icon on the desktop.v Run the StartMSSQLServerServices task from the

ITMMicrosoftSQLServerTasks library on the desktop.

Required authorization rolemssqlserver_dba

Microsoft SQL Server Permissions: System Administrators

Before you beginThe ServerAgent is dependent upon the Microsoft SQL Server Service. IfServerAgent is started, Microsoft SQL Server Service also starts, if it is not running.

When you finishNone


Command line: You can use the command line to start a server with thewruntask command. Although all the arguments are optional, you must specify atleast one. If you use only one argument, it cannot be StartMode=None. The CLIsyntax is as follows:

–t StartMSSQLServerServices–l ITMMicrosoftSQLServerTasks–h <target for task>[–a {START | NO_CHANGE | CONTINUE}][–a {START | NO_CHANGE}][–a {START | NO_CHANGE}][–a {START | NO_CHANGE}]

where:

The first parameter refers to the Microsoft SQL Server ServiceSTART starts the service required for any operations to be carried out on


the server or its databases. NO_CHANGE does not alter the current stateof the service. CONTINUE restarts the service after it has been paused.

GUI Name: Start Microsoft SQL Server Service?

The second parameter refers to the Microsoft SQL Server ServerAgentSTART starts the service required for running Microsoft SQL Server tasksand replication. NO_CHANGE does not alter the current state of theservice.

GUI Name: Start Microsoft SQL Server ServerAgent?

The third parameter refers to the Microsoft SQL Server MSDTCSTART starts the service required for distributed transaction control.NO_CHANGE does not alter the current state of the service.

GUI Name: Start Microsoft SQL Server MSDTC?

The fourth parameter refers to the Microsoft Search Service(Microsoft SQL Server 2000 only) START starts the service that assists incomplex search queries. NO_CHANGE does not alter the current state ofthe service.

GUI Name: Start Microsoft Search Service?

For example, to the following command starts the Microsoft SQL Server serviceson @MicrosoftSQLServer:hbergin@abc:wruntask -t StartMSSQLServerServices-l ITMMicrosoftSQLServerTasks-h @MicrosoftSQLServer:hbergin@abc-a START-a START-a START-a START

For more information about the wruntask command, refer to the online manualpage.

Desktop: (Server object icon right-click menu)

1. Open the Tivoli desktop.2. Double-click the Monitoring for Microsoft SQL Server policy region to display

the Policy Region: Monitoring for Microsoft SQL Server window.3. Right-click the server object icon to display the server drop-down menu.


4. Select Start from the server object drop-down menu to start the Microsoft SQLServer services.

Desktop: (Run the task from the desktop)

1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the Monitoring for Microsoft SQL Server policy region icon

to display the Policy Region: Monitoring for Microsoft SQL Server window.c. Double-click the ITMMicrosoftSQLServerTasks icon to display the product

task library window.2. Double-click the StartMSSQLServerServices task icon to display the Execute

Task window.Additional Information: The Execute Task window is a generic window ofexecution parameters for all tasks.

3. Click one of the following check boxes in the Execution Mode group box:v Parallel runs the task simultaneously on all targets. Parallel is typically the

fastest method of execution.—OR—

v Serial runs the task sequentially on all targets in alphabetical order.—OR—

v Staged runs the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you run the task on alarge number of endpoints. Specify the Staging Count (number of targets torun against for each stage) and the Staging Interval (number of secondsbetween each set).

4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional Information: The Timeout value does not stop the task. This valuespecifies the number of seconds the desktop waits for the task to completebefore it issues an error. The task continues to execute on the endpoint withoutdisplaying the output results. Setting an early timeout enables your desktop tobecome available again if the task takes a long time to execute. The default is60 seconds. If the task takes longer to complete than the specified Timeout andis running in Serial or Staged mode, the software moves on to other endpointsafter this time expires.

5. Select one or more of the following check boxes in the Output Format groupbox to choose the output returned when the task completes:

HeaderIncludes a descriptive header for each record, such as the task nameand target.

Return CodeIncludes the programming codes produced when the task runs.

Standard ErrorIncludes all error messages encountered when the task runs.

Standard OutputIncludes all information that results from running the task.

6. Select one of the following in the Output Destination group box to choose anoutput destination:v Select Display on Desktop to display the task output on the desktop.


Additional Information: If you choose Display on Desktop, you have anoption to save the information to a file as an option inside the output displaywindow.—OR—

v Click Save to File to save the output to a file.

To save the task output to a file, do the following:a. Click the Save to File check box in the Output Destination group box to

display the Destination for Task Output window.b. Type the name of the endpoint on which to save the output in the On Host

text box.Additional Information: The endpoint must be a Tivoli client.

c. Type the absolute path name for the output file in the Output File text box.Additional Information: Example: /tmp/mytask.out

d. Click Set & Close to set your choices and return to the Execute Taskwindow.

7. Choose the endpoints on which you want to run the task by doing one of thefollowing:v Run the task on specific endpoints by doing the following:

a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow button to move the selected endpoints to the Selected

Task Endpoints list.

—OR—v Run the task on all subscribers of the specified profile managers by doing the

following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.8. Click Execute to display the task argument window and configure the

StartMSSQLServerServices task.

where:

Start Microsoft SQL Server Service?Click New State to display a window with options for starting the


Microsoft SQL Server service. Choose one of the following from theStart Microsoft SQL Server Service window:

NO CHANGEMaintains the current state setting.

STARTStarts the server in multi-user mode with full access.

Start Microsoft SQL Server ServerAgent?Click New State to display the window that includes options forstarting the Microsoft SQL Server ServerAgent. Choose one of thefollowing from the Start Microsoft SQL Server ServerAgent window:


STARTStarts the service required for running Microsoft SQL Servertasks and replication.

CONTINUEContinues the service, if it is paused.

Start Microsoft SQL Server MSDTC?Click New State to display the window that includes options forstarting the Microsoft SQL Server MSDTC. Choose one of the followingfrom the Start Microsoft SQL Server MSDTC window:


STARTStarts the service required for distributed transaction control.

Start Microsoft Search Service?(Microsoft SQL Server 2000 only) Click New State to display thewindow that includes options for starting the Microsoft Search Service.Choose one of the following from the Start Microsoft Search Service?window:


STARTStarts the Microsoft Search Service so you can use the searchservice.

9. Click Set & Execute to run the task.

Shutting down a server

ObjectiveTo stop a Microsoft SQL Server from the Tivoli desktop so you can stop serverservices on a specified endpoint.

Background informationStopping a Microsoft SQL Server stops the following Microsoft SQL Server serviceson a specified endpoint:v Microsoft SQL Server Service (Database engine)v ServerAgent (SQL server agent)v MSDTC (Microsoft Distributed Transaction Coordinator)


v Microsoft Search (Microsoft search service — for Microsoft SQL Server 2000only)

You can stop services independently. Stopping a Microsoft SQL Server uses theStopMSSQLServerServices task. For more information on this task, see the IBMTivoli Monitoring for Databases: Microsoft SQL Server Reference Guide

You can perform this procedure using one of the following methods:v Run the StopMSSQLServerServices task from the

ITMMicrosoftSQLServerTasks library from the command line interface.v Use the right-click menu from the server object icon on the desktop.v Run the StopMSSQLServerServices task from the

ITMMicrosoftSQLServerTasks library using the desktop.

Required authorization rolemssqlserver_dba

Microsoft SQL Server Permissions: System Administrators

Before you beginThe ServerAgent is dependent upon the Microsoft SQL Server Service. If both arerunning when the Microsoft SQL Server Service stops, the ServerAgent stops also.

When you finishNone


Command line: You can shut down the server services from the command lineusing the wruntask command with the following parameters:

–t StopMSSQLServerServices–l ITMMicrosoftSQLServerTasks–h <Object Name>[–a {STOP | NO_CHANGE | PAUSE}][–a {STOP | NO_CHANGE}][–a {STOP | NO_CHANGE}][–a {STOP | NO_CHANGE}]

where:

The first parameter refers to the Microsoft SQL Server ServiceSTOP stops the SQLExecutive service. NO_CHANGE does not alter thecurrent state of the service. PAUSE pauses the service.

GUI Name: Stop or Pause Microsoft SQL Server Service?

The second parameter refers to the Microsoft SQL Server ServerAgentSTOP stops the SQLServerAgent service. NO_CHANGE does not alter thecurrent state of the service.

GUI Name: Stop or Pause Microsoft SQL Server ServerAgent?

The third parameter refers to the Microsoft SQL Server MSDTCSTOP stops the service required for distributed transaction control.NO_CHANGE does not alter the current state of the service.

GUI Name: Stop Microsoft SQL Server MSDTC?


The fourth parameter refers to the Microsoft Search Service(Microsoft SQL Server 2000 only) STOP stops the service used for complexsearches. NO_CHANGE does not alter the current state of the service.

GUI Name: Stop Microsoft Search Service?

For example, the following command shuts down the@MicrosoftSQLServer:VISION117@vision117 server:wruntask -t StopMSSQLServerServices-l ITMMicrosoftSQLServerTasks-h @MicrosoftSQLServer:VISION117@vision117-a STOP-a STOP-a STOP-a STOP

For more information about the wruntask command, refer to the TivoliManagement Framework Reference Manual.

Desktop: (Server object icon right-click menu)


the Policy Region: Monitoring for Microsoft SQL Server window.3. Right-click the server object icon to display the server drop-down menu.

4. Select Stop from the server object drop-down menu to stop the Microsoft SQLServer’s services.

Desktop: (Run the task from the desktop)

1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the product task icon to display the product task library

window.


2. Double-click the task icon that you want to run to display the Execute Taskwindow.Additional Information: The Execute Task window is a generic window ofexecution parameters for all tasks.





4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional Information: The Timeout value does not stop the task. This valuespecifies the number of seconds the desktop waits for the task to completebefore it issues an error. The task continues to execute on the endpoint withoutdisplaying the output results. Setting an early timeout enables your desktop tobecome available again if the task takes a long time to execute. The default is60 seconds. If the task takes longer to complete than the specified Timeout andis running in Serial or Staged mode, the product moves on to other endpointsafter this time expires.

5. Click one or more of the following check boxes in the Output Format groupbox to choose the output returned upon task completion:



Return CodeIncludes the programming codes produced when the task executes.

Standard ErrorIncludes all error messages encountered when the task executes.

Standard OutputIncludes all information that results from the task execution.

6. Select one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Desktop to display the task output on the desktop.




display the Destination for Task Output window.b. Type the name of the endpoint on which to save the output in the On Host

text box.Additional Information: The endpoint must be a Tivoli client.








Selected Profile Managers list.


8. Click Execute to display the task argument window and configure theStopMSSQLServerServices task.

where:

Stop or Pause Microsoft SQL Server Service?Click New State to display a window with options for stopping theMicrosoft SQL Server Service. Choose one of the following from theStop or Pause Microsoft SQL Server Service? window:


STOP Stops server without waiting for transactions to finish.

Stop or Pause Microsoft SQL Server ServerAgent?Click New State to display a window with options for stopping theMicrosoft SQL Server ServerAgent. Choose one of the following fromthe Stop or Pause Microsoft SQL Server ServerAgent? window:


PAUSEStops any new users from logging onto the server.

STOP Stops the SQLServerAgent service. The service is required forrunning Microsoft SQL Server tasks and replication.

Stop Microsoft SQL Server MSDTC?Click New State to display a window with options for stopping theMicrosoft SQL Server MSDTC. Choose one of the following from theStop Microsoft SQL Server MSDTC? window:


STOP Stops the service required for distributed transaction control.

Stop Microsoft Search Service?(Microsoft SQL Server 2000 only) Click New State to display a windowwith options for stopping the Microsoft Search Service. Choose one ofthe following from the Stop Microsoft Search Service? window:



STOP Stops the Microsoft Search Service.9. Click Set & Execute to run the task.


Chapter 6. Working with tasks and jobs

A task is an action that must be performed routinely on selected managedresources throughout the network. A task defines the executables to run, theauthorization role required to run the task, and the user or group name underwhich the task runs. The software provides standard tasks in a task library.Standard tasks run on any computer, regardless of the type of operating system.

A customized task is a standard task with defined arguments saved in the tasklibrary with a unique name. For example, you can customize a task to save taskoutput results to a file after each execution. Because you can customize taskarguments, the Tivoli environment does not display argument windows when yourun the task from the desktop. However, if you run a customized task from thecommand line, you must still specify the task arguments. Running a customizedtask requires additional information before it runs, such as the target of theexecution.

A job is a task with defined and saved arguments that can be executed many timeson specific managed resources. You can create jobs from both standard andcustomized tasks in the product task library. Like tasks, you store jobs in tasklibraries so you can reuse them. After you create a job, you can run it immediatelyby using the procedure described in “Running a job” on page 65. You also canschedule jobs to run at certain times in the Scheduler, as described in “Schedulinga job” on page 66.

Table 11 shows the options to manage tasks and jobs.

Table 11. Working with Tasks and Jobs

Goal Refer to

1. Running a task to perform a specificoperation.

“Running a task” on page 58

2. Defining a standard task with specificarguments to customize the task.

“Customizing a task” on page 61

3. Creating a job from a task so that it can bescheduled to run.

“Creating a job” on page 62

4. Running a job with predefined arguments. “Running a job” on page 65

5. Scheduling jobs to run at specified times. “Scheduling a job” on page 66

The installation process installs the task library in the product policy region. Donot remove the task library from this policy region. The task library containsdefault policies that affect how the task library works.

The policy region containing the task library defines a task default policy. Defaultpolicies set profile manager options and endpoint for tasks. Validation policiescontrol the creation and execution of tasks.

57

Running a task

ObjectiveTo customize one of the standard tasks in the task library so you can save definedarguments for future executions.

Background InformationA task is an action that must be routinely performed on selected managedresources throughout the network. A task defines the executables to run, theauthorization role required to execute the task, and the user or group name underwhich the task is run. The product provides standard tasks in a task library.Standard tasks run on any machine without consideration of platform type.

Required Authorization RolesEach task requires a specific authorization role to be able to run the task. Refer tothe IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide for therequired authorization role for each task.

Before You BeginNone

When You FinishNone


Command line: Use the wruntask command to run a task. Because not all usersuse the same task library, the documentation for the wruntask command does notprovide information for specific tasks. See the “CLI (command line interface)syntax” and “CLI example” sections in the product reference guide. The “CLIexample” section provides an example of how to enter the wruntask commandand the task arguments at the command line.

For more information about the wruntask command, see the Tivoli ManagementFramework Reference Manual.

Desktop:

1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the product task icon to display the product task library

window.2. Double-click the task icon that you want to run to display the Execute Task

window.


Additional Information: The Execute Task window is a generic window ofexecution parameters for all tasks.





4. Type a timeout value (in seconds) for the task in the Timeout text box.Additional Information: The Timeout value does not stop the task. This valuespecifies the number of seconds the desktop waits for the task to completebefore it issues an error. The task continues to execute on the endpoint withoutdisplay of output results. Setting an early timeout enables your desktop tobecome available again if the task takes a long time to execute. The default is

Chapter 6. Working with tasks and jobs 59

60 seconds. If the task takes longer to complete than the specified Timeout andis running in Serial or Staged mode, the product moves on to other endpointsafter this time expires.

5. Click one or more of the following check boxes in the Output Format groupbox to choose the output returned upon task completion:


Return CodeIncludes the programming codes produced when the task executes.

Standard ErrorIncludes all error messages encountered when the task executes.

Standard OutputIncludes all information that results from the task execution.

6. Select one of the following in the Output Destination group box to choose anoutput destination:v Click Display on Desktop to display the task output on the desktop.




display the Destination for Task Output window.b. Type the name of the managed resource on which to save the output in the

On Host text box.Additional Information: The managed resource must be a Tivoli client.








Selected Profile Managers list.8. Click Execute to display the task argument window.


Additional Information: For information about how to fill in the task argumentwindow, refer to the task description in the product reference guide or clickTask Description to display the online help.

9. Click Set & Execute to run the task.

Customizing a task

ObjectiveTo customize one of the standard tasks in the task library so you can save definedarguments for future executions.

Background InformationA customized task is a standard task with defined arguments saved in the tasklibrary with a unique name. For example, you can customize a task to save taskoutput results to a file after each execution. Because you can customize taskarguments, the Tivoli environment does not display argument windows when yourun the task from the desktop. However, if you run a customized task from thecommand line, you still must specify the task arguments. Running a customizedtask requires additional information before it runs, such as the target of theexecution.

Required Authorization Rolesadmin


When You FinishYou can run the task by following the procedure in “Running a task” on page 58.When you run a customized task, the Tivoli desktop does not display the taskargument window.

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Open the task library window by doing the following:

a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the product Task icon to display the task library window.

2. Double-click a task icon to display the Execute Task window for that task.3. Click Execute to display the task argument window.

Additional Information: Each standard task has a unique task argumentwindow. Below is one example of a task argument window.

4. Enter the appropriate values for this customized task.Additional Information: For information about each field in these windows, seethe task description in the product reference guide or click Task Descriptionto display the online help.

5. Click Save to display the Save Argument window.6. Type the following information to define the customized task:

a. Type a name for the task in the Name text box.Additional Information: This name appears in the Library Contents field soyou can view the customized tasks that are based on the parent task.

b. Type an identifier for this task.


Additional Information: An identifier is the name of the task icon in the TaskLibrary window. A customized task identifier has two parts. The first partshould be the standard task name (such as DiscoverMSSQLServers). Thesecond part should be descriptive information that makes sense to you.For example, you could type SYS. The resulting task name would beDiscoverMSSQLServers_SYS.The software generates a unique default name (such asDiscoverMSSQLServers_aaa) if no identifier is entered.To enable filtering for an identifier without the standard task name, editthe tl_def_man_nodes policy method in the task library policy object. Seethe Tivoli Management Framework Reference Manual for more information.

c. Type a description of this task in the Description text box.Additional Information: This description appears when you click TaskDescription in the task argument window for this customized task.

d. Optional: Select the Show by Identifier check box to change the LibraryContents list to use the task identifier instead of the task name.

e. Optional: Click Parent Description to display information about the parenttask from which you are creating a customized task.Additional Information: The task information appears under the headingDescription.

f. Click Save & Close to return to the task argument window.7. Click Cancel in the task argument window.8. Click Close in the Execute Task window to return to the Task Library window.9. Click View to display the View drop-down menu.

10. Click Refresh from the View drop-down menu to display the new customizedtask.

Creating a job

ObjectiveTo create a job by defining execution parameters so you can specify a target thatenables you to schedule the job to run at certain times.

Background InformationA job is a task with defined and saved arguments that can be executed many timeson specific managed resources. You can create jobs from both standard andcustomized tasks in the product task library. Like tasks, store jobs in task librariesso you can reuse them.

Required Authorization Rolesadmin


When You FinishAfter you create a job, you can run it immediately using the procedure describedin “Running a job” on page 65. You also can schedule jobs to run at certain timesin the Scheduler, as described in “Scheduling a job” on page 66.



Command line: Use the wcrtjob command to create jobs from the command line.The syntax is as follows:

wcrtjob –j job_name –l library_name –t task_name –M mode [–s interval –n number]–m timeout –o output_format [–D|–d hostname –f file_name] [–h task_endpoint] [–pprof_manager_name]

where:

–j job_nameThe name of the job being created. Job names can include anyalphanumeric character, an underscore (_), a dash (–), a period (.), and aspace.

–l library_nameSpecifies the task library containing the task to be included in the job.

–t task_nameSpecifies the name of the task to include in the job.

–M modeSpecifies the mode in which the job runs. Valid options are as follows:

parallelRuns the job on all specified endpoints and any subscriberssimultaneously.

serial Runs the job on one endpoint at a time.

staged Runs the job on a set number of endpoints at specified intervals.

–m timeoutSpecifies the number of seconds that the task library waits for results to bereturned from the task. This option does not affect the execution of the job.If you are using staged mode, the timeout must be smaller than theinterval time.

–o output_formatDefines the format of the job output. The job output contains a summaryof the job on each managed node. Task execution output format isspecified with an octal number from 0 to 17. The format is constructed byadding the value of the desired output. For example, to print the task’sreturn code and standard output, enter —o 12. Output values are asfollows:

01 Prints a descriptive header for each record

02 Prints the task’s return code

04 Prints the standard error output

10 Prints the standard output

–D Displays the job output to the screen.

–d hostname and —f file nameSpecifies the host system and file name in which to save the job output.

–h task_endpointSpecifies the endpoint on which to run the job.

–p prof_manager_nameSpecifies the profile managers on which the job runs.

Desktop:


1. Access the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the task library icon to display the task library window.

2. Click Create to display the Create drop-down menu.3. Click Job from the Create drop-down menu to display the Create Job window.4. Type a descriptive job name in the Job Name text box.

Additional Information: The job name identifies the icon on the desktop. Thename can include any alphanumeric character, an underscore (_), dash (–),period (.), or blank space.

5. Select the task on which the job is based from the Task Name list.6. In the Execution Mode group box, select one of the following check boxes:

ParallelRuns the task simultaneously on all targets. Parallel is typically thefastest method of execution.

—OR—

Serial Runs the task sequentially on all targets in alphabetical order.

—OR—

StagedRuns the task on all targets in alphabetical order according to aschedule you specify. Staged execution is useful if you are running thetask on a large number of endpoints. Complete Step 8 to specify theStaging Count (number of targets to run against per stage) and theStaging Interval (number of seconds between each set).

7. In the Execution Parameters group box, type the timeout value (in seconds)for the task in the Timeout text box.Additional Information: This value specifies the number of seconds the productwaits for the task or job to complete before it issues an error. The default is 60seconds. If the task takes longer to complete than the specified Timeout and isrunning in Serial or Staged mode, the product moves on to other endpointsafter this time expires. The task continues to execute on the endpoint, eventhough the product stopped waiting for it to end.

8. Optional: If you selected Staged in Step 6, specify the number of managedresources to include in each staged set in the Staging Count text box and thenumber of seconds between each set’s startup time in the Staging Intervaltext box.

9. Click one or more of the following check boxes to choose the output type inthe Output Format group box:

HeaderIncludes a descriptive header for each record.

Return CodeIncludes the programming codes produced when the job executes.

Standard ErrorIncludes all error messages encountered when the job executes.

Standard OutputIncludes all information that results from the job execution.

10. Do one of the following in the Output Destination group box to choose anoutput destination:


v Click Display on Desktop to display the job output on the desktop. Go toStep 12.Additional Information: If you choose Display to Desktop, you have anoption to save the information to a file as an option inside the outputdisplay window.—OR—

v Click Save to File to save the output to a file and display the Destinationfor Task Output window. Go to Step 11.

11. Do the following in the Destination for Task Output window to save the joboutput to a file:a. Type a Tivoli managed resource name on which to save the output in the

On Host text box.b. Type the absolute path name for the output file in the Output File text

box.Additional Information: Example: /tmp/myjob.out

c. Click Set & Close to set your choices and return to the Create Job window.12. Do one of the following to choose the managed resources on which to run the

job:v Run the job on specific managed resources by doing the following:

a. Select the managed resources from the Available Task Endpoints list.b. Click the left arrow button to move the selected managed resources to

the Selected Task Endpoints list.–OR–

v Run the job on all subscribers of the specified profile managers by doingthe following:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow button to move the selected profile managers to the

Selected Profile Managers list.13. Click Create & Close to create the job and return to the Task Library window.

Additional Information: The new job icon appears in the Task Library window.

Running a job

ObjectiveTo execute a job on specific endpoints immediately so you can perform amanagement operation.

Background InformationBefore you can run a job, you must create it, as described in “Creating a job” onpage 62.

If you created a job from a standard task, the Tivoli desktop displays the taskargument window so that you can fill in any required information.

Jobs created from customized tasks run without further input because all requiredinformation is specified. (See “Customizing a task” on page 61 for informationabout how to create a customized task.)


Required Authorization RolesEach job requires a specific authorization role to be able to run the job. Refer to theIBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide for therequired authorization role for each job.


When You FinishAfter you create a job, you can set it up to run on a regular schedule as describedin “Scheduling a job” on page 66.


Command line: Use the wrunjob command to run jobs from the command line.For more information about this command, see the Tivoli Management FrameworkReference Manual

Desktop:

1. Open the task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the task icon to display the task library window.

2. Do one of the following:v Double-click the job icon created from a customized task to begin executing

the job.–OR–

v Double-click the job icon created from a standard task. Go to Step 3.3. Type the values in the task window.

Additional Information: For information about specific fields, see the taskdescription in the product reference guide or click Task Description to displaythe online help. The product runs the job and displays the output on thedesktop or sends it to a file in accordance with the job specification.

Scheduling a job

ObjectiveTo schedule jobs to occur regularly so you can routinely perform managementoperations.

Background InformationThe product uses Scheduler to schedule jobs. Scheduler is a service that enablesyou to run jobs unattended. You can schedule a job to run one time or multipletimes. Scheduler notifies you by the manner you select when a job is complete. Toschedule a job, the job must exist in the task library. You create a job by followingthe procedure described in “Creating a job” on page 62.

Required Authorization Rolesmssqlserver_dba



When You FinishNone


Command line: Use the wschedjob command to schedule a job in the TaskLibrary from the command line. You can only schedule jobs that already exist inthe task library from the command line. For more information, see the TivoliManagement Framework Reference Manual.

Desktop:

1. Open the product task library window by doing the following:a. Open the Tivoli desktop.b. Double-click the product policy region icon to display the policy region.c. Double-click the product task library icon to display the task library

window.2. Drag the job icon that you want to schedule onto the Scheduler icon located

on the Tivoli desktop.3. Optional: Do the following if a task argument window displays:

a. Type the appropriate information for each field in the window.Additional Information: Refer to the task description in the product referenceguide or click Task Description to display the online help for this task.

b. Click Set & Execute to set the task arguments and open the AddScheduled Job window.

4. Type a label for the job icon in the Job Label text box of the Add ScheduledJob window.Additional Information: The label identifies the icon on the desktop. The joblabel can include alphanumeric character, underscores (_), dashes (–), periods(.), and blanks. If you do not specify a label, the job name is used.

5. Do one of the following:v Select the Disable the Job check box to stop a scheduled job from running.

—OR—v Clear the Disable the Job check box to continue running a scheduled job.

Additional Information: For more information on job disabling, see the TivoliEnvironment Framework User’s Guide.

6. Optional: Type a job description to uniquely identify the job in the Descriptionfield.

7. Set the date and time to begin scheduling in the Schedule Job For group box:a. Type a date in the Month, Day, and Year text boxes.b. Enter the time using the Hour and Minute drop-down lists and the AM

and PM radio buttons.8. Optional: Repeat the job by doing the following in the Repeat the Job group

box:a. Do one of the following:

v Select the Repeat the job indefinitely check box to repeat the jobindefinitely.–OR–


v Repeat the job a finite number of times by doing the following:1) Select the Repeat the job check box.2) Type the number of times you want the job to run.

b. Set the interval between start times for the job in the The job should startevery field.

9. Click any of the following check boxes in the When Job Completes group boxto send job completion notification:v Send a notice to a specific group by doing the following:

a. Click the Post Tivoli Notice check box.b. Click Available Groups to display the Available Groups window.c. Select a group from the list of notice groups.d. Click Set to set your group and return to the Add Scheduled Job

window.

Additional Information: You can read notices from the Tivoli desktop byclicking on the Notices icon.

v Send a notice to your desktop by doing the following:a. Click the Post Status Dialog on Desktop check box.b. Type the message you want displayed in the text box next to the check

box.v Send an e-mail to a specified user by doing the following:

a. Click the Send e-mail to check box.b. Type the complete e-mail address in the text box next to the check box.

v Log the job completion status to a file by doing the following:a. Click the Log to File check box.b. Enter the file destination by doing one of the following:

– Type the file destination in the Host and File text boxes.–OR–

– Browse for the file destination by doing the following:1) Click File Browser to display the File Browser window.2) Double-click on a host name to display the directories and files

for that host.3) Select a directory and file from the Directories and Files lists.4) Click Set File & Close to return to the Add Scheduled Job

window.10. Optional: Set retry, cancel, or restriction options by doing the following:

a. Click Set Retry/Cancel/Restriction Options to display the SetRetry/Cancel Restrictions Options window.

b. Choose one of the following cancel job options:v Clear the Cancel job check box to have the Scheduler continue trying

the job indefinitely.—OR—

v Set the Scheduler to cancel a job in a specified time frame by doing thefollowing:1) Select the Cancel job check box.2) Type the time frame for the Scheduler to wait before canceling a job

that has not started.


c. Click one of the following retry options:v Click Retry the job until success to retry the job until it runs

successfully.—OR—

v Specify the number of times a job attempts to run by doing thefollowing:1) Click the Retry the job check box.2) Type the number of attempts to start the job in the text box.3) Type the amount of time the Scheduler waits before retrying in the

The job should retry every field.d. Click any of the following check boxes in the Restrictions group box to

specify the job run times:

During the daySet the beginning and ending hour of day for the job to run.

At nightSet the beginning and ending hour of night for the job to run.

During the weekSet the beginning and ending day of the week for the job to run.

On weekendsSet the beginning and ending day of the weekend for the job torun.

e. Click Set to set the options and return to the Add Scheduled Job window.11. Click Schedule Job & Close to schedule the job and return to the Tivoli

desktop.


Chapter 7. Viewing resource model results with the IBM TivoliMonitoring Web Health Console

This chapter provides an overview of the IBM Tivoli Monitoring Web HealthConsole. For complete information on installing and working with the IBM TivoliMonitoring Web Health Console see the latest version of the IBM Tivoli MonitoringUser’s Guide. The IBM Tivoli Monitoring Web Health Console runs on Netscape 6.xand Internet Explorer 6.x.

You can use the IBM Tivoli Monitoring Web Health Console for the followingpurposes:v Checking, displaying, and analyzing the status and health of endpoints that

have distributed resource monitorsv Displaying an endpoint’s real-time and historical data logged to the IBM Tivoli

Monitoring databasev Viewing online and historical data on endpoints as a follow-up to specific

problemsv Starting and stopping the IBM Tivoli Monitoring engine and individual resource

models on selected endpointv Removing a profile from the selected endpoint

You can use the IBM Tivoli Monitoring Web Health Console to check, display, andanalyze the status and health of any endpoint with profiles and resource models.Status reflects the state of the endpoint displayed on the IBM Tivoli MonitoringWeb Health Console, such as running or stopped. Health is a numeric valuedetermined by resource model settings. You can also use the IBM TivoliMonitoring Web Health Console to work with real-time or historical data from anendpoint that is logged to the IBM Tivoli Monitoring database.

You can use the diagnostic and monitoring capabilities of the IBM TivoliMonitoring Web Health Console to perform targeted analysis of problemsassociated with individual endpoints when an event is sent to the Tivoli EnterpriseConsole. Use the online and historical data to follow up specific problems withsingle endpoints.

Understanding resource healthThe IBM Tivoli Monitoring Web Health Console obtains events and indicationsfrom endpoints. The IBM Tivoli Monitoring Web Health Console displays thehealth of each potential problem as a numeric value between 100 (perfect health)and zero (with zero meaning that the conditions for the corresponding event aremet). Intermediate values show the percentage of health considering the totalnumber of occurrences that have occurred.

Table 12. Health Determination Example

Cycle 1 2 3 4 5

CPU% 55 73 54 63 68

Occurrences or Holes H O H O O

Occurrence Count 0 1 1 2 3

71

Table 12. Health Determination Example (continued)

Health % 100 75 75 50 25

Table 12 on page 71 displays the health percentage changes in steps of 25% because4 occurrences were required to trigger an event; if the indication required 5occurrences, the health percentage would have changed by steps of 20%. Resourcehealth is determined at the indication level and passed up to the endpoint. Thelowest health of any indication in a resource model is shown as the health of thatresource model and the lowest health of any resource model running on anendpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is running on an endpoint has a health of zero, the healthof the endpoint is shown as zero. The required occurrences, cycle times, thresholds,and parameters for indications are defined when the resource model is created inthe IBM Tivoli Monitoring Workbench. You can, however, alter these resourcemodel components at any time.

For more information about the resource health, see the IBM Tivoli MonitoringUser’s Guide documentation.

Connecting the IBM Tivoli Monitoring Web Health ConsoleYou can connect the IBM Tivoli Monitoring Web Health Console to any Tivolimanagement region server or managed node and configure it to monitor any or allof the endpoints that are found in that region. The IBM Tivoli Monitoring WebHealth Console does not have to be within the region itself, although it could be.To connect to the IBM Tivoli Monitoring Web Health Console you need access tothe server on which the IBM Tivoli Monitoring Web Health Console server isinstalled and the IBM Tivoli Managed Region on which you want to monitorhealth. All user management and security is handled through the IBM Tivolimanagement environment. This includes creating users and passwords as well asassigning authority.


Chapter 8. Customizing resource models

This chapter provides an overview of IBM Tivoli Monitoring procedures you needto follow to customize resource models.

Overview of IBM Tivoli MonitoringIBM® Tivoli® Monitoring 5.1.1 allows you deploy preconfigured best practicesresource models as well as standard and customized resource models to automatethe monitoring of essential resources. In this context, a resource is anything thataffects the operation of a computer system and includes physical and logical disks,CPUs, memory, printers, as well as the processes running, and the services, such asLanMan, the Windows event log, the UNIX® syslogd (logging system daemon) andTCP/IP. This allows you to detect bottlenecks and other potential problems anddefine automatic recovery from critical situations. This ability frees systemadministrators from manually scanning extensive performance data. Themonitoring software integrates with other Tivoli Availability solutions, includingTivoli Business Systems Manager® and Tivoli Enterprise Console®.

A resource model captures and returns information, such as database status orserver availability, about a resource or software application in the Tivolimanagement environment. To use a resource model, you must define anddistribute it to an endpoint.

Tivoli provides tools for organizing system resources on the Tivoli desktop. Aprofile manager is the top level of organization. Servers are subscribed to profilemanagers. These subscriptions provide the channel through which resource modelsare distributed to servers. A profile manager also can contain profiles, which arecontainers for application-specific information about a particular type of resource.Each profile contains one or more resource models. You can subscribe resources toa predefined profile manager. You can distribute individual profiles within theprofile manager to subscribers of the profile manager. You can group profilemanagers in a way that meets your needs. Profile managers can reflect functionalgrouping of resources, functional grouping of resource models, or any grouping atall. Likewise, a profile can contain any combination of resource models.

You must segregate profiles according to resources: Web servers need Web serverresource models, and database servers need database server resource models. Youcan define each resource model to include information such as how often to checkthe server resource status and what to do when certain conditions are met. Someresource models provide predefined settings and response actions, which you canadjust. Other resource models require you to define all the settings. See the IBMTivoli Monitoring for Databases: Microsoft SQL Server Reference Guide for a descriptionof individual settings.

Before running a resource model, you must subscribe the MicrosoftSQLServerresource to the profile manager that contains the profile in which the resourcemodel is defined. You can distribute the profile to the resource. By default,resource models are set up to become active when you distribute them tosubscribers. You can activate and deactivate resource models at any time.

73

Customizing indications

ObjectiveTo customize indication rules so that resources are monitored and events generatedin the most appropriate manner for your environment.

Background informationEach resource model triggers an indication if certain conditions defined by theresource model’s thresholds are not satisfied during the monitoring cycle. Eachresource model has predefined thresholds that meet the business needs of mostcustomers; however, you may have specific requirements for which thesethresholds are not appropriate; therefore, you can adjust these values as needed.

An event is used to verify the persistence of a given indication by eliminatingunrepresentative peaks and troughs for the indication. For example, a process thatgenerates the Process High CPU indication in one cycle is behaving perfectlynormally, and is of no threat to other processes if the high usage does not repeat.However, an indication that persists over several cycles is a problem. Thus, anevent defines the number of consecutive occurrences of the indication that aresignificant.

An occurrence refers to a cycle during which a specific indication occurs for a givenresource model.

A hole refers to a cycle during which a specific indication does not occur for agiven resource model. In other words, the conditions specified for the generation ofthe indication are not met. This does not mean that none of the thresholds areexceeded.





profiles” on page 33 and “Adding custom resource models to profiles” onpage 76 for information.


When you finishDistribute the profile to which the resource model belongs. See “Distributingprofiles from the desktop” on page 34.

Optional: Continue customizing the resource model:v Specify if you want a recovery action when a specific event occurs. See “Editing

a built-in action” on page 79v Specify if you want corrective or reporting tasks for an event. See “Specifying

tasks for an event” on page 81v Specify if you want to receive information on a specific event through a notice.

See “Sending a notice to administrators when an event occurs” on page 83


v Specify if you want to customize your parameters to tailor the monitoringprocess. See “Customizing parameters” on page 84

v Specify if you want the monitoring of resource models to take place on specifictime periods of selected days. See “Creating scheduling rules” on page 85

v Determine when the monitoring of resource models takes place. See“Customizing the scheduling monitoring period” on page 87

v Specify if you want the log data collected by a resource model written to a localdatabase. See “Customizing data logging information” on page 89


Command line: Use the wdmeditprf command to customize a resource model fora profile.

Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize from the IBM Tivoli

Monitoring Profile window.3. Click Edit to display the Edit Resource Model window.4. Click Indications to display the Indications and Actions window.5. Select the indication of which you want to customize the values of the event

associated with that indication.6. Apply the changes to the values that are appropriate to your requirements.

Additional Information: See the IBM Tivoli Monitoring for Databases: Microsoft SQLServer Reference Guide for the default resource model settings. The followingdescribes the values that you can customize:

Number of OccurrencesSpecifies the number of consecutive times the indication occurs so thatthe software generates an event. You can change this value to specifythe number of times an indication occurs to trigger an event.

Number of HolesDetermines how many cycles that do not produce an indication canoccur between cycles that do produce an indication. This determines ifthe occurrences of an indication are consecutive. Each cycle without anindication is termed a hole. For example, an event that has a value oftwo holes means that when up to two cycles without an indicationoccur between any two cycles with an indication, the cycles with anindication are considered consecutive.

Use the value for the Number of Holes in conjunction with theNumber of Occurrences parameter and the Cycle Time to define atime window for the generation of an event. If, for example, you defineCycle Time as 10 seconds, Number of Occurrences as 5, and Numberof Holes as 2, the time that must elapse before an event occurs isbetween 50 and 130 seconds. The minimum elapsed time is the number

Chapter 8. Customizing resource models 75

of occurrences multiplied by the cycle time. The maximum timewindow assumes that the maximum number of holes occur betweeneach pair of occurrences, and is determined by the following equation:TW = CT x ((Oc - 1) + (H x (Oc - 1))

where:

TW Specifies the time window calculated

CT Specifies the cycle time

Oc Specifies the number of occurrences

H Specifies the number of holes

Send TEC EventsSelect this check box to send an event to the Tivoli Enterprise Console.You must have Tivoli Enterprise Console installed and configured.

Send to TBSMSelect this check box to send an event to Tivoli Business SystemsManager’s Common Listener. You must have Tivoli Business SystemsManager installed and configured.

7. Click Apply Changes & Close to save your changes to the indication.

Adding custom resource models to profiles

ObjectiveTo specify the platform, cycle time, and threshold values that customize a resourcemodel to meet the needs of your environment and add the resource model to aprofile.

Background informationA resource model captures and returns information about a resource or application.You set up resource models and distributed them to endpoints. A number ofpredefined resource models are installed with the product. To customize basicsettings of a resource model, specify the platform type, cycle time, and thresholdvalues appropriate for your environment. Choose the resource models to add to aprofile based on the resources you want to monitor. Adding one or more of theseresource models to a profile enables you to begin monitoring resourcesimmediately.




managers” on page 32 for information.v See the IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide

for detailed information about each resource model.

When you finishDistribute the profile. See “Distributing profiles from the desktop” on page 34.



Command line: Use the wdmeditprf command to add a customized resourcemodel to a profile.

For more information about this command, see the IBM Tivoli Monitoring User’sGuide.

Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to open the policy region.c. Double-click the profile manager icon to open the Profile Manager window.d. Double-click the profile icon to which you want to add a customized

resource model.2. Click Add to open the Add Resource Models to Profile window.3. Select the resource model category from the Category drop-down list.4. Select the desired resource model from the Resource Model drop-down list.5. Set the frequency with which the resource model monitors the data in the

Cycle Time text box. Enter a time in seconds.6. Use the following steps to change any of the threshold values:

a. Select the Threshold Name that you want to change.Additional Information: The description box displays a description of thethreshold that you selected. A window above the description displays thecurrently assigned threshold value. For the default threshold values see theIBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide.

b. Change the currently assigned threshold value to a value appropriate toyour requirements.

c. Click Apply to set and display the new value in the Threshold Valuewindow.

7. Optional: Click Indications or Parameters to make required modifications toindications and parameters, click Schedule to add schedule information, andclick Logging to add logging information.Additional information: If you do not perform this step, the indications andparameters use the default values shipped with the resource models. See“Customizing indications” on page 74, “Customizing parameters” on page 84,and “Customizing the scheduling monitoring period” on page 87 forinformation.

8. Click Add & Close to save your changes.Additional information: The IBM Tivoli Monitoring Profile window now showsthe customized resource model.

Adding or removing built-in actions

ObjectiveTo add a built-in action so administrators and users can reinstate an event’srecovery actions or to remove a built-in action so administrators and users canclear an event’s recovery actions.

Background informationA built-in action is a recovery action for an event. The actions take positive steps toremedy the situation, or ensures distribution of information about the event to theappropriate authorities or entities.


The Tivoli software has predefined actions for certain events. An action is eitherthe execution of a common information model class method, or the execution of aprogram. For example, an event that detects the failure of a service has the restartof that service as its built-in action. IBM Tivoli Monitoring detects the failure of aservice and automatically restarts it. Built-in actions are defined by default as partof an event when the resource model is created in the IBM Tivoli MonitoringWorkbench. See the IBM Tivoli Monitoring documentation for more information.


Before you beginv You must have previously removed a built-in action to activate the Built-In

button for adding a built-in action. Use this procedure to reinstate the previouslyremoved built-in action.

v Create a profile manager and profile. See “Creating profile managers andprofiles” on page 30 for information.

v Add subscribers to a profile manager. See “Subscribing resources to profilemanagers” on page 32 for information.

v Add a resource model to a profile. See “Adding default resource models toprofiles” on page 33 and “Adding custom resource models to profiles” onpage 76 for information.



Optional: Continue customizing the resource model:v Specify if you want a recovery action when a specific event occurs. See “Editing



See “Sending a notice to administrators when an event occurs” on page 83v Specify if you want to customize your parameters to tailor the monitoring

process. See “Customizing parameters” on page 84v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules” on page 85v Determine when the monitoring of resource models takes place. See

“Customizing the scheduling monitoring period” on page 87v Specify if you want the log data collected by a resource model written to a local

database. See “Customizing data logging information” on page 89



Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:


a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select a resource model from the IBM Tivoli Monitoring Profile window.3. Click Edit to open the Edit Resource Model window.4. Click Indications. The Indications and Actions window opens and displays the

indications appropriate to the selected resource model.5. Select the indication that has the associated events you want to add or remove.6. Select the action from the Action List panel of the Indications and Actions

window.7. Click Remove to remove the action from the list.

— OR —Click Built-in to open the Add Action window.a. Select the action you want to run when an event occurs.b. Enter the number of times you want the action to perform when an

indication generates an event in the Retry field.Additional information: If you set the Retry field to zero, the productcontinually tries to perform the action until the action is successful.

c. Click one of the following buttons:

Add Adds the selected action with the values specified and keeps theAdd Action window open.

Add & CloseAdds the selected action and closes the Add Action window.

8. Click one of the following buttons:

Apply ChangesSaves the changes made to the built-in actions and leaves theIndications and Actions window open.

Apply Changes and CloseCloses the Indications and Actions window and saves the changesmade to the built-in actions.

Editing a built-in action

ObjectiveSpecifies the number of times the software attempts to execute the built-in actionwhen an event is generated.

Background informationA built-in action is a recovery action for an event. The actions take positive steps toremedy the situation, or ensures distribution of information about the event to theappropriate authorities or entities.

The Tivoli software has predefined actions for certain events. An action is eitherthe execution of a common information model class method, or the execution of aprogram. For example, an event that detects the failure of a service has the restartof that service as its built-in action. IBM Tivoli Monitoring detects the failure of aservice and automatically restarts it. Built-in actions are defined by default as partof an event when the resource model is created in the IBM Tivoli Monitoring


Workbench. See the IBM Tivoli Monitoring documentation for more information.You can remove built-in actions from a resource model using the Tivoli desktop.See “Adding or removing built-in actions” on page 77.








Optional: Continue customizing the resource model:v Specify if you want to customize your thresholds and events to tailor the

monitoring process. See “Customizing indications” on page 74v Specify if you want corrective or reporting tasks for an event. See “Specifying









Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon to which you want to customize a resource

model.


2. Select the resource model that you want to customize from the IBM TivoliMonitoring Profile window.

3. Click Edit to display the Edit Resource Model window.4. Click Indications to display the Indications and Actions window and the

indications appropriate to the selected resource model.5. Select the indication that has the associated events you want to customize.6. Select the action to edit from the Action List panel of the Indications and

Actions window.7. Click Edit to open the Edit Current Action window.8. Enter the number of times you want the action to perform when an indication

generates an event in the Retry field.Additional information: If you set the Retry field to zero, the productcontinually tries to perform the action until the action is successful.

9. Click Apply next to the Retry field to apply the changes.10. Click one of the following buttons:

Close Closes the Edit Current Action window and saves the original retryvalue.

Modify & CloseCloses the Edit Current Action window and saves the modified retryvalue.

Specifying tasks for an event

ObjectiveTo specify a task so administrators and users can determine corrective or reportingtasks for an event.

Background informationYou can select one or more tasks to perform when an indication generates anevent. You can select one or more tasks for each event. These tasks can access theIBM Tivoli Monitoring event name and thresholds by accessing the environmentvariables.








Optional: Continue customizing the resource model:


v Specify if you want to customize your thresholds and events to tailor themonitoring process. See “Customizing indications” on page 74

v Specify if you want a recovery action when a specific event occurs. See “Editinga built-in action” on page 79

v Specify if you want to receive information on a specific event through a notice.See “Sending a notice to administrators when an event occurs” on page 83



v Determine when the monitoring of resource models takes place. See“Customizing the scheduling monitoring period” on page 87




Desktop:


model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model window.4. Click Indications to display the Indications and Actions window and the

indications appropriate to the selected resource model.5. Select the indication that you want to generate a task from the Indications and

Actions window.6. Click Tasks in the Action List window to display the Tasks window.7. Double-click the appropriate task library from the scroll list of the Libraries

panel.Additional Information: The tasks contained in the library display in the Taskspanel.

8. Double-click the appropriate task in the Tasks panel.9. Specify the appropriate parameters in the Configure Task window.

Additional Information: Run the wlsnotif -g command to see the availableNotice Groups.

10. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.


Sending a notice to administrators when an event occurs

ObjectiveTo send a notice in response to an event so administrators can take the appropriateactions or responses.

Background informationYou can select the IBM Tivoli Monitoring Utility task to send notices in response toan event.









monitoring process. See “Customizing indications” on page 74v Specify if you want a recovery action when a specific event occurs. See “Editing


tasks for an event” on page 81v Specify if you want to customize your parameters to tailor the monitoring







Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.


b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model window.4. Click Indications to display the Indications and Actions window and the

indications appropriate to the selected resource model.5. Select the indication that you want to generate a task from the Indications and

Actions window.6. Click Tasks in the Action List window to display the Tasks window.7. Double-click the IBM Tivoli Monitoring Utility Tasks library in the scroll list

of the Libraries panel.Additional Information: The tasks contained in the IBM Tivoli MonitoringUtility Tasks library are displayed in the Tasks panel.

8. Double-click dm_mn_send_notice in the Tasks panel to display the ConfigureTask window.

9. Specify the appropriate parameters in the Configure Task window.Additional Information: Run the wlsnotif -g command to see the availableNotice Groups.

10. Click Change & Close to add the task to the Action List panel in theIndications and Actions window.

Customizing parameters

ObjectiveTo customize the parameters of a resource model so administrators and users cantailor the monitoring process.

Background informationSome resource models have one or more parameters. Each parameter can take theform of a list of strings, a list of numeric values, a Boolean list of predeterminedvalues from which you can make any combination of selections, or a choice list ofmutually exclusive alternatives.













See “Sending a notice to administrators when an event occurs” on page 83v Specify if you want the monitoring of resource models to take place on specific

time periods of selected days. See “Creating scheduling rules”v Determine when the monitoring of resource models takes place. See





Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon to which you want to customize a resource

model.2. Select the resource model that you want to customize from the IBM Tivoli

Monitoring Profile window.3. Click Edit to display the Edit Resource Model window.4. Click Parameters.5. Select the type of parameter from the Name drop-down list in the Parameters

window.6. Add or delete the parameter values as required by checking or unchecking the

boxes.7. Click Apply Changes and Close to save your changes.

Creating scheduling rules

ObjectiveTo create schedule rules so administrators and users can determine the timeperiods on selected days when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to determinea period when monitoring takes place and specific scheduling rules. You candivide the overall collection period into active and inactive intervals by applyingone or more schedule rules.


The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules whichallows you set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If the profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, allowing you to set up asingle rule that will monitor the same local time period in different time zones. Alltimes of events or activities reported from endpoints or gateways are also loggedin the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesManages time intervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.











tasks for an event” on page 81




v Determine when the monitoring of resource models takes place. See“Customizing the scheduling monitoring period”




Desktop:


model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model window.4. Click Schedule to open the Scheduling window.5. Clear the Always check box in the Schedule panel.6. Click the New Rule button in the Schedule Rules panel.7. Type a name for the rule in the Rule Name text box of the Rule Editor panel.8. Select one or more items in the weekday list to specify the day or days on

which you want the collections active during the collection period.Additional information: Use the Shift or Ctrl key as necessary to select morethan one day from the list.

9. Set the Start Time and Stop Time for the collection activity or select the AllDay check box.Additional information: Times are always interpreted as local time where theendpoint engine runs. Setting a time interval of 08:00 to 13:00 ensures thatmonitoring takes place between those times in all time zones to which youdistribute the profile.

10. Click Set Rule. Your new rule appears in the Schedule Rules list.Additional information: To display the details of any rule, select the rule in theSchedule Rules list. Its settings are displayed in the Rule Editor group box.

11. Click Modify & Close to save your rule and close the Scheduling window.

Customizing the scheduling monitoring period

ObjectiveTo customize the scheduling monitoring period of a resource model soadministrators and users can determine when monitoring takes place.


Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to determinea period when monitoring takes place and specific scheduling rules.

The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules whichenables you set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor. If a profile contains more than oneschedule rule, all the time intervals are respected, and rules are combined byadding together the time periods they define. For example, if you specify a rulethat requests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules gives all-daymonitoring only on Fridays, and monitoring between 8:00 and 14:00 on all otherdays. If the second rule instead requested monitoring from 12:00 to 18:00 onFridays, the sum of the rules would give monitoring between 8:00 and 18:00 onFridays and between 08:00 and 14:00 on all other days.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that resource models the same local time period in different time zones.All times of events or activities reported from endpoints or gateways are alsologged in the local time of the system from where they originated.

The Scheduling window has the following group boxes:

ScheduleSets the data collection period. By default, all resource models are set toalways collect data.

Schedule RulesManages time intervals during which the resource model is active.

Rule EditorCreates and edits schedule rules.






v Create the schedule rules. See “Creating scheduling rules” on page 85 for moredetails.




monitoring process. See “Customizing indications” on page 74


v Specify if you want a recovery action when a specific event occurs. See “Editinga built-in action” on page 79

v Specify if you want corrective or reporting tasks for an event. See “Specifyingtasks for an event” on page 81




v Specify if you want the log data collected by a resource model written to a localdatabase. See “Customizing data logging information”



Desktop:


model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model window.4. Click the Schedule to open the Scheduling window.5. Clear the Always check box in the Schedule panel.6. Set a Start Date and Stop Date to define the monitoring period.7. Optional: Add one or more schedule rules that determine time periods on the

selected dates that monitoring takes place.8. Click Modify & Close to save your changes.

Customizing data logging information

ObjectiveTo customize data logging information so administrators and users can log datacollected by a resource model and write it in a local database.

Background informationYou can view the log data through the IBM Tivoli Monitoring Web Health Consoleafter you write it in a local database. You can store one of the following types ofdata in the database:

Raw dataData written exactly as the resource model collects it. All the monitoredvalues are collected and copied in the database.

Aggregated dataData collected and aggregated at fixed intervals that you define


(Aggregation Period). Only the aggregated values are written in thedatabase. The aggregated data is calculated on the basis of one or more ofthe following options:v Maximumv Minimumv Average















“Customizing the scheduling monitoring period” on page 87



Desktop:

1. Open the IBM Tivoli Monitoring Profile window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.


d. Double-click the profile icon in which you want to customize a resourcemodel.

2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model window.4. Click Logging to open the Logging window.5. Select the Enable Data Logging check box in the Data Logging Settings panel.

This enables logging of all raw data collected by the resource model to adatabase.

NoteResource models do not log data by default. You must select the EnableData Logging check box to log data. If you do not select this check box,resource model data will be lost.

6. Perform the following steps to specify the aggregation rule applied to the databefore it is written to the database:a. Set Hours and Minutes of the Aggregation Period to the required values.b. Select one or more of the following functions to perform on the numerical

data collected during the aggregation period before it is written to thedatabase:

MaximumCalculates and logs the peak value in each aggregation period.

MinimumCalculates and logs the lowest value in each aggregation period.

AverageCalculates and logs the average of all values in each aggregationperiod.

7. If you want to log the raw data instead of aggregate data, do the following:a. Clear the Aggregate Data check box.b. Select Raw Data.c. Optional: If Tivoli Enterprise Data Warehouse is installed, you can check the

TEDW Data option to store the raw data for use in Tivoli Enterprise DataWarehouse.

8. Set Hours and Minutes of the Historical Period to the required values.9. Click Apply Changes and Close to save your changes and close the Logging

window.

Managing profiles and resource models at endpoints

ObjectiveTo manage profiles and resource models after they are distributed to endpoints soadministrators and users can maintain monitoring processes on those endpoints.

Background informationNone.







v Distribute the profile. See “Distributing profiles from the desktop” on page 34 forinformation.


When you finishNone

ProcedureYou can perform this procedure from the Tivoli command line only.

Command line: Use the wdmcmd command to stop or restart IBM TivoliMonitoring on one or more endpoints from a gateway or server.

Use the wdmdistrib command to distribute a profile to one or more subscribers.

Use the wdmeng command to stop or start profiles or resource models atendpoints or to delete profiles at endpoints.

Use the wdmlseng command to return a list and the status of all resource modelsthat have been distributed on a specified endpoint.

Use the wdmtrceng command to set the trace parameters of the IBM TivoliMonitoring engine at the endpoint.

See the IBM Tivoli Monitoring documentation for more information about thewdm commands.

Managing IBM Tivoli Monitoring gateways

ObjectiveTo manage IBM Tivoli Monitoring on gateways so administrators and users canrun monitoring processes on those gateways.

Background informationNone




managers” on page 32 for information.


v Add a resource model to a profile. See “Adding default resource models toprofiles” on page 33 and “Adding custom resource models to profiles” onpage 76 for information.



When you finishNone


Command line: Use the wdmmn command to stop or start selected IBM TivoliMonitoring processes on one or all gateways.

Determining which resource models have been distributed toendpoints

ObjectiveTo determine which resource models have been distributed to an endpoint.

Background informationThis procedure refers only to database profile managers.

Open an endpoint window from the desktop to see if a resource model has beendistributed to it.

Note: To distribute IBM Tivoli Monitoring for Databases: Microsoft SQL Serverresource models, you must have the mssqlserver_dba authorization role.








When you finishNone


Desktop:


1. Open the Profile Manager window by doing the following:a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manger icon to display the Profile Manager

window.2. Double-click the endpoint icon from the Subscribers area to open the endpoint

window.3. Double-click the monitoring profile icon to display the IBM Tivoli Monitoring

Profile window, which lists the resource models distributed to the endpoint.

Determining which resource models are running on endpoints

ObjectiveTo determine which resource models are running on an endpoint.

Background information

Note: Resource models might show false running states even though they havenot been executed. When resource models are first distributed to a profileendpoint, the resource models all show running, even though they have notbeen executed. The resource models show valid states after they areexecuted by the IBM Tivoli Monitoring engine.

Use the Tivoli command line to determine which resource models are running onan endpoint.







v See the IBM Tivoli Monitoring for Databases, Version 5.1.1: Microsoft SQL Server fordetailed information about each resource model.

When you finishNone


Command line: Use the wdmlseng command to determine which resourcemodels are running on an endpoint. For example, to view the list of resourcemodels on an endpoint, enter the following command:wdmlseng -e <endpoint>

Refer to the IBM Tivoli Monitoring User’s Guide for more information.


Chapter 9. Enabling IBM Tivoli Monitoring for Databases:Microsoft SQL Server for Tivoli Enterprise Data Warehouse

This chapter provides information on enabling IBM Tivoli Monitoring forDatabases: Microsoft SQL Server for Tivoli Enterprise Data Warehouse.

OverviewTivoli Enterprise Data Warehouse enables you to access application reports fromvarious Tivoli and customer applications. The infrastructure provides a set ofextract, transform and load (ETL) utilities that you use to extract and move datafrom Tivoli application data stores to a central data warehouse database.

Tivoli Enterprise Data Warehouse provides the following capabilities:v An open architecture for storing, aggregating, and correlating historical data. In

addition to the data collected by IBM Tivoli software, Tivoli Enterprise DataWarehouse has the flexibility and extensibility to enable you to integrate yourown application data.

v Database optimizations for the efficient storage of large amounts of historicaldata and for fast access to data for analysis and report generation.

v The infrastructure and tools necessary for maintaining and viewing the collecteddata. These include the Tivoli Enterprise Data Warehouse application, IBM DB2Universal Database™ Enterprise Edition, the Data Warehouse Center, DB2Warehouse Manager, and a user interface for creating and viewing reports.

v The ability to use your choice of data analysis tools to examine your historicaldata. In addition to the report interface, you can analyze your data using otherproducts such as online analytical processing (OLAP), planning, trending,analysis, accounting, and data mining tools.

v The ability to control access to your historical data. You can keep data aboutmultiple customers and data centers in one central data warehouse, but restrictaccess so that customers can see and work with data and reports based only ontheir data and not any other customer’s data. You can also restrict an individualuser’s ability to access data.

v A zero-footprint client. Users can access Tivoli Enterprise Data Warehousereports from any system by using a Web browser. No special software isrequired on the user’s system.

v Internationalization support. Not only is the report interface localized,application programmers can localize the data stored in the central datawarehouse.

Tivoli Enterprise Data Warehouse consists of the following components:v Control serverv Central data warehousev Data martsv Report interface

Control serverThe control server contains the control database for Tivoli Enterprise DataWarehouse from which you manage your data warehouse.

95

The control server has these subcomponents:v A server that controls communication between the control server, the central

data warehouse server, the data mart server, and the report server.v The control database, which contains metadata for Tivoli Enterprise Data

Warehouse.

The control server uses the following parts of the IBM DB2 product, which youmust install manually before installing the control server. These parts are allautomatically installed when you install IBM DB2 Universal Database EnterpriseEdition on a Microsoft Windows system.v DB2 Serverv The Data Warehouse Center, a component that automates data warehouse

processing. You can use the Data Warehouse Center to define the ETL processesthat move and transform data into the central data warehouse and the starschemas used by the data marts. Then, you can use the Data Warehouse Centerto schedule, maintain, and monitor these processes.

v The warehouse agent, part of DB2 Warehouse Manager.

Central data warehouseThe central data warehouse is a DB2 database that contains the historical data foryour enterprise. The system that hosts the central data warehouse is called thecentral data warehouse server. The central data warehouse component uses IBM DB2Universal Database Enterprise Edition, which you must install manually beforeinstalling the control server.

Data martsA separate DB2 database contains the data marts for your enterprise. Each datamart contains a subset of the historical data from the central data warehouse tosatisfy the analysis and reporting needs of a specific department, team, customer,or application. The system that hosts this DB2 database is called the data martserver. Although you can have many data marts, you can have only one data martserver.

The data mart component requires IBM DB2 Universal Database EnterpriseEdition, which you must install manually before installing the control server.

The warehouse pack for IBM Tivoli Monitoring for Databases: Microsoft SQLServer creates data marts whose structure is suitable for the report interface. IBMTivoli Monitoring for Databases: Microsoft SQL Server does this by providing anextract, transform, and load (ETL) process, called a data mart ETL, that creates thedata mart and loads it with data from the central data warehouse.

You can modify an existing data mart, or create new data marts that containslightly different data, to address a reporting need specific to your situation. Tomodify or create a data mart, you must be familiar with database ETL processesand with the internal representation of a data mart as star schemas in the TivoliEnterprise Data Warehouse databases. For information about this, see Enabling anApplication for Tivoli Enterprise Data Warehouse.

Report interfaceThe Tivoli Enterprise Data Warehouse report interface (RPI) provides tools and agraphical user interface that other Tivoli software products use to create anddisplay reports. You can use Tivoli Enterprise Data Warehouse to customize reports


provided with other Tivoli software and to create new reports. You also use thereport interface to control access to data marts and to the reports associated with adata mart. The system on which you install the report interface is called the reportserver.

Use the Work with Reports task group in the report interface to manage users,groups, and data marts for Tivoli Enterprise Data Warehouse or to run, create, andview Tivoli Enterprise Data Warehouse reports.

Table 13. Goals and where to find procedures for enabling IBM Tivoli Monitoring forDatabases: Microsoft SQL Server for Tivoli Enterprise Data Warehouse

Goal Where to find procedures

Work with users and user groups “Accessing the IBM Console” on page 98

“Creating an IBM Console user” on page 98

“Assigning roles to a user” on page 99

“Creating a user group” on page 100

“Assigning users to a user group” on page100

“Assigning user groups to a data mart” onpage 101

Manage Tivoli Enterprise Data Warehousereports

“Running reports” on page 101

“Scheduling reports to run automatically”on page 102

“Modifying default settings for reports” onpage 102

“Creating reports” on page 103

Tivoli Enterprise Data Warehouse reportsTivoli Enterprise Data Warehouse reports display a static view of the data in a datamart. Reports are provided by the warehouse pack for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server, along with the data marts required to collect thedata used in the report.

For more information about working with reports, see the Tivoli Enterprise DataWarehouse online help.

Tivoli software products using the Tivoli Enterprise Data Warehouse can provideprepackaged reports that enable you to access specific information about yourbusiness environment. All of these reports are listed in the Manage Reports andReport Output task of the Work with Reports task group in the IBM Console. Thisincludes reports from all Tivoli software products that use the Tivoli EnterpriseData Warehouse report interface. Tivoli software products can also provide adifferent reporting interface.

A Tivoli Enterprise Data Warehouse report uses data from a single data mart.

If you have the appropriate role, you can also create additional reports or modifyexisting reports. Before you can create a new report or modify an existing report,

Chapter 9. Enabling IBM Tivoli Monitoring for Databases: Microsoft SQL Server for Tivoli Enterprise Data Warehouse 97

you must understand the structure of the underlying warehouse data and of theoperational data that is the source of that data. For information about the structureof data in the data mart and in the central data warehouse, see the IBM TivoliMonitoring for Databases: Microsoft SQL Server Warehouse Enablement PackImplementation Guide.

For information on the specific data mart, star schema, and report mapping of IBMTivoli Monitoring for Databases: Microsoft SQL Server, see the IBM TivoliMonitoring for Databases: Microsoft SQL Server Warehouse Enablement PackImplementation Guide located in the Docs directory of the IBM Tivoli Monitoring forDatabases: Microsoft SQL Server Installation CD.

Accessing the IBM Console

ObjectiveTo display the IBM Console so you can use Tivoli Enterprise Data Warehouse.

Background informationYou perform all Tivoli Enterprise Data Warehouse functions through the IBMConsole. Access the IBM Console using a web browser to connect to TivoliEnterprise Data Warehouse server.

Required authorization rolesuperadmin


When you finishNone

ProcedureTo access the IBM Console, complete the following steps:1. Start the web browser.2. Connect to the following URL:

http://<hostname of TEDW server>/IBMConsole3. Enter the default user, ‘superadmin’, and the default password, ‘password’. It is

recommended that you change the default password after you log in. Tochange the password, click Administer Users and Role and select ManageUsers.

Creating an IBM Console user

ObjectiveTo create an IBM Console user.

Background informationTivoli Enterprise Data Warehouse is displayed using the IBM Console, which isalso used by other Tivoli software products. A user is given access to tasks in theIBM Console based on the roles that are assigned to that user. One user can haveroles for diverse tasks including administering IBM Console users, managing TivoliEnterprise Data Warehouse user groups and data marts, running and viewing theoutput of Tivoli Enterprise Data Warehouse reports, and performing tasksassociated with other Tivoli software products.


Required authorization rolesuperadmin


When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.

ProcedureTo create an IBM Console user, complete the following steps from the IBMConsole:1. Select Administer Users and then Create a User.2. Open the Task Assistant and follow the instructions provided in the online help

to create a user.

Assigning roles to a user

ObjectiveTo assign roles to a user.

Background informationThe following Tivoli Enterprise Data Warehouse roles control access to tasks andactivities in the Work with Reports task group:v Warehouse Security Administrator

With this role, a user can create and manage groups and data marts. A user withthis role controls access to data marts by assigning users to groups and bygiving groups access to specific data marts. In effect, this role controls access tothe Tivoli Enterprise Data Warehouse data using user groups and data marts.

v Report roles control a user’s ability to create and modify reports for the datamarts user groups can access. Assign only one of the following roles to eachuser:– Advanced Report Author

With this role, a user can create, modify, run, and delete public and their ownpersonal reports, and save the output of these reports.

– Report AuthorWith this role, a user can run and save the output of public reports and createand modify personal reports. They can run public and personal reports, andcreate, modify, and delete personal reports.

– Report ReaderWith this role, a user can run public reports and view the saved output ofpublic reports.

Required authorization rolesuperuser


When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing users, such as updating or displaying the propertiesof a user and deleting a user.


ProcedureTo assign a role to a user, complete the following steps from the IBM Console:1. Select Administer Users and Roles and then Manage Users.2. From the table of users, click the context menu icon of a user and select

Properties.3. Follow the instructions in the Task Assistant about assigning roles to the user.

Creating a user group

ObjectiveTo create a user group.


Required authorization roleAdministration Authorizations


When you finishThe Tivoli Enterprise Data Warehouse online help guides you through additionaltasks for managing user groups, such as updating or displaying the properties of auser group, adding users to a user group, and deleting a user group.

ProcedureTo create a user group, complete the following steps from the IBM Console:1. Select Work with Reports and then Manage User Groups.2. In the Manage User Groups window, click the context menu of Root and select

Create.3. Follow the instructions in the Task Assistant about creating user groups.

Assigning users to a user group

ObjectiveTo assign users to user groups.

Background informationYou control access to data in Tivoli Enterprise Data Warehouse data marts byspecifying which user groups (collections of users) can run the reports that accessthe data in each data mart. Each user in a user group is given access to all reportsthat access the data in the data marts to which that user group has access.

By default, Tivoli Enterprise Data Warehouse provides the TWHAdmin user group,which contains a single user: superadmin. You can customize the TWHAdmin usergroup for the needs of your enterprise.

A user can be assigned to more than one user group.




When you finishThe Tivoli Enterprise Data Warehouse online help also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding or removing users from a user group, anddeleting a user group.

ProcedureTo assign one or more users to a user group, perform the following steps from theIBM Console:1. Select Work with Reports and then Manage User Groups.2. In the Manage User Groups window, click the context menu icon of a group

and select Properties.3. Follow the instructions in the Task Assistant about assigning users to user

groups.

Assigning user groups to a data mart

ObjectiveTo assign user groups to a data mart.

Background informationGrant access to only those user groups whose users need the data mart to performtasks.



When you finishThe Tivoli Enterprise Data Warehouse online help can guide you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, removing users from a user group, and removing datamart access from a user group.

ProcedureTo assign user groups to a data mart, complete the following steps from the IBMConsole:1. Select Work with Reports and then Manage Data Marts.2. In the Manage Data Marts window, in the Data Mart view, click the context

menu icon for the data mart that you want to change and click Properties.3. Select the User Groups tab.

Running reports

ObjectiveTo run a report using the report interface.


Required authorization roleAdvRepAuthRole, RepAuthRole, or RepReaderRole



When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as displaying the properties of a report anddeleting a report.

ProcedureTo run a report using the report interface, complete the following steps from theIBM Console:1. Select Work with Reports and then Manage Reports and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

the context menu icon of a report and select Run.

Scheduling reports to run automatically

ObjectiveTo automatically run reports.

Background informationUsing the Tivoli Enterprise Data Warehouse report interface, you can schedule areport to run automatically when the associated data mart is updated. This ensuresthat when you examine the output of the report, it displays the most recent data inthe warehouse.

Required authorization roleAdvRepAuthRole


When you finishThe Tivoli Enterprise Data Warehouse online help can also guide you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureTo schedule a report to run automatically when the associated data mart isupdated, complete the following steps from the IBM Console:1. Select Work with Reports and then Manage Reports and Report Output.2. In the Manage Reports and Report Output window, in the Reports view, click

Reports.3. Click the context menu icon of a report and select Properties.

Modifying default settings for reports

ObjectiveTo modify default settings for report creation.

Background informationWhen you create or modify a report, you select predetermined values for the timeframe of the report. The predetermined values of Peak Hours and Weekdaysspecified under Filtering in the Time page of report properties can be modified. Dothis by modifying the information in the control database on the control server.


The default value for Peak Hours is 9:00 am through 5:00 PM, or 0900 to 1700. Thisvalue can be modified to reflect different peak hours if necessary.

The default value for Weekdays is Monday through Friday. This value can also bemodified.

The RPI.TimeFilters table contains the following filters and default filter values:

Table 14. Default time filter names and values

TIME_FILTER_NAME TIME_FILTER_VALUES

Peak hours hour(meas_hour) in (9,10,11,12,13,14,15,16,17)

Weekdays dayofweek(meas_date) between 2 and 6

Required authorization roleAdvRepAuthRole


When you finishFor additional information on the properties of the RPI.TimeFilters table, see theIBM Tivoli Monitoring for Databases: Microsoft SQL Server Warehouse Enablement PackImplementation Guide.

ProcedureTo change the values displayed in the report interface, perform the following steps:1. Connect to the control database (TWH_MD).2. Use an SQL statement similar to the following to modify the values for Peak

Hours or Weekdays in the RPI.TimeFilters table. The following example sets theWeekdays filter to represent Sunday through Thursday:

Update RPI.TimeFilters set TIME_FILTER_VALUES =dayofweek(meas_date) between 1 and 5where TIME_FILTER_NAME =Weekdays

Upon completion, when a user selects a Weekdays filter for a report in the reportinterface, the data returned is for Sunday through Thursday.

Note: There is no error-checking for the values inserted into the tables for PeakHours and Weekdays. Therefore, ensure that the information you insert intothe tables is correct. You can save a report that contains incorrect values forthese parameters without receiving an error message. The message is notgenerated until the report is run.

Creating reports

ObjectiveTo create a report.

Background informationYou can receive a message that the name you specified is already in use, even ifyou do not have access to the report with that name.

Required authorization roleAdvRepAuthRole or RepAuthRole


Before you beginEnsure that you use descriptive and meaningful names for the reports you create.Report names are unique across all users of Tivoli Enterprise Data Warehouse.

When you finishThe Tivoli Enterprise Data Warehouse online help guides you through additionaltasks for reports, such as modifying or displaying the properties of a report anddeleting a report.

ProcedurePerform this procedure from the IBM Console:1. Select Work with Reports.2. Select Create a Report.

IBM Tivoli Monitoring for Databases: Microsoft SQL Server data martsand reports

This section describes the data marts, star schemas, and reports used for IBMTivoli Monitoring for Databases: Microsoft SQL Server.

IBM Tivoli Monitoring for Databases: Microsoft SQL Server provides the MicrosoftSQL Server data mart. This data mart uses the following star schemas:v MSSQL Daily Cpu Usage Star Schemav MSSQL Daily Data File Space Used Star Schemav MSSQL Daily Database Average Percent Used Star Schemav MSSQL Daily Error Message Star Schemav MSSQL Daily Jobs Activity Star Schemav MSSQL Daily Replication Activity Star Schemav MSSQL Daily Replication Delivery Latency Star Schemav MSSQL Daily Server Performance Star Schemav MSSQL Daily Service Availability Star Schemav MSSQL Hourly Cpu Usage Star Schemav MSSQL Hourly Data File Space Used Star Schemav MSSQL Hourly Database Average Percent Used Star Schemav MSSQL Hourly Error Message Star Schemav MSSQL Hourly Jobs Activity Star Schemav MSSQL Hourly Replication Activity Star Schemav MSSQL Hourly Replication Delivery Latency Star Schemav MSSQL Hourly Server Performance Star Schemav MSSQL Hourly Service Availability Star Schemav MSSQL Monthly Cpu Usage Star Schemav MSSQL Monthly Data File Space Used Star Schemav MSSQL Monthly Database Average Percent Used Star Schemav MSSQL Monthly Error Message Star Schemav MSSQL Monthly Jobs Activity Star Schemav MSSQL Monthly Replication Activity Star Schemav MSSQL Monthly Replication Delivery Latency Star Schemav MSSQL Monthly Server Performance Star Schemav MSSQL Monthly Service Availability Star Schema


v MSSQL Weekly Cpu Usage Star Schemav MSSQL Weekly Data File Space Used Star Schemav MSSQL Weekly Database Average Percent Used Star Schemav MSSQL Weekly Error Message Star Schemav MSSQL Weekly Jobs Activity Star Schemav MSSQL Weekly Replication Activity Star Schemav MSSQL Weekly Replication Delivery Latency Star Schemav MSSQL Weekly Server Performance Star Schemav MSSQL Weekly Service Availability Star Schema

This data mart provides the following prepackaged health check reports:

Daily Filegroup Space Usage Health CheckThis health check report provides details about the size of the variousdatabases (at the FileGroup level) on the server at a particular date andtime or per a specific range of dates and times. This report helps todetermine the change in the database sizes due to the higher volume of thedata flow.

Daily Database Space Used (Filegroup) SummaryThis summary report provides the maximum size of the various databasesfilegroups. This report helps to determine the change in the database sizesdue to the higher volume of the data flow.

Daily Server Availability Extreme CaseThis extreme case report provides the percentage of time that the MicrosoftSQL server is available.

Daily Replication Agent Latency Health CheckThis health check report provides the latency of delivery for replication.This report helps to determine whether the replication process was slowingdown.

Daily Server Cpu Usage Extreme CaseThis extreme case report provides the maximum CPU cycles used for agiven Microsoft SQL Server.

Daily Server Error Message Count SummaryThis summary provides the number of times a Microsoft SQL Server errormessage was logged within a time period.

Daily Database Usage Health CheckThis health check report provides maximum percent of space used by adatabase.


Appendix A. Authorization roles quick reference

Each IBM Tivoli Monitoring for Databases: Microsoft SQL Server procedure has arequired authorization role. The following table summarizes these activities androles and tells you where to find additional information in this manual:

Table 15. Authorization roles table

Activity Context Required Role For Additional Information

Change Tivoli administratorproperties

Administratorscollection

senior Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

Add or remove a managedresource type for a policy region

Policy region senior Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

Run Microsoft SQL Serverdiscovery

Policy region mssqlserver_dba Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

Register a database server Policy region mssqlserver_dba Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

Add an indicator collection Policy region admin Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

Configure the Tivoli EnterpriseConsole

Managed node (wherethe event server isinstalled)

senior andmssqlserver_dba(must have both roles)

Chapter 3, “Setting up IBM TivoliMonitoring for Databases:Microsoft SQL Server”, on page13

View events in the TivoliEnterprise Console

Event console mssqlserver_user Appendix B, “Setting up TivoliEnterprise Console”, on page 109

Opening the database serverendpoint

Database serverinstance

mssqlserver_user Chapter 5, “Working with IBMTivoli Monitoring for Databases:Microsoft SQL Server”, on page41

View database server properties Database serverinstance

mssqlserver_user Chapter 5, “Working with IBMTivoli Monitoring for Databases:Microsoft SQL Server”, on page41

Edit database server properties Database serverinstance

mssqlserver_dba Chapter 5, “Working with IBMTivoli Monitoring for Databases:Microsoft SQL Server”, on page41

Start a database server Database serverinstance


107

Table 15. Authorization roles table (continued)

Activity Context Required Role For Additional Information

Stop a database server Database serverinstance


Customize and save a copy of atask

Task library admin Chapter 6, “Working with tasksand jobs”, on page 57

Run a task Task library mssqlserver_dba Chapter 6, “Working with tasksand jobs”, on page 57

Create a job Task library admin Chapter 6, “Working with tasksand jobs”, on page 57

Schedule a job Task library mssqlserver_dba Chapter 6, “Working with tasksand jobs”, on page 57

Run a job Task library mssqlserver_dba Chapter 6, “Working with tasksand jobs”, on page 57

Add a profile manager andprofile

Profile manager admin Chapter 8, “Customizing resourcemodels”, on page 73

Add and edit a resource model IBM TivoliMonitoringprofile

admin Chapter 8, “Customizing resourcemodels”, on page 73

Add one or more subscribers Profile manager’spolicy region andsubscriber’s policyregion(s)

admin (profile) andmssqlserver_dba(database endpoint)

Chapter 8, “Customizing resourcemodels”, on page 73

Distribute a profile to the nextlevel

Profile admin Chapter 8, “Customizing resourcemodels”, on page 73

Distribute a profile to all levelsor distribute from a databaseendpoint

Profile and MicrosoftSQL Server endpoint

admin (profile) andmssqlserver_dba(database endpoint)

Chapter 8, “Customizing resourcemodels”, on page 73


Appendix B. Setting up Tivoli Enterprise Console

This appendix provides information about setting up the Tivoli Enterprise Consolefor use with IBM Tivoli Monitoring for Databases: Microsoft SQL Server. If you donot have Tivoli Enterprise Console installed or do not want to have IBM TivoliMonitoring for Databases: Microsoft SQL Server send events to Tivoli EnterpriseConsole, you do not need to use this information.

Table 16. Setting up the Tivoli Enterprise Console guidelines

Goal Refer to

1. Overview of Tivoli Enterprise Console “Overview of Tivoli EnterpriseConsole” on page 109

2. Configuring Tivoli Enterprise Console to workwith IBM Tivoli Monitoring for Databases:Microsoft SQL Server

“Configuring Tivoli Enterprise Consoleto work with IBM Tivoli Monitoringfor Databases: Microsoft SQL Server”on page 110

3. Viewing events in Tivoli Enterprise Console soyou can determine an appropriate response.

“Viewing events in Tivoli EnterpriseConsole” on page 114

Overview of Tivoli Enterprise ConsoleIn distributed computing environments, it is essential to address events andconditions that can lead to problems in a timely and efficient manner. TivoliEnterprise Console provides tools for the following functions:v Receiving events from various sourcesv Processing events using rulesv Grouping events and delegating the groups selectively to administratorsv Responding to events automaticallyv Viewing events at a console

The following list explains basic concepts of event management. For moreinformation about Tivoli Enterprise Console, refer to the Tivoli Enterprise ConsoleUser’s Guide. For a listing of event classes and events, see the Tivoli EnterpriseConsole classes appendix in the IBM Tivoli Monitoring for Databases: Microsoft SQLServer Reference Guide.

EventsAn event is a structured piece of information. It carries information aboutitself, including the event class, event identity, severity, location (hostwhere the event originated), and description.

Sources of eventsThe Tivoli Enterprise Console accepts events from many sources. Typically,Tivoli software is set up so that events are sent in response to changes inan application or system resource. For example, you can configure resourcemodels to send events as well as to report in other ways. Tivoli tasks cansend events.

Event processingThe Tivoli Enterprise Console uses rules to process events. A rule is madeup of a set of logic statements. The rule makes decisions on what to do

109

with the event based on information provided in the event, such as theevent class, event name, severity, location, and description.

A rule’s logic provides one or more responses to the event: it can dropinsignificant events, escalate important events, create new events, orrespond to defined relationships of multiple events (event correlation). Itcan also close an old event when a new event indicates that the originalcondition is resolved.

Event grouping

The Tivoli Enterprise Console can filter events into event groups. Theseevent groups are typically organized by function but can also be organizedby other criteria, such as location or organizational jurisdiction.

Event groups are especially useful for subdividing all Tivoli EnterpriseConsole events into manageable chunks. Administrators can be assigned toone or more event groups.

Viewing events

The Tivoli Enterprise Console includes a console where administrators canwatch for incoming events and respond to them. The event console is auseful tool for managing by exception. The Tivoli Enterprise Console canfilter out normal events, respond automatically to anticipated problems,and forward only those events that require human intervention.

Responses to eventsThe Tivoli Enterprise Console normally can provide automatic responses tomany common events, either by executing response programs or byexecuting Tivoli tasks. For example, you can set a response to respond tothe event that is received when a server becomes unavailable. The specificresponse can be to inform an administrator or to attempt automatic restartsof the server, or a combination of both.

Configuring Tivoli Enterprise Console to work with IBM TivoliMonitoring for Databases: Microsoft SQL Server

ObjectiveTo configure Tivoli Enterprise Console so you can access and view IBM TivoliMonitoring for Databases: Microsoft SQL Server events.

Background informationYou can send the following events to Tivoli Enterprise Console:

Resource model eventsAll resource models provided by IBM Tivoli Monitoring for Databases:Microsoft SQL Server provide the option to send events to Tivoli EnterpriseConsole. For example, the Free Space Deficit resource model can beconfigured to send an event when a database crosses from Normal (<70%full) to Warning (>70% full).

Task eventsAll tasks provided by IBM Tivoli Monitoring for Databases: Microsoft SQLServer provide the option to send events to Tivoli Enterprise Console inresponse to task success or task failure.

You can configure Tivoli Enterprise Console in any of the following ways:v Use the ConfigureTECMSSQL task from the Tivoli desktop


v Use the ConfigureTECMSSQL task from the command linev Use Tivoli Enterprise Console commands at the command line

Using the ConfigureTECMSSQL task is recommended. This task performs allTivoli Enterprise Console configuration in a single step. It provides options forconfiguring Tivoli Enterprise Console to accept events from resource models andtasks.

The task does the following:v Creates the specified rule base, if it does not already exist.v Optionally copies an existing rule base into a newly created rule basev Configures the rule base for the selected option(s) by importing the appropriate

class and rule set files.v Compiles the rule base.v Optionally restarts the event server.

Refer to the IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guidefor additional information about this task.

Required authorization rolesenior and mssqlserver_dba (you must have both roles)


When you finishNone

ProcedureYou can perform this procedure from either the Tivoli command line, Tivolidesktop, or by using Tivoli Enterprise Console commands.

Command line: See the IBM Tivoli Monitoring for Databases: Microsoft SQL ServerReference Guide for ConfigureTECMSSQL command line information.

Desktop:


the Policy Region: Monitoring for Microsoft SQL Server window.3. Double-click the ITMMicrosoftSQLServerTasks icon to display the Task

Library: ITMMicrosoftSQLServerTasks window.4. Double-click the ConfigureTECMSSQL icon to display the Execute Task

window.5. (Optional) Do the following to view the task results:

a. Change the value in the Timeout text box from 60 to 200.b. Select the Display on Desktop check box to display the task output to the

desktop.6. Select a managed resource from which to receive events by doing the following:

Additional Information: The Available Task Endpoints list displays only thosemanaged resources that have Tivoli Enterprise Console servers.a. Click on a managed resource from the Available Task Endpoints group box

to highlight that managed resource.

Appendix B. Setting up Tivoli Enterprise Console 111

b. Click the left arrow to move the selected resource into the Selected TaskEndpoints list.

7. Click Execute to display the ConfigureTECMSSQL task argument window.

8. Do the following to configure Tivoli Enterprise Console to work with IBMTivoli Monitoring for Databases: Microsoft SQL Server:

Enter the name for the Microsoft SQL rule baseSpecify the name of the new or existing rule base to configure. If youspecify an existing rule base, the task checks to make sure both its classand rule set files are defined correctly. Do not to modify the Defaultrulebase. The Tivoli command, wlsrb, provides a list of all rulebases.Enter only the name; a full path is ignored. A rule base consists of a setof expressions (rule set files) used by the event server to determine ifan event meets the rule conditions. The rules may also define a set ofactions that are taken when an event meets the specified ruleconditions.

Clone currently ACTIVE rule baseCheck this box if you want to copy the currently active rule base.

Note: If you intend to specify a rule base other than Default, be surethat the rule base is valid first.

Create new rule base without cloningCheck this box if you want to create a new rule base not based on onan existing rule base.

Rule base to clone:Select this option if you want to copy an existing rule base as the basisfor the rule base you are setting up for this configuration option.Specify the name of the rule base in the Rule base to clone: field.

Note: If you specify an invalid rule base name, the task fails with amessage that the rule base is invalid. Run the task again with thecorrect rule base name. If the name is correct but the task fails,check the validity of the specified rule base by compiling therule base. If the compiler does not report an error, the rule baseis valid.

Restart Event ServerCheck this box if you want to restart the event server immediately


following configuration. When you create a new rule base or modify anexisting one, you must restart the event server for any rule baseconfigurations to take effect.

This task starts an event server if it is not already running. If the eventserver is running, this task stops and restarts it. If you do not use thetask to restart the event server, you must load the rule base and restartthe event server manually.

9. Click Set & Execute to run the task.Additional Information: If the Restart Event Server option is specified, this taskstarts the server if it is not running, or stops and restarts it if it is currentlyrunning. If you set the Display on Desktop option (in step 5), the systemdisplays the results of this task in a window.

Using Tivoli Enterprise Console commands: In the following exampleconfiguration, the following assumptions are made:v You have the appropriate roles to create event server objects.v The Tivoli Enterprise Console server is installed on the same host as the Tivoli

management region server.v This is not an inter-region environment. There is only one Tivoli management

region server.v You want to configure the event server for IBM Tivoli Monitoring and tasks. An

import section is provided for each; you can skip any section.

Note: The import steps must be performed in the order given.v You create and configure a rule base named MSSQLBase.v You copy the Default rule base into the new MSSQLBase. If you currently use a

different rule base, you can copy it instead.v The rule base directory is $BINDIR/TME/TEC/rulebase_name

v You create and configure an event group called MSSQLBaseEvent.v You configure the Tivoli environment by running the setup_env script.1. Verify the installation and registration of the Tivoli Enterprise Console server

by using the wlookup command:wlookup -ar EventServer

Additional Information: This should return one line similar to the following line;the object identification number (OID) is different.EventServer 1671340084.1.695#Tec::Server#

If you have an interconnected Tivoli management region with an event serverinstalled in each Tivoli management region, each Tivoli Enterprise Consoleserver is reported.

2. Create a new rule base using the wcrtrb command:wcrtrb -S @EventServer:EventServer \-d $BINDIR/TME/TEC/ITMMSSQL_Base ITMMSSQL_Base

3. Copy the contents of the Default rule base into the new rule base using thewcprb command:wcprb -S @EventServer:EventServer Default ITMMSSQL_Base

Note: If your current rule base is not Default, copy your current rule baseinstead.


4. Configure the Tivoli Enterprise Console for IBM Tivoli Monitoring byimporting the classes, then compiling them:wimprbclass -S @EventServer:EventServer \tivoli_install_dir/<interp>/TMNT_TEC/Tmw2k.baroc \ITMMSSQL_Base

wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic_unix/ \/TME/MSSQL directory.

wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ \MSSQLScripts/ITMMSSQL.baroc\ITMMSSQL_Base

wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ \MSSQLScripts/ITMMSSQLResourceModels.baroc \ITMMSSQL_Base

wcomprules -S @EventServer:EventServer ITMMSSQL_Base

5. Configure Tivoli Enterprise Console for IBM Tivoli Monitoring for Databases:Microsoft SQL Server tasks by importing the classes, then compiling them:wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ MSSQLScripts/ESMTask.baroc \ITMMSSQL_Base

wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ MSSQLScripts/MSSQLTask.baroc \ITMMSSQL_Base

wcomprules -S @EventServer:EventServer ITMMSSQL_Base

6. Load the rule base by entering the following:wloadrb -S @EventServer:EventServer ITMMSSQL_Base

7. Do one of the following to activate the new classes and rules:v If the event server is running, enter the following:

wstopesvr -S @EventServer:EventServer

wstartesvr -S @EventServer:EventServer

—OR—v If the event server is not running, enter the following:

wstartesvr -S @EventServer:EventServer

Viewing events in Tivoli Enterprise Console

ObjectiveTo view events in Tivoli Enterprise Console so you can work with the events.

Background information

Note: The following procedure is relevant for versions of Tivoli Enterprise Consoleearlier than version 3.7.

After you set up Tivoli Enterprise Console, you can view events.

Required authorization roleuser



When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.1. Double-click the Event Server icon on the Tivoli desktop to open the Tivoli

Enterprise Console console.Additional Information: The Tivoli Enterprise Console console contains an iconfor each event group that you are authorized to view.

2. Double-click the SQLEventBase icon to display the list of events for that eventgroup in the SQLEventBase window.

3. View the details of an event by doing one of the following:v Double-click the event.

—OR—v Use the View Message button by doing the following:

a. Click on an event to highlight the event.b. Click View Message.

Additional Information: The Event Group Message Viewer window displaysinformation for each slot (information field) in the event.


Appendix C. Integrating with Tivoli Business SystemsManager

This chapter provides information on using Tivoli Business Systems Manager tomanage IBM Tivoli Monitoring for Databases: Microsoft SQL Server resources andevents.

Table 17. Guidelines for integrating with Tivoli Business Systems Manager

Goal Refer to

Understanding Tivoli Business SystemsManager

“Understanding Tivoli Business SystemsManager” on page 117

Integrating IBM Tivoli Monitoring forDatabases: Microsoft SQL Server intoTivoli Business Systems Manager

“Integrating IBM Tivoli Monitoring for Databases:Microsoft SQL Server into Tivoli Business SystemsManager” on page 118

Working with Tivoli Business SystemsManager

“Working with Tivoli Business Systems Manager”on page 121

Uninstalling IBM Tivoli Monitoring forDatabases: Microsoft SQL Serverintegration from Tivoli BusinessSystems Manager

“Uninstalling IBM Tivoli Monitoring forDatabases: Microsoft SQL Server integration fromTivoli Business Systems Manager” on page 121

Understanding Tivoli Business Systems ManagerTivoli Business Systems Manager is a business systems management tool thatenables you to graphically monitor and control interconnected businesscomponents and operating system resources. A business resource and its resourcesare referred to as a Line of Business (LOB).

Tivoli Business Systems Manager consists of the following components:

Tivoli Business Systems Manager serverThe Tivoli Business Systems Manager server processes all the availabilitydata that is collected from various sources. Availability data is inserted inthe Tivoli Business Systems Manager database, where intelligent agentsprovide alerts on monitored objects and then broadcast those alerts toTivoli Business Systems Manager workstations. The management serverprocesses all user requests that originate from the workstation and includesa database server that is built around a Microsoft SQL Server database.

Tivoli Business Systems Manager JAVA GUIThe Tivoli Business Systems Manager JAVA GUI displays objects incustomized views, called Line of Business Views. Objects are presented in ahierarchical TreeView so that users can see the relationship betweenobjects. Alerts are overlaid on the objects when the availability of the objectis threatened.

Tivoli Business Systems Manager Event enablementTivoli Business Systems Manager event enablement is installed on theTivoli Enterprise Console event server and enables the event server toforward events to Tivoli Business Systems Manager. Event enablementdefines event classes and rules for handling events related to TivoliBusiness Systems Manager.

117

Task serverThe Tivoli Business Systems Manager task server is installed on the TivoliEnterprise Console event server with event enablement. It receives taskrequests from the Tivoli Business Systems Manager workstation, runs thetasks on the Tivoli server on which it is installed, and returns the output toTivoli Business Systems Manager.

Integrating IBM Tivoli Monitoring for Databases: Microsoft SQL Serverinto Tivoli Business Systems Manager

Before you integrate Tivoli Business Systems Manager, perform the following threeprerequisite steps:v Install the Tivoli Business Systems Manager configuration, as described in the

Tivoli Business Systems Manager Installation and Configuration Guide. You mustinstall Tivoli Business Systems Manager Version 1.5.

v Install and configure the Tivoli Business Systems Manager Event Enablement onall Tivoli Enterprise Console event servers that receive events that you want toforward to Tivoli Business Systems Manager. See the Tivoli Business SystemsManager Installation and Configuration Guide for more information.

v Configure Tivoli Business Systems Manager to communicate with each TivoliBusiness Systems Manager Event Enablement installed in the previous step. Seethe Tivoli Business Systems Manager Installation and Configuration Guide for moreinformation.

Integrating IBM Tivoli Monitoring for Databases: Microsoft SQL Server into TivoliBusiness Systems Manager involves the following three steps:v Installing the IBM Tivoli Monitoring for Databases: Microsoft SQL Server

integration on the Tivoli Business Systems Manager server, as described in“Integrating IBM Tivoli Monitoring for Databases: Microsoft SQL Server withTivoli Business Systems Manager”.

v Configuring your Tivoli Enterprise Console event server to forward events toTivoli Business Systems Manager, as described in “Configuring the TivoliEnterprise Console event server” on page 119.

v Defining the specific IBM Tivoli Monitoring for Databases: Microsoft SQL Serverinstances to Tivoli Business Systems Manager using a discovery task, asdescribed in “Discovering resources for Tivoli Business Systems Manager” onpage 120.

Integrating IBM Tivoli Monitoring for Databases: Microsoft SQL Serverwith Tivoli Business Systems Manager

ObjectiveTo integrate IBM Tivoli Monitoring for Databases: Microsoft SQL Server with TivoliBusiness Systems Manager so you can enable your Tivoli Business SystemsManager server to receive IBM Tivoli Monitoring for Databases: Microsoft SQLServer events.

Background informationTo enable Tivoli Business Systems Manager to manage IBM Tivoli Monitoring forDatabases: Microsoft SQL Server events, you need to install an IBM TivoliMonitoring for Databases: Microsoft SQL Server integration program on the TivoliBusiness Systems Manager server. This integration program does the followingsteps:


v Defines the IBM Tivoli Monitoring for Databases: Microsoft SQL Server instancesin Tivoli Business Systems Manager

v Defines a line of business for IBM Tivoli Monitoring for Databases: MicrosoftSQL Server resources

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.

Before you beginEnsure that your Tivoli Business Systems Manager environment is configuredcorrectly and that you have event enablement on each Tivoli Enterprise Consoleevent server that you want to forward events. For more information, see the TivoliBusiness Systems Manager Installation and Configuration Guide.

When you finishConfigure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager.

Procedure1. Insert the IBM Tivoli Monitoring for Databases: Microsoft SQL Server CD on

the Tivoli Business Systems Manager server.2. From a command prompt, navigate to the \TBSM directory.3. Type install to start the installation wizard and display the welcome screen.4. Click Next.5. Specify an installation location for the Tivoli Business Systems Manager

integration.Additional Information: The default location is C:\tivoli\CTW. Click Browse toselect a different installation location.

6. Click Next to display the installation location and total installed size.7. Click Next to continue.8. Provide the following Microsoft SQL Server information:

SQL ServerThe name of the SQL server associated with this Tivoli BusinessSystems Manager server.

SQL UseridThe SQL user ID.

SQL PasswordThe password associated with the SQL User ID defined above.

9. Click Next to start the installation.Additional Information: A progress bar is displayed to show the progress of theinstallation. When installation is complete, a message appears.

10. Click Finish to exit the installation wizard.

Configuring the Tivoli Enterprise Console event server

ObjectiveTo configure the Tivoli Enterprise Console event server so you can forward eventsto Tivoli Business Systems Manager.

Appendix C. Integrating with Tivoli Business Systems Manager 119

Background informationBefore Tivoli Enterprise Console event servers can forward events to TivoliBusiness Systems Manager, you have to configure them to use a rule base toforward the events.


Before you beginInstall the Tivoli Business Systems Manager event enablement on each TivoliEnterprise Console event server that you want to forward events to Tivoli BusinessSystems Manager. For more information, see the Tivoli Business Systems ManagerInstallation and Configuration Guide for more information.

When you finishDefine your IBM Tivoli Monitoring for Databases: Microsoft SQL Server instancesto Tivoli Business Systems Manager with the MSSQLTBSMDiscovery task, asdescribed in “Discovering resources for Tivoli Business Systems Manager”.

ProcedureUse the ConfigureTECMSSQL task to configure (or reconfigure) each event server.If you installed the Tivoli Business Systems Manager event enablement on theevent server, this task recognizes that and compiles the rule base that forwardsevents to Tivoli Business Systems Manager.

Discovering resources for Tivoli Business Systems Manager

ObjectiveTo define the specific IBM Tivoli Monitoring for Databases: Microsoft SQL Serverinstances to Tivoli Business Systems Manager.

Background informationThe IBM Tivoli Monitoring for Databases: Microsoft SQL Server integration thatyou installed in “Integrating IBM Tivoli Monitoring for Databases: Microsoft SQLServer with Tivoli Business Systems Manager” on page 118 defined the types ofinstances that Tivoli Business Systems Manager manages. The next step is to definethe specific instances with the MSSQLTBSMDiscovery task. This task searches amanaged node for instances and sends a DISCOVER event to Tivoli BusinessSystems Manager for each instance. The MSSQLTBSMDiscovery task alsomaintains a list of the instances that have been discovered and alerts TivoliBusiness Systems Manager when they have been deleted by sending TivoliBusiness Systems Manager a GONE event for each instance that no longer existson the managed node.


Before you beginConfigure your Tivoli Enterprise Console event server, as described in“Configuring the Tivoli Enterprise Console event server” on page 119.

When you finishUse Tivoli Business Systems Manager to view and manage your IBM TivoliMonitoring for Databases: Microsoft SQL Server instances. For information onusing Tivoli Business Systems Manager, see the Tivoli Business Systems ManagerUser’s Guide. For information on the IBM Tivoli Monitoring for Databases:


Microsoft SQL Server tasks that you can run from Tivoli Business SystemsManager, see “Working with Tivoli Business Systems Manager”.


Command line: Use the wruntask command to run the MSSQLTBSMDiscoverytask from the command line. For information on the CLI syntax for this task, seethe IBM Tivoli Monitoring for Databases: Microsoft SQL Server Reference Guide.

Desktop:

1. Open the ITMMicrosoftSQLServerTasks task library.2. Double-click the MSSQLTBSMDiscovery task.3. Select the managed node on which you want to search for instances.4. Click Execute.

Additional Information: After the task completes successfully, you receive a list ofthe DISCOVER and GONE events that were sent to Tivoli Business SystemsManager.

Working with Tivoli Business Systems ManagerTivoli Business Systems Manager monitors the status of resource models. Eventsgenerated by the Tivoli Enterprise Console adapter or resource models areforwarded from Tivoli Enterprise Console to Tivoli Business Systems Manager.

For more information about these tasks and resource models, see the IBM TivoliMonitoring for Databases: Microsoft SQL Server Reference Guide.

Uninstalling IBM Tivoli Monitoring for Databases: Microsoft SQLServer integration from Tivoli Business Systems Manager

ObjectiveTo remove the IBM Tivoli Monitoring for Databases: Microsoft SQL Serverintegration from Tivoli Business Systems Manager.

Background informationUninstalling the IBM Tivoli Monitoring for Databases: Microsoft SQL Serverintegration removes the IBM Tivoli Monitoring for Databases: Microsoft SQL Serverobject definitions and objects from Tivoli Business Systems Manager.

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.


When you finishNone

Procedure1. On the Tivoli Business Systems Manager server, open a command prompt.2. Navigate to the directory where you installed the IBM Tivoli Monitoring for

Databases: Microsoft SQL Server integration.

Appendix C. Integrating with Tivoli Business Systems Manager 121

3. Type uninstall to start the uninstallation wizard.4. Click Next on the welcome screen to display the installation location for the

Tivoli Business Systems Manager integration.5. Click Next to continue.6. Provide the following Microsoft SQL Server information:

SQL ServerThe name of the SQL server with which this Tivoli Business SystemsManager server is associated

SQL UseridThe SQL user ID.

SQL PasswordThe password for the user ID defined above.

7. Click Next to start the uninstallation.8. Click Finish to exit the installation wizard.


Appendix D. Problem determination

This appendix provides information about resolving problems that might occurwhen you run IBM Tivoli Monitoring for Databases: Microsoft SQL Server.

Note: For install and uninstall problem determination, see the IBM TivoliMonitoring for Databases Installation and Setup Guide.

Frequently asked questionsThe following frequently asked questions are divided into the following categories:v Resource modelsv Connectivity and authorizationv Miscellaneous

Resource modelsHow can I determine why a resource model is failing?

Check the IBM Tivoli Monitoring logs for information. IBM TivoliMonitoring logs are stored in $LCF_DATDIR/LCFNEW/Tmw2k/Tmw2k.log on the endpoint. To increase the level of detail inthese logs, use the wdmtrceng command. Additional information about theMSSQL data provider can be found in$LCF_DATDIR/LCFNEW/CTW/logs.

What does the return code mean?Return codes provide information such as resource model status oravailability. The return code number displays in the IBM Tivoli MonitoringWeb Health Console status field, or by using the wdmlseng command. Seethe ″Resource model″ chapter of the IBM Tivoli Monitoring for Databases:Microsoft SQL Server Reference Guide for a listing of resource model returncodes, their description, and what action you can take to resolve each code.

Why was no event reported to Tivoli Enterprise Console when a resource modelfailed to start?

Tivoli Enterprise Console events are not generated when a resource modelfails to start. They are generated when there is a problem or change in aresource being monitored. Problems that occur with the resource modelitself are reported in the IBM Tivoli Monitoring Web Health Console.

Why are resource models unable to access the Microsoft SQL Server database?Providing an invalid user name, password, or account type at registrationcan cause the product to be unable to access the Microsoft SQL Serverinstance. You can check the defined authorization by running theExecuteSQL task. If the SQL query fails due to authorization, appropriatelyconfigure the Microsoft SQL Server object and redistribute the resourcemodels.

Why does an indication show a health of 100% when wdmlseng shows that thecorresponding resource model is failing?

IBM Tivoli Monitoring determines the health of a particular indication byhow often the indication is sent. Resource models do not send indicationsif they are in a state other than running. Since indications are not sent, theindication health displays as 100%.

123

Why are the resource models that I disabled now enabled?IBM Tivoli Monitoring enables all resource models when you reboot amachine.

Why are my resource models not logging data?Resource models do not log data by default. You must select the EnableData Logging check box for each resource model to log data. If you do notselect this check box, resource model data will not be recorded.

How does the wdmlseng command work?To check the status of resource models, run the following command:wdmlseng -e <endpoint>

Resource models should return the statement ″Running.″ This means thatthe resource models are monitoring everything correctly and have notfailed or errored out. To check which resource models are sendingindications, run the following command:wdmlseng -e <endpoint> -verbose

Sent indications show less than 100%. Indications that are not sent show100%.

What does ″Not Compiled″ mean when I run wdmlseng?An internal IBM Tivoli Monitoring error occurred running the resourcemodel if you see an error such as the following:bash-2.03#wdmlseng -e handleForwarding the request to the engine...The following profiles are running:v920@[email protected]#merfox-regionMicrosoftSQLServerAvailability:Not Compiled

Ensure that you have distributed the profile to the Microsoft SQL Serverobject and not the endpoint. If needed, contact customer support.

What do the numeric codes 1–8 mean when I run wdmlseng?For an explanation of the return codes for the resource models, see the″Resource models″ chapter of the IBM Tivoli Monitoring for Databases:Microsoft SQL Server Reference Guide.

Connectivity and authorizationWhy am I unable to connect to a server after registering it with Discovery?

You must configure user name and password credentials for a successfullogin to the Microsoft SQL Server. IBM Tivoli Monitoring for Databases:Microsoft SQL Server provides the following options to configure the username and password on each server following registration:v MSSQLAuthentication task

Use this task to automatically configure multiple servers. See theMSSQLAuthentication task in the IBM Tivoli Monitoring for Databases:Microsoft SQL Server Reference Guide for task information. See Chapter 6,“Working with tasks and jobs”, on page 57 for instructions on how torun a task.

v Desktop (Edit Properties window)Use the desktop to configure an individual server. See “Editing serverproperties” on page 42 for more information.

v Command line (wmchregsvr)


Use the command line to configure an individual server. See “Editingserver properties” on page 42 for more information.

What are the port requirements for communication?There are no special firewall considerations for IBM Tivoli Monitoring forDatabases: Microsoft SQL Server. The software depends on theframework‘s ability to communicate with the LCF endpoint and receivedowncalls. The ports required to be opened on the LCF endpoint are localports (0.0.0) and have no firewall implications.

What are the access requirements for Microsoft SQL Server authorization?Resource models access internal Microsoft SQL Server tables for job andmetric information. Job information is gathered from msdb.dbo sysjobsand sysjobhistory tables. Metrics are pulled from the sysperfinfo table.

The user name and password supplied for each Microsoft SQL Server mustallow access to these tables for proper function of the resource models. TheID assigned must have ″system administrator″ rights on the databaseserver. See the user name and password configuration informationdescribed on page 24.

Tasks that run against the Microsoft SQL Server also require appropriateauthorization. These tasks function properly when using an ID that has″system administrator″ rights.

MiscellaneousHow do I look up trace information?

You can find trace information in the following locations:

Table 18. Log file locations and descriptions

File Name Location From$LCF_DATDIR/

Description

trace.discgetattr.log LCFNEW/CTW/logs Contains trace information fromthe Discovery process.

trace.ITMMSSQLprov.log LCFNEW/CTW/logs Contains trace information fromthe provider for resource modeland task interaction. You canenable the file by editing theLCFNEW/CTW/config/ITMMSSQLprov.propertiesfile.

Tmw2k.log LCFNEW/Tmw2k (Windows NT only) Containstrace information from resourcemodels and IBM TivoliMonitoring engine. Enable withthe wdmtrceng command fromthe Tivoli Management Region.

How do I use witmcollectsupportdata to collect log files?Provided with IBM Tivoli Monitoring Component Services, thewitmcollectsupportdata command collects log files that can be sent tocustomer support. This command collects the log files from gateways andendpoints and stores the data in an XML file that you can view with a Webbrowser.

Note: This procedure can take up to ten minutes or more based on yourcurrent system load and network traffic. The log file created by this

Appendix D. Problem determination 125

command can exceed 10-20 MB. It is recommended that you storethe file on a file system with at least 50MB of free space.

The command syntax is as follows:# witmcollectsupportdata <OID> <Log_file> [-CHECKDB][-FULLLOGS]

Where:

$OID is either the Microsoft SQL Server, or endpoint object ID.

$Log_file is the name of the .xml file.

–CHECKDB if specified, causes wchkdb to run against the Tivolimanagement region environment.

–FULLLOGS if specified, causes the complete logs to be gathered. Thedefault collects the last 1,000 lines.

Example: The following example collects data for the Microsoft SQL ServerOID 1403131645.4.32 in the test.xml file in the /tmp directory:witmcollectsupportdata 1403131645.4.32 /tmp/test.xml MicrosoftSQLServer

Where is the trace log for IBM Tivoli Monitoring and how do I turn on traceloggers?

You can find the IBM Tivoli Monitoring trace log in the$LCF_DATDIR/LCFNEW/Tmw2k/Tmw2k.log for NT/2000 endpoints.

You must have previously set the trace log level to ’3’ in order for theselogs to be useful. To set the trace level to ‘3,’ enter the following commandfrom a managed node (not endpoint) command prompt:#wdmtrceng -e <endpoint name> "" 3 -1

After running this command, you must stop the IBM Tivoli Monitoringengine and restart it. Enter the following CLI command from a managednode (not the endpoint) to stop the IBM Tivoli Monitoring engine:# wdmcmd -stop -e <endpoint name>

Enter the following CLI command from a managed node (not theendpoint) to start the IBM Tivoli Monitoring engine:# wdmcmd —restart —e <endpoint name>

The resource models rely on the MSSQL data provider for access to theMicrosoft SQL Server. This log is found in$LCF_DATDIR/LCFNEW/CTW/logs/trace.ITMMSSQLprov.log. Theconfiguration file is found in$LCF_DATDIR/LCFNEW/CTW/config/ITMMSSQLprov.properties.

To increase the provider logging, modify the lineITMMSSQLprov.loggers.level=INFO

to readITMMSSQLprov.loggers.level=DEBUG_MAX

For changes to the properties file to take effect, the Windows Managementservice must be stopped and restarted. The following is an example ofoutput from the modified provider logging line:


ITMMSSQLprov.loggers.className=ccg_pdloggerITMMSSQLprov.loggers.level=DEBUG_MAX## Valid logging levels: ERROR, WARNING, INFO,# DEBUG_MIN, DEBUG_MID, DEBUG_MAX#ITMMSSQLprov.loggers.product=ITMMSSQLprovITMMSSQLprov.loggers.msgLogger.listenerNames=handlers.traceFileITMMSSQLprov.loggers.server=# ------------------------------------------handlers.traceFile.maxFiles=4\n# --------------------------------------------------\n# By default, the formatter will be a xml formatter\n# --------------------------------------------------\n# handlers.traceFile.formatterName=formatters.basicFmt\n# NOTE: To change logging from xml to text, uncomment the line above,\n# and comment the line below.\nhandlers.traceFile.formatterName=formatters.xmlFmt\n#=======================================================================\n# Define the properties for the formatter named\n# ’formatters.xmlFmt’\n#=======================================================================\n# ------------------------------------------\n# By default, the formatter will be a xml formatter\n# ------------------------------------------\n# formatters.basicFmt.className=ccg_basicformatter\n# NOTE: To change logging from xml to text, uncomment the line above,\n# and comment the line below.\nformatters.xmlFmt.className=ccg_xmlformatter\n# -------------------------------------------\n

Appendix D. Problem determination 127

Appendix E. Messages

CTW0100E No EditMode specified.

Explanation: The task requires that an edit mode ofAdd, Remove or Overwrite be specified.

Operator Response: Specify either Add, Remove orOverwrite as the edit mode and rerun the task.

CTW0101E Invalid error number supplied.

Explanation: The error number must consist of anumeric value.

Operator Response: Specify a valid numeric messagenumber and rerun the task.

CTW0102E An error number was not specified.

Explanation: The Task requires one or more messagenumbers as input.

Operator Response: Specify one or more validmessage numbers.

CTW0103I Error number that were overwritten(configured to not log) %1$s.

Explanation: No additional information is availablefor this message.

CTW0104E Cannot change error numbers %1$s.

Explanation: The message error numbers listed couldnot be altered.

Operator Response: Create the message number if itdoes not exist, or select a user defined messagenumber.

CTW0105W Message numbers %1$s do not exist.

Explanation: The message number specified does notexit.

Operator Response: Create the message number usingsp_addmessage or specify one that does exists.

CTW0106I Validation completed successfully.


CTW0107I Backup completed for database %1$s.


CTW0108I Backup to log complete for database%1$s.


CTW0109E Tivoli Enterprise Console NT Adapterfiles are not present.

Explanation: The tecad_win.conf, tecad_win.cds,tecad_win.fmt and win_gencds.exe files could not befound in the TEC Adapater installation directory.

Operator Response: Reinstall the TEC WindowsAdapter and rerun the task.

CTW0110I Customization completed successfully.


CTW0111I For database %1$s on Microsoft SQLServer %2$s the current options are:


CTW0112I Error numbers %1$s configured not tolog


CTW0113I Error numbers %1$s added to errorsalready configured to log


CTW0114I Error numbers %1$s only configured tolog.


CTW0302E You must enter one or more endpointson which to discover Microsoft SQLServers.

Explanation: No endpoints were supplied as inputarguments.

Operator Response: Run the Task/Job and supplyendpoints as input arguments.

129

CTW0303I IBM Tivoli Monitoring for Databases:Microsoft SQL Server is checking thestatus of the endpoint %1\$s.

Explanation: The discovery process is checking thestatus of the endpoint before proceeding with endpointtasks.

CTW0304I The endpoint %1\$s is up. IBM TivoliMonitoring for Databases: MicrosoftSQL Server is performing Discovery.


CTW0305W IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot performdiscovery because the endpoint %1\$s isnot up. Check the status of theendpoint.

Explanation: The endpoint is not reachable andMicrosoft SQL Server instances will not be discovered.

Operator Response: Start the LCF daemon on theendpoint and ensure the gateway is running. Re-runthe discovery process.

CTW0306W IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot contact%1\$s endpoint(s). See the Job outputfor details.

Explanation: The process attempted to discoverMicrosoft SQL Server instances but was unable tocontact the endpoint.

Operator Response: Ensure the LCF daemon on theendpoint and it’s associated gateway are operational.Re-run the discovery process.

CTW0307W Registry indicates that a Microsoft SQLServer was not installed on %1\$s.

Explanation: The discovery process has not found aMicrosoft SQL Server installed on this endpoint.

Operator Response: Install a Microsoft SQL Serverand re-run the discovery.

CTW0308E The Get_MSSQL_Attributes task onendpoint %1\$s failed.

Explanation: The discovery task has failed to runproperly on the endpoint.

Operator Response: Ensure the LCF daemon isrunning on the endpoint. Try running a different taskagainst the endpoint to verify the Tivoli framework isoperational. If the problem persists contact Tivolisupport.

CTW0309E The discsql.exe file was not found onthe endpoint %1\$s.

Explanation: The executable used to search theregistry for Microsoft SQL Server instances was notfound on the endpoint.

Operator Response: Verify that the Microsoft SQLServer PAC was installed on the gateway controllingthis endpoint. If the problem persists contact Tivolisupport.

CTW0310E Registration of ITMMSSQLprov.dllfailed for the endpoint %1\$s. For moreinformation, refer to Microsoft returncode %2\$s.

Explanation: The native provider registration hasfailed on this endpoint.

Operator Response: Verify that the Microsoft SQLServer PAC was installed on the gateway controllingthis endpoint. If the problem persists contact Tivolisupport.

CTW0311I Registration of ITMMSSQLprov.dllsucceeded for the server %1\$s on theendpoint %2\$s.

Explanation: The native provider registration hassucceeded for the endpoint.

CTW0312E The ODBC service setup failed for theserver %1\$s on the endpoint %2\$s.For more information, refer to Microsoftreturn code %3\$s.

Explanation: The ODBC data source creation hasfailed for this Microsoft SQL Server instance.

Operator Response: Verify that the Microsoft SQLServer PAC was installed on the gateway controllingthis endpoint. Verify that the endpoint has thesupported level of MDAC. If the problem persistscontact Tivoli support.

CTW0313I The ODBC services setup succeeded forthe server %1\$s on the endpoint%2\$s.

Explanation: The ODBC data source was setup for theMicrosoft SQL Server instance.

CTW0314E The Managed Object Format (MOF) forPerfProv MOF failed to compile for theserver %1\$s on the endpoint %2\$s.For more information, refer to the Tivolireturn code %3\$s.

Explanation: The MOF failed to compile for the nativeprovider.

CTW0303I • CTW0314E


Operator Response: Ensure that WMI is installed onthe endpoint and is running a supported version.

CTW0315I The Managed Object Format (MOF) forPerfProv MOF compiled successfully forthe server %1\$s on the endpoint%2\$s.

Explanation: The MOF was successfully compiled forthe native provider.

CTW0316E The Managed Object Format (MOF) forITMMSSQLprov.Mof failed to compilefor the server %1\$s on the endpoint%2\$s. For more information, refer tothe Tivoli return code %3\$s.

Explanation: The MOF failed to compile for the nativeprovider.

Operator Response: Ensure that WMI is installed onthe endpoint and is running a supported version.

CTW0317I The Managed Object Format (MOF) forfile ITMMSSQLprov.Mof compiledsuccessfully for the server %1\$s on theendpoint %2\$s.

Explanation: The MOF was successfully compiled forthe native provider.

CTW0318I The server %1\$s was previouslydiscovered on %2\$s. The server cannotbe discovered again.

Explanation: The Microsoft SQL Server already existsin the TMR and cannot be discovered again.

Operator Response: If the discovery must be runagainst this Microsoft SQL Server instance again thendelete the object from the TMR and re-run discovery.

CTW0319I The application proxy Create Objectsucceeded for the Microsoft SQL Serverobject %1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance objectwas created in the TMR.

CTW0320I The application proxy Set Namesucceeded for the Microsoft SQL Serverobject %1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance namewas set properly.

CTW0321W The application proxy Set Name failedfor the Microsoft SQL Server object%1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance namewas not set properly.

Operator Response: The Microsoft SQL Serverprototype object might be corrupt. Contact support.

CTW0322I The application proxy Set Homesucceeded for the Microsoft SQL Serverobject %1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance homedirectory was set properly.

CTW0323W The application proxy Set Home failedfor the Microsoft SQL Server object%1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance homedirectory was not set properly.


CTW0324I The application proxy Set Versionsucceeded for the Microsoft SQL Serverobject %1\$s on %2\$s.

Explanation: The Microsoft SQL Server instanceversion was set properly.

CTW0325W The application proxy Set Version failedfor the Microsoft SQL Server object%1\$s on %2\$s.

Explanation: The Microsoft SQL Server instanceversion was not set properly.


CTW0326E The application proxy Create Objectfailed for the Microsoft SQL Serverobject %1\$s on %2\$s.

Explanation: The Microsoft SQL Server instance wascreated in the TMR.

CTW0327U The DiscoverMSSQLServers taskcompleted. See the %1\$s log file fordetails.


CTW0315I • CTW0327U

Appendix E. Messages 131

CTW0370I TBSM Discovery Success


CTW0371I TBSM Discovery Failure


CTW0372I Microsoft SQL Server 1%$s


CTW0373I Authentication changed for MicrosoftSQL Server %1$s


CTW0374E Could not change authentication forMicrosoft SQL Server %1$s

Explanation: The task could not modify the contentsof the Microsoft SQL Server object.

Operator Response: Verify the Microsoft SQL Serverobject exists.

CTW0375W There is no Microsoft SQL Serverregistered.

Explanation: No Microsoft SQL Server is registered asa Tivoli managed object.

Operator Response: Run discovery to locate andcreate Microsoft SQL Server managed objects.

CTW0376E No user name specified.

Explanation: The task requires a user name bespecified as input.

Operator Response: Specify a user name and rerunthe task.

CTW0377W The database %1$s on Microsoft SQLServer %2$s does not exist.

Explanation: The task could not perform asp_dboption on the database name specified.

Operator Response: Specify a valid database name onthe server and rerun the task.

CTW0378E The following was returned to the taskduring its execution. %1$s

Explanation: During execution, the task was returnedthis text message from the Microsoft SQL Server.

Operator Response: Take the appropriate action based

on the contents of the message reported.

CTW0379I Backing up database %1$s


CTW0380I Backing up database log %1$s


CTW0381I The task has completed its processing.


CTW0417E An error occurred because the ‘Clonecurrently ACTIVE rule base’ option wasselected and a rulebase name wasentered. Either specify the ″Clonecurrently ACTIVE rule base″ option orenter a rule base name.

Explanation: An error occurred because mutuallyexclusive options have been selected.

Operator Response: Either select the ″Clone currentlyACTIVE rule base″ option or enter a rule base name.

CTW0418E An error occurred because the ‘Specify arule base to clone’ option was selectedbut no rule base name was specified.Specify a rule base name in the ″Rulebase to clone″ text box.

Explanation: An error occurred because a requiredargument was not specified.

Operator Response: Specify a rule base name in the″Rule base to clone″ text box.

CTW0419E An error occurred because both the‘Create new rule base without cloning’and ″Rule base to clone″ options wereselected. Choose either ″Create new rulebase without cloning″ or using a rulebase to clone.

Explanation: An error occurred because mutuallyexclusive options have been selected.

Operator Response: Choose either ″Create new rulebase without cloning″ or using a rule base to clone.



CTW0447E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot open thetemporary file %1\$s/%2\$s: %3\$s for%4\$s on the Tivoli Enterprise Consoleserver.

Explanation: An error occurred attempting to openthe specified temorary file on the specified node.

Operator Response: Make sure the specified file hasnot been deleted or, you have sufficient space andprivileges on the specified system.

CTW0448E You must prepare files for transferbefore the internal routine to preparefor the rulebase compilation.

Explanation: This error may occur because an attemptwas made to compile the rule base prior to importingthe necessary BAROC and rule set files.

Operator Response: Make sure the BAROC or rule setfiles exist on the TMR server where the TEC isinstalled.

CTW0449E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot get thelabel of the managed node object ID%1\$s. Verify the integrity of the Tivolidatabase using the wchkdb -ucommand.

Explanation: The managed node object ID could notbe determined.

Operator Response: Make sure the object for whichthe object ID was queried is valid or that the Tivolidatabase is not corrupt using the wchkdb -u command.

CTW0450E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot get theobject ID of the managed node %1\$s.Verify the integrity of the Tivolidatabase using the wchkdb -ucommand.

Explanation: An error occurred while attempting toget the managed node object ID.

Operator Response: Make sure the object for whichthe object ID was queried is valid or that the Tivolidatabase is not corrupt using the wchkdb -u command.

CTW0451E An error occurred accessing thedirectory %1\$s on the remote managednode %2\$s. Confirm that the managednode is up and try again.

Explanation: This error may occur because thedirectories where the BAROC and rule set files shouldbe located, do not exist on the TMR server.

Operator Response: Make sure the directories where

the BAROC and rule set files should be located, existon the TMR server.

CTW0452E The directory %1\$s does not exist onthe local managed node %2\$s.

Explanation: This error may occur because thedirectory from which to copy or transfer the BAROC orrule set files do not exist on the specified managednode.

Operator Response: Make sure the appropriatedirectories from which to copy or transfer the BAROCor rule set files, exist on the specified node.

CTW0453E An error occurred because IBM TivoliMonitoring for Databases: MicrosoftSQL Server cannot prepare files fortransfer before checking the endpoint.Check the endpoint and try again.

Explanation: This error may have occurred becausethe files to be transferred do not exist on the TMRserver.

Operator Response: Make sure the BAROC and ruleset files exist on the TMR server.

CTW0454E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot open thereport file. You must check the endpointbefore opening a report file.

Explanation: An error occurred attempting to writethe task output to a file.

Operator Response: Make sure the managed node towhich the file should be written is available.

CTW0456E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot close thereport file because it was never opened.

Explanation: An error occurred while attempting toclose a file.

Operator Response: An attempt was made to close afile that was not first opened. Contact your TivoliService provider should this internal error occur.

CTW0457E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot close%1\$s/%2\$s: %3\$s for %4\$s.

Explanation: An error occurred while attempting toclose a file.

Operator Response: An attempt was made to close afile that was not first opened. Contact your TivoliService provider should this internal error occur.

CTW0447E • CTW0457E


CTW0458E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot retrievethe object ID for host %1\$s.

Explanation: An error occurred while attempting toget the managed node object ID.

Operator Response: Make sure the managed node isavailable and verify the integrity of the Tivoli databaseusing the wchkdb -u command.

CTW0459E IBM Tivoli Monitoring for Databases:Microsoft SQL Server cannot copy filesto %1\$s on the host %2\$s.

Explanation: A failure occurred attempting to copyfiles to the specified directory on the specified host.

Operator Response: Make sure the file destination iswriteable and you have the appropriate permissions towrite to this location.

CTW0465E An error occurred because a rule basename to configure was not specified.Specify a rule base name to configure.

Explanation: An error occurred because a requiredargument was not specified.

Operator Response: Specify a rule base name toconfigure.

CTW0466I The task completed for event server%1\$s.


CTW0467E An event server was not installed onTivoli management region %1\$s.

Explanation: An attempt was made to run the eventserver configuration task on a TMR where the eventserver is not installed.

Operator Response: Make sure event server isinstalled on the machine where the event serverconfiguration task is run.

CTW0468E An error occurred because an eventserver option to configure was notselected. Specify an event server optionto configure and try again.

Explanation: An attempt was made to run the eventserver configuration task without specifying an eventserver to configure.

Operator Response: Run the event serverconfiguration task, specifying the event server toconfigure.

CTW0469E An error occurred while checkingexisting rule base %1\$s. Configure therule base and try again.

Explanation: An error occurred while checking anexisting rule base.

Operator Response: Manually compile the rule baseto clone to ensure the rule base is well configured.Optionally run the event server configuration taskwithout cloning an existing rule base.

CTW0470E Run this task on the managed node onwhich the event server was installed.

Explanation: An attempt was made to run the eventserver configuration task on a managed node with noevent server configured.

Operator Response: Run the event serverconfiguration task on the node where the event serveris configured.

CTW0471I Configuring Tivoli Enterprise Consolefor IBM Tivoli Monitoring for MicrosoftSQL Server.


CTW0472I Configuring the Tivoli EnterpriseConsole for IBM Tivoli Monitoring forMicrosoft SQL Server Tivoli EnterpriseConsole Event Adapter customization.


CTW0473E %1\$s was not found on node %2\$s.Make sure IBM Tivoli Monitoring forDatabases: Microsoft SQL Server isinstalled on Tivoli management regionserver %1\$s.

Explanation: The BAROC and rule set files required toconfigure the rule base where not found on the TMRserver.

Operator Response: Make sure IBM Tivoli Monitoringfor Databases: Microsoft SQL Server is installed on theevent server’s TMR region server.

CTW0474W Rule base %1\$s already exists.

Explanation: An attempt was made to create a rulebase that already exists.

Operator Response: Configure the rule base withoutfirst attempting to create it, or specify the name of arule base that does not exist.

CTW0458E • CTW0474W


CTW0475I Creating rule base %1\$s.


CTW0476E Failed to create rule base %1\$s. Makesure the Tivoli administrator has theappropriate privileges in Tivolimanagement region %2\$s and thatthere are no embedded spaces in therule base name. See the IBM TivoliMonitoring for Databases: MicrosoftSQL Server documentation forinstructions on how to checkadministrator privileges and rule basenames.

Explanation: An attempt to create the specified rulebase failed.

Operator Response: Make sure the Tivoliadministrator has the appropriate privileges in TMRand that there are no embedded spaces in the rule basename.

CTW0477E Cannot copy rule base %1\$s. Makesure the rule base is valid and try again.

Explanation: A error occured attempting to copy thespecified rule base.

Operator Response: Make sure the rule base is validand try again.

CTW0478W Event group %1\$s already exists.

Explanation: An attempt was made to create analready existing event group.

Operator Response: Configure the event groupwithout first attempting to create it, or specify thename of an event group that does not exist.

CTW0479W Cannot create event group %1\$s.

Explanation: An error occurred while creating andevent group.

Operator Response: Make sure you have theappropriate privilege to create event groups.

CTW0480W Event source %1\$s already exists.

Explanation: An attempt was made to create analready existing event source.

Operator Response: Configure the event sourcewithout first attempting to create it, or specify thename of an event source that does not already exist.

CTW0481I Event source %1\$s was createdsuccessfully.


CTW0482I Configuring event group filters.


CTW0483I Configuring rule base %1\$s.


CTW0484E An error occurred compiling rule base%1\$s.

Explanation: An error occurred while compiling thespecified rule base.

Operator Response: Compile the rule base manuallyto make sure the defined classes and rule sets are valid.

CTW0485E An error occurred accessing file %1\$son managed node %2\$s.

Explanation: An error occurred while attempting toread or copy a file from the specified managed node.

Operator Response: Make sure the specified file existson the specified managed node.

CTW0486E An error occurred accessing directory%1\$s on Tivoli management regionserver %2\$s.

Explanation: An error occured while attempting toread or copy from the specified directory.

Operator Response: Make sure the specified directoryexists on the specified managed node.

CTW0487E Cannot transfer files from Tivolimanagement region server %1\$s to%2\$s.

Explanation: This error may occur because the file totransfer does not exist on the TMR server.

Operator Response: Make sure the specified file existson the TMR server.

CTW0488I Loading rule base %1\$s.


CTW0475I • CTW0488I


CTW0489I Stopping event server %1\$s.


CTW0490I Starting event server %1\$s.


CTW0491I The event server %1\$s on managednode %2\$s was configured for IBMTivoli Monitoring for Databases:Microsoft SQL Server.


CTW0492I Do the following to complete the TivoliEnterprise Console configuration.


CTW0493I Assign event group %1\$s with theappropriate roles to a TivoliAdministrator. See the IBM TivoliMonitoring for Databases: MicrosoftSQL Server for instructions.


CTW0494I Use the following steps to complete theTivoli Enterprise Console configuration:

1. Load rule base %1\$s.2. Stop and restart the eventserver %2\$s.3. Assign Event Group %1\$swith the appropriate rolesto a Tivoli Administrator.

Refer to the IBM Tivoli Monitoring forDatabases: Microsoft SQL Server User’sGuide for more information.


CTW0496I The task for event server %1\$scompleted.


CTW0497I IBM Tivoli Monitoring for Databases:Microsoft SQL Server is checkingexisting rule base %1\$s.


CTW0498I Creating event group %1\$s.


CTW0499I Copying script file %1\$s to %2\$s.


CTW0500I wmssqldispout [-p preface] [-f file]

Explanation: The wmssqldispout command is a Tivoliinternal command. It was invoked with incorrectsyntax. The correct syntax is summarized in this usagemessage.

Operator Response: If this command is being issuedfrom Tivoli supplied code, Contact Customer Support.

CTW0501E wmssqldispout must be run within aTivoli callback context.

Explanation: The wmssqldispout command is a Tivoliinternal command. It was invoked from an incorrectcontext.


CTW0502I wmssqlispconf [-N] message

Explanation: The wmssqldispconf command is aTivoli internal command. It was invoked with incorrectsyntax. The correct syntax is summarized in this usagemessage.


CTW0503E wmssqldispconf must be run within aTivoli callback context.

Explanation: The wmssqldispconf command is aTivoli internal command. It was invoked from anincorrect context.




CTW0504E Exception: %1$s

Explanation: The wmssqldispconf command is aTivoli internal command. An unexpected exceptionoccurred displaying the conformation dialog.


CTW0505E The wmssqldispout utility could notopen file ″%1$s″.

Explanation: The wmssqldispout utility was calledwith a request to print the contents of a file, but the filecould not be opened.

Operator Response: If the problem persists, contactCustomer Support.

CTW0506E wmregsvr -e Endpoint -s ServerName -hHome [-m ProxyNode] -u Username -pPassword -v v7|2k [-d] -r PolicyRegion-e Endpoint = the label of the Endpoint-s ServerName = the name of theMicrosoft SQL Server -h Home = thehome directory of the Microsoft SQLServer -m ProxyNode = the name of themanaged node to be used as the proxyhost -u Username = username used toaccess the Microsoft SQL Server -pPassword = password to use with thespecified username -v v7|2K = theversion of the server -d = use MicrosoftSQL Server account authentication, notWindows account authentication -rPolicyRegion = policy region in whichto register the server

Explanation: The syntax used for the wmregsvrcommand was not valid.

Operator Response: Run the wmregsvr commandagain using the correct syntax.

CTW0507E wmchregsvr [-h Home] [-u Username][-p Password] [-v v7|2k] [-d|-o]SQLServer -h Home = the homedirectory of the Microsoft SQL Server -uUsername = username used to access theMicrosoft SQL Server -p Password =password to use with the specifiedusername -v v7|2K = the version of theserver -d = use Microsoft SQL Serveraccount authentication -o = useWindows account authentication

Explanation: The syntax used for the wmchregsvrcommand was not valid.

Operator Response: Run the wmchregsvr commandagain using the correct syntax.

CTW0504E • CTW0507E


Appendix F. Accessibility

Accessibility features help a user who has a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in IBM Tivoli Monitoring for Databases: Microsoft SQL Serverenable users to:v Use assistive technologies such as screen-reader software and a digital speech

synthesizer to hear what is displayed on the screenv Operate specific or equivalent features using only the keyboardv Magnify what is displayed on the screen

In addition, the product documentation has been modified to include features toaid accessibility:v All documentation available in both HTML and convertible PDF formats to give

the maximum opportunity for users to apply screen-reader software.v All images provided with alternative text so that users of the documentation

with vision impairments can understand the contents of the images.

Using assistive technologiesAssistive technology products such as screen-readers, function with both thetext-based and graphical user interfaces found in IBM Tivoli Monitoring forDatabases: Microsoft SQL Server. Consult the assistive technology productdocumentation for specific information about using it to access command line orgraphical interfaces.

Additional accessibility features might be included as part of the user interface of aparticular IBM Tivoli Monitoring for Databases: Microsoft SQL Server component.Check with the individual component’s documentation for any additionalinformation about accessibility.

Magnifying what is displayed on the screenIn all components of IBM Tivoli Monitoring for Databases: Microsoft SQL Serverother than the Web Health Console, users can magnify the screens used by theproduct’s user interfaces using facilities provided by the operating systems onwhich the product is run. For example, in a Windows environment you can changethe screen settings to a lower resolution to enlarge the font sizes of the text on thescreen. Information about these facilities is provided in the relevant operatingsystem documentation.

Documentation in accessible formatsAll user documentation is provided in HTML format, which can be read directlyby assistive tools such as screen readers, or in convertible PDF format. ConvertiblePDF files are those that can be converted from PDF to HTML by the Adobe PDF toHTML converter. For information about converting PDF documents to HTML, referto the Adobe book Optimizing Adobe PDF Files for Accessibility

139

Using alternative textAll documentation images are provided with an alternative text that can be readby assistive tools such as screen readers.

Using Alternative Text


Appendix G. Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

141

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:


This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

IBM, the IBM logo, Tivoli, the Tivoli logo, and Tivoli Enterprise Console aretrademarks or registered trademarks of International Business MachinesCorporation in the United States, other countries, or both.

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

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

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

Microsoft SQL Server is a registered trademark of Microsoft Corporation.

Other company, product, and service names may be trademarks or service marksof others.

Appendix G. Notices 143

Index

Aaccessibility viiiAccessibility 139actions, recovery 7administrators

definition 9subscribing to notice groups

overview 17attributes

about 2authorization roles

for each procedure 107mssqlserver_dba 9mssqlserver_user 9Tivoli 9

Bbaroc file

Tivoli Enterprise Console event class 114books

accessing online viiifeedback on vionline viordering vi

built-in actionsdefined 7

Cclearing events, concept 5commands

mstartup 45wcprb 113wcrtprf 31wcrtprfmgr 31wcrtrb 113wdmdistrib 37wdmeditprf 77wdmlseng 123wdmtrceng 123wgetpr 20wimprbclass 114witmcollectsupportdata 125wloadrb 114wlookup 113wlseng 94wsetpm 31wsetpr 20wstartesvr 114wstopesvr 114wsub 32

conceptsclearing events 5events (clearing) 5

Configure TEC for Microsoft SQL Server taskrunning from CLI 111running from desktop 111using to configure the Tivoli Enterprise Console 110

customer support viii

cyclesdefined 2

Ddata logging

defined 6database

registeringoverview 26

shutting downdesktop 51overview 49

startingCLI 45overview 44

database propertiesDatabase Home Directory

Discovery default 23, 41Database Name

Discovery default 23, 41Database Version

Discovery default 23, 41dataless profile managers

icon 31subscribers 31

directory names, notation ixDiscovery

default database properties 24, 26Microsoft SQL Server Discovery managed resource 23overview 22running 24

distributed systemsdefined 1

Eendpoint

dataless 31definition 9subscribing 32

environment variables, notation ixevent monitors

defined 5Health Console 6Tivoli Business Systems Manager 6Tivoli Enterprise Console server 5

eventsdefined 4

events (clearing), concept 5events, Tivoli Enterprise Console

defined 109groups 110processing 109responding to 110sources 109viewing 110

145

GGathering Historical Data Warehouse 2

Hheartbeat function 2historical data

gathering 2holes

defined 3

IIBM Tivoli Monitoring

about 1overview 73

IBM Tivoli Monitoring for Databases: Microsoft SQL Serveroverview 1

indicationsdefined 3

Llogging (data)

defined 6

Mmanaged resources

defined 1Microsoft SQL Server Discovery 22specifying in a policy region

from the CLI 20from the desktop 21

manualsaccessing online viiifeedback on vionline viordering vi

messages 129Microsoft SQL Server Discovery managed resource 22monitoring profiles, defined 30monitors

Tivoli Business Systems Manager 6mssqlserver_dba authorization role 9mssqlserver_user authorization role 9

Nnotation

environment variables ixpath names ixtypeface ix

notice groupssubscribing administrators to

overview 17

Ooccurrences

defined 3online publications

accessing viiiordering publications vi, viii

overviewIBM Tivoli Monitoring 73

Pparameters

defined 7path names, notation ixpolicy region

adding managed resource types tofrom the CLI 20from the desktop 21

port requirements 125profile managers

creating 30dataless 31setting up 30subscribing endpoints 32

profilesadding custom resource models to 76creating 30defined 7monitoring 30

publicationsaccessing online viiifeedback on vionline viordering vi

Rrecovery actions 2recovery actions, defined 7registering a database, See database, registering 26resource model

troubleshooting 123resource models

adding to profiles 76defined 7distributed 93

resources, manageddefined 1

return code 123rules, Tivoli Enterprise Console

about 110

Sscheduling

defined 8jobs 38

serverproperties

viewing 41starting

from the desktop 46, 47, 51servers

discovering 22setup guidelines 11software support viiisubscribing

endpoint 32


Ttasks

Configure TEC for Microsoft SQL Server 110running from CLI 111running from desktop 111

Tivoli Management Framework 7thresholds

defined 8Tivoli Business Systems Manager

as monitor, concept 6Tivoli Enterprise Console 109

baroc file 114configuring 110

using commands 113using Configure TEC for Microsoft SQL Server

task 111console 110event

viewing 114event class

activating 114importing and compiling 114

event groupsdefinition 110

eventsdefined 109processing 109responding to 110sources 109viewing 110

overview 109rule base

loading 114rules

activating 114overview 110

Tivoli Management Frameworktasks, defined 7

Tivoli Sotware Information Center viiitrace log 126typeface conventions ix

Vvariables, notation for ix

Wwcprb command 113wcrtprf command 31wcrtprfmgr command 31wcrtrb command 113wdmdistrib command 37wdmeditprf command 77wdmlseng

Not Compiled 124wgetpr command 20wimprbclass command 114witmcollectsupportdata 125wloadrb command 114wlookup command 113wlseng command 94wruntask command 45wsetpm command 31wsetpr command 20wstartesvr command 114

wstopesvr command 114wsub command 32

Index 147

��

Printed in U.S.A.

SC23-4853-00

ibm tivoli monitoring for databases: microsoft sql server...

Documents