IBM Tivoli Monitoring for Messaging and Collaboration ...publib.boulder.ibm.com/tividd/td/ITMMC/SC32-0841-00/en_US/PDF/S… · Chapter 8. Working with health data 191 Understanding

IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino

User’s GuideVersion 5.1.0

SC32-0841-00

��


User’s GuideVersion 5.1.0

SC32-0841-00

��

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

First Edition (September 2002)

This edition applies to version 5.1.0 of IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino andto all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2002. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . vii

Tables . . . . . . . . . . . . . . . ix

About this guide . . . . . . . . . . . xiWho should read this guide . . . . . . . . . xiWhat this guide contains . . . . . . . . . . xiPublications . . . . . . . . . . . . . . xii

IBM Tivoli Monitoring for Messaging andCollaboration library . . . . . . . . . . xiiRelated publications . . . . . . . . . . xiiiAccessing softcopy publications . . . . . . xivUsing the guide online . . . . . . . . . xivViewing online help . . . . . . . . . . xvOrdering publications . . . . . . . . . . xvProviding feedback about publications . . . . xv

Accessibility . . . . . . . . . . . . . . xvContacting Customer Support . . . . . . . . xvConventions used in this guide . . . . . . . xvi

Typeface conventions . . . . . . . . . . xviTivoli command syntax . . . . . . . . . xvi

Chapter 1. Overview of IBM TivoliMonitoring for Messaging andCollaboration: Lotus Domino . . . . . 1Tivoli administrators. . . . . . . . . . . . 2Authorization roles . . . . . . . . . . . . 2Endpoints . . . . . . . . . . . . . . . 3User interface options . . . . . . . . . . . 3Management Console . . . . . . . . . . . 4Understanding IBM Tivoli Monitoring . . . . . 10

Chapter 2. Getting startedquick-reference guide for IBM TivoliMonitoring for Messaging andCollaboration: Lotus Domino . . . . . 19

Chapter 3. Setting up IBM TivoliMonitoring for Messaging andCollaboration: Lotus Domino . . . . . 21Starting the Tivoli environment . . . . . . . . 21Starting the Management Console . . . . . . . 23Setting authorization roles . . . . . . . . . 23Managing policy regions . . . . . . . . . . 26Managing resource types . . . . . . . . . . 29Subscribing to notice groups. . . . . . . . . 32Locating a Domino server and creating a DominoServer object . . . . . . . . . . . . . . 35Discovering and configuring multiple servers in theManagement Console . . . . . . . . . . . 44Deleting a Domino Server object . . . . . . . 49

Chapter 4. Working with resourcemodels. . . . . . . . . . . . . . . 53Overview of IBM Tivoli Monitoring . . . . . . 53Suggested guidelines for setting up your resourcemodels . . . . . . . . . . . . . . . . 54Creating profile managers and profiles . . . . . 55Subscribing resources to profile managers . . . . 62Adding a default resource model to a profile . . . 65Adding a custom resource model to a profile . . . 69Customizing indications . . . . . . . . . . 74Specifying tasks for an indication . . . . . . . 80Sending a notice when an event occurs . . . . . 83Customizing parameters . . . . . . . . . . 85Customizing a schedule for a resource model . . . 88Customizing data logging information . . . . . 93Managing profiles and resource models at endpoints 98Managing IBM Tivoli Monitoring gateways. . . . 99Determining which resource models have beendistributed to endpoints . . . . . . . . . . 99Determining which resource models are runningon endpoints . . . . . . . . . . . . . 100Distributing a profile from the desktop . . . . . 101Distributing profiles using MDist2 . . . . . . 105Rerunning a failed distribution . . . . . . . 107

Chapter 5. Working with LotusDomino Servers . . . . . . . . . . 111Checking server status . . . . . . . . . . 111Controlling a server . . . . . . . . . . . 113Controlling resource models for servers . . . . 117Running Domino tasks . . . . . . . . . . 119Viewing server properties . . . . . . . . . 121Editing server properties . . . . . . . . . 122Viewing Domino statistics . . . . . . . . . 126Entering a Domino remote console command . . 128Checking server health . . . . . . . . . . 130Viewing and searching log files . . . . . . . 132Checking for database corruption. . . . . . . 135Verifying mail files and checking Mail Waiting . . 137Viewing replication information . . . . . . . 139Checking for inactive users . . . . . . . . . 141Viewing and changing the Access Control List(ACL) . . . . . . . . . . . . . . . . 142

Chapter 6. Working with DominoPerformance Stations . . . . . . . . 147Authorization Roles for Domino PerformanceStations . . . . . . . . . . . . . . . 148Planning and implementation . . . . . . . . 148

System design guidelines . . . . . . . . 148Hardware, software, and network guidelines 150Guidelines for creating Domino PerformanceStations . . . . . . . . . . . . . . 150Probe Characteristics . . . . . . . . . . 151

© Copyright IBM Corp. 2002 iii

Configuring a Domino Performance Station . . . 152Configuring probes for a station . . . . . . . 156Configuring a resource model to monitor probes 158Deleting a Domino Performance Station . . . . 161Controlling a station . . . . . . . . . . . 161Controlling resource models for stations . . . . 163Deleting probes . . . . . . . . . . . . 164Resetting probes . . . . . . . . . . . . 165Running a probe one time . . . . . . . . . 166Checking probe status . . . . . . . . . . 168Checking the integrity of a performance station 169

Chapter 7. Working with tasks andjobs . . . . . . . . . . . . . . . 171Running tasks . . . . . . . . . . . . . 172Customizing a task . . . . . . . . . . . 176Creating jobs . . . . . . . . . . . . . 180Running jobs . . . . . . . . . . . . . 184Scheduling jobs. . . . . . . . . . . . . 185

Chapter 8. Working with health data 191Understanding Resource Health . . . . . . . 191Connecting the IBM Tivoli Monitoring Web HealthConsole . . . . . . . . . . . . . . . 192Management Console. . . . . . . . . . . 192Checking the health of resources as real-time data 193Customizing data views and setting preferences 196Saving, exporting, and printing data and reports 203Viewing historical data . . . . . . . . . . 203

Chapter 9. Setting up the TivoliEnterprise Console for eventcorrelation . . . . . . . . . . . . 207Overview of the Tivoli Enterprise Console. . . . 207Configuring remote event correlation for thisproduct . . . . . . . . . . . . . . . 209Configuring local event correlation for this product 212Customizing the Events4 Profile for local eventcorrelation . . . . . . . . . . . . . . 214Controlling the local rule engine . . . . . . . 216Viewing events . . . . . . . . . . . . . 218Lists of event classes . . . . . . . . . . . 219

Chapter 10. Integrating with TivoliBusiness Systems Manager . . . . . 225Understanding Tivoli Business Systems Manager 225Prerequisites. . . . . . . . . . . . . . 226Integrating with Tivoli Business Systems Manager 226Discovering resources for Tivoli Business SystemsManager . . . . . . . . . . . . . . . 227

Objective . . . . . . . . . . . . . . 227Background information. . . . . . . . . 228Required authorization role. . . . . . . . 228Before you begin . . . . . . . . . . . 228When you finish . . . . . . . . . . . 228Procedure . . . . . . . . . . . . . 228

Configuring the Tivoli Enterprise Console eventserver . . . . . . . . . . . . . . . . 228

Objective . . . . . . . . . . . . . . 228

Background information. . . . . . . . . 229Required authorization role. . . . . . . . 229Before you begin . . . . . . . . . . . 229When you finish . . . . . . . . . . . 229Procedure . . . . . . . . . . . . . 229

Working with Tivoli Business Systems Manager 229Uninstalling IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino integration fromTivoli Business Systems Manager . . . . . . . 229

Chapter 11. Enabling Tivoli EnterpriseData Warehouse . . . . . . . . . . 231Overview of Tivoli Enterprise Data Warehouse . . 231

Control server . . . . . . . . . . . . 231Central data warehouse . . . . . . . . . 232Data marts . . . . . . . . . . . . . 232Report interface . . . . . . . . . . . 233

Working with users and user groups . . . . . 233About users and user groups . . . . . . . 233The Tivoli Enterprise Data Warehouseauthorization roles . . . . . . . . . . 233

Accessing the IBM Console . . . . . . . . . 234Creating an IBM Console user . . . . . . . . 235Assigning authorization roles to a user . . . . . 235Creating a user group . . . . . . . . . . 236Assigning users to a user group . . . . . . . 236Assigning user groups to a data mart . . . . . 237Managing Tivoli Enterprise Data Warehousereports . . . . . . . . . . . . . . . 238Running reports . . . . . . . . . . . . 238Scheduling reports to run automatically . . . . 239Modifying default settings for reports . . . . . 239Creating reports . . . . . . . . . . . . 240Creating a Many Measurements Versus TimeDomino-specific report . . . . . . . . . . 241IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino data marts andreports . . . . . . . . . . . . . . . 244

Chapter 12. Backing up and restoringDomino databases . . . . . . . . . 249Configuring Tivoli Data Protection for LotusDomino . . . . . . . . . . . . . . . 249Backing up Domino databases. . . . . . . . 252Restoring Domino databases . . . . . . . . 254Activating Domino databases . . . . . . . . 256Archiving transaction log files . . . . . . . . 258Viewing archived transaction log files . . . . . 260Inactivating transaction log files . . . . . . . 262

Appendix A. Authorization roles quickreference . . . . . . . . . . . . . 265

Appendix B. Problem determination 269Frequently asked questions . . . . . . . . . 273Domino server console messages . . . . . . . 273

iv IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

IBM Tivoli Monitoring for Messaging andCollaboration: Lotus DominoIBM Tivoli Monitoringfor Messaging and Collaboration: Lotus Dominomessages . . . . . . . . . . . . . . . 274Testing endpoint connectivity . . . . . . . . 275

Appendix C. Messages . . . . . . . 277

Appendix D. Accessibility . . . . . . 309

Using assistive technologies . . . . . . . . 309Magnifying what is displayed on the screen . . . 309Documentation in accessible formats . . . . . 309Using alternative text. . . . . . . . . . . 309

Appendix E. Notices . . . . . . . . 311Trademarks . . . . . . . . . . . . . . 313

Index . . . . . . . . . . . . . . . 315

Contents v

vi IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

Figures

1. Status and Operations tab window of theManagement Console . . . . . . . . . 5

2. Events tab window of the Management Console 63. Backup and Restore tab with subtab windows

of the Management Console . . . . . . . 74. Performance tab with the Probes subtab

window of the Management Console . . . . 85. Configuration tab with Servers subtab window

of the Management Console . . . . . . . 86. Configuration tab with Profiles subtab and

Profiles subtab window of the ManagementConsole . . . . . . . . . . . . . . 9

7. Configuration tab with Profiles subtab andSubscribers subtab window of the ManagementConsole . . . . . . . . . . . . . . 9

8. Configuration tab with Preferences subtabwindow of the Management Console . . . . 10

9. Administrators dialog box (Desktop) . . . . 2410. Set Resource Roles dialog box (Desktop) 2511. Create Policy Region dialog box (Desktop) 2812. Create Policy Region dialog box (Management

Console) . . . . . . . . . . . . . 2813. Delete Policy Region dialog box (Management

Console) . . . . . . . . . . . . . 2914. Set Managed Resources dialog box (Desktop) 3115. Set Notice Groups dialog box (Desktop) 3316. Edit Subscriber List dialog box (Management

Console) . . . . . . . . . . . . . 3517. Create Domino Server dialog box (Desktop) 4018. Configure Source Server dialog box

(Management Console). . . . . . . . . 4119. Create Domino Server dialog box

(Management Console). . . . . . . . . 4220. Create Domino Server dialog box Basics tab

(Management Console). . . . . . . . . 4221. Create Domino Server dialog box Backup tab

(Management Console). . . . . . . . . 4322. Edit dialog box Basics tab (Management

Console) . . . . . . . . . . . . . 4723. Configure dialog box (Management Console) 4824. Delete Objects? dialog box (Desktop). . . . 5125. Unconfigure dialog box (Management

Console) . . . . . . . . . . . . . 5126. Policy region icon . . . . . . . . . . 5727. Create Profile Manager dialog box (Desktop) 5828. Dataless profile manager icon (Desktop) 5829. Profile Manager dialog box (Desktop) . . . 5930. Create Profile dialog box (Desktop) . . . . 6031. Create Profile Manager dialog box

(Management Console). . . . . . . . . 6032. Add Profile dialog box (Management Console) 6133. Delete Profile dialog box (Management

Console) . . . . . . . . . . . . . 6234. Delete Profile Manager dialog box

(Management Console). . . . . . . . . 6235. Subscribers dialog box (Desktop) . . . . . 63

36. Edit Subscriber List dialog box (ManagementConsole) . . . . . . . . . . . . . 64

37. IBM Tivoli Monitoring Profile dialog box(Desktop) . . . . . . . . . . . . . 66

38. Add Default Models to Profile dialog box(Desktop) . . . . . . . . . . . . . 67

39. Configuration window Profiles tab(Management Console). . . . . . . . . 68

40. Add Resource Model window (ManagementConsole) . . . . . . . . . . . . . 69

41. Add Resource Models to Profile dialog box(Desktop) . . . . . . . . . . . . . 71

42. Add Resource Model window with Basics tabdialog box (Management Console) . . . . . 73

43. Edit Resource Model dialog box (Desktop) 7644. Indications and Actions dialog box (Desktop) 7745. Edit Resource Model window (Management

Console) . . . . . . . . . . . . . 7846. Indications tab dialog box (Management

Console) . . . . . . . . . . . . . 7947. Severity drop-down list (Management

Console) . . . . . . . . . . . . . 8048. Tasks dialog box (Desktop) . . . . . . . 8249. Task Configuration dialog box (Management

Console) . . . . . . . . . . . . . 8350. Parameters dialog box (Desktop) . . . . . 8751. Parameters tab dialog box (Management

Console) . . . . . . . . . . . . . 8852. Scheduling dialog box (Desktop) . . . . . 9053. Schedule tab dialog box for customizing a

resource model (Management Console) . . . 9254. Logging dialog box (Desktop) . . . . . . 9555. Logging tab dialog box (Management Console) 9756. Distribute Profile dialog box (Desktop) 10257. Distribute dialog box (Management Console) 10458. Server status icons: server up and server

down (Desktop). . . . . . . . . . . 11259. Server icon example (Management Console) 11360. Start/Stop/Recycle Server dialog box

(Management Console) . . . . . . . . 11761. Start/Stop Resource Model pop-up menu for

a server (Management Console) . . . . . 11962. Start/Stop Domino Task dialog box

(Management Console) . . . . . . . . 12063. Server properties dialog box (Management

Console) . . . . . . . . . . . . . 12164. Domino Server Properties dialog box

(Desktop) . . . . . . . . . . . . . 12365. Edit dialog box (Management Console) 12466. Configure dialog box (Management Console) 12667. Show Server Statistics dialog box

(Management Console) . . . . . . . . 12868. Remote Console dialog box (Management

Console) . . . . . . . . . . . . . 13069. Check Health dialog box (Management

Console) . . . . . . . . . . . . . 132

© Copyright IBM Corp. 2002 vii

70. Search Log File dialog box (ManagementConsole) . . . . . . . . . . . . . 134

71. Check Database Corruption dialog box(Management Console) . . . . . . . . 136

72. Mail dialog box (Management Console) 13873. Check Replication dialog box (Management

Console) . . . . . . . . . . . . . 14074. Check Inactive Users dialog box

(Management Console) . . . . . . . . 14275. ACL dialog box (Management Console) 14476. Create a Domino Performance Station dialog

box (Desktop) . . . . . . . . . . . 15377. Create dialog box (Management Console) 15478. Tested Servers buttons in the Add Server

dialog box (Management Console) . . . . 15579. Add Probe dialog box (Management Console) 15780. Edit Probe dialog box (Management Console) 15781. Start/Stop/Reboot dialog box (Management

Console) . . . . . . . . . . . . . 16382. Start/Stop Resource Model pop-up menu for

a station (Management Console) . . . . . 16483. Probe Once dialog box (Management

Console) . . . . . . . . . . . . . 16784. Probe Status dialog box (Management

Console) . . . . . . . . . . . . . 16985. Integrity dialog box (Management Console) 17086. Task Library window (Desktop) . . . . . 17387. Execute Task dialog box (Desktop) . . . . 17488. Destination for Task Output dialog box

(Desktop) . . . . . . . . . . . . . 17589. Dialog box for configuring task arguments

(Desktop) . . . . . . . . . . . . . 17690. Task Library window (Desktop) . . . . . 17791. Execute Task dialog box (Desktop) . . . . 17892. Dialog box for configuring task arguments

(Desktop) . . . . . . . . . . . . . 178

93. Dialog box for saving arguments (Desktop) 17994. Create Job dialog box (Desktop) . . . . . 18295. Destination for Task Output dialog box

(Desktop) . . . . . . . . . . . . . 18396. Add Scheduled Job dialog box (Desktop) 18697. Set Retry/Cancel Restrictions Options dialog

box (Desktop) . . . . . . . . . . . 18898. Health window for Lotus Domino Servers

(Management Console) . . . . . . . . 19499. Health window for Domino Performance

Stations (Management Console) . . . . . 195100. Filter menu (Management Console) . . . . 196101. Edit Filter dialog box (Management Console) 196102. Data view in bar chart format (Management

Console) . . . . . . . . . . . . . 197103. Data view in table format (Management

Console) . . . . . . . . . . . . . 198104. Statistics area in text table view (Management

Console) . . . . . . . . . . . . . 202105. Bar chart . . . . . . . . . . . . . 242106. Line chart . . . . . . . . . . . . . 243107. Backup and Restore tab Backup subtab

Options (Management Console) . . . . . 253108. Backup and Restore tab Restore subtab

Options (Management Console) . . . . . 256109. Backup and Restore tab Activate subtab

Options (Management Console) . . . . . 258110. Archive Logs dialog box (Management

Console) . . . . . . . . . . . . . 260111. View Log Archives dialog box (Management

Console) . . . . . . . . . . . . . 261112. Inactivate Log Archives dialog box

(Management Console) . . . . . . . . 263

viii IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

Tables

1. Authorization roles for the ManagementConsole . . . . . . . . . . . . . . 2

2. Counting occurrences . . . . . . . . . 133. High CPU Usage percentages over 12 cycles:

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

health . . . . . . . . . . . . . . 155. Quick reference for getting started with IBM

Tivoli Monitoring for Messaging andCollaboration: Lotus Domino. . . . . . . 19

6. Goals and where to find procedures for settingup the software . . . . . . . . . . . 21

7. Domino server properties . . . . . . . . 368. Goals and where to find procedures for

working with IBM Tivoli Monitoring . . . . 549. Profile managers and their default resource

models . . . . . . . . . . . . . . 5610. Goals and where to find procedures for

working with Lotus Domino Servers . . . . 11111. Goals and where to find procedures for

working with Domino Performance Stations . 14712. Goals and where to find procedures for

working with tasks and jobs . . . . . . 17113. Health determination example . . . . . . 19214. Goals and where to find procedures for

working with health data . . . . . . . 192

15. Goals and where to find procedures forsetting up the Tivoli Enterprise Console. . . 207

16. Goals and where to find procedures forintegrating with Tivoli Business SystemsManager . . . . . . . . . . . . . 225

17. Goals and where to find procedures forenabling IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Dominofor Tivoli Enterprise Data Warehouse . . . 234

18. Default time filter names and values 24019. Tivoli Enterprise Data Warehouse reports to

resource model mapping. . . . . . . . 24720. Goals and where to find procedures for

backing up and restoring databases . . . . 24921. Descriptions of configuration attributes for

Tivoli Data Protection for Lotus Domino . . 25022. Authorization roles and interfaces for

functions . . . . . . . . . . . . . 26523. Symptoms and suggested actions for

recovering from common problems . . . . 26924. Frequently asked questions related to

problem determination . . . . . . . . 27325. Domino server console messages and

workarounds . . . . . . . . . . . 27326. Messages and suggested actions . . . . . 274

© Copyright IBM Corp. 2002 ix

x IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

About this guide

IBM® Tivoli® Monitoring for Messaging and Collaboration provides the ability tomanage and monitor Domino resources. IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide describes in detail the tasks, monitors,and commands used in the procedures in this guide.

Who should read this guideThis guide is for system managers who use Domino to manage networkeddatabases.

Readers should be familiar with the following:v UNIX® or Windows NT® operating systemsv Domino administration

What this guide containsThis guide contains the following sections:v Chapter 1, “Overview of IBM Tivoli Monitoring for Messaging and

Collaboration: Lotus Domino”Provides an overview of the following aspects of the software: operations, Tivoliadministrators, authorization roles, endpoints, user interface options, tabs in theManagement Console, and resource models.

v Chapter 2, “Getting started quick-reference guide for IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino”Provides guidelines for setting up the product, including preparing for installingthe software; setting up administrators, managed resources, and profiles forDomino server monitors and performance station probes; connecting to theTivoli Enterprise Console® and Tivoli Business Systems Manager®; setting uptasks and jobs; creating reports in Tivoli Enterprise Data Warehouse; and backingup and restoring databases

v Chapter 3, “Setting up IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino”Describes how to set up the software, including setting up the Tivolienvironment and the Management Console, creating policy regions, adding andremoving managed resource types, subscribing to notice groups, and configuringLotus Domino Server objects.

v Chapter 4, “Working with resource models”Describes how to use resource models to monitor your managed resources.

v Chapter 5, “Working with Lotus Domino Servers”Describes how to manage Lotus Domino Servers in the Tivoli environment byperforming such activities as checking server status, starting and stopping tasks,and determining whether a server replicated according schedule.

v Chapter 6, “Working with Domino Performance Stations”Describes how to configure probing of Lotus Notes clients to reveal theperformance of a system from the perspective of the Notes user and to confirmcompliance with service level agreements (SLAs).

v Chapter 7, “Working with tasks and jobs”

© Copyright IBM Corp. 2002 xi

Describes how to create, configure, and run Tivoli tasks to automatemanagement activities that you perform frequently.

v Chapter 8, “Working with health data”Describes how to use the Web Health Console and the Management Console towork with health data.

v Chapter 9, “Setting up the Tivoli Enterprise Console for event correlation”Provides information about setting up Tivoli Enterprise Console (TEC) for usewith IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino.

v Chapter 10, “Integrating with Tivoli Business Systems Manager”Provides information about setting up Tivoli Business Systems Manager andhow to use it to manage Lotus Domino resources.

v Chapter 11, “Enabling Tivoli Enterprise Data Warehouse”Provides information about configuring Tivoli Enterprise Data Warehouse andhow to use it to create and access application reports from various Tivoli andcustomer applications.

v Chapter 12, “Backing up and restoring Domino databases”Provides information about using Tivoli Data Protection to back up LotusDomino databases.

v Appendix A, “Authorization roles quick reference”Provides a quick reference table for authorization roles relevant to performingoperations with IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino.

v Appendix B, “Problem determination”Provides information about common problems in using IBM Tivoli Monitoringfor Messaging and Collaboration: Lotus Domino.

v Appendix C, “Messages”Contains a list of messages and an explanation of each message.

v Appendix D, “Accessibility”Describes the accessibility features that help a user who has a physical disability,such as restricted mobility or limited vision, to use software productssuccessfully.

v Appendix E, “Notices”Contains copyright and trademark information referenced in this guide.

PublicationsThis section lists publications in the IBM Tivoli Monitoring for Messaging andCollaboration library and any other related documents. It also describes how toaccess Tivoli publications online, how to order Tivoli publications, and how tosubmit comments on Tivoli publications.

IBM Tivoli Monitoring for Messaging and Collaboration libraryThe following documents are available in the IBM Tivoli Monitoring for Messagingand Collaboration library:v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: Lotus Domino

User’s Guide, SC32-0841-00Provides information about how to use IBM Tivoli Monitoring for Messagingand Collaboration to manage Domino resources.

v IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide, SC32-0840-00

xii IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

Provides detailed information about Domino resource models, tasks, andcommands.

v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: Installation andSetup Guide, GC32-0839-00Provides instructions for installing IBM Tivoli Monitoring for Messaging andCollaboration and setting it up to manage Domino resources.

v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: Release Notes,GI11-0917-00Describes product features and provides information about the latest changes tothe installation requirements and procedures.

v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: Limitations andWorkarounds Supplement, SC23-4806-00 Provides the latest information aboutknown product limitations and workarounds. To ensure that the information isthe latest available, this document is provided only on the Web, where it isupdated on a regular basis. You can access the Limitations and Workaroundsdocument through the IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino link on the Tivoli Information Center Web site:

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

Related publicationsThe following documents provide other useful information:v IBM Tivoli Monitoring: Workbench User’s Guide, SH19-4571

Describes how to use the IBM Tivoli Monitoring Workbench to create newresource models and to modify existing ones.

v IBM Tivoli Monitoring, Version 5.1.0: User’s Guide, SH19-4569Describes how to use the IBM Tivoli Monitoring user interface.

v IBM Tivoli Monitoring, Version 5.1.0: Resource Model Reference, SH19-4570Describes the resource models that come with IBM Tivoli Monitoring software.

v Tivoli Management Framework, Version 3.7.1: User’s Guide , GC31-8433-04Describes the Tivoli environment, including profiles and profile management.

v Tivoli Management Framework, Version 3.7.1: Reference Manual, SC31-8434-04Provides detailed information about Tivoli commands.

v Tivoli Enterprise, Version 3.7.1: Installation Guide, GC32-0395-01Provides information and procedures for installing and upgrading TivoliManagement Framework resources (Tivoli management region server, managednodes, gateways, and endpoints), and provides the procedures for installing andupgrading Tivoli Enterprise products.

v Tivoli Management Framework, Version 3.7.1: Planning for Deployment Guide,GC32-0393-01Explains how to plan for deploying your Tivoli environment, and describesTivoli Management Framework and its services.

v Tivoli Data Protection, Version 1.1.2: Installation and User’s Guide, GC26-7320-02, forWindows NT or SH26-4088-03 for UNIX Operating SystemsDescribes how to install and configure Tivoli Data Protection.

v Tivoli Enterprise Console User’s Guide, Version 3.7.1, GC32-0667-01Describes how to use the Tivoli Enterprise Console®.

v Tivoli Enterprise Console Reference Manual, Version 3.7.1, GC32-0666-01

About this guide xiii

v Tivoli Enterprise Console, Version 3.7: Rule Builder’s Guide, GC32-0669-00Provides information about developing rules for managing events with TivoliEnterprise Console with a text editor and a graphical rule builder.

v TME 10 Software Installation Service User’s Guide, sis36gaDescribes how to use the Tivoli Software Installation Service (SIS) to installTivoli products.

v Tivoli Business Systems Manager, Version 1.5: User’s Guide

Describes how to use the Tivoli Business Systems Manager product.v Tivoli Business Systems Manager Console, Version 1.5: User’s Guide

Describes how to use the Tivoli Business Systems Manager console.v Tivoli Enterprise Data Warehouse documentation

Describes how to use Tivoli Enterprise Data Warehouse to compile historicaldata to monitor your system and to help you make strategic managementdecisions regarding your network.

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:

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

Accessing softcopy publicationsThe publications for this product are available in PDF and HTML formats throughthe following media:v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0:

Documentation CD, LK3T-8516–00The Documentation CD contains all of the English language publications for thisproduct, except for the Web-only Limitations and Workarounds supplements. Toaccess the publications, use a Web browser to open the start.html file, which islocated in the root directory of the CD.

v IBM Tivoli Monitoring for Messaging and Collaboration, Version 5.1.0: NLSDocumentation CD, LK3T-8601–00The NLS (national language support) Documentation CD contains both Englishand non-English language publications for this product, except for the Web-onlyLimitations and Workarounds supplements. To access the publications, use aWeb browser to open the start.html file, which is located in the root directory ofthe CD.

v Tivoli Information CenterIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Information Center Website. The Tivoli Information Center is located at the following Web address:http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.htmlClick the IBM Tivoli Monitoring for Messaging and Collaboration link to accessthe product library.

Using the guide onlineThis document is available on the IBM Tivoli Monitoring for Messaging andCollaboration, Version 5.1.0: Documentation CD, LK3T-8516-00 in PDF and HTMLformats. Refer to the readme.txt file on the CD for instructions on downloading theAcrobat Reader, Version 3.0 or later, to view, save, and print the manual.

xiv IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

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

Use your HTML browser to open the start.html file on the CD to access the .htmldocumentation files. Every navigation page also includes a link at the bottom todownload the Acrobat reader for viewing, saving, and printing the files.

Viewing online helpOnline help is available in several forms:v Desktop — Access online help by clicking Help in dialog boxes.v Commands — You can display command syntax and parameter information for

command line interface (CLI) commands by typing the name of the command ata command prompt and pressing the Enter key.

v Management Console — Access help by pressing the F1 key in the ManagementConsole.

Ordering publicationsYou can order hardcopy publications online from the IBM Publications Center Website:

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.tivoli.com/inside/store/lit_order.html

Providing feedback about publicationsIf you have comments or suggestions about Tivoli products and documentation,send an e-mail to [email protected] or complete the customer feedback survey atthe following Web site:

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

AccessibilityAccessibility features help a user who has 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 Appendix D, “Accessibility” on page 309 in thisguide.

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact IBM CustomerSupport for Tivoli products. See the Tivoli Customer Support Handbook at thefollowing Web site:

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

About this guide xv

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


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

The handbook provides information about how to contact Customer 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 What information you should gather before contacting Customer Support

Note: For Tivoli NetView for OS/390 customers only, additional support isavailable on the NETVIEW CFORUM (Customer Forum) through theIBMLink system. NetView developers monitor this forum, answer questions,and provide guidance. When you find a problem with the code, open anofficial problem management record (PMR) to get resolution.

Conventions used in this guideThis guide uses several conventions for special terms, actions and for commandsyntax.

Typeface conventionsThis guide uses the following typeface conventions:

Bold Commands, keywords, file names, authorization roles, URLs, orother information that you must use literally are displayed likethis, in bold. Names of windows, dialogs, and other controls arealso displayed like this, in bold.

Italic Variables and values that you must provide are displayed like this,in italic type. Words and phrases that are emphasized are alsodisplayed like this, in italic type.

Monospace Code examples, output, and system messages are displayed likethis, in a monospace font.

Tivoli command syntaxThe commands in this book use the following special characters to define Tivolicommand syntax:

< > Indicates that the text enclosed in the angle brackets is a variable that yousupply.

[ ] Identifies optional elements. Elements that do not have brackets aroundthem are required.

... Indicates you can specify multiple values for the previous element.Separate multiple values by a space, unless the command informationspecifies differently.

If the ellipsis for an element follows a closing bracket ( ] ), use the syntaxwithin the brackets to specify multiple values. For example, to specify twoadministrators for the option [–a admin]..., use –a admin1 –a admin2.

If the ellipsis for an element is within brackets, use the syntax of the lastelement to specify multiple values. For example, to specify two hosts forthe option [–h host...], use –h host1 host2.

| Indicates mutually exclusive information, meaning you can use the elementon either the left or right of the vertical bar, but not both.

xvi IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

{ } Delimits a set of mutually exclusive elements when a command requiresone of them, but not multiple elements. Brackets ([ ]) are around elementsthat are optional.

\ A backslash indicates that a command continues on the next line.

In addition to the special characters, Tivoli command syntax uses the typefaceconventions described in the Preface of this guide.

The following examples illustrate the typeface conventions used in Tivolicommand syntax:v wcrtpr [–a admin]... [–s region] [–m resource]... name

The name argument is the only required element for the wcrtpr command. Thebrackets around the options indicate that they are optional. The ellipsis after the–a admin option means that you can specify multiple administrators multipletimes. The ellipsis after the –m resource option means that you can specifymultiple resources multiple times.

v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}The –f, –i, and object elements are mutually exclusive. The braces that surroundthe –f, –i, and object elements indicate that you are including required elements.If you specify the object argument, you can specify more than one object.

When you reference an object in a command issued from the command line, thereference is not an absolute object reference like those used in programming.Instead, the reference is a user-friendly name. This user-friendly name derives froma name given to the object by the user of the application, such as when creating apolicy region.

About this guide xvii

xviii IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

Chapter 1. Overview of IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Dominocomplements existing Lotus® Domino™ tools and adds features for managing largenumbers of Domino servers and databases in a distributed environment. Itprovides the ability to manage and monitor Domino resources by providingextensions to the Tivoli Management Framework, IBM Tivoli Monitoring, and theTivoli Enterprise Console. It includes Domino-specific task libraries.

Use IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino toperform the following operations:v Track the availability and performance of Domino servers and databases with

resource models for this product.v Alert administrators to Domino performance problems and failures using

pop-up message boxes, logs, reports, graphs, and other tools.v Manage and monitor servers in functional groups by assigning a Server Type

property (such as mail, Web, database, or newsgroup) to a server.v Automate the following configuration and management operations for Domino

servers through a graphical user interface:– Check the status of servers and perform operations on those servers (for

example, checking health or checking for database corruption).– Generate and distribute graphs and tabular reports of monitoring data for a

server or for groups of servers.– Back up, restore, and activate databases and log files.– Filter significant event information to send to the Tivoli Enterprise Console.– Probe server performance from the perspective of a Lotus Notes client.– Configure servers to work with this product.– Organize servers in policy regions and group those servers in profile

managers.– Configure and run resource models, and collect data from those resource

models.v Monitor routine events, such as logical disk full, replication failures, Domino

service disruptions, database corruption or fragmentation, and hardware failures,so that you can manage them by standard methods.

v Determine the severity and relationship of events by using the Tivoli EnterpriseConsole to provide event correlation. You can define rules for automatedresponses, such as running a corrective task.

v Consolidate, transform, and display historical data from Domino servers in avariety of formats by using the Tivoli Enterprise Data Warehouse.

v Make secure backups and manage backup devices by using the Tivoli DataProtection (TDP) backup tool.

© Copyright IBM Corp. 2002 1

Tivoli administratorsDomino administrators are known in the Tivoli environment as Tivoliadministrators. Administrators are system or Tivoli administrators who have theauthorization to manage Domino servers in policy regions. After the product isinstalled, you can assign authorization roles to other administrators that define theoperations they can perform. Each administrator or group of administrators isrepresented by an icon on the Tivoli desktop.

This product fully integrates into Tivoli security. To perform administrationfunctions, administrators must have authorization roles for both this product andthe Tivoli management environment.

Authorization rolesTivoli authorization roles determine the range of actions an administrator canperform. You assign roles to administrators so they can perform server or Dominomanagement tasks. A role might cover the entire Tivoli management region or aspecific set of resources, such as those contained in a policy region. super, senior,admin, and user are examples of authorization roles provided in Tivoli software.See the Tivoli Management Framework, Version 3.7.1: User’s Guide for descriptions ofthese roles.

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino providesthe following additional authorization roles:

Domino_AdminPerforms all operations required for any operation that involves creatingand modifying servers or monitors.

Domino_UserHas read-only access to a limited set of functions required for viewingserver properties, status, and health.

Domino_DPS_AdminPerforms all operations for Domino Performance Stations, such as creatingand modifying performance stations.

Domino_DPS_UserHas read-only access to a limited set of functions for Domino PerformanceStations, such as running a probe one time.

Domino_TDP_AdminPerforms all operations for Tivoli Data Protection, such as backing up orrestoring databases.

Domino_TDP_UserHas read-only access to a limited set of functions for Tivoli DataProtection, such as querying a transaction log.

Table 1 contains the administrator roles that are the minimum requirements forlogging onto the Management Console, which is the graphical user interface forIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino:

Table 1. Authorization roles for the Management Console

Role Level

user Tivoli management region

Domino_User Messaging and Collaboration policy region

2 IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino: User’s Guide

To work with IBM Tivoli Monitoring profiles, an administrator must have either anadmin, senior, or super role for the policy region that contains the profile managerof the IBM Tivoli Monitoring profile. At least one administrator must have one ofthe listed roles for the Messaging and Collaboration policy region to work withthe default set of profile managers and profiles.

By default, the Management Console displays all objects associated with IBMTivoli Monitoring for Messaging and Collaboration. Depending on anadministrator’s assigned roles, an administrator may or may not be able to interactwith the displayed objects. Any attempt to operate with an object for which therequired Tivoli management region role has not been assigned results in an errormessage stating that the administrator does not have sufficient roles to perform theoperation.

EndpointsA Tivoli endpoint enables Tivoli management products to manage resources on acomputer system. You manage endpoints by subscribing them to profiles withinprofile managers, for example, when you set up subscriptions for the distributionof monitoring profiles.

This software provides the following types of endpoints:v DominoPerformanceStationv LotusDominoServer

User interface optionsIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino providesthe following user interfaces that you can use to manage and monitor LotusDomino Servers and Domino Performance Stations:v The Management Console is an interface that enables monitoring and managing

of Domino servers.v The Tivoli desktop is the traditional Tivoli graphical user interface that enables

monitoring and managing of Domino servers.v The command line interface (CLI) is useful in the following circumstances:

– Accessing the Tivoli environment through a modem when you do not haveaccess to a graphical user interface.

– Grouping multiple operations inside a single shell script.– Working on a keyboard without using a mouse or other pointing device.

You can perform many of the procedures in this guide through more than one ofthese interfaces. For each procedure in this guide, the procedure section containsthe steps for using each applicable interface.

In addition to these three interfaces, you can access the Web Health Consoleinterface to monitor the status and health of endpoints in both real-time andhistorical perspectives. See Appendix A, “Authorization roles quick reference” onpage 265 for a summary of the management operations that you can perform inthe various interfaces (Management Console, Tivoli desktop, command line, WebHealth Console) and by running tasks.

Chapter 1. Overview of IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino 3

This product also comes with IBM Tivoli Monitoring Workbench, a developmentenvironment for users who want to move beyond the resource models that comewith this product. In the workbench you customize existing resource models ordesign new resource models.

Management ConsoleThe Management Console is designed for the Domino administrator. It providestools to manage and monitor the Domino server environment. The ManagementConsole does not require additional Tivoli software on the machine that is runningthe Management Console. The Domino administrator does not need to learn Tivoliconcepts.

Note: When you access a dialog box in the Management Console you can press<F1> to see help information for that dialog box.

You can access the Management Console using the Internet Explorer Web browseror Netscape Web browser. On computers where you run the Management Console,set the screen resolution to 1024 by 768 or above. This resolution setting enablesthe user interface to display all available options for dialog boxes that containmany options.

The Login Panel controls access to the Management Console. You must providethe following information:

HostnameType a host name in the format hostname:port, where hostname is thename of the Tivoli management region host and port is the port numberon which the Tivoli management region listens for connections. If youconfigured the Tivoli management region with the default port of 94, onlythe hostname portion is necessary.

User Type a valid login ID for a Tivoli Administrator. Your session has allauthorization roles for that Administrator. This login ID must be a validoperating system user ID on the host specified in the Hostname field.

PasswordType the password associated with the user specified in the User field.

When you complete all three fields, the Login option becomes enabled. ClickLogin to log in to the specified host using the specified user and password. If anerror occurs during login, a message is displayed below the Password field.Correct the problem and retry the login.

The Management Console contains the following four or five tabs positionedhorizontally across the top:v Status and Operationsv Events (if Tivoli Enterprise Console is installed)v Backup and Restorev Performancev Configuration

Subtabs appear horizontally under some of these five top tabs depending on whichtab is selected.

Under the tabs or subtabs, the following three sections appear vertically from leftto right:


v Navigation treev Data specific to the selected resourcev Tools specific to the main tab

The contents of these three vertical sections change depending on which of the fivetabs is selected:v The navigation tree in the left column contains either a list of Lotus Domino

Server objects or a list of Domino Performance Station objects.v Data in the center pane provides information about the performance station or

server selected in the navigation tree.v Two Tools drop-down menus in the right column contain either Servers and

Diagnostics tools, or Stations and Diagnostics tools. These menus are open bydefault. Collapse any of these menus by clicking the menu name.

The Status and Operations tab window (Figure 1) provides a graphicalrepresentation of the current state of the Domino server environment and providestools for interacting with servers and diagnosing problems on all servers in theenvironment.

The Events tab window (Figure 2 on page 6) lists enterprise events that can affectthe Domino server environment so you can respond to those events in a timelymanner. Use the Events tab window to view the Tivoli Enterprise Console. To

Figure 1. Status and Operations tab window of the Management Console


access the Events tab window, you must install the Tivoli Enterprise Console inyour environment. The Tivoli Enterprise Console provides event correlation todetermine the severity and relationship of events and define rules for automatedresponses, such as running a corrective task.

The Backup and Restore tab provides a consolidated view for remotely backingup, restoring, and activating Domino server databases through three subtabwindows (Figure 3 on page 7): Backup, Restore, and Activate. The tools menuassists with managing transaction logs on servers where transaction logging isactivated. To use the Backup and Restore tab tools, you must install the TivoliStorage Manager (TSM) and Tivoli Data Protection (TDP) applications for Domino.

Figure 2. Events tab window of the Management Console


The Performance tab window (Figure 4 on page 8) provides tools to configure andmanage Performance Stations. Domino Performance Stations are Lotus Notes clientsthat run probes against Domino servers. A Performance Station is used specificallyfor performance management. Performance Stations run simulated usertransactions against Domino servers. Set up a Performance Station to collectresponse-time data for the servers in the Domino environment. You can use theresponse time data in graphs and reports.

A performance probe is an instance of a simulated Lotus Notes transaction. AvailableLotus Notes transaction types include round-trip mail, replication to a local client,database access, Web access, Name and Address Book search, calendar entrycreation, and network echo.

Figure 3. Backup and Restore tab with subtab windows of the Management Console


The Configuration tab with the Servers subtab window (Figure 5) provides a listof all servers in the Domino environment that are known to one or more Dominodomains. Use this tab to access tools to configure those servers for use with thisproduct.

The Configuration tab with the Profiles subtab and Profiles subtab window(Figure 6 on page 9) provides tools that simplify the event and resource modelconfiguration for Domino servers.

Figure 4. Performance tab with the Probes subtab window of the Management Console

Figure 5. Configuration tab with Servers subtab window of the Management Console


The Configuration tab with the Profiles subtab and Subscribers subtab window(Figure 7) provides a list of current subscribers and the ability to edit thesubscriber list.

The Configuration tab with the Preferences subtab window (Figure 8 on page 10)provides options for configuring Reliability, Accessibility, and Serviceability (RAS)logging and tracing. Use this tab to specify the directory in which log files arewritten, and to specify the logging level.

Figure 6. Configuration tab with Profiles subtab and Profiles subtab window of the Management Console

Figure 7. Configuration tab with Profiles subtab and Subscribers subtab window of the Management Console


Understanding IBM Tivoli MonitoringThis section describes the main concepts required for understanding how to set upand use resource models. IBM Tivoli Monitoring uses resource models to productmonitor and manage resources at distributed systems. A managed resource is adatabase object that represents a hardware, software, or data entity that youmanage according to policies set up in a Tivoli environment. Managed resourcescan include physical and logical disks, CPUs, memory, printers, processes, andservices. A distributed system is the service that monitors resources, compares datafrom monitored resources against configured thresholds, and runs automatedresponses in a Tivoli environment.

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.

AttributesAttributes can be string or numeric values. A resource model receivesattributes when it is created. In IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino, you do not add, delete, or modify attributesthat are in the default resource models. When creating a new resourcemodel with the IBM Tivoli Monitoring Workbench, you can qualify anevent by specifying relevant attributes according to the information youwant the resource model to monitor. For example, an event might indicateinsufficient disk space. When you specify attributes, such as disk name, oravailable disk space, the resource model can generate a more preciseindication of the problem. For each resource model, some of the attributesare designated as keys.

Cycles When a resource model runs at an endpoint, it gathers data at regularintervals, called cycles; the duration of a cycle is the cycle time, which is

Figure 8. Configuration tab with Preferences subtab window of the Management Console


displayed in seconds. A resource model with a cycle time of 60 secondsgathers data every 60 seconds. Each of the supplied resource models has 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 are 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, from which it canbe used in analyses that help plan network growth using key systemmetrics.

For more information about Tivoli Enterprise Data Warehouse, see thefollowing publications: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, which monitors the basic systemstatus at endpoints attached to the gateway at which it is enabled. Eventscan be sent to the Tivoli Business Systems Manager (provided that theTivoli Business Systems Manager Adapter component is installed at thegateway), the Tivoli Enterprise Console®, and the IBM Tivoli MonitoringNotice Group.

Indications and eventsAn indication is generated when the state of a given resource meetsdefined criteria. By itself, an indication does not trigger any specific action.When indications are aggregated, the resource model generates an event.When you define an event, you must specify under what conditions acertain number of indications are aggregated into an event. You alsospecify whether these indications must be consecutive, or whether thesequence may be interrupted by one or more monitoring cycles that do notregister any indication. The cycles during which no indication is generatedare called holes. An event can notify 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, however 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 and 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 Logical Disk resource model a HighRead Bytes per Second indication is not created when thepercentage disk time is higher than the High Percent Usagethreshold, provided that the Low Disk Space threshold isexceeded.

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. Thus, an event defines thesignificant 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 2.

Table 2. 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 3. The first row shows the cycle number andthe second the percentage of CPU usage.

Table 3. 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 3 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. The TivoliMonitoring operator can change these selections later, when theresource model is included in a Tivoli Monitoring profile. You canalso define the degree of severity and the message that will specifythe notification of the event.

Clearing EventsA clearing event is a resource model function that, if enabled, allows


IBM Tivoli Monitoring to close an event when the circumstancesthat caused the event are no longer present. Clearing events can beprocessed by the Tivoli Enterprise Console server and by TivoliBusiness Systems Manager. Clearing events have a severity ofharmless, regardless of the severity of the original event, but havethe 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, as soon as the service restarts, a clearingevent is sent to the Tivoli Enterprise Console server, therebyclosing the original event. The Clearing Event itself does notnormally appear on the server, because its only function is to clearthe original error event.

Note: Correlated events cannot be cleared.

Monitoring of events and indicationsEvents can be sent to the Tivoli Enterprise Console server, the WebHealth Console, and Tivoli Business Systems Manager.

Tivoli Enterprise Console ServerEvents can be viewed by a Tivoli Enterprise Console serverprovided that you have compiled and loaded the relevantBasic Recorder of Objects in C (BAROC) files on the server.The event contains a set of properties that can help toidentify the problem. For example, the information in theProcessHandleLeak event includes values for the following: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 incorporated in theabove-mentioned default procedure, the clearing event isdisplayed as a separate entity with the same id as theoriginal error event.

Web Health ConsoleThe Web Health Console, which is an optional part of IBMTivoli Monitoring, obtains events and indications fromendpoints. The Web Health Console displays the health ofeach potential problem as a numeric value between 100(perfect health) and zero (with zero meaning that theconditions for the corresponding event have been met).Intermediate values show the percentage of occurrencescurrently registered with respect to the total number ofoccurrences needed to trigger an event. For example,Table 4 on page 15 is based on Table 3 on page 13, butadditionally shows the health percentage:


Table 4. 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 were required to trigger anevent; if the indication had required 5 occurrences, thehealth percentage would have changed by steps of 20%.

Tivoli Business Systems Manager

Events can also be sent to the Tivoli Business SystemsManager, provided that the Tivoli Business SystemsManager Adapter component has been installed on thegateways of the endpoints that are to be monitored. A fulldescription of Tivoli Business Systems Manager can befound in the Tivoli Business Systems Managerdocumentation.

Clearing events can also be processed by the TivoliBusiness Systems Manager, which uses the clearing eventto close the associated error event.

LoggingFor any endpoint, you can log the data collected by a resource model andwrite it in a local database. Then you can view it through the History Viewof the Web Health Console. You can choose to store raw or aggregateddata.

ParametersWhile thresholds can be only numeric values, parameters can be lists ofnumbers or strings. Using parameters enables you to customize yourresource model. You can define different parameters, as required. For eachparameter you can specify a value, which can be a list of numbers orstrings. This list can represent the instances you want to monitor, or a limityou do not want your resource to exceed, depending on how you use thissetting in your script. The lists will then be displayed in the TivoliMonitoring dialogs, and depending on the type of list you select in theworkbench, the lists will appear in different forms on Tivoli Monitoring.Within the workbench you can define default values and then let theoperator customize the settings in Tivoli Monitoring. You can choose oneamong the following kinds of lists 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 can take positive steps toremedy the situation, or can ensure that information about the event isdistributed to the appropriate authorities or entities.

Built-in actions

Note: The indications in IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino resource models do not havebuilt-in actions.

Certain 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 couldhave the restart of that service as its built-in action. Thus, withoutany human intervention, IBM Tivoli Monitoring detects the failureof a service and automatically restarts it. Built-in actions aredefined by default as part of an event, but can be removed. Theyhave the same event ID as the event that they are designed tocorrect.

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

Resource modelsIBM Tivoli Monitoring products provide predefined resource models thataccess specific performance data from the system at runtime. (For example,the Process 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 either use a resource model’s default values to collectperformance data or customize the resource models to match specificrequirements in your environment. Distributing resource models usingdefault values enables you begin monitoring immediately to obtain usefuldata concerning your enterprise. When you become more familiar with themonitoring process and feedback, you may choose to customize theresource model information.

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 can


be 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 your region covers several time zones, but youwant to monitor morning activities in each time zone, a single ruledefining the monitoring period of between 08:00 and 13:00 is interpretedlocally in each of the time zones, so that you monitor the same relativeperiod.

You should note also that all times of events or activities reported fromendpoints or gateways are also logged in the local time of the system fromwhere they originated.

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 processes monitoredfor the highest usage of CPU. Thus, if you set the Maximum Processesthreshold to 5, the resource model only reports on the the five highestCPU-using processes.

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



Chapter 2. Getting started quick-reference guide for IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino

Table 5 provides a quick-reference table of the installation and setup proceduresyou must perform before you can use IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino.

Table 5. Quick reference for getting started with IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino

Goal Where to find procedures

Install the software See the IBM Tivoli Monitoring for Messaging andCollaboration Installation and Setup Guide.

Set up administrators

Assign each administrator the appropriate authorization rolefor the procedures that the administrator must perform.Note: You must assign Tivoli and Domino authorizationroles to administrators in the policy regions that you wantthem to administer.

Appendix A, “Authorization roles quick reference” onpage 265 lists the authorization roles required foreach procedure.

The Tivoli Management Framework, Version 3.7.1: User’sGuide describes how to assign authorization roles toTivoli administrators.

Set up managed resources

Assign the Tmw2kProfile option as a valid type of managedresource for the policy region.

Create server objects for this product.

“Managing resource types” on page 29

“Locating a Domino server and creating a DominoServer object” on page 35

Also see the IBM Tivoli Monitoring, Version 5.1.0:User’s Guide.

Set up profiles to monitor Domino servers

Set up resource models:

1. Set up the profile for the type of Domino server youwant to monitor.

2. Edit the profile, if necessary, to improve performance orresponsiveness.

“Adding a custom resource model to a profile” onpage 69

Set up profiles to probe Lotus Notes clients

Set up probes:

1. Create Domino Performance Stations to probe the LotusDomino clients that you designate.

2. Create the probes you need and run them one time totest connections.

3. Run probes at intervals that are appropriate to testcompliance with Service Level Agreements (SLAs).

Chapter 6, “Working with Domino PerformanceStations” on page 147

Perform management operations on Domino servers

Configure and manage Domino servers. Chapter 5, “Working with Lotus Domino Servers” onpage 111

Set up tasks and jobs

Set up any customized tasks that you require.

Create jobs, based on the tasks, that run on a schedule.

Chapter 7, “Working with tasks and jobs” on page171


Table 5. Quick reference for getting started with IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino (continued)


Connect to the Web Health Console

Connect to the Web Health Console so you can viewstatistics regarding server health in the Web Health Console.

“Connecting the IBM Tivoli Monitoring Web HealthConsole” on page 192

(Optional Feature) Connect to the Tivoli Enterprise Console

Set up the Tivoli Enterprise Console so that you can monitorpotential problems in your distributed environment.

Chapter 9, “Setting up the Tivoli Enterprise Consolefor event correlation” on page 207

(Optional Feature) Connect to the Tivoli Business Systems Manager

Set up Tivoli Business Systems Manager so that you canmonitor potential problems in your distributed environment.

Chapter 10, “Integrating with Tivoli Business SystemsManager” on page 225

(Optional Feature) Set up or connect to Tivoli Enterprise Data Warehouse

Set up Tivoli Enterprise Data Warehouse so that you canaccess application reports from various Tivoli and customerapplications.

Chapter 11, “Enabling Tivoli Enterprise DataWarehouse” on page 231

(Optional Feature) Back up and restore databases using Tivoli Data Protection

Back up and restore databases on Domino servers. Chapter 12, “Backing up and restoring Dominodatabases” on page 249


Chapter 3. Setting up IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino

This chapter describes how to set up IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino.

Table 6 provides a list of the goals you can achieve using the procedures in thischapter. The table also tells where to locate information about the procedures foreach goal.

Table 6. Goals and where to find procedures for setting up the software


Starting

Access the interfaces in the Tivolienvironment so you can use the operationsand functions of IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino.

“Starting the Tivoli environment” on page21

“Starting the Management Console” onpage 23

Setting up

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

“Setting authorization roles” on page 23

Group similar resources into policy regionsthat reflect your organization’s structures, soyou can perform tasks on multiple resourcesat one time.

“Managing policy regions” on page 26

Add or remove managed resource types soyou can create resource objects later.

“Managing resource types” on page 29

Create a subscription to a notice group for anadministrator so that the administrator canreview activity messages that alert him or herto failures that they can prevent or correct.

“Subscribing to notice groups” on page 32

Configuring Domino server objects

Configure Domino server objects to bemanaged by this software.

“Locating a Domino server and creating aDomino Server object” on page 35

“Discovering and configuring multipleservers in the Management Console” onpage 44

Delete a Domino server object. “Deleting a Domino Server object” on page49

Starting the Tivoli environment

ObjectiveTo access the Tivoli environment so that you can use the operations and functionsof IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino.

Background informationYou can access the Tivoli desktop or the Tivoli command line interface in order touse the operations and functions of IBM Tivoli Monitoring for Messaging and


Collaboration: Lotus Domino. (After you install the product, you can also use theManagement Console to perform operations and functions.)

The Tivoli desktop is a user interface that provides point-and-click access to IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino features andfunctions. The Tivoli desktop provides a central control point for you to organize,manage, and delegate system management operations.

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino alsoprovides a command line interface (CLI) that enables you to enter commands fromthe keyboard. You can use these commands in shell scripts and with systemutilities such as the UNIX cron utility. For more information about usingcommands, refer to the Tivoli Management Framework, Version 3.7.1: ReferenceManual.

Required authorization roleDomino_Admin

Before you beginNone.

When you finishNone.

ProcedureYou can perform this procedure from the command line or from the desktop ofyour workstation.

Command line: Use one of the following two methods to access the commandline interface, depending on whether you use a Windows NT or UNIX operatingsystem:v Windows NT

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

2. Click Start and select Command Prompt in the Windows taskbar to open thecommand prompt window.

3. Enter the following command to run the environment initialization and setupscript:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

This command enables you to perform all of the IBM Tivoli Monitoring forMessaging and Collaboration operations.

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

Windows NT desktop:

1. Do one of the following to access the login screen of the Tivoli desktop:v Click Start in the Windows taskbar and select Programs.


v Select Tivoli and selectTivoli a second time.—OR—

v Enter the tivoli command at a DOS prompt. See the Tivoli ManagementFramework, Version 3.7.1: Reference Manual for more information on thiscommand.

2. Type the following values in the fields of the login screen:v Host Machine specifies the Tivoli managed node, including the Tivoli server

where the Tivoli desktop should connect.v Log In As specifies the login name to the managed node.v Password specifies the password for the specified login name.

3. Click OK to display the Tivoli desktop.

Starting the Management Console

ObjectiveTo access the IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino Management Console so you can use the operations and functions of thissoftware.

Background informationThe Management Console is a graphical user interface on Windows NT that runsin a Web browser or in the Lotus Notes 5.x client to provide an alternative to theTivoli desktop. The Java 2 RunTime Environment enables the ManagementConsole. You can run most operations from either user interface with identicalresults.

Required authorization roleYou start the Management Console and view managed resources with thefollowing authorization roles:v Domino_Admin (You also use this role to perform all operations in the

Management Console)v Domino_User

Before you beginInstall the Management Console, as described in IBM Tivoli Monitoring forMessaging and Collaboration Installation and Setup Guide. The installation routine forthe Management Console creates a shortcut to IBM Tivoli Monitoring forMessaging and Collaboration. Use this shortcut to start the Management Console.

When you finishConfigure and manage IBM Tivoli Monitoring for Messaging and Collaboration.

ProcedureYou can perform this procedure in the Windows desktop of your workstation.

Windows desktop: Double-click the IBM Tivoli Monitoring for Messaging andCollaboration shortcut on the desktop to start the console.

Setting authorization roles

ObjectiveTo authorize persons to have the roles they need for managing resources in IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino.

Chapter 3. Setting up IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino 23

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 his or her responsibilities:v Domino_Admin authorizes the administration of Domino servers.v Domino_TDP_Admin authorizes the administration backups of Domino servers.v Domino_DPS_Admin authorizes the administration of Domino Performance

Stations.

The Domino_User role for these three areas of responsibility has less access andfewer capabilities in IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino.

Required authorization rolesenior


When you finishYou can add managed resources (objects) to a policy region. See “Managingresource types” on page 29 for more information on working with various types ofmanaged resources.

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

Command line: Use the wsetadmin command to set or change resourceauthorization roles. See the Tivoli Management Framework, Version 3.7.1: ReferenceManual for more information.

Desktop: Follow these steps to perform this procedure from the Tivoli desktop:1. Double-click the Administrators icon to display the Administrators dialog box.

2. Right-click the existing administrator whose role you want to modify to displaythe pop-up menu.

3. Select Edit Resource Roles to display the Set Resource Roles dialog box.

Figure 9. Administrators dialog box (Desktop)


4. Select a resource for which you want to set the administrator’s role from theResources list.Additional information: The roles listed in the Available Roles and CurrentRoles lists depend on the particular applications installed.

5. 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.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 only moves the selectedroles temporarily to the Current Roles or Available Rolesscrolling lists.

b. Click Change after moving each role or multiple roles.Additional information: The Set Resource Roles dialog box remainsdisplayed until 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.

Figure 10. Set Resource Roles dialog box (Desktop)


v Remove Rolesa. Do one of the following to remove roles for resources:

– Select one or more roles from those shown in the Current Rolesscrolling list, and click the right-arrow.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 or multiple roles.Additional information: The Set Resource Roles dialog box remainsdisplayed until you click Close or Change & Close.

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

6. Shut down and restart the Administrator’s desktop to activate these changes.

Managing policy regions

ObjectiveTo create or delete policy regions that group similar resources to reflect yourorganization’s structures, so you can perform tasks on multiple resources at onetime.

Note: You must create policy regions within the Messaging and Collaborationpolicy region that the product creates at installation. Automated features ofthe product are enabled in this policy region.

Background informationTo group resources, you create a policy region of similar resources. You use thepolicy region to perform a task (such as distributing resource models) one time onmultiple resources. By using this procedure you avoid performing the task severaltimes on individual resources.

A policy region is a collection of resources, such as servers or databases, that shareone or more common attributes. By grouping similar resources into a single policyregion, it is easier to perform tasks on multiple objects that are similar rather thanrepeating the task multiple times. One way to organize resources is to create policyregions that reflect your organizational or geographical structures. This customizesthe product to maintain and manage your resources. For example, you could createpolicy regions called North_America and South_America to manage site-specifichardware and software.

The product installation process creates a top-level policy region called Messagingand Collaboration. The product components install into this policy region. Createpolicy regions for Domino servers in the Messaging and Collaboration policyregion. The product does not manage any policy regions created outside of theMessaging and Collaboration policy region.

In IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino, you canorganize policy regions hierarchically to match your processes or to match your


company structure. However, make sure that you keep all regions within theMessaging and Collaboration policy region.

Note: You can delete a policy region only when it is empty.

Required authorization roleTo create a policy region: admin and senior.

To delete a policy region: senior.

Before you beginAssign authorization roles, as described in “Setting authorization roles” on page23.

When you finishIf you created a policy region, add managed resources (objects) to the policy region(see “Managing resource types” on page 29). You can create, clone, and modifypolicy regions to create the relationships, capabilities, and authorizations that theTivoli management region requires. See the Tivoli Management Framework, Version3.7.1: User’s Guide for information on working with policy regions.

ProcedureYou can perform this procedure from the command line, the Tivoli desktop, or theManagement Console.

Command line: Use the wcrtpr command to create a new policy region. Thesyntax for the command varies depending on the version of the TivoliManagement Framework you are using. You must have the resource types thatIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino requires, asdescribed in “Managing resource types” on page 29. For more information on thewcrtpr command, refer to the Tivoli Management Framework, Version 3.7.1: ReferenceManual.

For example, to create a policy region named Europe_Operations on the desktopof administrator Chris, enter the following command:wcrtpr -a chris Europe_Operations

Delete the resources in the policy region that you want to delete, as described in“Deleting a Domino Server object” on page 49. Then use the wdelpr command todelete an empty policy region. See the Tivoli Management Framework, Version 3.7.1:Reference Manual for more information.

Desktop:

v Create a Policy Region1. Open the Messaging and Collaboration policy region.2. Click Create and select Subregion to display the Create Policy Region

dialog box.


3. Type a name for the new policy region in the Name text box.Additional information: The policy region name can include letters, numbers,underscores, dashes, periods, and spaces. The name must be unique withinthe local Tivoli management region.

4. Click Create & Close to create the new policy region and return to thedesktop.

5. If necessary, add the resource types that the product requires, as described in“Managing resource types” on page 29.

v Delete a Policy Region1. Double-click the policy region icon to open the Policy Region window.2. Delete each resource object icon in the window as follows:

a. Click the icon for the resource object you want to delete.b. Click Edit and select Delete to delete the resource object.c. Click Yes to confirm deletion of the resource object.

3. Click Close to close the window.4. Select Delete in the Edit menu to delete the policy region.5. Click Yes to confirm deletion of the policy region.

Management Console:

v Create a Policy Region1. Click the Configuration tab.2. Click the Profiles tab.3. Click Create Policy Region from the Tools menu to display the Create

Policy Region dialog box.

4. Select the policy region from the Parent Policy Region drop-down list inwhich to create the new policy region in the Create Policy Region menu.

Figure 11. Create Policy Region dialog box (Desktop)

Figure 12. Create Policy Region dialog box (Management Console)


5. Enter the name of the new policy region in the New Policy Region Nametext box.Additional information: The policy region name can include letters, numbers,underscores, dashes, periods, and spaces. The name must be unique withinthe local Tivoli management region.

6. Click OK to create the new policy region and return to the ManagementConsole.

7. If necessary, add the resource types that the product requires, as described in“Managing resource types” on page 29.

v Delete a Policy Region1. Click the Configuration tab.2. Click the Profiles tab.3. If the policy region that you want to delete has resources in it, delete the

resources as described in “Deleting a Domino Server object” on page 49.4. Click Delete Policy Region in the Tools menu to display the Delete Policy

Region dialog box.

5. Select the policy region that you want to delete from the Policy Regiondrop-down list.

6. Click OK to delete the policy region and return to the Management Console.7. If necessary, add the resource types that the product requires, as described in

“Managing resource types” on page 29.

Managing resource types

ObjectiveTo add a previously deleted managed resource type so that you can create resourceobjects of this type, or to remove a managed resource type that you do not needfor the software to manage.

Background informationA managed resource is any hardware or software on your system or networkwhere Domino is installed and monitored. Resource types determine which typesof components you can manage. The managed resource types enable you to createresource objects for those resources that you want to manage. For example, tocreate a Domino server object, you must add the LotusDominoServer managedresource type to the policy region.

When you create a policy region in the Tivoli desktop or in the ManagementConsole, the component automatically adds the following managed resource typesto enable all basic configuration activity: DominoPerformanceStation,Events4Profile, LotusDominoServer, Tmw2kProfile, ProfileManager, andTaskLibrary. These resource types also exist by default in the top-level policy

Figure 13. Delete Policy Region dialog box (Management Console)


region (Messaging and Collaboration) of the product. You only need to add amanaged resource type if someone previously deleted it from a policy region.

Required authorization rolepolicy, senior, and super

Before you beginDetermine which types of resources you want the product to manage.

Create the policy region where you want to group the resource objects. See“Managing policy regions” on page 26 for information on this topic.

When you finishCreate the objects for the managed resources that you want to manage. See“Locating a Domino server and creating a Domino Server object” on page 35 and“Configuring a Domino Performance Station” on page 152 for information.


Command line: Use the following commands to manage resource types:v Use the wgetpr command to list the installed managed resources.v Use the wsetpr command to set up the managed resources of a policy region,

and to do the following:– Assign the policy used in a policy region.– Enable or disable policy validation.

—OR—– Add or remove a managed resource in a policy region.

The following is the partial CLI syntax for the wsetpr command. See the TivoliManagement Framework, Version 3.7.1: Reference Manual for a complete description.

wsetpr [–d <default_pol>] [–v <validation_pol>] [–E | –e] <resource region>

wsetpr [–r] <resource region>

where:

–d <default_pol>Specifies the label of the default policy to use for the managed resource.

–v <validation_pol>Specifies the label of the validation policy to use for the managedresource.

–E Displays policy validation.

–e Enables policy validation.

–r Removes the specified resource from the policy region.

<resource>Specifies the managed resource type. The following managed resourcetypes enable all basic configuration activity in IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino:DominoPerformanceStation, Events4Profile, LotusDominoServer,Tmw2kProfile, ProfileManager, and TaskLibrary.


<region>Specifies the label of the target policy region.

The following example removes the DominoPerformanceStation resource fromthe North_America policy region:wsetpr -r DominoPerformanceStation @PolicyRegion:North_America

Desktop:

1. Double-click the policy region where you want to add a managed resource todisplay the Policy Region window.

2. Click Properties and select Managed Resources to display the Set ManagedResources dialog box.

Additional information: The Current Resources list displays the policy region’scurrent managed resources, and the Available Resources list displays themanaged resources that you can add to the policy region.

3. Add or remove one or more resources as follows:Additional information: The following managed resource types enable all basicconfiguration activity in IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino: DominoPerformanceStation, Events4Profile,LotusDominoServer, Tmw2kProfile, ProfileManager, and TaskLibrary.

v Add Resourcesa. Do one of the following to add resources:

– Select one or more resources from those shown in the AvailableResources scrolling list, and click the left-arrow.The selected resources move from the Available Resources scrollinglist to the Current Resources scrolling list.—OR—

– Double-click an entry in the Available Resources scrolling list to moveit automatically to the Current Resources scrolling list.

Note: Moving a resource from one list to another only moves theselected resource temporarily to the Current Resources or

Figure 14. Set Managed Resources dialog box (Desktop)


Available Resources scrolling lists. The Set Managed Resourcesdialog box remains displayed until you click Close or Set &Close.

b. Click Set & Close to add all of the selected Resources for theadministrator and return to the Policy Region window.Additional information: This action also causes the Create menu to displayany managed resource type that you moved into the Available Resourceslist.

v Remove Resourcesa. Do one of the following to remove resources:

– Select one or more resources from those shown in the CurrentResources scrolling list, and click the right-arrow.The selected resources move from the Current Resources scrolling listto the Available Resources scrolling list.—OR—

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

Note: Moving a resource from one list to another only moves theselected resource temporarily to the Current Resources orAvailable Resources scrolling lists. The Set Managed Resourcesdialog box remains displayed until you click Close or Set &Close.

b. Click Set & Close to remove all of the selected resources for the policyregion and return to the Policy Region window.Additional information: This action also causes the Create menu to displayany resource that you moved into the Available Resources list.

Subscribing to notice groups

ObjectiveTo create a subscription to a notice group for an administrator so that theadministrator can review activity messages that alert him or her to failures thatthey can prevent or correct.

Background informationWhen you install the software, it creates a notice group called Messaging andCollaboration. The root administrator is the only administrator who subscribes tothis group automatically. Any other administrators must subscribe to the groupusing the subscribing to notice groups procedure.

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


Before you beginYou must create an administrator before you can subscribe the administrator to anotice group. For information about creating administrators, see the TivoliManagement Framework, Version 3.7.1: Reference Manual.

When you finishYou can review messages and prevent or correct failures.



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 Messagingand Collaboration notice group:wsetadmin -n "Messaging and Collaboration" "Steve Callahan"

For more information about this command, see the Tivoli Management Framework,Version 3.7.1: Reference Manual.

Desktop: Follow these steps to perform this procedure from the Tivoli desktop:1. Double-click the Administrators icon to open the Administrators window.2. Right-click the administrator you want to subscribe to the notice groups.3. Choose Edit Notice Group Subscriptions to display the Set Notice Groups

dialog box.Additional information: The Current Notice Groups list displays the noticegroups to which the administrator is currently subscribed. The Available NoticeGroups list displays the notice groups to which the administrator can subscribe.

4. Add or remove one or more notice groups as follows:v Add Notice Groups

a. Do one of the following to add notice groups:– Select one or more notice groups from those shown in the Available

Notice Groups scrolling list, and click the left-arrow.The selected notice groups move from the Available Notice Groupsscrolling list to the Current Notice Groups scrolling list.—OR—

Figure 15. Set Notice Groups dialog box (Desktop)


– Double-click an entry in the Available Notice Groups scrolling list tomove it automatically to the Current Notice Groups scrolling list.

Note: Moving a notice group from one list to another only moves theselected notice group temporarily to the Current Notice Groupsor Available Notice Groups scrolling lists.

b. Click Change after moving each notice group or multiple notice groups.Additional information: The Edit Notice Group Subscriptions dialog boxremains displayed until you click Close or Change & Close.

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

v Remove Notice Groupsa. Do one of the following to remove notice groups:

– Select one or more notice groups from those shown in the CurrentNotice Groups scrolling list, and click the right-arrow.The selected notice groups move from the Current Notice Groupsscrolling list to the Available Notice Groups scrolling list.—OR—

– Double-click an entry in the Current Notice Groups scrolling list tomove it automatically to the Available Notice Groups scrolling list.

Note: Moving a notice group from one list to another only moves theselected notice group temporarily to the Current Notice Groupsor Available Notice Groups scrolling lists.

b. Click Change after moving each notice group or multiple notice groups.Additional information: The Set Notice Groups dialog box remainsdisplayed until you click Close or Change & Close.

c. Click Change & Close to remove all of the selected notice groups for thepolicy region and return to the Administrators window.

Management Console:

1. Click the Configuration tab.2. Click the Profiles tab in the upper left corner of the window.3. Click the Subscribers tab in the middle section of the window.4. Click Edit Subscribers list on the menu bar between the Subscribers tab and

the Subscribers list to display the Edit Subscriber List.


5. Move a subscriber between the Available Subscribers list and the CurrentSubscribers list by doing the following:a. Click a subscriber name on either list to select it.b. Click the arrow that points toward the list in which you want to place the

selected subscriber.The subscriber name is displayed in the list toward which the arrowpointed.

c. Click OK to close the dialog box.Additional information: You can also double-click a single subscriber name tomove it, or you can move multiple subscribers by dragging over two ormore consecutive subscriber names before clicking the arrow.

The subscriber name is displayed in the Subscribers list.

Locating a Domino server and creating a Domino Server object

ObjectiveTo locate a Domino server that you want to manage in IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino, to capture the server configurationinformation, and to configure it as a server object in this product.

Note: You can use this procedure to configure each Domino server that you wantto manage. However, in the Management Console, you can use theautomated server configuration features of the Management Console toconfigure one or more Domino servers, as described in “Discovering andconfiguring multiple servers in the Management Console” on page 44.

Background informationA Domino server is represented in a Tivoli policy region by an object of the typeLotusDominoServer. Another object that is unique to this product isDominoPerformanceStation.

This product performs automatic discovery and configuration through the firstserver that is configured, which is the reference point for finding all other servers.In the Management Console, this reference server is called the source server. The

Figure 16. Edit Subscriber List dialog box (Management Console)


server that is your reference point can be any server object. This procedure forlocating a Domino server and creating a Domino server object describes how youcan create a server object to use as the reference point for configuring otherservers. It is recommended that you configure the Lotus Domino Registrationserver to be the server that is your reference point for configuring other servers.

You can perform this procedure while the target Domino server is running orwhile the server is down. As part of the configuration process the Tivolienvironment installs 2.5 MB of software including the following items: resourcemodels that match the server type, two versions of the Tivoli addin, and a binaryfile that enables the product to start the Domino server.

The Tivoli environment also adds the Lotus Domino Server to the appropriateprofile manager based on the server’s type.

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino can locateDomino servers on any endpoint in the Tivoli management region. The locateserver operation speeds configuration of a single server by capturing configurationinformation from the endpoint.

Note: The functionality for locating a server detects only servers that are notalready configured for this product.

The command for locating a server finds the endpoint and gathers configurationdata on the server. On UNIX systems, it searches the /opt/lotus/.install.dat file. OnWindows NT, the command searches the Services registry. This command thendisplays a dialog box with all available information filled in.

You can configure one or more Lotus Domino Server instances on an endpoint.When the endpoint server is partitioned and contains more than one instance ofthe Lotus Domino Server, use the wtmdlocateserver command as described in thecommand line procedure in this section.

If you use a Lotus Domino server configuration document to manage theServerTasks entry in the notes.ini file, you must update the configurationdocument as follows:v Add tivoliv46 to the list of ServerTasks.

—OR—v Add tivoliv50 to the list of ServerTasks.

The configuration procedures in “Discovering and configuring multiple servers inthe Management Console” on page 44 describe how to make this update to theLotus Domino Server configuration document.

Table 7 contains a list of the properties for Domino servers and a description ofeach one. Notice that some properties are required and others are not required.

Table 7. Domino server properties

Property Required Description

ObjectLabel Yes Label assigned to the Domino server object. Thedefault label is the common Domino server name.

Endpoint Name Yes Name of the endpoint where the Domino server islocated.

INI File Location Yes Full path name of the notes.ini file.


Table 7. Domino server properties (continued)

Property Required Description

Policy Region Yes Name of the existing policy region in which you wantthe new server object to reside, or name of a newpolicy region in which you want the new server objectto reside.Note: When you type a name in this text box, theproduct creates a new policy region with that name, ifit does not already exist. The policy region is asub-region in the Messaging and Collaboration policyregion.

Server Password No If specified, the password for this server’s ID file thatis used to start the server. The server password isrequired if the Domino server is password protected.

You use this parameter to perform an unattended startof a server that has a password protected server.idfile.Note: This parameter is not supported for WindowsNT servers.

Addin Port Yes Port number to use for the Tivoli addin process.

Mail Database Server No Type of Domino server. A server can have multipleserver types.

Web Server No Type of Domino server. A server can have multipleserver types.

Mail Router Server No Type of Domino server. A server can have multipleserver types.

Application Server No Type of Domino server. A server can have multipleserver types.

News Server No Type of Domino server. A server can have multipleserver types.

Note: The following properties are related to the optional backup capabilities in thisproduct. The properties are optional. However, when you specify one of the followingproperties, you must specify all of these properties, with one exception: if there is no TDPPassword, you can leave that text box empty.

TDP ProgramDirectory

No Directory where Tivoli Data Protection for LotusDomino is installed.

TSM API Directory No Directory where the Tivoli Storage Manager API filesare installed.

TDP ConfigurationFile

No Name of the Tivoli Data Protection configuration file,relative to the program directory that you specify inthe TDP Program Directory text box. The defaultname of the configuration file is domdsm.cfg.

TDP Options File No Name of the Tivoli Data Protection options file,relative to the program directory that you specify inthe TDP Program Directory text box. The defaultname of the options file is dsm.opt.

TDP User No Name of the Tivoli Data Protection user.

TDP Password No Password, if any, for the Tivoli Data Protection user.



Before you beginThe systems on which Domino is installed must be configured as endpoints in theTivoli environment. See the Tivoli Management Framework, Version 3.7.1: ReferenceManual for more information on this topic.

The Domino server can be running while you perform this procedure.

On Windows, the Domino server must be configured as a Windows NT ServerService. On Windows, you cannot locate a Domino server that does not have itsnotes.ini file location information within the service control registry.

When you finishIf you create a Domino server object while the Domino server is down, you muststart the server as described in “Controlling a server” on page 113. This action isan integral part of the server configuration process. After the server is configured,you can start the server in whatever way is most convenient.

If the Domino server runs Lotus Domino, Version 5.x, and you created the Dominoserver object while the server was up, you must restart the server before you canuse the mail tracing functionality of this product.


Command line: The wtmdlocateserver and wtmdcreateserver commands locateDomino servers and create server objects in the Tivoli environment. This sectionsummarizes the server configuration process. See the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide for a complete descriptionof these commands.1. Use the wtmdlocateserver command to locate a Domino server.

For example, to locate a Domino server or servers on endpoint Jersey, type thefollowing command:wtmdlocateserver Jersey

The command returns a list of the servers found on that endpoint. Thefollowing example shows the results for a partitioned server that contains twoLotus Domino Servers:Server Name INI File Location Domain Port=========================================================Freddy/Sales/IBMUS C:\domino\notes.ini IBMUS 3000Speedy/IBMUK C:\lotus\notes.ini IBMUK 3001

2. Using the information in the report, enter the wtmdcreateserver command tocreate the server object in Tivoli.For example, the following command defines Freddy/Sales/IBMUS as aDomino server object named MailSrvr1 on the endpoint Jersey with an .ini filelocated at C:\domino\notes.ini. The command creates a server object in theSales policy region. The software communicates with the server using port3000. The –TYPE argument identifies the server as a mail database server.v Example for UNIX-based operating systems:

wtmdcreateserver MailSrvr1 Jersey C:\\domino\\notes.ini Sales 3000 -TYPE=Mail

v Example for Windows-based operating systems:wtmdcreateserver MailSrvr1 Jersey C:\domino\notes.ini Sales 3000 -TYPE=Mail

3. Choose one of the following actions:


v If the Domino server was running while you performed the preceding steps,go to Step 4.—OR—

v If the Domino server was down while you performed the preceding steps,you must use one of the following methods to start the server:Additional information: Always use one of the following methods to start aDomino server on Windows systems.– Use the Management Console as described in “Controlling a server” on

page 113.OR

– On Windows, use the Services user interface in the Windows ControlPanel to start the Lotus Domino Server service.

Note: You might disable functionality in IBM Tivoli Monitoring forMessaging and Collaboration if you use an executable or use a Startmenu item in the Windows taskbar to start the Domino server.

4. If you do not use a Lotus Domino Server configuration document to managethe Domino server, go to Step 6.

5. If you use a Lotus Domino Server configuration document, do the following:a. If your Lotus Domino Server configuration document does not specify server

tasks in the ServerTasks field of the configuration document, go to Step 6.b. If your Lotus Domino Server configuration document does specify server

tasks in the ServerTasks field of the configuration document, do thefollowing:1) Copy the ServerTasks specifications from the notes.ini file of the

Domino server.Additional information: When you create a Domino server object, IBMTivoli Monitoring for Messaging and Collaboration adds one of thefollowing items to the beginning of the ServerTasks specification:v tivoliv46, if you are running Lotus Domino, Version 4.6.xv tivoliv50, if you are running Lotus Domino, Version 5.x

The following example shows typical ServerTasks specifications for aconfigured Domino server:ServerTasks=tivoliv50,Replica,Router,Update,Stats,AMgr,Adminp,Sched, \CalConn,Event

2) Access the server configuration document in the Lotus Domino userinterface.

3) Paste the values you copied in Step 5b1 into the ServerTasks field.Additional information: The string value for the addin for this product(which is tivoliv46 or tivoliv50) must be the first task named in thefield.

4) Save the modifications you made to the configuration document.6. Begin to use IBM Tivoli Monitoring for Messaging and Collaboration to

manage and monitor the Domino server, as described in Chapter 5, “Workingwith Lotus Domino Servers” on page 111 and in subsequent chapters.

Desktop: Follow these steps to locate a server from the Tivoli desktop:1. Double-click the Messaging and Collaboration policy region icon or the

policy region icon for the region to which you are adding a Domino server.The Policy Region window is displayed.


2. Click Create and select LotusDominoServer to display the Create DominoServer dialog box.

Note: If LotusDominoServer is not listed in the Create menu, follow theprocedure in “Managing resource types” on page 29 to add thismanaged resource type to the policy region and to the Create menu.

3. Do one of the following:v If you want to have this product locate the server:

a. Enter the endpoint name and click Locate.b. Enter the missing information and click Configure.

—OR—v If you already know the server properties and want to enter them yourself,

leave the Endpoint Name text box blank and click Advanced to display theCreate Domino Server dialog box.

4. Click Configure.Additional information: This product registers the server object, creates an iconfor the server, and displays a Server Successfully Created message. ClickView and select Refresh to see the new icon on the desktop. If you performthis procedure in the Messaging and Collaboration policy region, but define adifferent policy region as the target, you must navigate to that policy region tosee the server object that you created. It can take up to 10 minutes to completethe configuration based on network traffic, server load, and so on.

5. Choose one of the following actions:v If the Domino server was running while you performed the preceding

steps, go to Step 6.—OR—

v If the Domino server was down while you performed the preceding steps,you must use one of the following methods to start the server:Additional information: Always use one of the following methods to start aDomino server on Windows systems.– Use the IBM Tivoli Monitoring for Messaging and Collaboration user

interface as described in “Controlling a server” on page 113.OR




Figure 17. Create Domino Server dialog box (Desktop)


7. If your Lotus Domino Server configuration document does not specify servertasks in the ServerTasks field of the configuration document, go to Step 12.

8. Copy the ServerTasks specifications from the notes.ini file of the Dominoserver.Additional information: When you create a Domino server object, IBM TivoliMonitoring for Messaging and Collaboration adds one of the following itemsto the beginning of the ServerTasks specification:v tivoliv46, if you are running Lotus Domino, Version 4.6.xv tivoliv50, if you are running Lotus Domino, Version 5.x


9. Access the server configuration document in the Lotus Domino user interface.10. Paste the values you copied in Step 8 into the ServerTasks field, placing the

string value for the addin for this software (tivoliv46 or tivoliv50) as the firsttask named in the field

11. Save the modifications you made to the configuration document.12. Begin to use IBM Tivoli Monitoring for Messaging and Collaboration to


Management Console:

1. Click the Configuration tab to display the configuration view of theManagement Console.

2. Click the Server tab in the upper left corner of the window.3. Click Configure Source Server in the Tools - Directories drop-down bar. The

Configure Source Server dialog box is displayed.

4. Click Add to display the basic view of the Create Domino Server dialog box.

Figure 18. Configure Source Server dialog box (Management Console)


5. Use one of the following methods to select an endpoint to configure:

Note: It is recommended that the Lotus Domino Registration server be thefirst server that you configure for this product.

v If you know the name of the endpoint that you want to configure, enter thisname directly into the Endpoint text box.—OR—

v Click the Browse icon to the right of the Endpoint text box to display a listwhere you can select an endpoint.

6. Click Locate to begin the process of locating the server.Additional information: The populated Create Domino Server dialog box isdisplayed. The Basics tab is selected in this view and all availableconfiguration information is displayed in the fields of this tab.

Note: If you know all configuration parameters for a Domino server, you canclick Advanced instead of Locate. The Create Domino Server dialogbox with the Basics tab is displayed so that you can enter the requiredvalues.

Figure 19. Create Domino Server dialog box (Management Console)

Figure 20. Create Domino Server dialog box Basics tab (Management Console)


7. Enter missing values, if any, and in the Type area, select the type or types thatmatch the role that the Domino server plays in the Domino domain.Additional information: See Table 7 on page 36 for a description of all fields inthis dialog box.

8. (Optional) If you are managing backups with Tivoli Data Protection and TivoliStorage Manager, enter missing values, if any, in the Backup subtab of theCreate Domino Server dialog box.

Note: Do not enter values in these text boxes if you do not have Tivoli DataProtection and Tivoli Storage Manager.

9. Click Configure to finish creating the server object.Additional information: The Configure Source Server dialog box is displayedand shows the endpoint that you configured in the Available list box.

10. Double-click the endpoint name to move it to the Selected list box and clickOK. The endpoint is displayed in the list of servers in the table in theManagement Console.Additional information: After you configure the source (first) server in theDomino domain, all Domino servers appear in the Configuration view of theManagement Console. Servers that are not configured as server objects in thisproduct have the letter U (for Unconfigured) in the Status column of theirrow.

11. Choose one of the following actions:v If the Domino server was running while you performed the preceding steps,

go to Step 12.—OR—

v If the Domino server was down while you performed the preceding steps,use one of the following methods to start the server:

Figure 21. Create Domino Server dialog box Backup tab (Management Console)


Additional information: Always use one of the following methods to start aDomino server on Windows systems.– Use the IBM Tivoli Monitoring for Messaging and Collaboration user








15. Access the server configuration document in the Lotus Domino user interface.16. Paste the values you copied in Step 14 into the ServerTasks field.

Additional information: The string value for the addin for this product (which istivoliv46 or tivoliv50) must be the first task named in the field.



Discovering and configuring multiple servers in the ManagementConsole

ObjectiveTo discover and configure one or more Domino servers after you configure a firstserver in the Domino domain, as described in “Locating a Domino server andcreating a Domino Server object” on page 35.

Background informationBecause the Management Console presents a composite view of Domino servers inthe Tivoli management region, it offers the following functionality that does notexist when you use the Tivoli desktop or the CLI:v Discovery of all Domino servers in a Domino domain after you configure the

first (or source) server in the domain, which is described in the currentprocedure.


v Configuration of multiple servers at one time when servers share parameterssuch as location of .ini files, policy regions, and port numbers.

v Dynamic display of all configured servers in a tabular format for quickinspection of names, configuration status, and other attributes.

This software performs automatic discovery and configuration through the firstserver that is configured, which is the reference point for finding all other servers.In the Management Console, this reference server is called the source server. Theserver that is your reference point can be any server object. “Locating a Dominoserver and creating a Domino Server object” on page 35 describes how you cancreate a server object to use as the reference point for configuring other servers. Itis recommended that you configure the Lotus Domino Registration server to be theserver that is your reference point for configuring other servers.

The Management Console gives Domino servers one of the following state codes inthe State column within the Servers pane of the Configuration tab:v U — Server is not configured for this softwarev UM — Configuration settings modified, but server is not configured for this

softwarev C — Server is configured for this softwarev CM — Configuration settings modified, and server is already configured for this

software

Note: Use this procedure to modify configuration settings of unconfigured servers.See “Editing server properties” on page 122 to edit the configuration settingsof configured servers.

You can perform this procedure while the target Domino server is running orwhile the server is down. As part of the configuration process the Tivolienvironment installs 2.5 MB of software including the following items: resourcemodels that match the server type, two versions of the Tivoli addin, and a binaryfile that enables the product to start the Domino server.

The Tivoli environment also adds the Lotus Domino Server to the appropriateprofile manager based on the server’s type.

Configuration of Domino servers works best when only one instance of LotusDomino Server exists on the endpoint. When the endpoint server is partitionedand contains more than one instance of the Lotus Domino Server, use thewtmdlocateserver command as described in “Locating a Domino server andcreating a Domino Server object” on page 35.

You can perform this procedure while a Domino server is up or down.

If you use a Lotus Domino server configuration document to manage theServerTasks entry in the notes.ini file, you must update the configurationdocument as followsv Add tivoliv46 to the list of ServerTasks.





Before you beginYou must create a first Domino server object as described in “Locating a Dominoserver and creating a Domino Server object” on page 35. This Domino serverenables automatic discovery and configuration of other Domino servers.

The Domino servers can be running while you perform this procedure.

On Windows the Domino server must be configured as a Windows NT ServerService.

When you finishIf you create a Domino server object while the Domino server is down, you muststart the server as described in “Controlling a server” on page 113. This action isan integral part of the server configuration process. After the server is configured,you can start the server in whatever way is most convenient.

If the Domino server runs Lotus Domino, Version 5.x, and you created the Dominoserver object while the server was up, you must restart the server before you canuse the mail tracing functionality of this software.

ProcedureYou can perform this procedure from the Management Console only.

Management Console:


2. Click the Servers tab in the upper left corner of the window.3. Click Configure Source Server in the Tools - Directories drop-down bar. The

Configure Source Server dialog box is displayed.4. Select the name of the server that you want to define as the source server in

the Available list box.Additional information: If the name of the server is located in the Selected listbox, click Cancel from the dialog box and proceed to Step 7 because thatserver has already been selected as the source server.It is recommended, but not required, that you select only one source server foreach Domino domain. If you select more than one source server, IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino must performextra work to process information from both servers.

5. Double-click a server name in the Available list box to transfer the name tothe Selected list box.

6. Click OK.Additional information: The list of servers in the Configuration tab refreshes todisplay all the Domino servers that are listed in the Lotus Name and AddressBook database file (names.nsf) of the source server.

7. Click the name of the unconfigured server that you want to configure.Additional information: Unconfigured servers display a U in the State column.If you want to configure multiple servers, click in the column to the left of theserver list to place a check mark beside the name of each server that you wantto configure.

8. Click Edit in the toolbar above the server list to display the Edit dialog box.


Additional information: If you select only one server in the Server pane, thatserver name is selected by default in the Apply changes to area. If you selectmultiple servers, the All selected servers option is selected in the Applychanges to area.

9. Prepare text boxes of the Edit dialog box, if necessary.v If you are configuring a single server, all text boxes are enabled and you

can go to Step 10.v If you are configuring multiple servers, click the check box to the left of

each text box label to enable the text boxes that you want to edit.

Note: When you configure multiple servers, the software applies thechanges you enter to all servers that you designate. For example, allthe servers you configure are created in the policy region that youname in the Policy Region text box.

10. Enter missing values, if any, for the Basic and Backup tabs.Additional information: You can edit all values in the Edit dialog box when youconfigure an individual server. You can edit only the following propertieswhen you configure multiple servers: INI File Location, Policy Region,Server Password, Port, Type, and properties in the Backup tab. See Table 7 onpage 36 for a description of all fields in this dialog box.

Note: Do not enter values in the Backup tab of the Edit dialog box if you donot have Tivoli Data Protection and Tivoli Storage Manager softwareinstalled.

11. Click Save.

Figure 22. Edit dialog box Basics tab (Management Console)


Note: Your edits do not take effect when you click Save. Your edits take effectwhen you use the Configure tool located above the server list in theServers pane, as described later in this procedure.

12. (Optional) To clear all settings you made in the Edit dialog box, click theRefresh tool located above the server list in the Servers pane of theConfiguration tab of the Management Console.

13. Click the Configure tool located above the server list in the Servers pane todisplay the Configure dialog box.

14. Select one of the following options in the Configure Option area:v Click the option for a specific server if you want to configure only that

server.v Click the All modified servers option if you want to configure all servers

whose configuration settings have been modified.v Click the All selected servers option if you want to configure all servers

beside which you have placed a check mark in the Servers pane of theConfiguration tab.

15. Click Execute.16. Click Yes in the confirmation dialog box to configure the server or servers and

return to the Configure dialog box.17. Review the results of the configuration in the Results column of the table in

the Results area of the Configure dialog box.18. Click Close.19. Choose one of the following actions:

v If the Domino server was running while you performed the precedingsteps, go to Step 20.—OR—

v If the Domino server was down while you performed the preceding steps,you must use one of the following methods to start the server:

Figure 23. Configure dialog box (Management Console)


Additional information: Always use one of the following methods to start aDomino server on Windows systems.– Use the IBM Tivoli Monitoring for Messaging and Collaboration user








23. Access the server configuration document in the Lotus Domino user interface.24. Paste the values you copied in Step 22 into the ServerTasks field, placing the

string value for the addin for this software (tivoliv46 or tivoliv50) as the firsttask named in the field.



Deleting a Domino Server object

ObjectiveTo delete a Domino server object (managed resource).

Background informationThis process deletes the server object that permits IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino to manage the associated server. Italso cleans up all modifications made to the system for managing this server withthis software, including removing entries within events, removing entries fromnotes.ini, and removing any program files placed on the endpoint.

Note: When you complete this procedure, the Domino server is no longerconfigured to be managed by this software. However, the Domino servercontinues to function as an endpoint in the Tivoli management region.

The Domino servers can be running while you perform this procedure.



Before you begin

When you finishIf you are deleting the last server object, you might want to completely uninstallIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino.

If you use a Lotus Domino Server configuration document to manage the Dominoserver and that server configuration document includes ServerTasks specifications,modify the document as follows:

Note: If you fail to make these modifications, the configuration documentperiodically generates a harmless error message stating that Lotus Dominois unable to locate the addin for this software, which is one of the followingvalues:v tivoliv46, if you are running Lotus Domino, Version 4.6.xv tivoliv50, if you are running Lotus Domino, Version 5.x

1. Access the server configuration document in the Lotus Domino user interface.2. Access the ServerTasks specification for the configuration document.3. Delete the string value for the addin for this software: tivoliv46 or tivoliv50.


Command line: Use one of the following commands to delete server objects froma Domino server:v wtmddeleteserver commandv wruntask command with the Delete Server task

See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for more information.

Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Delete Server. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Open the Policy Region window for the regions that contain the Domino

server.2. Select the icon of the Domino server that you want delete.3. Click Edit and select Delete to display the Delete Objects? dialog box.


4. Click Yes to delete the server object from the selected server.

Management Console:


2. Select the server whose server object you want to delete in the Server list of theServer tab.Additional information: Configured servers display a C in the State column.You can select multiple servers from which to delete server objects. Click in thecolumn to the left of the Server list to place a check mark beside the name ofeach server whose server object you want to delete.

3. Click Unconfigure in the toolbar above the server list to display theUnconfigure dialog box.

4. Do one of the following:v Select the option for the name of the specific server in the Unconfigure area.

—OR—v Select the All selected servers option to unconfigure multiple servers that

you have selected in Step 2.

Figure 24. Delete Objects? dialog box (Desktop)

Figure 25. Unconfigure dialog box (Management Console)


5. Click Execute.6. Click Yes in the confirmation dialog box to unconfigure the server or servers

and return to the Unconfigure dialog box.7. Review the results of the configuration in the Results column of the table in the

Results area of the Unconfigure dialog box.8. Click Close.


Chapter 4. Working with resource models

This chapter provides an overview of IBM Tivoli Monitoring, a suggested order forhow to set up IBM Tivoli Monitoring to work with Domino resource models inyour environment, and the steps for procedures necessary for setting up andrunning resource models.

Overview of IBM Tivoli MonitoringThe Tivoli Workbench is a programming tool for creating, modifying, debugging,and packaging resource models for use with IBM Tivoli Monitoring products.Samples of Best Practice Resource Models have also been provided for your usagewithin the Tivoli Workbench. These Resource Models are intended to be used asworking examples for your usage in creating new resource models. Customersneed to have a current Tivoli Maintenance & Support Contract to get assistancewith problem and issues relative to the operation of the Tivoli workbench.

IBM Tivoli Monitoring provides preconfigured best practices resource models andthe ability to modify these resource models to automate the monitoring of essentialresources such as hardware, software, or data entities. This allows you to detectbottlenecks and other potential problems and define automatic recovery fromcritical situations. This ability frees system administrators from manually scanningextensive performance data. The monitoring software integrates with other TivoliAvailability solutions, including Tivoli Business Systems Manager and TivoliEnterprise Console. This software was previously called Tivoli DistributedMonitoring (Advanced Edition).

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 resource models on the Tivoli desktop. A profilemanager is the top level of organization. Servers are subscribed to profile managers.These subscriptions provide the channel through which resource models aredistributed 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 othergrouping. 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 status and what to do when certain conditions are met. Some resource modelsprovide predefined settings and response actions, which you can adjust. Otherresource models require you to define all the settings. See the IBM Tivoli Monitoringfor Messaging and Collaboration: Lotus Domino Reference Guide for a description ofindividual settings.


Before running a resource model, you must subscribe the server resource to theprofile manager that contains the profile in which the resource model is stored.You can then distribute the profile to the resource. By default, resource models areset up to become active when you distribute them to subscribers. You can activateand deactivate resource models after they are distributed.

View the information being monitored by your resource models using the IBMTivoli Monitoring Web Health Console, Tivoli Enterprise Console, Tivoli EnterpriseData Warehouse, or Tivoli Business System Management.

Suggested guidelines for setting up your resource modelsTable 8 provides a list of the goals you can achieve using the procedures in thischapter in the order in which you should set up monitoring information. The tablealso tells where to locate information about the procedures for each goal.

As you become more familiar with ITM, you will discover additional ways ofworking with resource models that may better fit the needs of your environment.

For additional or advanced information on Distributed Monitoring in the Tivolienvironment, see the IBM Tivoli Monitoring User’s Guide.

Table 8. Goals and where to find procedures for working with IBM Tivoli Monitoring


1. Set up profile managers and profiles to organizeyour resource models. This makes the distributionof resource models more efficient. You might needto set up multiple profile managers and profileswithin the profile managers to meet the needs ofyour environment.

“Creating profile managers andprofiles” on page 55

2. Subscribe endpoints to the profile manager. Thisdetermines which resources receive a profile whenthe profile is distributed. Profiles contain resourcemodels to run against the endpoints (see Step 3).

“Subscribing resources to profilemanagers” on page 62

3. Populate each profile manager and profile withresource models for the resource that you want tomonitor. You can include resource models withdefault settings or resource models with modifiedsettings to best meet the needs of yourenvironment.

“Adding a default resource modelto a profile” on page 65

“Adding a custom resource modelto a profile” on page 69

4. Modify resource model settings. “Customizing indications” on page74

“Specifying tasks for an indication”on page 80

“Sending a notice when an eventoccurs” on page 83

“Customizing parameters” on page85

“Customizing a schedule for aresource model” on page 88

“Customizing data logginginformation” on page 93


Table 8. Goals and where to find procedures for working with IBM TivoliMonitoring (continued)


5. Creating custom resource models using the IBMTivoli Monitoring Workbench.

See the ″Creating resource modelsusing the IBM Tivoli MonitoringWorkbench″ appendix in the IBMTivoli Monitoring for Messaging andCollaboration: Lotus Domino ReferenceGuide.

6. For each profile in your profile manager, do thefollowing:v Specify the subscribers that you want to

distribute the monitoring profile to.v Distribute the profile.v Determine if you need to rerun any failed

distributions.

“Subscribing to notice groups” onpage 32

“Distributing a profile from thedesktop” on page 101

“Rerunning a failed distribution”on page 107

Creating profile managers and profiles

ObjectiveSet up profile managers and profiles so you can organize and distribute resourcemodels more efficiently. You might need to set up multiple profile managers andprofiles within the profile managers to meet the needs of your environment.

Background informationYou can create profile managers and profiles in the Messaging and Collaborationpolicy region or in any policy region nested within it. The installation routineautomatically creates this policy region and also the Domino Performance StationRegion policy region.

A 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. Theprofile managers in this product can be hierarchically organized. The profilemanager is the top level of the organization and contains specific profiles thatcontain specific resource models. Instances and databases are then subscribed tothe profile managers, which enable the monitoring information to be channeled tothose resources.

You can create an unlimited number of profile managers, but it is recommendedthat they reflect some logical or functional grouping of server resources or theorganizational structure of your business. For example, profile managers could belabeled Sales and Marketing, Administration and Finance, and Operations to reflectthe business of your organization.

Table 9 on page 56 lists the profile managers that exist by default in this product.These profile managers correspond to the roles of Domino servers, for exampleWeb servers, mail servers, or database servers. The profile managers containresource models that monitor server characteristics that are important to the role ofthe Domino server. For example, the Domino 4.6 SMTP MTA Servers profile

Chapter 4. Working with resource models 55

manager contains the Domino SMTP Mail Statistics Monitor resource model tomonitor mail statistics for the number of mail items in the SMTPMTA.Dead andthe SMTPMTA.Waiting states.

Table 9. Profile managers and their default resource models

Profile manager Resource models within the profilemanager by default

For servers that run Lotus Domino, Version 4.6.x

Domino 4.6 Application Servers None

Domino 4.6 Basic Servers Domino Server Availability

Domino Server Health

Domino 4.6 Mail Database Servers Domino Database Management

Domino 4.6 Mail Router Servers Domino Mail Statistics Monitor

Domino 4.6 News Servers None

Domino 4.6 SMTP MTA Servers Domino SMTP Mail Statistics Monitor

Domino 4.6 Web Servers None

For servers that run Lotus Domino, Version 5.x

Domino 5.0 Application Servers None

Domino 5.0 Basic Servers Domino Server Availability

Domino Server Health

Domino 5.0 IMAP Servers None

Domino 5.0 LDAP Servers None

Domino 5.0 Mail Database Servers Domino Database Management

Domino 5.0 Mail Router Servers Domino Mail Statistics Monitor

Domino 5.0 News Servers None

Domino 5.0 POP3 Servers None

Domino 5.0 SMTP Servers Domino SMTP Mail Statistics Monitor

Domino 5.0 Web Servers None

For servers that run Domino Performance Stations

Domino Performance Station Resource Models Each probe you create has a profile in thisprofile manager. Each profile contains allavailable resource models for probing. SeeChapter 6, “Working with DominoPerformance Stations” on page 147 formore information.

You can create a dataless profile manager that distributes profiles without regard tothe existence of a database on its subscribers. A dataless profile managerdistributes to the system files on endpoints and other managed resources that havea profile database. However, it bypasses the profile database on these systems.Therefore, profiles are available only with database profile managers. A profilemanager (database or dataless) cannot subscribe to a dataless profile manager.Likewise, dataless profile managers cannot distribute to other profile managersbecause they require profiles to be written to a profile database.



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

When you finishSubscribe endpoints to the profile manager to determine which resources receive aprofile when the profile is distributed. See “Subscribing resources to profilemanagers” on page 62.


Command line:

1. Use the wcrtprfmgr command to create a profile manager. For example, tocreate a profile manager called ProfMgr2 in the TestRegion policy region, enterthe following command:wcrtprfmgr @PolicyRegion:TestRegion ProfMgr2

2. Use the wsetpm command to make the policy manager operate in datalessmode. For example, to make the profile manager ProfMgr2 dataless, enter thefollowing 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 dialog box by double-clicking the policy region icon:

2. Click Create and select Profile Manager to display the Create ProfileManager dialog box.

Figure 26. Policy region icon


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.Additional information: The policy region in Figure 28 contains two profilemanager icons, manufacturing and operations. The feathers under theoperations profile manager indicate that it is a dataless profile manager.

5. Click Create & Close to close the Create Profile Manager dialog box.6. Double-click the profile manager icon to display the Profile Manager dialog

box.

Figure 27. Create Profile Manager dialog box (Desktop)

Figure 28. Dataless profile manager icon (Desktop)


7. Click Create and select Profile to display the Create Profile dialog box.

Figure 29. Profile Manager dialog box (Desktop)


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. An icon for the new profile is displayed in the Profilesarea of the Profile Manager window.

Management Console:

1. Do the following to access the policy region in which you want to create aprofile manager or to access the profile manager in which you want to create aprofile.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile

managers.

Note: Since a profile resides in a profile manager, decide which profilemanager to put the new profile you create in, or create a new profilemanager before you create a new profile.

2. If you want to create a profile manager, do the following:a. Click Create in the Profile Managers Tools bar on the right side of the

Configuration tab window to display the Create Profile Manager dialogbox.

Figure 30. Create Profile dialog box (Desktop)

Figure 31. Create Profile Manager dialog box (Management Console)


b. Select the policy region in which you want the profile manager to residefrom the Policy Region drop-down list.

c. Type the name of the profile manager in the Profile Manager Name textbox.Additional information: The policy region name can include letters,underscores, dashes, periods, and spaces. The name must be unique withinthe local Tivoli management region.

d. Click OK to create the profile manager.Additional information: The name of the new profile manager is displayed inthe tree view under the policy region you specified.

3. If you want to create a profile, do the following:a. Click the profile manager in which you want the profile to reside in the tree

view.Additional information: If the profile manager already has profiles, a list ofthe profile names is displayed in the Profiles list.

b. Click Add Profile in the menu bar under the Profiles tab to display theAdd Profile dialog box is displayed, with Tmw2kProfile in the ProfileType drop-down listAdditional information: Tmw2kProfile is the profile type that containsresource models.

c. Type the name of the profile you want to add in the Profile Name text box.d. Click OK.

Additional information: The name and type of the profile is displayed in theProfiles list.

Delete a profile

1. Select the profile you want to delete from the Profiles list.2. Click Delete Profile in the menu bar between the Profiles tab and the Profiles

list to display the Delete Profile dialog box, with a question, ″Proceed to deletethese profiles?″, and a field with the name of the selected profile.

Figure 32. Add Profile dialog box (Management Console)


3. Click OK to delete the profile.

Delete a profile manager

Note: The profile manager must be empty for you to delete it.1. Select the profile manager you want to delete from the tree view.2. Click Delete in the Profile Managers Tools menu to display the Delete Profile

Manager dialog box, with the name of the selected profile manager in theProfile Manager drop-down list.

3. Click OK to delete the profile manager.

Subscribing resources to profile managers

ObjectiveTo add managed resources to a monitoring profile so administrators can definewhich resources 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 aprofile, you must add the subscriber to the profile manager.

Required authorization roleadmin

Before you beginCreate a monitoring profile with monitoring sources. Refer to “Creating profilemanagers and profiles” on page 55 for information.

Figure 33. Delete Profile dialog box (Management Console)

Figure 34. Delete Profile Manager dialog box (Management Console)


When you finishv Add default or custom resource models. Refer to “Adding a default resource

model to a profile” on page 65 and “Adding a custom resource model to aprofile” on page 69.

v Specify the subscribers that you want to distribute the monitoring profile to.Refer to “Subscribing to notice groups” on page 32 for information

v Distribute the monitoring profile to the subscribed endpoints. Refer to“Distributing a profile from the desktop” on page 101 for information.

v


Command line: Use the wsub command to add subscribers to the profilemanager.

For example, to add a Domino server called DominoMail01 as a subscriber to theprofile manager MailMonitors, enter the following command:wsub @ProfileManager:MailMonitors @LotusDominoServer:DominoMail01

For additional information about this command, see the Tivoli ManagementFramework, Version 3.7.1: User’s Guide.

Desktop:

1. Double-click a policy region icon to display the Policy Region dialog box.2. Double-click a profile manager icon to display the Profile Manager dialog box.3. Click Profile Manager and select Subscribers to display the Subscribers dialog

box.

4. Select the subscribers to receive the profile distribution from the Available tobecome Subscribers scrolling list.

Figure 35. Subscribers dialog box (Desktop)


5. Click the left-arrow to move the selected subscribers to the Current Subscribersscrolling list.

6. Click Set Subscriptions & Close to add the subscribers. Subscribers aredisplayed in the Subscribers field of the Profile Manager dialog box as shownin this example.

Management Console:

1. Do the following to access the profile manager to which you want to subscribean endpoint.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile

managers.c. Click the policy region in the tree view that contains the profile manager.

Additional information: A list of profile managers is displayed in the treeview.

d. Click the profile manager to which you want to subscribe an endpoint.Additional information: A list of profiles is displayed in the middle section ofthe window under the Profiles subtab.

2. Click the Subscribers tab that is next to the Profiles tab in the middle sectionof the window to display a list of subscribers in the middle section of thewindow under the Subscribers tab.

3. Click Edit Subscriber List on the menu bar between the list of subscribers andthe Subscribers tab to display the Edit Subscriber List with the following twolists.v Available Subscribers

v Current Subscribers

4. Do the following to move subscribers between the Available Subscribers listand the Current Subscribers as needed:a. Select one or more subscribers to move.b. Click the left or right arrow to move the subscribers.

5. Click OK to close the Edit Subscriber List dialog box.

Figure 36. Edit Subscriber List dialog box (Management Console)


Additional information: The names of the subscribers appear in the middlesection of the window under the Subscribers tab.

Adding a default resource model to a profile

ObjectiveTo add a resource model to a profile using its default values so you can includethem in an IBM Tivoli Monitoring profile to begin monitoring resourcesimmediately. This is the recommended way to use the best practices resourcemodels.

Background informationA resource model captures and returns information about a resource or application.Resource models are set up and distributed to Lotus Domino Server objects. Eachresource model monitors multiple resources. Resource models are grouped intocategories that represent platforms, for example, Domino, OS400, Solaris, Unix -Linux, and Windows. You choose resource models from a category 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. You can revise the default settings in the future as you refine theinformation you want to collect.

It is recommended that you put all of the monitoring sources that you are going todistribute to the same endpoint in a single profile because the distribute action ison a per-profile basis.

Refer to the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoReference Guide for detailed information, including default settings, about eachresource model.


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

profiles” on page 55 for information.v Subscribe endpoints to the profile manager. This determines which resources

receive a profile when the profile is distributed. See “Subscribing resources toprofile managers” on page 62.

When you finishFor each profile in your profile manager, do the following:v Specify the subscribers that you want to distribute the monitoring profile to. See

“Subscribing to notice groups” on page 32v Distribute the profile. See “Distributing a profile from the desktop” on page 101.v Determine if you need to rerun any failed distributions. See “Rerunning a failed

distribution” on page 107.


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


For more information about this command, see the IBM Tivoli Monitoring, Version5.1.0: User’s Guide.

Desktop:

1. Open the Policy Region dialog box by doing the following:a. Double-click the policy region icon to display the policy region.b. Double-click the profile manager icon to display the profile manager.c. Double-click the profile icon to which you want to add a default resource

model to display the IBM Tivoli Monitoring Profile dialog box.

2. Click Add with Defaults to display the Add Default Models to Profile dialogbox.

Figure 37. IBM Tivoli Monitoring Profile dialog box (Desktop)


3. Select the category of resource models from the Category drop-down list.4. Select the resource model that you want to add from the Select the models to

insert list.Additional information: You can select more than one resource model at at time.

5. Click Add & Close. The resource models are added to the IBM TivoliMonitoring Profile dialog box.

Management Console:

1. Do the following to access the policy region, profile manager, and profile towhich you want to add a resource model.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile to which you want toadd a resource model.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsor events is displayed under the Profiles list.

Figure 38. Add Default Models to Profile dialog box (Desktop)


2. Click Add Resource Model in the menu bar directly above the ResourceModel list to display the Add Resource Model window with tabs is displayed,with the Basics tab dialog box on top.

Figure 39. Configuration window Profiles tab (Management Console)


3. Select the category for the resource model you want to add from the Categorydrop-down list.

4. Select the resource model you want to add from the Resource Modeldrop-down list.

5. Click OK to add the resource model with all of its default settings to theprofile.Additional information: The name and category of the resource model isdisplayed in the list of resource models with a check mark in the enabled checkbox.

Adding a custom resource model to a profile

ObjectiveTo add a customized resource model so you can specify the type of platform, thecycle time, the threshold values, and other settings that meet the needs of yourenvironment.

Background informationA resource model captures and returns information about a resource or application.Resource models are set up and distributed to Lotus Domino Server objects. Inaddition to using the predefined resource models that are installed with theproduct, you can customize any of the predefined resource models. Each resourcemodel monitors a different resource.

Resource models are grouped into categories that represent platforms, for example,Domino, OS400, Solaris, Unix - Linux, and Windows. You choose resource modelsfrom a category to add to a profile and customize based on the resources you want

Figure 40. Add Resource Model window (Management Console)


to monitor and the settings you want to use to monitor those resources. If youwant to modify these categories or add other categories, use the IBM TivoliMonitoring Workbench.

When you add a custom resource model, you can modify the settings for thefollowing resource model parts:v Cycle Timev Thresholdsv Indicationsv Tasks associated with indicationsv Parametersv Schedulev Logging

It is recommended that you put all of the monitoring sources that you are going todistribute to the same endpoint in a single profile because the distribute action ison a per-profile basis.

Refer to the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoReference Guide for detailed information, including the default settings, about eachmonitoring collection and monitoring source.


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

profiles” on page 55 for information.v Subscribe endpoints to the profile manager. This determines which resources

receive a profile when the profile is distributed. See “Subscribing resources toprofile managers” on page 62.

When you finishFor each profile in your profile manager, do the following:v Specify the subscribers that you want to distribute the monitoring profile to. See

“Subscribing to notice groups” on page 32v Distribute the profile. See “Distributing a profile from the desktop” on page 101.


Command line: Use the wdmeditprf command to add a customized resourcemodel to a profile.


Desktop:

1. Open the Policy Region dialog box by doing the following:a. Double-click the policy region icon to display the policy region.b. Double-click the profile manager icon to display the profile manager.


c. Double-click the profile icon to which you want to add a customizedresource model.

2. Click Add from the IBM Tivoli Monitoring Profile dialog box to display theAdd Resource Models to Profile dialog box.

3. Select the category of the resource model from the Category drop-down list.4. Select the resource model that you want to customize from the Resource Model

drop-down list.5. Set the frequency (in seconds) with which the resource model monitors the data

in the Cycle Time text box.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 dialog box above the description displays thecurrently assigned threshold value.

b. Change the currently assigned threshold value to a value appropriate toyour requirements.Additional information: See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for the default values.

c. Click Apply to set and display the new value in the Threshold Value dialogbox.

7. Click one or more of the options along the bottom of the Add ResourceModels to Profile dialog box one at a time to change the following settings:

Figure 41. Add Resource Models to Profile dialog box (Desktop)


Additional information: An option is not active if you cannot customize thesettings for that part of the resource model. If you choose not to customize asetting, the resource model will retain the default settings.v Indications (occurrences, holes, where to send events, severity, tasks)

See “Customizing indications” on page 74.See “Specifying tasks for an indication” on page 80.

v ParametersSee “Customizing parameters” on page 85 for how to change the parametersfor the resource model.

v LoggingSee “Customizing data logging information” on page 93 for how to enablelogging and how to aggregate data.

v ScheduleSee “Customizing a schedule for a resource model” on page 88 for how toset the schedule for running a resource model.

8. Click Add & Close to save your changes. The IBM Tivoli Monitoring Profiledialog box now shows the customized resource model.

Management Console:

1. Do the following to access the policy region, profile manager, and profile towhich you want to add a customized resource model.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile to which you want toadd a resource model.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsor events is displayed under the Profiles list.

2. Click Add Resource Model in the menu bar directly above the ResourceModel list to display the Add Resource Model window, with the Basics tabdialog box on top.


3. Select the category of the resource model you want to customize and add fromthe Category drop-down list.

4. Select the resource model you want to customize and add from the ResourceModel drop-down list.

5. Change the Cycle Time to the number of seconds you want to lapse betweeneach of the times that the resource model runs.

6. If the resource model has one or more thresholds and you want to change athreshold value, change the number in the text box next to the name of thethreshold.Additional information: See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for the default values.

7. Click one or more of the other tabs one at a time to change the followingsettings:Additional information: A tab is not active if you cannot customize the settingsfor that tab. If you choose not to customize a setting, the resource model willretain the default settings.v Indications (occurrences, holes, where to send events, severity, tasks)




v Schedule

Figure 42. Add Resource Model window with Basics tab dialog box (Management Console)


See “Customizing a schedule for a resource model” on page 88 for how toset the schedule for running a resource model.

8. Click OK to add the customized resource model with all of its customizedsettings.Additional information: The name and category of the customized resource modelis displayed in the list of resource models with a check mark in the enabledcheck box.

Customizing indications

ObjectiveTo modify the occurrences, holes, which tasks to run, where to send events, andevent severity aspects of indications so you can customize a resource model togenerate an event that will notify you when a monitored resource is notperforming as needed.

Background informationEach resource model generates an indication if certain conditions defined by theresource model thresholds are not satisfied during the monitoring cycle. Eachresource model has its own algorithm to determine the combination of settings thatgenerate an indication.

An event verifies 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 might not pose a threat toother processes if the high usage is not repeated. However, an indication thatpersists over several cycles is more likely a problem. Thus, an event defines thenumber of consecutive occurrences of the indication.

You can customize the following values for indications and events:v Occurrences

Refers to a cycle during which an indication occurs for a given resource model.Specifies the number of consecutive times the problem occurs before thesoftware generates an indication. You can change this value to specify thenumber of times a problem occurs before an indication generates.

v Holes

Refers to a cycle during which an indication does not occur for a given resourcemodel. In other words, none of the conditions specified for the generation of anyindication are met. This does not mean that none of the thresholds are exceeded.Determines how many cycles that do not produce an indication can occurbetween cycles that do produce an indication. This determines if the occurrencesof an indication are consecutive. Each cycle without an indication is termed ahole. For example, an event that has a value of two holes means that when up totwo cycles occur without an indication between any two cycles with anindication, the cycles with an indication are considered consecutive.Use the value for the Number of Holes in conjunction with the Number ofOccurrences parameter and the Cycle Time to define a time window for thegeneration of an event. If, for example, you define Cycle Time as 10 seconds,Number of Occurrences as 5, and Number of Holes as 2, the time that mustelapse before an event occurs is between 50 and 130 seconds. The minimumelapsed time is the number of occurrences multiplied by the cycle time. Themaximum time window assumes that the maximum number of holes occursbetween each pair of occurrences, and is determined by the following equation:TW=CT x (Oc + (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 holesv Send TEC Events

Specifies that if an event occurs, the specified event server receives a messagefrom Tivoli Enterprise Console if you have Tivoli Enterprise Console installed.

Note: For IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino Tivoli Business Systems Manager receives the event if TivoliEnterprise Console and Tivoli Business Systems Manager are bothinstalled.

v SeverityIndicates how serious an event is if it is triggered: fatal, critical, warning,harmless, minor.

v Execute TasksSpecifies which tasks you want to execute.


Before you beginv Set up profile managers and profiles to organize your resource models. See

“Creating profile managers and profiles” on page 55.v Subscribe endpoints to the profile manager. See “Subscribing resources to profile

managers” on page 62.v Add a resource model that you can modify to each profile manager and profile.

See “Adding a custom resource model to a profile” on page 69.

When you finish1. Modify any other resource model settings that you want to change:

v Tasks. See “Specifying tasks for an indication” on page 80.v Parameters. See “Customizing parameters” on page 85.v Schedules. See “Customizing a schedule for a resource model” on page 88.v Logging. See “Customizing data logging information” on page 93.

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

See “Subscribing to notice groups” on page 32v Distribute the profile. See “Distributing a profile from the desktop” on page

101.


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



Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Double-click the policy region icon to display the policy region.b. Double-click the profile manager icon to display the profile manager.c. 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 dialog box.3. Click Edit to display the Edit Resource Model dialog box.

4. Click Indications to display the Indications and Actions dialog box and theindications relevant to the selected resource model.

Figure 43. Edit Resource Model dialog box (Desktop)


5. Select the indication you want to customize.6. Apply the changes to the values that are relevant for your requirements as

described in the background information of this procedure 74:v Send Tivoli Enterprise Consolev Send Tivoli Business Systems Managerv Occurrencesv Holesv Severity

Additional information: See IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino Reference Guide for the default values.

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

Management Console:

1. Access the resource model you want to customize by doing the following:a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile

managers.c. Click the policy region in the tree view that contains the profile manager to

display a list of profile managers is displayed in the tree view.d. Click the profile manager that contains the profile for the resource model

you want to customize.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Select the resource model you want to customize.

Figure 44. Indications and Actions dialog box (Desktop)


2. Click Edit Resource Model in the menu bar directly above the list of resourcemodels to display the Edit Resource Model window with the Basics tab dialogbox on top.

3. Click the Indications tab to display the Indications tab dialog box.Additional information: You can perform this step and the remaining steps of thisprocedure from both the Add Resource Model and Edit Resource Modeldialog boxes. See IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino Reference Guide for the default values.

Figure 45. Edit Resource Model window (Management Console)


4. Do the following to change the number of occurrences and holes:a. Click the Occurrence field or the Holes field next to the indication for

which you want to change the number of occurrences or holes.b. Enter the desired number of occurrences or holes.

5. Select the TEC check box to send events to the Tivoli Enterprise Console ifTivoli Enterprise Console is installed.Additional information: If both Tivoli Enterprise Console and Tivoli BusinessSystems Manager are installed, the indications also sends the event to TivoliBusiness Systems Manager.

6. Do the following to change the severity of the event:a. Click the Severity field for the indication that generates the event for which

you want to change severity.b. Select one of the following severity levels from the Severity drop-down list:

v Fatal

v Critical

v Warning

v Harmless

v Minor

Figure 46. Indications tab dialog box (Management Console)


7. Do one of the following:v Click another tab to customize other settings for the resource model.

—OR—v Click OK to save the customized settings for occurrences, holes, sending

events, and event severity.Additional information: Clicking OK closes the Add Resource Model or EditResource Model dialog box.

Note: You also set the tasks and built-in actions for a resource model from theIndications tab. Use the following procedure, “Specifying tasks for anindication” on page 80 to specify tasks. Built-in actions are disabled for allDomino resource models because there are none.

Specifying tasks for an indication

ObjectiveTo specify a task so you can determine corrective or reporting tasks for anindication.

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.

See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoReference Guide for detailed information about the tasks that you can associatewith indications.


Before you begin1. Set up profile managers and profiles to organize your resource models. See

“Creating profile managers and profiles” on page 55.

Figure 47. Severity drop-down list (Management Console)


2. Subscribe endpoints to the profile manager. See “Subscribing resources toprofile managers” on page 62.

3. Add a resource model that you can modify to each profile manager and profile.See “Adding a custom resource model to a profile” on page 69.

When you finish1.

Modify any other resource model settings that you want to change:v Indications. See “Customizing indications” on page 74.v Parameters. See “Customizing parameters” on page 85.v Schedules. See “Customizing a schedule for a resource model” on page 88.v Logging. See “Customizing data logging information” on page 93.



101.v Determine if you need to rerun any failed distributions. See “Rerunning a

failed distribution” on page 107.




Desktop:

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


Monitoring Profile dialog box.3. Click Edit to display the Edit Resource Model dialog box.4. Click Indications to display the Indications and Actions dialog box 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 dialog box.6. Click Tasks in the Action List area of the Indications and Actions dialog box

to display the Tasks dialog box.


7. Double-click the appropriate task library from the scroll list of the Librariespanel. The tasks contained in the library are displayed in the Tasks panel.

8. Double-click the appropriate task in the Tasks panel.9. Specify the appropriate parameters in the Configure Task dialog box.

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 dialog box.

Management Console:

1. Access the resource model for which you want to specify tasks by do thefollowing.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the resource modelyou want to customize.

Figure 48. Tasks dialog box (Desktop)


Additional information: A list of profiles is displayed in the middle sectionof the Configuration window under the Profiles tab. A list of resourcemodels is displayed under the Profiles list.

e. Select the resource model for which you want to specify tasks.f. Click Edit Resource Model in the menu bar directly above the list of

resource models to display the Edit Resource Model set of tabbed dialogboxes, with the Basics dialog box on top.

2. Click the Indications tab to display the Indications tab dialog box.Additional information: You can perform this step and the remaining steps ofthis procedure from both the Add Resource Model and Edit Resource Modeldialog boxes.

3. Click ... in the Tasks column for the indication for which you want to specifytasks to display the Task Configuration dialog box.

4. Select the library that contains the task you want to specify from the Librarydrop-down list.

5. Select the task you want to specify from the Name drop-down list.6. If the Arguments text box is present, type any arguments for the task.7. Click Update to add the task to the indication.8. If you need to remove a task in the Current Tasks list, do the following:

a. Click the task.b. Click Remove.

9. If you need to re-display the default Library and Name text boxes and clearthe Arguments text box from the dialog box, click Clear.


—OR—v Click OK to save the customized settings for the tasks.

Additional information: Clicking OK closes the Add Resource Model or EditResource Model dialog box.

Sending a notice when an event occurs

ObjectiveTo set up tasks that send notices in response to events so you can take theappropriate actions or responses.

Figure 49. Task Configuration dialog box (Management Console)


Background informationTo set up tasks that send notices when an event occurs, you use the procedure,“Specifying tasks for an indication” on page 80. In this procedure, you specify theIBM Tivoli Monitoring Utility Tasks library and the send notices task.



“Creating profile managers and profiles” on page 55.2. Subscribe endpoints to the profile manager. See “Subscribing resources to

profile managers” on page 62.3. Add a resource model that you can modify to each profile manager and profile.


When you finish1. Modify any other resource model settings that you want to change:

v Indications. See “Customizing indications” on page 74.v Parameters. See “Customizing parameters” on page 85.v Schedules. See “Customizing a schedule for a resource model” on page 88.v Logging. See “Customizing data logging information” on page 93.


See “Subscribing to notice groups” on page 32.v Distribute the profile. See “Distributing a profile from the desktop” on page

101.

Procedure



Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Double-click the policy region icon to display the policy region.b. Double-click the profile manager icon to display the profile manager.c. 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 display the Edit Resource Model dialog box.4. Click Indications to display the Indications and Actions dialog box 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 dialog box.6. Click Tasks in the Action List dialog box to display the Tasks dialog box.7. Double-click the IBM Tivoli Monitoring Utility Tasks library in the scroll

list of the Libraries panel. The tasks in the IBM Tivoli Monitoring UtilityTasks library are displayed in the Tasks panel.


8. Double-click dm_mn_send_notice in the Tasks panel to display the ConfigureTask dialog box.

9. Specify the appropriate parameters in the Configure Task dialog box.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 dialog box.

Management Console:

1. Access the indication for the task you want to set up to send notices when anevent occurs by doing the following:a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the resource modelyou want to customize.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Select the resource model that contains the task.f. Click Edit Resource Model in the menu bar directly above the list of

resource models to display the Edit Resource Model set of tabbed dialogboxes, with the Basics dialog box on top.

g. Click the Indications tab to display the Indications tab dialog box.h. Click ... in the Tasks column for the indication for which you want to

specify notices to display the Task Configuration dialog box.2. Select the IBM Tivoli Monitoring Utility Tasks library from the Library

drop-down list.3. Select the dm_mn_send_notice task in the Name drop-down list.4. Type the name of the notice group in the Notice Group text box.5. Type the level of the priority in the Priority text box.6. Click Update to add the task to the Current Tasks list.7. Click OK to save the task and close the Task Configuration dialog box.8. Run the wlsnotif -g command to see the available notice groups.

Customizing parameters

ObjectiveTo customize the parameters of a resource model so you can optimize themonitoring 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.







When you finish1.

Modify any other resource model settings that you want to change:v Indications. See “Customizing indications” on page 74.v Tasks. See “Specifying tasks for an indication” on page 80.v Schedules. See “Customizing a schedule for a resource model” on page 88.v Logging. See “Customizing data logging information” on page 93.



101.




Desktop:



Monitoring Profile dialog box.3. Click Edit to display the Edit Resource Model dialog box.4. Click Parameters.


5. Select the type of parameter from the Name drop-down list in the Parametersdialog box.

6. Add or delete the parameter values as required by checking or clearing theboxes.

7. Click Apply Changes and Close to save your changes.

Management Console:

1. Do the following to access the resource model for which you want to customizeparameters.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the resource modelyou want to customize.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Select the resource model for which you want to customize parameters.f. Click Edit Resource Model in the menu bar directly above the list of

resource models to display the Edit Resource Model window, with theBasics tab dialog box on top.

2. Click the Parameters tab to display the Parameters tab dialog box.Additional information: You can perform this step and the remaining steps of thisprocedure from both the Add Resource Model and Edit Resource Modeldialog boxes.

Figure 50. Parameters dialog box (Desktop)


3. Select the name of the parameter that you want to change from the Namedrop-down list.Additional information: The default values for the parameter is displayed belowthe name of the parameter. For example, one or more values separated by newline breaks is displayed in the Value text box. Also, a description of theparameter is displayed in the Parameter Description field.

4. Type (or select) the desired values for the parameters.Additional information: For example, type one or more string or numeric valuesin the Value text box.


—OR—v Click OK to save the customized settings for the parameters.


Customizing a schedule for a resource model

ObjectiveTo customize the schedule for a resource model so you can determine the timeperiods and days when monitoring takes place.

Background informationIBM Tivoli Monitoring contains a scheduling feature that enables you to determinewhen monitoring takes place and specific scheduling rules. You can divide theoverall collection period into active and inactive intervals by applying one or moreschedule rules.

Figure 51. Parameters tab dialog box (Management Console)


The scheduling rules enable you to define time periods on specific weekdaysduring which monitoring takes place. You can define any number of rules thatenable you to set up a complex pattern of resource monitoring for a profile andcovers the periods that you want to monitor.

The scheduled times are always interpreted as local times, enabling you to set up asingle rule that monitors 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.


Before you begin1. Set up profile managers and profiles to organize your resource models. This

makes the distribution of resource models more efficient. You might need to setup multiple profile managers and profiles within the profile managers to meetthe needs of your environment. See “Creating profile managers and profiles”on page 55.

2. Subscribe endpoints to the profile manager. This determines which resourcesreceive a profile when the profile is distributed. See “Subscribing resources toprofile managers” on page 62.

3. Add a resource model that you can modify to each profile manager and profile.See “Adding a custom resource model to a profile” on page 69.

When you finish1.

Modify any other resource model settings that you want to change:v Indications. See “Customizing indications” on page 74.v Tasks. See “Specifying tasks for an indication” on page 80.v Parameters. See “Customizing parameters” on page 85.v Logging. See “Customizing data logging information” on page 93.



101.v Determine if you need to rerun any failed distributions. See “Rerunning a

failed distribution” on page 107.




Desktop:

1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:a. Double-click the policy region icon to display the policy region.


b. Double-click the profile manager icon to display the profile manager.c. Double-click the profile icon to which you want to customize a resource


Monitoring Profile dialog box.3. Click Edit to display the Edit Resource Model dialog box.4. Click Schedule to display the Scheduling dialog box.

Additional information: The Scheduling dialog box contains the following groupsof options:

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.

5. Clear the Always check box if you want to customize the schedule.6. If you clear the Always check box, do the following to customize the schedule:

a. Click New Rule in the Schedule Rules area.

Figure 52. Scheduling dialog box (Desktop)


b. Type a name for the rule in the Rule Name text box of the Rule Editorpanel.

c. Select one or more items in the weekday list to specify the day or days onwhich 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.

d. Set the Start Date and Stop Date for the collection activity.e. Set the Start Time and Stop Time for the collection activity or select the All

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

f. Click Set Rule. Your new rule is displayed 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 section ofthe dialog box. If the Schedule Rules list contains more than one schedulerule, all the time intervals are respected, and rules are combined by addingtogether the time periods they define. For example, if you specify a rule thatrequests monitoring between 8:00 and 14:00 every day and another thatrequests all-day monitoring on Fridays, the sum of the two rules givesall-day monitoring only on Fridays, and monitoring between 8:00 and 14:00on all other days. If the second rule instead requested monitoring from 12:00to 18:00 on Fridays, the sum of the rules would give monitoring between8:00 and 18:00 on Fridays and between 08:00 and 14:00 on all other days.

7. Click Modify & Close to save your rule and close the Scheduling dialog box.

Management Console:

1. Do the following to access the resource model for which you want to customizethe schedule.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the resource modelfor which you want to customize the schedule.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Select the resource model for which you want to customize the schedule.f. Click Edit Resource Model in the menu bar directly above the list of

resource models to display the Edit Resource Model window, with theBasics dialog box on top.

2. Click the Schedule tab to display the Schedule tab dialog box.


Additional information: You can perform this step and the remaining steps of thisprocedure from both the Add Resource Model and Edit Resource Modeldialog boxes.

3. Click one of the following scheduling options:v Always

v Custom

4. If you select Custom do the following:

Note: If you select Custom, you must define at least one schedule rule fromthe Schedule Rule dialog box.

a. Set the From date and the To date.b. Add a new schedule rule, edit a schedule rule, or delete a schedule rule as

follows:v If you want to add a new schedule rule, do the following:

1) Click New.Additional information: The Schedule Rule dialog box is displayed.

2) Type a name for the schedule rule in the Name text box.3) Select the days on which you want the resource model to run.4) Click one of the timeframes:

– All Day

– Custom

5) If you clicked Custom, set the dates in the date fields next to theCustom option.

6) Click OK to save the schedule rule.v If you want to edit a schedule rule, do the following:

Figure 53. Schedule tab dialog box for customizing a resource model (ManagementConsole)


1) Click the name of the schedule rule you want to change.2) Click Edit.

Additional information: The Schedule Rule dialog box is displayed.3) Select the days on which you want the resource model to run.4) If you want to change the time frame, click one of the timeframes:

– All Day

– Custom

5) If you clicked Custom, set the time in the time field next to theCustom radio button.Additional information: You can set the time by typing the time rangeor clicking the clock to display the drop-down time setting feature.

6) Click OK to save the edited schedule rule.v If you want to delete a schedule rule, do the following:

1) Click the name of the schedule rule you want to change.2) Click Delete.

Additional information: The schedule rule disappears.3) Click OK to save the customized schedule.


—OR—v Click OK to save the customized settings for the schedule.


Customizing data logging information

ObjectiveTo customize data logging information so you can log data collected by a resourcemodel and write it in a local database.

Background informationYou can view the log data through the Web Health Console after you write it in alocal database. You can store one of the following types of data 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

TEDW dataTEDW Data aggregates the resource model data for use in the TivoliEnterprise Data Warehouse.







When you finish1.

Modify any other resource model settings that you want to change:v Indications. See “Customizing indications” on page 74.v Tasks. See “Specifying tasks for an indication” on page 80.v Parameters. See “Customizing parameters” on page 85.v Schedules. See “Customizing a schedule for a resource model” on page 88.



101.




Desktop:



Monitoring Profile dialog box.3. Click Edit to display the Edit Resource Model dialog box4. Click Logging to display the Logging dialog box.


5. Select the Enable Data Logging check box in the Data Logging Settings paneto enable logging.Additional information: This enables the Aggregate Data and Historical Periodoptions.

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. Average is the default setting.

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.

Note: You cannot choose both aggregate data and raw data at the same time,or aggregate data and TEDW data at the same time.

8. Set the Hours and Minutes of the Historical Period to the required values.

Figure 54. Logging dialog box (Desktop)


9. Click Apply Changes and Close to save your changes and close the Loggingdialog box.

Management Console:

1. Do the following to access the resource model for which you want to log data.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the resource modelfor which you want to log data.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Select the resource model for which you want to log data.f. Click Edit Resource Model in the menu bar directly above the list of

resource models.Additional information: The Edit Resource Model set of tabbed dialog boxes isdisplayed, with the Basics dialog box on top.

2. Click the Logging tab to display the Logging tab dialog box.Additional information: You can perform this step and the remaining steps of thisprocedure from both the Add Resource Model and Edit Resource Modeldialog boxes.

3. Enable logging by doing the following:a. Select the Enable Data Logging check box.

Additional information: Enabling logging activates the options for aggregatingdata.

b. Set the Historical Period by selecting the hours and minutes from theHours and Minutes drop-down lists.


4. If you want to summarize (aggregate) the data, do the following:a. Select the Aggregate Data option to activate the Aggregation options.b. Set the Aggregation Period by selecting the hours and minutes from the

Hours and Minutes drop-down lists.c. Check one of the following Data to Aggregate check boxes to select a

function to perform on the numerical data collected during the aggregationperiod before it is written to the database:

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. Average is the default.

5. If you want to log raw data, do the following:a. Select Other Data.b. Select Raw Data.c. Optional: If Tivoli Enterprise Data Warehouse is installed and Raw Data is

selected, you can check the TEDW Data option to store the raw data for usein Tivoli Enterprise Data Warehouse.

Note: You cannot choose both aggregate data and raw data at the sametime, or aggregate data and TEDW data at the same time.


—OR—

Figure 55. Logging tab dialog box (Management Console)


v Click OK to save the customized settings for logging data.Additional information: Clicking OK closes the Add Resource Model or EditResource Model dialog box.

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.


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

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

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

profile” on page 65 and“Adding a custom resource model to a profile” on page69 for information.

v Distribute the profile. See “Distributing a profile from the desktop” on page 101for information.

v See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoReference Guide for detailed information about each resource model.

When you finishNone

ProcedureYou can perform this procedure from the 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.









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 informationOpen an endpoint window from the desktop to see if a resource model has beendistributed to it.









When you finishNone

ProcedureYou can perform this procedure from the Tivoli desktop only.

Desktop:

1. Open the Profile Manager dialog box 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 dialog

box.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 TME 10 Distributed

Monitoring Profile Properties window, which lists the resource modelsdistributed 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 under the followingcircumstances:v When the database is down and the RDBMS State resource model has not

run, IBM Tivoli Monitoring shows the state of the resource model asrunning.

v When resource models are first distributed to a profile endpoint, theresource models all show running, even though they have not beenexecuted. The resource models show valid states after they are executedby the IBM Tivoli Monitoring engine.

Use the Tivoli command line to determine which resource models are running onan endpoint.









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.

Distributing a profile from the desktop

ObjectiveTo set distribution options for a profile so you can distribute profiles to specifiedsubscribers.

Background informationProfile managers and profile endpoints can reside at multiple levels in thedistribution hierarchy. You can distribute profiles at two levels: next level and alllevels. When you distribute to the next level of subscribers, only the subscribersthat are one level lower in the hierarchy receive the profiles. When you distributeto all levels, profile endpoints at all levels in the hierarchy receive the profiles.

If you distribute to the next level of subscribers, the distribution process affectsonly the next lower level in the hierarchy. You must distribute from profilemanagers residing at more than one level to reach all the profile endpoints. Also, ifyou distribute to the next level of subscribers from a profile manager to a profileendpoint only the profile endpoint database updates. The actual system files donot update. You can then make any necessary local modifications in the profileendpoint. You must perform a distribution from the profile endpoint to affect theactual system files and databases.

Example: Profile manager A has two subscribers, managed node Tom and profilemanager B, and profile manager B has one subscriber, managed node Ming. If youdistribute to all levels of subscribers, profile manager A distributes profile copies tomanaged node Tom, profile manager B, and managed node Ming. If you distributeto the next level of subscribers, profile manager A distributes profile copies only toprofile manager B and managed node Tom. Managed node Ming, residing onelevel below profile manager B, does not receive the profile copies. For managednode Ming to receive the profile copies, you must also distribute from profilemanager B.



“Creating profile managers and profiles” on page 55.


2. Subscribe endpoints to the profile manager. See “Subscribing resources toprofile managers” on page 62.

3. Add a default or custom resource model each profile manager and profile. See“Adding a custom resource model to a profile” on page 69.

4. Specify the subscribers that you want to distribute the monitoring profile to.

When you finishFor each profile in your profile manager, determine if you need to rerun any faileddistributions. See “Rerunning a failed distribution” on page 107.


Command line: Use the wdistrib command to set distribution options for aprofile.wdistrib

Desktop:

1. Open the Profile Manager dialog box by double-clicking the policy region iconto display the policy region.

2. Open the profile that you want to distribute from the Profile Manager dialogbox.

3. Click Profile and select Distribute to display the Distribute Profile dialog box.

4. Select one of the Distribute To distribution levels options:v Next level of subscribers

v All levels of subscribers

See page 101 for an explanation of the distribution levels.5. Select Make each subscriber’s profile an EXACT COPY of this profile from

the Distribution Will options.

Figure 56. Distribute Profile dialog box (Desktop)


Additional information: This option overwrites the subscriber’s profile with anexact copy of the profile that you are distributing.

Note: Do not distribute a profile to a Tivoli Enterprise endpoint with thePreserve modifications in subscriber’s copies of the profile option set.You must always use the Make each subscriber’s profile an EXACTCOPY of this profile option.

6. Select the subscribers to receive the profile using the following steps:a. Click the subscribers on the list that you want to distribute the profile to

from the Do Not Distribute to These Subscribers scrolling list.Additional information: Use the tools under the subscriber lists to select morethan one subscriber at a time.

b. Click the left arrow to move the subscribers to the Distribute to TheseSubscribers scrolling list.

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

7. Click one of the following options:

Distribute & CloseDistributes the profile immediately, closes the Distribute Profile dialogbox, saves the settings you have made, and returns to the IBM TivoliMonitoring Profile dialog box.

DistributeDistributes the profile immediately, saves the settings you have made,and leaves the Distribute Profile dialog box 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.

Management Console:

1. Do the following to access the profile you want to distribute.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile



d. Click the profile manager that contains the profile for the profile you wantto distribute.Additional information: A list of profiles is displayed in the middle section ofthe Configuration window under the Profiles tab. A list of resource modelsis displayed under the Profiles list.

e. Click the profile that you want to distribute.Additional information: A list of profiles is displayed under the Profiles tab.

2. Click Distribute in the Profile Manager list on the Tools menu in theright-hand section of the screen to display the Distribute dialog box.


3. Select the Override distribution defaults check box to display the distributionoptions:v Distribute to

– Next level of subscribers

– All levels of subscribers

This is the default option. Select this option if you want to distribute aprofile in which your endpoint is the only subscriber. See page 101 for anexplanation of the distribution levels.

v Distribute will

– Preserve modifications in subscriber’s copies

Do not distribute a profile to a Tivoli Enterprise endpoint with thePreserve modifications in subscriber’s copies of the profile option set.

Note: This is the default option.– Replace with an exact copy

Always use the Replace with an exact copy option.4. Specify distribution options by doing the following:

v Select Distribute to and Distribute will options:– Click one of the Distribute to options to choose the level of subscribers.– Click Replace with an exact copy to overwrite the subscriber’s profile

with an exact copy of the profile that you are distributing.

—OR—v Clear the Override distribution defaults check box.

5. Select the profile to distribute from the Select Profiles list.6. Select the subscribers to receive the profiles from the Select Subscribers list.

Note: Make sure that each subscriber is either a profile manager or asupported Tivoli endpoint. IBM Tivoli Monitoring does not support othertypes of endpoints.

7. Click OK to distribute the profile.

Figure 57. Distribute dialog box (Management Console)


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









When you finishNone

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

Command line: Use the wdmdistrib command to distribute the profile to thesubscribers of the profile manager. For example, to distribute the default profileDOMManager-DOMMonProfile to an instance endpoint labeled inst1@bburns,enter the following command:wdmdistrib @Tmw2kProfile:DOMManager-DOMMonProfile \@DominoInstanceManager: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 dialog box 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 dialog box.d. Double-click the profile you want to distribute to open the IBM Tivoli

Monitoring Profile dialog box.2. Select Profile → Distribute to display the Distribute Profile dialog box.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 dialog box. 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 the Distribute & Close button to begin the distribution and close theDistribute Profile window.

7. Optional : Schedule when the distribution will occur by completing thefollowing steps:a. Click the Schedule button to display the Add Scheduled Job dialog box.b. Set the job options as needed.c. Click the Schedule Job & Close button to set the schedule.

8. Click the Distribute & Close button to begin the distribution and close theDistribute Profile dialog box.

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

Rerunning a failed distribution

ObjectiveTo determine if the distribution to an endpoint failed and to rerun it to distribute itto the specified subscribers.

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

When you successfully redistribute, the software deletes the profile manager itcreated for the failed distribution. A wholly or partially unsuccessful redistributionretains the profile manager containing only the subscribers that were unsuccessfulin the redistribution. Continue the process of correcting the errors and retrying thedistribution until the profile has been successfully distributed to all endpoints.


Before you beginDistribute the profile. See “Distributing a profile from the desktop” on page 101.


ProcedureYou can perform this procedure from the Tivoli desktop or the ManagementConsole.

Desktop:

1. Open the Policy Region dialog box by double-clicking the policy region icon todisplay the policy region.

2. Click View and select Refresh from the Policy Region dialog box to see thenew profile managers.

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 displays at this point, indicating thatthe resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX endpoint, or vice versa.

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

where:


Provided that you created the profile manager that you used for the originaldistribution without checking the dataless endpoint mode option, you canuse these profile managers to redistribute the profile to the failed endpointswhen you have fixed the problem that caused the original failure. To do this,subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile. Distribute the original profile tothe failed endpoints by selecting these profile managers as the target for thedistribution. You can edit the profile managers to delete an endpoint from agroup of failed endpoints before retrying the distribution.

A successful redistribution deletes the profile manager relating to the errorcondition. A wholly or partially unsuccessful redistribution retains the profilemanager containing only the subscribers that were unsuccessful in theredistribution. You should continue the process of correcting the errors andretrying the distribution until all errors have been fixed.

If any of these problems persist and cannot be resolved, call CustomerSupport.

Management Console:

1. Do the following to access the profile you want to redistribute.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile

managers.2. Right-click the policy region and click Refresh to see the new profile managers.3. Review the new profile manager names to determine and correct the cause of

the 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:



The AMW089E error message displays at this point, indicating thatthe resource model type is not compatible with the endpointoperating system. For example, you might have distributed aWindows resource model to a UNIX endpoint, or vice versa.

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

where:


Provided that you created the profile manager that you used for the originaldistribution without checking the dataless endpoint mode option, you canuse these profile managers to redistribute the profile to the failed endpointswhen you have fixed the problem that caused the original failure. To do this,subscribe the profile managers that contain the failed endpoints to the profilemanager that contained the original profile. Distribute the original profile tothe failed endpoints by selecting these profile managers as the target for thedistribution. You can edit the profile managers to delete an endpoint from agroup of failed endpoints before retrying the distribution.

A successful redistribution deletes the profile manager relating to the errorcondition. A wholly or partially unsuccessful redistribution retains the profilemanager containing only the subscribers that were unsuccessful in theredistribution. You should continue the process of correcting the errors andretrying the distribution until all errors have been fixed.

If any of these problems persist and cannot be resolved, call Tivoli CustomerSupport.



Chapter 5. Working with Lotus Domino Servers

This chapter describes how to manage Domino servers in the Tivoli environment.


Table 10. Goals and where to find procedures for working with Lotus Domino Servers


Check the state of a server. “Checking server status” on page 111

Start, stop, and recycle a server. “Controlling a server” on page 113

Start and stop resource models for LotusDomino Servers.

“Controlling resource models for servers”on page 117

Start and stop Domino tasks. “Running Domino tasks” on page 119

View and edit the properties of a server. “Viewing server properties” on page 121

“Editing server properties” on page 122

View the current statistics for a Dominoserver as a snapshot of server activity.

“Viewing Domino statistics” on page 126

Open the Domino server console and executecommands within the IBM Tivoli Monitoringfor Messaging and Collaboration: LotusDomino environment.

“Entering a Domino remote consolecommand” on page 128

Check the current state of all processes on aserver. You can also check the status ofnotes.ini tasks and server console tasks.

“Checking server health” on page 130

View and search the Lotus Notes log file(log.nsf).

“Viewing and searching log files” on page132

Find and repair corruption in a database. “Checking for database corruption” onpage 135

Verify the setup of mail database files andcheck the queue of mail that is waiting on aserver.

“Verifying mail files and checking MailWaiting” on page 137

Determine whether a server replicatedaccording to the schedule defined by itsname and address book (NAB).

“Viewing replication information” on page139

View a list of inactive users for a server. “Checking for inactive users” on page 141

View and change ACL permissions forDomino databases, create and delete users,and modify permissions.

“Viewing and changing the Access ControlList (ACL)” on page 142

Checking server status

ObjectiveTo check the current status of a Domino server so that you can optimizeperformance and take corrective action if needed.


Background informationThe status of a server is one of the following:v Upv Up but not accepting connectionsv Down


When you finishObtain more detailed information on the status of the server that you are checking,as described in “Checking server health” on page 130.


Command line: Use the following commands to check the status of a Dominoserver:v wtmdserveravailable commandv wruntask command with the Server Available task

For more information, see the IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino Reference Guide.

Desktop: Run the following Tivoli task in the task library as described in“Running tasks” on page 172: Server Available. See IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide for a description of thedesktop options for this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server you want to

check to display the Policy Region window.2. Inspect the status icon of the server endpoint that you want to check. Figure 58

shows the server status icons. The server up icon has a green circle with anarrow. The server down icon has a red circle with a minus symbol.

Note: Icons for resource model response levels are not available in the Tivolidesktop.

Management Console:

1. Click the Status and Operations tab of the Management Console.

Figure 58. Server status icons: server up and server down (Desktop)


2. Find the name of the server that you want to check in the tree view on the leftside of the console. You can use the Group by drop-down list to view serversin the tree. The following groups are in the list: Domain, Release, OperatingSystem, Cluster, Hierarchy, Network, or Server Status.

3. Observe the two icons that are displayed to the left of any server name, as inthe example in Figure 59 for the Mail03 server:

v The server icon on the left includes one of the following symbols to showstatus:– An arrow in a green circle means that the server is up. The icon in

Figure 59 shows that Mail03 server is running.– A minus sign in a red circle means that the server is down.– A yellow triangle indicates a communication error with the IBM Tivoli

Monitoring engine on the endpoint. One of the following actions mightresolve this problem:- When the server is newly configured, start the server.- When you have reset the endpoint, distribute resource models to that

Lotus Domino Server object.v The color of the thermometer icon on the right indicates the highest lowest

health value among all resource models.– Green thermometer: all resource models with health greater than 30%.– Orange thermometer: at least one resource model with health that is

between 6% and 30%.– Red thermometer: at least one resource model with health that is between

0 and 5%.– Gray thermometer: unable to retrieve health information from server.

Controlling a server

ObjectiveTo start, stop, and recycle (restart) the Lotus Domino server process.

Background informationIf you use a Lotus Domino server configuration document to manage theServerTasks entry in the notes.ini file, you must update the configurationdocument as followsv Add tivoliv46 to the list of ServerTasks.



Always use the Windows NT Server service or the product to start the Dominoserver. If you use other methods to start the Domino server, you might disable

Figure 59. Server icon example (Management Console)

Chapter 5. Working with Lotus Domino Servers 113

functionality in the product. For example, if you start the server using the LotusDomino icon in the Start menu of the Windows taskbar, some functionality in theproduct might be disabled.

If you create a Domino server object while the Domino server is down, you muststart the server as described in “Controlling a server” on page 113. This action isan integral part of the server configuration process. After the server is configured,you can start the server in whatever way is most convenient.

If the Domino server runs Lotus Domino, Version 5.x, and you created the Dominoserver object while the server was up, you must restart the server before you canuse the mail tracing functionality of this product.

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino enablesyou to control a server in the following ways:

Starting a serverStarts the Lotus Domino server process on an endpoint. After the server isrunning, the IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino process is running and ready to receive commands.

Always use one of the following methods to start a Domino server onWindows systems:v Use one of the IBM Tivoli Monitoring for Messaging and Collaboration

user interfaces (command line, Tivoli desktop, or Management Console)as described in this procedure.OR

v Use the Services user interface in the Windows NT Control Panel tostart the Lotus Domino Server service. This method is valid only afteryou start the Domino server as required in some of the configurationscenarios described in “Discovering and configuring multiple servers inthe Management Console” on page 44. This scenario involvesconfiguring the Domino server object while the Domino server is down.Review these procedures if you are starting the Domino server for thefirst time after you have created a Domino server object.

Note: You might disable functionality in the product if you start theDomino Server with an executable or an option in the Start menu ofthe Windows taskbar.

Stopping a serverStops the Lotus Domino server process on an endpoint so that you cancorrect problems, upgrade software, or install software.

Recycling/Restarting a serverStops and then starts the Lotus Domino server process. Use this procedurewhen you believe that stopping and immediately restarting a server willcorrect a problem.

Running custom scripts after starting or stopping a Domino serverYou can associate custom scripts with the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino commands for starting andstopping a Domino server object.

About custom scripts: Domino administrators often write a custom script or a setof scripts that kill and restart a Domino server that has failed to respond to normalcontrol commands. The commands for controlling a Domino server in IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino enable you to run


scripts against an unresponsive Domino server when normal shutdown methodsfail. You can associate up to three separate scripts with this product’s commands tostart or stop the server. Place these scripts in the same directory as the notes.inifile on the Domino server.

These scripts are executed when the following conditions are true:v The user and group matches the user and group ownership of the notes.ini file.v The current directory matches the directory where the script resides.

The result from each script is passed to each subsequent script. Any script thatreturns a result greater than 10,000 signifies an immediate cancellation of the startor stop procedure. Unique error messages are provided for the six possible exitscenarios for the scripts. The following command calls the nsd.kill command toclean up processes on the server:v On UNIX, tmdpoststop.sh

v On Windows, tmdpoststop.cmd

About the Windows NT Server Service: The Windows NT operating system runsa Server service that gives the operating system the ability to receive requests fromthe network. Whenever you feel it is necessary, you can recycle the Server service.By default, the operating system associates the Server service with the ComputerBrowser service.

As a convenience, the product enables you to recycle the Server service. Thisoperation includes recycling the Computer Browser service, which is dependent onthe Server service process. Use one of the following methods to recycle the Serverservice:v wtmdrecyclentsvrsvc command in the command line interfacev Run the wruntask command with the Recycle NT Server Service task in the

command line interfacev Run the Recycle NT Server Service task in the Tivoli desktopv Use the Recycle NT Server Service tool in the Management Console

The command does not run if you associated other processes with the Serverservice, such as a Web server process or a database management system (DBMS)process. In these cases, recycle each process manually in the Services dialog box onWindows NT at a time when the work load on your system permits interruption(stopping and immediate restarting) of these types of processes.


Before you beginDo not stop or recycle (restart) a server unless conditions require that you stop theserver. For example, you might need to stop or recycle a server whose resourcemodels have exceeded their thresholds. Also, you might need to stop or recycle aserver as part of normal scheduled maintenance. You can use the followingprocedures to check conditions on a server:v View server status as described in “Checking server status” on page 111.v Determine more detailed information on the status of the server that you are

checking, as described in “Checking server health” on page 130.

When you finishYou can view server status as described in “Checking server status” on page 111.


After you stop a server and resolve problems or perform maintenance, you canstart the server as described in “Controlling a server” on page 113.


Command line: Use the following commands to control a server:v wtmdstartserver command to start a Domino Server.v wtmdstopserver command to stop a Domino Server.v wtmdrecycleserver command to restart a server.v wruntask command with the following tasks:

– Start Server to start a Domino Server.– Stop Server to stop a Domino Server.– Recycle Server to restart a server.

For more information about commands and tasks, see the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide.

Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Start Server to start a Domino Server.v Stop Server to stop a Domino Server.v Recycle Server to restart a server.

See IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for a description of the desktop options for these tasks.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server you want to

stop, start, or restart to display the Policy Region window.2. Right-click the server icon in the Policy Region window.3. Select one of the following items in the pop-up menu:

v Select Start Server to start the server. This menu item is available whenserver status is down.

v Select Stop Server to stop the server. This menu item is available whenserver status is up.

v Select Restart Server to restart the server.4. Click Yes in the confirmation dialog box.

Additional Information: When the command finishes running, the Informationdialog box displays the results of the operation.

5. Click the Results drop-down list to inspect the results of the operation for theserver or servers that you selected.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select a server you want to start, stop, or recycle in the tree view on the left

side of the console.


3. Click the Start/Stop/Recycle Server tool in the Tools - Operations collapsiblemenu to display the Start/Stop/Recycle Server dialog box.

4. (Optional) Use one of the following methods to select multiple servers on whichto perform this operation:v Type multiple server names separated by semicolons (;) in the Servers area.

—OR—v Perform the following steps in the graphical user interface:

a. Click the browse icon to the right of the text box in the Servers area toaccess the Select Servers dialog box.

b. Use standard selection methods to select multiple servers.Additional Information: For example, on a Windows keyboard, press Ctrl-ato select all servers, or press Ctrl and click multiple servers, one by one.

c. Click OK to return to the Start/Stop/Recycle Server dialog box.Additional Information: The text box in this dialog box reflects theselections you made in the Select Servers dialog box.

5. Select one of the following options in the Start/Stop/Recycle Server dialog box:v Click Start to start the server.v Click Stop to stop the server.v Click Recycle to recycle the server.

6. Click OK.7. Click OK in the confirmation dialog box.

Controlling resource models for servers

ObjectiveTo start or stop the IBM Tivoli Monitoring for Messaging and Collaborationresource models on a Domino server.

Background informationThis procedure controls IBM Tivoli Monitoring for Messaging and Collaborationresource models on a Domino server, but does not affect other resource modelsthat might be running on the server.

The procedure for starting resource models has the specific purpose of restartingresource models that you stopped intentionally. You do not need to use thisprocedure at first because the monitoring process begins automatically on a serverwhen you distribute a monitoring profile to that server.

Figure 60. Start/Stop/Recycle Server dialog box (Management Console)


When you want to stop a Domino server for an extended period of time, consideralso stopping the Domino server resource models. The resource models in IBMTivoli Monitoring for Messaging and Collaboration are designed to runcontinuously. Even when a server goes down and restarts, the monitoring processcontinues because IBM Tivoli Monitoring continues to run the profiles it hasloaded. In particular, resource models that are configured to log information andsend status messages continue to generate information unless you stop them.

Required Authorization RoleDomino_Admin

Before You BeginNone.

When You FinishNone.


Command line: Use the wdmeng command to start and stop resource models onthe server. For more information, see the Commands appendix of the IBM TivoliMonitoring, Version 5.1.0: User’s Guide.

Desktop:

1. Double-click the icon of the policy region that contains the server whoseresource models you want to start or stop to display the Policy Regionwindow.

2. Right-click the server icon in the Policy Region window.3. Select one of the following pop-up menu items:

v Select Start Resource Models to start resource models.v Select Stop Resource Models to stop resource models.

4. Click OK in the confirmation dialog box.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select a server whose resource models you want to start or stop in the tree

view on the left side of the console.3. Click the profile with the resource model you want to start or stop.4. Right-click in the Profile-Resource Model-Status header bar to display the

pop-up menu, and select one of the start or stop resource model options.


Additional information: When you start a resource model, Running is displayedin the Status column next to the name of the resource model. When you stop aresource model, Stopped is displayed in the Status column.

Running Domino tasks

ObjectiveTo start or stop a Lotus Domino task.

Background informationThis procedure enables you to run Lotus Domino administration tasks. You cannotuse this tool to run Tivoli tasks. See “Running tasks” on page 172 for informationon running Tivoli tasks.

The following Lotus Domino administration tasks are available in this procedure:router, replica, update, amgr, adminp, calconn, event, sched, stats, http, diiop,maps. See your Lotus Domino documentation for further information on Dominotasks.





Management Console:

Figure 61. Start/Stop Resource Model pop-up menu for a server (Management Console)


1. Click the Status and Operations tab of the Management Console.2. Select the server for which you want to run a Domino task in the tree view on

the left side of the console.3. Click the Start/Stop Domino Task tool in the Tools - Servers collapsible menu

to display the Start/Stop Domino Task dialog box.

4. (Optional) Use one of the following methods to select multiple servers on whichto perform this operation:v Type multiple server names separated by semicolons (;) in the Servers area.

—OR—v Use the graphical user interface as follows:


b. Use standard selection methods to select multiple servers.Additional Information: For example on a Windows keyboard, press Ctrl-ato select all servers, or press Ctrl and click multiple servers, one by one.

c. Click OK to return to the Start/Stop Domino Task dialog box.Additional Information: The text box in this dialog box reflects theselections you made in the Select Servers dialog box.

5. Select the Domino task that you want to control in the Domino Taskdrop-down menu. See your Lotus Domino documentation for furtherinformation on Domino tasks.

6. Select one of the following options:v Click Start to start a Domino task.v Click Stop to stop a Domino Task.

7. Click Execute.8. Click Yes in the confirmation dialog box.

Additional Information: When execution completes, the Information dialog boxdisplays the results of the operation.


Figure 62. Start/Stop Domino Task dialog box (Management Console)


Viewing server properties

ObjectiveTo view the properties of a Domino server.

Background informationFigure 63 shows the Server Properties display in the Management Console. Youcan see the same values in the Domino Server Properties message box of theTivoli desktop. Table 7 on page 36 describes all properties for Domino servers.

Required authorization roleDomino_User

Before you beginYou must define a Domino server object as described in “Locating a Domino serverand creating a Domino Server object” on page 35.

When you finishFrom the Tivoli desktop, in addition to viewing these properties, you can modifythe Tivoli Data Protection attributes. See “Editing server properties” on page 122for information on using the desktop or the Management Console to edit serverproperties.


Desktop:

1. Double-click the icon of the policy region that contains the server whoseproperties you want to view to display the Policy Region window.

2. Right-click the server icon in the Policy Region window.

Figure 63. Server properties dialog box (Management Console)


3. Select Properties in the pop-up menu to display the Domino Server Propertiesdialog box.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server whose properties you want to view in the tree view on the left

side of the console.3. Click the Server Properties tool in the Tools - Diagnostics collapsible menu to

display the Server Properties dialog box.4. Click OK to close the dialog box.

Editing server properties

ObjectiveTo edit the properties of a server to enable administrators and users to determinethe behavior of the server.

Background informationSeveral properties of a Domino server affect the backup and retrieval process. Toset up automatic backups and restores, you must have Tivoli Data Protection. SeeChapter 12, “Backing up and restoring Domino databases” on page 249 for moreinformation on this topic.


Before you beginYou create a server object as described in “Locating a Domino server and creatinga Domino Server object” on page 35.

When you finishPeriodically check server status as described in “Checking server status” on page111.


Desktop:

1. Double-click the icon of the policy region that contains the server whoseproperties you want to edit to display the Policy Region window.

2. Right-click the server icon in the Policy Region window.3. Select Properties in the pop-up menu to display the Domino Server Properties

dialog box. See Figure 64 on page 123.


4. Type the port number that the IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino addin process uses in the Tivoli Addin Port textbox.

5. Type the server password in the Server Password text box.6. Type the values to configure backups and restores:

Note: Do not enter values in these text boxes if you do not have Tivoli DataProtection and Tivoli Storage Manager software installed.

a. Type the path of the product in the TDP Program Directory text box.b. Type the path of the Tivoli Storage Manager API in the TSM API Directory

text box.c. Type the name of the Tivoli Data Protection configuration file, for example,

domdsm.cfg, in the TDP Configuration File text box.d. Type the name of the Tivoli Data Protection options file in the TDP Options

File text box.e. Type the name of the Tivoli Data Protection user in the TDP User text box.f. Type the password for Tivoli Data Protection in the TDP Password text box.

Figure 64. Domino Server Properties dialog box (Desktop)


7. Select one or more Server Type check boxes to assign resource model profilesthat correspond to the role that the server performs in your Domino system.

8. Click OK.

Management Console:

1. Click the Configuration tab of the Management Console.2. Click the Servers tab in the Configuration pane.3. In the Configure Servers list, do one of the following:

v To edit a single server, click on the row of the server whose properties youwant to edit.—OR—

v To edit multiple servers, click in the column to the left of the ConfigureServers list to place a check mark beside each server that you want to edit.

4. Click Edit in the tool bar above the Configure Server list to display the Editdialog box.

5. In the Apply changes to area, click the option that corresponds to the serveryou selected in Step 3. If you are editing a single server, the option for thatserver is the default selection.Additional Information: (Optional) If you selected multiple servers to edit in Step3, the All selected servers button is selected by default. Your edits apply to allservers that you selected in Step 3.

Figure 65. Edit dialog box (Management Console)


Note: When you select the All selected servers option, you must select thecheck box beside each field to enable the text fields and specify a valuethat will be applied to all selected servers.

6. Type new values in the following text boxes of the Basics tab:

Note: You can edit all attributes except the name of the Domino server(Object Label), the name of endpoint in the Tivoli management region(Endpoint Name), and the path name of the .ini file (INI FileLocation). If you are editing multiple servers, you can select the INIFile Location field; however, the product ignores this setting for anyserver you are editing that is already configured.

Policy RegionPolicy region to which a server or servers are moved. The policyregion must already exist. See “Managing policy regions” on page 26for more information on creating a policy region.

Server PasswordIf specified, the password for this server’s ID file that is used forstarting the server. (This field is not available for Windows NT.)

Port The port number to use for the IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino process.

Type Defines the type of Domino server: Mail Database server, Web server,Mail Router server, Application server, and News server.

7. Select the Backup tab in the Edit dialog box and enter new values for theproperties, as necessary. See Chapter 12, “Backing up and restoring Dominodatabases” on page 249 for more information on backup procedures.

Note: Do not enter values in these text boxes if you do not have Tivoli DataProtection.

TDP Program DirectoryDirectory where Tivoli Data Protection for Lotus Domino is installed.

TSM Api DirectoryDirectory where the Tivoli Storage Manager API files are installed.

TDP Configuration FileName of the Tivoli Data Protection configuration file, relative to theTDP Program Directory. By default, the configuration file isdomdsm.cfg.

TDP Options FileName of the Tivoli Data Protection options file, relative to TDPProgram Directory. By default, the options file is dsm.opt.

TDP UserName of the Tivoli Data Protection user.

TDP PasswordIf specified, the password for the Tivoli Data Protection user.

8. Click Save. The State column of the Configure Server list refreshes andreflects your edits.Additional Information: All servers in the list have a State code of U (notconfigured for the product) or C (configured for the product). In this step, theletter M is added to the State code for the server or servers that you havemodified. These are the results:


v CM means you have modified the configuration settings of a server that isalready configured for the product.

v UM means you have made configuration settings for a server that is notconfigured for the product.

9. (Optional) To configure multiple servers, complete the following action beforegoing to the next step: click in the column to the left of the Configure Serverslist to place a check mark beside each server that you want to configure.

10. Click Configure above the Configure Servers list to display the Configuredialog box.

11. Click one of the following options in the Configure Option area:v Click the name of the server that is highlighted in the Configure Servers

list to configure only that server.–OR–

v Click All modified servers to configure all edited servers.–OR–

v Click All selected servers to configure all servers that you selected in theConfigure Servers list, as described in Step 9.

12. Click Execute.13. Click Yes in the confirmation dialog box that appears. The Results area

refreshes with the status of the configuration command for each of theselected servers.

14. Click Close.

Viewing Domino statistics

ObjectiveTo view the current statistics for a Domino server as a snapshot of server activity.

Figure 66. Configure dialog box (Management Console)


Background informationUse this procedure to view any or all statistics for a Domino server in statisticalcategories such as memory (mem.), mail (mail.), server (server.), and disk (disk.).

The product refers to the type of the server, for example Web server or maildatabase server, to determine which statistics to collect and which statistics tomake available in the graphical user interface for this procedure.



When you finishTake remedial action if results indicate a problem.


Command line: Use the following commands to query statistics for a Dominoserver:v wtmdquerystat commandv wruntask command with the Query Statistics task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Query Statistics. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server whose

statistics you want to view. This displays the Policy Region window.2. Right-click the server icon in the Policy Region window and select Show

Statistics in the pop-up menu to display the Show Statistics dialog box.3. Use the Statistic Type drop-down list to select the type of statistic you want to

show, or select All to show all statistics for the server. The list of availablestatistics refreshes to show only the statistics available for the server you areviewing.

4. Click Execute to display the statistics in the Statistic Output area.5. Click Close.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server whose statistics you want to view in the tree view on the left

side of the console.


3. Click the Show Server Statistics tool in the Tools - Diagnostics collapsiblemenu to display the Show Server Statistics dialog box.

4. Use the drop-down list in the Statistic area to select the type of statistic youwant to show, or select All to show all statistics for the server. The list ofavailable statistics refreshes to show only the statistics available for the serveryou are viewing.

5. Click Execute to display the statistics in the Statistic Output area.6. Click Close.

Entering a Domino remote console command

ObjectiveTo open the Domino server console and execute commands within the IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino environment.

Background informationYou can issue a Lotus Domino server command from the remote console. See theLotus Domino documentation for more information on Domino commands.





Figure 67. Show Server Statistics dialog box (Management Console)


Command line: Use the following commands to issue console commands to aDomino Server:v wtmdremoteconsole commandv wruntask command with the Remote Console task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Remote Console. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server to display the

Policy Region window.2. Right-click the server icon in the Policy Region window and select Remote

Console in the pop-up menu to display the Remote Console dialog box.3. Type a Domino console command in the Command text box.4. Click Execute.5. View the results of the command in the Console Output area.6. Click Close.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server in the tree view on the left side of the console.3. Click the Remote Console tool in the Tools - Diagnostics collapsible menu to

display the Remote Console dialog box.


4. Type a Domino console command in the Console Command area.5. Click Execute.6. View the results of the command in the Console Output area.7. Click Close.

Checking server health

ObjectiveTo check the current state of all processes on a Domino server. You can also checkthe status of notes.ini tasks and server console tasks in the Management Console.

Background informationDomino server health consists of the status (up or down) of the followingprocesses: Tivoli Addin, Core Database, Event Monitor, Billing Manager, ClusterDatabase Directory, Cluster Replicator, HTTP, Web Retriever, SMTP, NNTP, LDAP,POP3, IMAP, Replication, Mail Router, Statistics Monitor, Agent Manager, AdminProcess, Schedule Manager, and Calendar Manager. To add to this list of processes,use the Notes.ini Task areas mentioned in the procedure below. Both the Notes.iniTask area and the Name area are for third-party tasks only.



When you finishTake remedial action if results indicate a problem.


Figure 68. Remote Console dialog box (Management Console)


Command line: Use the following commands to check the health of a DominoServer.v wtmdcheckhealth commandv wruntask command with the Check Health task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Check Health. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server whose health

you want to check to display the Policy Region window.2. Double-click the icon of the profile manager for the server you want to check to

display the Profile Manager dialog box.3. Right-click the server icon in the Profile Manager window and select Check

Health in the pop-up menu to display the Check Health dialog box containingthe results.Additional information: The status of a process can be Running, Hung, orStopped.

4. Click Close to dismiss the dialog box.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server in the tree view on the left side of the console.3. Click the Check Health tool in the Tools - Diagnostics collapsible menu to

display the Check Health dialog box.


4. (Optional) Type a list of third-party tasks as they appear in the Lotus DominoServer Notes.ini file into the Notes.ini Task area to include these tasks in thelist of task results. Separate these tasks using commas. If you complete thisstep, you must also complete the next step.

5. (Optional) Type a list of third-party tasks as they appear in the ManagementConsole Show Task command. The order of the names should correspond tothe order in the Notes.ini Task area. Separate these tasks using commas. If youcomplete this step, you must also complete the previous step.

6. Click Execute, and view results in the Processes State area.7. Click Close to dismiss the dialog box.

Viewing and searching log files

ObjectiveTo view and search log file information for a Domino server.

Background informationThe Lotus Notes log file, log.nsf, records server activity for a Domino server. Thisinformation can help you manage server resources in IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino.


Before you beginYou must create a Domino server object as described in “Locating a Domino serverand creating a Domino Server object” on page 35.

When you finishNone

Figure 69. Check Health dialog box (Management Console)



Command line: Use the following commands to search the log file of a DominoServer:v wtmdquerylog command to search the log file of a Domino Server.v wtmdquerydoc command to view the full text of a log file for a Domino server.v wruntask command with the Query Log task to search the log file of a Domino

server.


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Query Log. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server whose log file

you want to access. This displays the Policy Region window.2. Right-click the server icon in the Policy Region window and select Log File

Parser in the pop-up menu to display the Log File Analysis dialog box.3. Type the name of the Lotus Notes form to search in the Form Name text box.

Use one of the following form types:v session to search for log file data in the Session form.v activity to search for log file data in the Activity form.v events to search for log file data in the Misc. Events form.v replication to search for log file data in the Replication form.v routing to search for log file data in the Mail Routing form.v call to search for log file data in the Phone Call form.v incoming to search for log file data in the Phone Call - Incoming form.v outgoing to search for log file data in the Phone Call - Outgoing form.v size to search for log file data in the Size form.v nntp to search for log file data in the NNTP Events form.v usage to search for log file data in the Object Store Usage form.v passthru to search for log file data in the Passthru Connection form.

4. Type a starting date for the parsing of the log file in the Starting Date text box.5. Type strings in the Include String area and in the Exclude String area to cause

the Output area to display. Exclude lines from the display in the Log FileAnalysis area, according to your specifications. Apply the following rules:v You must provide either an include string or an exclude string.v An Include String specification generates output of only those lines that

contain the string. In other words, an Include String specification excludesall lines except lines that contain the string.

v If a line contains your include string and also contains your exclude string,that line is excluded. In other words, exclusion supersedes inclusion.


v You can enter multiple strings, separated by semicolons (;).6. Type a numerical value in the Tail Count text box.

Additional information: The value you specify determines the number of linesthat are displayed from the end of the log file.

7. Click Execute to retrieve the log file data and display it in the Log FileAnalysis area.

8. Click Close.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. In the tree view on the left side of the console, select the server whose log file

you want to access.3. Click the Search Log File tool in the Tools - Diagnostics collapsible menu to

display the Search Log File dialog box.

4. Type the name of the Domino server whose log files you want to search.5. In the Form Name drop-down list, select the name of the Notes form to

search for. Choose one of the following types of form:v Select Session to search for log file data in the Session form.v Select Activity to search for log file data in the Activity form.v Select Misc. Events to search for log file data in the Misc. Events form.v Select Replication to search for log file data in the Replication form.v Select Mail Routing to search for log file data in the Mail Routing form.v Select Phone Call to search for log file data in the Phone Call form.

Figure 70. Search Log File dialog box (Management Console)


v Select Phone Call - Incoming to search for log file data in the Phone Call -Incoming form.

v Select Phone Call - Outgoing to search for log file data in the Phone Call -Outgoing form.

v Select Size to search for log file data in the Size form.v Select NNTP Events to search for log file data in the NNTP Events form.v Select Object Store Usage to search for log file data in the Object Store

Usage form.v Select Passthru Connection to search for log file data in the Passthru

Connection form.6. Type strings in the Include String area and in the Exclude String area to

cause the Output area to display. Exclude lines from the display in the LogFile Analysis area, according to your specifications. Keep in mind thefollowing rules:v You must provide either an include string or an exclude string.v An Include String specification generates output of only those lines that



v You can enter multiple strings, separated by semicolons (;).7. Type a numerical value in the Tail text box.

Additional information: The value you specify determines the number of linesthat are displayed from the end of the log file.

8. Type a starting date for your query in the Date text box.9. Click Execute to retrieve the log file data and display it in the Output area.

10. (Optional) Click Details to display the Log File Document dialog box whereyou can access the log file whose complete information you want to view.

11. Click Close.

Checking for database corruption

ObjectiveTo check for corruption in a database or databases on a Domino server.

Background informationDuring this procedure, the product attempts to fix any database corruption that itfinds.


Before you beginNone

When you finishNone


Command line: Use the following commands to check for database corruption:


v wtmdchkdbcorruption command.v wruntask command with the Check Database Corruption task.


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Check Database Corruption. See IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide for a description of thedesktop options for this task.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. In the tree view on the left side of the console, select a server that you want to

check for corruption.3. Click the Check Database Corruption tool in the Tools - Diagnostics

collapsible menu to display the Check Database Corruption dialog box.

4. In the Database Specification text box, enter the names of database files thatyou want to check. Follow the rules that are listed in the discussion of thedatabase name parameter in the IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide when you specify the names andlocations of database files in this text box. Separate multiple databasespecifications with commas.

5. Type the name of the database views that you want to see in the View text boxto limit the number of database views that the Corrupt Views area displays.Separate multiple view names with commas.

6. Click Execute. The product attempts to fix corruption that it finds.7. View the Corrupt Views area, which lists all databases that were corrupted and

shows a flag to indicate whether the corruption is fixed.

Figure 71. Check Database Corruption dialog box (Management Console)


8. Click Close.

Verifying mail files and checking Mail Waiting

ObjectiveTo verify the setup of mail database files and to check the queue of mail that iswaiting on a Domino server.

Background informationThis procedure generates the following two lists to help you analyze the status ofmail in multiple mailboxes on a Domino mail database server:v Mail that is currently waiting in the Domino server’s mailbox, mail.box. This list

shows the mailbox, destination, sender, and duration of wait for each mail itemthat is waiting. This list can reveal performance that does not meet the servicelevel objectives for your system.

v Names of mail database files in the Domino server’s file system that do not havecorresponding user names in the server Name and Address Book. For example,if an administrator removed the user jbrown from a Name and Address Book,she or he might forget to delete that user’s mail database file, jbrown.nsf. Thisprocedure would list the jbrown.nsf file so that you can take corrective action.

Note: In the Management Console, both lists generate at the same time, in thesame dialog box.


Before you beginStart the server, as described in “Controlling a server” on page 113.

When you finishTake appropriate corrective action if results indicate unused mail database files orslow performance of a Domino mail database server.


Command line: Use the following commands to check mail files:v wtmdverifymail command to see a list of the names of mail database files in the

Domino Server file system that do not have corresponding entries in the Nameand Address Book.

v wtmdmailwaiting command to check for mail that is waiting.v wruntask command with the following Tivoli tasks:

– Mail Waiting

– Verify Mail

– Query NAB


Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Mail Waiting


v Verify Mail

v Query NAB


Management Console:

1. Click the Status and Operations tab of the Management Console.2. In the tree view on the left side of the console, select a server that you want to

check for mail that is waiting and to check for unused mail databases.3. Click the Mail tool in the Tools - Diagnostics collapsible menu to display the

Mail dialog box.

4. Click Execute to perform the test.5. Make note of mail wait times that exceed the performance objectives for your

system in the Mail Waiting area so that you can take corrective action.6. Make note of unused mail databases in the NAB Test Failed Databases area so

that you can take corrective action.7. Click Close to dismiss the dialog box.

Figure 72. Mail dialog box (Management Console)


Viewing replication information

ObjectiveTo determine whether a Domino server replicated according to the scheduledefined by its name and address book (NAB). This procedure compares scheduleswith the replication log in the log.nsf file. If it finds no log entries for thescheduled replication, it reports the replication as a Miss. If the log entries do notmatch any schedule, it reports the schedule as a Manual replication. If there is amatch, it reports the schedule as a Hit.

Background informationNone



When you finishNone


Command line: Use the following commands to check replication results for aDomino server:v wtmdcheckrep commandv wruntask command with the Check Replication task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Check Replication. See IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide for a description of the desktop optionsfor this task.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server to display the

Policy Region window.2. Right-click the server icon in the Policy Region window and select Replication

Analysis in the pop-up menu to display the Replication Analysis dialog box.3. (Optional) Type strings in the Include String area and in the Exclude String

area to cause the Output area to display. Exclude lines from the display in theReplication Analysis area, according to your specifications. Keep in mind thefollowing rules:v Your specifications affect only the Events section and the Database section of

the log.v An Include String specification generates output of only those lines that




v You can enter multiple strings, separated by semicolons (;).4. In the Date text box, enter the date on which you want your check of

replication history to begin. Use a numerical format for the month, day, andyear, as follows: MM/DD/YYYY.

5. Click Execute to retrieve the data and display it in the Replication Analysisarea.


Management Console:

1. Click the Status and Operations tab of the Management Console.2. In the tree view on the left side of the console, select the server.3. Click the Check Replication tool in the Tools - Diagnostics collapsible menu to

display the Check Replication dialog box.

4. (Optional) Type strings in the Include String area and in the Exclude Stringarea to cause the Output area to display. Exclude lines from the display in theReplication Analysis area, according to your specifications. Keep in mind thefollowing rules:v Your specifications affect only the Events section and the Database section of

the log.v An Include String specification generates output of only those lines that



v You can enter multiple strings, separated by semicolons (;).

Figure 73. Check Replication dialog box (Management Console)


5. In the Starting Date text box, enter the date on which you want your check ofreplication history to begin.Additional Information: Instead of entering a date, you can click on the date iconto the right of the Date text box and select a date in the calendar that isdisplayed.

6. Click Execute to retrieve the data and display it in the Output area.7. Click Close to dismiss the dialog box.

Checking for inactive users

ObjectiveTo generate a list of inactive users for a Domino server.

Background informationThis procedure identifies users who have not accessed a specific Domino serverduring a period of days that you specify. The list of these users includes the lastdate that each user accessed the server. The date that the command returns, if any,precedes the period of days that you specify.



When you finishNone

ProcedureYou can perform this procedure from the command line or from the ManagementConsole.

Command line: Use the following commands to generate a list of inactive usersfor a Domino Serverv wtmdchkinactusers commandv wruntask command with the Check Inactive Users task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Check Inactive Users. See IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino Reference Guide for a description of the desktopoptions for this task.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server in the tree view on the left side of the console.3. Click the Check Inactive Users tool in the Tools - Diagnostics collapsible menu

to display the Check Inactive Users dialog box.


4. In the Days text box, enter a number to define a period of days that users areinactive.

5. Click Execute to retrieve a list of inactive users and display it in the InactiveUsers area.Additional Information: The User column displays names of users who have notaccessed the server in the period of days that you define. The Date columndisplays beside each name the time that a user previously connected to theserver.


Viewing and changing the Access Control List (ACL)

ObjectiveTo view and change the access control list (ACL) for a database on a Dominoserver.

Background informationThis procedure enables you to view and change ACL permissions for Dominodatabases while you are working in IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino. The procedure also enables you to create and deleteusers and modify permissions in the ACL.



When you finishNone


Command line: Use the following commands for ACLs:

Figure 74. Check Inactive Users dialog box (Management Console)


v wtmdaclmod command to modify the ACL for a database on a Domino server.v wtmdgetacl command to view a list of all database ACL entries and the access

levels for the specified databases on the specified server.v wruntask command with the following tasks:

– Modify Database ACLs task to modify the ACL for a database on a Dominoserver.

– Get ACLs task to view a list of all database ACL entries and the access levelsfor the specified databases on the specified server.


Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Modify Database ACLs task to modify the ACL for a database on a Domino

server.v Get ACLs task to view a list of all database ACL entries and the access levels for

the specified databases on the specified server.

. See IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for a description of the desktop options for this task.

Management Console:

1. Click the Status and Operations tab of the Management Console.2. In the tree view on the left side of the console, select the server whose

database ACLs you want to modify.3. Click the ACL tool in the Tools - Diagnostics collapsible menu. The ACL

dialog box is displayed with the server’s name in the Server text box.


4. In the Database Specification text box, enter the names of database fileswhose ACLs you want to modify. Follow the rules that are listed in thediscussion of the database name parameter in the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide when you specify thenames and locations of database files in this text box. Separate multipledatabase specifications with commas.

5. Press Enter. The User list in the ACL area refreshes to show the databaseusers.

6. Modify the User list as follows:v Add a user.

a. Right-click in the list of users.b. Select Add user in the pop-up menu to invoke the Add user dialog box.c. Enter a user name.d. Click OK.

—OR—v Delete a user.

Figure 75. ACL dialog box (Management Console)


a. Right-click the user you want to delete in the list of users.b. Select Delete user in the pop-up menu to invoke the confirmation

dialog box.c. Click Yes to confirm deletion of the user.

—OR—v Rename a user.

a. Right-click the user you want to rename in the list of users.b. Select Rename user in the pop-up menu to invoke the Rename user

dialog box.c. Enter a new user name.d. Click OK.

7. Select the user name whose permissions you want to inspect or modify. Thepermissions options in the ACL area refresh to reflect the permissions for theselected user.

8. Select the permissions options that you want to grant to the user.

Note: Remember to clear any permission options that you want to revoke forthe selected user.

v Select Cannot create notes to prevent a user with Author privileges fromcreating new notes.

v Select Cannot delete notes to prevent a user from deleting notes.v Select Create personal agents to permit a user to create personal agents.v Select Create personal folders/views to permit a user to create personal

folders and views.v Select Create shared folders/views to permit a user to create and update

shared views and folders. This selection enables a user with Editorprivileges to assume some Designer-level access.

v Select Create LotusScript to permit a user to create LotusScripts.v Select Read public notes to permit a user to read public notes.v Select Write public notes to permit a user to write public notes.v Select Cannot register monitors to prevent a user from registering monitors

for this database.v Select Release locked notes to permit a user to release locked documents.

9. In the Access drop-down list, select a type of access to grant: No Access,Depositor, Reader, Author, Editor, Designer, or Manager. See the LotusDomino documentation for more information on these options.

10. In the User type drop-down list, select one of the following options:v Server defines the type of user to be a server.v Person defines the type of user to be a person.v Group defines the type of user to be a group.v Admin Reader Author defines the type of user to be an administration

server that can modify reader and author fields in the database.v Admin Server defines the type of user to be an administration server.

11. Click in the column to the left of a privilege in the Privileges area to select ordeselect a privilege for the selected user.

12. Click Execute to apply your ACL modifications.13. Click Close.



Chapter 6. Working with Domino Performance Stations

A Domino Performance Station is a virtual Notes user that you can use to runsimulated user transactions against Domino servers. This simulated transaction iscalled a probe. Probes perform the following functions:v Test a specific aspect of a Notes application, such as replicating a database or

generating a piece of mailv Reveal the performance of a system from the perspective of the Notes userv Provide data for the assessment of a system’s conformance with service-level

agreements (SLAs)

In the Domino Performance Station Resource Models profile manager, a profileexists for each Domino Performance Station object that you create. By default eachprofile has the following resource models, which you can add or remove at anytime:v DPSCalendarEntryv DPSDatabaseAccessv DPSNABSearchv DPSNetEchov DPSReplicateLocalv DPSRoundTripMailv DPSWebAccessv DPSDominoIntegrity


Table 11. Goals and where to find procedures for working with Domino PerformanceStations


Design your Domino PerformanceStation installation.

“Planning and implementation” on page 148

Create the Domino PerformanceStations you need in appropriatelocations throughout the network.

“Configuring a Domino Performance Station” onpage 152

Add probes that measure the quantitiesand qualities you need to capture.Configure these probes to report resultsand alert you to threshold events.

“Configuring probes for a station” on page 156

“Configuring a resource model to monitorprobes” on page 158

Manage Domino Performance Stations. “Deleting a Domino Performance Station” onpage 161

“Controlling a station” on page 161

“Controlling resource models for stations” onpage 163

Manage probes. “Deleting probes” on page 164

“Resetting probes” on page 165


Table 11. Goals and where to find procedures for working with Domino PerformanceStations (continued)


Diagnose user performance problemsand station status.

“Running a probe one time” on page 166

“Checking probe status” on page 168

“Checking the integrity of a performance station”on page 169

Authorization Roles for Domino Performance StationsTo access Domino Performance Station functionality, users must have the followingroles either globally or in the Messaging and Collaboration policy region:v Minimum roles: user, Domino_User, Domino_DPS_User

v To access station configuration functions: Domino_DPS_Admin

Planning and implementationThis section covers the following topics to help you plan and implement probing:v System design guidelinesv Hardware, software, and network guidelinesv Guidelines for creating Domino Performance Stationsv Probe characteristics

System design guidelinesDesign and deployment of a system for probing requires the knowledge of aDomino architect to resolve the following issues:v Where should Domino Performance Stations be located?v Which probes are necessary for a particular station?v Which client-server communications require probing? For example, a client can

communicate with many Domino servers, but you might need to probe only afew of those client-server connections.

Note: Within the Tivoli Desktop, you must not move station objects from theiroriginal policy regions. Also, you must not move profiles for station objectsfrom the original profile manager that contains the Domino PerformanceStation resource models that you deploy.

Probes and the server they testEach probe is intended to test a specific transaction against a specific server, suchas Notes-to-Notes mail. The performance and availability results reflect the Notesclient’s experience at the Domino Performance Station.

Network topology versus physical layoutGive attention to network topology. Even when your Domino Performance Stationsare physically adjacent, they might access the network through different links, orthey might exist on completely separate networks. Be sure you are testing thecorrect networks and connections.


Scope of testingIf possible, probe each server that can be tested by a probe transaction. If it is notpossible to test all servers, probe the most important mail, address book, andapplication servers.

Although you might want to thoroughly probe performance for all users, whereverthey are located, you must guard against the following two problems:v Excessive probing overloads the station with transactions and distorts

performance readings.v Deploying probes to all servers might be unrealistic for large and broadly

distributed networks.

Testing server performanceIf you primarily want to probe server performance, deploy probes on the serversite or as close on the network as possible to the server site. That way, the probestest server performance with minimal interference from the effects of networkperformance.

Testing network performanceIf you primarily want to probe network performance for Notes clients, deployprobes at representative Notes client sites, so that probes reflect the experience ofNotes users, including the effects of network performance.

You can customize sets of probes to the needs of each specific network. Keep inmind that specific user sites in your network might require access to only a fewprincipal mail or application servers. Eliminate probes that test servers that a Notesclient rarely or never uses.

Testing availabilityA probe can detect that a server is unavailable, but it cannot determine whetherthe server itself is down or the network connection to the server is down. You canuse the following methods to resolve this issue:v Connect sets of similar probes on separate networks to the same server. When

both sets show interruptions of service, you have a strong indication that theserver itself is down.

v Within the server site, connect sets of similar probes located on separate stationsto the same server. When both sets show interruptions of service, you have astrong indication that the server itself is down.

v Use the DPSNetEcho probe to monitor key nodes in the network path,independently of any server application. With appropriate monitors,DPSNetEcho can send alerts when problems are detected in the network.

Note: DPSNetEcho serves as a tool to test overall network communication.However, you must specify a server for DPSNetEcho to communicatewith. This communication represents a minimal transaction that provesonly that the message reaches the server hardware. Because no interactionwith server applications takes place, the probe provides no informationabout server performance.

Starting smallTesting on a small scale is the best way to evaluate your plan for probedeployment. Run one or more Domino Performance Stations at each site andexamine the measurement results to validate your configurations and capacityplanning estimates. You can also use the Probe Once function to run individualprobes, as described in “Running a probe one time” on page 166. One of the most

Chapter 6. Working with Domino Performance Stations 149

important advantages that small-scale testing offers is verification of access toresources. If you prematurely run a full set of probes, you might generate a largenumber of error messages.

Hardware, software, and network guidelinesTo achieve accurate probing, Domino Performance Stations should be Notes clientcomputers that are dedicated to running probe tests. Test results from a dedicatedstation are free from the distortion that a user might introduce as they performoperations that might interfere with the probes you run.

Each computer that you set up as a performance station must have the followingcharacteristics:v Is an endpoint in the Tivoli management regionv Runs the Windows NT or Windows 2000 operating systemv Is configured as a Notes client under Lotus Notes, Version 5.xv Has local copies of probe user ID files for each server to be tested, or has

network access to these files

A Domino Performance Station must have Tivoli endpoint software (Tivolimanagement agent) installed. It is not necessary to install Tivoli software on theDomino servers with which the Domino Performance Station communicates. Thus,a probe can test client-server communications for any Domino server in thesystem, even when the Domino server is not configured as a Lotus Domino Serverobject in the Tivoli management region. In such cases, you can consider probing tobe a form of proxy monitoring.

Guidelines for creating Domino Performance StationsYou should consider the following factors when you create Domino PerformanceStations:

Deciding how many stations to createYou should create Domino Performance Stations on dedicated computers at everyuser or server site where you want to monitor performance. The stations that youcreate must run probes for every aspect of performance that you need to test.However, you must decide how many Domino Performance Stations you need tocreate. One station might be able to run all probes for a specific site in a network.However, it is more likely that you will have to create multiple stations to performthe probing that you need for a specific site. To estimate the number of probesneeded for each station, you must account for the load that probe transactions addto the network.

Managing system resources for probe transactionsA probe transaction demands time from the system for the following actions: probeexecution, housekeeping, and other overhead functions. The time intervals atwhich you run a probe strongly affect the demand on system resources.

Each Domino Performance Station has a controller that invokes the probe tests atthe intervals that you set, coordinates the execution of multiple probes, andmanages test timeouts.

Minimizing the impact of probe transactionsTo minimize the impact of probe transactions on any individual Notes client, youcan distribute probes to multiple stations at the site you are testing. Presumably all


clients at the site you test link to the same servers for Web, mail, and otherservices. If not, be sure to deploy probes to stations that can test the correctservers.

The number of probes that a single Domino Performance Station can supportvaries with the number and type of probe, the number of times each hour that theprobes execute, and the configuration parameters that you choose. You mustdevelop a customized probe plan to match the characteristics of your system. See“System design guidelines” on page 148 for general information on this topic.

Probe Characteristics

Types of probesThe following Domino Performance Station probes can emulate Notes usertransactions and measure end-to-end response times:v DPSCalendarEntry creates and removes a calendar entry in the test user’s mail

file on the server you specify.v DPSDatabaseAccess accesses a server database from the station client.v DPSNABSearch searches the server you select for a specific pattern in a name

and address book.v DPSNetEcho sends a network data packet to a server using the protocol you

specify.v DPSReplicateLocal replicates a server database to the local Notes client.v DPSRoundTripMail sends an e-mail message from a source server to a target

mail user.v DPSWebAccess accesses a Web page on the server you specify from the station

client.

Scheduling probes

Domino administrators often set up a Domino Performance Station to run multipleprobes of the same type. For example, to run two types of probes against threeNotes mail application servers, a Domino Performance Station needs six probes:three probes of the first type and three probes of the second type. Each of theseprobes receives a test ID that permits IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino to trace results for each test transaction.

Keep in mind the following implications as probes run in a multithreaded mode:v Two probes on a station might run a transaction with the same database. If their

execution overlaps, the resulting transaction time might falsely indicate slowerresponse time.

v Because of the possibility of overlap that arises with multithreading, it is alwaysrecommended that you minimize the number of probes that you run from astation.

v Be aware that a probe execution occurs within a transaction window, a timeperiod within which the probe’s test must execute. This window is defined bythe combination of the execution offset, cleanup period, and probe interval,which are defined as follows:

Execution offsetTime period that the controller delays the launch of the probe. Forexample, after you set one probe’s interval parameter to 10 minutes, thecontroller might calculate an offset of 45 seconds to delay execution inrelation to another probe on the same station. If execution was set to


begin at 12 PM (12:00:00) the controller delays execution 45 seconds. So,execution begins at 12:00:45 and continues in ten-minute intervals at12:10:45, 12:20:45, 12:30:45, 12:40:45, and so on.

Cleanup periodSmall, fixed time period for cleaning up resources allocated during testexecution.

Probe intervalInterval that you set for the repeated execution of a probe transaction.The minimum polling interval is once a day, and the maximum that youcan specify is every 10 minutes.

Configuring a Domino Performance Station

ObjectiveTo create a Domino Performance Station on a Notes client computer and specifythe Domino server or servers that the station is capable of testing.

Background informationA probe tests communication between a client and a server. The servers that aspecific Domino Performance Station communicates with are called tested servers.You specify the Domino server or servers to be tested when you create or edit aDomino Performance Station.

Required authorization roleDomino_DPS_Admin

Note: The Domino_DPS_User role allows you to use one of the commands in thisprocedure: wdpsqueryservers.

Before you beginDetermine where in your Domino environment to set up dedicated Notes clients asDomino Performance Stations.

Every time you create a Domino Performance Station, a profile is createdautomatically.

When you finishDetermine which probes the Domino Performance Station should have and addthose probes, as described in “Configuring probes for a station” on page 156.

Within the Tivoli Desktop, you must not move station objects from their originalpolicy regions. Also, you must not move profiles for station objects from theoriginal profile manager that contains the Domino Performance Station resourcemodels that you deploy.


Command line: Use the following commands to configure a Domino PerformanceStation:v wdpscreate command to create a Domino Performance Station. For example, the

following command creates a station called Station1 on an endpoint calledNotesClient1:wdpscreate Station1 NotesClient1 c:\lotus\notes\notes.ini


v wdpsaddservercommand to add a tested server to the performance stationconfiguration.

v wdpsremoveserver command to remove a tested server from the performancestation configuration.

v wdpsqueryservers command to obtain a list of servers that the performancestation can probe. In general, only the Domino_DPS_Admin role is able toexecute this procedure. However, operators who have the Domino_DPS_Userrole can use the wdpsqueryservers command.

See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for further information about these commands.

Desktop:

1. Open the Messaging and Collaboration policy region or a policy region withinthat region.

2. Select Create → Domino Performance Station to display the Create a DominoPerformance Station dialog box.

3. In the Endpoint Name text box, enter the name of the Tivoli endpoint that youwant to set up as a Domino Performance Station.

4. Type a unique name for the station in the Station text box.The name must conform to the conventions for object-label names that arepresented in the Tivoli Management Framework, Version 3.7.1: User’s Guide.

5. In the Notes INI File text box, enter the path of the notes.ini file for theendpoint.

6. Click Set and Execute to create the station and a corresponding profile.

Note: You used the Tivoli desktop to create a Domino Performance Station.However, the Tivoli desktop does not enable you to query, add, andmodify the tested servers for the station or its probes. Instead of thedesktop, use the command line or Management Console to configuretested servers for a performance station, as described in this procedure.

Management Console:

1. Click the Performance tab of the Management Console.2. Click the Create tool in the Tools - Stations collapsible menu to display the

Create dialog box.

Figure 76. Create a Domino Performance Station dialog box (Desktop)


3. Type a unique name for the station in the text box that is in the Stationsection. The name must conform to the conventions for object-label names thatare presented in the Tivoli Management Framework, Version 3.7.1: User’s Guide.

4. In the Endpoint text box, enter the name of the Tivoli endpoint that you wantto set up as a Domino Performance Station.

Note: Do not configure (create) a Domino Performance Station on an endpointthat you already have configured with a Domino Performance Stationor with a Lotus Domino Server object. Such a configuration cangenerate invalid performance data and can cause resource conflicts.

5. In the INI File Location text box, enter the path of the notes.ini file for thatendpoint.

6. (Optional) In the TEC Server text box, enter the location of the TivoliEnterprise Console server.

7. If you want to add tested servers at this time, click Add Server in the TestedServers section to display the Add Server dialog box.Additional information: The following options are available in the TestedServers section:

Figure 77. Create dialog box (Management Console)


8. Complete the following text boxes in the Add Server dialog box to supply thearguments for a tested server:

Server NameThe common name of the Domino server.

Host The host name or IP address of the host on which the Domino serverresides.

ID FileThe location of the test user ID file for this server. You can use anabsolute path or a path that is relative to the Notes data directory.This file must be present on the station or accessible from the stationon a shared network location.

PasswordThe password to authenticate the test user ID.

Mail DBThe relative path to the test user’s mail file on the server.

9. Click OK in the Add Server dialog box to add the server to the TestedServers list.

10. Click OK in the Create dialog box to create the tested server.Select a server name in the Tested Servers list and perform one of thefollowing actions:v Click edit to access the Edit Server dialog box.

—OR—v Click delete to access the Delete Server dialog box.

11. Click OK to create the station and return to the Performance pane. The nameof the new station is displayed in the Station tree view on the left side of theconsole.

Note: Every time you create a Domino Performance Station, a profile iscreated automatically. Within the Tivoli Desktop, you must not movestation objects from their original policy regions. Also, you must notmove profiles for station objects from the original profile manager thatcontains the Domino Performance Station resource models that youdeploy.

Add tested server:

Edit tested server:

Delete tested server:

Figure 78. Tested Servers buttons in the Add Server dialog box (Management Console)


Configuring probes for a station

ObjectiveTo configure a probe for a Domino Performance Station.

Background informationWhen you are configuring probes, specify thresholds that reflect service levelagreements (SLAs) and configure the probes to generate alerts that support theSLAs. Before you add a probe, consider how you will use the data it generates.


Before you beginFirst, you must create a Domino Performance Station as described in “Configuringa Domino Performance Station” on page 152. In creating the Domino PerformanceStation, the product also creates a profile.

Next, you run a test probe to verify configuration settings, as described in“Running a probe one time” on page 166. If probing fails, you should manuallyrun the transaction from the actual Notes client to verify that the client has accessto resources.

When you finishRun an integrity check to verify that the probe is loaded in the DominoPerformance Station, as described in “Checking the integrity of a performancestation” on page 169.


Command line: Use the following commands when configuring probes:v wdpsqueryprobes command to obtain a list of probes on a Domino Performance

Stationv wdpsaddprobe command to add a probe to a Domino Performance Station

See IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for more information.

Management Console:

1. Click the Performance tab of the Management Console.2. In the Station list, select the station to which you want to add a probe. The

Probe list in the middle of the console refreshes to display any probes that arealready assigned to the station.

3. Click the Probes tab to display the Probe list.4. Click one of the following options above the Probe list:

v Click Add Probe to add a probe to display the Add Probe dialog box.


—OR—v Click Edit Probe to edit a selected probe.

The Edit Probe dialog box is displayed.

5. If you are in the Add Probe dialog box, provide a Probe ID by performingone of the following steps:v Leave the check mark in the Auto-generate check box if you want the

product to provide the Probe ID.Additional information: The auto-generated number is unique within thisstation’s list of currently configured probes. You can replace or modify theauto-generated number.

v Delete the check mark in the Auto-generate check box if you want toprovide the number for the Probe ID, and type the number in the Probe IDtext box.Additional information: Type a unique number for the Probe ID, or youwill receive an error message.

Figure 79. Add Probe dialog box (Management Console)

Figure 80. Edit Probe dialog box (Management Console)


6. Select the server from the Server drop-down list.7. Select the type of probe you want to add from the Probe Type drop-down list.8. Type the number of milliseconds for the threshold in the Threshold text box.9. Select an interval for the probe from the Interval drop-down list.

Additional information: The default interval for all probes is 30 minutes.10. When the probe you are adding or editing has arguments, enter the argument

values in the text boxes that are in the Arguments area of the Add Probedialog box.Additional information: Each probe requires different types of arguments.The arguments that appear in the Arguments area of the Add Probe dialogbox are specific to the type of probe you are adding or editing. All argumentsare case sensitive. See the IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino Reference Guide for descriptions of each probe and its arguments.If you change the argument values, select a different probe type, and thenreturn to the previous probe type, the values revert to the defaults.

11. Click OK to add the probe to the list of probes for the Domino PerformanceStation.

12. Click Reset Probes in the tool bar above the Probe list to distribute theupdated probe set to the station.

13. Add a resource model to the probe to collect probe data for a profile managerusing one of the following procedures:v “Adding a default resource model to a profile” on page 65v “Adding a custom resource model to a profile” on page 69

Configuring a resource model to monitor probes

ObjectiveTo configure a resource model to monitor probing on a Domino PerformanceStation.

Background informationThere is one resource model for each probe type:v DPSCalendarEntryv DPSDatabaseAccessv DPSNABSearchv DPSNetEchov DPSReplicateLocalv DPSRoundTripMailv DPSWebAccess

A resource model does not contain probe information, but collects probeinformation from the probe station log. Each time a resource model runs it collectsall of the probe information for the particular probe type. The resource modelgenerates indications and events based on the thresholds that you define for eachprobe. If you do not create a probe that corresponds to the resource model, theresource model does not collect any data. Creation of probes on a DominoPerformance Station is a separate procedure described in “Configuring probes for astation” on page 156.

Required authorization rolesenior, super, or admin


Before you beginCreate probes on Domino Performance Stations as described in “Configuringprobes for a station” on page 156.

When you finishView probe results in the health console within the Management Console asdescribed in Chapter 8, “Working with health data” on page 191.


Command line: Use the wdmeditprf command to add a customized resourcemodel to a profile.


Desktop:

1. Double-click the icon of the Domino Performance Station Resource Modelprofile manager in the Messaging and Collaboration policy region.

2. Double-click the monitoring profile icon that has the same name as thesubscriber station to display the IBM Tivoli Monitoring Profile dialog box.

Note: Every time you create a Domino Performance Station, this profile iscreated automatically.

3. Click Add to display the Add Resource Models to Profile dialog box.4. Select the All Domino Resource Models category from the Category

drop-down list.Additional information: Use the IBM Tivoli Monitoring Workbench to modifythese categories and add other categories.

5. Select one of the Domino Performance Station resource models from theResource Model drop-down list.Additional information: The names of these resource models begin with ″DPS,″for example, DPSCalendarEntry.

6. Set the frequency with which the resource model monitors the data in theCycle Time text box.

7. Click Indications to display the Indications and Actions dialog box.8. Select an indication in the Indications list if you need to modify one of its

settings. The fields for the indication are enabled so that you can edit them.9. Click Tasks in the right side of the dialog box to select a task that runs

whenever this indication generates an event. See “Specifying tasks for anindication” on page 80 for more information.

10. Click Change and Close.11. Choose one of the following options in the Add Resource Models to Profile

dialog box if you need to modify default settings for schedules or logging:v Click Parameters to modify the parameters for the resource model. See

“Customizing parameters” on page 85 for more information.—OR—

v Click Schedule to modify the default schedule information in theScheduling dialog box. See “Customizing a schedule for a resource model”on page 88 for more information.


—OR—v Click Logging to modify logging behavior in the Logging dialog box. See

“Customizing data logging information” on page 93 for more information.12. Click Add & Close to save your changes. The IBM Tivoli Monitoring Profile

dialog box now shows the customized resource model.

Management Console:

1. Do the following to access the policy region, profile manager, and profile towhich you want to add a customized resource model.a. Click the Configuration tab of the Management Console.b. Click the Profiles tab to see a tree view of policy regions and profile

managers.c. Click the policy region in the tree view that contains the profile manager to

display a list of profile managers is displayed in the tree view.d. Click the Domino Performance Station Resource Models profile manager

that contains the station profiles to which you want to add a resourcemodel. A list of resource models or events is displayed under the Profileslist.

2. Click Add Resource Model in the menu bar directly above the ResourceModel list to display the Add Resource Model tabbed dialog box, with theBasics dialog box on top.

3. Select the All Domino Resource Models category from the Categorydrop-down list.

4. Select one of the Domino Performance Station resource models from theResource Model drop-down list.Additional information: The names of these resource models begin with ″DPS,″for example, DPSCalendarEntry.

5. Change the Cycle Time to the number of seconds you want to lapse betweeneach of the times that the resource model runs.

6. Click one or more of the other tabs one at a time to change the followingsettings:Additional information: A tab is not active if you cannot customize the settingsfor that tab.v Indications (occurrences, holes, where to send events, severity, tasks)




v ScheduleSee “Customizing a schedule for a resource model” on page 88 for how toset the schedule for running a resource model.

v Click OK to add the customized resource model with all of its customizedsettings.Additional information: The name and category of the customized resourcemodel is displayed in the list of resource models with a check mark in theenabled check box.


Deleting a Domino Performance Station

ObjectiveTo delete a Domino Performance Station.

Background informationDeletes a Domino Performance Station from the Tivoli management region andremoves performance station software from the Notes client computer.





Command line: Use the wdpsdelete command to delete a station.

For more information about this command, refer to the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide.

Desktop:

1. Double-click the icon of the policy region that contains the station that youwant to delete to display its Policy Region window.

2. Click the icon of the station that you want to delete.3. Click Edit and select Delete to display the Delete Objects? confirmation box.4. Click Yes to delete the station.

Management Console:

1. Click the Performance tab of the Management Console.2. In the Station tree view on the left side of the console, select the station that

you want to delete.3. Click Delete in the Tools - Stations collapsible menu to display the Delete

dialog box.4. Click OK in the Delete dialog box.

Controlling a station

ObjectiveTo start, stop, or restart the controller for a Domino Performance Station.

Background informationIn the command line interface and in the Management Console, you can start, stop,and restart the controller on an individual Domino Performance Station. Keep inmind that the actions you take on Domino Performance Stations affect probing of aDomino server or servers.


In the Tivoli desktop, you can run Tivoli tasks that start, stop, or restart a DominoPerformance Station. These Tivoli tasks are primarily useful for controlling probingwhen you are performing scheduled server maintenance.





Command line: Use one of the following commands to control DominoPerformance Stations:v wdpsstart command to start probing on the station you specify.v wdpsstop command to stop probing on the station you specify.v wdpsreboot command to restart the operating system on the station you specify.

When the workstation restarts, the Tivoli endpoint process restarts if it isconfigured as a Windows NT service. If the process is not configured as aservice, the process does not restart automatically and you must restart theprocess manually.

v wruntask command with the following tasks:– Start Station

– Stop Station

– Reboot Station


Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Start Station

v Stop Station

v Reboot Station

. See IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for a description of the desktop options for these tasks.

Management Console:

1. Click the Performance tab of the Management Console.2. In the Station tree view on the left side of the console, select one or more

stations on which you want to perform an operation.3. Click Start/Stop/Reboot in the Tools → Stations collapsible menu to display the

Start/Stop/Reboot dialog box.


4. In the Start/Stop/Reboot dialog box, select one of the following options:v Select Start to start the station.v Select Stop to stop the station.v Select Reboot to restart the station.

5. Click OK.

Controlling resource models for stations

ObjectiveTo start or stop the IBM Tivoli Monitoring for Messaging and Collaborationresource models on a Domino Performance Station.






Command line: Use the following commands to start and stop resource modelsfor a Domino Performance Station:v wdmeng command with the -start parameter to start probing.v wdmeng command with the -stop parameter to stop probing.

For more information, refer to the IBM Tivoli Monitoring, Version 5.1.0: User’sGuide.

Management Console:

1. Click the Performance tab.2. Click the Health subtab.3. Right-click the resource model you want to start or stop to display the pop-up

menu.

Figure 81. Start/Stop/Reboot dialog box (Management Console)


4. Select one of the following options:v Start Resource Model

v Stop Resource Model

v Start All Resource Models of the Same Profile

v Stop All Resource Models of the Same Profile

Additional information: When you start a resource model, the Running isdisplayed in the Status column next to the name of the resource model. Whenyou stop a resource model, Stopped is displayed in the Status column.

Deleting probes

ObjectiveTo delete a single probe or multiple probes from a Domino Performance Station.

Background informationNone



When you finishReset probes as described in “Resetting probes” on page 165.


Figure 82. Start/Stop Resource Model pop-up menu for a station (Management Console)


Command line: Use the following commands to delete one or more probes:v wdpsdeleteprobe command to delete a single probe from a Domino

Performance Station.v wdpsclearprobes command to clear all of the probes from a Domino

Performance Station.


Management Console:

1. Click the Performance tab of the Management Console.2. In the Station tree view on the left side of the console, select the station from

which you want to delete a probe.3. Click the Probe tab to see the Probe list in the middle of the console.4. Choose one of the following options:

v Delete a single probe by performing the following steps:a. Select the probe you want to delete.b. Click Delete Probe in the Probe menu above the Probe list.c. Click Yes in the Confirm Delete dialog box.

—OR—v Delete all of the probes in the list by doing the following.

a. Select the probe you want to delete.b. Click Clear Probes in the Probe menu above the Probe list.c. Click Yes in the Confirm Clear dialog box.

Resetting probes

ObjectiveTo reset all the probes on a Domino Performance Station.

Background informationYou reset the probes when:v Probes have stopped functioning correctly.v Stopping and immediately restarting the probes can fix the problem.

In the Management Console, you reset probes by clicking a single commandoption.


Before you beginRun an integrity check, as described in “Checking the integrity of a performancestation” on page 169. This test can show whether probing is producing a recurringerror.

Use the Probe Once function to analyze network and server conditions that mightinterfere with the correct functioning of probes, as described in “Running a probeone time” on page 166.




Command line: Use the wdpsresetprobes command to send currently configuredprobes for an existing Domino Performance Station to the endpoint.

For more information about this command, see the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide.

Management Console:

1. Click the Performance tab of the Management Console.2. In the Station tree view on the left side of the console, select the station on

which you want to perform the operation. The Probe list in the middle of theconsole refreshes to display probes for the station.Additional information: An asterisk (*) after a probe name indicates that theprobe was modified, but not updated on the station endpoint.

3. Click Reset Probes above the probe list.

Running a probe one time

ObjectiveTo run a test probe from a Domino Performance Station against a Domino server.

Background informationThe Probe Once functionality offers the following benefits:v It enables a technician to perform single tests in response to requests for

information from Notes users or from Domino administrators.v It runs a probe one time, before you deploy it to run continuously. This single

instance of execution allows you to check server connections and probe settingsand to validate access to resources that might cause it to fail.

v It returns a breakdown of a transaction, including status and response timeinformation for primary and secondary transactions associated with the probe

The timeout parameter of this diagnostic tool enables you to set a limit for theamount of time that the tool waits for data from a probe. If the probe times outbefore the probe transaction completes, the probe continues to run, and the toolreturns a probe ID, which you can use with the Probe Status tool to check thestatus of a probe test.

This tool accepts specific execution arguments depending on the type of probe youchoose to run. See the IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino Reference Guide for a description of these arguments.

Required authorization roleDomino_DPS_User

Before you beginBefore you run a probe on a Domino Performance Station, you must create andstart the station and link it to tested servers, as described in “Configuring aDomino Performance Station” on page 152.


When you finishIf the probe times out before the probe transaction completes, you can use theprocedure in “Checking probe status” on page 168 to check the status of the ProbeOnce transaction.

After you test individual probes, you can deploy them to that run at specificintervals, as described in “Configuring probes for a station” on page 156.


Command line: Use the wdpsprobeonce command to run a probe against aserver one time.


Management Console:


you want to probe.3. Click Probe Once in the Tools - Diagnostics collapsible menu to display the

Probe Once dialog box.

4. Type a unique name for the station in the text box that is in the Stationsection. The name must conform to the conventions for object-label names thatare presented in the Tivoli Management Framework, Version 3.7.1: User’s Guide.

Figure 83. Probe Once dialog box (Management Console)


5. Choose a server from the list of tested servers in the Server Name drop-downlist.

6. Choose the probe you want to run in the Probe drop-down list.7. Type arguments for probe execution in the Arguments text box, separated by

semicolons.8. (Optional) In the Results Timeout (sec) text box, enter a value, in seconds, for

the amount of time to wait for probe data to execute.9. Click Execute.

10. (Optional) If the probe times out, record the ID number of the transaction thatthe Results area displays for use with the Probe Status tool. You must havethe identification number to run a status check on a probe transaction.

11. Click Close to dismiss the Probe Once dialog box.

Checking probe status

ObjectiveTo check the status of a probe that you started with the Probe Once functionality.

Background informationThis procedure queries a Domino Performance Station for the last value returnedfrom a scheduled probe or a probe that timed out after being started with theProbe Once functionality. This tool is useful for following the status of Probe Oncetransactions that require more than a few minutes to complete or that mightbecome caught in an endless loop. To check the status of a Probe Once transaction,you must have the probe ID that Probe Once generates when it times out.





Command line: Use the wdpsprobestatus command to check the status of aprobe transaction.


Management Console:


contains the probe for which you want to check status.3. Click Probe Status in the Tools - Diagnostics collapsible menu to display the

Probe Status dialog box.


4. Type a unique name for the station in the text box that is in the Station section.The name must conform to the conventions for object-label names that arepresented in the Tivoli Management Framework, Version 3.7.1: User’s Guide.

5. Type the probe ID in the Probe ID text box. A probe ID might be one that isgenerated from a timeout of the Probe Once command. Alternatively, a probeID may be one specified when creating a scheduled probe.

6. View the Results area of the dialog box to see the status of the transaction.The Results area can display the data resulting from the probe, a message thatthe data is not yet available, or a message that the probe expired withoutreturning any data.

7. Click Close.

Checking the integrity of a performance station

ObjectiveTo check the integrity of the Domino Performance Station.

Background informationThis procedure checks the status (up, down, or recurring error) of the controllerand the probes on a Domino Performance Station.

The DPSIntegrity resource model also monitors the state of a Domino PerformanceStation and its probes. If a resource such as a port, Domino database, or web pageis unavailable, a probe may generate an error. If this happens consistently, theDPSIntegrity resource model will catch this and generate an event.


Before you beginYou must create a Domino Performance Station to check, as described in“Configuring a Domino Performance Station” on page 152.

Figure 84. Probe Status dialog box (Management Console)




Command line: Use the wdpsintegrity command to check the integrity of astation.


Management Console:

1. Click the Performance tab of the Management Console.2. In the Station tree view on the left side of the console, select the station whose

integrity you want to check.3. Click Integrity in the Tools - Diagnostics collapsible menu to display the

Integrity dialog box.

4. Type a unique name for the station in the text box that is in the Station section.The name must conform to the conventions for object-label names that arepresented in the Tivoli Management Framework, Version 3.7.1: User’s Guide.

5. Click Execute to display the status of the controller (up or down) and itsprobes in the Results area of the dialog box to see the status.

6. Click Close.

Figure 85. Integrity dialog box (Management Console)


Chapter 7. Working with tasks and jobs

A task is an action that must be routinely performed on selected managed nodesthroughout the network. A task defines the executables to be run, the authorizationrole required to execute the task, and the user or group name under which the taskexecutes. The product provides standard tasks in a task library. Standard tasks runon any machine without consideration of platform type.

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

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 immediatelyusing the procedure described in “Running jobs” on page 184. You also canschedule jobs to run at certain times in the Scheduler, as described in “Schedulingjobs” on page 185.


Table 12. Goals and where to find procedures for working with tasks and jobs


1. Run a task to perform a specific operation. “Running tasks” on page 172

2. Define a standard task with specific argumentsto customize the task.

“Customizing a task” on page 176

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

“Creating jobs” on page 180

4. Run a job with predefined arguments. “Running jobs” on page 184

5. Schedule jobs to run at specified times. “Scheduling jobs” on page 185

The installation process installs the task library in the product policy region. Werecommend that you do not remove the task library from this policy region. Thetask library contains default policies that affect how the task library works.

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


This product provides several task libraries that contain various tasks supportinggeneral Domino monitoring and administration operations. The task libraries arestored in the Messaging and Collaboration policy region and are labeled asfollows:v Domino Performance Station Tasks — Tasks that start, stop, and restart Domino

Performance Stations and probes.v Domino Server Tasks — Tasks that perform server and database operations.v Messaging and Collaboration Configuration — A task that configures this

product to send events to the Tivoli Enterprise Console.

Note: Domino tasks are operations that you perform in the Lotus Dominoenvironment. This user’s guide refers to these tasks as ″Domino tasks″ toavoid confusion with Tivoli tasks. In all other cases, the word ″task″ refersto Tivoli tasks. See the IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino Reference Guide for a complete description of each task in thetask libraries for this product.

Running tasks

ObjectivePerform a routine action on a selected managed node.

Background informationA task is an action that must be routinely performed on selected managed nodesthroughout the network. A task defines the executables to be run, the authorizationrole required to execute the task, and the user or group name under which the taskis run. The product provides standard tasks in a task library. Standard tasks run onany machine without consideration of platform type.

See the introduction of this chapter for more information on tasks.

Required authorization rolesDomino_Admin




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 using the wruntask command with Lotus DominoServers and Domino Performance Stations, see the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide


The Tasks chapter of the IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino Reference Guide provides syntax statements and examples.

Desktop:

1. Open the task library window by doing the following:a. Double-click the policy region icon to display the policy region.b. 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 Taskdialog box.Additional Information: The Execute Task dialog box is a generic dialog box ofexecution parameters for all tasks.

Figure 86. Task Library window (Desktop)

Chapter 7. Working with tasks and jobs 173

3. Select 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 for each stage) and the Staging Interval (number of seconds betweeneach 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 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

Figure 87. Execute Task dialog box (Desktop)


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. Select one or more of the following check boxes in the Output Format groupbox to choose the output returned upon task completion:

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

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 Select Display on Desktop to display the task output on the desktop.

Additional Information: If you choose Display to Desktop, you have an optionto 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 dialog box.

b. Type the name of the managed node on which to save the output in the OnHost text box.

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 Task dialogbox.

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 to move the selected endpoints to the Selected Task

Endpoints list.

—OR—

Figure 88. Destination for Task Output dialog box (Desktop)


v Run the task on all subscribers of the specified profile managers by doing thefollowing:a. Select profile managers from the Available Profile Managers list.b. Click the left arrow to move the selected profile managers to the Selected

Profile Managers list.8. Click Execute to display the dialog box for configuring task arguments.

Additional Information: For information about how to fill in the dialog box forconfiguring task arguments, refer to the task description in the softwarereference guide, click Task Description to display the online help, or refer tothe specific procedure in this user’s guide.

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



Figure 89. Dialog box for configuring task arguments (Desktop)


When you finishYou can run the task by following the procedure in “Running tasks” on page 172.When you run a customized task, the Tivoli desktop does not display the dialogbox for configuring task arguments.

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

a. Double-click the policy region icon to display the policy region.b. 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.Additional Information: The Execute Task window is a generic dialog box ofexecution parameters for all tasks. Complete this dialog box to run the task asdescribed in “Running tasks” on page 172.

Figure 90. Task Library window (Desktop)


3. Click Execute to display the dialog box for configuring task arguments.

Additional Information: Each standard task has a unique argument dialog box.

Figure 91. Execute Task dialog box (Desktop)

Figure 92. Dialog box for configuring task arguments (Desktop)


4. If there are fields to complete, type the appropriate values for this customizedtask.Additional Information: For information about each field in these dialog boxes,see the task description in the product reference guide or click TaskDescription to display the online help.

5. Click Save to display the dialog box for saving arguments.

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.Example: SQL_SYS

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 CurrentRunningSQL). Thesecond part should be descriptive information that makes sense to you.For example, you could type SYS. The resulting task name would beCurrentRunningSQL_SYS.The software generates a unique default name (such asCurrentRunningSQL_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 dialog box for configuring task arguments for thiscustomized task.

Figure 93. Dialog box for saving arguments (Desktop)


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 dialog box for configuring taskarguments.

7. Click Cancel in the dialog box for configuring task arguments.8. Click Close in the Execute Task dialog 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 jobs

ObjectiveTo create a job by defining execution parameters so you can specify a targetenabling you to schedule it to run at certain times in the Scheduler.

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, you store jobs in tasklibraries so you can reuse them.



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


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 mannode_name –f file_name] [–h mannode_name][–p prof_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.

Desktop:

1. Access the task library window by doing the following:a. Double-click the policy region icon to display the policy region.b. 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 dialog

box.


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.

Figure 94. Create Job dialog box (Desktop)


—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 endpoints toinclude in each staged set in the Staging Count text box and the number ofseconds between each set’s startup time in the Staging Interval text 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 to

Step 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 dialog box. Go to Step 11.

11. Do the following in the Destination for Task Output dialog box to save thejob output to a file:

Figure 95. Destination for Task Output dialog box (Desktop)


a. Type a Tivoli client managed node name on which to save the output inthe On Host text box.

b. Type the absolute path name for the output file in the Output File textbox.Additional Information: Example: /tmp/myjob.out

c. Click Set & Close to set your choices and return to the Create Job dialogbox.

12. Do one of the following to choose the endpoints on which to run the job:v Run the job on specific endpoints by doing the following:

a. Select the endpoints from the Available Task Endpoints list.b. Click the left arrow to move the selected endpoints 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 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 jobs

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 jobs” onpage 180.

If you created a job from a standard task, the Tivoli desktop displays the dialogbox for configuring task arguments so that you can fill in any requiredinformation.

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



When you finishAfter you create a job, you can set it up to run on a regular schedule as describedin “Scheduling jobs” on page 185.



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. Double-click the policy region icon to display the policy region.b. 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 dialog box.

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 jobs

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 jobs” on page 180.





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. Double-click the product policy region icon to display the policy region.b. 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 locatedon the Tivoli desktop.

3. Optional: Do the following if a dialog box for configuring task argumentsdisplays:a. Type the appropriate information for each field in the dialog.

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 dialog box.

4. Type a label for the job icon in the Job Label text box of the Add ScheduledJob dialog box.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.

Figure 96. Add Scheduled Job dialog box (Desktop)


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. Select any of the following check boxes in the When Job Completes groupbox to send job completion notification:v Send a notice to a specific group by doing the following:

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

box.

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. Select 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. Select 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. Select 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 dialog.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 dialog

box.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 dialog box.

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 runssuccessfully.—OR—

v Specify the number of times a job attempts to run by doing thefollowing:1) Select the Retry the job check box.

Figure 97. Set Retry/Cancel Restrictions Options dialog box (Desktop)


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. Select 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 dialogbox.

11. Click Schedule Job & Close to schedule the job and return to the Tivolidesktop.



Chapter 8. Working with health data

There are two interfaces that you can use for working with real-time and historicalhealth data for resources:v IBM Tivoli Monitoring Web Health Console

Access to the IBM Tivoli Monitoring Web Health Console is through a Webbrowser. See the IBM Tivoli Monitoring User’s Guide for information about how toinstall and use the IBM Tivoli Monitoring Web Health Console features forgraphing, drill-down, and control of resource models.For complete information on installing and working with the IBM MonitoringWeb Health Console see the latest version of the IBM Tivoli Monitoring User’sGuide.The IBM Monitoring Web Health Console runs on Netscape 6.x and InternetExplorer 6.x. You can use the IBM Monitoring Web Health Console for thefollowing purposes:– Checking, displaying, and analyzing the status and health of endpoints that

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

Tivoli Monitoring database– Viewing online and historical data on endpoints as a follow-up to specific

problems– Starting and stopping the IBM Tivoli Monitoring engine and individual

resource models on selected endpoint– Removing a profile from the selected endpoint

v IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoManagement ConsoleAccess to the health console that is in IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino is through the Management Console in thissoftware. This chapter provides information about working with health datathrough the Management Console.

You can use these interfaces to check, display, and analyze the status and health ofany endpoint with profiles and resource models. Status reflects the state of theendpoint such as running or stopped. Health is a numeric value determined byresource model settings. You can also work with real-time or historical data froman endpoint that is logged to the IBM Tivoli Monitoring database.

You can use the diagnostic and monitoring capabilities of these interfaces toperform targeted analysis of problems associated with individual endpoints whenan event is sent to the Tivoli Enterprise Console. Use the online and historical datato follow up specific problems with single endpoints.

Understanding Resource HealthThe health data interfaces obtain events and indications from endpoints. Theydisplay the health of each potential problem as a numeric value between 100(perfect health) and zero (with zero meaning that the conditions for thecorresponding event are met). Intermediate values show the percentage ofoccurrences currently registered with respect to the total number of occurrencesneeded to trigger an event. See Table 13 on page 192


Table 13. 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

Health % 100 75 75 50 25

Table 13 displays the health percentage changes in steps of 25% because 4occurrences 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 installed on anendpoint is shown as the health of that endpoint. For example, if one indication onone resource model that is installed 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.


Table 14. Goals and where to find procedures for working with health data


Check the health of resources in real-time or ashistorical data

“Checking the health of resources asreal-time data” on page 193

“Viewing historical data” on page 203

Customize and set preferences for data views “Customizing data views and settingpreferences” on page 196

Save, export, and print data and reports “Saving, exporting, and printing dataand reports” on page 203

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.

Management ConsoleThe health console that is part of the Management Console of IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino consists of a resourcenavigation tree in the left column and a center pane of data composed of threetables. The navigation tree contains Lotus Domino Server or Domino PerformanceStation resources. The three tables in the center pane contain resource model data.


The navigation tree contains either a list of Lotus Domino server objects or a list ofDomino Performance Station objects. When grouping the servers by health, theserver navigation tree contains a list of servers in four health categories, onecategory for each level of health status. The tree lists the categories in increasinghealth, so that the least healthy category (health range 0 to 5%) is the top node inthe tree. If there are no servers for a specific category, the category node does notdisplay in the tree. The category node has a thermometer icon to the right of thecategory icon. The category node label indicates the health range as a percentage.The thermometer icons are different colors, one for each of the four categories ofserver health status:v green 31 – 100 healthv orange 6 – 30 healthv red 0 – 5 healthv gray – unknown health

The order of the servers in the list under the category label is from least healthyserver at the bottom of the list to most healthy servers at the top of the list.

You can group the Domino Performance Station by All Stations or Tested Servers.Grouping by health is not supported.

The center pane of the health window displays data in the following three tables:v Resource Model (top)

The Resource Model table contains a list of resource models for the selectedserver or station. The table also provides the status and health of each resourcemodel.

v Indications (bottom left)The heading of the Indications table is the name of the resource model selectedin the Resource Model table. The Indications table contains a list of indicationsfor the selected resource model and a value for the health of each indication.

v Instance (bottom right)The heading of the Instance table is the name of the indication selected in theIndications table. This table lists all instances of any indication selected in theIndications table that has a Health status that is less than 100.

Checking the health of resources as real-time data

ObjectiveTo obtain data about the health of a Lotus Domino Server or Domino PerformanceStation to identify potential problems with these resources.

Background informationWhen you display the data for a server or station, you can sort and filter the datawithin the Resource Models, Indications, and Instances tables. Sorting provides alist that is in ascending or descending order according to health value.

Required authorization roleuser


Chapter 8. Working with health data 193

When you finishUse the Server tools to manage Lotus Domino Servers, the Stations tools tomanage Domino Performance Stations, and the Diagnostic tools to performdiagnostic operations.

ProcedureYou can perform this procedure from the Web Health Console or the ManagementConsole.

Web Health Console: See the ″Working with the Web Health Console″ chapter inthe IBM Tivoli Monitoring User’s Guide for information.

Management Console:

Displaying data: Display data for servers and stations by doing the following:1. Display the health data in the management console by doing one of the

following depending on whether you are checking the health of a server or astation:v Display the health window for servers by clicking the Status and Operations

tab in the Management Console.

—OR—v Display the health data for stations by doing the following:

a. Click the Performance tab in the Management Console.b. Click the Health tab in the center pane.

Figure 98. Health window for Lotus Domino Servers (Management Console)


2. Select the category of resources you want to check from the Group bydrop-down list in the navigation column by doing one of the following:v If you are in the Status and Operations tab, select Health in the Group by

menu to display a tree view containing a list of servers with color-codedhealth status in four categories.—OR—

v If you are in the Performance tab, select any group to display a tree viewcontaining a list of stations.

3. Click the resource that you want to check in the tree view to display theResource Model table in the center pane of the window.Additional information: The Resource Model table is a list of resource models thathas been distributed to the IBM Tivoli Monitoring engine on that server orstation.

4. Click the resource model that you want to check from the Resource Model tableto display the Indications table in the bottom left part of the center pane.Additional information: The Indications table lists the indications for the selectedresource model.

5. Click any indication with a health value less than 100 to display the Instancestable in the bottom right part of the center pane.Additional information: The Instances table lists all instances of the indicationselected in the Indications table that has a Health status that is less than 100.

6. Double-click the instance in the Instances table for which you want to displayreal-time data.

Sorting data: Sort the data within the Resource Models, Indications, and Instancestables by doing the following:1. Place the cursor in the column header of the data you want to sort.2. Click the up or down arrow that is on the right side of the column header to

sort in ascending or descending order.Additional information: After the data sorts, the arrow that indicates the order ofthe data is highlighted.

Filtering data: Filter the data within the Resource Models, Indications, andInstances tables by doing the following:1. Place the cursor in the column header of the data you want to filter.

Figure 99. Health window for Domino Performance Stations (Management Console)


2. Right-click the header to display the pop-up menu, and select Show Filter Rowto display the filters that are set for each column under the column header.

Additional information: The default setting for the filters is no filter.3. Click the filter for the column you want to display the Edit Filter dialog box.

4. Set the filtering values by doing the following:a. Type the text you want to filter in the Enter text to filter text box.b. Select Contains or Starts with from the drop down list under the text box.c. Select or clear the Match case check box.d. Click OK to close the Edit Filter dialog and display the main view.

Customizing data views and setting preferences

ObjectiveTo customize the settings for viewing health data so the data is displayed in formsthat are the most meaningful to you and others who will view it. You cannot savethe settings as preferences for future use.

Figure 100. Filter menu (Management Console)

Figure 101. Edit Filter dialog box (Management Console)


Background informationA data view is a window that contains a table or one of five types of charts thatrepresent the data that the resource model collects. Use a data view to customize,print, and export data.

Figure 102 shows the dialog box for the data view in bar chart format.

The data view in any chart format contains the following areas from top to bottomand left to right:v Action barv Preferences area with drop-down list (Only the Default Settings are available in

the Management Console.)v Switch View toolbar with icons for a table and various types of chartsv Name of the instancev Chart area that displays the type of chart selected in the Switch View toolbar.

You can change the properties for the following parts of the chart area:– Y Title– Header– X Title– Chart area– Footer– Legend

v Timev Status area

Figure 103 on page 198 shows the dialog box for the data view in table format.

Figure 102. Data view in bar chart format (Management Console)


The data view in table format contains the following areas from top to bottom andleft to right:v Action barv Preferences area with drop-down list (Only the Default Settings are available in

the Management Console.)v Switch View toolbar with icons for a table and various types of chartsv Table with instance name and the following columns of data: Time, TotalCache,

PagesSec, TotalWorking Set, TotalAvailv Status area

You can customize the chart view and the table view to display the toolbar,preferences, or status. You can also display the data in a table or the followingdifferent types of charts, unless the data cannot be represented in a particularformat: bar, line, area, stack, and pie.


Before you beginOpen the graph for online data by right-clicking the instance to display the onlinedata view. Or, open the graph for historical data by right-clicking the resourcemodel.

When you finishFor more information about saving, exporting, and printing data and reports, see“Saving, exporting, and printing data and reports” on page 203.


Figure 103. Data view in table format (Management Console)



Management Console:

1. Customize the data view through the Options menu by doing the following:a. Click Options on the action bar, and select one or more of the following

areas to display in the dialog box for the instance:v Tool Bar Area

v Preferences Area

v Status Area

Additional information: You can also set these options through the Framesettings as described in step 2c of this procedure.

b. Click the type of graphical representation you want to display from thetoolbar:v Bar chartv Line chartv Area chartv Stack chartv Pie chartv Table

Additional information: You can switch to any type of chart that can representthe data. You can also select the type of graphical representation throughthe General settings as described in step 2b of this procedure.

2. Customize the data view by setting preferences (which cannot not be saved inthe Management Console) as follows:a. Click Options and select Preferences to display the Default Settings:

Preferences dialog box.b. Change the general settings of the data view by doing the following:

1) Select General in the left column, if it is not already selected.2) Select the type of view you want from the View Type drop-down list:

v Barv Linev Areav Stackv Piev Table

3) Type the maximum number of points that you want the view to collectin the Buffer Size text box.Additional information: The maximum value that you can specify for thebuffer size is 1000. The default setting is 250.

c. Change the Frame settings of the data view window by doing the following:1) Select Frame in the left column of the Default Settings Preferences

dialog box to update the right pane of the dialog with the fields thatapply to the frame.

2) Set the Dimensions, Options, and Title properties as follows:

Width Specify a number for the width of the data view window.


HeightSpecify a number for the height of the data view window.

Tool Bar VisibleSelect this check box to show the toolbar in the data viewwindow.

Status Area VisibleSelect this check box to show the status area in the data viewwindow.

Preferences Area VisibleSelect this check box to show the preferences area in the dataview window.

Title Specify a title for the data view window.3) Click OK to close the dialog box and reopen the data view.

Note: The settings that you specify apply immediately, but they are notsaved when you close the data view.

d. Change the Chart View settings of the data view by doing the following:1) In the left column of the Default Settings: Preferences dialog box, click

Chart View.Additional information: This is equivalent to double-clicking the chart thatis within the data view.

2) Set the General colors, Points Labels, and Line View properties asfollows:

Series ColorsClick the option corresponding to the color to use for the series.

Background ColorClick this field to select the color for the background.

Label FontClick Change to specify the type and size of the font to use forthe labels.

Label AnchorDisplay the list of values and select where to position the labels.

Labeling ModeSelect the radio option corresponding to the way you want todisplay the labels.

Symbol StylesClick the option corresponding to the symbol and color to usefor the Line view.

Note: The settings that you specify apply immediately, but they are notsaved when you close the data view.

e. Change the settings for the specific parts of the Chart View (Y Title, Header,X Title, Chart Area, Footer, and Legend) by doing the following:1) Change the Chart Area settings by doing the following:

a) In the left column of the Default Settings: Preferences dialog box,expand Chart View and select Chart Area.

b) Change the settings for the Chart Area by doing the following:


i. Set the General, Colors, Labels, Border, and Font properties asfollows:

Depth Specify a number greater than zero to make the chartthree-dimensional.

VisibleSelect this check box to show the chart area in the dataview.

Y Axis GridSelect this check box to show a grid on the Y axis.

X Axis GridSelect this check box to show a grid on the X axis.

Axis Bounding Box

Axis InversionSelect this check box to show the X axis on the verticalaxis and the Y axis on the horizontal axis.

Foreground ColorClick this field to set the color for the chart text.

Plot Area ColorClick this field to set the color for the plot area.

Background ColorClick this field to set the color for the background.

Y Labels RotationSelect an option to specify the degree of rotation of thelabels on the Y axis.

X Labels RotationSelect an option to specify the degree of rotation of thelabels on the X axis.

Border TypeDisplay the list of types and select the type of border forthe chart area.

Border WidthSpecify the width for the border of the chart area.

Font Select Change to set the type and size of font used in thechart area.

ii. Click OK to close the dialog box and reopen the data view.2) Change the settings for Y Title, Header, X Title, Footer, and Legend, by

doing the following:a) In the left column of the Default Settings: Preferences dialog box,

expand Chart View and select one of the following: Y Title, Header,X Title, Chart Area, Footer, or Legend.

b) Set the properties.c) Click OK to close the dialog box and reopen the data view.

f. Change the Text View by doing the following:1) Select Text View in the left column of the Default Settings: Preferences

dialog box.Additional information: This is equivalent to double-clicking the table thatis within the data view.


2) Change the General, Colors, and Grid properties as follows:

Title VisibleSelect this check box to show the title in the text view.

Statistics Area VisibleSelect this check box to show the statistics area within the texttable view.

In addition to selecting one or more of the check boxes for theoperations you want to perform (Average, Sum, Maximum, andMinimum), you can select the lines in the report that contain thevalues on which you want to perform the operations. Hold theCtrl key and click to select more than one line.

Title TextSpecify a title for the text view.

Foreground ColorClick this field to set the color for the text.

Background ColorClick this field to set the color for the text view background.

Show GridSelect this check box to show a grid in the text view.

Grid ColorClick this field to set the color for the grid.

3) Click OK to close the dialog box and reopen the data view.

Figure 104. Statistics area in text table view (Management Console)


Saving, exporting, and printing data and reports

ObjectiveTo translate data into forms that are useful for communicating the data to others.These forms include saving data as a graphic, using the data in a spreadsheet, orprinting reports of the data.

Background informationYou can perform the following operations to keep data in useful forms:v Save a data view as a GIF on a local disk.v Export all of the data as a Comma Separated Variables (CSV) file, and open the

file in a spreadsheet so you can continue to work on the data.v Print a report.


Before you beginOpen the data view window and customize the data view settings to represent thedata as you want it to look.




Management Console:

Saving a Data View as a GIF:

1. Click File and select Save As GIF to open the Save As Gif dialog box.2. Choose the path and specify a file name including the .gif file extension.3. Click Save As Gif.

Exporting Report Data:

1. Click File and select Export As CSV to open the Export As CSV dialog box.2. Choose the path and specify a file name including the .csv file extension.3. Click Export to create the CSV and reopen the Data View.

Printing a Report:

1. Click File and select Print to open the Print dialog box.2. Change the print options you want to modify.3. Click OK to send the data to the printer you selected and reopen the data view.

Viewing historical data

ObjectiveTo view historical data logged for a specified resource and for a specified resourcemodel.


Background informationThe display shows historical logged data for a specified resource and for aspecified resource model. With logged data, you can identify specific instances ofresource problems over the past 1, 6, 12, or 24 hours.

The characters =@ appended to the resource name indicate that only a singlebranch represents that part of the tree. The fully expanded tree view shows thefollowing details from the top down:

Resource modelName of the resource model.

ResourceName of a specific resource.

ContextName of the logical grouping of problems related to that specific resource.

InstancesNames of the instances of a particular indication.

Metric Name of the metric used to measure the indications.


Before you beginYou must enable logging for a resource model to create historical data and view itusing this procedure. See “Customizing data logging information” on page 93.


ProceduresYou can perform this procedure from the Web Health Console or the ManagementConsole.


Management Console:

1. Right-click the resource model you want from the Resource Models table inthe center pane.

2. Select Get Historical Data from the pop-up menu to display the data for theresource model you selected.

3. Double-click the resource model to show the corresponding resources.4. Double-click a resource to show the corresponding contexts.5. Double-click a context to show the corresponding instances.

Additional information: Each context identifies a logical group of problems thatare related to the selected resource.

6. Double-click an instance to show the corresponding metrics.Additional information: These metrics measure the selected indication.

7. View the following data:v A context, with all its instances and metricsv An instance, with all its metricsv A metric


8. Right-click the context, instance, or metric you want.9. Select Show History View of —> and the number of hours for which you

want to view data (1, 6, 12, or 24) to display a dialog box showing the datayou want.Additional information: For one context, data is displayed for a maximum of 50series. The data is presented with the time of the workstation where the healthconsole is running, regardless of the time-zone time of the endpoint wheredata was collected.

10. Click View and select Refresh to update the contents of the database browser.



Chapter 9. Setting up the Tivoli Enterprise Console for eventcorrelation

This section provides information about setting up the Tivoli Enterprise Console(TEC) for use with IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino. You can skip this section if you do not have the Tivoli Enterprise Consoleor do not want this product to send events to the Tivoli Enterprise Console. Youcan set up event correlation in one of the following ways:v In the Tivoli Enterprise Console. See Tivoli Enterprise Console User’s Guide, Version

3.7.1

—OR—v Locally, in the Tivoli management region for IBM Tivoli Monitoring for

Messaging and Collaboration: Lotus Domino

If the Tivoli Enterprise Console Server product is installed on the same machine asthe Domino server that is being managed by IBM Tivoli Monitoring for Messagingand Collaboration, you never need to start the local Tivoli Enterprise Console eventengine. The Tivoli Enterprise Console Server product rule engine performs allnecessary event processing on the Domino server. If you start the Tivoli EnterpriseConsole engine that comes with IBM Tivoli Monitoring for Messaging andCollaboration in these circumstances, the two engines might conflict and produceunpredictable results.


Table 15. Goals and where to find procedures for setting up the Tivoli Enterprise Console


Configure event correlation for thisproduct on Tivoli Enterprise Console.

“Configuring remote event correlation for thisproduct” on page 209

Configure local event correlation forthis product.

“Configuring local event correlation for thisproduct” on page 212

Customize the Events4 Profile forlocal event correlation.

“Customizing the Events4 Profile for local eventcorrelation” on page 214

Control the local events engine. “Controlling the local rule engine” on page 216

View Tivoli Enterprise Consoledisplays.

“Viewing events” on page 218

See a list of event classes and eventfor this product.

“Lists of event classes” on page 219

Overview of the Tivoli Enterprise ConsoleIn distributed computing environments, it is essential to address events andconditions that can lead to problems. The Tivoli Enterprise Console provides thetools for the following functions:v Receiving events from various sourcesv Processing events using rules


v Grouping events and delegating the groups selectively to administratorsv Responding to events automaticallyv Viewing events at a console

In the Tivoli Enterprise Console, rules (.rls) files contain the logic for correlation ofevents. BAROC (.baroc, Basic Recorder of Objects in C) files contain the definedevent classes.

The following list explains basic concepts of event management. For moreinformation about the Tivoli Enterprise Console, refer to the Tivoli EnterpriseConsole User’s 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 dowith 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.

You can also view events from this product’s Management Console.

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 specific


response can be to inform an administrator or to attempt automatic restartsof the server, or a combination of both.

The automatic response mechanism does not work with this product.However, you can write Tivoli Enterprise Console rules that accomplish thesame thing.

Configuring remote event correlation for this product

ObjectiveConfigure Tivoli Enterprise Console to handle events from Domino servers and setup an event group to display events.

Background informationWhen a Tivoli Enterprise Console is installed on a Domino server managed withIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino, the TivoliEnterprise Console’s rule engine performs all the necessary event processing. Younever need to start the standalone Tivoli Enterprise Console engine that comeswith the product. If you start the Tivoli Enterprise Console engine that comes withIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino in thesecircumstances, the two engines might conflict and produce unpredictable results.

Tivoli recommends using the Configure TEC for TMD task to perform thisprocedure because it requires less typing to complete. This task configures theTivoli Enterprise Console to handle Domino events and sets up an event group toview the events. The task performs the following work:v Creates the specified rule base, if it does not already exist.v Copies an existing rule base into a newly created rule base, if you select the

option to do so.v Configures the rule base for the selected options by importing the appropriate

class and rule set files.v Compiles the rule base.v Creates an event group, if you select the option to do so and the specified event

group does not already exist.v Configures the event group for the selected options by defining the appropriate

filters. For a detailed description of these class definitions, see “Lists of eventclasses” on page 219.

v Restarts the event server, if you select the option to do so.

Refer to the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoReference Guide for instructions on running this task.


Before you beginRun the wlookup command to confirm that the Tivoli Enterprise Console server isinstalled and registered as follows:wlookup -ar EventServer

This command returns a string that includes the object ID number of the TivoliEnterprise Console server, as in this example:EventServer 1671340084.1.695#Tec::Server#

Chapter 9. Setting up the Tivoli Enterprise Console for event correlation 209

If you have an interconnected Tivoli management region with an event serverinstalled in each Tivoli management region, this command reports each TivoliEnterprise Console server.



Command line:

1. Access the Tivoli bash shell to enable access to all required commands for thisprocedure.

2. Type the following series of commands to create variables that define the homedirectory of the Tivoli Enterprise console:

Variable name (value) Command to instantiate the variable

oserv oid oserv=’objcall 0.0.0 get_oserv’

directory (install_dir) tivoli_install_dir=’objcall $oserv query install_dir’

operating system (interp) interp=’objcall "$oserv" query interp’

path to Tivoli EnterpriseConsole binaries (bindir)

bindir="$install_dir/$interp"

EventServerOID, theObject Identifier of theTEC Event Server

EventServerOID=’wlookup -r EventServer EventServer’

Tivoli’s ID for thisinstallation of TivoliEnterprise Console(TECHomePath)

TECHomePath=’idlcall $EventServerOID _get_tec_home | \tr -d \ "’

Complete path to theTivoli Enterprise Consoleinstallation. (TECBase)

TECBase= "$bindir/$TECHomePath"

3. Create a new rule base using the wcrtrb command, as in the followingcommand:wcrtrb -S @EventServer:EventServer -d $BINDIR/TME/TEC/TMD TMD

where BINDIR/TME/TEC/TMD is the path to the directory of the TMD rulebase, and TMD is the name of the rule base you create.

4. Copy the contents of the Default rule base into the new rule base using thewcprb command for copying rule bases. In the following example, the wcprbcommand creates a rule base called TMD.wcprb -S @EventServer:EventServer Default TMD

where Default is the name of the rule base to copy, and TMD is the name ofthe new rule base.

Note: If the current rule base is not Default, use the name of the current rulebase in this copy command, not Default.

5. Run the following series of commands to import the classes that configure theTivoli Enterprise Console for IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino. In these commands the Tivoli software isinstalled in the tivoli_install_dir directory.


Purpose of command Command syntax

Place the *.baroc files fora resource model groupin the TMD rule base.

wimprbclass -S @EventServer:EventServer \$bindir/TMNT_TEC/Tmw2k.baroc TMD

wimprbclass -S @EventServer:EventServer \$tivoli_install_dir/generic_unix/ \TME/DominoManager/Tec_srv_cnfg/DominoEvent.baroc TMD

Issue the above command for each of the baroc files located inthe tivoli_install_dir/generic_unix/TME/DominoManager/Tec_srv_cnfg file, substituting the DominoEvent.baroc with eachbaroc file listed below:

DominoDatabaseManagement.barocDominoMailStatisticsMonitor.barocDominoReplicationStatus.barocDominoServerAvailability.barocDominoServerHealth.barocDominoSMTPMailStatisticsMonitor.barocDMXDPSCalendarEntry.barocDMXDPSDatabaseAccess.barocDMXDPSIntegrity.barocDMXDPSNABSearch.barocDMXDPSNetEcho.barocDMXDPSReplicateLocal.barocDMXDPSRoundTripMail.barocDMXDPSWebAccess.baroc

Place the *.rls rules filefor a resource modelgroup in the TMD rulebase.

If TBSM is installed, the Domino_send_to_TBSM.rls andDomino_Event.rls rulesets are needed. To install these rulesets,issue the following commands in order:

wimprbrules -S @EventServer:EventServer \tivoli_install_dir /generic_unix/ \TME/DominoManager/Tec_srv_cnfg/Domino_send_to_TBSM.rls TMD

wimprbrules -S @EventServer:EventServer \tivoli_install_dir /generic_unix/ \TME/DominoManager/Tec_srv_cnfg/Domino_Event.rls TMD

If TBSM is NOT installed, then the Domino_Event.rls andDomino_lookup_dps_info.rls rulesets are needed. To installthese rulesets, issue the following commands in order:

wimprbrules -S @EventServer:EventServer \tivoli_install_dir /generic_unix/ \TME/DominoManager/Tec_srv_cnfg/Domino_Event.rls TMD

wimprbrules -S @EventServer:EventServer \tivoli_install_dir /generic_unix/ \TME/DominoManager/Tec_srv_cnfg/Domino_lookup_dps_info.rls \TMD

Note: The order in which you run the rulesets is important, soissue these commands in the order documented above.

Compile the rules in theTMD rule base.

wcomprules -S @EventServer:EventServer TMD

6. Run the following commands to import event classes for IBM Tivoli Monitoringfor Messaging and Collaboration: Lotus Domino, where tivoli_install_dir is thedirectory where the Tivoli software is installed and TECBase is the directorywhere the rules files are located.a. wimprbclass -S @EventServer:EventServer \

$TECBase/default_rb/TEC_CLASSES/tecad_nt.baroc TMDb. wimprbclass -S @EventServer:EventServer $tivoli_install_dir/generic_unix/ \

TME/DominoManager/Tec_srv_cnfg/TMD3_srv_tecad.baroc TMD


c. wimprbrules -S @EventServer:EventServer $tivoli_install_dir/generic_unix/ \TME/DominoManager/Tec_srv_cnfg/TMD3_srv_tecad.rls TMD

d. wcomprules -S @EventServer:EventServer TMD

7. Run the following command to load the rule base:wloadrb -S @EventServer:EventServer TMD

8. Run the following command sets to active the new classes and rules:v When the event server is running,

wstopesvr -S @EventServer:EventServerwstartesvr -S @EventServer:EventServer

—OR—v When the event server is not running:

wstartesvr -S @EventServer:EventServer

Tivoli desktop: Run the Configure TEC for Messaging and Collaboration task.See “Running tasks” on page 172 for more information. You also can use wruntaskto run this task in the command line interface. See the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide for more information onthis task.

Configuring local event correlation for this product

ObjectiveTo configure the standalone event correlation engine that comes with this productto handle events from Domino servers and set up an event group to display eventslocally.

Background informationYou can set up local event correlation for one Domino server or for many Dominoservers. This procedure describes separate command line procedures to configureeach type of local event correlation:v Multiple servers: You configure event correlation on a managed node that can

correlate events from multiple Domino servers.

Note: You must set up this type of event correlation before you configureDomino servers for IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino.

—OR—v Single server: You configure event correlation on a specific Domino server. You

perform this procedure after you configure the server for this product.

IBM Tivoli Monitoring for Messaging and Collaboration can captureDomino-generated events, which Lotus Domino lists in the events4.nsf file, andforward them to the local event correlation engine. Using the rule-buildingguidelines for the Tivoli Enterprise Console, you can create rules for the localcorrelation engine to process the events. The local correlation engine implementsthe following rules by default:1. It forwards the events received to the Tivoli Enterprise Console.2. It does not forward duplicate events to the Tivoli Enterprise Console until the

original event is closed at the Tivoli Enterprise Console.

The rule file is called tmd_sa.rls, and the baroc file is called tecad_tmd.baroc.


When a Tivoli Enterprise Console is installed on a Domino server managed withIBM Tivoli Monitoring for Messaging and Collaboration, the Tivoli EnterpriseConsole’s rule engine performs all the necessary event processing. You never needto start the standalone Tivoli Enterprise Console engine that comes with IBM TivoliMonitoring for Messaging and Collaboration. If you start the Tivoli EnterpriseConsole engine that comes with IBM Tivoli Monitoring for Messaging andCollaboration in these circumstances, the two engines might conflict and produceunpredictable results.


Before you beginRun the wlookup command to confirm that the Tivoli Enterprise Console server isinstalled and registered as follows:wlookup -ar EventServer

This command returns a string that includes the object ID number of the TivoliEnterprise Console server, as in this example:EventServer 1671340084.1.695#Tec::Server#

If you have an interconnected Tivoli management region with an event serverinstalled in each Tivoli management region, this command reports each TivoliEnterprise Console server.


ProcedureYou can perform this procedure from the command line to set up event correlationfor multiple or single Domino servers.

Command line procedure for multiple servers:

Note: The event correlation rules you set in this procedure apply to all Dominoserver that you configure subsequently.

1. Type the following declaration to create a variable that defines the directorylocation of the event correlation files on the managed node:$install_dir =’objcall oserv_OID query install_dir’;

2. Use the variable you define in Step 1 to access the .rls (rules) files and the.baroc files in the following directories on a managed node:v Access the tmd_sa.rls rules file:

$install_dir/lcf_bundle/bin/w32-ix86/TME/DominoManager/TEC/rule_base \/TEC_RULES/tmd_sa.rls

v Access the tecad_tmd.baroc BAROC file:$install_dir/lcf_bundle/bin/w32-ix86/TME/DominoManager/TEC/rule_base \/TEC_CLASSES/tecad_tmd.baroc

3. Edit the .rls (rules) files and the .baroc files to match your requirements forevent correlation.

4. Set your environments and compile the rules according to the Tivoli EnterpriseConsole guidelines.

Command line procedure for a single server:


Note: The event correlation rules you set in this procedure apply only to oneDomino server that you have configured for IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino.

1. Edit the following files to change the rules and classes:Access the tmd_sa.rls rules file:$LCF_BINDIR/mrt/TMDTEC/rule_base/TEC_RULES/tmd_sa.rls

Access the tecad_tmd.baroc BAROC file:$LCF_BINDIR/mrt/TMDTEC/rule_base/TEC_CLASSES/tecad_tmd.baroc

2. Run the env_lcf.sh script to set the environment variables for the Tivoli lightclient framework (LCF) software on the endpoint.

3. Navigate to the following directory:$LCF_BINDIR/mrt/TMDTEC

4. Set the following environment variables.For Solaris:

SHLIB_PATH=./lib:$SHLIB_PATHLIBPATH=./lib:$LIBPATHLD_LIBRARY_PATH=./lib:$LD_LIBRARY_PATH%TEC_BIN_DIR=.TEC_KB_DIR=$TEC_BIN_DIR/rule_baseBIM_PROLOG_DIR=$TEC_BIN_DIRINTERP=solaris2

For AIX:SHLIB_PATH=./lib:$SHLIB_PATHLIBPATH=./lib:$LIBPATHLD_LIBRARY_PATH=./lib:$LD_LIBRARY_PATH%TEC_BIN_DIR=.TEC_KB_DIR=$TEC_BIN_DIR/rule_baseBIM_PROLOG_DIR=$TEC_BIN_DIRINTERP=aix4-r1

For Windows NT:PATH=.;.\lib;.\bin;%PATH%TEC_BIN_DIR=.TEC_KB_DIR=%TEC_BIN_DIR%\rule_baseBIM_PROLOG_DIR=%TEC_BIN_DIR%INTERP=w32-ix86SHELL=bin/bash.exe

5. Run the following command to compile the rules:tec_compile_rules [-notrace] rule_base

Customizing the Events4 Profile for local event correlation

ObjectiveTo configure the events profile of a Domino server so that it sends the appropriateevents to the local rule correlation engine.

Background informationServer Event Configuration profiles (Events4 profiles) are included with everyDomino server object that you create in this product. These profiles define whatevent types and event levels are sent to the local rule correlation engine forprocessing. See “Controlling the local rule engine” on page 216 for moreinformation on using the local rule correlation engine.


Note: In addition to customizing the Events4 profiles that come with IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino, you can createa new Events4 profile.

You can customize an Events4 profile to optimize local rules correlation. Yoursettings can cause the Domino server to send less event information to the localcorrelation engine for processing, thereby decreasing network traffic and improvingresponse time. You can set event levels that are significant for your system at thelevel of an individual Domino server. Also, you can disable reporting of specificevents that the local correlation engine does not need to process. For example, ifappropriate, you can customize the Events4 profile to eliminate the Normal andWarning Low events from the group of events that pass to the local correlationengine.

You can customize the Events4 profile in any of the following ways:v Delete an event type from the profile. IBM Tivoli Monitoring for Messaging and

Collaboration: Lotus Domino produces no event information for the deletedevent type.

v Add an event type to the profile.v Modify one or more of the following event levels from an individual event type:

Normal, Warning Low, Warning High, Failure, and Fatal.

Note: The distribution process for an Events4 profile is the same as thedistribution process for any other profile. However, the target Dominoserver must be running during the distribution of an Events4 profile.


Before you beginConfigure the Tivoli Enterprise Console to work with IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino.

The following procedures describe the configuration options:v “Configuring remote event correlation for this product” on page 209v “Configuring local event correlation for this product” on page 212

When you finishDistribute the customized Events4 profile, as described in “Distributing a profilefrom the desktop” on page 101.

Note: The distribution process for an Events4 profile is the same as thedistribution process for a profile. However, the target Domino server mustbe running during the distribution of an Events4 profile.


Management Console:

1. Click the Configuration tab.2. Click the Profiles tab in the Configuration pane.3. Select the server type that you want to modify in the server tree view on the

left side of the Management Console.


Note: The server type is an object that contains resource model profiles andEvents4 profiles that you distribute to Domino servers.

4. Click the event configuration profile in the Profiles list in the middle of theManagement Console.Additional Information: The Event Type table below the Profiles list refreshes todisplay event types and event levels.

5. Select or clear the check box items to customize local event correlation asfollows:a. Decide which Event Type row to modify.b. Select or clear the check box of an event level in the row to add or remove

the event level from the process of local event correlation.Additional Information: For example, you can clear the Normal check box forthe Addin event type in the Events4 profile for the Domino 5.0 BasicServer server type, which is called Domino 5.0 Basic Server EventConfiguration.

Note: These changes do not take effect until you distribute the profilewhose settings you have modified, as mentioned in step 8.

6. (Optional) Add an event to the Event Type table in the bottom of theManagement Console, as follows:a. Click Add Event to access the Add Event dialog box.b. Select the event type or event types that you want to add in the table.c. Click Add.

7. (Optional) Delete an event from the Event Type table in the bottom of theManagement Console, as follows:a. Select an event in the Event Type table.b. Click Delete Event.c. Click OK in the confirmation dialog box.

8. Distribute the customized Events4 profile, as described in “Distributing aprofile from the desktop” on page 101.

Note: The distribution process for an Events4 profile is the same as thedistribution process for a resource model profile. However, the targetDomino server must be running during the distribution of an Events4profile.

Controlling the local rule engine

ObjectiveTo start or stop the local rule engine, which sends event information from theDomino server to the Tivoli Enterprise Console.

Background informationThe local rule engine for IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino is a standalone version of the Tivoli Enterprise Console engine. Thelocal engine analyzes all event information on a Domino server and sendssignificant event information to the Tivoli Enterprise Console. Because event datais filtered locally, the Domino server sends less event information to the TivoliEnterprise Console for processing, thereby decreasing network traffic andimproving response time.


OS/400 has no Tivoli Enterprise Console standalone rules engine. It sends all IBMTivoli Monitoring for Messaging and Collaboration events directly to the TivoliEnterprise Console server. As on other operating systems, you can use the StartTEC Engine and Stop TEC Engine functions to control the sending of events tothe Tivoli Enterprise Console server.


Before you beginSee Chapter 9, “Setting up the Tivoli Enterprise Console for event correlation” onpage 207 for general information about using the Tivoli Enterprise Console withthis product.

When you finishWhile the local engine is running, view events in the Tivoli Enterprise Console, asdescribed in “Viewing events” on page 218.


Command line: Use the following commands to control the local rule engine:v wtmdstartengine command to start the local rule engine.v wtmdstopengine command to stop the local rule engine.v wruntask command with the following tasks to control the local rule engine:

– Start Engine task to start the local rule engine.– Stop Engine task to stop the local rule engine.


Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Start Engine task to start the local rule engine.v Stop Engine task to stop the local rule engine.

See IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for a description of the the desktop options for these tasks.

—OR—

Complete the following steps to run this task from the desktop:1. Double-click the icon of the policy region that contains the server for which

you want to start the local rule engine to display the Policy Region window.2. Right-click the server icon in the Policy Region window.3. Select one of the following pop-up menu items:

v Select Start Engine to start the engine.v Select Stop Engine to stop the engine.

4. Click OK.5. Click Yes in the confirmation dialog box.

Additional Information: When execution is completed, the Information dialogbox displays the results of the operation.



Management Console:

1. Click the Status and Operations tab of the Management Console.2. Select the server for which you want to start the local rule engine in the tree

view on the left side of the console.3. Click the Start/Stop Event Engine tool in the Tools → Operations collapsible

menu to display the Start/Stop Engine dialog box.4. (Optional) Use one of the following methods to select multiple servers on which

to perform this operation:v Type multiple server names separated by semicolons (;) in the Servers area.

—OR—v Use the graphical user interface as follows:


b. Use standard selection methods to select multiple servers.Additional Information: For example on a Windows keyboard, press Ctrl-Ato select all servers, or press Ctrl and click multiple servers, one by one.

c. Click OK to return to the Start/Stop Event Engine dialog box.Additional Information: The text box in this dialog box reflects theselections you made in the Select Servers dialog box.

5. Select one of the following options:v Select Start to start the local engine.v Select Stop to stop the local engine.

6. Click OK.

Viewing events

ObjectiveTo view events in the Tivoli Enterprise Console so you can watch for incomingevents and respond to them.

The time it takes to view events in the Tivoli Enterprise Console depends on thenumber of events.

Background informationThe Tivoli Enterprise Console can filter out normal events, respond automaticallyto anticipated problems, and forward only those events that require humanintervention.


Before you beginThe Tivoli Enterprise Console must be configured to receive events from IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino. (The TivoliEnterprise Console is represented on the Tivoli desktop by an Event Server icon.)

When you finishYou can respond to events yourself, or configure the Tivoli Enterprise Console toautomatically respond to certain events. See the Tivoli Enterprise Console User’sGuide for information.



Desktop: Follow these steps to view events:1. Double-click the EventServer icon on the Tivoli desktop. The Event Server

Rule Bases window is displayed. This window contains an icon for each rulebase that you are authorized to view.

2. Double-click the rule base icon. The list of events for that event group isdisplayed in the window.

3. To view the details of an event, do one of the following:v Double-click on the desired event.

—OR—v Select the desired event and click View Message. The Event Group Message

Viewer dialog box is displayed. Information for each slot (information field)in the event is displayed in this dialog box.

Management Console: Tivoli Enterprise Console events automatically appear inthe Management Console Events tab if the following conditions are met:v Configure Tivoli Enterprise Console to give access to all users who need access

to event data, as described in the Tivoli Enterprise Console User’s Guide.v Tivoli Enterprise Console 3.7 or later is installed.v The TecUIServer object was installed during the Tivoli Enterprise Console 3.7

installation.v The Tivoli Enterprise Console RIM object is installed and running (refer to the

Tivoli Management Framework documentation). Use the following command totest your connection to the Tivoli Enterprise Console RIM object:wrimtest -l tec

Lists of event classesThis section lists the event classes provided with IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino.

The following files define the event classes for IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino:v Tmw2k.baroc

Defines the IBM Tivoli Monitoring 5.1.1 events.v DominoEvent.baroc

Defines Domino_Event as a subclass of TMW_Event.v TMD3_srv_tecad.baroc

Defines TMD_Base as a subclass of Event.

The following Baroc files define the classes for the resource models:v DominoDatabaseManagement.baroc

v DominoMailStatisticsMonitor.baroc

v DominoReplicationStatus.baroc

v DominoServerAvailability.baroc

v DominoServerHealth.baroc

v DominoSMTPMailStatisticsMonitor.baroc


v DMXDPSCalendarEntry.baroc

v DMXDPSDatabaseAccess.baroc

v DMXDPSIntegrity.baroc

v DMXDPSNABSearch.baroc

v DMXDPSNetEcho.baroc

v DMXDPSReplicateLocal.baroc

v DMXDPSRoundTripMail.baroc

v DMXDPSWebAccess.baroc

Collectively, these files implement the following class hierarchy:Event

TMD_EVENTTEC_SyncTMD_Base

<event_classes>TMW_Event

Domino_Event<resource model classes>

All event_classes extend from TMD_Base. See the class definition files for IBMTivoli Monitoring for the definition of TMW_Event. See the class definition filesfor Tivoli Enterprise Console for the definition of EVENT.

The following lists contain the event classes and resource model classes that IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino uses:

Event classes

v TMD_Accessv TMD_Access_Controlv TMD_AdminPv TMD_Agentv TMD_AMgrv TMD_APPC_Subsystemv TMD_AppleTalkv TMD_Archivev TMD_Argument_Errorv TMD_Attach_Managerv TMD_Authenticationv TMD_Authorization TMD_B-treev TMD_Billing TMD_Binderyv TMD_BTVerifyNode_Errorv TMD_Calendarv TMD_Catalog TMD_Certificationv TMD_Change_Requestv TMD_Cluster TMD_Collectionv TMD_Commandv TMD_Compactionv TMD_Connectionv TMD_Controlv TMD_Conversation


v TMD_Conversion_Errorv TMD_Databasev TMD_Database_Driverv TMD_Database_Objectv TMD_Data_Access_Applicationv TMD_Datev TMD_DIIOPv TMD_Directoryv TMD_Directory_Assistancev TMD_Directory_Catalogv TMD_Directory_Managerv TMD_Disk_Errorv TMD_DNS_Errorv TMD_Documentv TMD_Domain_Indexerv TMD_Domino_Directoryv TMD_Duplicate TMD_Encryptionv TMD_Event_Errorv TMD_Extension_Managerv TMD_File_Errorv TMD_File_Systemv TMD_Folderv TMD_Formula_Scriptv TMD_Helpv TMD_ICM_Serverv TMD_IMAPv TMD_IMAP4v TMD_Indexv TMD_Internal_Errorv TMD_Internetv TMD_Invalidv TMD_JVMv TMD_LDAPv TMD_Mailv TMD_Mail_Convertv TMD_Maps_Extractorv TMD_Memoryv TMD_Miscv TMD_Misc_Errorv TMD_Modem_Errorv TMD_MT_Collectorv TMD_Namev TMD_NDSv TMD_NetBIOSv TMD_NetWare


v TMD_Networkv TMD_News_Serverv TMD_Notev TMD_Notesv TMD_Novellv TMD_NTIv TMD_Objectv TMD_Object_Storev TMD_Operationv TMD_OS2v TMD_POP3v TMD_Port_Commv TMD_Processv TMD_Providing_Servicev TMD_Proxyv TMD_Public_Keyv TMD_Queryv TMD_Recovery_Managerv TMD_Remote_Program_Error.txtv TMD_Remote_Server.txtv TMD_Remote_Server_Errorv TMD_Remote_Service_Errorv TMD_Replicav TMD_Reporterv TMD_Requestv TMD_Resourcev TMD_Routerv TMD_SchedMgrv TMD_SECDYv TMD_Securityv TMD_Security_IDv TMD_Security_Package_Protocol_Errorv TMD_Serverv TMD_Server_IDv TMD_Server_Namev TMD_Signaturev TMD_SMTP TMD_SSLv TMD_Statisticsv TMD_Tablev TMD_TCPIP TMD_Templatev TMD_TP TMD_Transferingv TMD_UBM_IOv TMD_View TMD_Vinesv TMD_VPE TMD_Webv TMD_XPCMQ


Resource model classes

v DPSCalendarEntry_DPSPerformanceDecliningv DPSCalendarEntry_DPSProbeErrorv DPSDatabaseAccess_v DPSPerformanceDecliningv DPSDatabaseAccess_DPSProbeErrorv DMXDPSStationDownv DPSNABSearch_DPSProbeErrorv DPSNABSearch_DPSPerformanceDecliningv DPSNetEcho_DPSProbeErrorv DPSNetEcho_DPSPerformanceDecliningv DPSReplicateLocal_DPSPerformanceDecliningv DPSReplicateLocal_DPSProbeErrorv DPSRoundTripMail_DPSProbeErrorv DPSRoundTripMail_DPSPerformanceDecliningv DPSWebAccess_DPSPerformanceDecliningv DPSWebAccess_DPSProbeError Corruption_In_Logv DBCorruption_TivoliAddin_Availabilityv Domino_Database_Corruptionv DominoMailDeadv DominoMailWaiting Mail_TivoliAddin_Availabilityv Replication_TivoliAddin_Availabilityv Domino_Replication_Manualv Domino_Replication_Durationv Domino_Replication_Missv DominoSMTPMTADeadv SMTPMTA_TivoliAddin_Availabilityv DominoSMTPMTAWaitingv Domino_Server_Panic Domino_ServerAvailabilityv AvailabilityIndexv ServerHealth_TivoliAddin_Availabilityv ClusterAvailabilityIndexv Domino_Taskv DroppedSession



Chapter 10. Integrating with Tivoli Business Systems Manager

This chapter provides information on using Tivoli Business Systems Manager tomanage IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Dominoresources and events.

Table 16 contains the procedures for integrating IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino into Tivoli Business Systems Manager.

Table 16. Goals and where to find procedures for integrating with Tivoli Business SystemsManager


1. Install the IBM Tivoli Monitoring forMessaging and Collaboration: LotusDomino integration on the TivoliBusiness Systems Manager server

“Integrating with Tivoli Business SystemsManager” on page 226

2. Configure your Tivoli EnterpriseConsole event server to forward eventsto Tivoli Business Systems Manager

“Configuring the Tivoli Enterprise Consoleevent server” on page 228

3. Define the specific IBM TivoliMonitoring for Messaging andCollaboration: Lotus Domino objects toTivoli Business Systems Manager usinga discovery task.

“Discovering resources for Tivoli BusinessSystems Manager” on page 227

4. Perform IBM Tivoli Monitoring forMessaging and Collaboration

“Working with Tivoli Business SystemsManager” on page 229

5. To remove the IBM Tivoli Monitoringfor Messaging and Collaboration:Lotus Domino integration from TivoliBusiness Systems Manager.

“Uninstalling IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Dominointegration from Tivoli Business SystemsManager” on page 229

This chapter also provides information about uninstalling the IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino integration from TivoliBusiness Systems Manager.

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 management serverThe Tivoli Business Systems Manager management server processes all theavailability data that is collected from various sources. Availability data isinserted in the Tivoli Business Systems Manager database, where intelligentagents provide alerts on monitored objects and then broadcast those alertsto Tivoli 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 workstationThe Tivoli Business Systems Manager workstation displays objects incustomized views, called Line of Business Views. Objects are presented in ahierarchical Tree View so that users can see the relationship betweenobjects. Alerts are overlaid on the objects when the availability of the objectis threatened.

Tivoli Event EnablementTivoli Event Enablement is installed on the Tivoli Enterprise Console eventserver and enables the event server to forward events to Tivoli BusinessSystems Manager. Tivoli Event Enablement defines event classes and rulesfor handling events related to Tivoli Business Systems Manager.

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 Systems Manager.

PrerequisitesBefore you integrate IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino into Tivoli Business Systems Manager, perform the followingprerequisite 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 with patch 35 and 91394bsm.

v Install and configure the Tivoli Event Enablement (with patch 38) on all TivoliEnterprise Console event servers that receive events that you want to forward toTivoli Business Systems Manager. See the Tivoli Business Systems ManagerInstallation and Configuration Guide for more information.

v Configure Tivoli Business Systems Manager to communicate with each TivoliEvent Enablement installed in the previous step. See the Tivoli Business SystemsManager Installation and Configuration Guide for more information.

Integrating with Tivoli Business Systems Manager

ObjectiveTo integrate IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino with Tivoli Business Systems Manager so you can receive IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino events on the TivoliBusiness Systems Manager

Background informationTo enable Tivoli Business Systems Manager to manage IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino events, you must install an IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino integrationprogram on the Tivoli Business Systems Manager server. This integration programdoes the following steps:v Defines the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus

Domino objects in Tivoli Business Systems Managerv Defines a line of business for IBM Tivoli Monitoring for Messaging and

Collaboration: Lotus Domino resources


Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.

Before you beginMake sure that your Tivoli Business Systems Manager environment is configuredcorrectly and that you have Tivoli Event Enablement installed on each TivoliEnterprise Console event server that you want to forward events. For moreinformation, see the Tivoli Business Systems Manager Installation and ConfigurationGuide.

When you finishConfigure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager. See “Configuring the Tivoli Enterprise Console eventserver” on page 228 for more information.

ProcedureUse the following steps to install the IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino integration:1. On the Tivoli Business Systems Manager server, insert the IBM Tivoli

Monitoring for Messaging and Collaboration: Lotus Domino CD and, from acommand prompt, navigate to the \TBSM directory.

2. Type install to start the installation wizard.3. Click Next on the welcome screen.4. Specify an installation location for the Tivoli Business Systems Manager

integration. The default location is C:\tivoli\itmABA. Click Browse to select adifferent installation location.Click Next to continue.The installation location and total installed size are displayed.

5. Click Next to continue.6. Provide the following Microsoft SQL Server information and click Next to start

the installation.

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.

A progress bar is displayed to show the progress of the installation. Wheninstallation is complete, a message appears.

7. Click Finish to exit the installation wizard.

Discovering resources for Tivoli Business Systems Manager

ObjectiveTo define the specific IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino objects to Tivoli Business Systems Manager.

Chapter 10. Integrating with Tivoli Business Systems Manager 227

Background informationThe IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Dominointegration that you installed in “Integrating with Tivoli Business SystemsManager” on page 226 defined the types of objects that you want Tivoli BusinessSystems Manager to manage. After you define the object types, you need to definethe specific objects. You can do this with the Domino TBSM Discovery task. Thistask searches a managed node for objects and sends a DISCOVER event to TivoliBusiness Systems Manager for each object. The Domino TBSM Discovery task alsomaintains a list of the objects that have been discovered and alerts Tivoli BusinessSystems Manager when they have been deleted by sending Tivoli Business SystemsManager a GONE event for each object that no longer exists on the managed node.


Before you beginConfigure your Tivoli Enterprise Console event server, as described in“Configuring the Tivoli Enterprise Console event server” on page 228.

When you finishUse Tivoli Business Systems Manager to view and manage your IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino objects. Forinformation on using Tivoli Business Systems Manager, see the Tivoli BusinessSystems Manager User’s Guide.

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

Command lineUse the wruntask command with the Domino TBSM Discovery task.


DesktopUse the following steps to run this procedure as a task:1. In the Domino Server Tasks task library, double-click the Domino TBSM

Discovery task.2. Select the managed node on which you want to search for objects and click

Execute.

If the task completes successfully, you can access a log file that contains the eventssent to Tivoli Business Systems Manager.

Configuring the Tivoli Enterprise Console event server

ObjectiveTo configure the Tivoli Enterprise Console event server to forward events to TivoliBusiness Systems Manager.


Background informationBefore Tivoli Enterprise Console event servers can forward events to TivoliBusiness Systems Manager, you must configure them to use a rule base to forwardthe 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 Messaging and Collaboration: LotusDomino objects to Tivoli Business Systems Manager with the Domino TBSMDiscovery task, as described in “Discovering resources for Tivoli Business SystemsManager” on page 227.

ProcedureUse the Configure TEC for Messaging and Collaboration task to configure (orreconfigure) each event server. If you installed Tivoli Business Systems Managerevent enablement on the event server, this task recognizes that and compiles therule base that forwards events to Tivoli Business Systems Manager. For informationon running this task, see IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino Reference Guide

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 Messaging and Collaboration: Lotus Domino Reference Guide.

Uninstalling IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino integration from Tivoli Business Systems Manager

ObjectiveTo remove the IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino integration from Tivoli Business Systems Manager.

Background informationUninstalling the IBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino integration removes the IBM Lotus Domino Server object definitions andobjects from Tivoli Business Systems Manager.

Required authorization roleYou must have administrator authority on the Tivoli Business Systems Managerserver.

Chapter 10. Integrating with Tivoli Business Systems Manager 229



ProcedureUse the following steps to perform this procedure:1. On the Tivoli Business Systems Manager server, from a command prompt,

navigate to the directory where you installed the IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino integration. The default directoryis c:\tivoli\itmABA.

2. Type uninstall to start the uninstall wizard.3. Click Next on the welcome screen.4. The installation location for the Tivoli Business Systems Manager integration is

displayed. Click Next to continue.5. Provide the following Microsoft SQL Server information:

SQL ServerThe name of the SQL server with which this Tivoli Business SystemsManager is associated.

SQL UseridThe SQL user ID.

SQL PasswordThe password for the user ID defined above.

6. Click Finish to exit the installation wizard.


Chapter 11. Enabling Tivoli Enterprise Data Warehouse

This chapter provides information on enabling IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino for Tivoli Enterprise Data Warehouse.

Overview of Tivoli Enterprise Data WarehouseTivoli 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.


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 Messaging and Collaboration:Lotus Domino creates data marts whose structure is suitable for the reportinterface. They do this by providing an ETL process, called a data mart ETL, thatcreates the data mart and loads it with data from the central data warehouse. Formore information on how the IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino warehouse pack is structured, see the IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino Warehouse Enablement PackImplementation Guide found in the Docs directory of this product’s Installation CD.

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 the Enablingan Application for Tivoli Enterprise Data Warehouse Guide.


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 reportsprovided 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. The following sections describehow to do the following tasks:v Working with usersv Working with roles and groupsv Working with data martsv Working with reports

Working with users and user groupsThis section describes tasks associated with managing user groups for TivoliEnterprise Data Warehouse. It includes the following topics:v An overview of users and user groupsv Creating an IBM Console userv An overview of the Tivoli Enterprise Data Warehouse rolesv Assigning roles to a userv Creating a user groupv Assigning users to a user group

About users and user groupsYou 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.

The Tivoli Enterprise Data Warehouse authorization rolesThe following Tivoli Enterprise Data Warehouse authorization roles control accessto tasks and activities 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.

Chapter 11. Enabling Tivoli Enterprise Data Warehouse 233

v Report roles control a user’s ability to create and modify reports for the datamarts the user’s user groups can access. Assign only one of the following rolesto each user:– Advanced Report Author

With this role, a user can create, modify, run, and delete public and their ownpersonal reports, and save the output of reports, both public and personal.

– Report AuthorWith this role, a user can run and save the output of public reports and createand modify their own personal reports. They can run public and personalreports, and create, modify, and delete personal reports.

– Report ReaderWith this role, a user can run public reports and view the saved output ofpublic reports.

Table 17. Goals and where to find procedures for enabling IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino for Tivoli Enterprise Data Warehouse


Work with users and user groups “Accessing the IBM Console” on page 234

“Creating an IBM Console user” on page235

“Assigning authorization roles to a user”on page 235

“Creating a user group” on page 236

“Assigning users to a user group” on page236

“Assigning user groups to a data mart” onpage 237

Manage Tivoli Enterprise Data Warehousereports

“Running reports” on page 238

“Scheduling reports to run automatically”on page 239

“Modifying default settings for reports” onpage 239

“Creating reports” on page 240

“Creating a Many Measurements VersusTime Domino-specific report” on page 241

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:1. From the IBM Console, 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 authorization roles to a user

ObjectiveTo assign authorization roles to a user.




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:1. From the IBM Console, 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 also guides you throughadditional tasks for managing user groups, such as updating or displaying theproperties of a user group, adding users to a user group, and deleting a usergroup.

ProcedureTo create a user group, complete the following steps:1. From the IBM console, 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.





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:1. From the IBM Console, 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:1. From the IBM Console, 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.4. Open the Task Assistant and follow the instructions provided in the online help

to assign a user group to a data mart.


Managing 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 forMessaging and Collaboration: Lotus Domino, along with the data marts requiredto collect the data used in the report.

This section describes the following tasks:v Running a report manuallyv Automatically running reportsv Modifying default settings for report creationv Creating a 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,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 Enabling anApplication for Tivoli Enterprise Data Warehouse.

For information on the specific data mart, star schema, and report mapping of thisproduct, see the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus DominoWarehouse Enablement Pack Implementation Guide located in the Docs directory ofthis product’s Installation CD.

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:1. From the IBM Console, 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:1. From the IBM Console, 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 Run.4. Specify the time frame for which you would like to run the report. Specify a

General Time Frame such as the last 7 days, or a Specific Time Interval such asJanuary 1, 2002 through January 31, 2002.

5. Click Next.6. Make any necessary changes for Report Output Name and Report Output

Description.7. Click Run.

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 Weekdays


specified 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 18. 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, seeEnabling an Application for Tivoli Enterprise Data Warehouse.

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

Additional information: After doing this, when a user selects a Weekdays filter for areport in the report interface, 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 also guides you throughadditional tasks for reports, such as modifying or displaying the properties of areport and deleting a report.

ProcedureYou can perform this procedure from the IBM Console.1. Click Work with Reports and select Create a Report.2. Select one of the following type of reports to create: Extreme Case, Health

Check, and Summary.3. Select the data mart that contains the information from which to create the

report.4. Click OK.5. Click the General tab and enter the Name and Description for the report.6. Click the Metrics tab, and select Add to add a new metric to graph and

display the Add Metrics screen.7. Select the star schema containing the metric that you would like to graph and

to display a list of Available Metrics for the star schema.8. Check one or more of the metrics that you would like to graph.9. Click Next.

10. Select the aggregation type that you would like for each metric.11. Click Next.12. Specify the attributes to filter by, group by, or order by.

Additional information: For example, if you only want to display informationabout a specific Domino server, specify the name of the Domino server in theDomino Server Component Name Filter By field.

13. Click the Time tab, and specify the Time frame for which you would like torun the report.Additional information: You can either specify a General Time Frame, such asthe Last 7 days, or a Specific Time Interval, such as January 1, 2002 throughJanuary 31, 2002.

14. Click the Schedule tab, and select whether the report should be run when thedata mart is built.

15. Click OK.

Creating a Many Measurements Versus Time Domino-specific report

ObjectiveTo create the Many Measurements Versus Time report.

Background informationIBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino includesreports that summarize data based on components such as Domino Servers.

Since each Domino server is specific to an environment, IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino does not include these reports. Usethis procedure to create reports of the Many Measurements Versus Time class.


Figure 105 contains a bar chart that shows the average MAIL.Dead value for theabatst.Server6 and domtst.Server6 servers. The MAIL.dead value is an aggregatevalue for the past 21 days. This is an example of a One Measurement VersusMany Components class of reports. Tivoli Enterprise Data Warehouse also allowsyou to graph Many Measurements Versus Time.

Figure 106 on page 243 shows the average MAIL.Dead value for abatst.Server6server.

Figure 105. Bar chart


Required authorization roleAdvRepAuthRole or RepAuthRole


When you finishNone

ProcedureYou can perform this procedure from the IBM Console. The steps are the same asthose for Creating Reports, but includes specific values for this type of report.

To create reports of the Many Measurements Versus Time class, perform thefollowing procedure:1. Click Work with Reports and select Create a Report.2. Select Health Check for the Type of report to create.3. Select the ABA Messaging and Collaboration Data Mart.4. Click OK.5. Click the General tab, and enter the Name and Description for the report.6. Click the Metrics tab, and select Add to add a new metric to graph and to

display the Add Metrics screen.7. Select the star schema containing the metric that you would like to graph and

to display a list of Available Metrics for the star schema.8. Check one or more metrics you would like to graph.9. Click Next.

Figure 106. Line chart


10. Select the Aggregation type you would like for each metric.11. Click Next

12. Select the Domino server to graph in the Filter By field for theDOMSERVER_COMP_NAME.Additional information: If you do not select one and choose ″*″, the values forall Domino servers will be averaged together for each metric.

13. Click the Time tab and specify the Time frame for which you would like torun the report.Additional information: You can either specify a General Time Frame, such asthe Last 7 days, or a Specific Time Interval, such as January 1, 2002 throughJanuary 31, 2002.

14. Click the Schedule tab and select whether the report should be run when thedata mart is built.

15. Click OK.

IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Dominodata marts and reports

This product provides the ABA Messaging and Collaboration Data Mart. This datamart uses the following star schemas:v Daily Domino Addin Task Star Schemav Daily Domino Agent Star Schemav Daily Domino Calendar Star Schemav Daily Domino Communications Star Schemav Daily Domino Database Pool Star Schemav Daily Domino Database Star Schemav Daily Domino Disk Star Schemav Daily Domino ICM Star Schemav Daily Domino IMAP Star Schemav Daily Domino Internet Port Star Schemav Daily Domino LDAP Star Schemav Daily Domino Mail Star Schemav Daily Domino Mail Transfer Agent Star Schemav Daily Domino NETBIOS Star Schemav Daily Domino Netware Disk Star Schemav Daily Domino News Protocol Star Schemav Daily Domino Performance Station Star Schemav Daily Domino POP3 Star Schemav Daily Domino Remote Server Star Schemav Daily Domino Replica Star Schemav Daily Domino Server Star Schemav Daily Domino SMTP Star Schemav Daily Domino SMTPMTA Star Schemav Daily Domino SPIN Star Schemav Daily Domino Web Retriever Star Schemav Daily Domino XPC Star Schema


v Hourly Domino Addin Task Star Schemav Hourly Domino Agent Star Schemav Hourly Domino Calendar Star Schemav Hourly Domino Communications Star Schemav Hourly Domino Database Pool Star Schemav Hourly Domino Database Star Schemav Hourly Domino Disk Star Schemav Hourly Domino ICM Star Schemav Hourly Domino IMAP Star Schemav Hourly Domino Internet Port Star Schemav Hourly Domino LDAP Star Schemav Hourly Domino Mail Star Schemav Hourly Domino Mail Transfer Agent Star Schemav Hourly Domino NETBIOS Star Schemav Hourly Domino Netware Disk Star Schemav Hourly Domino News Protocol Star Schemav Hourly Domino Performance Station Star Schemav Hourly Domino POP3 Star Schemav Hourly Domino Remote Server Star Schemav Hourly Domino Replica Star Schemav Hourly Domino Server Star Schemav Hourly Domino SMTP Star Schemav Hourly Domino SMTPMTA Star Schemav Hourly Domino SPIN Star Schemav Hourly Domino Web Retriever Star Schemav Hourly Domino XPC Star Schemav Monthly Domino Addin Task Star Schemav Monthly Domino Agent Star Schemav Monthly Domino Calendar Star Schemav Monthly Domino Communications Star Schemav Monthly Domino Database Pool Star Schemav Monthly Domino Database Star Schemav Monthly Domino Disk Star schemav Monthly Domino ICM Star Schemav Monthly Domino IMAP Star Schemav Monthly Domino Internet Port Star Schemav Monthly Domino LDAP Star Schemav Monthly Domino Mail Star Schemav Monthly Domino Mail Transfer Agent Star Schemav Monthly Domino NETBIOS Star Schemav Monthly Domino Netware Disk Star Schemav Monthly Domino News Protocol Star Schemav Monthly Domino Performance Station Star Schemav Monthly Domino POP3 Star Schemav Monthly Domino Remote Server Star Schema


v Monthly Domino Replica Star Schemav Monthly Domino Server Star Schemav Monthly Domino SMTP Star Schemav Monthly Domino SMTPMTA Star Schemav Monthly Domino SPIN Star Schemav Monthly Domino Web Retriever Star Schemav Monthly Domino XPC Star Schemav Weekly Domino Addin Task Star Schemav Weekly Domino Agent Star Schemav Weekly Domino Calendar Star Schemav Weekly Domino Communications Star Schemav Weekly Domino Database Pool Star Schemav Weekly Domino Database Star Schemav Weekly Domino Disk Star schemav Weekly Domino ICM Star Schemav Weekly Domino IMAP Star Schemav Weekly Domino Internet Port Star Schemav Weekly Domino LDAP Star Schemav Weekly Domino Mail Star Schemav Weekly Domino Mail Transfer Agent Star Schemav Weekly Domino NETBIOS Star Schemav Weekly Domino Netware Disk Star Schemav Weekly Domino News Protocol Star Schemav Weekly Domino Performance Station Star Schemav Weekly Domino POP3 Star Schemav Weekly Domino Remote Server Star Schemav Weekly Domino Replica Star Schemav Weekly Domino Server Star Schemav Weekly Domino SMTP Star Schemav Weekly Domino SMTPMTA Star Schemav Weekly Domino SPIN Star Schemav Weekly Domino Web Retriever Star Schemav Weekly Domino XPC Star Schema

This data mart provides the following prepackaged reports:v Bottom Servers By Availability

This summary report ranks the servers by the server availability value from thelast 7 days’ average.

v Calendar EntryThis report shows the daily average values for the DPSCalendarEntry probe. Theresults are for the last 30 days.

v Database AccessThis report shows the daily average values for the DPSDatabaseAccess probe.The results are shown over the last 30 days.

v Domino Server Usage: Sessions Dropped


This report shows daily average number of sessions dropped by Domino Serversfor the last 7 days.

v Mail Average StatisticsThis report shows the mail average statistics for all the Domino servers.

v Mail DeadThis report shows the daily average for the MAIL.Dead statistic with all theservers for the 7 last days.

v Mail WaitingThis report shows the daily average values for the Mail Waiting statistic for thelast 7 days.

v NAB SearchThis report shows the daily average values for the DPSNABSearch probe. Theresults are for the last 30 days.

v Net EchoThis report shows the daily average value for the DPSNetEcho probe. Theresults shown are for the last 30 days.

v Replicate LocalThis report shows the daily average values for the DPSReplicateLocal probe foreach server.

v Round Trip MailThis report shows the daily average values for DPSRoundTripMail probe foreach server.

v Web AccessThis report shows the daily average value for the DPSWebAccess probe. Theresults are shown for the last 30 days.

The following table lists the Tivoli Enterprise Data Warehouse reports that areprovided with this product, the resource models that must be run to create thosereports, and the metrics for the reports. For more information on how to createthese resource models see the Creating custom resource models using the IBM TivoliMonitoring Workbench chapter in the IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino Reference Guide

Table 19. Tivoli Enterprise Data Warehouse reports to resource model mapping

Report name Resource model name Report metric name

Bottom Servers byAvailability

DominoServerAvailability DominoServerAvailabilityUp

Calendar Entry DMXDPSCalendarEntry DPSCalendarEntry

Database Access DMXDPSDatabaseAccess DPSDatabaseAccess

Mail Average Statistics DominoMailStatisticsMonitor MAIL.Dead, Mail.Waiting,Mail.Delivered

Mail Dead DominoMailStatisticMonitor MAIL.Dead

Mail Waiting DominoMailStatisticsMonitor MAIL.Waiting

NAB Search DMXDPSNABSearch DPSNABSearch

Net Echo DMXDPSNetEcho DPSNetEcho

Replicate Local DMXDPSReplicateLocal DPSReplicateLocal

Round Trip Mail DMXDPSRoundTripMail DPSRoundTripMail

Web Access DMXDPSWebAccess DPSWebAccess



Chapter 12. Backing up and restoring Domino databases

Tivoli Data Protection for Lotus Domino is an application that backs up andrestores Lotus Domino databases, templates, and transaction log files. Whenarchive logging is used on the Domino server, it archives transaction log files andretrieves them as required for a database recovery. Database backups and archivedtransaction log files are stored on a Tivoli Storage Manager server.

Most of the functions of Tivoli Data Protection are integrated into IBM TivoliMonitoring for Messaging and Collaboration. The following features are notsupported and must be performed from Tivoli Data Protection:v Schedulingv Restoring a single archived transaction log filev Specifying a different destination or file name for restoresv Activating and applying archived transactions to a single database

Tivoli Data Protection for Lotus Domino must be installed and configured on everyserver whose databases you plan to back up.


Table 20. Goals and where to find procedures for backing up and restoring databases


Configure the product for Tivoli DataProtection for Lotus Domino.

“Configuring Tivoli Data Protection forLotus Domino” on page 249

Perform a backup of Domino databases andtemplate files on a Domino server.

“Backing up Domino databases” on page252

Restore and activate backed-up Dominodatabases. Bring restored databases on line foruse by the Domino server.

“Restoring Domino databases” on page254

“Activating Domino databases” on page256

Back up and archive transaction log files forthe specified Domino server.

“Archiving transaction log files” on page258

View all archived transaction log files for thespecified Domino server to determine whetherarchived transactions are available for a specificinterval.

“Viewing archived transaction log files”on page 260

Inactivate transaction log files that are notrequired by active databases.

“Inactivating transaction log files” onpage 262

Configuring Tivoli Data Protection for Lotus Domino

ObjectiveTo configure this product to work with Tivoli Data Protection for Lotus Domino.


Background informationThe most important aspect of configuring the product for Tivoli Data Protection forLotus Domino is to ensure that Tivoli Data Protection for Lotus Domino itself iscorrectly configured on the Domino server computer. Be sure that the domdsmcprogram, included with Tivoli Data Protection for Lotus Domino, is correctlyconfigured and that you can run it from a command line at the Domino server.

Note: If the domdsmc program is not running correctly, you cannot back up andrestore databases on a Domino server. This procedure describes how to testdomdsmc and then configure the Domino server correctly. See thedocumentation for Tivoli Data Protection for Lotus Domino for information oninstalling that product correctly.

This procedure describes how to access the Tivoli user interface in which you canset the following configuration attributes for Tivoli Data Protection for LotusDomino. These settings enable the domdsmc program:

Table 21. Descriptions of configuration attributes for Tivoli Data Protection for Lotus Domino

Name Description

TDP ProgramDirectory

The directory where Tivoli Data Protection for Lotus Domino isinstalled. The value for this directory corresponds to the DOMI_DIRenvironment variable on UNIX. On Windows the default path isC:\Program Files\Tivoli\TSM\domino.

TSM API Directory The directory where the Tivoli Data Protection for Lotus DominoAPI files are installed. The value for this directory corresponds to theDSMI_DIR environment variable on UNIX. On Windows, thedefault path is C:\Program Files\Tivoli\TSM\api.

TDP ConfigurationFile

The name of the Tivoli Data Protection for Lotus Dominoconfiguration file, relative to the Tivoli Data Protection for LotusDomino directory (unless you specify the full path and name). Thedefault file is domdsm.cfg. The value for this corresponds to theDSMI_DIR environment variable on UNIX. On Windows, thedefault path is C:\Program Files\Tivoli\TSM\api.

TDP Options File The name of the Tivoli Data Protection for Lotus Domino optionsfile, relative to the Tivoli Data Protection for Lotus Domino directory.The default file is dsm.opt. If you enter only the name dsm.opt, theproduct looks for the file in the tdpprogramdirectory. You can alsoenter a full pathname for the file.

TDP User The name of the Tivoli Data Protection for Lotus Domino user. Thisname corresponds to the nodename that was set in the dsm.sys fileduring the configuration of Tivoli Data Protection for Lotus Domino.

TDP Password The password of the Tivoli Data Protection for Lotus Domino userwhich permits you to run domdsmc, and is stored in encryptedformat in the LotusDominoServer object.

Required authorization roleDomino_TDP_Admin

Before you beginConfigure the Domino server as described in “Locating a Domino server andcreating a Domino Server object” on page 35. You use the procedure below whenyou have new or updated information to add the original server configurationsettings that you made. In the Tivoli command line interface, you can enter thesettings for Tivoli Data Protection for Lotus Domino only while you create a


Domino server object. To update those settings you must use the Tivoli desktop orthe Management Console, as described in this procedure.

Confirm that Tivoli Data Protection for Lotus Domino is correctly installed:1. Log in as the notes user on the Domino server you want to test.2. Run the following command:

domdsmc query adsmserver

3. Respond to the password prompt.4. Respond to the result as appropriate:

v If the command is successful, begin to configure Domino servers as describedin this procedure.—OR—

v If the command displays an error message, domdsmc is not responding.Check whether Tivoli Data Protection for Lotus Domino is correctly installedas described in the documentation for Tivoli Data Protection for LotusDomino. Be sure to consult the Read Me files for that product.



Desktop:

1. Navigate to the policy region that contains the Domino server that you want tomodify.

2. Double-click the Messaging and Collaboration policy region icon or the policyregion icon for the region to which you are adding a Domino server. The PolicyRegion window is displayed.

3. Double click the server icon to display the Properties dialog box.4. Click and drag a corner of the dialog box to expand the view. All configuration

attributes are displayed.5. Enter new or missing values the for settings described in “Background

information” on page 250.6. Click OK.

Management Console:

1. Click the Configuration tab to access the configuration view of theManagement Console.

2. Click the Domino server you want to modify in the tree view.3. Click Edit in the toolbar. The Edit dialog box is displayed.4. Click the Backup tab to display the configuration attributes for Tivoli Data

Protection for Lotus Domino.5. Enter new or missing values the for settings described in “Background

information” on page 250.6. Click Save.

Note: This step saves your settings. You must continue this procedure tocomplete the configuration of the server. Servers that are not configuredas server objects in this product have the letter U (for Unconfigured) inthe Status column of their row in the Management Console.

Chapter 12. Backing up and restoring Domino databases 251

7. Click Configure in the toolbar. The Configure dialog box is displayed.8. Click the name of the server you are configuring.9. Click Execute to apply your settings.

Backing up Domino databases

ObjectiveTo perform a backup — either incremental or selective — of Domino databases andtemplate files on a Domino server.

Background informationTwo types of backup are supported:v Incremental backups, which perform a full backup of the specified databases that

meet at least one of the following conditions:– The database is within the Domino data path or symbolically linked to the

Domino data path by directory or database links.– If the database has archive logging enabled, the Database Instance Identifier

(DBIID) has changed. (See your Domino server documentation for moreinformation on the DBIID and when it can change.)

– If the database is not logged, it was modified since the last backup occurred(data and non-data modification dates are checked).

– The database is new or newly included in the backup.v Selective backups, which unconditionally back up the specified databases.

The type of backup you choose depends on your site’s requirements, such as thesize of your Domino installation and the amount of network traffic. See the TivoliData Protection for Lotus Domino for Windows NT Installation and User’s Guide or theTivoli Data Protection for Lotus Domino for UNIX Installation and User’s Guide forinformation on backup strategy and timing.


Before you beginTivoli Data Protection must be installed and configured on every server whosedatabases you plan to back up. See the Tivoli Data Protection for Lotus Domino forWindows NT Installation and User’s Guide or the Tivoli Data Protection for LotusDomino for UNIX Installation and User’s Guide for more information on this topic.

When you finishYou can restore the backed up database, if necessary, as described in “RestoringDomino databases” on page 254.

You can activate the backed up database, if necessary, as described in “ActivatingDomino databases” on page 256.


Command line: Use the following commands to back up Domino databases:v wtmdincrementalbackup command to perform an incremental backup.v wtmdselectivebackup command to perform a selective backup.


v wtmdquerybackup command to obtain a list of all database template (.ntf) anddatabase (.nsf) files on the specified server.

v wruntask command with the following tasks:– Incremental Backup

– Selective Backup

– Query Backup

See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for more information about these commands.

Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Incremental Backup

v Selective Backup

v Query Backup


Management Console: Use the following procedure to back up Domino database(.nsf) files and template (.ntf) files:1. Click the Backup and Restore tab.2. From the Backup and Restore tab, click the Backup tab to display the Backup

pane.

Note: The left side of this pane lists all Domino servers that are running theappropriate version of Tivoli Data Protection for Domino. These servericons do not display server status.

3. Click a server name in the server list to display a list of all the databases andtemplate files on the server.

4. Click the Options tab on the right side of the Backup pane to display thebackup options.

5. Use the Show menu from the Options tab to filter the listing to display onlydatabases, only templates, or both.

6. Select the check box in the database listing next to each database and templatefile that you want to back up.

7. Select a backup type (Selective or Incremental) from the Options tab.8. Click Backup to display the Backup window.9. Click Execute from the Backup window to start the backup.

Figure 107. Backup and Restore tab Backup subtab Options (Management Console)


When the backup completes, status messages similar to the following appear in theBackup window. In this example, the database file admin4.nsf and the templatefile admin4.ntf are backed up successfully:Starting Domino database backup...Initializing Domino connection...Querying Domino for a list of databases, please wait...Logging on to the Tivoli Storage Manager server, please wait...

Backing up database admin4.nsf, 1 of 2.Full: 3 Read: 931840 Written: 0 Rate: 0.00 Kb/SecFull: 0 Read: 931840 Written: 931840 Rate: 507.53 Kb/SecBackup of admin4.nsf completed successfully.

Backing up database admin4.ntf, 2 of 2.Full: 0 Read: 647168 Written: 647168 Rate: 605.36 Kb/SecFull: 0 Read: 647168 Written: 647168 Rate: 437.37 Kb/SecBackup of admin4.ntf completed successfully.

Total Domino databases inspected: 2Total Domino databases backed up: 2Total Domino databases excluded: 0

Throughput rate: 472.72 Kb/SecTotal bytes transferred: 1,579,008Elapsed processing time: 3.26 Secs

Restoring Domino databases

ObjectiveTo restore and activate Domino databases that you have backed up.

If you need to apply transaction log files, restoring and activating is a two-partprocess:1. Restore the database using the Restore option as described in this procedure.2. Apply the transaction log files and activate the database using the Activate

option as described in “Activating Domino databases” on page 256.

Background informationDomino databases might need to be restored after a device failure or if a databaseis corrupted. You can restore Domino databases by reloading a database backupand optionally applying updates (from the transaction logs) that occurred after thebackup was taken. When you restore a database, keep in mind that data in thedatabase is overwritten and replaced by the data in the backup version.

A Domino database recovery can involve restoring several transaction log files inaddition to the database backup file. The function to restore database files isseparate from the function to apply updates from the transaction log. This enablesdatabase file restores to be performed separately, although transaction logprocessing for all restored databases is performed at the same time. This approachavoids restoring the same transaction log files multiple times.




When you finishIf necessary, apply transaction log files and activate the database as described in“Activating Domino databases” on page 256.


Command line: Use the following commands for restoring Domino databases:v wtmdrestoredbs command to perform a restore.v wtmdqueryrestore command returns a list of all backed-up database versions

for the specified Domino server.v wruntask command with the following tasks:

– Restore Databases

– Query Restore

See the IBM Tivoli Monitoring for Messaging and Collaboration: Lotus Domino ReferenceGuide for more information about these commands.

Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Restore Databases

v Query Restore


Management Console:

1. Click the Backup and Restore tab.2. Click the Restore tab from the Start Resource Modelto display the Restore

pane.3. Select a server from the server list to display a list of all the backup files stored

on the Tivoli Storage Manager server for the server you selected.4. Select the check box next to each file in the listing of backup files that you want

to restore.5. Click the Options tab on the right side of the Backup pane and select one or

more of the following options:v Select Activate to bring restored databases on line for use by the Domino

server. Select this option if you are not going to apply transaction log files.v Select Replace existing files to cause the backup file to overwrite the

existing file. If you do not select this option, the restore fails and displays amessage stating that the file already exists.

v Select Point in Time to restore the most recent backup version prior to thetime that you specify.


6. Click Restore to display the Restore window.7. Click Execute from the Restore window to start the restore.

When the restore completes, status messages similar to the following appear in theRestore window. In this example, the database backup admin4.ntf is beingrestored and is overwriting the current version of the database. The database is notbeing activated.Starting Domino database restore...

Initializing Domino connection...Logging on to the Tivoli Storage Manager server, please wait...Querying Tivoli Storage Manager server for a list of database backups,please wait...

Restoring database admin4.ntf, 1 of 1,to /tivoli/tools/lotus/notesr4/admin4.ntf.dad

Full: 0 Read: 647168 Written: 647168 Rate: 611.22 Kb/SecFull: 0 Read: 647168 Written: 647168 Rate: 610.63 Kb/SecRestore of admin4.ntf completed successfully.

Total database backups inspected: 1Total database backups requested for restore: 1Total database backups restored: 1Total database activated: 0

Throughput rate: 610.04 Kb/SecTotal bytes transferred: 647,168Elapsed processing time: 1.04 Secs

Activating Domino databases

ObjectiveTo bring restored databases on line for use by the Domino server. You canoptionally apply transactions from the transaction log files to update the database.

Background informationThis is the second part of the two-part Restore and Activate procedure. “RestoringDomino databases” on page 254 describes the first part of the procedure.

This function restores transactions from all transaction log files. For information onrestoring transactions from a single transaction log file, see the Tivoli Data Protectionfor Lotus Domino for Windows NT Installation and User’s Guide or the Tivoli DataProtection for Lotus Domino for UNIX Installation and User’s Guide.

You can view a list of all transaction log files with the date and time they werecreated as described in “Viewing archived transaction log files” on page 260.

Figure 108. Backup and Restore tab Restore subtab Options (Management Console)



Before you beginYou should have already restored the databases as described in “Restoring Dominodatabases” on page 254.



Command line: Use the following commands when activating Domino databases:v wtmdactivatedbs command to activate a database and to optionally apply

updates from a transaction log filev wtmdqueryactivate command returns a list of databases that were restored but

were not yet activated on the specified serverv wruntask command with the following tasks:

– Activate Databases

– Query Activate


Desktop: Run the following tasks in the task library as described in “Runningtasks” on page 172:v Query Activate

v Query Backup


Management Console: Use the following procedure to activate all databases thatwere restored and optionally apply updates from a transaction log file. You do nothave the option to activate a single database within a group of restored databases:1. Click the Backup and Restore tab.2. Click the Activate tab from the Backup and Restore tab to display the Activate

pane.3. Select a server from the server list.4. Select the check box in the listing of backup files next to each file that you want

to activate.5. Click the Options tab on the right side of the Backup pane and choose one or

both of the following options:v Select Apply Logs to apply transactions from the transaction log files to

update the database.v Select Point in Time to apply transactions up to the point in time that you

specify.


6. Click Activate to display the Activate window.7. Click Execute from the Activate window.

When activation completes, status messages similar to the following appear in theActivate window:wtmdactivatedbs TigerSUCCESS

Starting Domino database activation...

Initializing Domino connection...Logging on to the Tivoli Storage Manager server, please wait...

Activating database alog4.ntf, 1 of 3,Activate of alog4.ntf completed successfully.

Activating database billing.ntf, 2 of 3,Activate of billing.ntf completed successfully.

Activating database busytime.ntf, 3 of 3,Activate of busytime.ntf completed successfully.

Total pending databases inspected: 3Total pending databases requested for activation: 3Total pending databases activated: 3

Archiving transaction log files

ObjectiveTo back up and archive transaction log files for the specified Domino server.

Background informationTransaction log files capture changes to databases between full backups. They arestored on the Tivoli Storage Manager server. Changes to a database that occur afterthe last full backup can be applied from the transaction log files after you restorethe backup.

To work with Tivoli Data Protection, you must use archive logging, which is atransaction logging method based on files that are created as needed. These filescannot be overwritten until they are archived. IBM Tivoli Monitoring forMessaging and Collaboration can write data to transactions logs only for databasesthat have archive logging in effect.

In contrast to archive logging, circular logging is a transaction logging methodbased on a fixed amount of disk space. If the disk space you allocate fortransaction logs is filled, the application overwrites the oldest transactions. Thismethod is not valid for use with Tivoli Data Protection. If the Domino

Figure 109. Backup and Restore tab Activate subtab Options (Management Console)


administrator activates circular logging or disables logging on a Domino server,IBM Tivoli Monitoring for Messaging and Collaboration cannot write data to atransaction log for a database on that server.


Before you beginEnable archive logging on the Domino server.



Command line: Use the following commands to archive transaction log files:v wtmdarchivetranslog commandv wruntask command with the Archive Transactional Log task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Archive Transactional Log. See IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino Reference Guide for a description of thedesktop options for this task.

Management Console:

1. Click the Backup and Restore tab.2. Click Tools to display the Tools drop-down menu.3. Click Transaction Logs from the Tools menu.4. Click Archive Logs from the Transaction Logs menu to display the Archive

Logs window.


5. Select a server from the Archive Logs window and click Execute.

When archiving completes, status messages similar to the following appear in theArchive Logs window. The following example shows a successful backup of thelog file S0000001.TXN.Starting Domino transaction log archive...Initializing Domino connection...Logging on to the Tivoli Storage Manager server, please wait...

Backing up archivelog file /data/lotus/notesr4/log/S0000001.TXNFull: 0 Read: 67109888 Written: 67109888 Rate: 559.85 Kb/SecBackup of /data/lotus/notesr4/log/S0000001.TXN completed successfully.

Total Domino transaction log files ready for archive: 1Total Domino transaction log files archived: 1

Throughput rate: 559.84 Kb/SecTotal bytes transferred: 67109888Elapsed processing time: 117.06 Secs

Viewing archived transaction log files

ObjectiveTo display a list of all archived transaction log files for the specified Dominoserver. The listing includes the date and time each file was created. You can usethis information to determine whether archived transactions are available for aspecific interval.

Background informationSee “Archiving transaction log files” on page 258 for an overview of transactionlog files.

Required authorization roleDomino_TDP_User

Figure 110. Archive Logs dialog box (Management Console)


Before you beginRun the archive transaction log command.



Command line: Use the following commands to list archived transaction log files:v wtmdquerytranslog commandv wruntask command with the Query Transaction Log task


Desktop: Run the following task in the task library as described in “Runningtasks” on page 172: Query Transaction Log. See IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino Reference Guide for a description of the desktopoptions for this task.

Management Console: To view archived transaction log files, perform thefollowing steps:1. Click the Backup and Restore tab.2. Click Tools to display the Tools drop-down menu.3. Click Transaction Logs from the Tools menu.4. Click View Log Archives from the Transaction Logs menu to display the View

Log Archives dialog box.

Figure 111. View Log Archives dialog box (Management Console)


5. Select a server from the View Log Archives window and click Execute. A list ofall transaction log files on the selected server is displayed in the View LogArchives window.The following example shows the log archive that this procedure displays fortransaction log files S0000001.TXN and S0000000.TXN.count: 2

Logger Id: OF062569F8:00541677-ON99030000:05646AAE----------

TransactionLog Archive Date Log Filename A/I Size------------------- ------------ --- ------02/28/2001 12:13:56 S0000001.TXN A 64.00MB02/28/2001 12:12:42 S0000000.TXN A 64.00MB

Inactivating transaction log files

ObjectiveTo inactivate transaction log files that are not required by active databases.

Background informationSee “Archiving transaction log files” on page 258 for an overview of transactionlog files.

Transaction log files are archived on the Tivoli Storage Manager server as long as adatabase backup exists that requires these log files for a complete recovery. Thisfunction inactivates transaction log files that are no longer needed.





Command line: Use the following commands to inactivate transaction log files:v wtmdinactivatetranslog commandv wruntask command with the Inactivate Transaction Logging task


Desktop: Run the following Tivoli task in the task library as described in“Running tasks” on page 172: Inactivate Transaction Logging. See IBM TivoliMonitoring for Messaging and Collaboration: Lotus Domino Reference Guide for adescription of the desktop options for this task.

Management Console:

1. Click the Backup and Restore tab.2. Click Tools to display the Tools drop-down menu.3. Click Transaction Logs from the Tools menu.


4. Click Inactivate Log Archives from the Transaction Logs menu to display theInactivate Log Archives dialog box.

5. Select a server and click Execute from the Inactivate Log Archives window.

The Inactivate Log Archives window displays a message similar to the following:Number of Logs Inactivated: 4

Figure 112. Inactivate Log Archives dialog box (Management Console)



Appendix A. Authorization roles quick reference

Table 22 contains a list of the authorization roles that you need to perform the IBMTivoli Monitoring for Messaging and Collaboration: Lotus Domino functions. Thetable also shows which interfaces you can use to perform the functions (commandline, Tivoli Desktop, and Management Console) and whether you can run thefunction as a task. You can run most of the functions as a task through both thecommand line and the Tivoli desktop. In the table, x indicates that the interface issupported for the function, or that you can run the function as a task from eitherthe command line or desktop. Some functions run from other interfaces, which arenoted as applicable in the table.

Table 22. Authorization roles and interfaces for functions

Functions Authorization roles Interfaces and methods

CLI Desktop Console Task

Setting up

Setting authorization roles senior x x

Managing policy regions admin, senior x x x

Managing resource types policy, senior, super x x

Subscribing to notice groups senior x x x

Configuring Domino Server objects

Locating a Domino server andcreating a Domino Server object

Domino_Admin x x x

Discovering and configuring multipleservers in the Management Console

Domino_Admin x

Deleting a Domino Server object Domino_Admin x x x x

Working with IBM Tivoli Monitoring

Creating profile managers and profiles senior x x x

Adding a default resource model to aprofile

admin x x x

Adding a custom resource model to aprofile

admin x x x

Customizing indications admin x x x

Specifying tasks for an indication admin x x x

Customizing parameters admin x x x

Customizing a schedule for a resourcemodel

admin x x x

Customizing data logging information admin x x x

Subscribing resources to profilemanagers

admin x x x

Managing profiles and resourcemodels at endpoints

admin x

Managing IBM Tivoli Monitoringgateways

admin x

Determining which resource modelshave been distributed to endpoints

admin x


Table 22. Authorization roles and interfaces for functions (continued)



Determining which resource modelsare running on endpoints

admin x

Creating resource models using theTivoli workbench

admin

Distributing a profile from the desktop admin x x x

Rerunning a failed distribution admin x x

Working with Lotus Domino Servers

Checking server status x x x x

Controlling a server Domino_Admin x x x x

Controlling resource models forservers

Domino_Admin x x x

Running Domino tasks Domino_Admin x

Viewing server properties Domino_Admin x x

Editing server properties Domino_Admin x x

Viewing Domino statistics Domino_Admin x x x x

Entering a Domino remote consolecommand

Domino_Admin x x x x

Checking server health Domino_User x x x x

Viewing and searching log files Domino_Admin x x x x

Checking for database corruption Domino_User x x x x

Verifying mail files and checking MailWaiting


Viewing replication information Domino_Admin x x x x

Checking for inactive users Domino_User x x x x

Viewing and changing the AccessControl List (ACL)


Working with Domino Performance Stations

Configuring a Domino PerformanceStation

Domino_DPS_Admin x x x

Configuring probes for a station Domino_DPS_Admin x x

Configuring a resource model tomonitor probes

Domino_DPS_Admin x x x

Deleting a Domino PerformanceStation

Domino_DPS_Admin x x x x

Controlling a station Domino_DPS_Admin x x

Controlling resource models forstations

Domino_DPS_Admin x x

Deleting probes Domino_DPS_Admin x x

Resetting probes Domino_DPS_Admin x x

Running a probe one time Domino_DPS_User x x

Checking probe status Domino_DPS_Admin x x





Checking the integrity of aperformance station

Domino_DPS_Admin x x

Working with tasks and jobs

Running tasks Domino_Admin x x x

Customizing a task Domino_Admin x

Creating jobs Domino_Admin x x

Running jobs Domino_Admin x x

Scheduling jobs Domino_Admin x x

Backing up and restoring databases

Configuring Tivoli Data Protection forLotus Domino

Domino_TDP_Admin x x

Backing up Domino databases Domino_TDP_Admin x x x x

Restoring Domino databases Domino_TDP_Admin x x x x

Activating Domino databases Domino_TDP_Admin x x x x

Archiving transaction log files Domino_TDP_Admin x x x x

Viewing archived transaction log files Domino_TDP_User x x x x

Inactivating transaction log files Domino_TDP_Admin x x x x

Setting up Tivoli Enterprise Console

Configuring remote event correlationfor this product

Domino_Admin x x

Configuring local event correlation forthis product

Domino_Admin x

Customizing the Events4 Profile forlocal event correlation

Domino_Admin x

Controlling the local rule engine Domino_Admin x x x x

Viewing events user x x

Integrating with Tivoli Business Systems Manager

Integrating with Tivoli BusinessSystems Manager

administrator on TivoliBusiness SystemsManager server

x

Configuring the Tivoli EnterpriseConsole event server

senior x x

Discovering resources for TivoliBusiness Systems Manager

Domino_Admin x x

Uninstalling IBM Tivoli Monitoring forMessaging and Collaboration: LotusDomino integration from TivoliBusiness Systems Manager

administrator on TivoliBusiness SystemsManager server

x

Working with health data

*The command line and desktop interfaces are not supported for working with the health data.

Checking the health of resources asreal-time data

user Web Health Console* x

Viewing historical data user Web Health Console* x

Appendix A. Authorization roles quick reference 267




Customizing data views and settingpreferences


Saving, exporting, and printing dataand reports


Enabling the software for Tivoli Enterprise Data Warehouse

**The command line, desktop, and management console interfaces are not supported.

Accessing the IBM Console superadmin Web Console**

Creating an IBM Console user superadmin IBM Console**

Assigning authorization roles to a user superuser IBM Console**

Creating a user group admin IBM Console**

Assigning users to a user group admin IBM Console**

Assigning user groups to a data mart admin IBM Console**

Running reports AdvRepAuthRole,RepAuthRole,RepReaderRole

IBM Console**

Scheduling reports to runautomatically

AdvRepAuthRole IBM Console**

Modifying default settings for reports AdvRepAuthRole IBM Console**

Creating reports AdvRepAuthRole,RepAuthRole

IBM Console**

Creating a Many MeasurementsVersus Time Domino-specific report

AdvRepAuthRole,RepAuthRole

IBM Console**


Appendix B. Problem determination

Problems that you encounter while using the product to manage a Dominoinstallation can have many causes, such as machine or server availability, errorsoriginating in the operating system or in Lotus Notes, or configuration problems inthis product.

You can activate logging in the Management Console to log errors and otherdebugging information by performing the following steps:1. Click the Configuration tab.2. Click the Preferences tab and select the options you want: error logging only,

various levels of debugging, and the directory to which the product saves thelog.

Table 23 lists some common problems and suggestions for recovering.

Table 23. Symptoms and suggested actions for recovering from common problems

Symptom Suggested action

A server not responding error message results fromthe execution of one of the following operations:

v A task in the Domino Server Operations tasklibrary

v A menu option on the server icon pop-up menu

v An action in the Management Console

Issue a remote console command from the Domino remoteconsole window to test communication within the Dominoenvironment. If Domino is not communicating with itself,IBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino cannot communicate with Domino.

A server-level task fails with a permissions error,such as:

Could not delete object <object_name> (theobject identifier is1229815375.1.943#DominoManager::LotusDominoServer#). An authorization error oftype "insufficient authorization" occurred.

1. Ensure that you assigned the Domino_Adminauthorization role to the administrator who runs the task.

2. When you assign new roles, restart the Tivoli desktop sothat the assigned roles take effect.

Distribution of .id files or .ini files fails. Check Tivoli resource roles. You must have senior authorityto perform these tasks.

Domino Performance Station endpoints on whichother Java-based applications are running producesa contention problem because the station controllerrelies on a dedicated Java run-time instance.

Avoid this problem by disabling all other Java-basedapplications or services running on the system that is host forthe performance station. Ensure that you close the Notesclient open on the Performance Station Host.

In versions of the Lotus Notes R5 client earlier thanrelease 5.0.3b, the station controller can terminateunexpectedly with a pop-up message indicating thata Java memory access violation occurred.

Avoid this error by periodically restarting the DominoPerformance Station object using a Tivoli scheduled job orupgrade the Lotus Notes client to version 5.0.3b or later.

Events are not being forwarded to the TivoliEnterprise Console.

Verify that the Tivoli Enterprise Console is working, by usingthe wpostemsg command, as described in the Tivoli EnterpriseConsole, Reference Manual, Version 3.7.1 .

Verify that the ConfigureTEC for TMD task has been run.

The Events tab on the Management Console is notpresent.

Run the ConfigureTEC for TMD task.


Table 23. Symptoms and suggested actions for recovering from common problems (continued)


You are not receiving any Tivoli Enterprise Consoleevents.

Manually modify all of your .conf files located on theendpoint to contain the name of the Tivoli Enterprise Consoleserver and the port on which the server is listening. Forexample:

FileName: fcbs-tivoli-2.confServerLodation=TheActualTECServerNameServerPort=PortYouUse

When creating probes from the ManagementConsole, the Reset Probes action pushes the probesdown to the Performance Station.

Use the wdpsintegrity command to verify that the engineand the probes are up and running. If the creation was notsuccessful, try the Reset Probes action again. If the probecreation is still unsuccessful, complete the following steps:

wdpsstop $stationwdpsdelete $stationwdpscreate $stationwdpsaddserverwdpsstart $stationwdpsstartengine

Add the probes from the Management Console. Repeat theReset Probes procedure until you see the probes in theoutput of the wdpsintegrity command.

The DPSRoundTripMail resource model sends ane-mail to the administrator you designate to confirmthe success of each round-trip mail transaction.These e-mails can accumulate and overload themailbox of that administrator.

Create a Lotus Notes agent to archive or delete these e-mails.See the Lotus Notes online documentation for informationabout how to create Lotus Notes agents.

The Tivoli add-in does not start when the Dominoserver starts.

Depending on the version of the Domino server, Tivoliv46 orTivoliv50 must be on the ServerTasks line of the NOTES.INIfile.




A yellow triangle is displayed next to the servericon in the Management Console Status andOperations tab.

The yellow triangle generally indicates a problemdetermining the status of the Domino server either because ofcommunication problems or endpoint problems.

v Make sure the endpoint is running (wep <endpoint label>status and wadminep <endpoint label> view_versionreturns successfully). Also verify that the ITM 5.1 engine isrunning properly on that endpoint.

The Status and Operations tab has a view of the resourcemodels currently running on the endpoint where the LotusDomino Server is configured. When you click on the serverobject in the server tree, the Management Console tries toobtain the resource model information and display it in thecenter table. If this information cannot be retrieved fromthe endpoint (the LCF is down or the ITM 5.1 engine is notrunning).

v Make sure that the gateway that controls the endpointwhere the Domino server resides is up and available (Thewgateway command should return that gateway as ″up″and controlling the selected endpoint. The wep lscommand should report the endpoint as attached to theproper gateway.

If there is a problem communicating with the server objectin the gateway or Tivoli management region when usingany of the operations for a Domino Server object on theStatus and Operations tab (for example: Start, Stop,Remote Console, ACL, Check Health) it might be becausethe gateway is not up and available.

Tivoli Enterprise Console events are not reaching theTivoli Enterprise Console server.

This might happen for the following reasons:

v The endpoint correlation engine is not started on theDomino server. Use the wtmdstartengine command or itsequivalent on the Management Console, and make sure thetec_rule process is running on the endpoint after using thiscommand.

v The server needs an events4 profile. Use the ManagementConsole to distribute an events4 profile to this server so itcan start relaying events4 events to the Tivoli EnterpriseConsole.

v The server is sending the events to the wrong TivoliEnterprise Console server. Change the server objectproperties in the Configuration tab dialog box in theManagement Console to specify the proper TivoliEnterprise Console server to forward events to.

v The Tivoli Enterprise Console rule base is not updated withthe IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino classes. Be sure to run theConfigure TEC for Messaging and Collaboration task in theMessaging and Collaboration Configuration Task Librarythat is in the Messaging and Collaboration Policy Region.

Appendix B. Problem determination 271



Server objects remain unconfigured for a shortperiod of time after object creation.

There is a period of time after the creation of a Lotus DominoServer object when the object remains unconfigured. Duringthis time, important object attributes such as server name,domain name, and server network allow time for the Tivoliaddin task to initialize and set these variables to theirconfigured settings. During the time that the object hasunconfigured values, do not distribute monitoring profiles toit. After the Tivoli addin task loads and the object becomesfully configured, IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino automatically distributes theappropriate predefined monitoring profiles to the object.

Tivoli automatically distribute profiles. During installation, IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino creates several predefinedprofile managers populated with ″best practices″ monitoringprofiles. As you create a LotusDominoServer object, IBMTivoli Monitoring for Messaging and Collaboration: LotusDomino attempts to subscribe the new object to one or moreof the predefined profile managers and subsequentlydistributes the monitoring profiles to the new object. If youdo not want this behavior, stop the automatic subscriptionsand distributions by renaming all of the predefined profilemanagers that were created during the installation of IBMTivoli Monitoring for Messaging and Collaboration: LotusDomino.

The Tivoli addin task (tivoliv50/ntivoliv50)disappears from the notes.ini file.

During configuration of a Domino server, Tivoli inserts theaddin task (tivoliv50/ntivoliv50.exe) into the list of addintasks on the ServerTasks= line in the notes.ini file. However,when the Domino server starts, the notes.ini file isback-leveled. This can happen where there is a serverconfiguration document in the Domino Name and AddressBook (also known as the Domino Directory). Tivoli does notedit the server configuration document, so if you have one, itoverwrites notes.ini every time the server starts. If you knowyou have server configuration documents, configure Tivoliwhen the Domino server is running. Allow theLotusDominoServer object to become fully initialized. Watchthe value of Server Release, Cluster Name, or both in theLotusDominoServer settings window. Then make a copy ofthe notes.ini file and incorporate it into the serverconfiguration document.

A TIVOLI DUMP file is in the data directory on theserver.

An unexpected exception occurred in the Tivoli addin task.Gather these items and report this symptom to CustomerSupport:

v Notes about any user action that directly resulted in theexception

v The set of monitors running at the Domino server(wdmlseng?) at the time of the exception

v The Tivoli dump file

v If the Tivoli exception causes a Domino server panic, theninclude a copy of the nsd*.log file that results from nsd-kill.




If a resource model fails and thetrace_dmxengine.log does not contain details thatexplain why the resource model failed, set the tracesettings higher (the default is 0).

To reset the trace settings type the following from your TMR:wdmtrceng -e endpoint name ″″ 3 5000000 This command tellsthe endpoint specified by endpoint name to set the trace levelto 3 for all log files (″″) and to roll the logs over at 5000000bytes (approximately 5 MB). Modify these parameters to fityour needs. For more information, type

wdmtrceng

with no arguments. It will display a brief help message.

Frequently asked questionsTable 24 contains a list of questions related to problems you may have with thissoftware and answers for each question.

Table 24. Frequently asked questions related to problem determination

Question Answer

Does Tivoli Manager for Domino (TMD) version 3.1use secured or unsecured (that is, TME or non-TME)communication when forwarding events to the TivoliEnterprise Console server from the local TMD TECengine?

TMD 3.1 only supports unsecured (non-TME)communications when forwarding events from its localTivoli Enterprise Console engine to a designated TivoliEnterprise Console server. This is a Tivoli Manager forDomino 3.1 product limitation.

Can the severity filtering for the events4.nsf databaseevent actions be globally set on multiple Dominoservers, rather then one at a time?

Yes. The changes can be made on one Domino server andthen distributed to other servers. This distribution is part ofthe Domino application. Please see your DominoAdministrator for more information.

Does the user ID used to configure a Domino serverin IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Domino need to match the IDused to start the Domino Server Service/Process?

Yes. It is important to ensure that the file permission of thedom_lock and domcache files is set to be owned by theuserid used to run the Domino server. Otherwise thetivaddin might have difficulty updating the files correctly.This can also cause difficulties in creating log files totroubleshoot any creation or configuration issues.

Can we create a Domino Server object while theserver is up?

Yes, you can create a Domino Server object while the serveris running. It detects the proper version and subscribes tothe corresponding Domino Basic profiles.

Domino server console messagesTable 25 shows error messages that might be displayed in the Lotus Domino serverconsole. The list includes workarounds for the errors.

Table 25. Domino server console messages and workarounds

Message Workaround


Table 25. Domino server console messages and workarounds (continued)

Tivoli: Could not initialize TECAgent

This message is displayed in the Domino server console or is logged in the log.nsffile because the standalone Tivoli Enterprise Console engine at the endpoint is notstarted. You must start it with one of the following methods:

v From the command prompt, type wtmdstartengine <object_name>,

where <object_name> is the name of the server object on which the engine islocated.

v From the Tivoli desktop, right-click the server icon and select Start Engine fromthe menu.

v From the Management Console Tools menu on the Status and Operations tab,click Start/Stop Event Engine. In the displayed dialog box, select the name ofthe server, click Start, and click OK.

Tivoli: Could not Send eventsto TEC. Make sure TEC isrunning.

This message is displayed in the Domino server console or is logged in the log.nsffile because the standalone Tivoli Enterprise Console engine at the endpoint hasstopped and cannot send Tivoli Enterprise Console events to the engine. You muststart the engine with one of the following methods:

v From the command prompt, type wtmdstartengine <object_name>,

where <object_name> is the name of the server object on which the engine islocated.

v From the Tivoli desktop, right-click the server icon and select Start Engine fromthe menu.

v From the Management Console Tools menu on the Status and Operations tab,click Start/Stop Event Engine. In the displayed dialog box, select the name ofthe server, click Start, and click OK.

When the engine starts, the following message is displayed:

Tivoli: TEC is running. Sending events to TEC.

Error Calling System Command If you receive the Error Calling System Command message when adding a Notesserver to the performance station object, check that Administrator is part of thew32-ix86 map using the widmap list_entries root_user command.

IBM Tivoli Monitoring for Messaging and Collaboration: LotusDominoIBM Tivoli Monitoring for Messaging and Collaboration: LotusDomino messages

Table 26 contains a list of messages that you can receive from IBM TivoliMonitoring for Messaging and Collaboration: Lotus DominoIBM Tivoli Monitoringfor Messaging and Collaboration: Lotus Domino and suggested actions for eachmessage.

Table 26. Messages and suggested actions

Error message Suggested action

ABA250025E: Error, The call to the NT ServiceSubsystem to start the Domino Server failed.

This error occurs when you are starting the Domino serverfrom the Management Console or command line. You mustconfigure the Domino server as a Windows NT ServerService. This allows IBM Tivoli Monitoring for Messagingand Collaboration: Lotus Domino to start, stop, or locate theserver.


Table 26. Messages and suggested actions (continued)

ABA270169E TEC Operator preferences couldn’t beretrieved from TEC Server.

—OR—

ABA270201E Unable to create TEC console or forsome reason the Events tab in the ManagementConsole fails to load.

The Events tab in the Management Console does not work.In the Management Console, the Events tab does not showanything.

The ABA270169E error means that the user in the TivoliEnterprise Console has not been assigned to any TECconsole, no event groups have been assigned to this userconsole in the Tivoli Enterprise Console, or both.

The ABA270201E means that there has been an errorconnecting, retrieving data from the Tivoli EnterpriseConsole server, or both.

Open the Tivoli Enterprise Console JAVA console using thetec_console command and ensure that the following is true:

v The user who is logging into IBM Tivoli Monitoring forMessaging and Collaboration: Lotus Domino has beenassigned to a console.

v The console has at least one Event Group assigned to it.

v The user can see events in the Tivoli Enterprise Console3.7 JAVA console.

Note: A Tivoli Enterprise Console administrator has todefine this user as a Tivoli Enterprise Console operatorusing the Tivoli Enterprise Console 3.7.1 JAVA console inroot mode before this user can see events in TMD 3.1 orIBM Tivoli Monitoring for Messaging and Collaboration:Lotus Domino.

Testing endpoint connectivityThe Tivoli server must be able to communicate with the Domino server objects itmanages. The Tivoli endpoint is software that you install on a Domino server toenable communication. You can use the Tivoli endpoint wizard to verify the Tivoliendpoint, as described in the IBM Tivoli Monitoring for Messaging and CollaborationInstallation and Setup Guide. The wizard might generate an Error message duringverification. You should test endpoint connectivity when you encounter this Errormessage.

Test the connection of an endpoint to the Tivoli management region server for thisproduct as follows:1. Run the ping command from the Tivoli server to confirm that the endpoint is

accessible over the network. If you receive connection or timeout errors, stop atthis point and contact your network administrator for help.

2. If you do not know the name of the endpoint, run the following command onthe Tivoli server to see a list of all endpoints that are connected to the server:wlookup -a -r Endpoint

3. Run the following command on the Tivoli management region server:wadminep <ep_name> view_version

where <ep_name> is the name of a specific Tivoli endpoint on a Domino server.See the list generated in Step 2 to obtain the names of endpoints.

4. If you receive a message other than one containing a single version number, theTivoli endpoint software must be restarted. You can manually restart the Tivoliendpoint on that server as follows:


v On Windows systems, perform the following steps:a. Run the following command to stop the lcfd process of the Tivoli

endpoint:net stop lcfd

b. Run the following command to start the lcfd process:net start lcfd

v On Solaris and AIX systems, perform the following steps:a. Use the following command to identify the lcfd process:

ps -ef | grep lcfd

b. Kill this process.c. Use the following command to set the required environment variables:

. /etc/Tivoli/lcf/<RUN_ID>/lcf_env.sh

where [RUN_ID] is the ID number of the lcfd process.d. Use the following command to restart the lcfd process:

$LCF_BINDIR/lcfd.sh

v On OS/400 systems perform the following steps:a. Run the ENDTMEEPT command and press F4 to select the appropriate

commands for stopping the endpoint process.b. Run the STRTMEEPT command and press F4 to select the appropriate

commands for restarting the endpoint process.5. Monitor the state of the Tivoli endpoint you have just restarted from a Web

browser using the following URL:http://<ep_host>:<ep_port>

where <ep_host> is the name of the Domino server object and <ep_port> is thename of the port that you assigned for Tivoli endpoint transactions on theTivoli server. After the state of the Tivoli endpoint changes to running, go toStep 6.

6. Use the TMA Wizard to run the TMA Verify command.Additional Information: Verification can generate one of the following results:v Success means that the endpoint is running and communicating with the

Tivoli server. You have finished checking endpoint connectivity.—OR—

v Error means that verification failed. You can respond as follows:a. Clean up and remove the Tivoli endpoint as described in “Deleting a

Domino Server object” on page 49.b. Install the Tivoli endpoint on the Domino server object again, as

described in “Managing resource types” on page 29.c. Verify whether reinstallation of the Tivoli endpoint resolved the original

problem.d. If verification generates an Error message again, contact Customer

Support for further assistance with problem determination.


Appendix C. Messages

ABA220002E Domino performance station objectalready exists.

Explanation: No additional information is availablefor this message.

ABA220003E Station does not exist.


ABA220004E Program terminated before the log couldbe generated.


ABA220005E Endpoint does not exist.


ABA220007I Success.


ABA220008W Already running.


ABA220009E A general failure has occurred - checkyour endpoint.


ABA220010E Notes.jar file not found in INI directory.


ABA220011W Not running.


ABA220012W Already stopped.


ABA220013E Exceeded time limit.


ABA220015E ID file was not found on the endpoint.


ABA220016I Server is already supported by thisstation.


ABA220017E Server is not supported by this station.


ABA220018E Installation requires a w32-ix86 platformon the endpoint.


ABA220020E Invalid probe name.


ABA220021I Ok.


ABA220022E Timeout - check connection orpassword.


ABA220023E I/O error.


ABA220024E Initialization error.



ABA220025E Finalization error.


ABA220026E Controller probe error.


ABA220027E Controller system error.


ABA220028E Unknown host.


ABA220029E Unknown service.


ABA220030E Invalid host, server, or URL.


ABA220031E Cannot establish connection.


ABA220032E Error reading/writing to connection.


ABA220033E Error closing connection.


ABA220034E Transaction timeout.


ABA220035E Transaction did not complete.


ABA220036E An undefined error was encountered.


ABA220037E Subtransaction did not complete.


ABA220038E Error creating Notes session.


ABA220039E Error authenticating user.


ABA220040E Error connecting to server or database.


ABA220041E Error searching through database.


ABA220042E Error creating document.


ABA220043E Error removing document.


ABA220044E Error reading document.


ABA220045E Error writing document.


ABA220046E Error sending document.


ABA220025E • ABA220046E


ABA220047E Error saving document.


ABA220048E Error replicating database.


ABA220049E Inconsistent time on source server.


ABA220050E Fatal probe error.


ABA220051E Error getting common name of server.


ABA220052E Error updating location document.


ABA220053E Size of received UDP packet not equalto sent.


ABA220054E Error text encountered.


ABA220055I Ok.


ABA220058I Data currently not available.


ABA220059E Insufficient role to complete thisoperation.


ABA220061E Manager for Domino 3.0 region missingor corrupted.


ABA220067I You may monitor probe status(wdpsprobestatus) with probe ID.


ABA220068E No probes running matching this IDand no data.


ABA220070E One or more components are notrunning.


ABA220071E One or more probes are consistently inerror.


ABA220071E One or more probes are consistently inerror.


ABA220072E An unexpected exception occurred.


ABA220406E ProbeID is not valid. ProbeID must be anumber from 1 to 4,294,967,295.


ABA220407E Probe type is not valid.

Explanation: Probe type must be one of the following:DPSCalendarEntry, DPSDatabaseAccess,DPSNABSearch, DPSNetEcho, DPSReplicateLocal,DPSRoundTripMail, DPSWebAccess (case insensitive).

ABA220408E Threshold is not valid. Threshold mustbe a number from 0 to 4,294,967,295.


ABA220047E • ABA220408E

Appendix C. Messages 279

ABA220409E Frequency is not valid. Possible valuesare 10_min, 30_min, 1_hour, 4_hour,8_hour (case insensitive).


ABA220410E The number of arguments for the givenprobe type is not correct.


ABA220411E The probe id supplied already exists.Use a probe id that does not currentlyexist.


ABA220412E A probe was unable to be started.


ABA220413E A probe was unable to be stopped.


ABA220414E The EPP controller on the endpointfailed to start.


ABA220415E The EPP controller on the endpointfailed to stop.


ABA220416E The Domino Performance Station (DPS)is downlevel. Unable to execute thisprogram against a downlevel DPS.


ABA220417E No configured probe exists with thegiven probe ID.


ABA220418E Probe ID is reserved.


ABA220419E An internal error occurred.


ABA220420E This function is no longer supported.


ABA220421E An out of memory error occurred.


ABA220422E Unable to open probe log file.


ABA220423E Unable to read probe log file.


ABA220424E Unable to find LCF_DATDIR in thecurrent environment.


ABA220073E TEC engine directory not found.


ABA220074E File I/O handles to spawn new processare NULL.


ABA220075E Error calling system command.


ABA220076E Monitoring environment file not foundon station.


ABA220409E • ABA220076E


ABA250001E You specified an endpoint name that isnot known to the system. Please specifya different endpoint name: For a listingof all valid endpoints, use the wep lscommand

Explanation: The endpoint name that you specified isnot known to this system. This error can occur if youincorrectly type the name or if the endpoint is deletedfrom this Tivoli management region. To view the list ofall valid endpoints, use the wep ls command.

ABA250002E You specified an endpoint that iscurrently not connected to the system

Explanation: The endpoint that you are attempting towork with is not currently communicating with itsgateway. This can occur if the endpoint process hasstopped, its gateway is stopped, or there is a networkproblem. To ensure that your endpoint is correctlyoperating and communicating, issue the wadminep<ENDPOINTNAME> view_version command, where<ENDPOINTNAME> is the name of the endpoint inquestion.

ABA250003E The system is unable to locate thespecified Policy Region

Explanation: The specified policy region cannot befound within this Tivoli management region. To view alist of all known policy regions, use the wlookup -arPolicyRegion command.

ABA250004E An error occurred attempting to createthe specified Policy Region

Explanation: The policy region that you specifiedcannot be created. This error can occur if the policyregion already exists. To view a list of all known policyregions, use the wlookup -ar PolicyRegion command.

ABA250005E An error occurred attempting to set thestate of the object

Explanation: An error occurred while you weresetting the state of the object. If this problem persists,contact Tivoli Customer Support.

SUPPORT: This should not occur. Deleting andrecreating the object should resolve this problem ifthere is corruption in the Tivoli Object Database. Toinvestigate, use the idlcall %OBJECT% _get_state andidlcall %OBJECT% _set_state commands to attempt tomanually set and get the state of the object.

ABA250006E An error occurred while attempting tomove an object between Policy Regions

Explanation: An error occurred while you weremoving an object from one policy region to another.This can occur if there is a problem with the policy

region to which you are moving the object. If youreceive this error while creating a server object, specifya different policy region as part of your creationparameters. You can also move all of the objects fromthe problem policy region to a new policy region,delete the problem region, and then rename the newregion to match the name of the original policy region.

ABA250007E An unexpected exception occurred

Explanation: An unexpected error occurred during theoperation of the command that you specified. If thisproblem persists, contact Tivoli Customer Support.

SUPPORT: Use the specified command with -DEBUG toobtain more information on the error.

ABA250008E An unknown class name was specified

Explanation: This is an internal error related to aproblem with the object class names used by thisproduct. Contact Tivoli Customer Support for furtherassistance.

SUPPORT: This can occur if the internal InterfaceRepository (IR) is corrupted.

ABA250009E An out of memory error occurred

Explanation: There is not enough memory available tocomplete the requested command. If this commandworks on multiple items (such as checking thereplication for multiple days or checking for databasecorruption on multiple databases), narrow your criteria.If this error continues to occur, contact Tivoli CustomerSupport.

ABA250010E Unable to open specified file

Explanation: The file specified is not available. Ensurethat the file you specified is available and that the filesecurity permissions enable it to be accessed.

ABA250011E Error, the specified object label isalready in use. Please select a differentname for this server object

Explanation: The name that you specified for theobject during creation is already in use. Each objectmust have a unique name. Specify a unique name forthe object.

ABA250012E Error, During configuration,NotesInitExtended1 Failed. If thisproblem persists after restarting yourserver, then contact Tivoli support

Explanation: A failure occurred when youcommunicated with the Domino Server. Ensure thatyour Domino server is operating correctly. Restart theDomino Server to resolve this issue.

ABA250001E • ABA250012E


ABA250013E Error, During configuration,NotesInitExtended2 Failed. If thisproblem persists after restarting yourserver, then contact Tivoli support

Explanation: A failure occurred when youcommunicated with the Domino Server. Ensure thatyour Domino server is operating correctly. Restart theDomino Server to resolve this issue.

ABA250014E Error, During configuration, unable tolocate server name. If this problempersists after restarting your server, thencontact Tivoli support

Explanation: The Domino server cannot determine itsserver name. This can occur if the notes.ini file that youspecified when locating or creating servers is corrupt orinvalid for this server.

ABA250015E Error, During configuration unable tolocate server task information inNotes.ini file. Please insure that there isa server task entry in your Notes.ini file

Explanation: No ServerTasks= line is contained withinthe notes.ini file that was specified during the creationof the Domino server object.

ABA250017E Error, Unable to open NT ServiceManager, possible Registry corruption

Explanation: This can occur if there is a problem withyour Windows NT service manager or registry. Use theservice control panel within Windows to start theserver to ensure that there is no corruption or problemwith your service registry. Use the SC.EXE tool that isavailable within the Window NT Resource Kit todiagnose problems with your services control registry.

ABA250018E Error, Unable to Enumerate NT Services,possible Registry corruption

Explanation: This can occur if there is a problem withyour NT service manager or registry. Use the servicecontrol panel within Windows to start the server toensure that there is no corruption or problem with yourservice registry. Use the SC.EXE tool that is availablewithin the Window NT Resource Kit to diagnoseproblems with your services control registry.

ABA250019E Error, Unable to open NT Service Entryfor Domino Server, possible Registrycorruption

Explanation: This can occur if there is a problem withyour NT service manager or registry. Use the servicecontrol panel within Windows to start the server toensure that there is no corruption or problem with yourservice registry. Use the SC.EXE tool that is availablewithin the Window NT Resource Kit to diagnose

problems with your services control registry.

ABA250020E Error, Unable to query NT Serviceconfiguration, possible Registrycorruption


ABA250021E Error, Unable to query NT Servicestatus, possible Registry corruption


ABA250022W The Domino Server is already running


ABA250023E Error, requested the NT Service forDomino to start, but it’s state is notStart Pending


ABA250024E Error, Attempted to Start the NT Servicefor Domino Server, but received an NTService error


ABA250025E Error, The call to the NT Servicesubsystem to start the Domino serverfailed

Explanation: This can occur if there is a problem withyour NT service manager or registry. Use the servicecontrol panel within Windows to start the server to

ABA250013E • ABA250025E


ensure that there is no corruption or problem with yourservice registry. Use the SC.EXE tool that is availablewithin the Window NT Resource Kit to diagnoseproblems with your services control registry.

ABA250026E Error, There is no NT Registry serviceentry for the specified Domino Serverwith the specified INI file

Explanation: There is no service entry for the .ini fileassociated with this server. During the server locationprocess, this error can occur if the specified .ini pathname is invalid. After the server is created, this erroroccurs only if the service entry is modified, corrupted,or deleted. Use the service control panel withinWindows to start the server to ensure that there is nocorruption or problem with the service registry. Use theSC.EXE tool that is available within the Window NTResource Kit to diagnose problems with your servicescontrol registry.

ABA250027E Error, requested the NT Service forDomino to stop, but its state is not StopPending

Explanation: This can occur if there is a problem withyour NT service manager or registry. Use the servicecontrol panel within Windows to start the server toensure that there is no corruption or problem with theservice registry. Use the SC.EXE tool that is availablewithin the Window NT Resource Kit to diagnoseproblems with your services control registry.

ABA250028E Error, Attempted to Stop the NT Servicefor Domino Server, but received a NTService error

Explanation: This can occur if there is a problem withyour NT service manager or registry. Use the servicecontrol panel within Windows to start the server toensure that there is no corruption or problem with theservice registry. Use the SC.EXE tool that is availablewithin the Window NT Resource Kit to diagnoseproblems with your services control registry.

ABA250030E Error, Unable to dynamically load theNotes DLL

Explanation: This error occurred while youdynamically loaded the notes.dll file. This error occursif an incorrect version, corrupted version, or no versionof the notes.dll file exists within the Domino serverprogram directory. ensure that this file exists and is thecorrect version.

ABA250031E Error, Unable to copy the Tivoli addinprocesses

Explanation: During server creation, the Tivolitivoliv46 and tivoliv50 addin processes on UNIX andthe Tivoli tivoliv46.exe and tivoliv50.exe addin

processes on NT (W32-I386) could not be copied to theDomino server program directory. Ensure that there issufficient free space on this file system.

ABA250032E Error, unable to locate theNotesInitExtended API in the NotesDLL

Explanation: This error can occur if an incorrect orcorrupted version of the notes.dll file exists in theDomino server program directory. Ensure that thecorrect version of this file exists in the domino serverprogram directory.

ABA250033E Error, unable to locate the NotesTermAPI in the Notes DLL

Explanation: This error can occur if an incorrect orcorrupted version of the notes.dll file exists in theDomino server program directory. Ensure that thecorrect version of this file exists in the domino serverprogram directory.

ABA250034E Error, unable to locate theOsGetEnvironment API in the NotesDLL

Explanation: This error can occur if an incorrect orcorrupted version of the notes.dll file exists in thedomino server program directory. Ensure that thecorrect version of this file exists in the domino serverprogram directory.

ABA250035E Error, unable to locate theOsSetEnvironment API in the NotesDLL


ABA250036E Error, unable to locate theSeckFMGetUserName API in the NotesDLL


ABA250037E Error, unable to locate theNSFRemoteConsole API in the NotesDLL

Explanation: This error can occur if an incorrect orcorrupted version of the notes.dll file exists in thedomino server program directory. Ensure that the

ABA250026E • ABA250037E


correct version of this file exists in the domino serverprogram directory.

ABA250038E Error, unable to locate theOSLockObject API in the Notes DLL


ABA250039E Error, unable to locate theOSUnlockObject API in the Notes DLL


ABA250040E Error, unable to locate the OSLoadStringAPI in the Notes DLL


ABA250041E Error, unable to locate the OSMemFreeAPI in the Notes DLL


ABA250042E Error, unable to get the ServerTasksentry from the Notes.ini file

Explanation: No ServerTasks= line is contained in thenotes.ini file that was specified during creation of theDomino server object.

ABA250043E Error, NotesInitExtended Call failure

Explanation: An attempt to communicate with theDomino server failed. This error normally occurs whenyou specify the incorrect notes.ini file for this server orwhen the specified notes.ini file is corrupted.

ABA250044E Error, SECKFMGetUserName Callfailure, unable to locate the servername

Explanation: The domino request to access the servername failed. This error can occur if the specifiednotes.ini file for this server is incorrect or corrupted.

ABA250045E Error, No response from the consolewhen starting the Tivoli Addin, TheAddin may not have started

Explanation: During the server creation andconfiguration process, the server requests that the Tivoliaddin process be started. If the Tivoli addin process isnot started, it is possible that the request did notsucceed. The Tivoli addin is already running or theserver file is not configured to enable password sharingwith addin tasks.

ABA250046E Error, An unknown error occurred whenattempting to start the Tivoli Addin

Explanation: During the server creation andconfiguration process, the server requests that the Tivoliaddin process be started. If the Tivoli addin process isnot started, it is possible that the request did notsucceed. The Tivoli addin is already running or theserver file is not configured to enable password sharingwith addin tasks.

ABA250047E Error, The call to the NT Servicesubsystem to stop the Domino serverfailed

Explanation: This error can occur if there is a problemwith your NT service manager or registry. Use theservice control panel within Windows to start theserver to ensure that there is no corruption or problemwith the service registry. Use the SC.EXE tool that isavailable within the Window NT Resource Kit can helpyou to diagnose problems with your services controlregistry.

ABA250048E Error, an unexpected error occurredattempting to start the Domino server

Explanation: This error can occur if there is a problemwith your NT service manager or registry. Use theservice control panel within Windows to start theserver to ensure that there is no corruption or problemwith the service registry. Use the SC.EXE tool that isavailable within the Window NT Resource Kit can helpyou to diagnose problems with your services controlregistry.

ABA250049E Error, The specified INI file name isinvalid

Explanation: The specified notes.ini file was notfound, could not be read, or is corrupted. Ensure thatthe file is available, readable, and correct for this server.

ABA250050I Error, The Domino Server is alreadyrunning


ABA250038E • ABA250050I


ABA250051I Domino server already stopped


ABA250052E Error, NT Server Service Recycle is onlysupported for NT platform.

Explanation: The NT Server Service Recycle commandcan be used only with Domino Servers running on NT.

ABA250053E Error, Unable to get Data Directory fromNotes

Explanation: The request by the Domino server todemsgnumine the location of the data directory failed.This error can occur if there is a problem with theconfiguration of the domino server.

ABA250054E Error, Unable to write local Tivoliconfiguration file in server datadirectory

Explanation: Ensure that there is ample free space onthe file system for the data directory and that securitypermission is enabled for writing and creating files.

ABA250055E Error, unable to locate theOSGetDataDirectory API in the NotesDLL

Explanation: This error can occur if an incorrect orcorrupt version of the notes.dll file exists in theDomino server program directory. Ensure that thecorrect version of the notes.dll file exists in the Dominoserver program directory.

ABA250056E Error, unable to locate theDNCanonicalize API in the Notes DLL


ABA250057E Error, unable to locate the NSFDBCloseAPI in the Notes DLL

Explanation: This error can occur if an incorrect orcorrupt version of the notes.dll file exists in theDomino server program directory. Ensure that thecorrect version of the notes.dll file existsin the Dominoserver program directory.

ABA250058E Error, unable to locate the NSFDBopenAPI in the Notes DLL

Explanation: This error can occur if an incorrect orcorrupt version of the notes.dll file exists in the

Domino server program directory. Ensure that thecorrect version of the notes.dll file exists in the Dominoserver program directory.

ABA250059E Error, unable to locate theNSFNoteOpen API in the Notes DLL


ABA250060E Error, unable to locate theNSFNoteUpdate API in the Notes DLL


ABA250061E Error, unable to locate theNSFNoteClose API in the Notes DLL


ABA250062E Error, unable to locate theNSFItemGetTextListEntries API in theNotes DLL


ABA250063E Error, unable to locate theNSFItemGetTextListEntry API in theNotes DLL


ABA250064E Error, unable to locate theNSFItemAppendTextList API in theNotes DLL


ABA250051I • ABA250064E


ABA250065E Error, unable to locate theNIFFindDesignNote API in the NotesDLL


ABA250066E Error, unable to locate theNIFCloseCollection API in the NotesDLL


ABA250067E Error, unable to locate theNIFOpenCollection API in the NotesDLL


ABA250068E Error, unable to locate theNIFFindByName API in the Notes DLL


ABA250069E Error, unable to locate theNIFReadEntries API in the Notes DLL


ABA250070E Error, unable to locate theEndpointManager object

Explanation: The attempt to locate the endpointmanager object failed. Ensure that you have the correctversion of Tivoli Framework installed. Rebooting theTivoli management region server can correct this error.

ABA250071E Error, unable to locate endpointinstance(s)

Explanation: Endpoints cannot be located. Ensure thatyou have the correct version of Tivoli Frameworkinstalled. Rebooting the Tivoli management regionserver can correct this error.

ABA250072W The server did not stop. (Portmapperserver may be stopped.)


ABA250073I The Domino server service has apending stop request.


ABA250074I The Domino server service has apending start request.


ABA250075I The Domino server service is currentlypaused.


ABA250076I The Domino server has either not beenstarted, or has started but not completedit’s initial configuration


ABA250077E The SERVER service cannot be stoppedbecause other running services aredependent on it

Explanation: The NT Server Service can only berecycled (restarted) if no other services are running. Ifanother service is running, the Server Service cannot bestopped. Use the Windows service manager todemsgnumine which services depend on the ServerService and stop those services before running thiscommand.

ABA250089E Invalid or obsolete View

Explanation: The specified view is invalid or obsoletewithin the database. Manually check the database toensure that the specified view is present and notinvalid or obsolete.

ABA250065E • ABA250089E


ABA250090E Database Open Failure

Explanation: The specified database cannot beaccessed. Ensure that the database is availablemanually and can be opened within the Lotus Notesclient.

ABA250091E The specified port is already in use

Explanation: The specified port is already in use.Please select a different port number or use thewtmdlocateserver command to have Tivoli Manager forDomino locate an unused port.

ABA250092E Unable to open the Name and AddressBook, to add this server as an admin

Explanation: There is a problem accessing thenames.nsf file on this server. Manually check that thenames.nsf file is present and not corrupted within theLotus Notes client.

ABA250093E Unable to locate the server document inthe Name and Address Book


ABA250094E Unable to open the server document inthe Name and Address Book


ABA250095E Unable to append to the serverdocument in the Name and AddressBook


ABA250096E Unable to update the server documentin the Name and Address Book


ABA250097E Unable to find the server view in theName and Address Book

Explanation: There is a problem accessing thenames.nsf file on this server. Manually check that the

names.nsf file is present and not corrupted within theLotus Notes client.

ABA250098E Unable to open server view collection inthe Name and Address Book


ABA250099E Unable to open server view by name inthe Name and Address Book


ABA250100E Unable to read the entries in the serverdocument in the Name and AddressBook


ABA250101E Unable to read the entry buffer in theserver document in the Name andAddress Book


ABA250102E Unable to find the server note in theName and Address Book


ABA250103E Unable to locate any servers on thisendpoint.

Explanation: There are no unconfigured servers onthis endpoint, or the location of the notes.ini files forthe servers cannot be located. This error can occur ifthe service control registry does not have an entry forthe Domino server on NT or if the data directoriesspecified in the /opt/lotus/.install.dat file do notcontain valid notes.ini files on UNIX.

ABA250090E • ABA250103E


ABA250104I Server Successfully Started


ABA250105I Server Successfully Stopped


ABA250106I Server Successfully Created


ABA250107I Server Successfully Deleted


ABA250108E No addin processes found

Explanation: No addin processes were found on thisserver. Use the sh tasks remote console command toensure that there are addin processes on this server.

ABA250109I The NT Server Service has beensuccessfully recycled.


ABA250110I The Domino Server has beensuccessfully recycled.


ABA250111I No users were found meeting thespecified criteria


ABA250112W No corrupt database views matchingthe passed specification were found.


ABA250115E 00 Error, unrecognized parameter

Explanation: One of the specified parameters isinvalid. Check the usage information for this commandto ensure that you are using the correct parameters.

ABA250116E 00 Error, Unable to create pw file

Explanation: The server cannot be started because afile within the data directory could not be created.Ensure that there is sufficient free space on the filesystem for this data directory and that the securitysettings enable writing, reading, and creating files.

ABA250117E 00 Error, unable to change the port forthis server

Explanation: The attempt to change the port for thisserver failed. Ensure that the server is running andcommunicating correctly with Tivoli. If not, use theLotus remote console to load the correct Tivoli addin.

ABA250118E When specifying TDP arguments, allTDP arguments are required except thepassword

Explanation: This error occurs if you do not specifyall the required Tivoli Data Protection (TDP)arguments. You must specify all Tivoli Data Protectionarguments or server creation fails.

ABA250119E Failure setting attributes for DominoServer

Explanation: When modifying Domino serverattributes, ensure that other administrators are not alsoattempting to modify the parameters at the same time.

ABA250120E A failure occurred while attempting toadd a value to the ApplSvcs AttributeCache

Explanation: When adding attributes to the endpoint,ensure that there is sufficient disk space available in thefile system where the Tivoli endpoint is installed.

ABA250181E Bad request type was passed to Tivoliaddin

Explanation: An invalid work request type waspassed to the Tivoli addin. This error can occur if thereare communication problems on the Domino serverwhere the addin is running or if another program isincorrectly attempting to use the same port as theTivoli addin. Specify a different port for this server toresolve this problem. If the problem persists, contactTivoli Customer Support.

ABA250182E The statistic name requested is eithernot available on the server or the nameis bad

Explanation: The specified statistic is not valid for thisserver. To view a list of valid statistics for this server,use the sh stat remote console command.

ABA250104I • ABA250182E


ABA250184W The console command was executedhowever it does not generate a result


ABA250186E Either Tivoli addin is not running orDomino server is not running

Explanation: Unable to communicate with the Tivoliaddin. If the Domino server is not running, you muststart it. If the Domino server is running, use the shtasks remote console command to ensure that the Tivoliaddin is running. If the Tivoli addin does not exist, usethe load tivoliv46 or the load tivoliv50 remote consolecommand to load the addin. If this problem persists,contact Tivoli Customer Support.

ABA250187I Tivoli addin is running


ABA250188W The command completed successfullyhowever the server did not produce anyresult for this command


ABA250189E The requested statistic(s) is not available

Explanation: The requested statistic is not available.Use the remote console command sh stat to view a listof all valid statistics for this server.

ABA250190E The database name specified could notbe located

Explanation: The specified database is not availableon this server. Use the Lotus Notes client to locate thisdatabase and then re-enter the correct database nameand path.

ABA250191E The ACLs for some or all of thedatabases specified could not be found

Explanation: The requested Access Control List (ACL)entries for some or all of the specified databases couldnot be located. Use the wtmdgetacl command to view alist of valid ACLs for these databases.

ABA250193W The Database was not modified pastthe date specified


ABA250194W There was no matching string foundthat matches the requested criteria


ABA250195E The syntax of the date specified is notcorrect: The correct syntax isMM/DD/YYYY

Explanation: The date specified is incorrect. Specifythe correct MM/DD/YYYY date format.

ABA250196E The nickname specified for FORM isnot correct: The correct options are

Explanation: You specified an incorrect nicknameform. Select from the following valid options andre-enter the command:

v Select Session to search for log file data in theSession form.

v Select Activity to search for log file data in theActivity form.

v Select Misc. Events to search for log file data in theMisc. Events form.

v Select Replication to search for log file data in theReplication form.

v Select Mail Routing to search for log file data in theMail Routing form.

v Select Phone Call to search for log file data in thePhone Call form.

v Select Phone Call - Incoming to search for log filedata in the Phone Call - Incoming form.

v Select Phone Call - Outgoing to search for log filedata in the Phone Call - Outgoing form.

v Select Size to search for log file data in the Sizeform.

v Select NNTP Events to search for log file data in theNNTP Events form.

v Select Object Store Usage to search for log file datain the Object Store Usage form.

v Select Passthru Connection to search for log file datain the Passthru Connection form.

ABA250197E The field name specified cannot befound

Explanation: The specified field name cannot befound. Check this database to ensure that the fieldname is correct.

ABA250198E The document ID specified is incorrect

Explanation: This error can occur if the document isremoved from the database. Use the wtmdquerylogcommand to view a list of valid document IDs.

ABA250184W • ABA250198E


ABA250199E log query requires either Include stringor Exclude string: Neither has beenspecified

Explanation: You must specify an include string,exclude string, or both.

ABA250200E Invalid mailbox specified.

Explanation: The specified mailbox does not exist.Specify a valid mailbox name.

ABA250201I There are no messages in the mailbox todelete.


ABA250202E Unable to open message in mailbox.

Explanation: An error occurred during an attempt toopen a message in this mailbox. Ensure that themailbox is not corrupt.

ABA250203E Unable to delete 1st message inmailbox.

Explanation: This error can occur if the message is nolonger the first message in the mailbox. Use thewtmdmailwaiting command to demsgnumine the firstmessage in this mailbox.

ABA250204E The Note ID and/or the Sender of themessage to purge does not match withthe message to be deleted.

Explanation: Cannot delete the first message in thismailbox. This error can occur if the message is nolonger in the mailbox or you incorrectly specified theNote ID or sender. Use the wtmdmailwaiting commandto demsgnumine the first message in this mailbox.

ABA250205E Address Book search found that serverdoes not contain any mail databases.

Explanation: The address book contains no maildatabase information. Check the address book for thisserver to ensure that there are mail databases on thisserver.

ABA250206E Cannot open names.nsf to look for theserver’s mail databases.

Explanation: This error can occur if the names.nsf fileis corrupt or locked. Ensure that the names.nsf isavailable on the Lotus Notes client.

ABA250207E Cannot open the ($People) view innames.nsf.

Explanation: Use the Lotus Notes client to ensure thatthere is a valid view in the names.nsf file.

ABA250208E Cannot open the collection in names.nsf.

Explanation: Specify a valid and accessible collectionview in the names.nsf file on the Lotus Notes client.

ABA250209E Cannot read the collection entries.

Explanation: Specify a valid and accessible collectionview in the names.nsf file on the Lotus Notes client.

ABA250210E Cannot open the person document.

Explanation: Use the Lotus Notes client to ensure thatall person documents within the names.nsf database arevalid and not corrupted.

ABA250211E Cannot open the mail database.

Explanation: This error can occur if the database iscorrupt or unavailable. Specify a valid and accessiblemail database on the Lotus Notes client.

ABA250212E Cannot create an ID table.

Explanation: Cannot create an ID table to view theage and size of each mail message in the specifieddatabase. Ensure that you can open the specified maildatabase and that it is not corrupt within the LotusNotes client.

ABA250213E Compilation of the selection formulafailed.

Explanation: Cannot create an ID table to view theage and size of each mail message in the specifieddatabase. Ensure that you can open the specified maildatabase and that it is not corrupt within the LotusNotes client.

ABA250214E Database search failed.

Explanation: Cannot perform a database search toview the age and size of each mail message in thespecified database. Ensure that you can open thespecified mail database and that it is not corrupt withinthe Lotus Notes client.

ABA250215E Unable to run the purge routine for eachnote.

Explanation: Cannot delete messages that match theage or size criteria specified. Ensure that you can openthe specified mail database and that it is not corruptwithin the Lotus Notes client.

ABA250199E • ABA250215E


ABA250216E Unable to find the size of each note.

Explanation: Cannot demsgnumine the message sizeof each mail message in the specified database. Ensurethat you can open the specified mail database and thatit is not corrupt within the Lotus Notes client.

ABA250217E Unable to delete the note.

Explanation: Cannot delete messages that match theage or size criteria specified. Ensure that you can openthe specified mail database and that it is not corruptwithin the Lotus Notes client.

ABA250218E Transactional logs not found on server.

Explanation: The transactional log files were notfound on this server. Ensure that transactional loggingis enabled and set it to the archival logging type. Checkthe logging directory and files to make sure that the logfiles exist.

ABA250220E Time could not be converted from textto timedate format.

Explanation: The time from the Domino server couldnot be converted to a timedate format. Check theDomino server to verify that the server time isconfigured properly.

ABA250221E Disk drive where transaction logs filesreside NOT found.

Explanation: The transactional log files could not befound in the location specified in the server documentof the Name and Address Book. If a network directorywas specified, ensure that this directory can be accessedfrom the server.

ABA250222E Check transactional log monitor is notsupported for this version of Notes.

Explanation: The transactional logging option is onlysupported in Lotus Domino 5.x versions. The serverdoes not support transactional logging for earlierversions of Notes.

ABA250227E Could not find ServerTasks entry in theNotes.ini file.

Explanation: A ServerTasks= line could not be locatedin the notes.ini file. Ensure that the notes.ini file for thisserver is correct and contains a valid ServerTasks= line.If this is the last line in the file, ensure that it isfollowed by a carriage return.

ABA250228E Number of Notes.ini tasks and ServerConsole tasks do not match.

Explanation: The number of custom notes.ini tasksand Server Console tasks specified do not match.

When you specify a custom notes.ini task, you mustalways specify a corresponding Server Console taskthat runs with this notes.ini task.

ABA250229E The database specified is invalid. Formultiple databases specification, pleaseuse semi-colon as the separator.

Explanation: The specified database is invalid. Ensurethat this database exists on this server and is notcorrupt.

ABA250230E Cannot get message information fromNotes

Explanation: An error occurred while attempting toretrieve information from the Notes message. Verifythat the message is not corrupt and that all the requiredfields were set.

ABA250231E Cannot access the database time


ABA250232E Cannot open Notes database file

Explanation: The specified database could not beopened. Ensure that the database name is valid and canbe opened within the Lotus Notes client.

ABA250234E Cannot create mail message list

Explanation: The list of mail messages cannot becreated. Ensure that the mail database has messagesand is not corrupt.

ABA250235E Cannot open mail message

Explanation: The mail message document cannot beopened. Ensure that the message has not been deletedand is not corrupt.

ABA250236I The server does not have anyReplication scheduled


ABA250237I There are no replication data availableon the server specified


ABA250216E • ABA250237I


ABA250239E Error cannot find any database specified

Explanation: The database specification provided doesnot match any databases on this server. Check thisserver to ensure that that a database matching thesupplied database specification is present and notcorrupted.

ABA250240E Error getting database space usageinformation


ABA250241E Error getting database quota information


ABA250242E Error attribute to be monitored isUNKNOWN

Explanation: The monitor attribute value is not valid.Specify a valid attribute value from the attribute list.

ABA250243E Error getting database access activities

Explanation: The database activity log is not enabled.Enable the log and try the function again.

ABA250244I The agent specified did not run in thetime frame specified


ABA250245W There is not agent run information toreport: The agent did not run at all


ABA250249W Attempt was made to start the server,however could not communicate withTivoli addin to confirm server startup.


ABA250250E Cannot initialize TCP/IP communicationwith Tivoli addin: Either the Dominoserver is down or the Tivoli addin is notrunning

Explanation: Communications cannot be initiated withthe Tivoli addin. This can occur if the domino server isnot running, in which case it should be started. If it isrunning, ensure that that the Tivoli addin is runningand if not, start it. If the Tivoli addin is running, theremay be a conflict with the port being used to

communicate with it. Changing the port should resolvethis problem. If this problem persists ,contact TivoliCustomer Support.

ABA250251E Cannot connect to Tivoli addin: Eitherthe Domino server is down or the Tivoliaddin is not running

Explanation: A connection cannot be made with theTivoli addin. If the Domino server is not running, startit. If it is running, use the remote console command shtasks to ensure that the Tivoli addin is running. If it isnot present, use the remote console command loadtivoliv46 or load tivoliv50 to start the addin. If thisproblem persists, contact Tivoli Customer Support.

ABA250252E Cannot write command to Tivoli addin:Either the Domino server is down or theTivoli addin is not running

Explanation: Unable to communicate with the Tivoliaddin. The domino server may have stopped in themiddle of communications for the Tivoli addin. Ensurethat the server is running and the Tivoli addin isrunning. If this problem persists, contact TivoliCustomer Support.

ABA250253E Cannot read result from Tivoli addin:Either the Domino server is down or theTivoli addin is not running

Explanation: Unable to communicate with the Tivoliaddin. The Domino server might have stopped in themiddle of communications for the Tivoli addin. Ensurethat the server is running and the Tivoli addin isrunning. If this problem persists, contact TivoliCustomer Support.

ABA250254E Tivoli addin cannot read from clientsocket

Explanation: A work request from another processended prematurely. This can occur if a command wasstopped during execution. If this problem persists,contact Tivoli Customer Support.

ABA250255E Tivoli addin cannot write to clientsocket

Explanation: A work request from another processended prematurely. This can occur if a command wasstopped during execution. If this problem persists,contact Tivoli Customer Support.

ABA250257W There were no extra mail files found atthe server.


ABA250239E • ABA250257W


ABA250258W There were no mail database filesfound at the server.


ABA250259E Cannot allocate memory

Explanation: Memory cannot be allocated to completethis request. If this request is for a large number ofwork items, break the request up into more than onepiece to enable it to complete successfully. If thisproblem persists, contact Tivoli Customer Support.

ABA250260E ***Bad Access level specification: Pleasecheck the Access levels ***

Explanation: An incorrect access level was specified.Refer to the Tivoli Manager for Domino ReferenceGuide for a list of valid access levels.

ABA250261E ***Bad Access flags specification: Pleasecheck the Access flags ***

Explanation: An incorrect access flag was specified.Refer to the Tivoli Manager for Domino ReferenceGuide for a list of valid access flags.

ABA250262I 1st message deleted from mailboxsuccessfully.


ABA250263I 1st message NOT deleted from mailbox:Message that would be deleted is shownbelow.


ABA250264I Messages purged successfully.


ABA250265I Messages NOT purged from the maildatabase(s): Mail that would be deletedis shown below.


ABA250266E A username is required for modifyingthe acl

Explanation: You must specify a valid user namewhen modifying the access control list. Re-enter thecommand specifying a valid user name.

ABA250267E When requesting to change a user name,both the old name and new name isrequired

Explanation: You specified only the old or new namein a name change request. Re-enter the commandspecifying both the old and new names.

ABA250268E Invalid number of arguments specified

Explanation: The arguments specified do not matchthe command. Refer to the Tivoli Manager for DominoReference Guide for the correct arguments for thiscommand.

ABA250269E Cannot get port from attribute cache

Explanation: The information stored within the Tivoliendpoint cannot be located. This can occur if yourendpoint has moved, or files have been removed fromthe endpoint. To resolve this problem, use thewtmdrecycleserver command to replace thisinformation on the Tivoli endpoint. If this problempersists, contact Tivoli Customer Support.

ABA250270E Cannot convert port string to number

Explanation: There is a problem with the specifiedport for this server. Ensure that it is a valid portnumber and then use the restart server command toensure that the port information is correct within theTivoli endpoint. If this problem persists, contact TivoliCustomer Support.

ABA250271E No recipient specified for the mailmessage

Explanation: You attempted to send a messagewithout specifying a recipient. Re-enter the commandand specify a recipient.

ABA250272E Cannot get mail server name

Explanation: There might be a problem with thisserver. Select a different server to send this message. Ifthe problem persists, contact Tivoli Customer Support.

ABA250273E Cannot open mail box file

Explanation: Cannot open the mail box file on thisserver to send a message. There might be a problemwith the server. Select a different server to send thismessage. If this problem persists, contact TivoliCustomer Support.

ABA250274E Cannot create a mail message

Explanation: Cannot create a mail message on thisserver. There might be a problem with the server. Selecta different server to send this message. If this problem

ABA250258W • ABA250274E


persists, contact Tivoli Customer Support.

ABA250275E Cannot create Recipient list

Explanation: Cannot create a Recipient list on thisserver. There might be a problem with the server. Selecta different server to send this message. If this problempersists, contact Tivoli Customer Support.

ABA250276E Cannot create SendTo list

Explanation: Cannot create a SendTo list on thisserver. There might be a problem with the server. Selecta different server to send this message. If this problempersists, contact Tivoli Customer Support.

ABA250277E Cannot create CopyTo list

Explanation: A CopyTo list cannot be created on thisserver. There might be a problem with the server. Selecta different server to send this message. If this problempersists, contact Tivoli Customer Support.

ABA250278E Cannot create BlindCopyTo list

Explanation: A BlindCopyTo list on this server couldnot be created. There might be a problem with thisserver. Select a different server to send this message. Ifthis problem persists, contact Tivoli Customer Support.

ABA250279E Cannot add recipient address to SendTolist

Explanation: An error occurred in adding a recipientaddress to the SendTo list. Ensure that the addressesspecified are valid. There might be a problem with thisserver. Select a different server to send this message. Ifthis problem persists, contact Tivoli Customer Support.

ABA250280E Cannot add recipient address toRecipient list

Explanation: An error occurred in adding a recipientaddress. Ensure that the addresses specified are valid.There might be a problem with this server. Select adifferent server to send this message. If this problempersists, contact Tivoli Customer Support.

ABA250281E Cannot add recipient address to CopyTolist


ABA250282E Cannot add recipient address toBlindCopyTo list


ABA250283E Cannot add Recipient list to the mailmessage


ABA250284E Cannot add SendTo list to the mailmessage

Explanation: An error occurred in adding the SendTolist to the message. Ensure that the addresses specifiedare valid.

There might be a problem with this server. Select adifferent server to send this message. If this problempersists, contact Tivoli Customer Support.

ABA250285E Cannot add CopyTo list to the mailmessage

Explanation: An error occurred in adding the CopyTolist to the message. Ensure that the addresses specifiedare valid. There might be a problem with this server.Select a different server to send this message. If thisproblem persists, contact Tivoli Customer Support.

ABA250286E Cannot add BlindCopyTo list to the mailmessage

Explanation: An error occurred in adding theBlindCopyTo list to the message. Ensure that theaddresses specified are valid.


ABA250287E Cannot set Form item in the mailmessage

Explanation: An error occurred in sending this mailmessage. There might be a problem with this server.Select a different server to send this message. If thisproblem persists, contact Tivoli Customer Support.

ABA250275E • ABA250287E


ABA250288E Cannot set From item in the mailmessage


ABA250289E Cannot set Subject item in the mailmessage


ABA250290E Cannot set Composed Date item in themail message


ABA250291E Cannot create Body item


ABA250292E Cannot append text to the Body item

Explanation: An error occurred in sending this mailmessage.


ABA250293E Cannot add Body item to the mailmessage



ABA250294E Cannot add Posted Date item in themail message



ABA250295E Cannot update the message to themailbox



ABA250296E Cannot close the mail message



ABA250297E Cannot close the mailbox file



ABA250298E Cannot add file attachment to themessage



ABA250299E Cannot open file for writing.

Explanation: The specified file name is invalid, or thespecified file path does not exist. Ensure that the filename does not contain invalid characters and that thespecified file path exists.

ABA250300E Error writing to file.

Explanation: The disk is full or write-protected, or theuser does not have permission to write to the filelocation. Ensure that there is enough disk space andthat the user has permission to write to the specifiedlocation.

ABA250301I wtmdsendmail complete successfully.


ABA250288E • ABA250301I


ABA250302E Invalid recipient specified.

Explanation: An invalid recipient was specified.Ensure that the recipients specified are valid andre-enter the command.

ABA250303E Invalid attachment specified.



ABA250304E Error occurred while processing file forattachment.



ABA250305E Error occurred when sending numericdata to DM

Explanation: The numeric data that was sent to IBMTivoli Monitoring was out of the valid range of dataallowed. Contact Tivoli Customer Support.

ABA250306E Data from get_log_req function isinvalid

Explanation: The log.nsf file does not haveinformation for database activity. Ensure that thelog.nsf file on the server has the Usage view.

ABA250307I Rule Engine Successfully Started.


ABA250308I Rule Engine Successfully Stopped.


ABA250309I Rule Engine Successfully Restarted.


ABA250310I Rule Engine Successfully Reloaded.


ABA250311E TEC Engine Directory Not Found.

Explanation: The directory%LCF_BINDIR%/TMDTEC was not found. Thisdirectory is created during configuration of eachDomino server. Make sure it was not deleted.

ABA250312E File IO Handles To Spawn New ProcessAre NULL.

Explanation: Could not create a file for spawning aprocess to start or stop Tivoli Manager for Domino.Contact Tivoli Customer Support.

ABA250313E Error Calling System Command.

Explanation: An error occurred when you tried tospawn a system command. Retry this command againsta different server. If this problem persists, contact TivoliCustomer Support.

ABA250314I Monitors successfully stopped


ABA250315I Monitors successfully started


ABA250316I Already running


ABA250317I Not running


ABA250318I Verify Mail Success.


ABA250319E DM Setup Environment File Not Found.

Explanation: There are no distributed monitorscurrently running on this server. Distributing monitorsto this endpoint will resolve this error.

ABA250320E TDP Unavailable. Unable to locate theTDP program directory for running theTDP command.

Explanation: An error occurred during an attempt tolocate the Tivoli Data Protection for Lotus Dominoprogram. Ensure that this server is configured for TivoliData Protection, and check that all Tivoli Data

ABA250302E • ABA250320E


Protection options are valid. Run this command usingthe Tivoli Data Protection command line to check ifTivoli Data Protection is configured and workingcorrectly.

ABA250321E The TDP configuration file was notfound. Unable to locate the TDPconfiguration file that contains theDomino server information.

Explanation: An error occurred during an attempt tolocate the Tivoli Data Protection for Lotus Dominoconfiguration file. Ensure that this server is configuredfor Tivoli Data Protection, and check that the TivoliData Protection configuration file exists in the specifiedlocation.

ABA250322E The TDP options file was not found.Unable to locate the TDP options filethat contains the TSM server connectioninformation.

Explanation: An error occurred during an attempt tolocate the Tivoli Data Protection for Lotus Dominooptions file. Ensure that this server is configured forTivoli Data Protection, and check that the Tivoli DataProtection options file exists in the specified location.

ABA250324W The TDP output file was not found:The TDP command may have failed torun. Make sure that your TDP forDomino environment has beenconfigured properly.


ABA250325E An out of memory error has occurred.

Explanation: Unable to run the following commandbecause an out-of-memory error occurred. Retry thiscommand against a different server. If this problempersists, contact Tivoli Customer Support.

ABA250326E The TDP command completed witherrors. Check with your TDPdocumentation for more information onthe specific error message.

Explanation: An error occurred in running the TivoliData Protection for Lotus Domino command. If a TivoliData Protection error code was returned, refer to theTivoli Data Protection for Lotus Domino Installationand User’s Guide for more information.

ABA250327E The TDP command has failed. Makesure that TDP has been properlyconfigured and that the TSM server isrunning.

Explanation: An error occurred in running the TivoliData Protection for Lotus Domino command. If a TivoliData Protection error code was returned, refer to theTivoli Data Protection for Lotus Domino Installationand User’s Guide for more information.

ABA250328I SUCCESS.


ABA250329E Failed to create new process to run theTDP command.

Explanation: An error occurred during an attempt tospawn the Tivoli Data Protection program. Retry thiscommand against a different server. If this problempersists, contact Tivoli Customer Support.

ABA250331E The dsm.sys file was not found. Unableto locate the dsm.sys file that containsthe TSM server connection information.

Explanation: An error occurred during an attempt tolocate the Tivoli Data Protection for Lotus Dominodsm.sys file. Check to ensure that this server isconfigured for Tivoli Data Protection, and check thatthe dsm.sys file exists in the specified ApplicationProgramming Interface (API) directory.

ABA250332E No database was found that matchedthe file specification entered.

Explanation: No database was found that matched thefile specification. Check to ensure that the databasespecified exists on the Domino server.

ABA250333E There are no databases to restore for thespecified server.

Explanation: There was no database to restore for thespecified server. No database backups exist on theTivoli Storage Manager server to be restored.

ABA250334E There are no databases to activate forthe specified server.

Explanation: There was no database to activate for thespecified server. No restored database exist on theDomino server to be activated.

ABA250321E • ABA250334E


ABA250335E No transaction log file to archive on thespecified server.

Explanation: There was no transactional log file toarchive for the specified server. Ensure that archivedtransactional logging is enabled on the Domino server.

ABA250336E There are no transaction log filearchives for the specified server.

Explanation: There were no transactional log filearchives for the specified server. No log files archivesexist on the Tivoli Storage Manager server.

ABA250337E Unable to locate RIM object tmd.

Explanation: An error occurred during an attempt tolocate the tmd RIM object. Check that the database forTivoli Manager for Domino, Version 3.1.0, has beencreated and use the wgetrim tmd command to viewthis RIM object information.

ABA250338E Unable to connect to RIM DatabaseHost. Either the RIM parameters areincorrect or the RDBMS is notresponding.

Explanation: An error occurred during an attempt toconnect to the RIM database using the tmd RIM object.Check that the database for Tivoli Manager forDomino, Version 3.1.0, has been created, and use thewrimtest -l tmd command to check this connection.Also, check that the Relational Database ManagementSystem (RDBMS) is running and that the databaseparameters are correct.

ABA250340E Unable to release RIM object tmd.

Explanation: An error occurred during an attempt torelease the RIM connection using the tmd RIM object.Ensure that the Relational Database ManagementSystem (RDBMS) is running and that the databaseparameters are correct.

ABA250341E Unable to lookup policy region "TivoliManager for Domino 3.1".

Explanation: There was a problem finding the TivoliManager for Domino 3.1 policy region. Ensure thatTivoli Manager for Domino, Version 3.1.0, was installedsuccessfully and that this policy region exists.

ABA250342E Date Format not supported.

Explanation: An error occurred during an attempt toprocess the specified date. Ensure that the datespecified is in the correct format according to thecommand usage.

ABA250343E Unable to insert row(s) into database.

Explanation: An error occurred during an attempt toinsert rows into the tmd database. Ensure that theRDBMS is running and that the database parametersare correct. Also check that the database and thetransaction log files are not full.

ABA250344E Unable to delete row(s) from database.

Explanation: An error occurred during an attempt todelete rows from the tmd database. Ensure that theRDBMS is running and that the database parametersare correct.

ABA250346I Data successfully removed.


ABA250347E Specified port is not valid or in thevalid range of port numbers, 3000 to9999, inclusive. Attempt the operationagain providing a port number in thisvalid range.


ABA250350E No TEC Event Server found


ABA250351E The specified TEC Server in thisDomino server was not found. Checkthe property "TEC Server" in the Serverconfiguration


ABA254508I Successfully restarted the addin.


ABA254509E Unable to restart the addin.


ABA254510E Addin failed to stop. Will not attempt tostart it.


ABA250335E • ABA254510E


ABA254511E Use of the remote console to start theaddin failed.


ABA254512E Use of the remote console to stop theaddin failed.


ABA254513E Failed to allocate memory internallywhen trying to restart the addin.


ABA254514E Restarting of the Tivoli addin is notallowed.


ABA254515E Lotus Domino Server does not exist.




ABA259200E The attempt to determine the cluster forthis server failed with an unexpectederror.

Explanation: The NOTES API (ApplicationProgramming Interface) request GetServerClusterMatesreturned an error outside of the expected range. Thismight occur due to unexpected problems with theconfiguration of the Domino Server. Ensure that thisserver is indeed part of a cluster and that it is correctlyconfigured. Also ensure that there are no warning orerror messages in the log.nsf. If this problem persists,please contact IBM support.

ABA259201E The Domino Server was unable to locateany cluster information for this server.

Explanation: The NOTES API (ApplicationProgramming Interface) requestNSGetServerClusterMates returned an error stating thatthis server does not contain any cluster mates(ERR_CLUSTER_NOMATES). There may be problemswith the configuration of the Domino Server. Ensurethat this server is indeed part of a cluster and that it iscorrectly configured. Also ensure that there are no

warning or error messages in the log.nsf. If thisproblem persists, please contact IBM support.

ABA259202E An error occurred attempting tocanonicalize the server’s name.

Explanation: While attempting to determine theservers within this servers cluster we attempted tocanonicalize this servers name. This caused anunexpected error to occur from the Domino Server.There may be problems with the configuration of thisDomino Server. Ensure that this server is indeed part ofa cluster and that it is correctly configured. Also ensurethat there are no warning or error messages in thelog.nsf. If this problem persists, please contact IBMsupport.

ABA259205E An error occurred getting the clusterentries.

Explanation: An unexpected error occurred whileattempting to get the list of servers in this serverscluster. There may be problems with the configurationof this Domino Server. Ensure that this server is indeedpart of a cluster and that it is correctly configured. Alsoensure that there are no warning or error messages inthe log.nsf. If this problem persists, please contact IBMsupport.

ABA259206E An error occurred while attempting toallocate memory on the Domino Serverto contain the State Array.

Explanation: An error occurred while attempting toallocate memory on the Domino Server. Under normalconditions this error should not occur. Check the serverto ensure that there is adequate memory and swapspace given the systems workload. If this problempersists, please contact IBM support.

ABA259207E An error occurred while attempting toallocate memory on the Domino Serverto contain the Name Array.

Explanation: An error occurred while attempting toallocate memory on the Domino Server. Under normalconditions this error should not occur. Check the serverto ensure that there is adequate memory and swapspace given the system’s workload. If this problempersists, please contact IBM support.

ABA259208E An error occurred while attempting toallocate memory on the Domino Serverto contain the Clustered Server Name.

Explanation: An error occurred while attempting toallocate memory on the Domino Server. Under normalconditions this error should not occur. Check the serverto ensure that there is adequate memory and swapspace given the systems workload. If this problempersists, please contact IBM support.

ABA254511E • ABA259208E


ABA259209E An error occurred attempting to get thename of the clustered server in theclustered sever list.

Explanation: While attempting to determine the nameof a server within this servers cluster we received anunexpected error from the Domino Server. There maybe problems with the configuration of this DominoServer. Ensure that this server is indeed part of acluster and that it is correctly configured. Also ensurethat there are no warning or error messages in thelog.nsf. If this problem persists, please contact IBMsupport.

ABA259215E Unable to open the specified database.

Explanation: There is a problem accessing thedatabase that was specified. Ensure that this database isactually available on the server and can be opened.Also ensure that the database is not corrupt.

ABA259216E Unable to open the get the user activityfor the specified database.

Explanation: There is a problem accessing thedatabase user activity information. Ensure that thisdatabase is available on the server and can be opened.Also ensure that the database is not corrupt.

ABA259217E Unable to open the get the space usagefor the specified database.

Explanation: There is a problem accessing thedatabase space usage information. Ensure that thisdatabase is available on the server and can be opened.Also ensure that the database is not corrupt.

ABA259218E Unable to open the get the databasequota for the specified database.

Explanation: There is a problem accessing thedatabase quota information. Ensure that this database isavailable on the server and can be opened. Also ensurethat the database is not corrupt.

ABA259500E Custom "PreStart" script failed. Whenatempting to run a custom script beforethe start of a server, the custom scriptindicated an unrecoverable error.


ABA259501E Custom "Start" script failed. Whenatempting to run a custom script inplace of starting of a server, the customscript indicated an unrecoverable error.


ABA259502E Custom "PostStart" script failed. Whenatempting to run a custom script afterthe start of a server, the custom scriptindicated an unrecoverable error.


ABA259600E Custom "PreStop" script failed. Whenatempting to run a custom script beforethe stop of a server, the custom scriptindicated an unrecoverable error.


ABA259601E Custom "Stop" script failed. Whenatempting to run a custom script inplace of stopping of a server, the customscript indicated an unrecoverable error.


ABA259602E Custom "PostStop" script failed. Whenatempting to run a custom script afterthe stop of a server, the custom scriptindicated an unrecoverable error.


ABA259603E The Request type specified is no longersupported.


ABA259604E This operation is no longer supportedon a LotusDominoServer object that hasbeen migrated.


ABA259605E When attempting to contact a remoteserver, the host was unable to be found.

Explanation: Possible solutions to this problem are,make sure the host name in the server document iscorrect, see if you can ping the server and if not, addan entry in the /etc/hosts file for this server.

ABA259606E Cannot open names.nsf to query Namesand Address book.


ABA259209E • ABA259606E


ABA259607E Cannot open a note within the Namesand Address book.

Explanation: Please make sure the names.nsf file isnot corrupt.

ABA259608E This command is already running,unable to run it now.

Explanation: Another process is running the samecommand you are trying to run. This can occurr whenone process is executing a “long running‘ commandand another process attempts to execute the samecommand. Attempt to run the command at a latertime.’”

ABA259614E The maximum number of long termtasks are already running, can’t run thistask now.

Explanation: A percentage of the worker threads inthe Tivoli addin are allocated to run “long term‘ tasks.To see the percentage of the Tivoli addin workerthreads that can run long term tasks, and the numberof worker threads in the Tivoli addin, execute a TELLTIVOLI INFO command from the Domino console. Youcan increase the number of Tivoli addin worker threadsand modify the percentage of worker threads allocatedto run long term tasks by making changes in thenotes.ini file. Refer to the Tivoli Manager for DominoReference Guide for details on how to make thesechanges.’”

You can attempt to run this command at a later time orreload the Tivoli addin with changes to the notes.inifile for worker threads of long term tasks percentage.

ABA260033E Duplicate Real Time Monitors are notallowed.

Explanation: Only a single instance of a specificreal-time monitor can be distributed to a Dominoserver at one time.You attempted to distribute a secondreal-time monitor for the same statistic to this server.Ensure that you have only one unique real-timemonitor for each statistic to distribute to this server.This error can occur if you delete a monitor and thenadd it back. Delete the newly added monitor anddistribute the old monitor, then add the new monitorand distribute it a second time.

ABA260034E Invalid Event Name.

Explanation: The event name is invalid. Ensure thatthe event name is correct and retry the operation.

ABA260035E Invalid Data.

Explanation: An error occurred because the data isinvalid. Retry the operation and contact TivoliCustomer Support if this problem persists.

ABA260036E Couldn’t find useable winsock.dll.

Explanation: An error occurred because the data isinvalid. Retry the operation and contact TivoliCustomer Support if this problem persists.

ABA260037E Could not connect to server on port.

Explanation: An error occurred during an attempt toconnect to the server on the specified port. Ensure thatthe specified port is not in use.

ABA270100I Please select one or more servers.


ABA270102E The {0} event already exists.


ABA270103I Please select an Events4 profile.


ABA270104I Please select a Sentry profile.


ABA270105E A {0} value is required for {1}.


ABA270106E Unable to connect to host.


ABA270107E A database error occurred.


ABA270108E From-date should be To-date.


ABA259607E • ABA270108E


ABA270109I Please select an event for deletion.


ABA270110I Please select a monitor for deletion.


ABA270111E Please select a policy region fordeletion.


ABA270112E The policy region is not empty.


ABA270113I Please select a profile manager fordeletion.


ABA270114I Please select a profile for deletion.


ABA270115E An error occurred deleting the report.


ABA270116E An error occurred communicating withthe server.

Explanation: Verify that the endpoint, Domino server,and DM engine are working properly.

ABA270117I {0}: Targets may be listed only once.


ABA2701118I Please select a monitor for editing.


ABA270119I Please select a profile for editing.


ABA270120E Bad database connection or query.


ABA270121E Failed to distribute profiles.


ABA270122E Failed to distribute profile tosubscribers.


ABA270123E Error retrieving NAB information fromserver {0}.


ABA270124W Initialization timed out.


ABA270125I Incorrect number of arguments for theselected probe.




ABA270127E Invalid date range.


ABA270128E Invalid file name.


ABA270129E Password not valid for the specifieduser.


ABA270109I • ABA270129E


ABA270130I Invalid server {0}.


ABA270131I Invalid station.


ABA270132E Specified user not valid for this host.


ABA270134W An error occurred loading the servertable data.


ABA270135E Message not sent: make sure recipient isvalid and server is running.


ABA270136E Filename required for the attachment.


ABA270137E Please specify a file.


ABA270138E Report name required.


ABA270139I Please select databases.


ABA270140E Please select a monitor.


ABA270141E Please specify a numeric value for acolumn width and returned rows.


ABA270142I Please select a probe.


ABA270143I Please select a profile manager.


ABA270144E Recipient is required.


ABA270145I Please select a report.


ABA270146I No results returned.


ABA270147E Please select a server.


ABA270148I Please select a station.


ABA270149I Station currently does not support anyservers.


ABA270150E Only one instance of the applet isallowed per VM instance.


ABA270152E The specified printer was unable toprint.


ABA270153E Please remove this profile manager’sprofiles and subscribers.


ABA270130I • ABA270153E


ABA270154E Report name already in use.


ABA270155E View still initializing...


ABA270156E Character ’|’ is reserved and may not beused.


ABA270157W Graph names could not be retrievedfrom database.


ABA270158W Report names could not be retrievedfrom database.


ABA270159E Attempt to connect to database failed.


ABA270161E Could not delete from database table.


ABA270162E Could not execute the databasecommand.


ABA270163E The RIM object could not be found.


ABA270164E Could not retrieve data from thedatabase.


ABA270165E Unable to save to this location.


ABA270166E An error occurred saving the report..


ABA270167E The server object is invalid.

Explanation: The server may have been deleted byanother user.

ABA270168E No TEC server found on this TMR.


ABA270169E TEC Operator preferences couldn’t beretrieved from the TEC server.


ABA270170E No Event Groups are assigned to thisOperator’s TEC Console.


ABA270171E TEC Operator Console has not beencreated in the TEC server.


ABA270172E TEC Operator information is not onTEC database.


ABA270173E Current username does not exist in theTEC Server.


ABA270174E Policy region already exists in the TMR.


ABA270154E • ABA270174E


ABA270175E Policy region not found.


ABA270176E Profile manager already exists.


ABA270177E Profile manager not found.


ABA270178E {0} profile type not found.


ABA270179E Profile type not supported.


ABA270180E Unrecoverable error: The TMRconnection is no longer valid.


ABA270182E This field only accepts integer values.


ABA270184I The selected profile manager does nothave any defined properties.


ABA270185E No profile manager selected.


ABA270186I The selected profile manager does nothave any subscribers.


ABA270187E Probe list currently locked by anotheruser.


ABA270189E Report format corrupted in the database.

Explanation: Some settings may be lost.

ABA270190E Could not load the page layout (XML)template.


ABA270191E Could not place report on page.

Explanation: Try adjusting column widths or changingthe page size.

ABA2701092E An internal error occurred.

Explanation: Please try again.

ABA270198I Initialization completed with errors.


ABA270200E One or more source servers isunavailable.


ABA270201E Unable to create TEC Console.


ABA270205E Unable to change port.


ABA270206E Unable to move the server to thespecified policy region.


ABA270208E Could not connect to database.

Explanation: Check privileges and connection.

ABA270210I Improperly formatted date.


ABA270175E • ABA270210I


ABA270211I Improperly formatted date range.


ABA270212I The Sentry profile is currently locked inanother transaction.


ABA270213E An unexpected exception occurred.

Explanation: Please contact Tivoli support.

ABA270214E The specified object is not valid orcould not be resolved.


ABA270215E The policy region for the selectedprofile manager does not manage any ofthe supported profile types.


ABA270216E Could not change logging level to {0}.


ABA270217E Could not change log dir to {0}.


ABA270218W Resource {0} is not managed by policyregion {1}.


ABA270219I Please select a profile.


ABA270220W Policy region was created successfully.However, managed resources could notbe added because of insufficient roles.


ABA270221E To use this console, your roles mustinclude: {0}.


ABA270222E The selected resource model does notexist.


ABA270223I Please specify a rule name.


ABA270224I Please select at least one day.


ABA270225I Please specify a rule to edit.


ABA270226I The schedule rule name already exists.

Explanation: Please specify a different name.

ABA270227I Please specify a rule to delete.


ABA270228I Please select a profile to add theresource model to.


ABA270229E No resource models found.

Explanation: Please make sure ITM is installedcorrectly.

ABA270230I Please select a resource model to edit.


ABA270231I Please select a resource model to delete.


ABA270211I • ABA270231I


ABA270232I The schedule end date must be after theschedule start date.


ABA270233I You must create at least one schedulerule.


ABA270234I The probe id must be greater than 0.


ABA270235I All probe arguments must contain avalue.


ABA270236I The probe was created successfully. Thenew probe id is {0, number,integer}.


ABA270237E Error creating probe.


ABA270238E Error saving changes to the probe. Theprobe may have been deleted in theprocess of saving changes.


ABA270239E Error deleting probe.


ABA270240I The specified probe id already exists.

Explanation: Please specify a different probe id.

ABA270241E Error clearing probes.


ABA270242E Error resetting probes. First erroroccurred on probe id {0, number,integer}


ABA270243E The management console has lost itsconnection to the Tivoli server.

Explanation: Please restart the management console tore-establish the connection.

ABA270244I Log file directory changes will not takeeffect until the management console isrestarted.


ABA270245E Could not obtain resource model lock.

Explanation: Make sure the resource model isnotbeing modified by another user.

ABA270246E Error deleting resource model.


ABA270247E Error modifying resource model.

Explanation: Make sure the resource model is notbeing modified by another user.

ABA270248E The profile {0} already exists.

Explanation: Please specify a different name for theprofile.

ABA2702249E The selected profile manager nolonger exists.

Explanation: Right-click in the profile manager treeand select Refresh to refresh the profile manager list.

ABA270232I • ABA2702249E



Appendix D. Accessibility

Accessibility features help users who have a physical disability, such as restrictedmobility or limited vision, to use software products successfully. The majoraccessibility features in IBM Tivoli Monitoring for Messaging and Collaborationenable you 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 includes the following features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for you to apply screen-reader software.v All images are 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 forMessaging and Collaboration. Consult the assistive technology productdocumentation for specific information about using it to access command-line orgraphical interfaces.

Magnifying what is displayed on the screenIn all components of IBM Tivoli Monitoring for Messaging and Collaboration otherthan the Web Health Console, you can magnify the screens of the product userinterfaces using facilities provided by the operating systems on which the productis run. For example, in a Windows environment you can change the screen settingsto a lower resolution to enlarge the font sizes of the text on the screen. Informationabout these facilities is provided in the relevant operating system 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

Using alternative textAll documentation images are provided with an alternative text that can be readby assistive tools such as screen readers.



Appendix E. 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.


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.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, and Tivoli Enterprise Console aretrademarks or registered trademarks of International Business MachinesCorporation in the United States or other countries, or both.

Lotus and Lotus Notes are trademarks of International Business MachinesCorporation and Lotus Development Corporation in the United States, othercountries, 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.

Other company, product, and service names may be trademarks or service marksof others.

Appendix E. Notices 313


Index

Special characters.nsf files 255.ntf files 255%SystemRoot%\system32\drivers\

etc\Tivoli\setup_env.cmdcommand 22

AABA Messaging and Collaboration Data

Mart 246access

to the IBM console 236access control list (ACL), viewing and

changing 144accessibility xv, 311actions, recovery 16activate a database after a restore 258Activate Databases task 259administrators, Tivoli 2aggregated data 95archive logging 260Archive Transactional Log task 261assign

authorization roles 24assured delivery 107asynchronous delivery 107attributes

definition of 10authorization roles 267

assigning 24assigning of Tivoli Enterprise Data

Warehouse roles 237defined 2for Domino Performance

Stations 150Tivoli Enterprise Data

Warehouse 235

Bback up

databases and template files 254bash shell 212built-in actions

definition 16

Ccentral data warehouse 234Check Database Corruption task 138Check Health task 133Check Inactive Users task 143Check Replication task 141check–point and restart delivery 107circular logging 260classes

import and compile for IBM TivoliMonitoring events 211

classes (continued)import and compile for Tivoli

Enterprise Console 211clearing events

definition of 13command line

user interface options 3, 21commands

%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd 22

ENDTMEEPT 278executing within Domino server

console 130lcf_env.sh 278lcfd.sh 278net start 278net stop 278nsd.kill 117ps 278special characters xviSTRTMEEPT 278syntax xviwadminep 277wcomprules 214wcrtjob 182wcrtpr 27wcrtprf 59wcrtprfmgr 59wdistrib 104, 108wdmcmd 100wdmdistrib 100wdmeditprf 67, 72, 77, 83, 86, 88, 91,

96, 161wdmeng 100, 120, 165wdmlseng 100wdmmn 101wdmtrceng 100wdpsaddprobes 158wdpsaddserver 155wdpsclearprobes 167wdpscreate 154wdpsdelete 163wdpsdeleteprobe 167wdpsintegrity 172wdpsprobeonce 151, 169wdpsprobestatus 170wdpsqueryprobes 158wdpsqueryservers 155wdpsreboot 164wdpsremoveserver 155wdpsresetprobes 168wdpsstart 164wdpsstop 164wgetpr 30wimprbclass 213wimprbrules 213wloadrb 214wlookup 211, 215, 277wlseng 103wping 277wrunjob 187

commands (continued)wruntask 51, 114, 117, 118, 131, 133,

135, 138, 139, 141, 143, 145, 174, 230,255, 257, 259, 261, 263, 264

wsartesvr 214wschedjob 187wsetadmin 24, 33wsetpm 59wsetpr 30wstopesvr 214wsub 65wtmdaclmod 145wtmdactivatedbs 259wtmdarchivetranslog 261wtmdcheckhealth 133wtmdcheckrep 141wtmdchkdbcorruption 138wtmdchkinactusers 143wtmdcreateserver 38wtmddeleteserver 51wtmdgetacl 145wtmdinactivatetranslog 264wtmdincrementalbackup 254wtmdlocateserver 38wtmdmailwaiting 139wtmdqueryactivate 259wtmdquerybackup 255wtmdquerydoc 135wtmdquerylog 135wtmdqueryrestore 257wtmdquerystat 129wtmdquerytranslog 263wtmdrecyclentsvrsvc 117wtmdrecycleserver 118wtmdremoteconsole 131wtmdrestoredbs 257wtmdselectivebackup 254wtmdserveravailable 114wtmdstartengine 219wtmdstartserver 118wtmdstopengine 219wtmdstopserver 118wtmdverifymail 139

configurationservers 36, 45

Configure TEC for Messaging andCollaboration task 214, 231

Configure TEC for TMD task 211configure the Tivoli Enterprise Console

with the Configure TEC for TMDtask 211

connectivitytesting Domino server endpoint 277

control server 233conventions xvicorrupted databases, checking for 137create

IBM console user 237jobs 182policy regions 26


custom scriptsrunning after starting or stopping a

server 116customer support xvcustomization

data logging information of resourcemodels 95

indications of resource models 76,82, 85

parameters of resource models 87schedules of resource models 90

customized tasks 178definition of 173

cyclesdefinition of 10

Ddata

export reports 205view historical 205

data depoting delivery 107data health

obtain for Lotus Domino Servers orDomino Performance Stations 195

data loggingdefinition 15

data marts 234, 240ABA Messaging and Collaboration

Data Mart 246access to 235assign to Tivoli Enterprise Data

Warehouse user groups 239data view

definition of 199save as a GIF 205

database access control list (ACL),viewing and changing 144

database mail filescomparing to the Name and Address

Book (NAB) 139databases

activate after a restore 258apply transaction log files to 258back up 254checking for corruption 137restore 251, 256

dataless profile managersicon 60subscribers 58

DB2 databasecontaining data marts 234containing historical data 234

deletionpolicy regions 29servers 50

displayof the IBM console 236

distributed systemsdefined 10

distributionendpoint rerun 109profiles from the desktop 103profiles using MDist2 107rerun to endpoint 109

Domino Performance Stationendpoints 3

Domino Performance Station ResourceModels

profile managers 149profiles 149

Domino Performance Station Tasks tasklibrary 174

Domino Performance Stationsabout 149, 151authorization roles 150check probe status 170check status of 171configuration 154configuration for probe 158configuration of resource models for

probe monitoring 160delete 163delete probes 166designing an installation 150hardware requirements 152network requirements 152network topology 150number of probes per 153obtain health data for 195performance issues 152quantity needed 152reset probes 167restart 163run the Probe Once function 168schedule probes 153software requirements 152start and stop 163start and stop probes 165

Domino server endpoint problemstroubleshooting 277

Domino server endpointstesting connectivity of 277

Domino Server Tasks task library 174Domino servers

viewing statistics 128Domino tasks, running 121DominoEvens.baroc file 221DominoPerformanceStation managed

resource 30DPSNetEcho probe 151

Ee-mail contact xvedit

resource models 76, 82, 85, 87, 90, 95endpoints

check status 193dataless 58distribution rerun 109IBM Tivoli Monitoring for Messaging

and Collaboration: Lotus Domino 3managing profiles 100managing resource models 100resource models distributed to 101resource models running on 102testing connectivity of 277troubleshooting 277

ENDTMEEPT command 278error messages

Tivoli endpoint wizard 277event classes

definition files 221

event classes (continued)hierarchy 222names 222

event engineevent handling 214

event groupsconfiguring 211create for Tivoli Enterprise

Console 211setup 214

eventscustomizing the Events4Profile for

correlation 216definition of 12forward to Tivoli Business Systems

Manager 230importing and compiling classes for

Tivoli Enterprise Console 211local display 214receive 228respond to 210sending of 14sent to Tivoli Business Systems

Manager 15sent to Tivoli Enterprise Console

server 14sent to Web Health Console 14Tivoli Enterprise Console definition

of 210Tivoli Enterprise Console groups 210Tivoli Enterprise Console

processing 210Tivoli Enterprise Console sources 210view 210, 220

events, clearing 13events4.nsf file 214Events4Profile 216

managed resource 30extract, transform, and load utilities

access from applications 233

Ffeedback about publications xvfiles

.nsf 255

.ntf 255baroc, tecad_tmd.baroc 214DominoEvens.baroc 221events4.nsf 214log.nsf 141notes.ini 38, 50, 115, 132, 155rule, tmd_sa.rls 214searching and viewing log.nsf 134TMD3_srv_tecad.baroc 221Tmw2k.baroc 221

Ggateways

management of 101Gathering Historical Data Warehouse 11Get ACLs task 145guides

feedback xiionline xii


guides (continued)ordering xii

Hhealth data

export 205of endpoints 193print 205resource health 193save 205view settings 198

health of servers, checking 132heartbeat function 11help, online xvhistorical data

access using Tivoli Enterprise DataWarehouse 233

gathering 11view 205

holes 76definition of 12occurrences of 76

IIBM console

access to 236Tivoli Enterprise Data Warehouse

functions available through 236user creation 237

IBM DB2DB2 Server 234Universal Database Enterprise

Edition 234IBM Tivoli Monitoring

about 10gateway management 101overview 55


integrate with Tivoli Business SystemsManager 228

product overview 1receive events 228

IBM Tivoli Monitoring for Messaging andCollaboration: Lotus Dominoinstallation

set up and start of the Tivolienvironment 21

starting the Management Console 23Inactivate Transaction Logging task 264inactive users, listing 143incremental backup 254Incremental Backup task 255indications

definition of 11occurrences of 76sort table data 195

installationprocedures 19

installation of IBM Tivoli Monitoring forMessaging and Collaboration: LotusDomino

setup and start of the Tivolienvironment 21

installation of IBM Tivoli Monitoring forMessaging and Collaboration: LotusDomino (continued)

starting the Management Console 23instances

sort table data 195

Jjobs

about 182creation of 182definition of 173running 186schedule of 187

Kkill scripts for servers 116

Llcf_env.sh command

using to access lcfd Tivoli endpointprocess 278

lcf.sh commandusing to restart lcfd Tivoli endpoint

process 278lcfd, Tivoli endpoint process

stopping with net stopcommand 278

location of servers 36, 45log files

searching and viewing log.nsf 134log files, transaction

apply to a database 258archiving 260inactivating 264viewing archived files 262

log.nsf file 141log.nsf file, searching and viewing 134logging data

aggregated data 95definition 15raw data 95TEDW data 95

Lotus Domino Server endpoints 3Lotus Domino Servers

check status of 113managing 113obtain health data for 195

Lotus Domino tasks, running 121LotusDominoServer managed

resource 30

Mmail database files

comparing to the Name and AddressBook (NAB) 139

mail queue, checking 139Mail Waiting task 139mailbox

mail waiting list 139

managed nodesrun tasks on 174

managed resource types, adding to apolicy region 30

managed resourcesdefined 10

Management Console 193about 194definition of 4server health status categories 195starting 23thermometer icons 195user interface options 3, 21

management server 227manuals

feedback xiionline xiiordering xii

MDist2assured delivery function 107asynchronous delivery function 107check-point and restart function 107data depoting delivery function 107profile distribution 107

messages 271, 279Messaging and Collaboration

Configuration task library 174Messaging and Collaboration notice

group 33Messaging and Collaboration policy

regionMessaging and Collaboration 173

Messaging and Collaboration policyregions 27

Modify Database ACLs task 145monitoring profiles, definition 57monitors

compared to probes 153multithreaded monitoring 153

NName and Address Book (NAB)

comparing to mail database 139verifying replication schedule 141

net start commandusing to start lcfd Tivoli endpoint

process 278net stop command

using to stop lcfd Tivoli endpointprocess 278

network performance, measuring withDomino Performance Stations 151

network problems, detecting withDomino Performance Stations 151

notes.inifile 38

notes.ini file 50, 115, 132, 155notice groups

Messaging and Collaboration 33removal of a subscription 34subscription to 32

nsd.killcommand 117

Index 317

Ooccurrences 76

definition of 12online help xvopening Domino server console 130ordering publications xvoverview

IBM Tivoli Monitoring 55

Pparameters

definition 15partitioned server, configuration 36permissions, changing for a user 144policy regions

about 27adding managed resource types

to 30creation of 26deletion of 29Messaging and Collaboration 27, 173

probe ID 168Probe Once function 168probes

about 149check status of 170, 171cleanup period 154compared to monitors 153configuration for a Domino

Performance Station 158delete 166DPSNetEcho 151execution offset 153monitoring on a Domino Performance

Station 160probe interval 154quantity supported by a Domino

Performance Station 153reset 167run once 168schedule of 153start and stop 165test 168test of servers 150transaction window 153types 153

processes, checking state of 132product overview 1profile endpoints

distribution overview 103profile managers

creating 57creation of 109dataless 58definition of 55distribution overview 103Domino Performance Station Resource

Models 149setup 57subscribing resources 64

ProfileManager managed resource 30profiles

adding custom resource modelsto 71

adding default resource models to 67

profiles (continued)creating 57customizing Events4Profile for local

event correlation 216definition 16definition of 55distribution from the desktop 103distribution using MDist2 107Domino Performance Station Resource

Models 149management at endpoints 100monitoring 57

ps commandusing to identify lcfd Tivoli endpoint

process 278publications

feedback xiionline xiiordering xiiordering of xvviewing online xiv

QQuery Activate task 259Query Backup task 255Query Log task 135Query NAB task 139Query Restore task 257Query Statistics task 129Query Transaction Log task 263queue

mail check 139

Rraw data 95recovery actions, definition 16Recycle NT Server Service task 117Recycle Server task 118Remote Console task 131remove

Tivoli Business Systems Manager 231replication

verifying 141report interface 235reports

access from applications 233create 242create a specific report 243export 205export data 205list of metrics 249listed with available resource

models 249metrics 243modify default settings 241name of 243print 205run using the report interface 240save 205schedule to run automatically 241Tivoli Enterprise Data

Warehouse 240Tivoli Enterprise Data Warehouse, list

of 248, 249

resource health 193resource models

adding to profiles 67, 71customization of data logging

information 95customization of indications 76, 82,

85customization of parameters 87customization of schedules 90definition 16distributed to endpoints 101editing of 76, 82, 85, 87, 90, 95listed with available reports 249management at endpoints 100probe monitoring on a Domino

Performance Station 160running on an endpoint 102setup 56sort table data 195starting and stopping 119stopping during a server

shutdown 120resources

subscription of 64resources, managed

defined 10restore a database 251, 256Restore Databases task 257rule base

copy 211create 211load 211

rule enginestart and stop 218

rulesabout 210scheduling of 16

SScheduler

about 187use to schedule probes 153

schedulingdefinition 16jobs 109probes 153rules 16

scriptssetup_env.csh 22setup_env.sh 22tmdpoststop.cmd 117tmdpoststop.sh 117

selective backup 254Selective Backup task 255server endpoint problems, Domino

troubleshooting 277server endpoints, Domino

testing connectivity of 277server properties

definition 37, 38editing 124

Server service, Windows NT,recycling 117

serversavailability testing with Domino

Performance Stations 151


servers (continued)check status of 113checking health of 132configuration 36, 45configuration of a partitioned

server 36creating in the Tivoli

environment 36, 45deletion from the Tivoli

environment 50discovering and configuring all

servers in a domain 45display data 196filter data 197icons showing status in Management

Console 115location 36, 45measuring performance with Domino

Performance Stations 151partitioned 36probes 150recycling 115sort or filter data 195starting and stopping 115status icons 114stopping resource models during a

server shutdown 120verifying replication 141viewing properties 123viewing statistics for 128

setupIBM Tivoli Monitoring for Messaging

and Collaboration: LotusDomino 21

procedures 19resource models 56

setup_env.csh script 22setup_env.sh script 22shell

bash 212softcopy publications xivstandard tasks 174star schemas

Tivoli Enterprise Data Warehouse, listof 246

Start Engine task 219Start Server task 118Start TEC Engine task 219stations

display data 196filter data 197sort or filter data 195

statistics, viewing 128Stop Engine task 219Stop Server task 118Stop TEC Engine task 219STRTMEEPT command 278subscription

resources 64

Ttask libraries

customization of tasks 178Domino Performance Station

Tasks 174Domino Server Tasks 174

task libraries (continued)Messaging and Collaboration

Configuration 174stored in the Messaging and

Collaboration policy region 173Task server 228TaskLibrary managed resource 30tasks

about 174Activate Databases 259Archive Transactional Log 261Check Database Corruption 138Check Health 133Check Inactive Users 143Check Replication 141Configure TEC for Messaging and

Collaboration 214, 231Configure TEC for TMD 211customization 178customized 173definition of 173Domino 174Get ACLs 145Inactivate Transaction Logging 264Incremental Backup 255Mail Waiting 139Modify Database ACLs 145Query Activate 259Query Backup 255Query Log 135Query NAB 139Query Restore 257Query Statistics 129Query Transaction Log 263Recycle NT Server Service 117Recycle Server 118Remote Console 131Restore Databases 257run 174running Domino tasks 121Selective Backup 255standard 174Start Engine 219Start Server 118Start TEC Engine 219Stop Engine 219Stop Server 118Stop TEC Engine 219Tivoli Management Framework 16troubleshooting 271Verify Mail 139

tecad_tmd.baroc filerule, tmd_sa.rls 214

TEDW data 95template files, back up 254thresholds

definition 17Tivoli administrators 2Tivoli Business Systems Manager

about 227components of 227defining IBM Tivoli Monitoring for

Messaging and Collaboration: LotusDomino objects to 229

discovering resources for 229events sent to 14, 15forward events to 230

Tivoli Business Systems Manager(continued)

integrate with IBM Tivoli Monitoringfor Messaging and Collaboration:Lotus Domino 228

management server 227prerequisites 228remove 231Task server 228Tivoli Event Enablement 228uninstall 231workstation 228

Tivoli Customer Support xvTivoli Data Protection

archive logging 260circular logging 260functions not supported by IBM Tivoli

Monitoring for Messaging andCollaboration 251

installation requirements 251overview 251server properties 37

Tivoli desktopuser interface options 3, 21

Tivoli endpointwizard

error messages 277Tivoli Enterprise Console

classes, importing and compiling 211configure event groups 211console 210copy rule base 211create rule base 211customizing the Events4Profile for

local event correlation 216definition files 221event class names 222event classes 221event classes hierarchy 222event groups definition 210event processing 210event viewing 210events and sources 210events definition 210events sent to 14importing and compiling classes for

events 211load rule base 211overview 209respond to events 210rule engine, start and stop 218rules overview 210use the Configure TEC for TMD

task 211view events 220

Tivoli Enterprise Data Warehouse 11assign user groups to data marts 239assign users to user groups 238assigning authorization roles 237authorization roles 235capabilities 233central data warehouse 234components 233control server 233create a specific report 243create reports 242data marts 234, 235

Index 319

Tivoli Enterprise Data Warehouse(continued)

functions available through the IBMconsole 236

list of reports 248, 249list of reports metrics 249list of star schemas 246modify report’s default settings 241overview 233report interface 235report metrics 243report names 243reports 240reports listed with available resource

models 249run reports 240schedule reports to run

automatically 241user group creation 238user groups 235users 235

Tivoli Event Enablement 228Tivoli Management Framework

tasks, definition 16Tivoli management region

event server reports 215Tivoli Storage Manager server 251tmd_sa.rls file 214TMD3_svr_tecad.baroc file 221tmdpoststop.cmd

script 117tmdpoststop.sh

script 117Tmw2k.baroc file 221Tmw2kProfile managed resource 30transaction log files

about 260apply to a database 258archiving 260inactivating 264viewing archived files 262

transaction logging methods (archive vs.circular) 260

troubleshooting 271endpoint problems 277

TWHAdmin user group 235

Uuninstall

Tivoli Business Systems Manager 231user groups

assign Tivoli Enterprise DataWarehouse data marts 239

assign Tivoli Enterprise DataWarehouse users to 238

create 238data mart access 235TWHAdmin 235

user interface optionscommand line 3, 21Management Console 3, 21Tivoli desktop 3, 21Web Health Console 3

user interfacesManagement Console 193Web Health Console 193

usersassign Tivoli Enterprise Data

Warehouse authorization roles 237assign to Tivoli Enterprise Data

Warehouse user groups 238change permissions for 144create and delete 144IBM console 237inactive list 143

VVerify Mail task 139

Wwadminep command

using to test connectivity 277wcomprules command 214wcrtjob command 182wcrtpr command 27wcrtprf command 59wcrtprfmgr command 59wdistrib command 104, 108wdmcmd commands 100wdmdistrib commands 100wdmeditprf command 67, 72, 77, 83, 86,

88, 91, 96, 161wdmeng command 120, 165wdmeng commands 100wdmlseng commands 100wdmmn command 101wdmtrceng commands 100wdpsaddprobes command 158wdpsaddserver command 155wdpsclearprobes command 167wdpscreate command 154wdpsdelete command 163wdpsdeleteprobe command 167wdpsintegrity command 172wdpsprobeonce command 151, 169wdpsprobestatus command 170wdpsqueryprobes command 158wdpsqueryservers command 155wdpsreboot command 164wdpsremoveserver command 155wdpsresetprobes command 168wdpsstart command 164wdpsstop command 164Web Health Console 193

connect to 194events sent to 14user interface options 3

wgetpr command 30wimprbclass command 213wimprbrules command 213Windows NT Server Service

recycling 117wizard, Tivoli endpoint

error messages 277wloadrb command 214wlookup command 211, 215

using to test connectivity 277wlseng command 103workstation 228

wping commandusing to test connectivity 277

wrunjob command 187wruntask command 51, 114, 117, 118,

131, 133, 135, 138, 139, 141, 143, 145,174, 230, 255, 257, 259, 261, 263, 264

wschedjob command 187wsetadmin command 24, 33wsetpm command 59wsetpr command 30wstartesvr command 214wstopesvr command 214wsub command 65wtmdaclmod command 145wtmdactivatedbs command 259wtmdarchivetranslog command 261wtmdcheckhealth command 133wtmdcheckrep command 141wtmdchkdbcorruption command 138wtmdchkinactusers command 143wtmdcreateserver command 38wtmddeleteserver command 51wtmdgetacl command 145wtmdinactivatetranslog command 264wtmdincrementalbackup command 254wtmdlocateserver command 38wtmdmailwaiting command 139wtmdqueryactivate command 259wtmdquerybackup command 255wtmdquerydoc command 135wtmdquerylog command 135wtmdqueryrestore command 257wtmdquerystat command 129wtmdquerytranslog command 263wtmdrecyclentsvrsvc command 117wtmdrecycleserver command 118wtmdremoteconsole command 131wtmdrestoredbs command 257wtmdselectivebackup command 254wtmdserveravailable command 114wtmdstartengine command 219wtmdstartserver command 118wtmdstopengine command 219wtmdstopserver command 118wtmdverifymail command 139


��

Printed in U.S.A.

SC32-0841-00

Documents

IBM Tivoli Monitoring for Messaging and Collaboration ...publib.boulder.ibm.com/tividd/td/ITMMC/SC32-0841-00/en_US/PDF/S… · Chapter 8. Working with health data 191 Understanding