tivoli decision support for lotus domino release...

Tivoli Decision Support for Lotus DominoRelease Notes

Version 2.0 November 9, 1999

Tivoli Decision Support for Lotus Domino Release Notes (November, 1999)

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

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli, Tivoli Management Environment, and Tivoli Decision Support.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.Notices

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

Tivoli Decision Support for Lotus Domino: Release Notes i

Contents

Contents

Release NotesProduct Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Lotus Domino Guide Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Topics and Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Domino Configuration for Manager for Applications Rollup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Software Requirements for the Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Hardware Requirements for the Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Supported Platforms and Databases for the Domino Configuration for Manager for Applications Rollup . . . 5Software Prerequisites for the Domino Configuration for Manager for Applications Rollup . . . . . . . . . . . . . 5

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Prerequisite Activities for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Determining Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Uninstalling Tivoli Decision Support for Lotus Domino 1.0 and Domino Rollup 1.0 . . . . . . . . . . . . . . . . . . . 7Installing the Manager for Applications Rollup 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installing the Domino Configuration for Manager for Applications Rollup 2.0. . . . . . . . . . . . . . . . . . . . . . . . 8Creating the TDS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Creating the RIM Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Configuring the Domino Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Distributing the Domino Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Configuring the Rollup Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11TDS Domino DataAggregation Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11TDS Domino RollupIntoDB Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Scheduling the Rollup Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting up an Oracle, Sybase, DB2 or MS/SQL Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installing TDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installing Cognos PowerPlay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Setting Up an ODBC Data Source Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Configuring the Shared Source File Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing and Configuring the Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing the Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Importing the Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Configuring the Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Assigning and Verifying a Data Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Setting the Date Range Parameter in the Cube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Building the Cubes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Scheduling the Cube Build Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Uninstalling or Reinstalling the Lotus Domino Guide and Domino Configuration for Manager for Applications Rollup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Domino Discovery Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Domino Configuration for Manager for Applications Rollup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Solving Cube Building Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

ii Version 1.0

Contents

Solving Report Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Addressing Year 2000 (Y2K) Readiness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Domino Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Seagate Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Product Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Domino Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Domino Configuration for Manager for Applications Rollup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Domino Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Cubes (Tivoli Discovery Administrator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Domino Monitors Cube . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Check of the Allowed Measures and Dimensions Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Domino Trend Cube. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Check of the Allowed Measures and Dimensions Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Software Defects, Limitations, and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Defects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Chapter 1.Release Notes

This document describes the Tivoli Decision Support for Lotus Domino Version 2.0 product. This product belongs to the family of Tivoli Decision Support Discovery Guides, and as such the product is referred to in this documentation as the Domino Discovery Guide, or more simply, the Lotus Domino Guide. These notes also describe the Domino Configuration for Manager for Applications Rollup 2.0, a prerequisite, companion product for the Lotus Domino Guide. These release notes are the most current information for the product and take precedence over all other documentation. This document is intended for systems administrators who are responsible for Domino installations.

Please review these notes thoroughly before installing or using this product.

These release notes include the following topics:

� System Requirements

� Prerequisite Activities for Installation

� Installing and Configuring the Domino Discovery Guide

� Uninstalling or Reinstalling the Lotus Domino Guide and Domino Configuration for Manager for Applications Rollup

� Troubleshooting

� Product Details

� Prerequisite and Related Documents

� Software Defects, Limitations, and Workarounds

� Contacting Customer Support

Product OverviewLotus Domino Guide works with the Tivoli Discovery Interface to provide information that guides the Domino or Tivoli system administrator in making decisions about Domino installations. Thus, this product (and similar Tivoli products for other applications) is called a discovery guide. Specifically, this product is referred to as the Domino Discovery Guide, or the Lotus Domino Guide.

The Lotus Domino Guide augments the functions the Tivoli Manager for Domino 2.0 product (Manager for Domino) to let you strategically manage your enterprise network. Where Manager for Domino provides a powerful, rule-based management application for Domino installations, the Lotus Domino Guide provides the IT manager of a business enterprise with an overview of how systems are running.

Lotus Domino Guide DescriptionThe Lotus Domino Guide displays data collected from Domino servers into reports that meet your needs by helping you make decision on your Domino environment. The content and detail of the reports depend on the type of data that can be collected, and on the database schema where this data

2 Version 1.0

is stored. In a Tivoli Management Region (TMR) environment, Tivoli Distributed Monitoring (DM) monitors are defined and distributed to collect data, and then the data is stored in a relational database. Once this data is in the relational database, the Lotus Domino Guide can extract and analyze the data through reports viewed in the Tivoli Discovery Interface.

Since the Lotus Domino Guide uses Domino-specific DM monitors for reporting, this guide requires the Manager for Applications Rollup 1.0 product to roll up data from these monitors into an RDBMS. This product, which is installed in a TMR environment, contains the aggregation and rollup tasks on all subscribed endpoints.

A separate product, the Domino Configuration for Manager for Applications Rollup 2.0, must also be installed to work with the Manager for Applications Rollup. This product provides scripts to create the database schema and the RIM object, and to install the default Domino monitors. The monitors are then distributed in a TMR environment and the rollup jobs are run nightly to collect and aggregate the data into the database table.

The Tivoli Discovery Administrator defines queries to extract data from this database table into a delimited text with columns file, or a comma-separated-values (CSV) file. The Cognos Transformer builds the multidimensional cube from this CSV file, which can then be reported by Cognos PowerPlay. Finally, once the guides and roles have been defined, you can use the Tivoli Discovery Interface to view these reports.

Topics and ViewsOn the Tivoli Discovery Interface, the database data collected for the Lotus Domino Guide is organized into topics and views. Selecting a view within a topic displays a report showing the results of a database query based on the topic and view selected. In addition to the report itself, each view displays a view description in the Hints panel the bottom of the interface. The Lotus Domino Guide provides the following topics and views:

Topic: How are the Domino Servers Performing?

Views in this topic show some basic Domino server performance statistics:

View Titles Addin Program Status

Calendar and Scheduling Statistics

Cluster Status

Disk Space Percent Free

Disk Space Statistics

Host Availability

Mail Average Statistics

Mail Calculated Totals

Notes Database Size

QOS.Mail.ISPY

Replication Statistics

Server Availability

Topic: How busy are the Domino servers?

Views in this topic show statistics that reflect the load on Domino servers:

View Titles CPU Utilization

Tivoli Decision Support for Lotus Domino: Release Notes 3

Domino Network Traffic

HTTP Requests

Memory Usage

Server Usage

Topic: What servers currently need the most attention?

This topic contains ranked views. That is, these view show how servers rank with other servers against specific metrics:

View Titles Bottom 25 Servers by Available Disk Space

Bottom 25 Servers by Server Availability

Top 25 Servers by CPU Utilization

Top 25 Servers by HTTP Requests

Top 25 Servers by Memory Allocated

Top 25 Servers by Total Mail Routed

Topic: When and where are server problems occurring?

The views in this topic use several different dimensions and measures to show statistics that help determine when and where server problems occur:

View Titles Domino Statistics by Day

Domino Statistics by Day of Week

Domino Statistics by Hour

Domino Statistics by Server

Domino Statistics by Server Profile

Topic: When might servers begin experiencing problems?

The view in this topic forecasts server behavior. The forecast includes averages and peaks for the next 30, 60 and 90 days for different metrics:

View Title Server Forecasted Averages and Peaks

Domino Configuration for Manager for Applications RollupThe Domino Configuration for Manager for Applications Rollup product performs the primitive data gathering functions needed by Tivoli Manager for Domino and Domino Discovery Guide customers.

This product schedules a nightly aggregating task that performs the following functions for each node subscribed to the aggregation task:

� Collects information (metrics) for all probes for which graphable data logs are available.

� Aggregates the collected metrics into hourly and daily minimum, maximum or average values.

� Writes the aggregated metrics into a flat file on the TMR.

� Schedules a rollup into a DB task that inserts only the TDS-specific data into a central RDBMS by means of RIM.

This product is packaged as a standard Tivoli installation file package. It includes one product image, tdsdom_20.image. Included in the module are the following items:

4 Version 1.0

� Installation scripts (invoked through the Tivoli Desktop or by means of the winstall CLI command)

� A set of RDBMS configuration scripts for initializing the database and schema

� Two rollup tasks:

• Aggregation task: Runs on subscribed endpoints to extract and aggregate log data.

• RollupIntoDB task: Inserts only the TDS related data into the RDBMS using the RIM interface.

These items are packed into one product image, tdsdom_20.image. Package installation and usage instructions for these listed items are provided in separate sections later in this document.

System RequirementsThis section describes the system requirements, including software and hardware, necessary to install and use the Lotus Domino Guide, as well as the requirements to install and configure the Domino Configuration for Manager for Applications Rollup product.

Software Requirements for the Domino Discovery GuideThe following prerequisite software must be installed on your system:

� Microsoft Windows NT 4.0 (Service Packs 4 and 5)

� Relational Database including:

� Tivoli Decision Support 2.0, 2.1

� Domino Configuration for Manager for Applications Rollup 2.0

If you are an administrator for the Lotus Domino Guide, you need the following additional components

� Tivoli Discovery Interface

� Tivoli Discovery Administrator

� Cognos PowerPlay

� Seagate Crystal Reports (only required when creating new reports)

� A version of Microsoft Access should be available, although not required, to run Tivoli Decision Support

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


� Seagate Crystal Reports (only required when creating new reports)

Database Type Database Version

Sybase 11.0.X All Tier 1

Oracle 7.3.X, 8.0.X All Tier 1

DB2 5.2 All Tier 1

MS/SQL 6.5 All Tier 1


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


� Cognos PowerPlay

Hardware Requirements for the Domino Discovery GuideTivoli products that support Windows, Windows 95, Windows NT, OS/2, and NetWare must be installed on an IBM PC AT-compatible machine. Tivoli does not support platforms (such as the NEC PC 98xx series) that are not 100% compatible with the IBM PC AT.

Each installation of the Domino Discovery Guide requires 10MB of disk space. That is, the installation process requires 10MB of disk space, although the installed Guide may not take up all 10MB of space.

Supported Platforms and Databases for the Domino Configuration for Manager for Applications Rollup

This product supports the following platforms:

� Solaris 2.4, 2.5 and 2.6

� AIX 4.x

� NT 4.0 (Service Packs 4 and 5)

Supported databases for this product include:

� Oracle 7.3.X, 8.0.X

� Sybase 11.x

� DB2 5.2 (except on Solaris)

� MS/SQL 6.5

Software Prerequisites for the Domino Configuration for Manager for Applications Rollup

This product has a dependency on the following products:

� Tivoli Framework Version 3.6.1

� Tivoli Framework Patch 3.6.1-TMF-0002 (for DB2 5.2 only)

� Tivoli Distributed Monitoring Version 3.6.1

� Distributed Monitoring Patch 3.6.1-DMN-0008




� Tivoli Manager for Applications Rollup 1.0

� Tivoli Manager for Domino Version 2.0

In addition, this product has a dependency on the following monitoring collections:

� Universal

� UNIX_Sentry

6 Version 1.0

� NT

Prerequisite and Related DocumentsRefer to the following TDS documentation when installing and using the Domino Discovery Guide:

Prerequisite Activities for InstallationThe sequence of prerequisite tasks to be performed before installing the Lotus Domino Guide include:

1. Determining Software RequirementsIf you have not previously installed the Domino Configuration for Manager for Applications Rollup 2.0, the list of steps also includes:

2. Uninstalling Lotus Domino Guide 1.0 and Domino Rollup 1.0

3. Installing the Manager for Applications Rollup 1.0

4. Installing the Domino Configuration for Manager for Applications Rollup 2.0

5. Creating the TDS Repository

6. Creating the RIM Object

7. Configuring the Domino Monitors

8. Distributing the Domino Monitors

9. Configuring the Rollup Job

10. Setting up an Oracle, Sybase, DB2 or MS/SQL ClientIf you have not previously installed TDS, the list of steps also includes:

11. Installing TDS

12. Installing Cognos PowerPlayOnce TDS is installed, the prerequisite activities include:

13. Setting Up an ODBC Data Source Connection

14. Configuring the Shared Source File Path

Once these prerequisite tasks have been completed, install the Lotus Domino Guide by using the following installation procedure.

Publication Description Location

Installation Guide Describes installing TDS and its components in stand-alone and network mode.

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

Decision Support User′s Guide

Describes TDS features and concepts and provides procedures for using the Tivoli Discovery Interface.

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

Administrator Guide Explains the features of the Tivoli Discovery Administrator component.

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


Determining Software RequirementsRefer to “System Requirements” on page 4 to determine the software requirements for the Domino Discovery Guide, as well as prerequisite and dependent software needed for the Domino Configuration for Manager for Applications Rollup 2.0. Make sure all the preliminary requirements are met for both products. You can find the required DM 3.6.1 patches on the Lotus Domino Guide CD-ROM. Locate and install them from this directory: D:\TDSLD\patches (where D: is the drive letter of the CD-ROM).

Uninstalling Tivoli Decision Support for Lotus Domino 1.0 and Domino Rollup 1.0

If you do not have an existing Tivoli Decision Support for Lotus Domino 1.0 or Domino Rollup 1.0 installation, then skip this step.

1. Use the Add/Remove Programs option on the Windows NT Control Panel to uninstall Tivoli Decision Support for Lotus Domino 1.0.

2. After uninstalling Version 1.0 of the Domino Guide, you must also uninstall Tivoli Decision Support (TDS) 2.0 if you will be using TDS 2.0 or TDS 2.1. Use the Add/Remove Programs option on the NT Control Panel to uninstall TDS 2.0.

3. If you had an existing TDS 2.0 installation with Cognos PowerPlay 5.21, and you plan to upgrade to TDS 2.1, then uninstall Cognos PowerPlay. Use the Add/Remove Programs option on the NT Control Panel to uninstall Cognos PowerPlay.

4. To uninstall the Domino Rollup 1.0, find the following file on the TMR Server:

$BINDIR/../generic_unix/TME/Notes/TDS/uninst_dr.sh

Run this script to uninstall the Domino Rollup 1.0

If you have created the domino_db database with the Domino Rollup 1.0, you can use this database for Lotus Domino Guide 2.0. Since the Domino Configuration for Manager for Applications Rollup 2.0 product uses the same database, you can use data from this database for the Version 2.0 Lotus Domino Guide. If you still have this database but do not want to use it for the Version 2.0 Lotus Domino Guide, then you must rename it, delete it, or use a different RDBMS for the Version 2.0 Lotus Domino Guide.

Installing the Manager for Applications Rollup 1.0Follow these steps to install this product on the TMR Server and Gateways. The installation is performed from the Tivoli Desktop.

1. Select Install —> Install Product from the Desktop menu to display the Install Product dialog.

2. If the Manager for Applications Rollup 1.0 product name is not listed in the Select Product to Install scrolling list, click Select Media, and then specify the path to the installation media (the CD-ROM drive).

3. Navigate to the D:\TDSLD\tdsmar_10.image directory (where D: is the drive letter of the CD-ROM drive) on the Tivoli Manager for Domino 2.0 CD-ROM.

4. Click Set Media and Close, and then select the following from the Select Product to Install list:

Manager for Applications Rollup 1.0

8 Version 1.0

5. Confirm that the names of the TMR Server and required Gateways are listed in the Clients to Install On scrolling list, or add them if they are not already listed.

6. Click Install & Close or Install to display the Product Install dialog. This dialog provides a list of operations that will take place and warns you of any problems that you may want to correct before installing. Software prerequisites are also checked at this point in the installation procedure.

7. Do one of the following:

a. Click Continue Install. The Product Install dialog shows status information and indicates when the installation is complete.

—OR—

b. Click Cancel to install at another time. Your settings will not be saved.

8. When the installation is complete, click Close.

Installing the Domino Configuration for Manager for Applications Rollup 2.0

Follow these steps from the Tivoli Desktop to install this product on the TMR server:

1. Select Install->Install Product from the Desktop menu to display the Install Product dialog.

2. If the Domino Configuration for Manager for Applications Rollup 2.0 is not listed in the Select Product to Install scrolling list, click Select Media, and then specify the path to the installation media (the CD-ROM drive).

3. Navigate to the D:\TDSLD\tdsdom_20.image directory (where D: is the drive letter of the CD-ROM drive) on the Tivoli Manager for Domino 2.0 CD-ROM.

4. Click Set Media & Close, and then select the following from the Select Product to Install list:

Domino Configuration for Manager for Applications Rollup 2.0

5. Confirm that the name of the TMR server is listed in the Clients to Install On scrolling list, or add them if they are not already listed.

6. Click Install & Close or Install to display the Product Install dialog. This dialog provides a list of the operations that will take place and warns you of any problems that you may want to correct before installing. Software prerequisites are also checked at this point in the process.

7. Click Continue Install. The Product Install dialog shows status information and indicates when the installation is complete.

-- OR --

To install at another time, click Cancel. Your settings will not be saved.

8. When the installation is complete, click Close.

A successful installation creates the TDS policy region on the Tivoli Desktop. This policy region contains a profile manager with sentry profiles, as well as a task library containing the rollup tasks.


Creating the TDS RepositoryBefore the Domino Configuration for Manager for Applications Rollup can store the aggregated metrics in an RDBMS, you must create the database or repository. Scripts have been provided to create the database and install the DOMINO_METRICS schema. If you had an existing Domino Rollup 1.0 installation with a DOMINO_METRICS table in an RDBMS, then verify that this table still exists in the domino_db database. If so then you can skip this step since the Domino database has already been created.

The RDBMS should have already been installed and configured on the TDBMS server and RIM host (if different). To create the TDS Domino database and table, run the dom_cr_db.sh script on the RIM host. This script can be found in the following directory on the TMR server:

$BINDIR/../generic_unix/TME/DominoMngr/TDS/db

This script prompts you for the database configuration information, such as the database name, server ID and user ID, and then creates the database and table.

Because the password could not be checked visually, you must make sure the database user’s password in both the RDBMS and the RIM object are consistent when you create the database. Otherwise the rollup task will fail to insert data into the database. The script that creates the RIM object sets a default password of DOMINO_TDS. This password for the database user and RIM object can be changed by using the dom_new_passwd.sh script once the RIM object has been configured.

To remove the TDS repository, run the dom_rm_db.sh script from the RIM host. Note that running this script completely removes the domino_db database and the DOMINO_METRICS table from the RDBMS. Thus, all data will be lost.

If you run the dom_rm_db.sh script for removing the TDS database and tables from Oracle RDBMS, you need stop the database server, manually remove the data file for this database, and then restart the server. Oracle does not provide the SQL statement to perform these functions. Leaving the data file in the database will interfere with the re-creation of the same database.

Creating the RIM ObjectAfter creating the TDS repository, configure the RIM object so the rollup task can write data to the repository. Follow these steps to create and configure the dom_rim RIM object.

1. If the current TMR server is the RIM host and RDBMS client/server, go to step 2. Otherwise, copy the dom_set_rim.sh file from the $BINDIR/../generic_unix/TME/DominoMngr/TDS/rollup directory on the TMR server to a temporary directory on the RIM host and RDBMS client/server.

2. From the directory that contains the file, run the dom_set_rim.sh script, and then fill in the following information to configure the dom_rim RIM object:

Database Vendor: Specify Oracle, Sybase, DB2 or MS/SQL

Database Home: Enter the location/path of the RDBMS client software on the RIM host. If the RDBMS server is the RIM host, this path is the directory where the RDBMS is installed.

Server ID: Enter an RDBMS-specific value

Database ID: Enter the name of the Rollup database in the RDBMS. The default name is domino_db, except for DB2, which is dom_db.

10 Version 1.0

Database User Specify a user name for the database. The default name is DOMINO.

The script should specify whether the RIM object was created successfully. You may also run the wrimtest -l dom_rim command to test the RIM object.

Once the module is successfully installed and the RDBMS is configured, the data aggregation and rollup jobs will run nightly. However, these jobs perform no aggregation or rollup unless monitors are created and distributed to the appropriate endpoints. The WebInspector graphable task logs all data from these monitors.

Configuring the Domino MonitorsAs part of the Domino Configuration for Manager for Applications Rollup installation process, a set of pre-configured Domino monitors is created to work with the Lotus Domino Guide. The Lotus Domino Guide supports specific Tivoli Manager for Domino 2.0 monitors, as well as some Universal, NT, and UNIX monitors. For a complete listing of all the supported monitors for the Lotus Domino Guide, refer to Domino Monitors in the Product Details section of this document.

The set of pre-configured Domino monitors can be found in the TDS Domino ProfileMgr profile manager in the TDS Domino policy region. Profiles are created for Domino 4.5, 4.6 and 5.0 servers. In these profiles, you can disable the monitors that you do not want reported by the Lotus Domino Guide, or add monitors that are not included in the pre-configured profiles. Remember to refer to the list of supported monitors when you add monitors to these profiles.

To run the supported Universal, NT, or UNIX monitors, you must create these monitors in a separate policy region. Since the TDS Domino ProfileMgr profile manager is not a dataless profile manager, you cannot distribute monitors to endpoints. Therefore, you must create a dataless profile manager with profiles for these monitors. In this dataless profile manager, you should be able to subscribe endpoints. Also, make sure that any additional monitors are configured with the ALWAYS response, and with the notification sent to the Create graphable log task in the Sentry Graphable Logs task library. Two points to consider when configuring the graphable log monitors:

� The data is aggregated with hourly minimum/maximum/average values. So, if the monitor is scheduled to run at intervals greater than 1 hour, some of the hourly values will be unset in the rolled up DB record. Setting such an interval does not affect the daily minimum/maximum/average calculations, but you may wish to consider scheduling the monitor to run more frequently if you wish to have more aggregated data.

� When you set up the Create graphable log task response, you set the size of the log file by specifying a Max Entries value. The default value is 1000. Each time a monitor fires (if configured with the ALWAYS response), a log file entry is written. Normally, the default log file size is sufficient. But, if you set up any monitor to run every minute, it is possible that by the time the nightly rollup task aggregates through the previous day’s data, the log file will have rolled over and some data loss would result. To prevent this situation from occurring for “one-minute-monitors,” change the default size (Max Entries) value to 1500 or higher.

Distributing the Domino MonitorsFollow these steps to distribute Domino monitors:

1. Subscribe the desired DominoServer endpoints or profile managers to the TDS Domino ProfileMgr profile manager. If you have created a dataless profile manager with Universal, NT, or UNIX monitors, subscribe the desired endpoints to that profile manager.


2. In the TDS Domino ProfileMgr profile manager, distribute the TDS Domino profiles to the appropriate DominoServer endpoints or profile managers. If you have created a dataless profile manager for Universal, NT or UNIX monitors, distribute these profiles tot he appropriate endpoints.

The Domino Configuration product requires that all Domino monitors be distributed to the DominoServer endpoints or to the profile manager containing one or more DominoServer endpoints. The only exception to this requirement is the NT_System CPU Percent Busy monitor (Percent Total Processor Time). If you run this monitor, then you should distribute it to the managed node/endpoint. This monitor is the only monitor that should not be distributed to the DominoServer endpoints.

Configuring the Rollup JobAfter distributing the monitors, you should modify the Rollup jobs to work with the appropriate endpoints.

TDS Domino DataAggregation Job

You can edit this job in one of two ways:

� From the command line, you can use the wsetjob CLI command.

� On the Tivoli desktop, you can right-click the job to open the Edit Job dialog.

Follow these steps to modify the TDS Domino DataAggregation job from the Tivoli desktop:

1. Open the TDS Domino TaskLib task library.

2. Edit the TDS Domino DataAggregation job.

3. In the Execution Target window, select the appropriate TMA endpoints (not theDominoServer endpoints) where the aggregation task should run. That is, select the TMA endpoints where the DominoServer endpoints reside. Also, if you havedistributed Universal, NT or UNIX monitors to endpoints, select these TMAendpoints.

4. Click Change and Close.

You can change parameters of the aggregation task. Points to consider when specifying parameters for the aggregation job:

� The output format must include standard out (-o 04 is mandatory). You can add the other formats. The default is 15.

� The job runs in the staged mode by default. This mode has been set for scalability, you can change the mode to parallel to fit your needs. You can also change the time-out value.

� The job output is mandatory and needs to be provided on the TMR server node. The location and the file name can be modified. The default location is the /tmp directory and the file name is dr_out.log. You should ensure that the /tmp directory exists on the server node before executing the aggregation task.

TDS Domino RollupIntoDB Job

The TDS Domino RollupIntoDB job should already be configured to run on the TMR server managed node. Therefore the parameters for this job should not be changed.

12 Version 1.0

Scheduling the Rollup Jobs

You can use the TME Scheduler to schedule these rollup jobs to run at different times. However, the TDS Domino DataAggregation job is set by default to run at 1:00 AM every day, since it only looks at data from the previous 25 hours, not including the last hour (that his, from 12:00AM yesterday to 12:00 AM today). Therefore, if the scheduled time for this job is changed, it will aggregate data based on when it was run, and not data from 12:00AM the previous midnight to 12:00 AM today. Changing the scheduled time of the job means that the data in the Domino Guide reports will not coincide with the actual times. Also remember that you must schedule the TDS Domino DataAggregation job to run and finish before you schedule the TDS Domino RollupIntoDB job to run.

Only one record of metrics (previous day) is inserted into the database for each DominoServer endpoint subscribed to the aggregation job. For performance reasons, make sure you do not subscribe endpoints more than once to the aggregation job. The TDS Domino RollupIntoDB job automatically re-runs against endpoints where the tasks failed due to timeout. Thus, metrics can be picked up and inserted into the RDBMS the following day.

Setting up an Oracle, Sybase, DB2 or MS/SQL ClientConsult your database administrator for the appropriate client configuration. Your system must have a valid client configuration for the ODBC connection that TDS uses to access your database.

Installing TDSRefer to the Tivoli Decision Support Installation Guide listed in ““Prerequisite and Related Documents” on page 6”. If you are installing TDS 2.0, you will also need to install the 2.0-TDS-0001 patch. You must first download it from the Tivoli web site at this URL:

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

Installing Cognos PowerPlayRefer to the Tivoli Decision Support Installation Guide listed in ““Prerequisite and Related Documents” on page 6”.

Setting Up an ODBC Data Source ConnectionFollow these steps to setup up an ODBC data source connection.

1. On the Control Panel, select the ODBC icon.

2. Select the System DSN tab.

3. Click Add.

4. Select the appropriate ODBC driver and then click Finish.

5. Type a meaningful name for this ODBC data source in the Data Source text box.

Note: Record the data source name. Use this data source name when you add a data source for the discovery guide in the Tivoli Discovery Administrator.

6. Type a description for the data source in the Description text box.

7. Type the data source server name in the Server Name text box.

8. Click OK.


Configuring the Shared Source File PathBefore using the Tivoli Discovery Administrator or the Tivoli Discovery Interface, you must configure them to locate certain files (called source files) that are stored on your system (the local system) or on the network. If you installed TDS by means of the stand-alone installation option, your source files are on your system. For other installations, the source files usually reside on a network server. Specify the path to the source files when you start the Tivoli Discovery Administrator for the first time.

To set the shared source file path, follow these steps:

1. Select View->Options.

2. Click the General tab on the Options dialog.

3. In the Network box, type the name of the drive (and folder, if appropriate) that contains the following folders:

Data

Reports

4. Click OK.

Installing and Configuring the Domino Discovery GuideThis section describes the procedure for installing the Lotus Domino Guide discovery guide. The procedure can be summarized as follows:

1. Installing the Discovery Guide

2. “Importing the Discovery Guide” on page 14

3. “Configuring the Discovery Guide” on page 14

Installing the Discovery GuideInstall the discovery guide on the TDS server. Follow these steps to install the guide from the Lotus Domino Guide product CD-ROM.

1. Select Run from the NT Start menu.

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

d:\TDSLD\Tivoli Decision Support for Lotus Domino 2.0\NTimage\setup.exe

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

3. At the Installation dialog, click Lotus Domino Guide 2.0.

The discovery guide files are placed in the following Tds installation directories:

\Cubes\Install\Models\Reports

The online documentation is installed in this directory:

\Guide Docs\Lotus Domino Guide

14 Version 1.0

Importing the Discovery GuideImport the Discovery Guide into TDS by using the Tivoli Discovery Administrator. Follow these steps:

1. Start the Tivoli Discovery Administrator.

2. Click Import on the Decision Support Guides menu to display the Import/Install dialog.

Note: If a discovery guide has not been installed on your system, you are prompted to import an installed discovery guide, and then to connect to a data source. Refer to “Running the Tivoli Discovery Administrator for the First Time” in the Tivoli Decision Support Administrator Guide.

3. Select Lotus Domino Guide 2.0 on the Import dialog, and then click Yes.

4. When prompted to add a data source, click Yes to start the Add Data Source task guide.

5. Select the Data Source Name from the drop-down list, and then click Next.

6. Enter the database User Name and Password, and then click Next

The default User Name for the Domino Configuration for Manager for Applications Rollup database connection is:

DOMINO

The default Password is:

DOMINO_TDS

7. Enter the database Qualifier, and then click Next

The default database Qualifier for the TDS database connection is:

DOMINO

Note: Contact the database administrator for additional information if the default settings were not used.

8. Select Lotus Domino on the Import Decision Support Guides dialog box, and then click OK.

Configuring the Discovery GuideConfiguring a discovery guide involves the following tasks:

1. Assigning and Verifying a Data Source

2. Setting the Date Range Parameter in the Cube

3. Building the Cubes

4. Scheduling the Cube Build Task

Assigning and Verifying a Data Source

Complete the discovery guide installation by assigning and verifying a data source. This task is accomplished from the Tivoli Discovery Administrator console. Follow these steps:

1. Select the Domino Monitors cube on the Tivoli Discovery Administrator console.

2. Select Assign Data Sources from the Data Sources menu.

3. Select the data source from the drop-down list.

4. Select the following queries, and then click OK:


domino_calc_valuesdomino_cluster_valuesdomino_mb_valuesdomino_orig_valuesdomino_trend_calcdomino_trend_mbdomino_trend_orig

5. Click the Data Sources folder.

6. Right click on the data source you just assigned, and then select Test Connectivity.

7. If the Tivoli Discovery Administrator message dialog box appears with the message:

Error connecting to Data Source – DataSourceName

click Details to display more information about the connection error. Click OK, and then verify the data source definition, userid, password, and qualifier.

If the connection is successful, the Test Data Source dialog box displays the message Connection Successful.

Setting the Date Range Parameter in the Cube

Both the Domino Monitors and the Domino Trend cubes contain a Date Range parameter. By default, this parameter is set to Rolling 6 Months. You can change this parameter by right-clicking the parameter value, and then selecting Set Values from the context menu.

Building the Cubes

Cube building is a resource-intensive activity. Thus, while you should schedule regular cube builds, schedule them during periods of decreased database activity. Adjust your cube date range to optimize the time required to build a cube. This task is performed from the Administrator panel of the Tivoli Discovery Administrator console. Follow these steps to build a cube:

1. Double-click Cubes on the Administrator panel

2. Right-click on the Domino Monitors cube, and then select Build. The Confirm Cube Build dialog box displays the date ranges.

3. Click Yes.

TDS connects to your database and retrieves the records specified in your query. The size of your data and the network speed affect the time required to retrieve all records. Use the status bar to check the status of the processing. The Cube Transform Status dialog box displays processing messages.

4. Review the processing messages for any errors. If an error generates an error dialog box, review the error, and then click OK.

5. Click Close.Repeat the previous steps for the Domino Trend cube, and then complete the task for both cubes as follows:

6. Start the Tivoli Discovery Interface

7. Use the discovery guide to review the views for each topic (a topic is presented as a question).

For more information about how to use the Tivoli Decision Support Discovery Interface, see the Tivoli Decision Support User’s Guide document described in ““Prerequisite and Related Documents” on page 6”.

16 Version 1.0

Scheduling the Cube Build Task

You must periodically rebuild the cube to update your cube data. The build process can be scheduled to build automatically at regular intervals (for example, schedule nightly cube builds). Stagger the start times for your cube builds for improved performance. Also, make sure the cube builds are scheduled after the TDS RollupIntoDB job runs since this job must finish in order to have updated data for the cubes.

To schedule the cube builds, refer to the Tivoli Decision Support Administrator Guide listed in “Prerequisite and Related Documents”.

Uninstalling or Reinstalling the Lotus Domino Guide and Domino Configuration for Manager for Applications Rollup

The Domino Discovery Guide uses an NT process for uninstalling on TDS 2.0, and uses the Delete feature for TDS 2.1. The Domino Configuration for Manager for Applications Rollup uses a script.

Domino Discovery GuideIf you are using TDS 2.0, you must use the Add/Remove Programs option on the NT Control Panel to uninstall a discovery guide. To reinstall the discovery guide on TDS 2.0, you must first uninstall TDS 2.0 by using thes Add/Remove Programs option.

To uninstall the Domino Guide on TDS 2.1, open the Tivoli Discovery Administrator and go to the Decision Support Guides folder. Right-click on the Lotus Domino guide, and then select Delete.

To reinstall the Domino Guide on TDS 2.1, you can go through the normal guide installation steps in the “Installing and Configuring the Domino Discovery Guide” section on page 13.

Domino Configuration for Manager for Applications RollupThis product uses an uninstall script. The following file:

$BINDIR/../generic_unix/TME/DominoMngr/TDS/dom_uninst.sh

uninstalls the tdsdom_20.image. This script removes the TDS installation scripts, rollup tasks, RDBMS configuration scripts, as well as the dom_rim RIM object. However, this uninstall script does not remove the domino_db database and the DOMINO_METRICS table. The dom_rm_db.sh script removes these two items.

Before running the uninstall script, remove all Domino Discovery Guide monitors from the subscribers. You can unsubscribe the endpoints from the profile managers by using the Delete Profile Copies option. After unsubscribing the endpoints, run the uninstall script.

TroubleshootingThis section describes troubleshooting tips for the following areas:

� Solving Cube Building Problems

� Solving Report Problems

� Addressing Year 2000 (Y2K) Readiness


Solving Cube Building ProblemsCube building has the following problems and possible solutions:

� What do I do when the Tivoli Discovery Administrator message appears:

Error building cube.

and the Details information includes:

Error 91 - Error getting query parameters; object variable or with block variable not set.

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

� During use of the Tivoli Discovery Interface, what does it mean when a Cognos PowerPlay report icon appears with a Cannot Execute indicator, and report cannot be opened?

The cube is unavailable. Contact the TDS administrator and request that the cube be built.

� Why does the Tivoli Discovery Administrator report that a cube could not be built?

The cube you are attempting to rebuild is currently in use, and TDS cannot overwrite this cube with the new cube data. Close all copies of the Tivoli Discovery Interface that are running. Copy the CubeName.mdc file from the Tds\Cubes\Temp directory to the Tds\cubes directory, where Tds\ is the TDS installation directory.

The queries returned insufficient data to build a cube. Verify your queries.

� If all the Tivoli Discovery Interface processes are closed, why doesn’t the cube build?

A copy of Cognos PowerPlay may still be running in the background. This can also prevent cube builds from succeeding. Open the Task manager. If you find the process pplay.exe, end the process and rebuild the cube.

� Why don’t the cubes build automatically overnight?

For scheduled cube builds to occur, the Cognos Scheduler must be running. Start Cognos Scheduler. Review the schedule definitions in Cognos Scheduler and the Tivoli Discovery Administrator.

� How are relative dates calculated in a report?

The Date Range parameter for a cube determines the time period that you want to examine. This 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 the Date Range parameter and the CubeName_dt.txt to set the current period in the following cases:

• Explicit Date RangeEnd date

Calculated ValuesCalculated end date

No Date Range parameter in cubeDate the cube is built

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

• Use the Date Range parameter, but do not use the CubeName_dt.txt. This selects only records between the specific start date and end date, and sets the current period to the most recent date in the data.

18 Version 1.0

• Do not use either the Date Range parameter or the CubeName_dt.txt. This selects all the records, and sets the current period to the most recent date in the data.

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

For more information on how to set the current period and select records, see the TDS Administrator Guide

Solving Report Problems The following problems can occur:

� In TDS 2.0, what should I do when the error message “Overflow” appears in the Discovery Interface?

The message occurs because the 2.0-TDS-0001 patch has not been installed. Download and install this patch.

� What should I do when the error message load_graph_from_powercube appears?

The cube has not been built. Build the cube.

� I tried to open a report, but the Tivoli Discovery Interface gets stuck at the wait cursor.

The Tivoli Discovery Interface may have lost its connection to the Cognos PowerPlay task. Close the Tivoli Discovery Interface and Cognos PowerPlay. Restart the Tivoli Discovery Interface and the reports should open.

� I opened a report, but it contained no data.

There may be data in the report, but there is no data in the drill-down. The report may be filtered on a dimension. Look at the dimension bar and check if any of the values, especially the date dimension, are drilled down.

� The Crystal Reports do not have a left margin.

The type of printer attached to a workstation influences the alignment of Crystal Reports. Try disconnecting the printer and restarting TDS.

� Why do some values look “off” in reports?

First, make sure that each monitor is running and has returned a value. For instance, if no replication monitors have been distributed from the TDS monitors, then no replication data will show in the “Replication Statistics” report, even though this report shows some data. Second, make sure that all cube builds finished successfully. Some data may be missing if the cube builds did not finish. Third, make sure that all levels in the dimension line match what those shown in the “Report Definitions” table on page 36. For instance, check to see if the correct monitor is showing in the By Monitor dimension.

� Why am I not getting data from all my measures?

You can view hourly, daily average, daily minimum, daily maximum and daily total values for each report. However, not all monitors have values for each measure, since report data is calculated based on the monitor type. For instance, the Mail.TotalRouted monitor only calculates and reports hourly and daily total values. This monitor has no daily average, daily minimum, or daily maximum values.

� Why are the maximum or minimum daily values significantly off compared to all the hourly average values?

The hourly values correspond either to an hourly average or an hourly total, based on the monitor that is being reported. The maximum and minimum values for each hour are not


shown. Therefore, if a monitor is run frequently to produce several values for each hour, one value may be much higher or lower than the others. This value may become the daily maximum or minimum. However, only the hourly average value is shown.

Addressing Year 2000 (Y2K) ReadinessThis information does not constitute a certification or warranty, express or implied, of any kind.

Readiness information is provided for your database product and for Seagate products such as Crystal Reports.

Domino Database

To ensure that TDS continues to select data correctly after January 1, 2000, the database used to store historical data must be Y2K certified. Contact your systems administrator and your database vendor if you have any questions concerning the Y2K readiness of your database.

Seagate Crystal Reports

For information regarding the Y2K-readiness of Seagate Crystal Reports, refer to the Seagate Software web site at this URL: http://www.seagatesoftware.com

Product DetailsThis section describes some of the details of Lotus Domino Guide features and functions, and lists pointers to information supplied on the Tivoli Discovery Interface for this discovery guide.

Data StructureThe Domino Configuration for Manager for Applications Rollup consists of scripts for creating the database schema and tasks for the rollup. After this product has been installed, the database schema scripts are run on the Oracle, Sybase, DB2 or MS/SQL database to create a DOMINO_METRICS table. Once the TDS monitors are distributed, the rollup tasks aggregate and store the data into this table in the relational database. Domino monitors will have to be created for reporting.

Domino Database Schema

Because the Lotus Domino Guide uses Domino monitors to collect data, the guide also uses the database schema supplied with the Domino Configuration product.

The TDS table DOMINO_METRICS contains the following columns:

Column Name Field Type Description

COLLECTION_DATE date Date when the Domino data was aggregated. The field type varies according to the vendor DB.

DT_STAMP integer The Unix timestamp that is converted in date by means of a trigger

HOSTNAME varchar(32) Host name where the aggregation job runs

ENDPOINT varchar(32) Endpoint name where the aggregation job runs

PROFILE_COLLECTION varchar(48) Name of the profile where the monitors are created

20 Version 1.0

PROBE_COLLECTION varchar(32) SENTRY monitoring collection name

PROBE varchar(32) SENTRY monitoring source

PROBE_DESC varchar(32) Monitor description

PROBE_ARG varchar(64) Unique monitor name

MIN_VALUE_00 float Minimum monitor value during the hour

MAX_VALUE_00 float Maximum monitor value during the hour

AVG_VALUE_00 float Average monitor value during the hour





























22 Version 1.0

The SQL scripts used to define the database user and create this schema are supplied with the Domino Configuration product. A separate SQL script exists for the different databases. The database table schema for Sybase is created by using the a script named DOMINO_METRICS.

The script for the other database supported on this version of the guide presents a few differences relative mainly to the date datatype, to syntax of the end of line (“;” instead of “go”), to the use of the datatype varchar2 instead of varchar, to the trigger and indices creation.

You can view these scripts from the Tivoli Discovery Administrator console after you install the Lotus Domino Guide. The contents of these scripts are also available in a detailed technical section that is appended to the Technical Reference version of this document. This Technical Reference version is available on the Tivoli Customer Support web site. Point your browser to http://www.tivoli.com/support and follow the instructions to the Product Manuals section, where you can download this document in two forms: the same PDF document that is shipped on the product CD-ROM, and the Technical Reference version of the PDF file that contains a section that presents more detailed technical information.

Domino Configuration for Manager for Applications Rollup

Since the Lotus Domino Guide uses Domino monitors for reporting, it uses the rollup tasks supplied by the Domino Configuration product. The rollup scripts consist of a nightly job that collects metrics from all probes installed in a TMR for which graphable data logs are available. The three actions of the rollup job include:

� Collecting the raw data with the Domino monitors from the subscribed endpoints.

� Processing the raw data and converting them into the required measurements shown the database tables.

� Storing the measurement metrics into the RIM supported databases: Oracle, Sybase, DB2 or MS/SQL.









MIN_DAILY_VALUE float Minimum monitor value during the day

MAX_DAILY_VALUE float Maximum monitor value during the day

AVG_DAILY_VALUE float Average monitor value during the day

MIN_HOURLY_AVG float Minimum of average monitor value during hour

MAX_HOURLY_AVG float Maximum of average monitor value during hour



The rollup job must run daily since it only looks for the previous day’s data. Currently, the job runs on the endpoints for which graphable data logs exist, and then the data is sent to the RIM database through the TMR server.

Domino Monitors

This section describes the monitors that are supported by the Lotus Domino Guide. These supported monitors include specific Domino monitors, as well as some Universal, NT, and UNIX monitors.

For the following monitors, the hourly and daily totals are calculated based on each hourly value reported from the Domino server, so the monitoring interval should NOT be set more frequently than 1 hour. Setting the interval for these monitors on a more frequent interval may result in inaccurate values when reported:

� Domino.Requests.Per1Hour� MAIL.TotalRouted� MAIL.TotalFailures� MAIL.Transferred� MAIL.TransferFailures� Mail.TotalKBTransferred� MTA.Smtp.TotalKBTransferred� NET.X.BytesReceived� NET.X.BytesSent� NET.X.Sessions.Established.Incoming� NET.X.Sessions.Established.Outgoing� NET.X.Sessions.Established.Recycled� Replica.Cluster.X� Replica.Docs.Added� Replica.Docs.Deleted� Replica.Docs.Updated� Replica.Failed� Replica.Successful� Server.Trans.Total� MTA.Smtp.TotalRouted� MTA.Smtp.Transferred� MTA.Smtp.TransferFailures

Note: For the network monitors, the X represents the port name. For the Replica.Cluster monitor, X represents the appropriate monitor’s name

For the following monitors, hourly and daily averages are calculated and reported, so these monitors can be set a more frequent interval than 1 hour:

� Calendar.Total.All.Appts.Reservations� Calendar.Total.All.Users.Resources� Calendar.Total.Appts� Calendar.Total.Reservations� Calendar.Total.Resources� Calendar.Total.Users� ClusterStatus� Notes database file size monitors� Host� Disk.X.Free� Disk.X.Size

24 Version 1.0

� MAIL.Dead� MAIL.Waiting� MAIL.WaitingRecipients� Mail.AverageDeliverTime� Mail.AverageSizeDelivered� Mail.AverageServerHops� Mailn.Dead� Mailn.Waiting� Mailn.Total� Mem.Allocated� Mem.Free� PcrTotCpuTime� QOS.Mail.ISpy.<servername>.ResponseTime� avgcpubusy� Server.Cluster.X� Server.Sessions.Dropped� Server.Trans.PerMinute� Server.Trans.PerMinute.Peak� Server.Users� MTA.Smtp.Dead� MTA.Smtp.Waiting� DominoServerAvailable

For the Lotus Domino Guide to calculate Domino server availability, the DominoServerAvailable monitor should be run for each Domino server. The value returned from this statistic is used to determine the server availability percentage for each Domino server.

For the database size monitors, a monitor must be created for each Notes database that will be reported. A file size monitor can be created for any Notes database on that Domino server. For the disk space monitors, disk space free and disk space size monitors are supported for Domino servers on Unix and NT platforms.

The following Domino disk statistics are supported for reporting with the Lotus Domino Guide:

� Disk./.Free� Disk./.Size� Disk./data.Free� Disk./data.Size� Disk.C.Free� Disk.C.Size� Disk.D.Free� Disk.D.Size� Disk.E.Free� Disk.E.Size

The following tables list the available monitors by collections. The description for each monitor includes a suggested monitor’s interval. For the DominovX.X Collection, X.X represents the server version 4.5, 4.6 or 5.0

Domino vX.X Collection

Monitor Name Monitor ArgumentSuggested

Interval

Category (Source): Disk (Disk)


/XFree XFree 30 minutes

/XSize XSize 30 minutes

Category (Source): Domino (Domino)

Domino.Requests.Per1Hour Domino.Requests.Per1Hour 60 minutes

Category (Source): Calendar (Calendar)

Calendar.Total.All.Appts.Reservations Calendar.Total.All.Appts.Reservations 30 minutes

Calendar.Total.All.Users.Resources Calendar.Total.All.Users.Resources 30 minutes

Calendar.Total.Appts Calendar.Total.Appts 30 minutes

Calendar.Total.Reservations Calendar.Total.Reservations 30 minutes

Calendar.Total.Resources Calendar.Total.Resources 30 minutes

Calendar.Total.Users Calendar.Total.Users 30 minutes

Category (Source): Mail Total Monitors (Mail)

MAIL.TotalRouted MAIL.TotalRouted 60 minutes

MAIL.TotalFailures MAIL.TotalFailures 60 minutes

MAIL.TotalKBTransferred MAIL.TotalKBTransferred 60 minutes

MAIL.Transferred MAIL.Transferred 60 minutes

MAIL.TransferFailures MAIL.TransferFailures 60 minutes

Category (Source): Mail Total Monitors (MTA)

MTA.Smtp.TotalKBTransferred MTA.Smtp.TotalKBTransferred 60 minutes

MTA.Smtp.TotalRouted MTA.Smtp.TotalRouted 60 minutes

MTA.Smtp.Tranferred MTA.Smtp.Tranferred 60 minutes

MTA.Smtp.TransferFailures MTA.Smtp.TransferFailures 60 minutes

Category (Source): Mail Average Monitors (Mail)

MAIL.Dead MAIL.Dead 30 minutes

MAIL.Waiting MAIL.Waiting 30 minutes

MAIL.WaitingRecipients MAIL.WaitingRecipients 30 minutes

Mail.AverageDeliverTime Mail.AverageDeliverTime 30 minutes

Mail.AverageSizeDelivered Mail.AverageSizeDelivered 30 minutes

Mail.AverageServerHops Mail.AverageServerHops 30 minutes

Category (Source): Mail Average Monitors (MTA)

MTA.Smtp.Dead MTA.Smtp.Dead 30 minutes

MTA.Smtp.Waiting MTA.Smtp.Waiting 30 minutes



Interval

26 Version 1.0

Category (Source): Memory (Memory)

Mem.Allocated Mem.Allocated 30 minutes

Mem.Free Mem.Free 30 minutes

Category (Source): NET (NET.<PortName>)

NET.X.BytesSent NET.X.BytesSent 60 minutes

NET.X.BytesReceived NET.X.BytesReceived 60 minutes

NET.X.Sessions.Established.Incoming NET.X.Sessions.Established.Incoming 60 minutes

NET.X.Sessions.Established.Outgoing NET.X.Sessions.Established.Outgoing 60 minutes

NET.X.Sessions.Recycled NET.X.Sessions.Recycled 60 minutes

Category (Source): Server (Server)

Server.Cluster.X Server.Cluster.X 30 minutes

Server.Sessions.Dropped Server.Sessions.Dropped 30 minutes

Server.Trans.PerMinute Server.Trans.PerMinute 30 minutes

Server.Trans.PerMinute.Peak Server.Trans.PerMinute.Peak 30 minutes

Server.Trans.Total Server.Trans.Total 60 minutes

Server.Users Server.Users 30 minutes

Category (Source): DominoServerAvailable (Server Availability)

Percentage Available 30 minutes

Category (Source): Replication

Replica.Cluster.X Replica.Cluster.X 60 minutes

Replica.Failed Replica.Failed 60 minutes

Replica.Docs.Added Replica.Docs.Added 60 minutes

Replica.Docs.Deleted Replica.Docs.Deleted 60 minutes

Replica.Docs.Updated Replica.Docs.Updated 60 minutes

Replica.Successful Replica.Successful 60 minutes

Category (Source): Cluster Status (Cluster Availability Status)

ClusterStatus ClusterStatus 30 minutes

Category (Source): Mailn.box (Mailn.box)

Mailn.dead Mailn.dead 30 minutes

Mailn.waiting Mailn.waiting 30 minutes

Mailn.total Mailn.total 30 minutes

Category (Source): QOS (QOS.Mail.ISpy.<servername>.ResponseTime)



Interval


Cubes (Tivoli Discovery Administrator)A PowerCube contains data (measure values) organized in dimensions and measures to provide for faster retrieval and drill-down in PowerPlay Explorer and Reporter. The Lotus Domino Guide has two cubes, the Domino Monitors and Domino Trend cubes.

The Lotus Domino Guide cubes use queries to extract data from the DOMINO_METRICS database table. These queries consist of SQL Columns (a SELECT statement) and Calculated Columns. The following example shows the SQL Columns and Calculated Columns for the domino_calc_values query in the Domino Monitors Cube:

QOS servername 30 minutes

Universal Monitor Collection

Monitor Name Monitor Argument Suggested Interval

Category (Source): Filesize (File size)

FilesizeName Notes database file

(for example, C:\notes\data\names.nsf)

30 minutes

Category (Source): host (Host Availability)

host Host name 30 minutes

NT_System Monitor Collection


Category (Source): CPU Percent Busy (Percent Total Processor Time)

CPU Percent Busy 30 minutes

UNIX_Sentry Monitor Collection


Category (Source): CPU Percent Busy (CPU Usage)

CPU Percent Busy 30 minutes



Interval

28 Version 1.0

SQL ColumnsSELECT

COLLECTION DATE,{fn year(COLLECTION_DATE) as YEAR,{fn month(COLLECTION_DATE) as MONTH,{fn dayofmonth(COLLECTION_DATE) as DAY,ENDPOINT,PROFILE_COLLECTION,PROBE,PROBE_ARG,AVG_VALUE_00,AVG_VALUE_01,AVG_VALUE_02,AVG_VALUE_03,AVG_VALUE_04,AVG_VALUE_05,AVG_VALUE_06,AVG_VALUE_07,AVG_VALUE_08,AVG_VALUE_09,AVG_VALUE_10,AVG_VALUE_11,AVG_VALUE_12,AVG_VALUE_13,AVG_VALUE_14,AVG_VALUE_15,AVG_VALUE_16,AVG_VALUE_17,AVG_VALUE_18,AVG_VALUE_19,AVG_VALUE_20,AVG_VALUE_21,AVG_VALUE_22,AVG_VALUE_23,

FROMDOMINO_METRICS

WHERECOLLECTION_DATE

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

(PROBE_ARG IN (’Server.Trans.Total’,‘Domino.Requests.Per1Hour’,'Replica.Failed','Replica.Successful','Replica.Docs.Added','Replica.Docs.Deleted','Replica.Docs.Updated') OR

PROBE_ARG like ‘Replica.Cluster.%’ ORPROBE_ARG like ‘%.TotalRouted’ ORPROBE_ARG like ‘%.TotalFailures’ ORPROBE_ARG like ‘%.TransFailures’ ORPROBE_ARG like ‘%.Transferred’ ORPROBE_ARG like ‘%.TransferFailures’ ORPROBE_ARG like ‘NET.%.BytesSent’ ORPROBE_ARG like ‘NET.%.BytesReceived’ ORPROBE_ARG like ‘NET.%.Sessions.Established.Incoming’ ORPROBE_ARG like ‘NET.%.Sessions.Established.Outgoing’ ORPROBE_ARG like ‘NET.%.Sessions.Recycled’)


Calculated Columnscc_1 AMcc_2 AMcc_3 AMcc_4 AMcc_5 AMcc_6 AMcc_7 AMcc_8 AMcc_9 AMcc_10 AMcc_11 AMcc_12 AMcc_1 AMcc_2 AMcc_3 AMcc_4 AMcc_5 AMcc_6 AMcc_7 AMcc_8 AMcc_9 AMcc_10 AMcc_11 AMcc_Daily Totalcc_ENDPOINTcc_PROBEcc_PROBE_ARGcc_WEEKDAYcc_WEEKDAY_NAMEcc_WEEKDAY_OR_WEEKEND

Domino Monitors Cube

The Domino Monitors cube consists of four queries and two parameter settings. Each query creates a .csv (comma-separated values) data file for the Cognos Transformer, and the four resulting .csv files are used to build the Cognos model and powercube. Each of the queries extracts data from the DOMINO_METRICS table in the relational database through an ODBC driver. Data from the Domino monitors defined are collected for reporting from these queries.

Parameters

The following table lists the parameter settings:

Parameter Name

Type Values

Date Range Range Start Date

End Date

Calculated on Rolling 6 Months

Probe Name Terminology Value Name Value

30 Version 1.0

Queries

The Domino Monitors Cube uses four queries to the database table. This section describes those queries. You can review all of the query select statements and calculated columns in a technical appendix to this document that is available on the Tivoli Customer Support web site at http://www.tivoli.com/support. Follow the links to the Product Manuals section to download the PDF file. After you install the Lotus Domino Guide, can also view the functions for the calculated columns, as well as the SQL Columns and Calculated Columns) from the Tivoli Discovery Administrator console. Simply open the Domino Monitors Cube, and then double-click on Queries. You can then double-click on an individual query to display a tabbed dialog that lets you view query information.

domino_calc_valuesqueries the database table for Domino monitors in which the hourly totals must be calculated. For instance, mail monitors such as MAIL.TotalRouted are reported from the Domino server as a cumulative value since the server was last started. Therefore, this query calculates the hourly and daily totals for these types of monitors for reporting.

domino_cluster_valuesqueries the database table for the ServerCluster Domino monitor value to convert it to a percentage of availability.

domino_mb_valuesqueries the database table for Domino monitors that report values in bytes and then converts the values into megabytes.

domino_orig_valuesqueries the database table for Domino monitors that do not need any calculations to any of the hourly metrics. Therefore, all hourly values are reported in their original value from the database.

Dimensions

Once cubes are defined in the Tivoli Discovery Administrator, a model can be created for each cube in Cognos Transformer. The model for the Domino Monitors cube consists of 4 dimensions and 28 measures. A dimension is a grouping of descriptive data about a major aspect of a

PrcTotCpuTime

Avgcpubusy

/, Free

/, Size

C, Free

C, Size

D, Free

D, Size

E, Free

E, Size

CPU percent busy

CPU percent busy

Disk./.Free

Disk./.Size

Disk.C.Free

Disk.C.Size

Disk.D.Free

Disk.D.Size

Disk.E.Free

Disk.E.Size

Parameter Name

Type Values


business. Each dimension includes categories in one or more drill-down paths and an optional set of special categories. Below is a listing and description of the four dimensions found in the Transformer model for the Lotus Domino Guide.

By Date The date dimension has the following categories, which are automatically generated during the PowerPlay cube build. The lowest level of detail it can go to is by day. Five special categories added are: by last day, by last 7 days, by last 30 days, by last 60 days, and by last 90 days.

By Day of WeekThis dimension, when viewed as a PowerPlay report, can be drilled down to specific days of the week. It also has an alternate drill down for viewing by business days or weekends.

By Server This dimension is used to categorize reports by the endpoint name (which will be the machine alias name). An alternate drill down can be done to view servers by the profile in which the monitors were distributed in. This alternate drill category allows users to customize how they want to distribute and view their monitors.

By Monitor This dimension drills down from the type of Domino monitor to the specific monitor argument.

By Date

Year

Quarter

Month

Day

By Day of Week

WEEKDAY_OR_WEEKEND

WEEKDAY_NAME

By Server

PROFILE_COLLECTION

cc_ENDPOINT

By Monitor

PROBE

PROBE_ARG

32 Version 1.0

Measures

The measures in the Transformer model are the quantitative values returned from the Domino monitors. These values change according to what dimensions you are looking at. The Transformer model for the Domino Monitors cube contains the measures in the table below. Each measure returns an “na” value when the column is null, and all measure values are displayed to two decimal places.

Check of the Allowed Measures and Dimensions Combination

Before building a powercube with a model, a check can be performed to make sure there are no problems with the model. For each measure, you can see if each is in scope with all the dimensions. For the model in the Domino Monitors cube, all measures described in the previous ““Measures” on page 32” section are in scope with all the model dimensions.

Domino Trend Cube

The Domino Trend cube consists of four queries and four parameter settings. Each query creates a .csv data file for the Cognos Transformer, and the four resulting .csv files are used to build the Cognos model and powercube. Each of the queries extracts data from the DOMINO_METRICS table in the relational database through an ODBC driver. The data is then used to calculate the

Measure Name Rollup Function Type12 AM Average Column = 12 AM

1 AM Average Column = 1 AM











12 PM Average Column = 12 PM












Daily Average Average Column = Daily Average

Daily Minimum Average Column = Daily Minimum

Daily Maximum Average Column = Daily Maximum

Daily Total Average Column = Daily Total


forecasted values. Data from the Domino monitors defined are collected for reporting from these queries.

Parameters

The Forecast Accelerator means the percentage accelerating added value in the next 30 days to the trend value.

Queries

The Domino Trend Cube uses four queries to the database table. This section describes those queries. As with the Domino Monitors Cube queries, you can view complete query statements and columns by downloading the technical appendix to this document from the Tivoli Customer Support web site (http://www.tivoli.com/support), or you can install the Lotus Domino Guide, and then view query, column and function information from the Tivoli Discovery Administrator console.

domino_trend_calcqueries the database table for all Domino mail monitors in which the hourly totals must be calculated. For instance, mail monitors such as MAIL.TotalRouted are reported from the Domino server as a cumulative value since the server was last started. Therefore, this query calculates the hourly and daily totals for these types of monitors for reporting.

domino_trend_clusterqueries the database table for the ServerCluster monitor to compute the forecasted values.

Parameter Name Type Values

Date Range Range Start Date

End Date

Calculated on Rolling 6 Months

Forecast Accelerator

Terminology Value Name Value

Default 0

Probe Name Terminology Value Name Value

PrcTotCpuTime

Avgcpubusy

/, Free

/, Size

C, Free

C, Size

D, Free

D, Size

E, Free

E, Size

CPU percent busy

CPU percent busy

Disk./.Free

Disk./.Size

Disk.C.Free

Disk.C.Size

Disk.D.Free

Disk.D.Size

Disk.E.Free

Disk.E.Size

34 Version 1.0

domino_trend_mbqueries the database table for Domino monitors that report values in bytes and then converts the values into megabytes.

domino_trend_origqueries the database table for Domino monitors that do not need any calculations to any of the hourly metrics. The query then computes the forecast values for these monitors.

Dimensions

Once cubes are defined in the Tivoli Discovery Administrator, a model can be created for each cube in Cognos Transformer. The model for the Domino Trend cube consists of 2 dimensions and 6 measures. A dimension is a grouping of descriptive data about a major aspect of a business. Each dimension includes categories in one or more drill-down paths and an optional set of special categories. The Transformer model for the Lotus Domino Guide consists of two dimensions: By Server and By Monitor

By Server This dimension is used to categorize reports by the endpoint name (which will be the machine alias name). An alternate drill down can be done to view servers by the profile in which the monitors were distributed in. This alternate drill category allows users to customize how they want to distribute and view their monitors.

By Monitor This dimension drills down from the type of Domino monitor to the specific monitor argument.

Measures

The measures in the Transformer model are the quantitative values returned from the Domino monitors. These values change according to what dimensions you are looking at. The Transformer model for the Domino Trend cube contains the measures in the following table. Each measure returns the value “na” when the column is null, and all measure values are displayed to two decimal places.

By Server

PROFILE_COLLECTION

cc_ENDPOINT

By Monitor

PROBE

PROBE_ARG

Measure NameRollup

FunctionType

30 Day Forecast Average Average Column=30 Day Forecast Average



30 Day Forecast Peak Average Column=30 Day Forecast Peak



Check of the Allowed Measures and Dimensions Combination

Before building a powercube with a model, a check can be performed to make sure there are no problems with the model. For each measure, you can see if each is in scope with all the dimensions. For the model in the Domino Trend cube, all measures described in the previous “Measures” on page 34 section are in scope with all the model dimensions.


Measure NameRollup

FunctionType

36 Version 1.0

Report DefinitionsThe following table describes the reports available on the Tivoli Discovery Interface for each View provided by the Lotus Domino Guide


.

Vie

w T

itle

Rep

ort

File

nam

e (C

ub

eS

ou

rce

File

)C

har

t Ty

pe

Ran

kR

epo

rt

Typ

eP

erio

dM

on

ito

rM

easu

reR

ow

C

olu

mn

Lay

er

Add

in

Pro

gram

S

tatu

s

dom

ino_

prog

ram

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 7

Day

sA

ddin

Sta

tSta

tus

Dai

ly A

vera

geA

ddin

Sta

tSt

atus

Las

t 7 D

ays

By

Ser

ver

Cal

enda

r an

d S

ched

ulin

g St

atis

tics

dom

ino_

cale

ndar

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 7

Day

sC

alen

dar

Dai

ly A

vera

geC

alen

dar

Las

t 7 D

ays

By

Ser

ver

Clu

ster

Sta

tus

dom

ino_

clus

ter.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Lin

e

Exp

lore

rL

ast D

ayC

lust

er S

tatu

sM

EA

SU

RE

SB

y S

erve

rM

EA

SUR

ES

Dis

k S

pace

P

erce

nt F

ree

dom

ino_

disk

spac

efre

e.pp

r (D

omin

o_M

onit

ors.

mdc

)C

ross

tab

Rep

orte

rL

ast D

ayD

isk

Dai

ly A

vera

geD

aily

Ave

rage

Dis

k S

pace

St

atis

tics

dom

ino_

disk

spac

e.pp

r (D

omin

o_M

onit

ors.

mdc

)L

ine

Exp

lore

rL

ast 3

0 D

ays

Dis

kD

aily

Ave

rage

Dis

kL

ast 3

0 D

ays

By

Ser

ver

Hos

t A

vail

abil

ity

dom

ino_

host

.ppr

(D

omin

o_M

onit

ors.

mdc

)C

ross

tab

Exp

lore

rL

ast 7

D

ays

Hos

t Ava

ilabi

lity

Dai

ly A

vera

geL

ast 7

Day

sB

y Se

rver

Mai

l Ave

rage

St

atis

tics

dom

ino_

mai

l_av

g.pp

r (D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t Day

Mai

l Ave

rage

Mon

itors

Dai

ly A

vera

geL

ast D

ayS

erve

rs b

y P

rofi

leM

ail

Ave

rage

M

onit

ors

Mai

l C

alcu

late

d To

tals

dom

ino_

mai

l_ca

lc.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Lin

eE

xplo

rer

Las

t 30

Day

sM

ail T

otal

Mon

itor

sD

aily

Tot

alM

ail T

otal

M

onit

ors

Las

t 30

Day

sB

y S

erve

r

Not

es

Dat

abas

e S

ize

dom

ino_

data

base

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 30

Day

sfi

lesi

zeD

aily

Ave

rage

file

size

Las

t 30

Day

sB

y Se

rver

QO

S.M

ail.

ISP

Ydo

min

o_is

py.p

pr(D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 7

Day

sQ

OS

Dai

ly A

vera

geL

ast 7

Day

sB

y Se

rver

Rep

licat

ion

Stat

isti

csdo

min

o_re

plic

atio

n.pp

r (D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 30

Day

sR

eplic

atio

nD

aily

Tot

alR

epli

catio

nL

ast 3

0 D

ays

By

Ser

ver

Ser

ver

Ava

ilab

ilit

ydo

min

o_av

aila

bili

ty.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Cro

ssta

bE

xplo

rer

Las

t 7

Day

sP

erce

ntag

e A

vaila

ble

Dai

ly A

vera

geL

ast 7

Day

sB

y Se

rver

CPU

U

tiliz

atio

ndo

min

o_cp

u.pp

r (D

omin

o_M

onit

ors.

mdc

)L

ine

Exp

lore

rL

ast D

ayC

PU

per

cent

bus

yM

EA

SU

RE

SSe

rver

s by

Pr

ofile

ME

ASU

RE

S

Dom

ino

Net

wor

k T

raff

ic

dom

ino_

net.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Bar

Exp

lore

rL

ast 7

D

ays

NE

TD

aily

Tot

alN

ET

Las

t 7 D

ays

By

Serv

er

HT

TP

Req

uest

sdo

min

o_ht

tp.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Pie

Exp

lore

rL

ast 7

D

ays

Dom

ino.

Req

uest

sPer

1 H

our

Dai

ly T

otal

Dai

ly T

otal

By

Day

of

Wee

kB

y Se

rver


Mem

ory

Usa

gedo

min

o_m

emor

y.pp

r (D

omin

o_M

onit

ors.

mdc

)L

ine

Exp

lore

rL

ast 3

0 D

ays

Mem

ory

Dai

ly A

vera

geM

emor

yL

ast 3

0 D

ays

By

Ser

ver

Ser

ver

Usa

gedo

min

o_us

age.

ppr

(Dom

ino_

Mon

itor

s.m

dc)

Bar

Exp

lore

rL

ast D

ayS

erve

rM

EA

SUR

ES

Serv

erM

EA

SUR

ES

By

Serv

er

Bot

tom

25

Ser

vers

by

Ava

ilabl

e D

isk

Spa

ce

dom

ino_

rank

_dis

k.rp

t (D

omin

o_M

onit

ors.

mdc

)D

etai

lC

ryst

alL

ast 7

D

ays

Dis

k.X

.Fre

eD

aily

Ave

rage

Dai

ly

Ave

rage

By

Serv

er

Bot

tom

25

Ser

vers

by

Ser

ver

Ava

ilab

ilit

y

dom

ino_

rank

_ava

ilabi

lity

.ppr

(D

omin

o_M

onit

ors.

mdc

)C

ross

tab

Las

t 7

Day

sE

xplo

rer

Las

t 7

Day

sP

erce

ntag

e av

aila

ble

Dai

ly A

vera

geL

ast 7

Day

sB

y Se

rver

Top

25 S

erve

rs

by C

PU

U

tiliz

atio

n

dom

ino_

rank

_cpu

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arL

ast 7

D

ays

Exp

lore

rL

ast 7

D

ays

CPU

per

cent

bus

yD

aily

Ave

rage

Las

t 7 D

ays

By

Serv

er

Top

25 S

erve

rs

by H

TT

P

Req

uest

s

dom

ino_

rank

_htt

p.pp

r (D

omin

o_M

onit

ors.

mdc

)B

arL

ast 7

D

ays

Exp

lore

rL

ast 7

D

ays

Dom

ino.

Req

uest

sPer

1Ho

urD

aily

Tot

alL

ast 7

Day

sB

y Se

rver

Top

25 S

erve

rs

by M

emor

y A

lloc

ated

dom

ino_

rank

_mem

ory.

ppr

(Dom

ino_

Mon

itor

s.m

dc)

Bar

Las

t 7

Day

sE

xplo

rer

Las

t 7

Day

sM

em.A

lloc

ated

Dai

ly A

vera

geL

ast 7

Day

sB

y Se

rver

Top

25 S

erve

rs

by T

otal

Mai

l R

oute

d

dom

ino_

rank

_mai

l_ro

uted

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arL

ast 7

D

ays

Exp

lore

rL

ast 7

D

ays

MA

IL.T

otal

Rou

ted

Dai

ly T

otal

Las

t 7 D

ays

By

Serv

er

Dom

ino

Sta

tisti

cs b

y D

ay

dom

ino_

day.

ppr

(Dom

ino_

Mon

itor

s.m

dc)

Bar

Exp

lore

rL

ast 3

0 D

ays

By

Mon

itor

Dai

ly A

vera

geSe

rver

s by

Pr

ofile

Las

t 30

Day

s

Dom

ino

Sta

tisti

cs b

y D

ay o

f W

eek

dom

ino_

wee

kday

.ppr

(D

omin

o_M

onit

ors.

mdc

)B

arE

xplo

rer

Las

t 7

Day

sB

y M

onito

rD

aily

Ave

rage

Serv

ers

by

Prof

ileB

y D

ay o

f W

eek

Dom

ino

Sta

tisti

cs b

y H

our

dom

ino_

hour

.ppr

(D

omin

o_M

onit

ors.

mdc

)L

ine

Exp

lore

rL

ast D

ayB

y M

onito

rM

EA

SU

RE

SB

y M

onit

orM

EA

SUR

ES

By

Ser

ver

Dom

ino

Sta

tisti

cs b

y S

erve

r

dom

ino_

serv

er.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Cro

ssta

bE

xplo

rer

Las

t Day

By

Mon

itor

Dai

ly A

vera

geB

y M

onit

orB

y Se

rver

Vie

w T

itle

Rep

ort

File

nam

e (C

ub

eS

ou

rce

File

)C

har

t Ty

pe

Ran

kR

epo

rt

Typ

eP

erio

dM

on

ito

rM

easu

reR

ow

C

olu

mn

Lay

er


Dom

ino

Sta

tisti

cs b

y S

erve

r P

rofi

le

dom

ino_

serv

er_p

rofi

le.p

pr

(Dom

ino_

Mon

itor

s.m

dc)

Bar

Exp

lore

rL

ast D

ayB

y M

onito

rD

aily

Ave

rage

Serv

ers

by

Prof

ileB

y M

onit

or

Ser

ver

For

ecas

ted

Ave

rage

s an

d P

eaks

dom

ino_

tren

d.pp

r (D

omin

o_T

rend

.mdc

)B

arE

xplo

rer

By

Mon

itor

ME

AS

UR

ES

Serv

ers

by

Prof

ileM

EA

SUR

ES

Vie

w T

itle

Rep

ort

File

nam

e (C

ub

eS

ou

rce

File

)C

har

t Ty

pe

Ran

kR

epo

rt

Typ

eP

erio

dM

on

ito

rM

easu

reR

ow

C

olu

mn

Lay

er

40 Version 1.0

Software Defects, Limitations, and WorkaroundsThis section lists the current defects, limitations and workarounds known for this product.

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

LimitationsThe following limitations are known for this product:

� The size of the DOMINO_METRICS table can affect the cube building process. Manage the size of this table in the Domino Configuration for Manager for Applications Rollup database to optimize the cube building process.

� Because columns within the DOMINO_METRICS table are allocated only a certain maximum length, make sure that the column values for each monitor are within this length.

� When you create monitors to store data to the Sentry Graphable Logs file, large numeric values are logged with only six significant digits. For example, if a monitor returns the value 123456789, this value will be stored in the Sentry Graphable Logs file as 1.234567x10^8. Only six significant digits are stored, and the sixth number is rounded. Therefore, large numeric values may be rounded when stored in the RDBMS for the Lotus Domino Guide.

� When DB2 is used as the RDBMS for the RIM object, the 3.6.1-TMF-0002 patch has revealed issued with DB 5.2 on Solaris. Therefore, DB2 5.2 is not supported by the Domino Configuration for Manager for Applications Rollup 2.0 on Solaris.

� In the TDS 2.1 Discovery Interface, the Ranking tab in the Properties of a view does not retrieve the categories to automatically re-rank the PowerPlay view. Instead, the following error message may be displayed, “Cannot retrieve the categories for this view.” This is a known problem in the TDS 2.1 Discovery Interface, and the issue will be addressed in a future TDS release or patch.

WorkaroundsThis section lists workarounds for the following problems:

Contacting Customer SupportFor support for this or any Tivoli product, you can contact Tivoli Customer Support in one of the following ways:

� Visit our Web site at http://www.tivoli.com/support

� Send e-mail to [email protected]

Customers in the United States can also call 1-800-TIVOLI8 (1-800-848-6548). International customers should consult the Web site for customer support telephone numbers. You can also

Problem Workaround

Measures on simple bar graphs appear twice: centered on the graph and over the Y-axis. On low resolution monitors, the measure names may overlap.

A minimum resolution of 800x600 pixels is recommended for monitors.


review the Customer Support Handbook, which is available on our Web site at http://www.tivoli.com/support/handbook/.

When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily. Company identification information may also be needed to access various online services available on the Web site.

The Web site offers extensive information, including a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and documentation for all Tivoli products, including Release Notes, Redbooks, and Whitepapers. The documentation sets for some product releases are available in both PDF and HTML formats. Translated documents are also available for some product releases.

You can order documentation by e-mail at [email protected]. Please provide the part number or order number of the desired document; alternatively, you can provide the document’s title, version number, and date of publication.

We are very interested in hearing about your experience with Tivoli products and documentation. We also welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please contact us in one of the following ways:

� Send e-mail to [email protected]

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

42 Version 1.0