TDS Guide for Software Deployment Analysis 1.0 Release Notes (March 1999)

Transcription

1 TDS for Software Deployment Analysis Release Notes Version 1.0 March 7, 1999

2 TDS Guide for Software Deployment Analysis 1.0 Release Notes (March 1999)

3 TDS Guide for Software Deployment Analysis 1.0 Release Notes (March 1999) TDS for Software Deployment Analysis 1.0 (March 1999) Copyright Notice Copyright 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 machinereadable 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. Trademarks The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, CICS, IBM, MVS, NetView, Tivoli, Tivoli Change Management, Tivoli Decision Support 2.0, Tivoli Management Environment, TME 10, OS/2, O/S390, and RS/6000. Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation. Java and all Java-based trademarks or logos are trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited. 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 , U.S.A. Tivoli Decision Support Guide Documentation Each TDS Guide is delivered with on-line documentation. During the installation process, the applicable TDS guide documentation is copied to the Tds\guide docs installation directory on your system.

4 Table of Contents Preface...vii Who Should Read This Book... vii Prerequisite Software... viii ODBC Drivers...viii Software Deployment Analysis Guide Documentation...ix Prerequisite and Related Documentation...x Contacting Customer Support...xi Introduction...1 Tivoli Decision Support for Software Deployment Analysis 1.0 Product Summary...1 Installation...2 Requirements...3 Installing the Software Deployment Analysis Guide...5 Preparing to Work with the Inventory Database... 5 Setting Up an Oracle or Sybase Client... 5 Preparing the Inventory Database... 6 Setting Up an ODBC Data Source... 6 After Installing TDS... 6 Configuring the Shared Source File Path... 7 Installing and Importing the Software Deployment Analysis Guide... 8 Assigning and Verifying a Data Source Setting the Date Range Parameter in the Cube Building the Cube Reinstalling a Discovery Guide...12 Operating Procedures for the Software Deployment Analysis Guide...12 Scheduling the Cube Build Task...12 Setting Up Scheduled Cube Builds TDS for Software Deployment Analysis 1.0 Release Notes iv

5 Using the Software Deployment Analysis Guide Specifying the Database Logon for Crystal Reports Troubleshooting...15 ODBC Driver Problems...15 Cube Building...15 Report Problems...18 Year 2000 (Y2K) Compliance...19 Inventory Database Seagate Crystal Reports Version Software Defects, Limitations, and Workarounds...21 Defects...21 Limitations...21 Workarounds...22 Dependencies and Compliance Criteria...23 Definition...23 Application Dependencies Database Dependencies Supported Platforms Supported Languages Functional Definition...25 Data Sources...25 Software Deployment Analysis Database Schema TABLE: installed_sw_component TABLE software_filepack TABLE software_component Cubes (Tivoli Discovery Administrator)...27 Software Distribution Analysis Query Used to Build the Cube Parameters Used to Build the Cube Dimensions Measures Check of the Allowed Measures and Dimensions Combination TDS for Software Deployment Analysis 1.0 Release Notes v

6 Topics and Views (Interface)...35 Related Views and Roles...37 New Roles Report Definitions...41 APPENDIX A...43 Functions for Calculated Columns: Software Distribution Analysis Cube...43 QueryName swd_analysis TDS for Software Deployment Analysis 1.0 Release Notes vi

7 Preface This document describes the Tivoli Decision Support (TDS) for Software Deployment Analysis product. The Software Deployment Analysis Guide is designed to support the Tivoli Software Distribution product with a ready-to-use tool in order to spot hidden trends, improve service levels and make better IT decisions using Tivoli Decision Support. Note: The Tivoli guides as a group are called discovery guides. The TDS for Software Deployment Analysis product is a discovery guide that is also called the Software Deployment Analysis Guide. Who Should Read This Book This document is intended for the users of the Tivoli Decision Support (TDS) for Software Deployment Analysis and anyone responsible for the administration of Tivoli Decision Support. Before using the Software Deployment Analysis Guide, you should be familiar with the following: The operating system on your computer The basic use of discovery guides and the Tivoli Discovery Interface To set up the Software Deployment Analysis Guide, your system administrator should be familiar with the following: The Tivoli Discovery Administrator The basic use of Crystal Reports The basic use of Cognos PowerPlay TDS for Software Deployment Analysis 1.0 Release Notes vii

8 TME 10 Software Distribution 3.6 TME 10 Inventory 3.6 and the Inventory database The Open Database Connectivity (ODBC) for your database Prerequisite Software ODBC Drivers ODBC drivers are provided on the TDS 2.0 CD-ROM. Database Database Version Database Version Database Version Type ODBC Version ODBC Version ODBC Version Sybase 10.X all tier X all tier X all tier 1 INTERSOLV Inc. ODBC 3.01 INTERSOLV Inc. ODBC 3.01 INTERSOLV Inc. ODBC 3.01 (10.03 client or higher) Oracle 7.2.X all tier X all tier1 Microsoft ODBC Driver for Oracle Microsoft ODBC Driver for Oracle Microsoft ODBC for Oracle Microsoft ODBC for Oracle Note: If you experience problems with the INTERSOLV ODBC driver version 3.01 for Sybases, contact Tivoli Customer Support, and request the updated INTERSOLV ODBC driver version 3.01 for Sybase. For more information about this issue, please contact Tivoli Customer Support by sending an to support@tivoli.com or by visiting the Tivoli Customer Support web site at Please be sure to include your customer identification information. TDS for Software Deployment Analysis 1.0 Release Notes viii

9 Software Deployment Analysis Guide Documentation Refer to the following documentation when installing and using the Software Deployment Analysis Guide: Document Tivoli Decision Support (TDS) 2.0 Readme0399.txt TDS for Software Deployment Analysis Readme.txt TDS for Software Deployment Analysis Release Notes Using Decision Support Guides Description Location Review this document before installing TDS for Event Management. It contains the latest information about the TDS product. This document also describes the features of the Tivoli Discovery Interface that are not documented in version 2.0. These features are found in the Tivoli Discovery Interface, and not in the Tivoli Discovery Administrator. The Tivoli Decision Support 2.0 User Online Help system provides detailed information and procedures for using the undocumented features. Filename on the CD-ROM: d:\readme0399.txt (where d: is the drive letter for your CD-ROM Drive) Filename on your system: Tds\Docs\Readme0399.txt Provides a description of the product documentation, the initial installation instructions, and the contact information for Tivoli Customer Support. Filename on the CD-ROM: d:\tivoli Decision Support for Software Deployment Analysis\NTimage\Readme.txt (where d: is the drive letter for your CD-ROM Drive) Filename on your system: TDS\Guide docs\tivoli Decision Support for Software Deployment Analysis\Readme.txt Provides copyright, prerequisite, installation procedures, and trouble shooting for the Software Deployment Analysis Guide. Filename on the CD-ROM: d:\tivoli Decision Support for Software Deployment Analysis\NTimage\TDS_SDA_Rel_Notes.pdf (where d: is the drive letter for your CD-ROM Drive) Filename on your system: TDS\Guide docs\tivoli Decision Support for Software Deployment Analysis\Tds_SDA_Rel_Notes.pdf Provides an overview of the TDS Guides, cube dimensions and measures, and detailed procedures for using the TDS Guides. Filename on your system: TDS\Docs\Pdf\dg.pdf TDS for Software Deployment Analysis 1.0 Release Notes ix

10 Document Installation Guide Decision Support User s Guide Administrator Guide Other Guides Description Location Provides installation procedures for TDS and its components in stand-alone and network mode. Filename on your system: TDS\Docs\Pdf\install.pdf Describes TDS features, concepts, and provides procedures for using the Tivoli Discovery Interface. Filename on your system: TDS\Docs\Pdf\user-gd.pdf Explains the features of the Tivoli Discovery Administrator. Filename on your system: TDS\Docs\Pdf\admin-gd.pdf Each Tivoli discovery guide is delivered with online documentation. During the installation process for each discovery guide, the applicable discovery guide documentation is copied to the Tds\Guide docs installation directory on your system. Directory on your system: Tds\Guide docs Prerequisite and Related Documentation To use the Tivoli Decision Support for Software Deployment Analysis Guide, you should be familiar with the Tivoli Decision Support library of publications: Tivoli Decision Support Installation Guide Tivoli Decision Support 2.0 Administrator Guide Tivoli Decision Support 2.0 User s Guide Tivoli Decision Support 2.0 Using Decision Support Guides TDS for Software Deployment Analysis 1.0 Release Notes x

11 Contacting Customer Support To contact Tivoli Customer Support: Note: Whenever contacting Tivoli Customer Support, please have your customer identification information available. Access the Tivoli Customer Support home page at After you link to and submit the customer registration form, you can access many customer support services on the World Wide Web. Refer to the Customer Support Handbook for a listing of Tivoli Customer Support services, hours of operation, and contact numbers. This handbook is available online at Send an to support@tivoli.com. In the United States, call Tivoli Customer Support at TIVOLI-8. Outside the United States, refer to your Customer Support Handbook for a list of support numbers in your country. This handbook is available online at To provide comments and suggestions about our documentation: We at Tivoli are very interested in hearing from you about your experience with Tivoli products, documentation, and services. We welcome your suggestions for improvements. If you have comments or suggestions about our documentation, please send to pubs@tivoli.com. TDS for Software Deployment Analysis 1.0 Release Notes xi

12

13 Introduction Tivoli Decision Support for Software Deployment Analysis 1.0 Product Summary The Tivoli Decision Support for Software Deployment Analysis 1.0 responds to the need for a strategic view of network activity in terms of the results of distribution actions. This discovery guide provides information about successful and failed attempts to modify the software contents and supplies the link between the action performed, its result, and the system concerned with this action. The Tivoli Discovery Interface presents information in a graphical and a text format and is organized using a set of topic questions and reports. The topic questions for software distribution address success, effectivness, trends, peak volume, and sources of events. Tivoli Discovery Interface uses a multidimensional cube built with data added by the distribution process in the Inventory database and with the data about software and hardware in the configuration repository. Each TDS installation site can control when the multidimensional cube is refreshed. TDS for Software Deployment Analysis 1.0 Release Notes 1

14 Installation The following table lists the sequence of activities required to install the Software Deployment Analysis Guide. The shaded activities are only performed if you are first installing TDS on your system. If TDS is already installed on your system, skip the shaded steps. How to See section Page 1. Determine the software requirements Prerequisite Software viii Requirements 3 Dependencies and Compliance Criteria 23 Set up an Oracle or Sybase Client Setting Up an Oracle or Sybase Client 5 2. Install TDS See the TDS Installation Guide document ix 3. Install Cognos described in the section Software Deployment Analysis Guide Documentation. 4. Install the ODBC drivers Prerequisite and Related Documentation x 5. Set up an ODBC data source connection Setting Up an ODBC Data Source 6 6. Configure the shared source file path Configuring the Shared Source File Path 7 7. Install the discovery guide Installing and Importing the Software 8 8. Import the discovery guide Deployment Analysis Guide 9. Assign the ODBC data source Assigning and Verifying a Data Source Test the connectivity with the data source 11. Build the cube Building the Cube Schedule the cube build task Scheduling the Cube Build Task 12 TDS for Software Deployment Analysis 1.0 Release Notes 2

15 Requirements This section lists the products that are prerequisites for the Software Deployment Analysis Guide. Refer to the appropriate product documentation for installation procedures. If you are an administrator, you need: Microsoft Windows 95 and Windows NT 3.51 or later Tivoli Decision Support 2.0 with the following components: Tivoli Discovery Interface Tivoli Discover Administrator ( to build cubes) Cognos PowerPlay (Administrator) Crystal Reports (only required when creating or modifying reports) TME 10 Software Distribution 3.6 on your network TME 10 Inventory 3.6 on your network Access to the Inventory database that contains the software distribution tables Oracle or Sybase ODBC driver. For Oracle and Sybase ODBC driver versions, see the section ODBC Driver Versions. A version of Microsoft Access should be available though not required to run TDS If you are a Crystal Reports user, you need: Microsoft Windows 95 and Windows NT 3.51 or later Tivoli Decision Support 2.0 with the following components: Tivoli Discovery Interface Crystal Reports (only required when creating or modifying reports) TDS for Software Deployment Analysis 1.0 Release Notes 3

16 TME 10 Software Distribution 3.6 on your network TME 10 Inventory 3.6 on your network Access to the Inventory database that contains the software distribution tables Oracle or Sybase ODBC driver. For Oracle and Sybase ODBC driver versions, see the section ODBC Driver Versions. If you are a multidimensional view user, you need: Microsoft Windows 95 and Windows NT 3.51 or later Tivoli Decision Support 2.0 with the following components: Tivoli Discovery Interface Cognos PowerPlay (Standard) Access to the cube built by the administrator TDS for Software Deployment Analysis 1.0 Release Notes 4

17 Installing the Software Deployment Analysis Guide Before using the Software Deployment Analysis Guide, complete the installation procedures described in the following sections. Preparing to Work with the Inventory Database Use the following procedures to create the network identification required by Sybase or Oracle to access the Inventory database from the systems running TDS. Setting Up an Oracle or Sybase Client Consult 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. TDS for Software Deployment Analysis 1.0 Release Notes 5

18 Preparing the Inventory Database Setting Up an ODBC Data Source Use the following procedure to connect to an ODBC data source: 1. On the Control Panel, select the ODBC icon 2. Select the System DSN tab. 3. Click Add. 4. Select an ODBC driver, and click Finish. For more information about the ODBC drivers, see the section ODBC Drivers. 5. Enter the appropriate identification and login information for the database. 6. Enter the database qualifier: For Sybase, enter tivoli For Oracle, enter TIVOLI Note: Your database qualifier may be different. Contact the database administrator for additional information. After Installing TDS After installing TDS, complete the procedures described in this section to finish the Software Deployment Analysis Guide installation process. TDS for Software Deployment Analysis 1.0 Release Notes 6

19 Configuring the Shared Source File Path Before using the Tivoli Discovery Administrator or the Tivoli Discovery Interface, they must be configured to locate certain files (called source files) that are stored on your system (the local system) or on the network. If you installed TDS using 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. Use the following procedure to set the shared source file path: 1. On the View menu, select Options. The Options dialog box appears. On the General tab, in the Network box, type the name of the drive (and folder, if appropriate) that contains the following folders: Cubes Data Reports 2. Click OK. TDS for Software Deployment Analysis 1.0 Release Notes 7

20 Installing and Importing the Software Deployment Analysis Guide Use the following procedure to install and import the Software Deployment Analysis Guide: 1. Insert the Tivoli Decision Support for Software Deployment Analysis CD-ROM in the CD-ROM drive for your TDS server, and from the Start menu, choose Run. The Run dialog box appears. 2. In the Run dialog box, type d:\setup.exe (where d: is the drive letter for your CD- ROM drive), and click OK. The Tivoli Decision Support Discovery Guide Installation window appears. 3. Click on Tivoli Decision Support for Software Deployment Analysis. The discovery guide files are placed in the following Tds\ installation directories: cubes, models, reports, and install (where Tds\ is the TDS installation directory). The online documentation is installed in the following director: Tds\Guide docs\tivoli Decision Support for Software Deployment Analysis The updated TDS readme is installed in the following directory: Tds\Docs\Readme0399.txt Note: For more information, see the section Documentation. 4. Start the Tivoli Discovery Administrator. 5. On the Decision Support Guides menu, click Import. OR If a discovery guide has not been installed on your system, you are prompted to import an installed discovery guide, and to connect to a data source. TDS for Software Deployment Analysis 1.0 Release Notes 8

21 Note: For a step-by-step procedure, see Running the Tivoli Discovery Administrator for the First Time in the Administrator Guide document. 1. A dialog box appears prompting you to import and to install the decision support guide, select the Tivoli Decision Support for Software Deployment Analysis Guide, click Yes. 2. When prompted to add a data source, click Yes. 3. Select your configured data source. 4. Enter the database userid and password. 5. Enter the database qualifier: For Sybase, enter tivoli For Oracle, enter TIVOLI Note: Your database qualifier may be different. Contact the database administrator for additional information. 6. Select Software Deployment Analysis on the Import Decision Support Guides dialog box, and click OK. 7. Open Microsoft Explorer, and navigate to the Tds\cubes directory (where Tds\ is the installation directory path for TDS). TDS for Software Deployment Analysis 1.0 Release Notes 9

22 Assigning and Verifying a Data Source Use the following procedure to assign and verify a data source for the Software Distibution Analysis Guide: 1. Using the Tivoli Discovery Administrator, select the Software Distribution Analysis cube. 2. On the Data Sources menu, click Assign Data Sources. 3. Select the data source from the dropdown list. 4. Select the following query, and click OK: swd_analysis 5. Click the Data Sources folder. 6. Right click on the data source you just assigned, and select Test Connectivity 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 verify the data source definition, userid, password, and qualifier. If the connection is successful, the Test Data Source dialog box appears with the message Connection Successful. Click OK. Setting the Date Range Parameter in the Cube The Software Deployment Analysis Guide is designed to work without using the date range parameter. All calculated periods are relative to the most recent date in the data. TDS for Software Deployment Analysis 1.0 Release Notes 10

23 Building the Cube Schedule cube builds on a regular basis and during periods of decreased database activity. Use the following procedure to build a cube: 1. From the Administrator pane in the Tivoli Discovery Administrator window, double-click Cubes. 2. Right-click on the Software Distribution Analysis cube, and select Build. The Confirm Cube Build dialog box appears. 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 appears. Processing messages appear in the dialog box. 4. Review the processing messages for any errors. If an error generates an error dialog box, review the error, and click OK. 5. Click Close. 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 Discovery Interface, see the TDS User s Guide, and the Using Decision Support Guides documents described in the section Required Documentation. TDS for Software Deployment Analysis 1.0 Release Notes 11

24 Reinstalling a Discovery Guide To reinstall a discovery guide, you must first uninstall all the discovery guides on your system, and then uninstall TDS. You must now reinstall TDS and then reinstall the discovery guides. Operating Procedures for the Software Deployment Analysis Guide Scheduling the Cube Build Task You must periodically rebuild the cube to update your 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. Setting Up Scheduled Cube Builds The following procedure uses the Tivoli Discovery Administrator to create a cube building schedule and to determine the schedule TaskID. The cube build is then scheduled using the Cognos Scheduler. Use the following procedure to define a cube building schedule: 1. Start the Tivoli Discovery Administrator. 2. On the Scheduled Task menu, point to Add, and click Cube Build. The Add Schedule Wizard appears. TDS for Software Deployment Analysis 1.0 Release Notes 12

25 3. Type a name for the schedule you are creating in the Schedule Name box, and click Next. 4. Continue to click Next until you are prompted for the date range for the schedule. 5. In the Effective from date box, type or select a date that is prior to the current date. 6. Select the To checkbox to display the ending date box. 7. In the ending date box, type or select the date that you entered in the Effective from date box, and click Next. 8. Click Finish. 9. In the Tivoli Discovery Administrator pane, click on Scheduled Tasks. 10. In the Properties pane, right click on the scheduled task you created, and click Edit. The Edit Schedule dialog box appears. 11. On the Task tab, record the schedule Task ID for use in Step Click OK. 13. On the Start menu, under Programs, choose Cognos, and click Scheduler to start the Cognos Scheduler. 14. On the Insert menu, click Recurring task. The Insert Task dialog box appears. 15. On the Identification tab, type the following command string in the File name box: <directory path>\edamin.exe /TaskID=X (where <directory path> is the installation directory path for TDS and X is the schedule Task ID from Step 11) Note: Enclose the directory path and the edamin.exe in quotes as shown in the following example: c:\program Files\TDS\edamin.exe /TaskID=1 TDS for Software Deployment Analysis 1.0 Release Notes 13

26 16. Type a brief description of the cube and the schedule in the Description box. 17. On the Timetable tab, specify the cube building frequency, run time, and duration. 18. Minimize Cognos Scheduler. Note: Cognos Scheduler must be running for the cube to build at the scheduled time. Using the Software Deployment Analysis Guide. After your system administrator has built the Software Deployment Analysis cube using the Tivoli Discovery Administrator, start the Tivoli Discovery Interfaces. Select the Software Deployment Analysis Guide, and view a report. Specifying the Database Logon for Crystal Reports The first time you run a Crystal Report using the Discovery Interface, you must set the data source using the Software Deployment Database Logon dialog box. Specify the DSN, the Qualifier, and the Database name and type for the data source you defined. Enter the following values for the qualifier: Sybase database: tivoli Oracle database: TIVOLI Note: Your database qualifier may be different. Contact the database administrator for additional information. TDS for Software Deployment Analysis 1.0 Release Notes 14

27 Troubleshooting ODBC Driver Problems If you experience problems with the INTERSOLV ODBC driver version 3.01 for Sybases, contact Tivoli Customer Support, and request the updated INTERSOLV ODBC driver version 3.01 for Sybase. For more information about this issue, please contact Tivoli Customer Support by sending an to or by visiting the Tivoli Customer Support web site at Please be sure to include your customer identification information. Cube Building In the Tivoli Discovery Administrator the following message appears: Error building cube. If you click Details on the message dialog box, the following message appears: 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. While using the Discovery Interface, a Cognos PowerPlay report icon appears with the symbol (a circle bisected by a diagonal line), and you cannot open the report. What does this indicate? This symbol indicates that the cube is unavailable. Contact your Tivoli Discovery Administrator, and request that the cube be rebuilt. TDS for Software Deployment Analysis 1.0 Release Notes 15

28 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 Tds\cubes directory (where Tds\ is the TDS installation directory), replacing the existing cube. The queries returned insufficient data to build a cube. Verify your queries. You closed all the Tivoli Discovery Interface processes, and the cube still does not 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, and look for the process pplay.exe. If you find it, end the process, and rebuild the cube. Your cube does not automatically build 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. TDS for Software Deployment Analysis 1.0 Release Notes 16

29 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, a start date and end date, or a calculated value (for example, the last three months and the last six months). The calculated values are relative to the current date. The current period for a TDS cube is set using one of the following methods: Use the Date Range parameter and the <CubeName>_dt.txt to set the current period as shown in the following table: If the Date Range parameter is defined for a query using Explicit Date Range Calculated Values No Date Range Parameter in the Cube then the resulting date in the <CubeName>_dt.txt 1 is the End Date Calculated End Date Date the Cube is Built 1 where <CubeName> is the name of the cube that is being built If you want to use the date in the <CubeName>_dt.txt as the current period, then you must 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. 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. (This method is used by the Software Deployment Analysis Guide.) 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. TDS for Software Deployment Analysis 1.0 Release Notes 17

30 Report Problems The following error message appears: load_graph_from_powercube. This indicates that the cube has not been built. Build the cube. You tried to open a report, and 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 PowerPlay. Restart the Tivoli Discovery Interface, and your reports should open. You opened a report, and it contained no data. There are several reasons why you might not see any data in a report: There may be data in the report, but there is no data in 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. You cannot open a Crystal Report using the Discovery Interface. You may be addressing the wrong database. Click Options on the Software Deployment Database Logon dialog box to verify that the Data Source is properly defined by checking the DSN, the Qualifier, and the Database name and type. TDS for Software Deployment Analysis 1.0 Release Notes 18

31 Year 2000 (Y2K) Compliance THIS INFORMATION DOES NOT CONSTITUTE A CERTIFICATION OR WARRANTY, EXPRESS OR IMPLIED, OF ANY KIND. Inventory Database How do you ensure that the database that TDS accesses is Y2K compliant? To help ensure that TDS continues to select data correctly after January 1, 2000, the database used to store historical data must be Y2K certified. Please contact your system administrator and your database vendor if you have any questions concerning the Y2K compliance of your database. TDS for Software Deployment Analysis 1.0 Release Notes 19

32 Seagate Crystal Reports Version 6 How do you ensure that Seagate Crystal Reports is Y2K compliant? Seagate Crystal Reports version 6 is Y2K ready if you download the required patches. Seagate Software considers a product Year 2000 ready if the product performance and functionality are unaffected by processing of dates prior to, during and after the Year 2000, but only if all products (for example hardware, software and firmware) used with the product properly exchange accurate date data with it. Based on testing to date the following versions (in all available languages) of Seagate Crystal Reports, Seagate Crystal Info and Seagate Info are currently Year 2000 ready: 1 Seagate Crystal Reports 6 2 Seagate Crystal Reports 7 - Shipped Year 2000 Ready Product Name and Version - All Versions, STANDARD & PRO 1 For the compiled report option of Seagate Crystal Reports 6 to be Year 2000 ready, the appropriate version update must be downloaded from the Seagate Software Website. 2 If using a native connection to Xbase (.dbf) database files, a patch must be downloaded from the Seagate Software Website. Please refer to the attached FAQ for more information. The official disclosure is posted on Seagate Software s Year 2000 Readiness page at TDS for Software Deployment Analysis 1.0 Release Notes 20

33 Software Defects, Limitations, and Workarounds Defects The following is a list of some of the more important software defects. Workarounds are provided when applicable. None. Limitations The following is a list of known software limitations for the release of Software Deployment Analysis. Workarounds are provided when applicable. 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. Workaround: The recommend minimum resolution for your monitor is 800 x 600 pixels. TDS for Software Deployment Analysis 1.0 Release Notes 21

34 <Process_Name.exe> Application Error message dialog box appears with the following message: The instruction at <memory address> referenced memory at <memory address>. The could not be read. Workaround: Occasionally, when the cubes are built or their queries are exported, an application error message appears when TDS is used in combination with the Sybase INTERSOLV Inc ODBC driver Version This error message can appear frequently for a time and then suddenly cease to appear. If you experience this problem during cube build, wait until the transformation process has completed before clicking OK or Cancel on the error message dialog box. By waiting, you allow the cube to finish building. After the build process has completed, click OK on the error message dialog box. The Tivoli Discovery Administrator will close. Start the Tivoli Discovery Administrator and continue building any remaining cubes. Workarounds The following is a list of workarounds for this release. None. TDS for Software Deployment Analysis 1.0 Release Notes 22

35 Dependencies and Compliance Criteria Definition Application Dependencies The Software Deployment Analysis Guide runs using TDS version 2.0 The Software Deployment Analysis Guide requires the following: Installation of TME 10 Software Distribution 3.6 on your network Installation of TME 10 Inventory 3.6 on your network Database Dependencies The Software Deployment Analysis Guide uses ODBC Drivers to communicate with the Inventory database. Oracle 7.x, 8.x except 7.2x on AIX Sybase 10.x, x, x TDS for Software Deployment Analysis 1.0 Release Notes 23

36 Supported Platforms The Tivoli Decision Support Guide for Software Deployment Analysis version 1.0 runs on the following platforms: Windows NT 3.51 and higher Windows 95 Supported Languages This version of TDS for Software Deployment Analysis version 1.0 only supports the English language. TDS for Software Deployment Analysis 1.0 Release Notes 24

37 Functional Definition Note: The term subscribe is used to refer to workstations, personal computers, or other types of applicable computing devices. Data Sources The data source for the Software Deployment Analysis Guide is the Inventory database used by the TME 10 Inventory 3.6 Software Distribution (SWD) product. The Software Deployment Analysis Guide uses the following database tables: installed_sw_component software_filepack software_component Table installed_sw_component software_filepack software_component Modification SWD adds a row for each distribution event when a distribution is completed. If the same file packages is distributed several times, a new distribution event is added to the table for each time the file package is distributed. SWD adds a row for each unique file package name. SWD adds rows for each unique file package name. This table also contains an a software inventory of each system. Software Deployment Analysis Database Schema In the following there is the structure of the three tables mentioned above: TABLE: installed_sw_component Element Name Datatype NULL Accepted HARDWARE_SYSTEM_ID VARCHAR(64) NOT NULL SOFTWARE_COMPONENT_NAME VARCHAR(64) NOT NULL SOFTWARE_COMPONENT_VERSION VARCHAR(16) NOT NULL Field Description TDS for Software Deployment Analysis 1.0 Release Notes 25

38 Element Name Datatype NULL Field Description Accepted COMPONENT_LANGUAGE_EDITION VARCHAR(16) NOT NULL INSTALLED_FILEPACK_TIME VARCHAR(32) NOT NULL INSTALLED_FILEPACK_PATH VARCHAR(255) NULL FILEPACK_ACTIVATED INTEGER NULL FILEPACK_ACTIVATION_TIME VARCHAR(32) NULL TME_ADMINISTRATOR_ID VARCHAR(64) NULL ACTION_COMPLETED VARCHAR(32) NULL Distributed Distributed-Failed Committed Committed-Failed Removed Removed-Failed TABLE software_filepack Element Name Datatype NULL Accepted SW_FILEPACK_ID VARCHAR(128) NOT NULL FILEPACK_TYPE VARCHAR(64) NOT NULL FP_SOURCEHOST VARCHAR(32) NULL Field Description TABLE software_component Element Name Datatype NULL Field Description Accepted SOFTWARE_COMPONENT_NAME VARCHAR(64) NOT NULL SOFTWARE_COMPONENT_VERSION VARCHAR(16) NOT NULL COMPONENT_LANGUAGE_EDITION VARCHAR(16) NOT NULL SW_FILEPACK_ID VARCHAR(128) NULL MANUFACTURER_ID VARCHAR(64) NULL not used COMPONENT_MAJOR_VERSION VARCHAR(16) NULL not used COMPONENT_MINOR_VERSION VARCHAR(16) NULL not used COMPONENT_REVISION VARCHAR(16) NULL not used SOFTWARE_COMPONENT_DESCRIPTION VARCHAR(128) NULL not used SOFTWARE_COMPONENT_PLATFORM_OS VARCHAR(64) NULL not used SOFTWARE_COMPONENT_PLATFORM_HW VARCHAR(64) NULL not used SOFTWARE_COMPONENT_FUNCTION VARCHAR(16) NULL not used SOFTWARE_COMPONENT_SERIAL_NUMB VARCHAR(32) NULL not used SOFTWARE_COMPONENT_ID_CODE VARCHAR(32) NULL not used TDS for Software Deployment Analysis 1.0 Release Notes 26

39 Cubes (Tivoli Discovery Administrator) Software Distribution Analysis The Software Distribution Analysis multidimensional cube contains information from several of the Inventory database tables in order to provide metrics about distribution performance. Query Used to Build the Cube The following sql query is used to create the flat file in comma separated value (csv) format. This file will be used to create the multi-dimensional cube. SELECT MIN(T1.SOFTWARE_COMPONENT_NAME) AS SOFTWARE_COMPONENT_NAME, MIN(T1.SOFTWARE_COMPONENT_VERSION) AS SOFTWARE_COMPONENT_VERSION, T2.HARDWARE_SYSTEM_ID, T1.SW_FILEPACK_ID, T2.INSTALLED_FILEPACK_TIME, MIN(T2.FILEPACK_ACTIVATED) AS FILEPACK_ACTIVATED, MIN(T2.FILEPACK_ACTIVATION_TIME) AS FILEPACK_ACTIVATION_TIME, T2.ACTION_COMPLETED, MIN(T3.FILEPACK_TYPE) AS FILEPACK_TYPE, MIN(T3.FP_SOURCEHOST) AS FP_SOURCEHOST, MIN(T4.TME_OBJECT_ID) AS TME_OBJECT_ID, MIN(T4.BOOTED_OS_NAME) AS BOOTED_OS_NAME, MIN(T4.BOOTED_OS_VERSION) AS BOOTED_OS_VERSION, MIN(T4.TME_OBJECT_LABEL) AS TME_OBJECT_LABEL, MIN(T5.NETWORK_NODE_NAME) AS NETWORK_NODE_NAME, MIN(T5.NETWORK_NODE_ADDRESS) AS NETWORK_NODE_ADDRESS, MIN(T5.NETWORK_PROTOCOL) AS NETWORK_PROTOCOL, 1 AS ITEM_COUNT FROM?[DB Qualifier].SOFTWARE_COMPONENT T1,?[DB Qualifier].INSTALLED_SW_COMPONENT T2,?[DB Qualifier].SOFTWARE_FILEPACK T3,?[DB Qualifier].COMPUTER_SYSTEM T4, TDS for Software Deployment Analysis 1.0 Release Notes 27

40 ?[DB Qualifier].NETWORK_NODE T5 WHERE T1.SOFTWARE_COMPONENT_NAME = T2.SOFTWARE_COMPONENT_NAME AND T3.SW_FILEPACK_ID = T1.SW_FILEPACK_ID AND T2.HARDWARE_SYSTEM_ID = T4.HARDWARE_SYSTEM_ID AND T5.HARDWARE_SYSTEM_ID = T4.HARDWARE_SYSTEM_ID AND T5.NETWORK_PROTOCOL = TCP AND ( T5.CONFIG_CHANGE_TYPE in ( INSERT, UPDATE ) OR T5.CONFIG_CHANGE_TYPE IS NULL ) GROUP BY T2.HARDWARE_SYSTEM_ID, T1.SW_FILEPACK_ID, T2.INSTALLED_FILEPACK_TIME, T2.ACTION_COMPLETED CALCULATED COLUMNS CC_ALTERNATE_ACTION CC_COMPLETION_STATUS CC_SUCCESS_VALUE CC_FAILURE_VALUE CC_DAY CC_YYYY CC_YY CC_MONTH CC_HOUR CC_MINUTE CC_SECOND CC_HOUR_MINUTE CC_COMPLETE_HOUR CC_COMPLETE_DATE CC_DAY_OR_NIGHT CC_WEEKDAY CC_WEEKDAY_NAME CC_DAY_AND_TIME CC_WEEKDAY_OR_WEEKEND CC_FILEPACK_NAME_VERSION CC_OSNAME_VERSION CC_SUBSCRIBER_NAME_ADDR CC_IP_A_NETWORK CC_IP_B_NETWORK CC_IP_C_NETWORK String String Integer Integer Integer Integer Integer Integer Integer Integer Integer String String String String String String String String String String String String String String FUNCTIONS See Appendix A. TDS for Software Deployment Analysis 1.0 Release Notes 28

41 Parameters Used to Build the Cube Parameter name Type Default Values Day or Night Categorization 7 17 (7 AM to 5 PM) Dimensions The dimensions defined for the Software Distribution Guide determine the types of questions that can be answered by the application. 1. By Date: The time dimension associated with the model. By Date Month Week Day 2. By Day of Week: Permit categorization on Days of the Week. By Day of Week CC_WEEKDAY_OR_WEEK END CC_WEEKDAY_NAME CC_COMPLETE_DATE Special instuctions for model: The values for weekday names should not be deleted. TDS for Software Deployment Analysis 1.0 Release Notes 29

42 3. By Time of Day: Permit categorization by Day and Night and Time of Day By Time of Day CC_DAY_OR_NIGHT CC_HOUR_MINUTE CC_COMPLETE_HOUR Special Instuctions: CC_Hour_Minute will have entries for 24 hours in the format HH:MM [AP]M. These same hours will appear in Daytime or Night definition, the organization of the hours is based on the Parameter field Day or Night. 4. By Day and Time: Permit Categorization by a concatenated field of date and time By Day and Time CC_DAY_AND_TIME 5. By Entire Network: this dimension breaks the IP address down by the 4 parts of the IP address. A drill down is provided to relate IP Address to hostname. By Network Address CC_IP_A_NETWORK CC_IP_B_NETWORK CC_IP_C_NETWORK NETWORK_NODE_ADDRESS CC_SUBSCRIBER_NAME_ADDR TDS for Software Deployment Analysis 1.0 Release Notes 30

43 6. By Subscriber: This dimension presents the hostname for the subscriber. A drill down is provided to identify the IP Address for the subscriber and the date of the completed software distribution operation. By Subscriber TME_OBJECT_LABEL CC_SUBSCRIBER_NAME_ADDR CC_COMPLETE_DATE 7. By OS: This dimension is provided to relate the OS of the subscriber machine. This information must be available in the inventory table to be meaningful. By OS BOOTED_OS_NAME CC_OSNAME_VERSION TME_OBJECT_LABEL CC_SUBSCRIBER_NAME_ADDR CC_COMPLETE_DATE TDS for Software Deployment Analysis 1.0 Release Notes 31

44 8. By Filepackage: This dimension provides information related to the individual software distribution file packages. Drill down is provided to associate filepack version, subscriber, subscriber IP Address and file pack completion date. By Filepackage SOFTWARE_COMPONENT_NAME CC_FILEPACK_NAME_VERSION TME_OBJECT_LABEL CC_SUBSCRIBER_NAME_ADDR CC_COMPLETE_DATE 9. By Action: This dimension presents the actions which software distribution provides as the alternate actions category and the actual result of the operation. By Action CC_ALTERNATE_ACTIONS ACTION_COMPLETED 10. By Result: This dimension identifies if a software distribution action was a success or a failure. By Result CC_COMPLETION_STATUS ACTION_COMPLETED TDS for Software Deployment Analysis 1.0 Release Notes 32

45 Measures The measures defined for the Discovery Guide for Software Deployment Analysis determine key performance indicators using qualitative data. Measure Name Purpose Calculation Total number of actions Sum column Column = ITEM_COUNT Number of success actions Sum column Column = CC_SUCCESS_VALUE Number of failure action Sum column Column = CC_FAILURE_VALUE Percent of success Percentage column DPERCENT ( Number of success actions, Total number of actions ) Percent of failure Percentage column DPERCENT ( Number of failure actions, total number of actions ) Check of the Allowed Measures and Dimensions Combination The following table lists the measures of the cube and if they are in scope for the dimensions. Measures out of scope for a certain dimension produce invalid information or no data. Table Legend y = In scope g = Out of scope gx = Out of scope, measure allocated to the dimension TDS for Software Deployment Analysis 1.0 Release Notes 33

46 Dimension Measure Total number of actions Number of success actions Number of failure actions Percent of success Percent of failure By Date y y y y y By Day of Week y y y y y By Time of Day y y y y y By Day and Time y y y y y By Network Address y y y y y By Subscriber y y y y y By OS y y y y y By Filepackage y y y y y By Action y y y y y By Result y y y y y TDS for Software Deployment Analysis 1.0 Release Notes 34

47 Topics and Views (Interface) The TDS Discovery Guide for Software Deployment Analysis pose the following questions to be answered by data collected from the Inventory configuration repository. How effective are file package distributions? This topic helps you assess and improve your software distribution process based on the success or failure of each distribute, commit or remove operation. View Title Report Title Data Source Distribution actions that failed by file swd_001.ppr Software Distribution Analysis package File package distribution status swd_002.ppr Software Distribution Analysis File package status as of last distribution swd_fp_target(last).rpt Software Deployment Database What are the peak distribution periods? This topic will help you detect patterns in software distribution volume that are sensitive to the day of the week. This is important for establishing staffing plans and shift schedules for support personnel. View Title Report Title Data Source Volume of software distributions by time swd_003.ppr Software Distribution Analysis period What are the software distribution trends? This topic helps you to spot trends in the volume of software distributions to subscribers and for file package delivery. TDS for Software Deployment Analysis 1.0 Release Notes 35

48 View Title Report Title Data Source Software distribution history by swd_target(1day).rpt Software Deployment Database subscriber Success rate for software distribution by file package swd_004.ppr Software Distribution Analysis Which file package distributions have the most problems? This topic helps to identify problems with file package distributions related to specific types of systems or operating systems. View Title Report Title Data Source File package distribution history by swd_fp_target(history).rpt Software Deployment Database subscriber Software distribution status related to subscriber OS swd_007.ppr Software Distribution Analysis Which subscribers are receiving distributions? This topic helps identify software distribution recipients and evaluate the status of the distribute, commit and remove operations for the subscribers. View Title Report Title Data Source History of file package distributions to swd_target_fp(history).rpt Software Deployment Database subscribers Software distribution status by network swd_005.ppr Software Distribution Analysis address Status of last distribution to subscribers swd_target_fp(last).rpt Software Deployment Database Top 100 subscribers with failures swd_006.ppr Software Distribution Analysis TDS for Software Deployment Analysis 1.0 Release Notes 36