Using Tivoli Decision Support for Lotus Dominopublib.boulder.ibm.com/tividd/td/Domino/GC32-0674... · Using Tivoli Decision Support for Lotus Domino Version 310.. GC32-0674-00

Using Tivoli Decision Support forLotus DominoVersion 3.1.0 GC32-0674-00

Using Tivoli Decision Support forLotus DominoVersion 3.1.0 GC32-0674-00

Using Tivoli Decision Support for Lotus Domino

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems SoftwareLicense Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer orLicense Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic,optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grantsyou limited permission to make hardcopy or other reproductions of any machine-readable documentation for your ownuse, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights undercopyright are granted without prior written permission of IBM Corporation. The document is not intended forproduction and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, DB2, and Tivoli Manager for Domino are trademarks or registeredtrademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries,or both.

Lotus and Lotus Notes are registered trademarks of Lotus Development Corporation. Domino is a trademark of LotusDevelopment Corporation.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will beavailable in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subjectto valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalentproduct, program, or service can be used instead of the referenced product, program, or service. The evaluation andverification of operation in conjunction with other products, except those expressly designated by Tivoli Systems orIBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applicationscovering subject matter in this document. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North CastleDrive, Armonk, New York 10504-1785, U.S.A.

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Using the Guide Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Domino Discovery Guide Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Tivoli Decision Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Tivoli Discovery Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The Rollup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Tivoli Discovery Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Tivoli Task Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Discovery Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Drill-down Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Topics and Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Topic: How are the Domino servers performing? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Topic: How busy are the Domino servers? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Topic: What servers currently need the most attention? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Topic: When and where are server problems occurring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Topic: When might servers begin experiencing problems? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

View Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Setup Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 3. Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Creating ODBC Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Defining the Data Sources for the ODBC Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

iiiUsing Tivoli Decision Support for Lotus Domino

Specifying the Path for Shared Source Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Importing the Domino Discovery Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Assigning a Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Setting the Date Range Parameter for a Cube. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Updating the SQL Query Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Building Cubes Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Scheduling Automatic Cube Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Uninstalling the Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 4. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Troubleshooting Cube Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Viewing Log Files after a Cube Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

“Error Building Cube” Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

“Cannot Execute” Message (Cognos PowerPlay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

“load_graph_from_powercube” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

“Cube Cannot Be Built” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Cubes Fail to Build Overnight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Troubleshooting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Report Contains No Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Some Values Look Incorrect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

No Data for Certain Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 5. Product Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Domino Rollup Tool Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Cubes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Domino Monitors Cube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Domino Trend Cube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 6. Report Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 7. Defects, Limitations, and Workarounds . . . . . . . . . . . . . . . . . . . . . . 41Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Appendix A. Technical Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

iv Version 3.1.0

Domino Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Sybase Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Query Statements and Calculated Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Functions for Calculated Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Domino.DLL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

TMD30IncrementValue Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

TMD30PredictionValue Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

vUsing Tivoli Decision Support for Lotus Domino

vi Version 3.1.0

Preface

Using Tivoli Decision Support for Lotus Domino describes Tivoli® Decision Support™ forLotus® Domino™, Version 3.1.0, and explains how to install, import, and configure theproduct. This product belongs to the family of Tivoli Decision Support Discovery Guides.This document refers to the Tivoli Decision Support Discovery Guide as the DominoDiscovery Guide. The Domino Discovery Guide works with Tivoli Manager for Domino,Version 3.1.0, to provide reports that give Lotus Domino administrators and Tivoli systemadministrators valuable information about the behavior and performance of their Dominoenvironment.

Who Should Read This GuideThe target audience for this book is Lotus Domino administrators who are responsible forinstalling Tivoli Decision Support for Lotus Domino and for making information technologydecisions for the Domino environment. Readers of this book should have a knowledge ofMicrosoft® Windows NT® and the Tivoli environment.

Related DocumentsRefer to the following Tivoli Decision Support, Version 2.1.1, documentation when installingand using the Domino Discovery Guide.

Table 1. Related DocumentsPublication Description Location

Tivoli Decision SupportInstallation Guide

Describes installing TivoliDecision Support and itscomponents in stand-alone andnetwork modes.

<TDS Installation Directory>\Docs\Pdf\install.pdf

Tivoli Decision SupportUser’s Guide

Describes Tivoli Decision Supportfeatures, concepts, and proceduresfor using the Tivoli DiscoveryInterface.

<TDS Installation Directory>\Docs\Pdf\user-gd.pdf

Tivoli Decision SupportAdministrator Guide

Explains the features of the TivoliDiscovery Administrator.

<TDS Installation Directory>\Docs\Pdf\admin-gd.pdf

What This Guide ContainsThis guide contains the following sections:

¶ Chapter 1, Product Overview

Describes how the Domino Discovery Guide augments the functions of Tivoli Managerfor Domino, Version 3.1.0, to assist you in strategically managing your enterprisenetwork.

¶ Chapter 2, Setup Guidelines

Summarizes the tasks you must perform to install and use the Domino Discovery Guide.

¶ Chapter 3, Installation and Configuration

Describes how to install and configure the Domino Discovery Guide and how to buildand verify cubes.

viiUsing Tivoli Decision Support for Lotus Domino

¶ Chapter 4, Troubleshooting

Describes how to troubleshoot cube builds and reports.

¶ Chapter 5, Product Details

Provides reference information for Tivoli Decision Support users.

¶ Chapter 6, Report Definitions

Describes the reports available from the Tivoli Discovery Interface for each viewprovided by the Domino Discovery Guide.

¶ Chapter 7, Defects, Limitations, and Workarounds

Describes known problems with the software and provides workarounds, when available.

¶ Appendix A, Technical Reference

Provides reference information for Tivoli or Domino database planners who areresponsible for designing and implementing a Tivoli Decision Support for Lotus Dominoinstallation.

¶ Appendix B, Domino.DLL File

Provides a detailed description of the functions used in the Domino.DLL file.

Conventions Used in This GuideThis guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Bold Commands, keywords, file names, authorization roles, URLs, or otherinformation that you must use literally appear like this, in bold. Names ofwindows, dialogs, and other controls also appear like this, in bold.

Italics Variables and values that you must provide appear like this, in italics. Wordsand phrases that are emphasized also appear like this, in italics.

Monospace Code examples, output, and system messages appear like this, in amonospace font.

Using the Guide OnlineThis document is available in the following formats for viewing online:

¶ An Adobe Acrobat (.pdf) file in the doc directory of the installation CD for the product.Use the Adobe Acrobat Reader, Version 3.0 or later, to view and print the manual. Youcan use the ar405eng.exe executable in the extras directory of the Tivoli Manager forDomino installation CD to install Version 4.0 of the reader.

¶ A set of .html files in the doc directory of the installation CD for the product. You canuse any Web browser to view and print these files.

Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide tosupport services (the Customer Support Handbook); frequently asked questions (FAQs); andtechnical information, including release notes, user’s guides, redbooks, and white papers.You can access Tivoli publications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.

viii Version 3.1.0

To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to http://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” for more information aboutobtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of thefollowing telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.

Contacting Customer SupportThe Tivoli Customer Support Handbook at http://www.tivoli.com/support/handbook/provides information about all aspects of Tivoli Customer Support, including the following:

¶ Registration and eligibility.

¶ How to contact support, depending on the severity of your problem.

¶ Telephone numbers and e-mail addresses, depending on the country you are in.

¶ What information you should gather before contacting support.

ixUsing Tivoli Decision Support for Lotus Domino

x Version 3.1.0

Product Overview

Tivoli Decision Support for Lotus Domino works with the Tivoli Discovery Interface and theTivoli Discovery Administrator of Tivoli Decision Support to provide information that aidsthe Domino or Tivoli system administrator in analyzing and making decisions about Dominoinstallations. This product (and similar Tivoli products for other applications) is referred toas a discovery guide. Specifically, this product is referred to as the Domino DiscoveryGuide. Tivoli Decision Support, the tool for customer reporting, uses the Domino DiscoveryGuide to organize and group topics around similar concepts to enable Lotus Domino serveradministrators to immediately view and analyze data.

The Domino Discovery Guide augments the functions of Tivoli Manager for Domino,Version 3.1.0, to assist you in strategically managing your enterprise network. Where TivoliManager for Domino provides a rule-based management application for Dominoinstallations, the Domino Discovery Guide provides the Information Technology (IT)manager of a business enterprise with an overview of how systems are running.

Domino Discovery Guide DescriptionThe Domino Discovery Guide reorganizes and displays data collected from Domino serversinto reports that help you make decisions about your Domino environment. The content anddetail of the reports depend on the type of data collected and the database schema where thisdata is stored. In a Tivoli management region environment, Tivoli Distributed Monitoringmonitors are defined and distributed to Lotus Domino server objects to collect data. The datafrom these monitors is stored in a relational database management system (RDBMS). Whenthis data becomes part of the relational database, the Domino Discovery Guide extracts andanalyzes the data through reports viewed in the Tivoli Discovery Interface.

Tivoli Decision SupportTivoli Decision Support is decision-support software that aids in analysis anddecision-making in an organization. It contains prepackaged information in the form of anintuitive topic map and a discovery guide.

Tivoli Decision Support collects data from your data sources and transforms it intomultidimensional extracts called cubes. Using Tivoli Decision Support to extract data fromthe RDBMS, you build information into cubes. These cubes contain information that enablesusers to drill down data to view generalized or detailed data. Drilling down is thehierarchical method of viewing data in a table where each viewing level is a subset of theprevious level. Tivoli Decision Support is integrated with Cognos PowerPlay to providesnapshot-style views of data. You can view the data in any of the following formats:

¶ Text

¶ Bar charts

1

1Using Tivoli Decision Support for Lotus Domino

1.P

rod

uct

Overview

¶ Line charts

¶ Other graphical formats

The default format depends on the type of data you view. You can also select differentformats for some types of views. Multidimensional views enable you to do the following:

¶ Analyze data from different perspectives

¶ Compare current activities to historical records

¶ Detect trends

¶ Evaluate resource allocation

¶ Forecast and make projections

¶ Perform other management tasks

For more information, see the Tivoli Decision Support User’s Guide.

Tivoli Discovery InterfaceThe Tivoli Discovery Interface is the user interface for Tivoli Decision Support. It is thecomponent that is installed on end-users’ workstations to help them find specific informationabout their organizations.

Tivoli Decision Support preformats all views prior to displaying them. The following twoviews are available in the Tivoli Discovery Interface:

¶ Detailed reports, which are always formatted to display in a Seagate Crystal Reportstemplate.

¶ Multidimensional views, which are always formatted to display in a PowerPlay template.

You do not need to create any templates or format any data.

Detailed ReportsTivoli Decision Support uses Crystal Reports to collect and summarize tabular (text-only)reports. Instead of building static cubes, Crystal Reports uses live data extracted from thedatabase upon request. Because it might not be convenient to access the database at alltimes, Tivoli Decision Support stores a static version of Crystal Reports in a MicrosoftAccess database.

Multidimensional ViewsTivoli Decision Support presents graphical data by extracting information stored in cubes.Data collected from your data source is used to transform Cognos Model files intomultidimensional cubes. This predesigned model is supplied with the Domino DiscoveryGuide.

The Rollup ToolThe Domino Discovery Guide relies on Tivoli Manager for Domino to roll up data into arelational database. Tivoli Manager for Domino, Version 3.1.0, contains its own RDBMS anda built-in rollup tool. The Domino Discovery Guide does not require installation of anadditional rollup tool.

The Tivoli Manager for Domino rollup tool provides scripts to create the database schemaand the RDBMS Interface Module (RIM) object, and to install the default Domino monitors

2 Version 3.1.0

necessary for the Domino Discovery Guide. The rollup tool then distributes the monitors inthe Tivoli environment, and the Domino Discovery Guide runs the rollup nightly to collectand aggregate the data into the database table.

Tivoli Discovery AdministratorThe Tivoli Discovery Administrator is the Tivoli Decision Support component that connectsto the database. When you issue a request for information in the Tivoli Discovery Interface,Tivoli Decision Support reads the information directly from the database or from a cube filecreated by the Tivoli Discovery Administrator. A cube is a special data structure populatedwith data from your database. The Tivoli Discovery Administrator defines queries thatextract data from the database table and creates a file of delimited columns of text, alsoreferred to as a comma-separated-variables (.csv) file. The Cognos Transformer builds amultidimensional cube from this .csv file, which Cognos PowerPlay can use to creategraphs. Finally, when the guides and roles have been defined, use the Tivoli DiscoveryInterface to view these reports.

Cognos TransformerThe Tivoli Discovery Administrator exports data from the database and calls the CognosTransformer to transform the data into a data structure called a cube. Cubes are Cognostemplates or model files before your database populates them with data.

RoverAfter the Cognos Transformer runs, the Tivoli Discovery Administrator calls Rover to movethe cube from a temporary directory to its permanent location on a local or networkdirectory.

Tivoli Task ServerThe Tivoli Task Server is a scheduler program that enables you to run cube builds andpublish views to a local or network directory automatically. The Tivoli Task Server programalso serves as a central location for viewing the status of scheduled tasks.

Discovery PublisherThe Tivoli Discovery Interface enables you to configure Tivoli Decision Support to publishviews to a local or network drive.

Drill-down DatabaseA drill-down database minimizes traffic to your database. You can generate reports fromyour real-time database or, when this is not feasible, from a static Microsoft Access databasefile.

Topics and ViewsOn the Tivoli Discovery Interface, the database data collected for the Domino DiscoveryGuide is organized into topics and views in the topic map. A topic is a subcategory of datain the topic map. Within the Domino Discovery Guide, data is categorized into relatedtopics. Within a topic, you can choose a view that provides a unique set of data created froma special database query. Use the topics and views to help you do the following:

¶ View the performance of the Domino servers

¶ Determine how much work the servers are performing

¶ Rank the servers by several metrics

¶ Determine when and where server problems are occurring


1.P

rod

uct

Overview

¶ Forecast when server problems can occur

Select a view within a topic to view a report displaying the results of a database query basedon the topic and view selected. This section lists the Domino Discovery Guide topics andviews.

Topic: How are the Domino servers performing?Views in this topic display basic Domino server performance statistics.

Calendar and Scheduling StatisticsThis view displays calendar and scheduling statistics for the Domino servers and dailyaverage values for each of the last seven days. Toggle the layers to see different calendarstatistics.

Cluster StatusThis view displays the calculated percentage of time a server cluster is available. Thisinformation is calculated from the Cluster Availability Status monitor. It displays thehourly and daily average percentage values for the last day. To view this statistic for aspecific server, drill down on the server name in the legend of the report.

Disk Space StatisticsThis view displays the amount of free disk space and the amount of disk space of theDomino server program and data drive. The average value for the last 30 days is displayedfor each server.

Because the Lotus Notes® installation can exist on any system drive, the disk spacepercentage free calculation is supported for monitors with the following format:

Disk.X.Free, Disk.X.Size , where X = /, Vol0, Vol1, Vol2, Vol3 or any letter (A–Z)

Mail Average StatisticsThis view displays the mail average statistics with all the servers grouped by the domain towhich they belong. The average daily message count for the mail average statistics isdisplayed for the last day. Tivoli Decision Support supports statistics for all the Mail andMTA monitors within this view, except for those that are supported only in the Mail TotalStatistics view.

To view these statistics for servers within a specific domain, double-click the domain namein the column. To view statistics for each mail average monitor, toggle the layer of thereport. These mail statistics reflect their original server values.

Mail Total StatisticsThis view displays the mail total statistics for each domain. The total number of messages isdisplayed for each mail statistic for each of the last thirty days. The following mail statisticsare supported:

¶ MAIL.TotalRouted

¶ MAIL.TotalFailures

¶ MAIL.TotalKBTransferred

¶ MAIL.TransferedFailures

¶ MAIL.Transferred

¶ MTA.Smtp.TotalKBTransferred

4 Version 3.1.0

¶ MTA.Smtp.TotalRouted

¶ MTA.Smtp.TransferredFailures

¶ MTA.Smtp.Transferred

To see the statistics for a specific server, double-click the server’s domain name. Toggle thelayers to view a specific calculated mail monitor.

Notes Database SizeThis view displays the size of Lotus Notes databases for which file size monitors have beencreated. The daily average value in megabytes is displayed for each of the last thirty days.Toggle the layer to view the database size values for each server. To display statistics for aspecific database, double-click that database at the bottom of the graph.

QOS.Mail.ISPYThis view displays the TCP/IP probe response time, in seconds, for all QOS monitors. Thedaily average percentage is displayed for each of the last seven days. To display statisticsonly for a specific server, double-click the server name in the column of the report.

Replication Statistics for the Last 24 HoursThis view displays the number of server replication failures and successes, and documentsadded, deleted, and updated, for each domain in the last 24 hours. Drill down into thedomain to select specific servers.

Replication Statistics for the Last 7 DaysThis view shows the number of server replication failures, successes, documents added,deleted, and updated for each of the last 7 days. Drill down into the domains to selectspecific servers.

Server AvailabilityThis view displays the calculated percentage of time the Domino servers are available. Thispercentage is calculated from the Server Availability monitor. The daily average percentageis displayed for each of the last seven days. To display statistics for a specific server,double-click the server name in the column of the report. The summary row reports eachserver’s average for the last seven-day period, and the summary column reports each day’saverage for all servers.

Server Health StatusThis view shows the calculated percentage of time the Domino addin tasks are available.This percentage is calculated from the Server Health monitor. The daily average is shownfor each task for the last 7 days.

Topic: How busy are the Domino servers?Views in this topic display statistics that reflect the load on Domino servers.

CPU UtilizationThis view shows how the system’s CPU percent busy value is affected by the Dominoservers. The hourly and daily average percentage values are shown for the last day. To viewthis statistic for a specific server, drill down on the domain at the bottom of the graph. Thispercentage represents the value from the Percent Total Processor Time monitor from theUNIX and NT monitoring collection.


1.P

rod

uct

Overview

Domino Network TrafficThis view displays how much network traffic is handled by the Domino servers, includingthe number of incoming, outgoing, and recycled network sessions. The report containsstatistics for any port name for which monitors have been created. The daily total values inbytes are displayed for each of the last seven days. To display statistics for different servers,toggle the layer of the report.

HTTP RequestsThis view displays the number of HTTP requests from the Domino web servers. The totalnumber of requests for each day of the week is displayed for the last seven days.

Memory UsageThis view contains data about the memory usage of the Domino servers, including thestatistics for the Mem.Allocated and Mem.Free monitors. The daily average value inmegabytes is displayed for each of the last 30 days. Toggle the layers of the report todisplay statistics for each server.

Server UsageThis view displays the number of Lotus Notes users, transactions per minute, transactionsper minute peak, total transactions, sessions dropped, and any server cluster statistics. Thehourly and daily averages for the Domino servers are displayed for the last day. For theServer.Trans.Total monitors, the hourly and daily total values are displayed for the last day.Toggle the layers of the report to display statistics for each monitor.

Topic: What servers currently need the most attention?This topic contains ranked views. That is, these views display how servers rank with otherservers against specific metrics. The ranked reports in this topic include available disk space,CPU use, database usage, HTTP requests, memory allocated, server availability, total mailrouted, and mail user statistics. For each of the ranked reports, only the top and bottom 25servers are displayed. To change the number of servers ranked for the PowerPlay report,right-click the view and select Properties. From the Ranking tab, change the number in thedisplayed Top/Bottom section.

25 Least Used DatabasesThis view displays the 25 least-used databases for all servers in a 30-day period. Thedatabases are compared based on the minimum daily usage. To view a particular server,double-click the server in the legend.

25 Most Used DatabasesThis view shows the 25 most-used databases for all servers in the last seven days. Thedatabases are compared based on the average daily usage. To view a particular server,double-click on the server in the legend.

Bottom 25 Servers by Available Disk SpaceThis view shows the 25 servers with the least average amount of free disk space in the lastseven days. Toggle through the layers to view statistics for different partitions.

Bottom 25 Servers by Server AvailabilityThis view ranks the servers by the server availability value from the average of the lastseven days. This report displays only the 25 servers with the lowest percentage values ofserver availability. In addition to the seven-day average value displayed in the summary row,the daily averages for each of the last seven days are displayed for each server.

6 Version 3.1.0

Top 25 Mail Users by Mail File SizeThis view displays the top 25 mail users on all servers for the last seven days. The rankingis obtained by a comparison with the average mail file size of users. To view statistics on aspecific server, toggle the layers of the report.

Top 25 Mail Users by Mail TrafficThis view displays the top 25 mail users on all servers for the last seven days. The rankingis obtained by a comparison with total mail traffic of users. To view statistics on a specificserver, toggle the layers of the report.

Top 25 Servers by CPU UtilizationThis view ranks the Domino servers by the CPU percent busy value from the last seven-dayaverage. This report displays the 25 servers with the highest values for CPU percent busy.

Top 25 Servers by HTTP RequestsThis view ranks the servers by the number of HTTP requests from the last seven-day total.This report displays the 25 servers with the highest number of HTTP requests.

Top 25 Servers by Memory AllocatedThis view ranks the servers by the amount of memory allocated. It compares the dailyaverage memory for the last seven days.

Top 25 Servers by Total Mail RoutedThis view ranks the servers by the amount of total mail routed from the daily total in thelast seven days. This report displays the 25 servers with the highest amounts of total mailrouted.

User Mail File and QuotaThis view contains a report that compares user mail file sizes with their correspondingquotas. It reports the monitor values from the UserMail.Statistics.Sync/Async monitors forthe mail size and size limit.

Topic: When and where are server problems occurring?The views in this topic use several different dimensions and measures to display statisticsthat help determine when and where server problems occur.

Domino Statistics by DayThis view displays all server statistics for the last 30 days. This is a good starting point tolook for daily trends to find specific server problems. The daily average values are displayedfor each of the last 30 days.

To view statistics for a specific server, double-click the server name at the bottom of thegraph. To view statistics for a specific monitor, toggle the layers. To view daily statistics foranother time period, select the By Date dimension and drill down into the appropriate daterange.

Domino Statistics by WeekdaysThis view displays all server statistics by day of the week. This is a good starting point tolook for trends occurring on specific days of the week to find server problems. The dailyaverage values are displayed for the last seven days.

To view statistics for a specific server, double-click the domain at the bottom. Toggle thelayers to view statistics for a specific monitor.


1.P

rod

uct

Overview

To view statistics by business days or weekends, select the By Day of Week dimension anddrill down into the WEEKDAY_OR_WEEKEND category.

Domino Statistics in Business HoursThis view displays all server statistics in business hours. This is a good starting point to lookfor hourly trends to find specific server problems.

Toggle the layers to view specific monitors.

Domino Statistics by ServerThis view displays all statistics for all servers by the last day period. Use this view todetermine server trends. The daily average values are displayed for the last day. Change themeasure to view the daily maximum, minimum, or total for each monitor.

Double-click each monitor type in the row to drill down to a specific monitor. To viewstatistics for a specific server, double-click the server in the column.

Domino Statistics by Server RolesThis view displays all monitor statistics for all server roles by the last day period. Use thisview to determine trends by role. The daily average values are displayed for the last day.

To view statistics for a specific group of servers, double-click the role name. To viewstatistics for a specific monitor, toggle the layers.

Topic: When might servers begin experiencing problems?The view in this topic forecasts server behavior. The forecast includes averages and peaksfor the next day, 15 days later, and 30 days later for different metrics.

Server Forecasted AveragesThis view displays all monitor forecasts for the Domino servers. The trend is displayed withdata points at the next day, 15 days later, and 30 days later.

To select a specific server, click on the legend. You can filter by server properties to sort bydomain, operating system, cluster, server roles, or release. To select trends for differentmonitor arguments, drill down from all monitors.

View PropertiesEach view has a View Properties dialog box that includes the settings and properties of theview. From this dialog box, you can view and edit the settings. To open the view dialog box,use the following steps:

1. From the Tivoli Discovery Interface Topic Map pane, select a Topic.

2. Right-click a View. A drop-down list is displayed.

3. Select Properties. The View Properties dialog box is displayed.

For more information, see the Tivoli Decision Support User’s Guide.

8 Version 3.1.0

Setup Guidelines

Table 2 summarizes the tasks you must perform to install and configure the DominoDiscovery Guide.

Table 2. Setup TasksTask Refer to

Ensure that your system meets the hardware and softwarerequirements for installing the Domino Discovery Guide.

“System Requirements” on page 11

Ensure that your database is supported by the DominoDiscovery Guide.

“Database Requirements” on page 12

Ensure that your system has a valid configuration for theObject Database Connection (ODBC) that Tivoli DecisionSupport uses to access your database.

Consult your database administrator for the appropriateclient ODBC

Install Tivoli Decision Support. Tivoli Decision Support Installation Guide

Install Cognos PowerPlay. Tivoli Decision Support Installation Guide

Create ODBC drivers, which are used to connect to thedatabase.

“Creating ODBC Drivers” on page 12

Set up the ODBC data source. “Defining the Data Sources for the ODBC Drivers” onpage 13

Specify the location of shared source files on a networkserver (not necessary if you are running in stand-alonemode).

“Specifying the Path for Shared Source Files” on page 14

Install the Domino Discovery Guide “Installing the Domino Discovery Guide” on page 15

Import the Domino Discovery Guide “Importing the Domino Discovery Guide” on page 16

Assign and verify a data source “Assigning a Data Source” on page 17

Set the Date Range parameter for a cube “Setting the Date Range Parameter for a Cube” on page18

Update the SQL query statement for the Domino Monitorscube. The SQL statement differs depending on the type ofdatabase that you are using as the data source.

“Updating the SQL Query Statement” on page 19

Build the cube “Building Cubes Manually” on page 20 (required for thefirst cube build)

—OR—

“Scheduling Automatic Cube Builds” on page 21

2


2.S

etup

Gu

idelin

es

10 Version 3.1.0

Installation and Configuration

This chapter describes how to install and configure the Domino Discovery Guide. It coversthe following topics:

¶ “System Requirements” on page 11

¶ “Database Requirements” on page 12

¶ “Creating ODBC Drivers” on page 12

¶ “Defining the Data Sources for the ODBC Drivers” on page 13

¶ “Specifying the Path for Shared Source Files” on page 14

¶ “Installing the Domino Discovery Guide” on page 15

¶ “Importing the Domino Discovery Guide” on page 16

¶ “Assigning a Data Source” on page 17

¶ “Setting the Date Range Parameter for a Cube” on page 18

¶ “Updating the SQL Query Statement” on page 19

¶ “Building Cubes Manually” on page 20

¶ “Scheduling Automatic Cube Builds” on page 21

¶ “Uninstalling the Domino Discovery Guide” on page 22

Note: Authorization roles are not required to perform the procedures listed in this chapter.

System RequirementsThis section describes the software and hardware requirements for installing the DominoDiscovery Guide.

Software RequirementsThe Domino Discovery Guide, Version 3.1.0, works with Tivoli Decision Support for LotusDomino, Version 2.1.1. The following software must be installed on your system:

¶ Microsoft Windows NT 4.0 (service packs 4 and 5)

¶ Tivoli Decision Support, Version 2.1.1

¶ Open database connectivity (ODBC) drivers provided with your relational databasemanagement system (RDBMS) database client installation

If you are an administrator for the Domino Discovery Guide, you need the followingadditional components:

3


3.In

stallation

and

Co

nfig

uratio

n

¶ Tivoli Discovery Interface

¶ Tivoli Discovery Administrator

¶ Cognos PowerPlay

¶ Crystal Reports (required only when you create new reports)

¶ Microsoft Access (recommended, although not required, to run Tivoli Decision Support)

If you are a Crystal Reports user, you need the following additional components:


¶ Crystal Reports (required only when you create new reports)

If you are a multidimensional view user, you need the following additional components:


¶ Cognos PowerPlay

Hardware RequirementsTivoli products that support Windows NT must be installed on an IBM PC Intel-compatiblemachine. Tivoli does not support platforms (such as the NEC PC 98xx series) that are not100% compatible with the IBM PC.

Each installation of the Domino Discovery Guide requires 10 MB of disk space. That is, theinstallation process requires 10MB of disk space, although the installed guide might not useall 10 MB of space.

Database RequirementsTivoli Decision Support for Lotus Domino supports the following database types:

Table 3. Supported DatabasesDatabase Type Database Version

Sybase 11.5, 11.9.2

Oracle 7.3.4, 8.0.5, 8.1.5

DB2 5.2, 6.1

Microsoft SQL Server 6.5 (service pack 5), 7.0 (service pack 1)

Creating ODBC Drivers

ObjectiveTo create the ODBC drivers to connect to your database.

Background InformationNone

Before You BeginYou should already have installed an RDBMS client that includes ODBC drivers. See“Database Requirements” on page 12 for supported database clients. Use the drivers fromthis RDBMS client install to set up the ODBC. Refer to your database documentation formore information.

12 Version 3.1.0

Your system must have a valid client configuration for the ODBC that Tivoli DecisionSupport uses to access your database. Consult your organization’s database administrator forthe appropriate client ODBC.

When You FinishAfter you add the ODBC drivers, configure Tivoli Decision Support to use these drivers toconnect to your data sources as described in “Defining the Data Sources for the ODBCDrivers” on page 13.

Procedure1. Open the Windows NT Control Panel.

2. Double-click the Data Sources (ODBC) icon. The ODBC Data Source Administratordialog is displayed.

3. Click the System DSN tab.

4. Click Add.

5. Select the ODBC driver that was installed with your RDBMS client. Refer to theRDBMS documentation for setting up this ODBC driver to connect to the databasecreated with Tivoli Manager for Domino.

6. When you have finished setting up this ODBC driver to the database, click Add to addanother ODBC driver. This driver will connect to the .csv export file created from theDomino Monitor Values query in the Domino Monitors cube.

7. Select the Microsoft Text Driver (*.txt; *.csv) as the driver and click Finish.

8. For the data source name, enter a descriptive name for this driver.

9. Uncheck the Use Current Directory option and click Select Directory to set thedirectory where the .csv export file will reside.

10. Set this directory to TDS 2.1/Data/Export. If the Export directory does not exist, createit. When building the Domino Monitors cube, this directory will be populated with the.csv export files.

11. Click OK to add this ODBC driver.

12. Click OK to close the ODBC Data Source Administrator dialog.

Defining the Data Sources for the ODBC Drivers

Objective

To define the data source for the ODBC drivers.


When You FinishIf you are running Tivoli Decision Support over a network, proceed to “Specifying the Pathfor Shared Source Files” on page 14.

If you installed Tivoli Decision Support in stand-alone mode, proceed to “Installing theDomino Discovery Guide” on page 15.


3.In

stallation

and

Co

nfig

uratio

n

Procedure1. Open the Tivoli Discovery Administrator.

2. Right-click the Data Sources folder and select Add. The Add Data Source Wizarddialog is displayed.

3. Select the datasource name that connects to the database that you created in theprevious section.

4. Click Next.

5. Enter the user name and password for connecting to this data source. For connecting tothe database created with Tivoli Manager for Domino, the default user name is tmd andthe password is DOMINO.

6. Click Next.

7. Leave the database qualifier field blank.

8. Click Next.

9. Confirm the options you selected. Click Finish to add this data source.

10. Return to step 2 and repeat this procedure to add the Microsoft Text ODBC driver.Enter the following values in the Wizard dialog:

a. Specify the datasource name you assigned that corresponds to the Microsoft Textdriver.

b. No user name or password is required, but you must enter text in the user namefield to continue configuring the data source.

c. Leave the qualifier field blank.

11. Click Finish to add this data source and close the Wizard dialog.

Specifying the Path for Shared Source Files

ObjectiveTo specify the location of shared source files on a network server.

This procedure is only necessary if you are running Tivoli Decision Support over a network.If you installed Tivoli Decision Support in stand-alone mode, proceed to “Installing theDomino Discovery Guide” on page 15.

Background InformationThe Tivoli Discovery Administrator must be able to find the following source files:

¶ Tivoli Discovery Interface topic map database (*.mdb) files

¶ PowerPlay reports (*.ppr) files

¶ Crystal Reports (*.rpt) files

If you installed Tivoli Decision Support using the stand-alone installation option, these filesare on the drive where you installed Tivoli Decision Support. The path is set duringinstallation and no further action is necessary.

14 Version 3.1.0

If you are running Tivoli Decision Support over a network and are sharing the source fileswith other users, the files reside on a network server and are called shared source files.Contact your system administrator for the location of the source files, then perform thisprocedure to specify the path to the shared source files.

If you reinstall Tivoli Decision Support or switch from stand-alone to shared mode on anetwork, you must reset the shared source file path.

For more information, refer to the Tivoli Decision Support Installation Guide.

When You FinishProceed to the section “Installing the Domino Discovery Guide” on page 15.


2. Select View → Options. The Options dialog is displayed.

3. Click the General tab.

4. In the Network text box, enter the name of the drive (and folder, if necessary) thatcontains the Data and Reports folders.

5. Click OK to close the Options dialog.

Installing the Domino Discovery Guide

ObjectiveThis section describes how to install the Domino Discovery Guide from the Tivoli Managerfor Domino, Version 3.1.0, CD-ROM on the Tivoli Decision Support server.

Background InformationThe Domino Discovery Guide files are placed in the following Tivoli Decision Supportinstallation directories:

\Cubes\Install\Models\Reports

The online documentation is installed in the following directory:

\Guide Docs\Tivoli Decision Support for Lotus Domino

Before You BeginNone

When You FinishImport the Domino Discovery Guide into Tivoli Decision Support. See “Importing theDomino Discovery Guide” on page 16.

ProcedureYou can perform this procedure from the Tivoli desktop or the Windows NT Start menu.


3.In

stallation

and

Co

nfig

uratio

n

Tivoli Desktop1. Insert the Tivoli Manager for Domino CD into the CD-ROM drive.

2. Select Desktop → Install → Install Product. The Install Product dialog box is displayed.

3. Click Select Media. The File Browser dialog box is displayed.

4. In the Path Name text box, type the following path:

D:\TDS\setup.exe

where D: is the drive letter for the CD-ROM drive.

5. Click Set Media & Close.

6. From the Install dialog box, click Install & Close.

Windows NT Start Menu1. Insert the Tivoli Manager for Domino CD into the CD-ROM drive.

2. Click the Windows NT Start menu and select Run.

3. In the Run dialog box, enter the following command:

D:\TDS\setup.exe

where D: is the drive letter for the CD-ROM drive.

4. In the Installation dialog, click Tivoli Decision Support for Lotus Domino.

Importing the Domino Discovery Guide

ObjectiveTo import the Domino Discovery Guide into Tivoli Decision Support.


Before You BeginYou must install the Domino Discovery Guide before you can import it. See “Installing theDomino Discovery Guide” on page 15.

Make sure that you have installed Tivoli Decision Support with the Tivoli DiscoveryAdministrator before attempting this task. See the Tivoli Decision Support Installation Guidefor more information.

When You FinishProceed to “Assigning a Data Source” on page 17.


2. Select Decision Support Guides → Import to display the Import Decision SupportGuides dialog.

3. Select Tivoli Decision Support for Lotus Domino and click OK.

16 Version 3.1.0

Assigning a Data Source

ObjectiveThis section describes how to assign a data source to the queries for building cubes.


Before You BeginBefore assigning a data source, you must have the following installed on your system:

¶ Tivoli Discovery Administrator. See the Tivoli Decision Support Installation Guide formore information.

¶ A database supported by Tivoli Decision Support (see “Database Requirements” on page12).

When You FinishProceed to “Setting the Date Range Parameter for a Cube” on page 18.


2. Click the Domino Monitors cube.

3. Select Data Sources → Assign Data Source. The Assign Data Source dialog box isdisplayed.

4. From the Data Source menu, select the data source that connects to your database.(You defined this data source in “Defining the Data Sources for the ODBC Drivers” onpage 13.)

5. Select the following queries (use Shift-click), then click OK to return to the TivoliDiscovery Administrator:

¶ Domino Monitor Values

¶ Domino Server Info

6. Click Data Sources → Assign Data Source. The Assign Data Source dialog box isdisplayed.

7. From the Data Sources menu, select the data source that uses the Microsoft ODBC textdriver. (You defined this data source in “Defining the Data Sources for the ODBCDrivers” on page 13.)

8. Select Domino Prediction from the query list, then click OK to return to the TivoliDiscovery Administrator.

9. Click the Data Sources folder.

10. From the right-hand pane of the Tivoli Discovery Administrator, right-click on the datasource you just assigned and select Test Connectivity.

If the test is successful, the following message is displayed:Connection Successful


3.In

stallation

and

Co

nfig

uratio

n

If a connection could not be established, the following message is displayed. ClickDetails to display more information about the connection error. Click OK and verifythe data source information, user name, and password.Error connecting to Data Source-<DataSourceName>

Setting the Date Range Parameter for a Cube

ObjectiveTo set the value of the Date Range parameter to ensure that the Domino Monitors cube andthe Domino Trend cube gather and calculate data according to your requirements.

Background InformationA cube parameter enables you to change the scope of the data you want to analyze. TheDomino Monitors cube and the Domino Trend cube each contain a Date Range parameter.By default, this parameter is set to Rolling 6 Months.

You can change the values of this parameter to ensure that the cubes gather and calculatedata according to your requirements. Include parameters as part of your queries to representselection criteria that can change from time to time. Set the cube parameters before youperform the initial cube build and before you schedule automatic cube builds. Set theparameters in your queries to produce a specific selection criteria for your cube.

The Date Range parameter uses explicit values, start and end dates, or a calculated value,such as the last three months. The calculated values are relative to the current date. Use theDate Range parameter and the CubeName_dt.txt file to set the current time period in thefollowing cases:

¶ Use End Date for an explicit date range.

¶ Use Calculated Values for a calculated end date.

¶ Use the date the cube was built when there is no Date Range parameter in the cube.

¶ If you want to use the date in the CubeName_dt.txt file as the current time period,create a new query in the cube model. This query must use the CubeName_dt.txt file asa local data file. Also, set the current time period option for this query only.

¶ Use the Date Range parameter, but do not use the CubeName_dt.txt file. This usageselects only records between the specific start date and end date, and sets the currentperiod to the most recent date in the data.

¶ Do not use the Date Range parameter or the CubeName_dt.txt file, which selects all therecords and sets the current period to the most recent date in the data.

¶ Use the CubeName_dt.txt file, but do not use the Date Range parameter. This usageselects all the records and sets the current period to the date of the current cube build.

For more information about how to set the current period and select records, see the TivoliDecision Support Administrator Guide.


When You FinishProceed to “Updating the SQL Query Statement” on page 19.

18 Version 3.1.0


2. Double-click the Cubes folder to open it.

3. Double-click the cube whose Date Range parameter you want to change.

4. Click Parameters.

5. In the Properties pane, right-click Date Range and select Set Values.

6. Select Explicit Values and enter a Start Date and an End Date.

—OR—

Select Calculated Values and choose an option from the drop-down menu.

7. Click OK to set the Date Range value and return to the Tivoli Discovery Administrator.

Updating the SQL Query Statement

ObjectiveTo add a database-specific SQL query statement to the Domino Monitors cube.

Background InformationThe SQL statement used to query data from your database differs depending on the type ofdatabase that you are using as the data source. Before you can perform cube builds to querydata from the database, you must update the SQL statement for the Domino Monitors cube.

When You FinishProceed to “Building Cubes Manually” on page 20.

Procedure1. Open a file browser.

2. Go to the directory TDS 2.1/Util/Tivoli Decision Support for Lotus Domino.

3. If you are using DB2 or Oracle as your RDBMS, open the file domino_db2_oracle.txt.If you are using Sybase or SQL Server, open the file domino_sybase_mssql.txt.

4. Select the entire contents of this file and select Copy.

5. Open the Tivoli Discovery Administrator.

6. Double-click the Cubes folder to open it.

7. Double-click the Domino Monitors cube to open it.

8. Click Queries to view the queries for this cube in the Properties pane.

9. Right-click the Domino Monitor Values query and select Edit.

The Cube Query window is displayed.

10. The current SQL statement for this monitor is shown in a text box in the SQL Columnstab. Select the entire contents of this text box and paste (Ctrl-v) to replace it with thestatement you copied.

11. Select OK to save your changes and close the window.


3.In

stallation

and

Co

nfig

uratio

n

Building Cubes Manually

ObjectiveTo manually build a Domino Monitors cube and a Domino Trend cube.

Background InformationThe phrase building a cube means to populate an empty Cognos Transformer model withdata from your data source. Cube building is also referred to as creating a multidimensionalcube or a PowerCube. PowerCubes package data from your database and makemultidimensional views possible. They define the way that Tivoli Decision Supportaccumulates and summarizes your data.

You must build at least one cube manually before you can use Tivoli Decision Support.After the first build, you can build the cubes manually or schedule them to buildautomatically.

Builds should occur regularly to keep the cube data current. You determine how often thecubes are built based on your needs.

Cube building is a resource-intensive activity; therefore, make sure to schedule this activityduring periods of decreased database activity. Adjust your cube date range to optimize thetime required to build a cube.

Before You BeginNot applicable

When You FinishAfter the initial cube build, you can automate the cube building process. For moreinformation see “Scheduling Automatic Cube Builds” on page 21.

Start the Tivoli Discovery Interface and use the Tivoli Discovery Guide to review the viewsfor each topic.


2. Double-click Cubes.

3. Right-click the Domino Monitors cube and select Build. The Confirm Cube Builddialog box displays the date ranges.

4. Perform one of the following:

¶ Click Yes to approve the date ranges and continue.

The Tivoli Discovery Administrator connects to the database and builds the cube,populating it with records from your database tables. The volume of data andnetwork speed both affect the build time. The Cube Transform Status dialog boxdisplays. View this dialog box for cube-building processing messages.

¶ Click No to go back and change the date ranges before proceeding. For moreinformation, refer to “Setting the Date Range Parameter for a Cube” on page 18.

5. Review the Cube Transform dialog box for error messages that were generated duringthe cube build. Refer to “Troubleshooting Cube Builds” on page 23 for help in solvingcube build problems.

20 Version 3.1.0

6. Click Close.

7. Repeat the previous steps for the Domino Trend cube.

Scheduling Automatic Cube Builds

ObjectiveTo schedule automatic cube builds.

Background InformationAutomatic cube builds accomplish the following:

¶ Free you of the task of scheduling them manually

¶ Enable you to build cubes when the system is least busy

¶ Ensure that cube data is current

To streamline the scheduling of cube builds, you can create cube build tasks using the TaskScheduler and run them using an external scheduler. You can also use an external scheduler,such as Tivoli Workload Scheduler or the Scheduler program supplied with CognosPowerPlay.

Remember the following when scheduling cube builds:

¶ After the initial build is complete, rebuild the cube periodically to update the data. Youdetermine how often the cubes are built based on your needs.

¶ Schedule the build process to build automatically at regular intervals.

¶ Stagger the cube build start times for improved performance.

¶ Schedule the cube builds after the rollup tool completes the rollup job when updateddata for the cubes is available.

Before You BeginYou must have built at least one set of cubes manually as described in “Building CubesManually” on page 20.

When You FinishStart the Tivoli Task Server. The Tivoli Task Server must be running to automatically buildcubes. After you start the Tivoli Decision Support Scheduler service one time, itautomatically restarts when you reboot the machine.

For more information about scheduling cube builds, refer to the Tivoli Decision SupportAdministrator Guide.


2. Right-click the Scheduled Tasks icon and select Add.

The Add Schedule Wizard dialog box is displayed.

3. Type a name for the schedule and click Next.

4. Select a cube and click Next.

5. Select an interval for the build and click Next.


3.In

stallation

and

Co

nfig

uratio

n

6. Select a task interval and click Next.

7. Enter a time interval and click Next.

8. Enter a date range and click Next.

9. View the automatic cube build settings and do one of the following:

¶ Click Back to go back and edit the settings.

¶ Click Finish to close the dialog box and return to the Tivoli DiscoveryAdministrator.

10. From the Properties pane, right-click the scheduled task you just created.

11. Click Edit.

12. Click the Task tab and verify that it is set to build the cube you want.

13. Click OK.

14. Click the Windows NT Start menu and select Programs → Tivoli Decision Support2.1→Tivoli Task Server. The Tivoli Task Server window opens. Minimize the window.

Uninstalling the Domino Discovery Guide

ObjectiveTo uninstall the Domino Discovery Guide.



When You FinishIf you reinstall Tivoli Decision Support, you must reset the path for the shared source files.For more information, see “Specifying the Path for Shared Source Files” on page 14.


2. Click the Decision Support Guides folder.

3. In the right-hand pane, right-click the Lotus Domino guide.

4. Select Delete from the drop-down menu.

22 Version 3.1.0

Troubleshooting

This section provides the following troubleshooting topics:

¶ “Troubleshooting Cube Builds” on page 23

¶ “Troubleshooting Reports” on page 24

Troubleshooting Cube BuildsThis section describes how to view log files from a cube build and how to interpret errormessages that appear in the log file.

Viewing Log Files after a Cube BuildErrors encountered during manual builds are displayed in the Cube Transform Statuswindow. For errors encountered during automatic builds, view the <ModelName>.log in theTDS 2.1\Models directory on your hard drive where Tivoli Decision Support was installed.For errors encountered during manual or automatic builds, look in the EDAdmin.log file inthe TDS 2.1 directory on your hard drive where Tivoli Decision Support was installed.

You can view log files from the Tivoli Discovery Administrator or the Windows NTExplorer.

Tivoli Discovery Administrator1. Right-click the cube in the Tivoli Discovery Administrator.

2. Click View Log from the pop-up menu.

Windows NT Explorer1. Open the Windows NT Explorer.

2. Navigate to TDS 2.1\Models.

3. Open the <ModelName>.log file.

“Error Building Cube” MessageIf the Tivoli Discovery Administrator displays the following message:Error building cube

and the detail information is as follows:\Error 91 - Error getting query parameters; object variable or with block variablenot set.

the data sources have not been assigned to the cube queries. Assign the data sources to thequeries.

4


4.Tro

ub

lesho

otin

g

“Cannot Execute” Message (Cognos PowerPlay)The Tivoli Discovery Interface might display a Cognos PowerPlay report icon with a CannotExecute indicator when you attempt to open the report. The cube is unavailable and must bebuilt. Contact the Tivoli Decision Support administrator and request that the cube be built.

“load_graph_from_powercube” MessageThe error message load_graph_from_powercube indicates that the cube was not built.Build the cube following the instructions in “Building Cubes Manually” on page 20 or“Scheduling Automatic Cube Builds” on page 21.

“Cube Cannot Be Built” MessageThe following list describes several reasons why the Tivoli Discovery Administrator mightdisplay the message cube cannot be built. The cube will not build if any of the followingoccurs:

¶ Any Tivoli Discovery Interface processes are open.

Close all running copies of the Tivoli Discovery Interface. Open the Windows NT TaskManager. Click on the Processes tab. Right-click on the DiscoveryInterf process orprocesses and select End Process.

¶ The cube you are attempting to rebuild is currently in use.

Tivoli Decision Support cannot overwrite a cube with new cube data. Close all runningcopies of the Tivoli Discovery Interface. Copy <CubeName>.mdc from the TDS2.1\Cubes\Temp directory to the TDS 2.1\cubes directory.

¶ A copy of Cognos PowerPlay is running in the background.

Open the Windows NT Task Manager. If the pplay.exe process is running, end theprocess and rebuild the cube.

Cubes Fail to Build OvernightFor scheduled cube builds to occur, the Tivoli Task Server must be running. Review thescheduled tasks in the Tivoli Discovery Administrator. For more information, see“Scheduling Automatic Cube Builds” on page 21.

Troubleshooting ReportsThis section includes topics and hints for troubleshooting problems you might encounterwith reports.

Report Contains No DataThere may be data in the report, but none in the drill-down. The report may be filtered on adimension. Look at the dimension bar and check if any of the values, especially the datedimension, are drilled down.

Some Values Look IncorrectIf the maximum or minimum daily values seem incorrect compared to the hourly averagevalues, consider that the hourly values correspond to an hourly average or an hourly total,based on the monitor that is reported. The maximum and minimum values for each hour arenot displayed. Therefore, if a monitor is run frequently to produce several values for eachhour, one value can be much higher or lower than the others. This value might become thedaily maximum or minimum. However, only the hourly average value is displayed.

If other values look incorrect in the reports, confirm the following:

24 Version 3.1.0

¶ Each monitor is running and has returned a value.

For instance, if no replication monitors have been distributed from the Domino monitors,no replication data displays in the Replication Statistics report, even though this reportdisplays other data.

¶ All cube builds finished successfully. Some data may be missing if the cube builds didnot finish.

¶ All levels in the dimension line match those displayed in “Report Definitions” on page35.

For example, check to see if the correct monitor is displayed in the By Monitordimension.

No Data for Certain MeasuresYou can view hourly, daily average, daily minimum, daily maximum, and daily total valuesfor each report. However, not all monitors have values for each measure because report datais calculated based on the monitor type. For instance, the Mail.TotalRouted monitorcalculates and reports only hourly and daily total values. This monitor has no daily average,daily minimum, or daily maximum value.


4.Tro

ub

lesho

otin

g

26 Version 3.1.0

Product Details

This chapter describes the Domino Discovery Guide features and functions and lists pointersto information supplied on the Tivoli Discovery Administrator for the Domino DiscoveryGuide.

Data StructureThe built-in rollup tool for Tivoli Manager for Domino, Version 3.1.0, contains scripts forcreating the database schema and tasks for the rollup. After you install Tivoli Manager forDomino, run the database schema scripts on the Oracle, Sybase, DB2, or Microsoft SQLdatabase to create the TMD_SERVER and TMD_MON tables. After you distribute theDomino Discovery Guide monitors, the rollup tasks aggregate and store the data into thesetables in the relational database. You must then create the Domino monitors for reporting.

Domino Rollup Tool DatabaseBecause the Domino Discovery Guide uses Domino monitors to collect data, it uses thedatabase schema supplied with Tivoli Manager for Domino. The database name for theDomino Discovery Guide is tmd, and the default password is DOMINO.

The Domino Discovery Guide TMD_SERVER table contains the following information:

Table 4. TMD_SERVER TableField Name Data Type Field Size (bytes) Field Description

SERVER varchar 255 Lotus Domino server name

DOMAIN varchar 255 Server domain

CLUSTER_NAME varchar 255 Cluster name

RELEASE varchar 32 Server version

OS varchar 32 Server platform

WEB int Not applicable Web server type

MAIL int Not applicable Mail server type

MAILROUTER int Not applicable Mail router server type

DB int Not applicable Database server type

NEWS int Not applicable News server type

The Domino Discovery Guide TMD_MON table contains the following information.

Table 5. TMD_MON TableField Name Data Type Field Size (bytes) Field Description

RUN_DATE datetime Not applicable Date the Monitor Was Run

5


5.P

rod

uct

Details

Table 5. TMD_MON Table (continued)Field Name Data Type Field Size (bytes) Field Description

RUN_TIME varchar 8 Time the Monitor Was Run

SERVER varchar 64 Monitor Server Name (LotusDominoServer Object)

PROBE varchar 64 Monitor Name

PROBE_ARG varchar 255 Monitor Argument

VALUE1 text Not applicable Monitor Value1

VALUE2 varchar 192 Monitor Value2

The SQL scripts used to define the database user and create the Tivoli Manager for Dominodatabase schema are supplied with Tivoli Manager for Domino, Version 3.1.0. Each databaseuses a separate SQL script. Use the TMD_SERVER and TMD_MON scripts to create thedatabase table schema for Sybase.

The scripts for the other databases supported by the Domino Discovery Guide differ in thedata type, the syntax of the end of line (semicolon [;] instead of “go”), the use of the datatype varchar2 instead of varchar, the trigger, and the indices creation. You can view thesescripts and their contents from the following locations:

¶ The Tivoli Discovery Administrator (after you install the Domino Discovery Guide)

¶ Appendix A, “Technical Reference” on page 43.

Purging Records from the Rollup Tool DatabaseTivoli Manager for Domino provides a task (Clean Database) and a commandwtmdcleandb for purging records from the database. Refer to the Tivoli Manager forDomino Reference Guide for more information.

CubesA PowerCube, or cube, contains data (measure values) organized in dimensions andmeasures to facilitate faster retrieval and drill-down in PowerPlay Explorer and Reporter.The Domino Discovery Guide has two cubes, the Domino Monitors cube and the DominoTrend cube. Use the Tivoli Decision Support Administrator Guide to define cubeinformation.

You can view all of the query select statements and calculated columns in Appendix A,“Technical Reference” on page 43. After you install the Domino Discovery Guide, you canview the functions for the calculated columns, as well as the SQL columns and calculatedcolumns, from the Tivoli Discovery Administrator.

To view the queries used to build the cubes, follow these steps:

1. Open the Tivoli Discovery Administrator.

2. Double-click the cubes folder.

3. Double-click the Domino Monitors Cube or the Domino Trend Cube.

4. Double-click Queries.

5. Double-click an individual query. A tabbed dialog that enables you to view queryinformation is displayed.

28 Version 3.1.0

Domino Monitors CubeThe Domino Monitors cube consists of two queries and three parameter settings. Each querycreates a comma-separated variable data file for the Cognos Transformer, and the tworesulting .csv files are used to build the Cognos model and PowerCube. Each of the queriesextracts data from the TMD_SERVER and TMD_MON tables in the relational databaseusing the ODBC driver. Data from the defined Domino monitors are collected for reportingfrom these queries.

Queries Used to Build the Domino Monitors CubeThis section describes the two queries used to build the Domino Monitors cube.

Domino Monitors Values QueryThe Domino Monitors Values query retrieves monitor data from the TMD_MON table. Alldata within the date range specified in the Date Range parameter is retrieved by this query.The .csv file name for this query is domino_monitors.csv. The following table lists thecalculated columns for this query. Functions for the calculated columns are described inAppendix A, “Technical Reference” on page 43.

Table 6. Calculated Columns for the Domino Monitors Values QueryField Name Data Type

Cc_converted_probe String

Cc_PROBE_ARG String

Cc_Converted_Value_1 Variant

Cc_Converted_Value_2 Variant

Cc_hour Integer

Cc_business hour String

Cc_am pm String

Cc_weekday or weekend String

Cc_day of week String

Cc_IsCumulativeMonitor Boolean

Cc_Actual_Increment Variant

Domino Server Info QueryThe Domino Server Info query retrieves all server information from the TMD_SERVERtable. For each server, the server name, domain name, cluster name, release version,operating system, and server type are retrieved. The .csv file name for this query isdomino_server.csv. The following table lists the calculated columns for this query.Functions for the calculated columns are described in Appendix A, “Technical Reference” onpage 43.

Table 7. Calculated Columns for the Domino Server Info QueryField Name Data Type

cc_ServerRole String


5.P

rod

uct

Details

Parameters Used to Build the Domino Monitors CubeThe following table lists the parameter settings for the Domino Monitors cube.

Table 8. Parameters for the Domino Monitors CubeParameter Name Type Values

Date Range Range Rolling 6 Months

Probe NameConversions

Terminology

Business Hour Categorization Business Hour: 8-17 (otherwise non-business houror non-business)

DimensionsAfter you define the cubes in the Tivoli Discovery Administrator, you can create a model foreach cube in Cognos Transformer. The file name for the created model isdomino_monitors.mdc. The Domino Monitors cube model consists of five dimensions andfour measures. A dimension is a grouping of descriptive data about a major aspect of abusiness. Each dimension includes categories in one or more drill-down paths and anoptional set of special categories. The Cognos Transformer model for the Domino Monitorscube consists of the following dimensions:

¶ By Date/Time

The date/time dimension has the following categories, which are automatically generatedduring the PowerPlay cube build. This dimension allows you to drill down to the exacttime a monitor runs.

Table 9. Date DimensionBy Date/Time

QUARTER

MONTH

DAY

HOUR

RUN_TIME

¶ By Server

The Server dimension allows you to drill down by the subscriber.

Table 10. By Server DimensionBy Server

Domain CLUSTER_NAME RELEASE OS cc_ServerRole

SERVER

¶ By Monitor

By Monitor

PROBE

PROBE_ARG

Misc. information

30 Version 3.1.0

¶ By Day of Week

Table 11. By Day of WeekBy Day of Week

Weekday or Weekend

Day_Of_Week

¶ By Hour

The By Hour dimension is used to filter data by a.m./p.m. or business or non-businesshours.

Table 12. By Hour DimensionBy Hour

AMPM Business or non-business

Hour (AM/PM)

MeasuresThe measures in the Cognos Transformer model are the quantitative values returned from theDomino monitors. These values change according to which dimensions you view. TheCognos Transformer model for the Domino Monitors cube contains the measures in thefollowing table. Each measure returns an na value when the column is null, and all measurevalues are displayed to two decimal places.

Table 13. Domino Monitors Cube MeasuresMeasure Name Purpose Calculation Included

Average Average MonitorValues

Total Total Monitor

Maximum Maximum MonitorValues

Minimum Minimum MonitorValues

Checking the Allowed Measures and Dimensions CombinationBefore building a PowerCube with a model, perform a check to ensure there are noproblems with the model. For each measure, determine if each model is in scope with all thedimensions. For the model in the Domino Monitors cube, all measures described in theprevious section, “Measures”, are in scope with all the model dimensions.

The following table lists the measures of the cube and whether they are in scope for thedimensions. After you design a cube for a guide, building this table can help you determineif everything will work properly. When a dimension is out of scope, the relative level isdisplayed in brackets, and the letters in parentheses have the following meanings:

¶ Level derived indirectly (query scope) from columns in queries associated with theselected query. Valid for query scope dimension maps only.

¶ Level derived directly (query and measure scope) from a column within the selectedquery; or a measure that has direct meaning at that level.


5.P

rod

uct

Details

¶ Level derived from a query with missing columns (query scope). A level derived from acolumn in a query that lacks the columns required to generate categories for higherlevels in the dimension. Valid for query scope dimension maps only.

¶ Level with allocated measures (measure scope). Levels whose measure values areallocated by the Cognos Transformer. Valid for measure scope dimension maps only.

¶ Not applicable (out of measure and query scope).

Table 14. Measures In and Out of ScopeValue Description

Y In scope

G Out of scope

Gx Out of scope, measure allocated to the dimension

Domino Trend CubeThe Domino Trend cube consists of one query and no parameter settings. The query createsa .csv data file for the Cognos Transformer, and the resulting .csv file is used to build theCognos Transformer model and PowerCube. The queries extract data from the tables in therelational database through the ODBC driver. The extracted data are then used to calculatethe forecasted values. Data from the Domino monitors are collected from this query forreporting.

Query Used to Build the Domino Trend CubeThe Domino Prediction query is the only one used to build the Domino Trend cube.

This query retrieves the monitor data from the TMD_MON table and uses this data tocalculate the predicted values for each monitor. The .csv file name for this query isdomino_trend.csv. The following table lists the calculated columns for this query. Functionsfor the calculated columns are described in Appendix A, “Technical Reference” on page 43.

Table 15. Calculated Columns for the Domino Prediction QueryField Name Data Type

Cc_Forcast_0_Day_Average Variant



Parameters Used to Build the Domino Trend CubeThere are no parameters used to build the Domino Trend cube.

DimensionsAfter you define the cubes in the Tivoli Discovery Administrator, create a model for eachcube with the Cognos Transformer. The file name for the created model isdomino_trend.mdc. The Domino Trend cube model consists of two dimensions (server andmonitor) and three measures (Next Day, 15 Days, and 30 Days Later). The two dimensionsof the Domino Trend cube are as follows:

¶ By Server

This dimension is used to categorize reports by the endpoint name (which is themachine alias name). An alternate drill-down allows you to view servers by the profilein which the monitors were distributed. By performing an alternate drill category, you

32 Version 3.1.0

can customize how you want to distribute and view your monitors.

Table 16. By Server DimensionAll Servers

DOMAIN CLUSTER_NAME RELEASE OS cc_ServerRole

SERVER

¶ By Monitor

This dimension drills down from the type of Domino monitor to the specific monitorargument.

Table 17. By Monitor DimensionAll Monitors

PROBE

PROBE_ARG

Miscellaneous. information

MeasuresThe Cognos PowerPlay model for the Domino Trend cube contains the measures displayedin the following table. Each measure returns an na value when the column is null, and allmeasure values are displayed to two decimal places.

Table 18. Domino Trend Cube MeasuresMeasure Name Purpose Calculation Included DrillThru

Report

Next Day Trend value for thatday

15 Days Later Trend value for thatday

30 Days Later Trend value for thatday

Checking the Allowed Measures and Dimensions CombinationBefore building a PowerCube with a model, perform a check to ensure there are noproblems with the model. For each measure, you can see if each model is in scope with allthe dimensions. For the model in the Domino Trend cube, all measures described in“Measures” are in scope with all the model dimensions.

The following table lists the measures of the cube and whether they are in scope for thedimensions. After you design a cube for a guide, building a table like this helps you todetermine if everything is defined properly. When a dimension is out of scope, the relativelevel is displayed in brackets, and the letters in parentheses have the following meanings:

¶ Level derived indirectly (query scope) from columns in queries associated with theselected query. Valid for query scope dimension maps only.

¶ Level derived directly (query and measure scope) from a column within the selectedquery; or a measure that has direct meaning at that level.


5.P

rod

uct

Details

¶ Level derived from a query with missing columns (query scope). A level derived from acolumn in a query that lacks the columns required to generate categories for higherlevels in the dimension. Valid for query scope dimension maps only.

¶ Level with allocated measures (measure scope). Levels whose measure values areallocated by Cognos Transformer. Valid for measure scope dimension maps only.

¶ Not Applicable (out of measure and query scope).

Table 19. Measures In and Out of ScopeValue Description

Y In scope

G Out of scope

Gx Out of scope

MonitorsFor a number of monitor values returned from the Tivoli Manager for Domino monitors, thestatistic represents a counter value taken from a particular point in time from a Dominoserver. These counter values continually increase from the time the Domino server is starteduntil it is stopped. In order to show the calculated delta values for these statistics, the TivoliDecision Support for Lotus Domino guide calculates these values based on the differencebetween the previous and current values. For instance, if the statistic Replica.Failed returnsthe value of 10 at 8:00am and 25 at its next polled instance at 8:30am, the calculateddifference shown at 8:30am will be 15.

The guide calculates delta values for the following monitors:¶ Domino.Requests.Per1Hour.Total¶ Server.Trans.Total¶ Replica.Failed¶ Replica.Successful¶ Replica.Cluster.*¶ Replica.Docs.Added¶ Replica.Docs.Deleted¶ Replica.Docs.Updated¶ NET.*.BytesReceived¶ NET.*.BytesSent¶ NET.*.Sessions.Established.Incoming¶ NET.*.Sessions.Established.Outgoing¶ NET.*.Sessions.Established.Recycled¶ Mail.TotalRouted¶ Mail.TotalFailures¶ Mail.Transferred¶ Mail.TransferFailures¶ Mail.TotalKBTransferred¶ MTA.Smtp.TotalKBTransferred¶ MTA.Smtp.TotalRouted¶ MTA.Smtp.Transferred¶ MTA.Smtp.TransferFailures

34 Version 3.1.0

Report Definitions

The following table describes the reports available from the Tivoli Discovery Interface foreach view provided by the Domino Discovery Guide.

6


6.R

epo

rtD

efinitio

ns

Tabl

e20

.R

epor

tD

efin

ition

sV

iew

Tit

leP

erio

dM

easu

reSe

rver

Gro

upR

owC

olum

nO

ther

Info

rmat

ion

Rep

ort

File

nam

ean

dSo

urce

Cub

eN

ame

Cal

enda

ran

dSc

hedu

ling

Stat

istic

s

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:C

alen

dar

Lay

er:

Cal

enda

rD

omin

o_ca

lend

ar.p

prD

omin

o_m

onito

rs.m

dc

Clu

ster

Stat

usL

ast

7da

ysA

vera

geA

llSe

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Clu

ster

Ava

ilabi

lity

Stat

usD

omin

o_cl

uste

r.ppr

Dom

ino_

mon

itors

.mdc

Dis

kSp

ace

Stat

istic

sL

ast

30da

ysA

vera

geA

llse

rver

sL

ast

30da

ysA

llSe

rver

sM

onito

r:D

isk

Lay

er:

All

Serv

ers

Dom

ino_

disk

_sta

ts.p

prD

omin

o_m

onito

rs.m

dc

Mai

lAve

rage

Stat

istic

sL

ast

7da

ysA

vera

geA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Mai

lA

vera

geL

ayer

:M

ail

Ave

rage

Dom

ino_

mai

l_av

erag

e.pp

rD

omin

o_m

onito

rs.m

dc

Mai

lTo

tal

Stat

istic

sL

ast

7da

ysTo

tal

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:M

ail

Tota

lL

ayer

:M

ail

Tota

lD

omin

o_m

ail_

tota

l.ppr

Dom

ino_

mon

itors

.mdc

Not

esD

atab

ase

Size

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:D

atab

ase.

Stat

istic

s.A

sync

Lay

er:

All

Serv

ers

Dom

ino_

data

base

_si

ze.p

prD

omin

o_m

onito

rs.m

dc

QO

S.M

ail.

ISPY

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:Q

OS.

Mai

l.ISp

y.<

serv

erna

me>

.Res

pons

eTim

eDom

ino_

ispy

.ppr

Dom

ino_

mon

itors

.mdc

Rep

licat

ion

Stat

istic

sfo

rth

eL

ast

24H

ours

Las

t24

hour

sTo

tal

All

serv

ers

Las

t24

hour

sA

llSe

rver

sM

onito

r:R

eplic

atio

nD

omin

o_re

plic

atio

n_da

ily.p

prD

omin

o_m

onito

rs.m

dc

Rep

licat

ion

Stat

istic

sfo

rth

eL

ast

7D

ays

Las

t7

days

Tota

lA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Rep

licat

ion

Dom

ino_

repl

icat

ion_

wee

kly.

ppr

Dom

ino_

mon

itors

.mdc

Serv

erA

vaila

bilit

yL

ast

7da

ysA

vera

geA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Serv

erA

vaila

bilit

yD

omin

o_av

aila

bilit

y.pp

rD

omin

o_m

onito

rs.m

dc

Serv

erH

ealth

Stat

usL

ast

7da

ysA

vera

geA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Serv

er.H

ealth

.A

Sync

Dom

ino_

heal

th.p

prD

omin

o_m

onito

rs.m

dc

CPU

Util

izat

ion

Las

t24

hour

sA

vera

geA

llse

rver

sL

ast

24H

ours

All

Serv

ers

Mon

itor:

Perc

ent

Tota

lPr

oces

sor

Tim

eD

omin

o_cp

u.pp

rD

omin

o_m

onito

rs.m

dc

36 Version 3.1.0

Tabl

e20

.R

epor

tD

efin

ition

s(c

ontin

ued)

Vie

wT

itle

Per

iod

Mea

sure

Serv

erG

roup

Row

Col

umn

Oth

erIn

form

atio

nR

epor

tF

ilena

me

and

Sour

ceC

ube

Nam

e

Dom

ino

Net

wor

kT

raff

ic

Las

t7

days

Tota

lA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

NE

T.<

Port

Nam

e>L

ayer

:N

ET.

<Po

rtN

ame>

Dom

ino_

net.p

prD

omin

o_m

onito

rs.m

dc

HT

TP

Req

uest

sL

ast

7da

ysTo

tal

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:D

omin

o.R

eque

st.P

er1H

our.T

otal

Dom

ino_

http

.ppr

Dom

ino_

mon

itors

.mdc

Mem

ory

Usa

geL

ast

30da

ysA

vera

geA

llse

rver

sL

ast

30D

ays

All

Serv

ers

Mon

itor:

Mem

ory

Lay

er:

All

Serv

ers

Dom

ino_

mem

ory.

ppr

Dom

ino_

mon

itors

.mdc

Serv

erU

sage

Las

t24

hour

sA

vera

geA

llse

rver

sL

ast

24H

ours

All

Serv

ers

Mon

itor:

Serv

erL

ayer

:Se

rver

Dom

ino_

usag

e.pp

rD

omin

o_m

onito

rs.m

dc

25L

east

Use

dD

atab

ases

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:D

atab

ase.

Stat

istic

s.A

sync

Dom

ino_

leas

t_us

ed_

data

base

.ppr

Dom

ino_

mon

itors

.mdc

25M

ost

Use

dD

atab

ases

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:D

atab

ase.

Stat

istic

s.A

sync

Dom

ino_

mos

t_us

ed_

data

base

.ppr

Dom

ino_

mon

itors

.mdc

Bot

tom

25Se

rver

sby

Ava

ilabl

eD

isk

Spac

e

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:D

isk

Dom

ino_

rank

_ava

ilabi

lity.

ppr

Dom

ino_

mon

itors

.mdc

Bot

tom

25Se

rver

sby

Serv

erA

vaila

bilit

y

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:Se

rver

Ava

ilabi

lity

Dom

ino_

rank

_ava

ilabi

lity.

ppr

Dom

ino_

mon

itors

.mdc

Top

25M

ail

Use

rsby

mai

lfi

lesi

ze

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:U

serM

ail.

Stat

istic

s.A

snyc

Dom

ino_

rank

_mai

l_us

ers_

file

.ppr

Dom

ino_

mon

itors

.mdc

Top

25M

ail

Use

rsby

Mai

lT

raff

ic

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:U

serM

ail.

Stat

istic

s.A

snyc

Dom

ino_

rank

_mai

l_us

ers_

traf

fic.

ppr

Dom

ino_

mon

itors

.mdc


6.R

epo

rtD

efinitio

ns

Tabl

e20

.R

epor

tD

efin

ition

s(c

ontin

ued)

Vie

wT

itle

Per

iod

Mea

sure

Serv

erG

roup

Row

Col

umn

Oth

erIn

form

atio

nR

epor

tF

ilena

me

and

Sour

ceC

ube

Nam

e

Top

25Se

rver

sby

CPU

Util

izat

ion

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:Pe

rcen

tTo

tal

Proc

esso

rT

ime

Dom

ino_

rank

_cpu

.ppr

Dom

ino_

mon

itors

.mdc

Top

25Se

rver

sby

HT

TP

Req

uest

s

Las

t7

days

Tota

lA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Dom

ino.

Req

uest

.Per

1Hou

r.To

tal

Dom

ino_

rank

_http

.ppr

Dom

ino_

mon

itors

.mdc

Top

25Se

rver

sby

Mem

ory

Allo

cate

d

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:M

em.A

lloca

ted

Dom

ino_

rank

_mem

ory.

ppr

Dom

ino_

mon

itors

.mdc

Top

25Se

rver

sby

Tota

lM

ail

Rou

ted

Las

t7

days

Tota

lA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Mai

l.Tot

alR

oute

dD

omin

o_ra

nk_m

ail_

rout

ed.p

prD

omin

o_m

onito

rs.m

dc

Use

rM

ail

File

and

Quo

taL

ast

7da

ysA

vera

geA

llse

rver

sL

ast

7D

ays

All

Serv

ers

Mon

itor:

Use

rMai

l.St

atis

tics.

Asn

ycL

ayer

:A

llSe

rver

s

Dom

ino_

user

_m

ail_

file

.ppr

Dom

ino_

mon

itors

.mdc

Dom

ino

Stat

istic

sby

Day

Las

t30

days

Ave

rage

All

serv

ers

Las

t30

Day

sA

llSe

rver

sM

onito

r:A

llPr

obes

Lay

er:

All

Prob

esD

omin

o_da

y.pp

rD

omin

o_m

onito

rs.m

dc

Dom

ino

Stat

istic

sby

Wee

kday

s

Las

t7

days

Ave

rage

All

serv

ers

Las

t7

Day

sA

llSe

rver

sM

onito

r:A

llPr

obes

Lay

er:

All

Prob

esD

omin

o_w

eekd

ay.p

prD

omin

o_m

onito

rs.m

dc

Dom

ino

Stat

istic

sin

Bus

ines

sH

ours

Las

t24

hour

sA

vera

geA

llse

rver

sL

ast

24ho

urs

All

Serv

ers

Mon

itor:

All

Prob

esL

ayer

:A

llPr

obes

Dom

ino_

hour

.ppr

Dom

ino_

mon

itors

.mdc

Dom

ino

Stat

istic

sby

Serv

er

Las

t24

hour

sA

vera

geA

llse

rver

sL

ast

24H

ours

All

Serv

ers

Mon

itor:

All

Prob

esD

omin

o_se

rver

.ppr

Dom

ino_

mon

itors

.mdc

38 Version 3.1.0

Tabl

e20

.R

epor

tD

efin

ition

s(c

ontin

ued)

Vie

wT

itle

Per

iod

Mea

sure

Serv

erG

roup

Row

Col

umn

Oth

erIn

form

atio

nR

epor

tF

ilena

me

and

Sour

ceC

ube

Nam

e

Dom

ino

Stat

istic

sby

Serv

erR

oles

Las

t24

hour

sA

vera

geB

yse

rver

role

Las

t24

Hou

rsB

ySe

rver

Rol

eM

onito

r:A

llPr

obes

Lay

er:

All

Prob

esD

omin

o_se

rver

_ro

les.

ppr

Dom

ino_

mon

itors

.mdc

Serv

erFo

reca

sted

Ave

rage

s

No

time

dim

ensi

onin

cube

Ave

rage

(for

one

day,

15da

ys,

and

30da

ysla

ter)

All

serv

ers

All

Serv

ers

All

Mon

itors

Mon

itor:

All

Mon

itors

Dom

ino_

tren

d.pp

rD

omin

o_tr

end.

mdc


6.R

epo

rtD

efinitio

ns

40 Version 3.1.0

Defects, Limitations, and Workarounds

This chapter lists the current known defects, limitations, and workarounds for this product.

DefectsCurrently, no defects are reported for the Domino Discovery Guide.

LimitationsThe following limitations are known for this product:

¶ The size of the TMD_SERVER and TMD_MON database tables can affect thecube-building process. Control the size of these tables in the Tivoli Manager forDomino, Version 3.1.0, database to optimize the cube-building process.

¶ Because columns within the database tables are allocated only a certain maximumlength, ensure that the column values for each monitor are within the maximum allowedlength.

¶ When you create monitors to store data to the Sentry Graphable Logs file, large numericvalues are logged with only six significant digits. For example, if a monitor returns thevalue 123456789, this value is stored in the Sentry Graphable Logs file as1.234567x10^8. Only six significant digits are stored, and the sixth number is rounded.Therefore, large numeric values can be rounded when stored in the RDBMS for theDomino Discovery Guide.

¶ In the Tivoli Decision Support, Version 2.1.1, Tivoli Discovery Interface, the Rankingtab in the Properties of a view does not retrieve the categories to automatically re-rankthe Cognos PowerPlay view. Instead, the following error message might appear:Cannot retrieve the categories for this view.

WorkaroundsTable 21 lists workarounds for the following problems:

Table 21. WorkaroundsProblem Workaround

Measures on simple bar graphs are displayedtwice: centered on the graph and over theY-axis. On low-resolution monitors, themeasure names can overlap.

A minimum resolution of 800x600 pixels isrecommended for monitors.

7


7.D

efects,L

imitatio

ns,

and

Wo

rkarou

nd

s

Table 21. Workarounds (continued)Problem Workaround

Process_Name.exe

The Application Error message dialog boxdisplays the following message: Theinstruction at “memory address” referencedmemory at “memory address” could not be“read.”

If the Process_Name.exe error message appearsduring a cube build, wait until the transformationprocess has completed before clicking OK orCancel on the error message dialog box.Occasionally, during the cube-build or query-exportprocess, this application error message is displayed.This situation can occur when Tivoli DecisionSupport is used in combination with the TivoliODBC Driver for Sybase 3.11. This error messagecan be displayed frequently for a time and then notat all. By waiting, you allow the cube to finishbuilding. After the build process has completed,click OK on the error message dialog box. TheTivoli Discovery Administrator closes. Start theTivoli Discovery Administrator and continuebuilding any remaining cubes.

42 Version 3.1.0

Technical Reference

The information in this appendix is intended for Tivoli or Domino database planners whoare responsible for designing and implementing a Tivoli Decision Support for Lotus Dominoinstallation to monitor Lotus Domino. This information is not applicable for day-to-dayadministration. For a discussion of the daily administration of Tivoli Decision Support forLotus Domino, refer to “Product Details” on page 27.

Note: The following sections are intended to provide information about how Tivoli DecisionSupport for Lotus Domino works with the Tivoli Decision Support database (Oracle,Sybase, DB2, or Microsoft SQL) and with Lotus Domino. Do not change theinformation in the schema script or the database queries or calculated columns. Anychanges to the schema scripts or query statements can cause the product to fail.

Domino Database SchemaThe Domino Discovery Guide uses the database schema supplied with the Tivoli Managerfor Domino rollup tool. The guide uses a separate database schema for each of the supporteddatabases. The following script is used to create the database for Sybase.

Sybase ScriptTo create the database table schema for Sybase, use the following script:CREATE TABLE TMD_SERVER (

SERVER varchar(255) NOT NULL,DOMAIN varchar(255) NOT NULL,CLUSTER_NAME varchar(255) NULL,RELEASE varchar(32) NOT NULL,OS varchar(32) NOT NULL,WEB int NOT NULL,MAIL int NOT NULL,MAILROUTER int NOT NULL,DB int NOT NULL,NEWS int NOT NULL

)go

ALTER TABLE TMD_SERVER ADD CONSTRAINT TMD_PK1 PRIMARY KEY (SERVER)go

CREATE INDEX TMD_INDEX1 ON TMD_SERVER (SERVER)go

CREATE TABLE TMD_MON (RUN_DATE datetime NOT NULL,RUN_TIME varchar(8) NOT NULL,SERVER varchar(64) NOT NULL,PROBE varchar(64) NOT NULL,

A


A.

Techn

icalR

eference

PROBE_ARG varchar(255) NOT NULL,VALUE1 text NULL,VALUE2 varchar(192) NOT NULL

)go

ALTER TABLE TMD_MON ADD CONSTRAINT TMD_PK2 PRIMARY KEY (RUN_DATE, RUN_TIME, SERVER, PROBE,PROBE_ARG, VALUE2)go

CREATE INDEX TMD_INDEX2 ON TMD_MON (RUN_DATE, PROBE, PROBE_ARG)go

CREATE INDEX TMD_INDEX3 ON TMD_MON (RUN_DATE)go

CREATE TABLE TMD_REPORT(REPORT_NAME varchar(255) NOT NULL,REPORT_TYPE varchar(16) NOT NULL,REPORT_DEF text NOT NULL,WEB int NOT NULL,MAIL int NOT NULL,MAILROUTER int NOT NULL,DB int NOT NULL,NEWS int NOT NULL,REPORT_VER float NOT NULL

)go

Query Statements and Calculated ColumnsThis section describes the SELECT statements and calculated columns that the DominoDiscovery Guide uses in its queries to create the database.

Domino Monitors CubeTo create the flat files in comma-separated variables (.csv) format, use the following SQLqueries. Cognos Transformer uses one or more .csv files to create a multidimensional cube.

For the Domino Monitors Values query:SELECT

RUN_DATE,RUN_TIME,SERVER,PROBE,PROBE_ARG,VALUE1,VALUE2

FROMTMD_MON

WHERERUN_DATE

Between ?[Date Range].[Start Date] AND?[Date Range].[End Date]

ORDER BYSERVER,PROBE,PROBE_ARG,RUN_DATE,RUN_TIME

For Domino Server Info query:

44 Version 3.1.0

SELECTSERVER,DOMAIN,SERVER_ROLE,CLUSTER_NAME,RELEASE,OS,SERVER

FROMTMD_SERVER

Domino Trend CubeThe following SQL queries are used to create the flat files in comma-separated variables(.csv) format. One or more .csv files are used by the Cognos Transformer to create amultidimensional cube.SELECTSERVER,cc_converted_probe as PROBE,cc_PROBE_ARG,cc_Converted_Value_2,MIN(RUN_DATE) AS FIRST_DAY,MAX(RUN_DATE) AS LAST_DAY

FROM ?[DB Qualifier].domino_monitors.csv

GROUP BYSERVER,cc_converted_probe,cc_PROBE_ARG,cc_Converted_Value_2

Functions for Calculated ColumnsThis section describes the functions for the calculated columns used by Tivoli DecisionSupport for Lotus Domino:Function cc_converted_probe_Calculate()

On error Resume Next

Probe = Parameters("Probe Name Conversions").Values(Columns("PROBE_ARG")).Value

Select Case err.NumberCase 0

cc_converted_probe_Calculate = ProbeCase 15500 'Item not found in collection error

cc_converted_probe_Calculate = Columns("PROBE")Case Else

'All other errors are bad.errNumber = err.NumbererrSource = err.SourceerrDesc = err.DescriptionOn error GoTo 0 'Resets the error handler to handle the errorerr.Raise errNumber, errSource, errDesc

End Select

If cc_converted_probe_Calculate = "Mail" Thencc_converted_probe_Calculate = "Mail Average"

End If

End Function

Function cc_PROBE_ARG_Calculate()


A.

Techn

icalR

eference

cc_PROBE_ARG_Calculate = Columns("PROBE_ARG")

Dim tempValue, trimmedValue

tempValue = Columns("PROBE_ARG")trimmedValue = Trim(tempValue)

If trimmedValue = null or trimmedValue = "" or trimmedValue = " " Thencc_PROBE_ARG_Calculate = "<none>"

End If

End Function

Function cc_Converted_Value_1_Calculate()

Dim Value1, NumCheck

'This function converts VALUE1 (value returned by monitor) into a more useful format'To add more customized conversions, modify the example code commented out below

if Columns("cc_converted_probe") = "Server Availability" or Columns("cc_converted_probe")= "DominoServerAvailable" or Columns("cc_converted_probe") = "Server.Health.ASync" Then

if Columns("VALUE1") = "up" ThenValue1 = 100

ElseValue1 = 0

End If

ElseIf Columns("cc_converted_probe") = "Cluster Availability Status" Thenif Columns("VALUE1") = 0 Then

Value1 = 100Else

Value1 = 0End If

'ElseIf Columns("cc_converted_probe") = "PUT_IN_CORRESPONDING_PROBE_NAME" Then' if Columns("VALUE1") = "PUT_IN_VALUE1_TO_BE_CONVERTED" Then' Value1 = PUT_IN_VALUE1_TO_CONVERT_INTO' Else' Value1 = PUT_IN_VALUE1_TO_CONVERT_INTO' End If

ElseValue1 = Columns("VALUE1")

End If

NumCheck = IsNumeric(Value1)

If NumCheck = True Thencc_Converted_Value_1_Calculate = Value1

Elsecc_Converted_Value_1_Calculate = 0

End If

End Function

Function cc_Converted_Value_2_Calculate()

cc_Converted_Value_2_Calculate = Columns("VALUE2")

Dim tempValue, trimmedValue

46 Version 3.1.0

tempValue = Columns("VALUE2")trimmedValue = Trim(tempValue)

If trimmedValue = null or trimmedValue = "" or trimmedValue = " " Thencc_Converted_Value_2_Calculate = "<none>"

End If

End Function

Function cc_Hour_Calculate()

cc_Hour_Calculate = Hour(Columns("RUN_TIME"))

End Function

Function cc_business_hour_Calculate()

cc_business_hour_Calculate = MainEdObj.ResolveCategory\(Columns("cc_Hour"),Parameters("business hour"))

End Function

Function cc_AMPM_Calculate()

If (Columns("cc_Hour") < 12 ) thencc_AMPM_Calculate = "AM"

Elsecc_AMPM_Calculate = "PM"

End If

End Function

Function cc_Weekday_or_Weekend_Calculate()

tmd_day_in_week = Weekday(Columns("RUN_DATE"))

If tmd_day_in_week = vbSunday or tmd_day_in_week = vbSaturday thencc_Weekday_or_Weekend_Calculate = "Weekend"

Elsecc_Weekday_or_Weekend_Calculate = "Weekday"

End If

End Function

Function cc_Day_Of_Week_Calculate()

num = Weekday(Columns("RUN_DATE"))cc_Day_Of_Week_Calculate = WeekdayName(num)

End Function

Function cc_IsCumulativeMonitor_Calculate()

'this function returns a true/false boolean based on whether the monitor/monitor_argumentgives a cumulative value


A.

Techn

icalR

eference

'To add a new cumulative monitor, do the following:' 1) update the variable monMax' 2) update the dynamic array SelectionCriteriaArray (see example below)

Dim counterDim internalAnswerDim monMAX

counter = 0monMAX = 28 'update this to add new cumulative monitorinternalAnswer = false

Dim SelectionCriteriaArray( )

ReDim SelectionCriteriaArray(2, monMAX)

'example criteria - add in new probe name in SelectionCriteriaArray(0, X), new probeargument in SelectionCriteriaArray(1, X)'SelectionCriteriaArray(0, 0) = "cc_converted_probe"'SelectionCriteriaArray(1, 0) = "Probe_Arg"

'Actual criteriaSelectionCriteriaArray(0, 0) = "Domino"SelectionCriteriaArray(1, 0) = "Domino.Requests.Per1Hour.Total"

SelectionCriteriaArray(0, 1) = "Server"SelectionCriteriaArray(1, 1) = "Server.Trans.Total"

SelectionCriteriaArray(0, 2) = "Replication"SelectionCriteriaArray(1, 2) = "Replica.Failed"

SelectionCriteriaArray(0, 3) = "Replication"SelectionCriteriaArray(1, 3) = "Replica.Successful"

SelectionCriteriaArray(0, 4) = "Replication"SelectionCriteriaArray(1, 4) = "Replica.Cluster.%"

SelectionCriteriaArray(0, 5) = "Replication"SelectionCriteriaArray(1, 5) = "Replica.Docs.Added"

SelectionCriteriaArray(0, 6) = "Replication"SelectionCriteriaArray(1, 6) = "Replica.Docs.Deleted"

SelectionCriteriaArray(0, 7) = "Replication"SelectionCriteriaArray(1, 7) = "Replica.Updated"

SelectionCriteriaArray(0, 8) = "Replication"SelectionCriteriaArray(1, 8) = "Replica.Successful"

SelectionCriteriaArray(0, 9) = "NET.<PortName>"SelectionCriteriaArray(1, 9) = "%,BytesReceived"

SelectionCriteriaArray(0, 10) = "NET.<PortName>"SelectionCriteriaArray(1, 10) = "%,BytesSent"

SelectionCriteriaArray(0, 11) = "NET.<PortName>"SelectionCriteriaArray(1, 11) = "%,Sessions.Established.Incoming"

SelectionCriteriaArray(0, 12) = "NET.<PortName>"SelectionCriteriaArray(1, 12) = "%,Sessions.Established.Outgoing"

SelectionCriteriaArray(0, 13) = "NET.<PortName>"SelectionCriteriaArray(1, 13) = "%,Sessions.Established.Recycled"

SelectionCriteriaArray(0, 14) = "Mail Total"SelectionCriteriaArray(1, 14) = "MAIL.TotalRouted"

48 Version 3.1.0

SelectionCriteriaArray(0, 15) = "Mail Total"SelectionCriteriaArray(1, 15) = "MAIL.TotalFailures"

SelectionCriteriaArray(0, 16) = "Mail Total"SelectionCriteriaArray(1, 16) = "MAIL.Transferred"

SelectionCriteriaArray(0, 17) = "Mail Total"SelectionCriteriaArray(1, 17) = "MAIL.TransferFailures"

SelectionCriteriaArray(0, 18) = "Mail Total"SelectionCriteriaArray(1, 18) = "MAIL.TotalKBTransferred"

SelectionCriteriaArray(0, 19) = "MTA"SelectionCriteriaArray(1, 19) = "MTA.Smtp.TotalKBTransferred"

SelectionCriteriaArray(0, 20) = "MTA"SelectionCriteriaArray(1, 20) = "MTA.Smtp.TotalRouted"

SelectionCriteriaArray(0, 21) = "MTA"SelectionCriteriaArray(1, 21) = "MTA.Smtp.Transferred"

SelectionCriteriaArray(0, 22) = "MTA"SelectionCriteriaArray(1, 22) = "MTA.Smtp.TransferFailures"

SelectionCriteriaArray(0, 23) = "Mail Total"SelectionCriteriaArray(1, 23) = "Mail.TotalRouted"

SelectionCriteriaArray(0, 24) = "Mail Total"SelectionCriteriaArray(1, 24) = "Mail.TotalFailures"

SelectionCriteriaArray(0, 25) = "Mail Total"SelectionCriteriaArray(1, 25) = "Mail.Transferred"

SelectionCriteriaArray(0, 26) = "Mail Total"SelectionCriteriaArray(1, 26) = "Mail.TransferFailures"

SelectionCriteriaArray(0, 27) = "Mail Total"SelectionCriteriaArray(1, 27) = "Mail.TotalKBTransferred"

While ((internalAnswer = false ) and (counter < monMAX))if Columns("cc_converted_probe") = SelectionCriteriaArray(0,counter) ANDColumns("Probe_arg") = SelectionCriteriaArray(1,counter) _Then

internalAnswer = TrueEnd Ifcounter = counter + 1

Wend

cc_IsCumulativeMonitor_Calculate = internalAnswer

End Function

Function cc_Actual_Increment_Calculate()

If Columns("cc_IsCumulativeMonitor") = true _Then

cc_Actual_Increment_Calculate = TMDIncrementObj.TMD30Increment\Value(Columns("Probe"), Columns("Probe_Arg"), Columns("SUBSCRIBER"), \Columns("cc_Converted_Value_1"), Columns("cc_Converted_Value_2"))Else

cc_Actual_Increment_Calculate = Columns("cc_Converted_Value_1")End If

End Function


A.

Techn

icalR

eference

Function cc_ServerRole_Calculate()

comma = 0cc_ServerRole_Calculate = ""

If (Columns("WEB") = "1") thenIf (comma = 0) then

cc_ServerRole_Calculate = "Web"Else

cc_ServerRole_Calculate = cc_ServerRole_Calculate + "," + "Web"End Ifcomma = 1

End If

If (Columns("MAIL") = "1") thenIf (comma = 0) then

cc_ServerRole_Calculate = "Mail"Else

cc_ServerRole_Calculate = cc_ServerRole_Calculate + "," + "Mail"End Ifcomma = 1

End If

If (Columns("MAILROUTER") = "1") thenIf (comma = 0) then

cc_ServerRole_Calculate = "Mail Router"Else

cc_ServerRole_Calculate = cc_ServerRole_Calculate + "," + "Mail Router"End Ifcomma = 1

End If

If (Columns("DB") = "1") thenIf (comma = 0) then

cc_ServerRole_Calculate = "Database"Else

cc_ServerRole_Calculate = cc_ServerRole_Calculate + "," + "Database"End Ifcomma = 1

End If

If (Columns("NEWS") = "1") thenIf (comma = 0) then

cc_ServerRole_Calculate = "News"Else

cc_ServerRole_Calculate = cc_ServerRole_Calculate + "," + "News"End Ifcomma = 1

End If

End Function

Function cc_Forcast_0_Day_Average_Calculate()

cc_Forcast_0_Day_Average_Calculate = TMDPredictionObj.TMD30PredictionValue(15,Columns("SERVER"), Columns("Probe"), Columns("Probe_Arg"), Columns("cc_Converted_Value_2"),Query.Datasource)

If Columns("PROBE") = "Server Availability" or Columns("PROBE_ARG") ="Server.Availability.Index" or Columns("PROBE") = "DominoServerAvailable" orColumns("PROBE") = "Server.Health.ASync" or Columns("PROBE") = "Cluster AvailabilityStatus" or Columns("PROBE") = "CPU percent busy" Then

50 Version 3.1.0

If cc_Forcast_0_Day_Average_Calculate > 100 Thencc_Forcast_0_Day_Average_Calculate = 100

End IfEnd If

End Function





End IfEnd If

End Function





End IfEnd If

End Function

Domino.DLL FileThis section provides a detailed description of the functions used in the Domino.DLL file.

TMD30IncrementValue FunctionThe TMD30IncrementValue function runs when you specify in the calculated columncc_IsCumulativeMonitor_Calculate that the return value from a certain probe or probeargument is cumulative.

To convert the unsorted cumulative values to increment values, TMD30IncrementValuestores a previous value in a dynamic array for each server/probe/probe_arg/value2 valuecombination and returns the change in values, or increment. When the current data is lessthan the previous value, the current data is returned unchanged.

TMD30PredictionValue FunctionThe TMD30PredictionValue function finds the linear regression model for eachserver/probe/probe_arg/value2 value from the domino_monitors.csv file. Create this file


A.

Techn

icalR

eference

by building the Domino Monitors cube. This domino_monitors.csv file gives the projectedvalues at three default values of 1, 15, and 30 days. You can change these values. This trendis a simple straight line with the best fit to the data.

The domino_monitors.csv file is hard-coded in the select statement used in this function.Therefore, the ODBC text driver used in this cube must point to the validdomino_monitors.csv file (a copy of the export file from the Domino Monitors cube). Thisfunction uses module1 (from Tivoli Manager for Domino) and the RDO object.

The following is an extract of the code:'This is written for Tivoli Decision Support Domino Guide Version 3.1.0

'It consists of 2 main methods: TMD30IncrementValue and TMD30PredictionValue''IncrementValue is run when the user specified (in Tivoli Decision Administrator)'that the return value from a certain probe/probe arg is cumulative.'To convert these unsorted cumulative values to the more useful actual increments,'TMD30IncrementValue keeps a previous value in a dynamic array for each server/probe/probe_arg'combination and returns the actual delta'Functions used: HasRecordInPreviousValueArray' CreateRecordInPreviousValueArray' UpdatePreviousValueArrayAndReturnIncrement''PredictionValue finds the linear regression model for each server/probe/probe_arg'from the .csv file created from the export calling TMD30IncrementValue.'It gives the projected values for a time specified by the user'It uses the rdo object, as well as some objects defined in Module1'In the select statement domino_monitors.csv file is hard-coded.

'needed for both functionsPrivate pProbePrivate pProbeArgPrivate pServerPrivate pValue1Private pValue2

'needed for TMD30IncrementValuePrivate pValue1IsNull As BooleanPrivate i As IntegerPrivate j As IntegerPrivate pPositionInPreviousValueArray As IntegerPrivate pEmptySpaceInPreviousValueArray As IntegerPrivate pPreviousValueArray() As Variant

'needed for TMD30PredictionValuePrivate pTrendFileName As StringPrivate pSlope As DoublePrivate pIntercept As DoublePrivate pSlopePeakDay As DoublePrivate pInterceptPeakDay As DoublePrivate pSlopeNormalized As DoublePrivate pInterceptNormalized As DoublePrivate pMaxHourlyFactor As DoublePrivate pMaxDailyFactor As DoublePrivate pMaxDailySub As IntegerPrivate pMaxHourlySub As IntegerPrivate pStdDev As DoublePrivate pHostname As StringPrivate pFirstDay As StringPrivate pLastDay As StringPrivate pHistoryTable(181, 23) As DoublePrivate pMinimumsTable(181, 23) As Double

52 Version 3.1.0

Private pHourFactors(23) As DoublePrivate pDayFactors(6) As Double

'*************************************************************Public Function TMD30PredictionValue(sDate, _

sServer, _sProbe, _sProbeArg, _sValue2, _DataSource As Object) As Double

Dim iReturn As IntegerDim internalresult As Variant

'The Function Calculate Regression kicks off an SQL select statement to get the data'for the probe/probeArg/Server combinations and find the linear regression'The following If Statement determines when we should SELECT from the database again

iReturn = 0

If sServer <> pServer Or _sProbe <> pProbe Or _sProbeArg <> pProbeArg Or _sValue2 <> pValue2 _

ThenpServer = sServerpProbe = sProbepProbeArg = sProbeArgpValue2 = sValue2iReturn = CalculateRegression(DataSource)

End If

If iReturn = 0 Theninternalresult = pInterceptNormalized + (sDate * pSlopeNormalized)If internalresult < 0 Then

internalresult = 0End If

Elseinternalresult = -1

End If

TMD30PredictionValue = internalresult

End Function

'**********************************************************************Private Function CalculateRegression(ByVal DataSource As Object) As Integer

Dim rdc As rdoConnectionDim rd As rdoResultsetDim sSQL As StringDim sqlFirstDay As StringDim sqlLastDay As StringDim dDayNumber As DoubleDim dDailyAvg As DoubleDim dDailyPeak As DoubleDim dSumXY(2) As DoubleDim dSumX(2) As DoubleDim dSumY(2) As DoubleDim dSumX2(2) As DoubleDim dNumSamples(2) As DoubleDim dWeekValue(6) As Double


A.

Techn

icalR

eference

Dim dMaxValue As DoubleDim dMaxDay As DoubleDim dStartOfWeek As DoubleDim dEndOfWeek As DoubleDim dGrandMean As DoubleDim dWorkTotal As DoubleDim dWorkSamples As DoubleDim dWorkMean As DoubleDim dSumDeltas As DoubleDim dCalculatedValue As DoubleDim dNormalizedTrend(181) As Double

Dim dCurrentDay As String

Dim i As IntegerDim j As IntegerDim k As Integer

Dim NumCheckDim NewValue As Double

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' GOLDEN CODE'' Piggieback on the same datasource that was passed into' the function from the base query.'' Checks to see if the connection has been established.' This is done the very first time this function is' called.''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

On Error Resume Next

Set rdc = Datasources(DataSource.Name)

If Err <> 0 Then'need to make connectionOn Error GoTo 0Set rdc = ConnectToDataSource(DataSource)

End If

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' END GOLDEN CODE'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' EXAMPLE CODE'' Checks the ficticious RANGE table and sums all of the' rows in the table. Then, returns that amount.'' For example purposes only'' TWO IMPORTANT THINGS TO NOTE:'' 1. The ReturnDBQ function will add the database qualifier' to the front of the tablename.' 2. If you are using a string field in the where clause,' it is important that you wrap the string field with' SQLTickFix. This wrapper function will handle' database columns that may contain quotation marks in the' data. VERY IMPORTANT FOR STRING FIELDS ONLY.

54 Version 3.1.0

' 3. Note, numeric columns do not use the single quotation' mark or the SQLTickFix function.''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

On Error GoTo CalcError

'NC WARNING: escape function NOT SUPPORTED BY SYBASE ODBC Driver 3.01

sSQL = "SELECT RUN_DATE, cc_Hour, cc_Actual_Increment" & _" FROM " & ReturnDBQ(DataSource) & "domino_monitors.csv" & _" WHERE SERVER = '" & SQLTickFix(pServer) & "' " & _"AND cc_converted_probe = '" & SQLTickFix(pProbe) & "' " & _"AND cc_PROBE_ARG = '" & SQLTickFix(pProbeArg) & "' " & _"AND cc_converted_value_2 = '" & SQLTickFix(pValue2) & "' " & _"ORDER BY RUN_DATE"

Set rd = rdc.OpenResultset(sSQL, rdOpenForwardOnly)

dDayNumber = 0dDailyAvg = 0dDailyPeak = 0dMaxValue = 0dMaxDay = 0dStartOfWeek = 0dEndOfWeek = 0dGrandMean = 0dWorkTotal = 0dWorkSamples = 0dWorkMean = 0dSumDeltas = 0dCalculatedValue = 0

For i = 0 To 1dSumX(i) = 0dSumXY(i) = 0dSumX2(i) = 0dSumY(i) = 0dNumSamples(i) = 0

Next i

dStartOfWeek = 0dEndOfWeek = -7For i = 0 To 6

dWeekValue(i) = 0Next i

For i = 0 To 181For j = 0 To 23

pHistoryTable(i, j) = -1Next j

Next i

i = 0dCurrentDay = rd.rdoColumns("RUN_DATE")

While Not rd.EOF

''''''''''''''''''''''''''''''''''''''''''''''''''''''' Put all of the hourly values for the last 180 days' into a table to calculate the trend using the trending' algorithm'''''''''''''''''''''''''''''''''''''''''''''''''''''''


A.

Techn

icalR

eference

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Change to Support DB2: Michael Wilkerson'' i is expected to always be positive as pHistoryTable's' index goes from 0 to 181. dDayNumber is expected to' always be negative. This appears to be the case when' Oracle or Sybase is used. However, DB2 always returns' a positive number. The result of this is then that' i is negative and the assignments that follow attempt' to assign values outside the range of indexes that' pHistoryTable was created with.'' The modified line should ensure that i is always positive'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''i = (0 - dDayNumber)

If rd.rdoColumns("RUN_DATE") = dCurrentDay Then

'Check for non-numeric valuesNumCheck = IsNumeric(rd.rdoColumns("cc_Actual_Increment"))If NumCheck = False Then

NewValue = 0Else

NewValue = rd.rdoColumns("cc_Actual_Increment")End If

If rd.rdoColumns("cc_Hour") = 0 ThenpHistoryTable(i, 0) = NewValue

ElseIf rd.rdoColumns("cc_Hour") = 1 ThenpHistoryTable(i, 1) = NewValue



















56 Version 3.1.0





End If

Elsei = i + 1dCurrentDay = rd.rdoColumns("RUN_DATE")

'Check for non-numeric valuesNumCheck = IsNumeric(rd.rdoColumns("cc_Actual_Increment"))If NumCheck = False Then

NewValue = 0Else

NewValue = rd.rdoColumns("cc_Actual_Increment")End If

If rd.rdoColumns("cc_Hour") = 0 ThenpHistoryTable(i, 0) = NewValue






















ElseIf rd.rdoColumns("cc_Hour") = 22 Then


A.

Techn

icalR

eference

pHistoryTable(i, 22) = NewValueElseIf rd.rdoColumns("cc_Hour") = 23 Then

pHistoryTable(i, 23) = NewValueEnd If

End If

rd.MoveNext

Wend

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Close the recordset' Set the recordset and remote data object connection' object variables to nothing''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

rd.Close

Set rd = NothingSet rdc = Nothing

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Calculate normalized trend formula. Here is an overview of the' process:'' Step 1 - Calculate the grand mean of all the data' Step 2 - Calculate the average hourly factor for each hour' Step 3 - Calculate the average daily factor for each weekday' Step 4 - Remove the daily factors from the data and calculate a' trend line for the remaining average daily value' Step 5 - Calculate a standard deviation based on the trend line' and the hourly and daily factors.'' Note that this particular function will use at most 26 weeks' of data. This is because (unlike the other trend calculations)' we need to keep the data in an array to go through it multiple' times. This could probably be changed to dynamically size the' array based on information passed in or at least to set a limit' on how much of the array is processed (for performance).'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

''''''''''''''''''''''''''''''' Calculate grand mean''''''''''''''''''''''''''''''dWorkTotal = 0dWorkSamples = 0For i = 0 To 181

For j = 0 To 23' The check on the NULL value for the Domino Rollup should be only -1If (pHistoryTable(i, j) > -1) Then

dWorkTotal = dWorkTotal + pHistoryTable(i, j)dWorkSamples = dWorkSamples + 1

End IfNext j

Next iIf dWorkSamples > 0 Then

dGrandMean = dWorkTotal / dWorkSamplesElse

dGrandMean = 0End If

''''''''''''''''''''''''''''''

58 Version 3.1.0

' Calculate hourly factors''''''''''''''''''''''''''''''

For j = 0 To 23dWorkTotal = 0dWorkSamples = 0For i = 0 To 181

' The check on the NULL value for the Domino Rollup should be only -1If (pHistoryTable(i, j) > -1) Then

dWorkTotal = dWorkTotal + pHistoryTable(i, j)dWorkSamples = dWorkSamples + 1

End IfNext iIf dWorkSamples > 0 Then

dWorkMean = dWorkTotal / dWorkSamplesElse

dWorkMean = 0End IfpHourFactors(j) = dWorkMean - dGrandMean

Next j

pMaxHourlyFactor = 0For i = 0 To 23

If pHourFactors(i) > pMaxHourlyFactor ThenpMaxHourlyFactor = pHourFactors(i)pMaxHourlySub = i

End IfNext i

''''''''''''''''''''''''''''''' Calculate daily factors''''''''''''''''''''''''''''''dWorkTotal = 0dWorkSamples = 0For i = 0 To 6

dWorkTotal = 0dWorkSamples = 0For j = 0 To 175 Step 7

For k = 0 To 23If pHistoryTable((i + j), k) > -1 Then

dWorkTotal = dWorkTotal + pHistoryTable((i + j), k)dWorkSamples = dWorkSamples + 1

End IfNext k

Next jIf dWorkSamples > 0 Then

dWorkMean = dWorkTotal / dWorkSamplesElse

dWorkMean = 0End IfpDayFactors(i) = dWorkMean - dGrandMean

Next i

pMaxDailyFactor = 0For i = 0 To 6

If pDayFactors(i) > pMaxDailyFactor ThenpMaxDailyFactor = pDayFactors(i)pMaxDailySub = i

End IfNext i

''''''''''''''''''''''''''''''' Calculate normalized daily trend''''''''''''''''''''''''''''''

For i = 0 To 181


A.

Techn

icalR

eference

dWorkTotal = 0dWorkSamples = 0For j = 0 To 23


dWorkTotal = dWorkTotal + pHistoryTable(i, j) + pHourFactors(j)dWorkSamples = dWorkSamples + 1

End IfNext jIf dWorkSamples > 0 Then

dNormalizedTrend(i) = (dWorkTotal / dWorkSamples) _+ pDayFactors(i Mod 7)

ElsedNormalizedTrend(i) = 0

End IfNext i

For i = 0 To 181dDayNumber = (0 - i)If dNormalizedTrend(i) > 0 Then

dSumX(2) = dSumX(2) + dDayNumberdSumX2(2) = dSumX2(2) + (dDayNumber * dDayNumber)dSumY(2) = dSumY(2) + dNormalizedTrend(i)dSumXY(2) = dSumXY(2) + (dDayNumber * dNormalizedTrend(i))dNumSamples(2) = dNumSamples(2) + 1

End IfNext i

'''''''''''''''''' Calculate linear regression of normalized trend''''''''''''''''''i = 2If dNumSamples(i) > 0 Then

'Check on DenominatorIf ((dNumSamples(i) * dSumX2(i)) - (dSumX(i) * dSumX(i))) = 0 Then

'Test Debug.Print "Denom. = 0"pSlopeNormalized = 1

ElsepSlopeNormalized = ((dNumSamples(i) * dSumXY(i)) - (dSumX(i) * dSumY(i))) / _

((dNumSamples(i) * dSumX2(i)) - (dSumX(i) * dSumX(i)))

End IfpInterceptNormalized = (dSumY(i) / dNumSamples(i)) - (pSlopeNormalized * (dSumX(i) /dNumSamples(i)))

End If

''''''''''''''''''''''''''''''' Calculate standard deviation with hour and day factors removed''''''''''''''''''''''''''''''dSumDeltas = 0dWorkSamples = 0pStdDev = 0For i = 0 To 181

dDayNumber = (0 - i)For j = 0 To 23


k = i Mod 7dCalculatedValue = pInterceptNormalized + _

(pSlopeNormalized * dDayNumber) + _pHourFactors(j) + _pDayFactors(k)

dSumDeltas = dSumDeltas + _((pHistoryTable(i, j) - dCalculatedValue) | 2)

dWorkSamples = dWorkSamples + 1

60 Version 3.1.0

End IfNext j

Next iIf dWorkSamples > 0 Then

pStdDev = Sqr((dSumDeltas / dWorkSamples))End If

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' Exit back to the calling function'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

CalculateRegression = 0Exit Function

CalcError:

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' GOLDEN CODE'' This is the standard error handling code. DO NOT CHANGE' except by changing the Example1 and Class1 to your' appropriate project and class names.''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

If Not rd Is Nothing Then rd.CloseSet rdc = NothingSet rd = Nothing

If InStr(Err.Source, ":") Then 'not localErr.Raise Err.Number, "DominoFunctions.DominoClass.TMD30PredictionValue:" & Err.Source,Err.Description

ElseErr.Raise Err.Number, "DominoFunctions.DominoClass.TMD30PredictionValue:" & Err.Source,BuildErrorText("Error calculating Domino Trend")

End If

Exit Function

Resume

''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' END GOLDEN CODE''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

End Function

Public Function TMD30IncrementValue(sProbe, _sProbeArg, _sServer, _sValue1, _sValue2)

pProbe = sProbepProbeArg = sProbeArgpServer = sServerpValue1 = sValue1pValue2 = sValue2

pValue1IsNull = FalseIf ((pValue1 = Null) Or (pValue1 = "<none>")) Then

pValue1IsNull = TrueEnd If


A.

Techn

icalR

eference

If pEmptySpaceInPreviousValueArray = 0 ThenReDim pPreviousValueArray(4, 100000)

End If

If Not pValue1IsNull ThenIf Not HasRecordInPreviousValueArray Then

CreateRecordInPreviousValueArrayinternalresult = 0

Elseinternalresult = UpdatePreviousValueArrayAndReturnIncrement

End IfElse

internalresult = "<none>"End If

TMD30IncrementValue = internalresult

End Function

Private Function UpdatePreviousValueArrayAndReturnIncrement()

Dim answer As Integer

delta = pValue1 - pPreviousValueArray(4, pPositionInPreviousValueArray)returnresult = delta

If delta < 0 Thenreturnresult = pValue1

End If

pPreviousValueArray(4, pPositionInPreviousValueArray) = pValue1

UpdatePreviousValueArrayAndReturnIncrement = returnresult

End Function

Private Function HasRecordInPreviousValueArray() As Boolean

Dim j As IntegerDim answer As Boolean

answer = Falsej = 0

While ((answer = False) And (j <= pEmptySpaceInPreviousValueArray))

If pPreviousValueArray(0, j) = pServer And _pPreviousValueArray(1, j) = pProbe And _pPreviousValueArray(2, j) = pProbeArg And _pPreviousValueArray(3, j) = pValue2 _

ThenpPositionInPreviousValueArray = janswer = True

End If

j = j + 1Wend

62 Version 3.1.0

HasRecordInPreviousValueArray = answer

End Function

Private Function CreateRecordInPreviousValueArray()

pPreviousValueArray(0, pEmptySpaceInPreviousValueArray) = pServerpPreviousValueArray(1, pEmptySpaceInPreviousValueArray) = pProbepPreviousValueArray(2, pEmptySpaceInPreviousValueArray) = pProbeArgpPreviousValueArray(3, pEmptySpaceInPreviousValueArray) = pValue2pPreviousValueArray(4, pEmptySpaceInPreviousValueArray) = pValue1

pEmptySpaceInPreviousValueArray = pEmptySpaceInPreviousValueArray + 1

If pEmptySpaceInPreviousValueArray > 100000 ThenReDim Preserve pPreviousValueArray(4, pEmptySpaceInPreviousValueArray)

End If

End Function


A.

Techn

icalR

eference

64 Version 3.1.0

Index

Special Characters*.csv files, definition 3*.mdb files

definition 14setting the path to 14

*.ppr filesdefinition 14setting the path to 14

*.rpt filesdefinition 14setting the path to 14

<CubeName>_dt.txt file 18<CubeName>.mdc file 24<ModelName>.log file 23

BBusiness Hour parameter 30

Ccalculated columns, functions for 45Clean Database task 28Cognos PowerPlay 1Cognos Transformer 3commands, wtmdcleandb 28connectivity, data source, testing 17Crystal Reports 2cube, Domino Monitors

building automatically 21building manually 20dimensions

Date/Time 30Day of Week 31Hour 31Monitor 30Server 30testing 31

Domino Monitors Values querycalculated columns 29SQL queries 44

Domino Server Info querycalculated columns 29SQL queries 44

measuresAverage 31Maximum 31Minimum 31testing 31Total 31

cube, Domino Monitors (continued)parameters used to build 30scheduling builds 21updating the SQL query 19

cube, Domino Trendbuilding automatically 21building manually 20dimensions

Monitor 33Server 32

Domino Prediction querycalculated columns 32SQL queries 45

measures15 Days Later 3330 Days Later 33Next Day 33

scheduling builds 21cube builds

automatic 21manual 20scheduling 21testing 31troubleshooting 23viewing log files from 23viewing queries used for 28

cubesabout 1changing date range for 18creating a model 30, 32Date Range parameter, setting 18

customer support, contacting ix

Ddata sources

assigning to queries 17defining for ODBC drivers 13testing connectivity 17

database schema 27databases

purging records from 28types supported 12updating the SQL query for 19

date range, specifying for a cube 18Date Range parameter, setting 18Date/Time cube dimension, Domino Monitors cube 30Day of Week cube dimension, Domino Monitors cube 31directory structure of Domino Discovery Guide files 15Discovery Publisher 3DiscoveryInterf process 24disk space requirements for installation 12


Ind

ex

Domino Discovery Guideabout 1directory structure 15importing into Tivoli Decision Support 16installing 15uninstalling 22

Domino.DLL filecontents of 52TMD30IncrementValue function 51TMD30PredictionValue function 51

domino_monitors.csv file 29, 51Domino Monitors cube


Date/Time 30Day of Week 31Hour 31Monitor 30Server 30testing 31

Domino Monitors Values querycalculated columns 29SQL queries 44

Domino Server Info querycalculated columns 29SQL queries 44

measuresAverage 31Maximum 31Minimum 31testing 31Total 31

parameters used to build 30scheduling builds 21updating the SQL query 19

domino_monitors.mdc file 30, 32domino_server.csv file 29domino_trend.csv file 32Domino Trend cube


Monitor 33Server 32

Domino Prediction querycalculated columns 32SQL queries 45

measures15 Days Later 3330 Days Later 33Next Day 33

scheduling builds 21domino_trend.mdc file 32drivers, ODBC

creating 12defining the data source for 13

EEDAdmin.log file 23

Ffile types

*.csv, definition 3*.mdb

definition 14setting the path to 14

*.pprdefinition 14setting the path to 14

*.rptdefinition 14setting the path to 14

files<CubeName>_dt.txt 18<CubeName>.mdc 24<ModelName>.log file 23Domino.DLL

contents of 52TMD30IncrementValue function 51TMD30PredictionValue function 51

domino_monitors.csv 29, 51domino_monitors.mdc 30, 32domino_server.csv 29domino_trend.csv 32domino_trend.mdc 32EDAdmin.log file 23

functionsfor calculated columns 45TMD30IncrementValue 51TMD30PredictionValue 51

Hhardware requirements for installation 12Hour cube dimension, Domino Monitors cube 31

Iimporting the Domino Discovery Guide into Tivoli Decision

Support 16installation

database requirements 12Domino Discovery Guide 15hardware requirements 12software requirements 11

66 Version 3.1.0

Llog file for cube builds, viewing 23

Mmeasures

15 Days Later 3330 Days Later 33Average 31Maximum 31Minimum 31Next Day 33Total 31

messages“Cannot Execute” 24“Cube Cannot Be Built” 24“Error Building Cube” 23“load_graph_from_powercube” 24

Monitor cube dimensionDomino Monitors cube 30Domino Trend cube 33

monitors, how delta values are calculated 34

Nnetwork operation, specifying the path to shared source

files 14

OODBC drivers

creating 12defining the data source for 13

Pparameters

Business Hour 30Date Range 18, 30Probe Name Conversions 30used to build the Domino Monitors cube 30

PowerPlay 1PowerPlay Scheduler, using to schedule cube builds 21pplay.exe process 24Probe Name Conversions parameter 30processes

DiscoveryInterf 24pplay.exe 24

publicationsordering ixproviding feedback on ixrelated vii

publications (continued)viewing online viii

Publisher 3

Qqueries, assigning data sources to 17queries, cube

Domino Monitors Valuescalculated columns 29SQL queries 44

Domino Predictioncalculated columns 32SQL queries 45

Domino Server Infocalculated columns 29SQL queries 44

Rrecords, purging from a database 28reports

about 2incorrect values 24missing data 24missing data for certain measures 25report definitions 35troubleshooting 24

rollup toolabout 2schema scripts 27

Rover 3

Sscheduling cube builds 21schema, database 27schema scripts

about 27contents of 43

scripts, schemaabout 27contents of 43

Seagate Crystal Reports 2Server cube dimension

Domino Monitors cube 30Domino Trend cube 32

shared source files, specifying the path for 14software requirements for installation 11source files, shared, specifying the path for 14SQL query, adding to the Domino Monitors cube 19statistics, how delta values are calculated 34


Ind

ex

Ttables

TMD_MONcreating 27fields in 27

TMD_SERVERcreating 27fields in 27

Task Scheduler, using to schedule cube builds 21tasks, Clean Database 28technical support, contacting ixtime period, specifying for a cube 18Tivoli Decision Support

about 1importing Domino Discovery Guide into 16

Tivoli Discovery Administrator, about 3Tivoli Discovery Interface

about 2topics

How are the Domino servers performing? 4How busy are the Domino servers? 5What servers currently need the most attention? 6When and where are server problems occurring? 7When might servers begin experiencing problems? 8

Tivoli Task Server 3, 24Tivoli Workload Scheduler, using to schedule cube builds 21TMD_MON table

creating 27fields in 27

TMD_SERVER tablecreating 27fields in 27

TMD30IncrementValue function 51TMD30PredictionValue function 51topics

How are the Domino servers performing? 4How busy are the Domino servers? 5What servers currently need the most attention? 6When and where are server problems occurring? 7When might servers begin experiencing problems? 8

Transformer, Cognos 3troubleshooting

cube builds 23reports 24

Uuninstalling the Domino Discovery Guide 22

Wwtmdcleandb command 28

68 Version 3.1.0

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0674-00