IBM Tivoli License Managerpublib.boulder.ibm.com/tividd/td/ITLM/GC23-4833-01/en_US/... · 2005-11-11 · Shortcut keys for starting tasks .....113 Shortcut keys for ... Provides descriptions

IBM Tivoli License Manager

License Administrator’s GuideVersion 1.1.1

GC23-4833-01

��

Second Edition (May 2003)

This edition applies to Version 1.1.1 of IBM Tivoli License Manager (program number 5724–D33) and to allsubsequent releases and modifications until otherwise indicated in new editions.

This edition replaces GC23-4833-00.

IBM welcomes your comments.

Address your comments to:

License Management Information DevelopmentRome Tivoli LabIBM Italia S.p.A.Via Sciangai, 5300144 RomeItaly

Fax Number: (+39) 06 5966 2077

Internet ID: [email protected]

When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

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

Note

Before using this information and the product it supports, read the information under “Notices” on page 115.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWho should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWhat this guide contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixPublications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Tivoli License Manager library . . . . . . . . . . . . . . . . . . . . . . . . . . . . xRelated publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xAccessing publications online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . xOrdering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiContacting software support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiConventions used in this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiOperating system-dependent variables and paths. . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Managing software product information . . . . . . . . . . . . . . . . . . . . . . . . . . 4Administering licenses and metering software use . . . . . . . . . . . . . . . . . . . . . . . 4Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Event management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Logs and support for problem determination . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Getting started on the Web interfaces . . . . . . . . . . . . . . . . . . 7Browser level and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Java Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Accessing the administration server . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Accessing a runtime server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About the Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

The portfolio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11The work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11The toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Web interface tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 3. Managing customers and administrators . . . . . . . . . . . . . . . . 15Adding customers to the administration server database . . . . . . . . . . . . . . . . . . . . 16Updating or deleting customer details . . . . . . . . . . . . . . . . . . . . . . . . . . 16Adding administrator accounts to the administration server database . . . . . . . . . . . . . . . . 17Updating or deleting administration account details . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4. Managing a customer infrastructure . . . . . . . . . . . . . . . . . . 23Defining the monitoring structure for a customer . . . . . . . . . . . . . . . . . . . . . . . 23

Registering a runtime server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Reviewing and changing runtime servers . . . . . . . . . . . . . . . . . . . . . . . . 25Adding divisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Reviewing and changing divisions. . . . . . . . . . . . . . . . . . . . . . . . . . . 28Deploying an agent on a node . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Reviewing and deleting agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Managing demographic information . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Adding nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Reviewing and changing nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

© Copyright IBM Corp. 2001, 2003 iii

Adding application users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Changing or deleting user details . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 5. Managing software entitlement and license pool details. . . . . . . . . . 43Selecting a product for entitlement or license pool maintenance . . . . . . . . . . . . . . . . . . 43Maintaining entitlement settings for a product. . . . . . . . . . . . . . . . . . . . . . . . 45Creating a license pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Setting license distribution parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 50Updating a license pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Changing license distribution settings . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Changing target distribution settings . . . . . . . . . . . . . . . . . . . . . . . . . . 55Changing user distribution settings . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 6. Reporting software usage information . . . . . . . . . . . . . . . . . 59Producing a historical snapshot software usage report . . . . . . . . . . . . . . . . . . . . . 59

Requesting the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Navigating the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Producing a software usage trend analysis report . . . . . . . . . . . . . . . . . . . . . . . 67Requesting the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Using the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Producing a software usage level analysis report . . . . . . . . . . . . . . . . . . . . . . . 71Producing a realtime software usage report. . . . . . . . . . . . . . . . . . . . . . . . . 75

Requesting the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Navigating the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Exporting reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 7. Managing and reporting inventory information. . . . . . . . . . . . . . 83Scheduling inventory scans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Producing a software inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Requesting the inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . . 85The software inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 8. Managing product information. . . . . . . . . . . . . . . . . . . . . 91Catalogs and unknown file information . . . . . . . . . . . . . . . . . . . . . . . . . . 91Using the catalog manager to update the master catalog . . . . . . . . . . . . . . . . . . . . 92

Adding unknown files to the master catalog . . . . . . . . . . . . . . . . . . . . . . . 94Importing the IBM catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Modifying entries in the master catalog . . . . . . . . . . . . . . . . . . . . . . . . . 98

Appendix A. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Message details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Appendix B. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Navigating the Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Shortcut keys for starting tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Shortcut keys for performing toolbar actions . . . . . . . . . . . . . . . . . . . . . . . . 114

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

iv IBM Tivoli License Manager: License Administrator’s Guide

Figures

1. Structural relationship of Tivoli License Manager components . . . . . . . . . . . . . . . . . 32. The parts of the Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 113. Product list in the historical software usage report . . . . . . . . . . . . . . . . . . . . 624. Product details in the historical software usage report . . . . . . . . . . . . . . . . . . . 645. List of agents in the historical software usage report . . . . . . . . . . . . . . . . . . . . 646. License pools in the historical software usage report . . . . . . . . . . . . . . . . . . . . 657. Sessions in the historical software usage report . . . . . . . . . . . . . . . . . . . . . 668. Trend Analysis report in step format . . . . . . . . . . . . . . . . . . . . . . . . . 709. The Level Analysis report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

10. Product list in the realtime software usage report . . . . . . . . . . . . . . . . . . . . . 7811. Product details in the realtime software usage report. . . . . . . . . . . . . . . . . . . . 7912. License pools in the realtime software usage report . . . . . . . . . . . . . . . . . . . . 8013. Open sessions in the realtime software usage report . . . . . . . . . . . . . . . . . . . . 8114. Software inventory report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

© Copyright IBM Corp. 2001, 2003 v

vi IBM Tivoli License Manager: License Administrator’s Guide

Tables

1. Toolbar icons and actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122. Web interface tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Tivoli License Manager message categories . . . . . . . . . . . . . . . . . . . . . . 1034. Tivoli License Manager messages . . . . . . . . . . . . . . . . . . . . . . . . . . 1045. Key combinations for navigating the Web interface . . . . . . . . . . . . . . . . . . . . 1136. Key combinations for starting tasks . . . . . . . . . . . . . . . . . . . . . . . . . 1137. Key combinations for toolbar actions. . . . . . . . . . . . . . . . . . . . . . . . . 114

© Copyright IBM Corp. 2001, 2003 vii

viii IBM Tivoli License Manager: License Administrator’s Guide

About this guide

This guide describes IBM® Tivoli® License Manager.

It contains a general overview of the functionality of Tivoli License Manager andinstructions on using the Web interfaces to set up a monitoring infrastructure,define licensing conditions, and produce reports.

Who should read this guideThis guide is intended for anyone who needs to use the Tivoli License Manageruser interfaces. This includes:v Administrators who are responsible for setting up the infrastructure for

monitoring license compliance and software usagev License administrators who are responsible for recording the terms and

conditions of procured licensesv Managers who need information about software usage and license availability to

assist them in making decisions about license procurement

What this guide containsThis guide contains the following sections:v Chapter 1, “Overview” provides a summary of the benefits of Tivoli License

Manager and a brief description of the components that it includes.v Chapter 2, “Getting started on the Web interfaces” summarizes the online

functionality of Tivoli License Manager.v Chapter 3, “Managing customers and administrators” provides instructions for

the online tasks of creating and managing the customers and administrators ofthe license management implementation.

v Chapter 4, “Managing a customer infrastructure” provides instructions for theonline tasks required for setting up the monitoring infrastructure.

v Chapter 5, “Managing software entitlement and license pool details” providesinstructions for the online tasks involved in administering licenses andmonitoring the presence and usage of software products.

v Chapter 6, “Reporting software usage information” provides instructions aboutproducing and navigating the realtime and historical software usage reports thatare available from the Web interfaces.

v Chapter 7, “Managing and reporting inventory information” providesinformation about scheduling inventory scans of monitored machines andproducing inventory reports.

v Chapter 8, “Managing product information” provides an overview of themanagement and use of product catalogs and instructions for updating themaster catalog by using the catalog manager application.

v Appendixes, including a list of the error messages used in Tivoli LicenseManager and a summary of the keyboard alternatives that make the use of theinterface accessible to people with some physical disabilities.

© Copyright IBM Corp. 2001, 2003 ix

PublicationsThis section lists publications in the Tivoli License Manager library and relateddocuments. It also describes how to access Tivoli publications online and how toorder Tivoli publications.

Tivoli License Manager libraryThe Tivoli License Manager library also includes the following books:v IBM Tivoli License Manager: System Administrator’s Guide, GC23-4834-01

Provides planning, installing, and managing the Tivoli License Manager productv IBM Tivoli License Manager: Data Dictionary, GC23-4835-01

Provides descriptions of the database tables and indexes maintained in the TivoliLicense Manager administration server database.

v IBM Tivoli License Manager: Warehouse Enablement Pack Implementation Guide,SC32-1244-01Provides instructions and other information related to enabling the use of theTivoli Enterprise™ Data Warehouse with Tivoli License Manager.

v IBM Tivoli License Manager: Release Notes, SC23-4848-01Provides a summary of changes made in a release, documents known errors andworkarounds, and includes information about any product changes that couldnot be included in the main documentation.

Related publicationsThe Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. The Tivoli Software Glossary is available, in English only,at the following Web site:

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

Accessing publications onlineThe documentation CD contains the publications that are in the product library,other than the Release Notes, in all supported languages. The format of thepublications is PDF, HTML, or both. To access the publications using a Webbrowser, open the allpubs.html file. The file is in the root directory on thedocumentation CD. Select the language of your choice, and an Information Centerfor the product in that language is displayed. Select the publication and the formatin which you want to view it.

Note: On Windows platforms an autorun exec opens the allpubs.html file in yourdefault browser.

IBM posts the IBM Tivoli License Manager: Release Notes along with publications forthis and all other Tivoli products, as they become available and whenever they areupdated, to the Tivoli Software Information Center Web site. The Tivoli SoftwareInformation Center is located by using the following Web address:

http://www.ibm.com/software/tivoli/library/

Click the Product manuals link to access the Tivoli Software Information Center.

Click the IBM Tivoli License Manager link to access the product library.

x IBM Tivoli License Manager: License Administrator’s Guide

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

http://www.ibm.com/software/tivoli/library/

http://publib.boulder.ibm.com/tividd/td/IBMTivoliLicenseManager1.1.html

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

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

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

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

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

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

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

This product is operated using a Web browser, which has certain built-inaccessibility features, and has been provided with specific shortcut keys fornavigating the Web interface, starting tasks, and performing toolbar actions.

For additional information, see the Accessibility appendix, Appendix B,“Accessibility”, on page 113.

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

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

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

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

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

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

About this guide xi

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

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

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

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

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

Conventions used in this guideThis guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that areotherwise difficult to distinguish from surrounding text

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

v Column headings in a tablev Keywords and parameters in text

Italic

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

Monospace

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

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

<text> Indicates a variable in a path name. For example in the path<INSTALL-DIR>\tlm, INSTALL-DIR depends on the location whereyou have installed the component, while \tlm is constant.

Operating system-dependent variables and pathsThis guide uses the Windows convention for specifying environment variables andfor directory notation.

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

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

xii IBM Tivoli License Manager: License Administrator’s Guide

Chapter 1. Overview

Tivoli License Manager is a Web-based solution that provides software usagemetering and license allocation services on Windows and UNIX platforms. It canbe scaled to meet the needs of large and small customers, and supports themanagement of multiple customers, for example by service providers.

This chapter provides a summary of the capabilities of Tivoli License Manager andof the benefits that it can provide, as follows:v A summary of the benefits of using Tivoli License Manager. See “Benefits”.v An overview of the architecture of a Tivoli License Manager installation. See

“Components” on page 2.v An overview of the processes for collecting and maintaining the information

about the software products that are managed and metered by Tivoli LicenseManager. See “Managing software product information” on page 4.

v An overview of different options for license allocation that are available withinTivoli License Manager. See “Administering licenses and metering software use”on page 4.

v A summary of the facilities for realtime and historical reporting that areprovided by Tivoli License Manager. See “Reporting” on page 5.

v A summary of the facilities for sending notifications about license managementevents. See “Event management” on page 5.

v A summary of the facilities for logging events and tracing problems within thecomponents of Tivoli License Manager. See “Logs and support for problemdetermination” on page 5.

BenefitsTivoli License Manager provides the following benefits:v Consolidation of information about products installed and software usagev The capability to compare the figures for procured, installed, and used licensesv The capability to enforce licensing agreementsv Maintenance of historical software usage information and the provision of

reports to assist in forward planning for license needsv Realtime reporting of software and license usage informationv Ability to export reports to a standard XML interfacev A method of metering software usage even for products that have no license

requirementv Automatic generation of alerts when license usage reaches a defined levelv A flexible architecture that enables you to scale the installation to fit your license

management needsv A flexible method of defining rules for license allocation, including the facility to

assign pools of licenses to specific users, nodes, and groups of nodesv Security of confidential information ensured by the maintenance of security

profiles for access to the Web interface, and by the encryption of data duringtransmission between the administration and runtime servers

© Copyright IBM Corp. 2001, 2003 1

ComponentsAny Tivoli License Manager installation has the following components:

Tivoli License Manager agentA license management agent must be deployed on each customer node that isto be monitored by Tivoli License Manager. Each agent has the followingfunctions:v Performing an inventory of the software installed on the node and forwards

this information to the runtime serverv Detecting the starting or stopping of a software product and communicates

this information to the runtime server so that a license can be assigned orreleased

You can set the agent to automatically apply any upgrades that are availableon the runtime server.

Tivoli License Manager runtime serverA Tivoli License Manager installation has at least one runtime server and canhave several. Each runtime server provides the following facilities:v A repository for information about the software installed on the agents that

are managed by the serverv The capability to assign and release the licenses that are assigned to the

server according to the rules defined for each set of licensesv The capability to generate and send e-mails to provide a notification about

events that have occurred on the server or its agentsv A Web interface that can be used to deploy the agents to nodes that are to

be monitored and to produce realtime reports of license usage for softwarerunning on the managed agents

Tivoli License Manager administration serverA Tivoli License Manager installation has a single administration server. Itprovides the following facilities:v A central repository of product, license agreement, license usage, and

customer informationv A Web interface that can be used to perform license management and

administration tasks and to produce historical reports of license usage overtime

Figure 1 on page 3 shows the basic Tivoli License Manager structure: a singlecentral administration server, a runtime server, and multiple agents.

Components

2 IBM Tivoli License Manager: License Administrator’s Guide

You can expand this structure, adding more runtime servers on different machinesto improve performance in an environment where there are many agents. You canalso add divisions within which agents can be grouped so that multiple agents canbe selected as a single entity. For example, you can use divisions to limit theavailability of licenses to the nodes that are monitored by agents within a specifieddivision.

There is always only one administration server, which maintains the centralknowledge-base of product, license, and user information in an associated DB2®

database. The administration server can be used to manage the licensing needs ofmultiple customers or can be dedicated to a single customer.

In all Tivoli License Manager installations, the runtime servers and agents must beassigned to a customer. In a self-managed scenario, there is normally only onecustomer to which all components belong. A service provider, managing thelicenses of multiple customers, defines a separate structure of runtime servers andagents for each customer. Runtime servers cannot be shared between customers.

The management of the Tivoli License Manager components, the definition of thelicense management rules, and the management of events that occur duringmonitoring are the responsibility of Tivoli License Manager administratorsassigned to the customer.

For information on defining the structure of your Tivoli License Managerinstallation, see Chapter 4, “Managing a customer infrastructure”, on page 23. Forinformation on defining customers and administrators, see Chapter 3, “Managingcustomers and administrators”, on page 15.

RuntimeServer

DBMSAdministrationServer

Agents

DBMS

Figure 1. Structural relationship of Tivoli License Manager components

Components

Chapter 1. Overview 3

Managing software product informationTivoli License Manager maintains a master catalog where details of all theproducts that can be monitored by Tivoli License Manager are stored. This catalogresides on the administration server and a copy of changes made to it areperiodically downloaded to each runtime server.

The master catalog is based on a version of the Tivoli signatures file. An initialmaster catalog is installed on the administration server machine.

You can add entries to the catalog, using information from the following sources:

The unknown files tableThis table is compiled from information collected by the agents aboutapplications that started but could not be monitored because they were not inthe catalog. The catalog manager allows you to add these files to the catalogby creating new catalog entries or by assigning files to existing entries.

The IBM catalogLike the master catalog, the IBM catalog is based on a version of the Tivolisignatures file. You can use the catalog manager to merge this file with themaster catalog when you receive a new version from IBM.

In addition to the copy of the master catalog, each runtime server has a runtimecatalog. This catalog is a subset of the master catalog. It only includes those entriesfrom the master catalog that have licenses defined or that relate to products thathave been discovered running on nodes by agents that are assigned to the server.

For more information about catalogs, unknown files, and using the catalogmanager, see Chapter 8, “Managing product information”, on page 91.

Administering licenses and metering software useYou can use Tivoli License Manager to enforce the conditions of procured licenses,to meter the usage of software products by recording and reporting their presenceand levels of usage on monitored nodes, or to do both of these.

Administration of licenses and metering of software depends on the license poolsthat exist for each product. If you have procured licenses and want to enforce theirconditions, you can define license pools to reflect the terms and conditions of thelicenses. If you only want to track the usage of software products, you can use thedefault license settings provided with Tivoli License Manager.

The information specified for a license pool includes the number of licensesavailable, any limitations on the availability of the license pools to specified usersand nodes, and rules that control allocation of licenses when the limit is reached.

You can define a license pool to enforce an existing license agreement or you canuse a default license pool to simply monitor the usage of software, withoutapplying any limits.

By default, license pools are available to all valid users on the monitored nodes.However, you can specify that a license pool is available only to selected users oronly on selected monitored nodes.

For more information about defining license pools, see Chapter 5, “Managingsoftware entitlement and license pool details”, on page 43.

Managing software information


You define license pools on the administration server, and they are automaticallydeployed to the appropriate runtime servers. The license pool for a product isaccessed when the agent communicates to the runtime server that a monitoredapplication has started. Availability is checked, and the license is allocated orrefused accordingly. When the application closes, the agent communicates with theruntime server, and the license is released.

ReportingTivoli License Manager provides both realtime and historical reporting.

You can obtain realtime reports on the status of software usage on a specificruntime server by accessing the server Web pages with a suitable browser.

Historical reports of inventory and software usage information are available on theadministration server. Tivoli License Manager includes a set of preconfiguredreports for the analysis of collected software usage and inventory data.

For more information about reporting, see Chapter 6, “Reporting software usageinformation”, on page 59 and Chapter 7, “Managing and reporting inventoryinformation”, on page 83.

Event managementThe event management component can identify events that require the attention ofthe system administrator and forward them to an external e-mail system.

Events are generated on the administration server and on each runtime server.These include events regarding the state of the license pools. For example, an eventis generated if the number of licenses in use for a pool has reached the specifiedthreshold or if the full entitlement is used. The event management component isable to determine that an agent is either down or has been uninstalled and cangenerate and forward an e-mail to alert the person responsible. You can specifywhich administrators are to receive notifications.

For more information about event management, see the IBM Tivoli License Manager:System Administrator’s Guide.

Logs and support for problem determinationTivoli License Manager provides a trace service on the administration server andon all runtime servers. This service allows you to trace all activities generated byTivoli License Manager.

You can determine the level of detail you record by setting a trace level on eachserver. Depending on the trace level you select, the trace service records details oferrors, operations, data movement, and processes.

For more information about problem solving, see the IBM Tivoli License Manager:System Administrator’s Guide.

Administering and metering

Chapter 1. Overview 5


Chapter 2. Getting started on the Web interfaces

The aim of this chapter is to help you to start using the Tivoli License ManagerWeb interfaces.

The main Web interface is on the administration server. Using this interface, youcan request historical reports and perform Tivoli License Manager systemdefinition and license maintenance tasks.

Web interfaces are also provided on each runtime server. You can use theseinterfaces to request realtime reports and to deploy agents.

This chapter provides the following information:v Instructions for logging on to the administration server. See “Accessing the

administration server” on page 8.v Instructions for logging on to a runtime server. See “Accessing a runtime server”

on page 9.v A description of the components of the Web interface, including general

information that is relevant to all Web interface tasks. See “About the Webinterface” on page 11.

v A summary of functions available on the interface and where to find them. See“Web interface tasks” on page 12.

Note: When logging on to any Tivoli License Manager server for the first time,you must use the user ID tlmroot. When you are logged on as tlmroot youcan create accounts for the administrators who will work on the server.

The initial password for the tlmroot user is system. You should change thison each server as soon as you have logged on. See “Updating or deletingadministration account details” on page 19 for instructions on changing thepassword of an administrator.

Browser level and settingsYou access the Web interfaces using a Netscape or Microsoft® Internet Explorerbrowser. If you are working on the main Web interfaces of the administration andruntime servers, you must have one of the following browser versions or a laterversion:v Internet Explorer 5.5v Netscape Navigator 6.2

Users accessing the agent registration interface to deploy the Tivoli LicenseManager agent on their machines can use an earlier browser version for this task,as follows:v Internet Explorer 5.0 or laterv Netscape Navigator 4.7.x or later

Notes:

1. For Sun platforms, you can only use Netscape Navigator.2. On AIX®, Netscape Navigator 4.79 is recommended.


The default browser settings are acceptable in most cases, but you should checkthat following is true:v JavaScript™ is enabled.v The cache is set to automatically refresh.

In addition, any programs that prevent additional windows from openingautomatically must be disabled.

Java Virtual MachineThe Tivoli License Manager agent uses a Java Virtual Machine. This is normallybundled as part of your Web browser or operating system. However, on someplatforms, you may have to specifically download and install the Java VirtualMachine that corresponds to the Web browser you want to use.

One platform where this occurs is on Windows NT 4.0 running Internet Explorer6.0. The symptom you see is that the agent registration starts but then hangs. Go tothe Microsoft Web site and download and install the Java Virtual Machine.

Accessing the administration serverTo access the Web interface of the administration server:1. Using a browser, access the administration server logon page.

The address of the page is http:\\<server name>:<port>\slmadmin\login.

Notes:

a. If you are using the default port (80), you do not need to specify the port inthe page address.

b. If you are using a secure socket layer (SSL) connection, you must specifyhttps instead of http.

2. Type the User Name and Password of a Tivoli License Manager administratorand click OK.You can create administrators on the administration server Web interface whenyou are logged on as the superuser tlmroot. The initial password for tlmroot issystem.

Settings


A welcome panel appears on the main part of the window. From this panel.you can select a customer from the drop-down list if you are working on acentral administration site with multiple customers.

The portfolio on the left of the page provides a navigable list of the tasks youcan perform on the administration server.

Accessing a runtime serverTo access the Web interface of a runtime server:1. Using a browser, access the runtime server logon page.

The address of the page is http:\\<server name>:<port>\slmruntime\login.

Notes:

a. If you are using the default port (80), you do not need to specify the port inthe page address.

b. If you are using a secure socket layer (SSL) connection, you must specifyhttps instead of http.

Accessing the administration server

Chapter 2. Getting started on the Web interfaces 9

2. Type the User Name and Password of a Tivoli License Manager administratorand click OK.You should have one administrator for each customer on the administrationserver. You can create administrators on the runtime server Web interface whenyou are logged on as the superuser tlmroot. The initial password for tlmroot issystem.

A welcome panel appears on the main part of the window.

The portfolio on the left of the page provides a navigable list of the tasks youcan perform on the runtime server.

Accessing a runtime server


About the Web interfaceThis section aims to help you become familiar with features of the Tivoli LicenseManager Web interface that are common to all tasks.

The Web interface consists of the following parts:v The portfolio, where you select the task you want to performv The work area, where you supply information and make selections that are

needed to complete the task you selectedv The toolbar, which contains a number of icons representing actions that are

available within tasks, for example, getting help

Figure 2 shows a page on the Tivoli License Manager Web interface and indicatesthe different parts of the interface

The portfolioThe portfolio shows a list of all the task groups that are available on the Webinterface. Most task groups include several tasks. For example, the Software Usagetask group includes the software usage snapshot, trend analysis, and level analysisreports. When you click a task group, it expands and you can see the individualtasks it includes. When you click a task name, the first dialog of the task appearsin the work area.

The work areaThe dialogs that you must complete to perform a task appear in the work area ofthe Web interface. They consist of controls where you must supply or selectinformation, as follows:v Text fields that allow you to enter information by typing. These boxes can have

restrictions on the type of characters that can be used. For example, the productname field shown in Figure 2 allows any alphanumeric characters, but an inputbox that is part of a date would expect a numeric input that can be interpretedas a valid date.

Figure 2. The parts of the Web interface

The Web interface


v List boxes that allow you to select from a set of possible values. Lists can bestatic or dynamic.Static lists show a set of fixed values. For example, when defining a license pool,you must choose a target type from one of four possible values.Dynamic lists are those that show values that are user-defined. For example, alist of divisions includes all the divisions that have been defined for the selectedcustomer. As dynamic lists can include a large number of items, the list issometimes truncated to a default maximum of 5 000.Where it is possible thatlists might include more items than this maximum the dialogs provide a form ofpre-selection. For example, because the agent list is likely to be long, the TivoliLicense Manager wizards that include agent selection, allow you to limitselection to selected divisions. The resulting agent list only includes agents forthe selected divisions.Generally, static lists allow the selection of a single value. In a dynamic list youcan select multiple items.

v Radio buttons, which allow you to choose one of a small group of pre-definedoptions.

Note: Any control that is marked with an asterisk (*) is a required field.

The toolbarTable 1 lists the toolbar icons that are available and action that is taken when youclick each icon.

Table 1. Toolbar icons and actions

Icon Action

Toggles between the default view where the interface is divided betweenthe portfolio and the work area and a view where the portfolio is hidden.

Displays the home page where you can select a different customer towork with.

Refreshes the display to show the most recent data.

Logs the user off the Web interface.

Opens the accessibility help window where you can read about keyboardalternatives for navigating the interface and performing actions.

Opens the Tivoli License Manager information where you can see productversion and copyright information.

Opens the help window for the current dialog.

Web interface tasksTable 2 on page 13 summarizes the tasks that you can perform on the Webinterfaces. For each task, the table indicates whether you perform the task on theadministration or runtime server and provides a reference to instructions forperforming the task.

Note: You can perform most of the tasks by accessing the appropriate server fromany node that has a browser that meets the Tivoli License Managerprerequisites. The exception to this is deployment of the agent. This taskmust be performed from the node where the agent is to be deployed.

Work area


Table 2. Web interface tasks

Task Server See

Adding customers to theadministration serverdatabase

Administration “Adding customers to theadministration server database” onpage 16

Making changes to customerdetails

Administration “Updating or deleting customer details”on page 16

Removing customers from theadministration serverdatabase

Administration “Updating or deleting customer details”on page 16

Adding Tivoli LicenseManager administrators

Administrationand Runtime

“Adding administrator accounts to theadministration server database” onpage 17

Changing administratordetails and assigningcustomers to administrators


“Updating or deleting administrationaccount details” on page 19

Removing administratoraccounts


“Updating or deleting administrationaccount details” on page 19

Registering runtime serversthat you have installed

Administration “Registering a runtime server” onpage 24

Reviewing and modifyingruntime servers that arealready registered

Administration “Reviewing and changing runtimeservers” on page 25

Adding divisions Administration “Adding divisions” on page 27

Reviewing, modifying, ordeleting existing divisions

Administration “Reviewing and changing divisions” onpage 28

Registering nodes in theadministration serverdatabase

Administration “Adding nodes” on page 35

Reviewing, modifying ordeleting node information

Administration “Reviewing and changing nodes” onpage 36

Deploying the agent on anode

Runtime “Deploying an agent on a node” onpage 30Note: For this task, you do not need tolog on to the runtime server.

Reviewing or deletingdeployed agents

Administration “Reviewing and deleting agents” onpage 32

Defining users of monitoredapplications

Administration “Adding application users” on page 38

Updating application userinformation

Administration “Changing or deleting user details” onpage 39

Removing application usersfrom the administrationserver database

Administration “Changing or deleting user details” onpage 39

Maintaining general licenserules for a product

Administration “Maintaining entitlement settings for aproduct” on page 45

Creating a license pool for aproduct.

Administration “Creating a license pool” on page 47

Updating a license pool for aproduct

Administration “Updating a license pool” on page 52

Tasks


Table 2. Web interface tasks (continued)

Task Server See

Changing the users andtargets that have access to alicense pool

Administration “Changing license distribution settings”on page 54

Producing a detailed reportof software usage as it was ata specified date and time

Administration “Producing a historical snapshotsoftware usage report” on page 59

Producing charts for theanalysis of trends in softwareusage over a specified periodof time

Administration “Producing a software usage trendanalysis report” on page 67

Producing a summary of thelevel of usage of softwareproducts over a specifiedperiod of time

Administration “Producing a software usage levelanalysis report” on page 71

Producing a report of thecurrent software usage onagents registered with aspecific runtime server

Runtime “Producing a realtime software usagereport” on page 75

Defining a schedule forinventory scans of monitorednodes

Administration “Scheduling inventory scans” on page 83

Producing a historical reportof inventory information thathas been collected frommonitored nodes

Administration “Producing a software inventory report”on page 85

Tasks


Chapter 3. Managing customers and administrators

This chapter describes the functions on the administration server Web interfacethat allows you to create records for the administrators who will use the Webinterfaces and for customers and to assign customers to the administrators.

Each customer is the owner of its Tivoli License Manager components, licensepools, and reports. Whenever you log on to the administration server, you mustselect a customer. The Tivoli License Manager components, license pools, andreports that you can work with are those that belong to selected customer.

Administrators are the users who can log on to the Web interfaces. On theadministration server, you must define administrators and assign customers tothem. When the administrator logs on to the administration server, the onlycustomers available for selection are those that are assigned to the administrator.All customers must have at least one administrator for administration server tasks,and might have several, because administrators can have different levels of accessto the administration server functions. You should also create at least oneadministrator for each customer on the administration server.

When you have created a customer and assigned it to an administrator, you cancreate a monitoring structure for the customer. See Chapter 4, “Managing acustomer infrastructure”, on page 23.

The following tasks are described:v Creating details of a customer whose site is monitored from the application

server. See “Adding customers to the administration server database” onpage 16.

v Changing or deleting the details of a customer. See “Updating or deletingcustomer details” on page 16.

v Creating an account for a Tivoli License Manager administrator. See “Addingadministrator accounts to the administration server database” on page 17.

v Changing the details of an administrator account. See “Updating or deletingadministration account details” on page 19.

You perform these tasks using a browser to access the administration or runtimeserver interface. See Chapter 2, “Getting started on the Web interfaces”, on page 7for instructions on logging on to Web interfaces.

To perform these tasks you must be logged on to the Tivoli License Managerserver Web interface as tlmroot.


Adding customers to the administration server databaseYou use this function to record details of the customers whose licenses you aremonitoring.

To add a customer to the administration server database, complete the followingsteps:1. In the portfolio, click Administration. When the Administration task group

opens to show a list of tasks, click Customers.

2. Click Create.

3. Supply the details of a customer whose licenses you are managing.4. Click Finish.

The customer details are recorded in the administration server database. Youcan now select this customer using the Change Customer function, and set upthe topology of runtime servers, agents, and application users for the customer.See Chapter 4, “Managing a customer infrastructure”, on page 23.

Updating or deleting customer detailsTo change or delete information for a customer whose details are recorded on theadministration server database, complete the following steps:

Adding administration server customers


1. In the portfolio, click Administration. When the Administration task groupopens to show a list of tasks, click Customers.

2. Select the customer you want to update or delete from the list of customers.3. Click Next.

4. If you want to delete the customer, check the details, and if this is the correctcustomer, click Delete.

Note: When you delete a customer, you also delete the entire infrastructure ofruntime servers, agents, divisions, nodes, end users, and licenses that isassociated with the customer and all the data that has been collected forthe customer.

If you want to change the customer details, make the required changes andthen click Finish.

Adding administrator accounts to the administration server databaseYou use this function to create accounts for administrators who are entitled to usethe Tivoli License Manager Web interface.

Note: This function is available on both the administration and runtime serverinterface. On the administration server, define administrators who are to usethe administration server interface and receive notifications generated by the

Updating or deleting details

Chapter 3. Managing customers and administrators 17

administration server. On each runtime server, define administrators whoare to use the runtime server interface and receive notifications generated bythat runtime server.

To add an administration account to the administration server database, completethe following steps:1. In the portfolio, click Administration. If you are working on the administration

server, the Administration task group opens to show a list of tasks; clickAccounts.

2. Click Create.

3. Supply the details of the user who is to be allowed access to the Web interface.If the administrator is to receive notifications, you must specify the e-mailaddress to which the notifications are to be sent.If you are defining an account on the administration server Web interface, theadministrator will receive notifications generated by the administration serverfor events relating to a customer that is assigned to the administrator.If you are

Adding administrator accounts


defining an account on a runtime server, the administrator will receive allnotifications generated by events on the runtime server.For Information about the different types of event notifications generated bythe administration and runtime servers, see the IBM Tivoli License Manager:System Administrator’s Guide.

4. Click Finish.The account details are recorded in the administration server database. Theuser can now log on the Web interface using the logon name and passwordthat you have specified.

Note: The administrator currently has no customers assigned and no profile toassign an access level. To select a profile and assign customers to theadministrator, you must update the administration account details. See“Updating or deleting administration account details”.

Updating or deleting administration account detailsYou can select an existing administration account and perform any of the followingtasks:v Change the account details, for example, the user’s logon name, or e-mail

addressv Define the user’s level of access to Web interface functions (administration

server only)v Select the customers that are assigned to the user (administration server only)v Change the user’s passwordv Delete the administration account

To change or delete information for an administration account, complete thefollowing steps:1. In the portfolio, click Administration. If you are working on the administration

server, the Administration task group opens to show a list of tasks; clickAccounts.

Adding administrator accounts


2. Select an account from the list and click Change.

3. If you want to delete the account, check the details, and if this is the correctaccount, click Delete.

4. You can change the account details and notification status you defined.If this is a new account, you must do the following:a. Select a profile. The profile defines the user’s level of access to the

administration server functions, as follows:

AdministratorThe user can perform all tasks on the administration server Webinterface that relate to a customer that is assigned to him or her. Theonly tasks on the Web interface that are not available to theadministrator are managing customers and managing administrator’saccounts. These tasks are reserved for the user tlmroot.

Licensing managerThe user can define software entitlement settings and license pools forproducts, and determine which agents and users should have access tolicenses. These tasks are accessed using the Software Entitlement menuoption.

Software resources managerThe user can request the inventory and software usage reports.

Updating administration accounts


5. If you want to change the administrator’s password, click Password.

6. Type the password and then confirm it by retyping it.7. Click Finish. The Change Password window closes.8. When you have made the necessary changes to the account, click Finish.





Chapter 4. Managing a customer infrastructure

This chapter provides instructions for the tasks related to creating and managingthe components of a Tivoli License Manager installation for a selected customer.The topology has two types of component:v Components that form the structure of the Tivoli License Manager

implementation for a customer. See “Defining the monitoring structure for acustomer”.

v Components that record demographic information. See “Managing demographicinformation” on page 34.

You perform these tasks using a browser to access the Web interfaces. SeeChapter 2, “Getting started on the Web interfaces”, on page 7 for information aboutthe tasks available on each server and for instructions on logging on to theadministration and runtime servers.

All of the components must belong to a customer, whose details have beenrecorded in the administration server database. You are prompted to select thecustomer you want to work with when you log on to the administration server. Tochange the customer during a session, click the Home icon on the tool bar andselect a different customer from the list that appears. For instructions for creating acustomer, see “Adding customers to the administration server database” onpage 16.

Defining the monitoring structure for a customerIn a Tivoli License Manager implementation, you must define a monitoringstructure for each customer. The structure comprises the following:v The runtime servers that have been installed. These must be registered with the

administration server before they can be used.v Agents that you must deploy to nodes that are to be monitored. You must

decide on the distribution of agents among the runtime servers in order to makethe most efficient use of resources.

v Divisions that divide agents into logical groupings. Grouping of agents intoseparate divisions is not obligatory. You can create a single division and assignall agents to it. However, having agents grouped makes it possible to definedifferent frequencies of inventory scans for different groups, select groups ofagents for reporting, and limit access to license pools to a specific group orgroups of agents.

The tasks related to the monitoring structure that you can perform on the Webinterfaces are:v Registering a new runtime server with the administration server. See

“Registering a runtime server” on page 24.v Reviewing and updating the runtime servers included in the Tivoli License

Manager implementation. See “Reviewing and changing runtime servers” onpage 25.

v Adding new divisions to the topology. See “Adding divisions” on page 27.v Reviewing and updating divisions. See “Reviewing and changing divisions” on

page 28.


Divisions are used to group agents. Each customer implementation must includeat least one division, and in large implementations there can be many.

v Deploying an agent to a node. See “Deploying an agent on a node” on page 30.v Reviewing the details of deployed agents and deleting agents that are no longer

required. See “Reviewing and deleting agents” on page 32.

Registering a runtime serverWhen you install the runtime server component on a machine, you must registerthe new runtime server on the administration server before it can be used byagents.

To register a runtime server with the administration server complete the followingsteps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Servers.

2. Click Create.

3. Complete the form with the requested details.

Defining monitoring structure


Notes:

a. The server name must be exactly the same as the name you specified whenyou installed the runtime server component on the machine.

b. The password is used to authenticate communications between the runtimeserver and the administration server. If the initial password that isregistered on the administration server is not exactly the same as thepassword specified when the runtime server was installed, communicationsfail.

4. Click Finish.When you submit the server information, the runtime server is plugged in tothe administration server and is then ready for use.The server fails to plug in if the one or more of the following occurs:v The server name does not match the name of any installed serverv The server name identifies a server that does not belong to the customer you

are working withv The password does not match the runtime password that was specified when

the server was installed

If any of these problems occur, an entry is made in the event.log file, which islocated on the administration server machine, in the folder:

<INSTALL_DIR>\admin\log

You can open this log file using any text editor.

Reviewing and changing runtime serversUsing this function, you select a runtime server and can then do the following:v View the current information for the server, including a list of the agents that are

assigned to it.v Change the name, IP address, and port number of the server.v Change the server password.

To review and update a runtime server, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Servers.

2. Select a server from the list and click Next.

Register a runtime server

Chapter 4. Managing a customer infrastructure 25

The details of the selected server are displayed.

3. You can change the Name, Address, and Port number fields. However, makeany changes with care and be aware of the following:v The name must be exactly the same as the server name specified when the

runtime server was installed on the machine. Therefore, the only change youshould make is to correct an error made when the server was originallyregistered.

v The address may be a host name or an IP address depending on the networkenvironment. You should only change the IP address if it was originallyentered wrongly, or if the machine on which the server is installed haschanged its IP address.

v If you change the port number to anything other than the default (80), andyou configure WebSphere® Application Server to receive incoming requestson a different port, you must include the port number in the Web pageaddress when accessing the runtime server. For example,http:\\alpha:8080\slmruntime\login.

v The address and port fields are used by agents to contact the runtime server.If you change either of these values when agents are already deployed, youwill have to redeploy all agents to enable them to contact the runtime serverusing the new values.

4. To save your changes, click Finish.

From this page, you can select the following additional options:v Change the password that is used to authenticate communications from this

server. To do this:

Reviewing a runtime server


1. Click Password.

2. Type the password and then confirm it by retyping it.3. Click Finish. The Change Password window closes.

v View a list of the agents that use this server. To do this:1. Click Details.

2. If the list of agents extends to more than one page, click the back andforward arrows or type a page number and click Go.

Adding divisionsDivisions are organizational units within a customer implementation of TivoliLicense Manager. They are used to group agents. You must create at least onedivision for a customer before you can deploy any agents for that customer. Largecustomers can include several divisions.

Reviewing a runtime server


To create a division, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Divisions.

2. Click Create.

3. Supply the name and description of the division.4. Click Finish.

Reviewing and changing divisionsYou can review and change an existing division, as follows:v View the current information for the division, including a list of the agents that

are assigned to it.v Change the name and description of the division.v Delete a division you no longer want to use.

If you delete a division that has agents assigned to it, the agents will also beremoved.

To review and update a division, complete the following steps:

Adding divisions


1. In the portfolio, click Topology. When the Topology task group opens to showa list of tasks, click Divisions.

2. Select a division from the list and click Next.The details of the selected division are displayed.

3. You can do the following:v Make changes to the name and description and then click Finish to save the

changes.v Delete the division by clicking Delete.

If any agents are currently assigned to the division, they will be removedwhen the division is deleted.

Reviewing divisions


v View a list of the agents that are assigned to the division. To do this, clickDetails.

If the list of agents extends to more than one page, click the back andforward arrows or type a page number and click Go.

Deploying an agent on a nodeEach runtime server hosts a Web page from which you can download TivoliLicense Manager agent and install it on a node. This page is not passwordprotected, so you do not need to have the user name and password of a TivoliLicense Manager administrator to use it, though you must be logged on as a userwith administrator rights to the node. Typically, the Tivoli License Manageradministrator would contact users and tell them to deploy the agent on theirmachines.

Note: If you are installing the agent on a Windows node, ensure that the WindowsService Manager Tool is stopped.

To deploy an agent on a node, complete the following steps:1. Log on to the node as a user with administrator rights. If you are not logged

on with administrator rights, the registration process will start, but willsubsequently fail.

2. Access a runtime server.

Reviewing divisions


The address of the page is http:\\<server name>\slmruntime\register.

3. Complete the requested information, as follows:

DivisionSelect the division to which the agent is to belong from the drop-down list.

ServerSelect the runtime server that the agent will use from the drop-down list.This does not need to be the runtime server from which you are deployingthe agent.

Note: The drop-down list includes all runtime servers that have beenregistered with the administration server for the selected customer. Ifthe server you want is not in the list, this may be because you haveinstalled the component but have not registered the new server.

Computer LabelType the number on the identifying label of the machine on which theagent is to be deployed.

4. Click Finish.Standard security warnings for downloading from a Web site appear.

5. Accept the security warnings.

Note: The number and format of warning panels differs for different browsers.For Netscape Navigator, there are multiple panels, and you must clickGrant to accept each warning. For Internet Explorer, there is a singlepanel, and you must click Yes to accept it. If you do not accept thesewarnings, the agent will not be deployed.

The agent is deployed on the node and started. For information about the filescreated when the agent is deployed, see the IBM Tivoli License Manager: SystemAdministrator’s Guide.

If the deployment is not successful, a message is displayed indicating thereason. See ″Problem Determination″ in the IBM Tivoli License Manager: SystemAdministrator’s Guide for details of the possible messages and the actions youcan take to resolve problems.

Deploying an agent


Note: There is a delay between the agent starting to monitor the node andinformation from the agent being available on the servers. You must takeinto account the time delays required for scanning the node and fortransferring data to the runtime server and then to the administrationserver. You can set time delay parameters on the administration serverinterface. These parameters are held in the system.properties file for theadministration server.

Redeploying or upgrading an agentThere are some circumstances in which you need to redeploy the agent on a node:v You change the server name or port of the runtime server after the agent has

been deployed or you decide to monitor the node using a different server or toassign the agent to a different division.In this case, you should simply follow the deploy procedure again. You do notneed to uninstall the agent.

v A newer version of the agent is available on the runtime server with which theagent is registered.In this case, you can use the agent self-update facility. See the Agent chapter inthe IBM Tivoli License Manager: System Administrator’s Guide for informationabout this facility and how to enable it.

Reviewing and deleting agentsYou can use this function to review details of the agents that are deployed and todelete agents when they are no longer needed.

Note: You do not need to delete the agent before redeploying. The delete agentfunction is intended for the situation where a node is no longer beingmonitored.

The delete function deletes the record of the agent that is held in theadministration server database. It does not remove the agent files from themonitored node. To remove an agent, use the uninstall agent procedure describedin the installation chapter of the IBM Tivoli License Manager: System Administrator’sGuide. You do not need to delete the agent before redeploying. The delete functionis intended for the situation where a node is no longer being monitored. Youshould delete the agent record from the database after uninstalling the agent file.The delete function is not available if the agent is active.

You can request details of all agents, or you can limit the information displayed, asfollows:v Include all agents that are assigned to a specified divisionv Include only a specific agent

The resulting report provides you with the following information for each agentthat is included:v The name, machine label, serial number, and hardware platform of the node

where the agent is installedv The name and version of the operating system running on the machinev The IP address of the machinev The number of hard disk drives, configured processors, and online processors on

the machinev The division to which the agent is assignedv The runtime server that the agent uses

Deploying an agent


v The date and time of the last inventory scan by this agentv The agent status (whether the agent is active or inactive)

To review or delete agents, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Agents.

2. Accept the default to include agents from all divisions or select a division fromthe list.

3. Click Next.

The list of agents includes all agents or, if you selected a division, all agents forthe selected division.

4. Accept the default to include all the agents included in the list or select a singleagent from the list.

5. Click Next.A page appears showing details of a single agent.

Reviewing agents


6. To display details of another agent that is included in the report, click the backand forward arrows or type a page number and click Go.

7. To delete the agent for which details are displayed, click Delete.You are asked to confirm your decision to delete. If you do so, the entry for theagent is removed from the administration server database.

Note: The purpose of the delete function is to remove database entries foragents that have been uninstalled or where the node on which the agentis deployed has been removed from the monitored network. The deletefunction is only available if the selected agent is inactive.

Managing demographic informationYou can store information in the administration server database about the customernodes that are to be monitored and about the users who can start applications onthe nodes. Using this information, Tivoli License Manager can restrict access tolicense pools to specified users or nodes.

The tasks related to demographic information that you can perform on the Webinterface are:v Adding new nodes to the administration server database. See “Adding nodes”

on page 35.v Reviewing and updating nodes. See “Reviewing and changing nodes” on

page 36.

Reviewing agents


v Recording details of the users of monitored applications. See “Addingapplication users” on page 38.

v Changing or deleting the details of an application user. See “Changing ordeleting user details” on page 39.

Adding nodesYou can use this function to record details of nodes within the customer’s network.

Note: When an agent is deployed on a node for which there is no entry in theadministration server database, Tivoli License Manager automatically createsa new node record.

To add a node to the administration server database, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Nodes.

2. Click Create.

Managing demographics


3. Supply the details of a node that is in the network of the currently selectedcustomer.

Note: The Tag, which is also referred to as the computer label, is the uniqueidentifier of the node. It is this value that the agent deployment processattempts to match when it looks for a node entry in the administrationserver database for the target node of the deployment. If it does not finda match, it creates a new entry.

4. Click Finish.The node details are recorded in the administration server database. The nodecan now be specified when you set target distribution details for a license poolto limit access to a license pool to specified nodes. You can also selectautomatically created nodes when distributing a license pool.

Reviewing and changing nodesYou can use this function to do the following:v Change the details of nodes that are recorded on the administration server

database.v View information about nodes and the agents that are deployed on them.v Delete records for nodes that do not have an agent deployed.

To review and update an existing node, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Nodes.

2. Select one of the radio buttons to determine which nodes will be available forselection on the next form.

Adding nodes


3. Click Next.

4. Select a node from the list and click Next.

Reviewing nodes


5. You can do the following:v Make any necessary changes and click Finish.v Delete the node.

You delete the node only if there are no agents deployed on the node. If thisis the case, the Delete button is displayed.

Adding application usersYou can use this function to record details of users who are entitled to runapplications on monitored nodes. The purpose of registering users in theadministration server database is allow license pools to be restricted to specifiedusers.

To add a user to the administration server database, complete the following steps:1. In the portfolio, click Topology. When the Topology task group opens to show

a list of tasks, click Users.

2. Click Create.

Reviewing nodes


3. Supply the details of a user who has access to one or more of the monitorednodes in the network of the currently selected customer.

4. Click Finish.The user details are recorded in the administration server database. The usercan now be specified when you define user distribution settings for a licensepool if you want to limit access to the license pool to selected users. When youare defining distribution settings only those users you created with a logonname can be browsed and added to the allowed users group of a license pool.

Changing or deleting user detailsTo change or delete information for an application user whose details are recordedon the administration server database, complete the following steps:

Adding users


1. In the portfolio, click Topology. When the Topology task group opens to showa list of tasks, click Users.

2. Under the User Selection banner you can limit the number of users availablefor selection on the next form.To do this, from the drop-down list, select Last Name, Logon Name, orEmployee No, then in the text box make an entry that is to be used inmatching. For example, select Last Name and type Smith to select all userswith the last name Smith.Leave the User Selection fields unchanged to select all users.

3. Click Next.

Changing users


4. Select a user from the list and click Change.

5. If you want to delete the user, check the details, and if this is the correct user,click Delete.If you want to change the user details, make the required changes and thenclick Finish.

Changing users


Changing users


Chapter 5. Managing software entitlement and license pooldetails

This chapter provides instructions for the tasks involved in creating andmaintaining license entitlement information and license pools for products. Thesetasks are:v Maintaining the license entitlement settings for a product. See “Maintaining

entitlement settings for a product” on page 45.v Creating new license pools for a product. See “Creating a license pool” on

page 47.v Updating existing license pools. See “Updating a license pool” on page 52.v Limiting access to a license pool to specific divisions, agents, nodes, and users.

See “Setting license distribution parameters” on page 50 and “Changing licensedistribution settings” on page 54.

You perform these tasks using a browser to access the administration serverinterface. See Chapter 2, “Getting started on the Web interfaces”, on page 7 forinstructions on logging on.

License entitlement and license pool information relates to a specific customer,whose details must recorded in the administration server database. You areprompted to select the customer you want to work with when you log on to theadministration server. To change the customer during a session, click the Homeicon on the tool bar and select a different customer from the list that appears.

Changes in license information that you make on the administration server areautomatically downloaded to the customer’s runtime servers at regular intervals.

Selecting a product for entitlement or license pool maintenanceThe first two forms of the Software Entitlement wizard allow you to select theproduct for which you want to update license information.

To select a product, complete the following steps:1. In the portfolio, click Software Entitlement.


The first form of the Software Entitlement wizard appears.

2. Complete this form as follows:

SW VendorSelect All to allow selection of products from all vendors or select one ormore vendors and limit selection of products to products supplied by thosevendors.

PlatformSelect All to allow selection of products installed on all platforms or selectone or more platforms and limit selection to products installed on thoseplatform.

Product NameTo limit the selection criteria by product name matching, type part of aproduct name, preceded, followed, or surrounded by wildcard characters(%). All products that have names that match are available for selection onthe next form. Leave the field blank if you do not want to use productname matching.

IncludeIndicate whether your selection should include products that already havesettings or products that do not have settings by selecting the appropriateradio button.

Selecting a product


3. Click Next to move to the next form.


ProductSelect the product for which you want to create or update softwareentitlement settings.

The list includes only those products that match the criteria you entered onthe previous form.

IncludeIndicate which licenses are to be selected for update by selecting theappropriate radio button.

5. Click Next to show the license information about the product you selected.

You can now update the license information for the selected product. Forinstructions see:v “Maintaining entitlement settings for a product”v “Creating a license pool” on page 47v “Updating a license pool” on page 52v “Changing license distribution settings” on page 54

Maintaining entitlement settings for a productThe entitlement settings for a product determine whether a product is subject tomonitoring and if so, how the license agreements are to be defined and enforced.

To change the entitlement settings for a product, complete the following steps:1. Select the product for which you want to maintain license entitlement details.

See “Selecting a product for entitlement or license pool maintenance” onpage 43.

Selecting a product

Chapter 5. Managing software entitlement and license pool details 45

2. Complete the Product Settings section of this form by selecting radio buttonsas follows:

Software monitoringSelect Enabled if you want to track the presence and use of this productusing Tivoli License Manager. Otherwise, select Disabled.

Licenses controlSelect User-defined if you want to define license pools for this product.Select Default to use default license pool settings. The default settingsallow unrestricted use of the product. There is no limit to the number oflicenses available, no expiration date, and no restriction on the users oragents that can access the license pool. A default license pool is assignedthe capacity type Users, so that product usage is metered according to thenumber of user sessions that are started.

If you select Default, you do not need to create any license pools as a set ofdefault license rules is applied. Any license pools that exist are ignored.

Run offlineSelect Yes if the product can be used when there is no connection betweenthe agent and the runtime server. Otherwise select No.

If you select Yes, the product can be used in off-line mode, and no licensechecks will be made. License rules can be applied only when the agent isconnected to the runtime server.

Server responseSelect Required if the agent must wait for a server response beforeallowing the application to start. Select Not required if the application canstart before a response from the runtime server has been received.

Note: If you select Yes for Run offline and Required for Server response, theagent will await a server response when running online, but will allowthe product to start without a response when running offline.

3. Click Finish to record these settings.

Maintaining entitlement settings


A confirmation page appears and you can click Back to return to the previousform, where you can continue working with software entitlement settings bycreating or updating license pools for the selected product.For instructions on maintaining license pools, see:v “Creating a license pool”v “Updating a license pool” on page 52

Creating a license poolEach product that specifies user-defined license settings must have at least onelicense pool and might have more than one.

When you create a license pool, you define a set of rules that is to be appliedwhen administering the licenses assigned to the pool.

To create a license pool, complete the following steps:1. Select the product for which you want to create a license pool. See “Selecting a

product for entitlement or license pool maintenance” on page 43.2. You can define the product level license entitlement settings. See “Maintaining

entitlement settings for a product” on page 45.

Notes:

a. If you do not define product settings before creating license pools, defaultsettings are used.

b. For the Licenses control setting, you must select User Defined. If you selectDefault, any license pools you define are ignored.

3. When you return to the form where you defined product settings, scroll downuntil you reach the License Pools heading.



4. Click Create.

5. Complete the form as follows:

Capacity TypeSelect a capacity type from the drop-down list. The capacity type controlshow the number of licenses required when a product starts is determined.The following options are available:

UsersA license is assigned for each user who starts the application.

MemoryThe volume of licenses assigned is equal to the size of the memory(MB) of the requesting node.

Processors On-lineThe number of licenses assigned is equal to the number of onlineprocessors on the requesting node.

Processors configuredThe number of licenses assigned is equal to the number of configuredprocessors on the requesting node.

DisksThe number of licenses assigned is equal to the number of hard diskson the requesting node.

Hard StopSelect Yes or No. If you select Yes, the number of licenses available is an



absolute maximum. When all licenses are in use, the next license request isrefused and the application cannot start.

If you select No, the number of licenses available is not an absolutemaximum. When all licenses are in use, the next license request causes awarning event to be generated, but the application can start.

Multi-InstanceThis setting defines the circumstances where a single license can be usedfor multiple instances of the product that start on the same node. Select thedefault, Disabled, if multi-instance licenses are not allowed. Otherwise,select one of the following options from the drop-down list:

Same UserIf the application is started by a user who has already been assigned alicense for this product, no further license is required.

Same GroupIf a license is already assigned to the group of the user who starts theapplication, no further license is required.

Same NodeIf a further instance of the product is started on a node to which alicense has already been assigned, no further license is required.

QuantitySpecify the volume of licenses available in this license pool.

ThresholdSpecify the percentage of the total licenses in the pool at which to set athreshold for warnings. When the volume of licenses that are in use reachesthis percentage, a warning event is generated.

Target TypeSelect a target type from the drop-down list. The target type indicates theavailability of the license pool within the customer monitoring structure.

Select Enterprise to make the license pool available to all nodes in thecustomer structure, or select Division, Node, or Agent to limit availabilityto selected components. If you choose anything other than Enterprise, youmust specify which divisions, nodes, or agents can use this license pool.You do this when you set distribution parameters for the license pool. See,“Setting license distribution parameters” on page 50.

Start DateSpecify the date from which the license pool is available.

Expiration DateSpecify the date when the license pool will stop being available.

DescriptionType a short description of the license pools that will help you to recognizethe license pool when it appears in the software usage reports.

Creation ModeSelect Set distribution now if you want to go immediately to the formwhere distribution details are defined. See “Setting license distributionparameters” on page 50.

Select Set distribution later if you want to defer setting the distributiondetails. See “Changing license distribution settings” on page 54.



Note: If you do not set distribution parameters when you create a licensepool, the default is to allow all users to access the license pool.Therefore, if you do not want to limit access to specific users, youmight not need to create distribution details.

However, if you chose a target type other than Enterprise, you mustuse set distribution parameters for targets either immediately orlater. By default, no nodes, agents, or divisions are selected.

6. Click Finish to create the license pool.

Setting license distribution parametersThe Create License Distribution Parameters wizard starts if you chose immediatecreation of distribution parameters when you created a license pool. The first formof the wizard is the confirmation that the license pool has been created.

The details requested by the wizard differ depending on the target type youselected for the license pool. If you selected any target type other than Enterprise,the wizard requests details of the targets on which you want the license pool to beavailable.

The wizard always asks you if you want to limit the distribution to specified users.The default is to allow all users to access the license pool.

To create license distribution details, complete the following steps:1. Define the license pool, following the instructions in “Creating a license pool”

on page 47 and selecting the Set distribution now creation mode.When you click Finish to create the license pool, the following form appears.



In this example, the target type selected on the license creation form wasDivision. If you had selected Enterprise for target type, you would not need toselect any targets and instead would be immediately prompted for userlimitations.

2. To use target name matching to limit target selection, type part of a targetname, preceded, followed, or surrounded by wildcard characters (%). All targetnames that match are available for selection on the next form. Leave the fieldblank if you do not want to use target name matching.

3. Click Next.

4. Select the targets you want to include in the distribution of the license pool.5. Click Next.

6. Choose whether the license pool is to be restricted to selected users or availableto all users:v To allow all users, click Allow all.

The creation of distribution details is now complete.v To restrict the license pool to selected users click Next.

If you want to use name matching to restrict the entries in the list of usersfrom which you will choose on the next page, type a part of the User logonname, preceded, followed, or surrounded by wildcard characters (%). Alluser names that match are available for selection.

Setting distribution parameters


7. Select the users who are to have access to the license pool.8. Click Finish.

A confirmation page appears summarizing the distribution parameters youspecified.

Updating a license poolYou can use the Change action to make changes to a license pool that you havealready defined.

To update a license pool, complete the following steps:1. Select the product for which you want to make changes to a license pool. See

“Selecting a product for entitlement or license pool maintenance” on page 43.2. Scroll down the form that starts with license entitlement product settings until

you reach the License Pools banner and the list of licenses that exist for theselected product.

Setting distribution parameters


3. Select the license pool you want to update and click Change.

4. Complete the form as follows:

Hard StopSelect Yes or No. If you select Yes, the number of licenses available is anabsolute maximum. When all licenses are in use, the next license request isrefused and the application cannot start.

If you select No, the number of licenses available is not an absolutemaximum. Once all licenses are in use, the next license request causes awarning event to be generated, but the application is allowed to start.

Multi-InstanceThis setting defines the circumstances where a single license can be usedfor multiple instances of the product that start on the same node. Select thedefault, Disabled, if multi-instance licenses are not allowed. Otherwise,select one of the following options from the drop-down list:

Same UserIf the application is started by a user who has already been assigned alicense for this product, no further license is required.

Same GroupIf a license is already assigned to the group of the user who starts theapplication, no further license is required.

Updating a license pool


Same NodeIf a further instance of the product is started on a node to which alicense has already been assigned, no further license is required.

QuantityYou can change the volume of licenses available in this license pool.

ThresholdYou can change the percentage of the total licenses in the pool at which toset a threshold for warnings. When the volume of licenses that are in usereaches this percentage, a warning event is generated.

Target TypeYou cannot change the target type on this form. To change the target type,you must select the Change option for target distribution details.

Start DateYou can change the date from which the license pool is available.

Expiration DateYou can change the date when the license pool will stop being available.

5. If you want to change the distribution details for the license pool, scroll downto the Distribution banner and select from the options to change or deletetarget and user distribution information. See “Changing license distributionsettings”.

Note: When you have made changes to distribution details, you return to thisform. You must click Finish on this form to save the changes you madeto the distribution details.

6. Click Finish to save the changes you have made.

Changing license distribution settingsAll license pools include distribution settings. These can be the default values toallow use of the pool by all users throughout the customer enterprise or they caninclude limitations to specific users and targets within the enterprise.

When you update a license pool, the current distribution details are displayed onthe Manage License Settings page, under the Distribution heading.

Updating a license pool


If the current settings include target or user limitations, the allowed targets andusers are listed. You can change the settings by deleting items from either list. Todelete an item from the target or user list, select it and click the related Deletebutton.

Note: If you delete all users from the list, the user distribution settings default toallow the pool to be accessed by all users. If you delete all current targetsyou must the target distribution settings to select new targets.

To add users or targets or to change the target type, use the Change options forusers and targets.

Changing target distribution settingsTo change the target distribution settings, complete the following steps:1. In the Distribution section of the License Settings page, click the Change button

for the target settings.

2. To change to a different type of target, select a Target Type from thedrop-down list. For example, you can change from Division to Node.

3. Click Next.If you chose Enterprise as the target type, the target update is complete andyou return to the Manage License Settings page. Otherwise, you are promptedto select targets of the type you specified.

4. To use target name matching to limit target selection, type part of a targetname, preceded, followed, or surrounded by wildcard characters (%). All targetnames that match are available for selection on the next form. Leave the fieldblank if you do not want to use target name matching.

Changing distribution settings


5. Click Next.

6. Select the targets you want to include in the distribution of the license pool.If you have not changed to a different target type, the list includes only thosetargets that are not selected in the current settings. You can add more targetshere, but you can only delete targets using the Delete button on the LicenseSettings page.

7. Click Next.You now return to the License Settings page.

8. Click Finish.

Changing user distribution settingsWhen you are defining the distribution settings for a license pool, only the usersthat you created with a logon name can be browsed and added to the allowedusers group of the license pool. When there are no registered users with a logonname you will not be able to add users to the allowed user group of the selectedlicense, and all the users will be allowed to use the license.

To change the user distribution settings, complete the following steps:1. In the Distribution section of the License Settings page, click the Change button

for the Allowed Users settings.

2. Choose whether the license pool is to be restricted to selected users or availableto all users:v To allow all users, click Allow all.

The creation of distribution details is now complete.v To restrict the license pool to selected users click Next.

Changing target distribution


If you want to use name matching to restrict the entries in the list of usersfrom which you will choose on the next page, type part of the User logonname, preceded, followed, or surrounded by wildcard characters (%). Alluser names that match are available for selection.

If you selected the option to allow all users, the update of user distributionsettings is now complete. Otherwise, the following form appears.

3. Select the users you want to include in the distribution of the license pool.The list includes only those users that are not selected in the current settings.You can add more users here, but can only delete users using the Delete iconon the License Settings page.

4. Click Next.You now return to the License Settings page.

5. Click Finish.

Changing user distribution


Changing user distribution


Chapter 6. Reporting software usage information

This chapter provides instructions for producing software usage reports.

Tivoli License Manager provides realtime and historical information on softwareusage. You request the realtime information from the appropriate runtime serverand the historical information from the administration server. The followingreports are available:v A snapshot report of software usage at a specified time. See “Producing a

historical snapshot software usage report”.v A report in graphical format showing trends in usage of a product over a period

of time. See “Producing a software usage trend analysis report” on page 67.v A report that summarizes the highest or average usage of products during a

specified period. See “Producing a software usage level analysis report” onpage 71.

v A realtime software usage report which you can request on a runtime server. See“Producing a realtime software usage report” on page 75.

You perform these tasks using a browser to access the Web interfaces. SeeChapter 2, “Getting started on the Web interfaces”, on page 7 for information aboutthe tasks available on each server and for instructions on logging on to theadministration and runtime servers.

You are prompted to select the customer you want to work with when you log onto the administration server. To change the customer during a session, click theHome icon on the tool bar and select a different customer from the list thatappears.

Producing a historical snapshot software usage reportThe software usage report, which is available from the Web interface onadministration server, provides information about the software usage on monitorednodes as at a date and time that you specify.

The report includes detailed information about the products and their level ofusage at the specified time, the agents on which they were installed, the licensepools that were available, and the sessions that were active.

Requesting the reportThe software usage snapshot report wizard consists of two forms where you candefine parameters for the report. You can limit the report as follows:v Only specified productsv Only products supplied by a selected vendorv Only products installed on a specified operating systemv Only products installed on nodes that are monitored by specified agents or

agents in specified divisions

To produce a software usage snapshot report complete the following steps:1. In the portfolio, click Software Usage. When the Software Usage task group

opens to show a list of tasks, click Snapshot. The first form of the software


usage snapshot wizard appears. This form allows you to limit the products andagents that can be selected for inclusion in the report on the second form.




Product NameTo limit the products available for selection using product name matching,type a part of a product name preceded, followed, or enclosed by wildcardcharacters (%). All products that have names that match are included in theselection list on the next form. Leave the field blank if you do not want touse product name matching.

DivisionSelect All to allow selection of agents from all divisions or select one ormore divisions to limit selection to agents assigned to those divisions.

Agent NameTo limit the agents available for selection using agent name matching, typea part of an agent name preceded, followed, or enclosed by wildcardcharacters (%). Agents with names that match are available for selection onthe next form. Leave the field blank if you do not want to use agent namematching.

Requesting the report




Product nameAccept the default, All, to include all products that match the criteria youspecified in the first form or select a product to limit the report to instancesof a single product.

AgentAccept the default, All, to include products installed on all agents thatmatch the criteria you specified in the first form or select agent to limit thereport to products installed on that agent.

DateDefine the effective date of the report. Software usage information at thedate and time entered will be included in the report.

TimeDefine the effective time of the report.

Time ZoneSelect a time zone from the drop-down list. Ensure that the time zone youselect does not put the specified date and time in the future.

HWM Time RangeFrom the drop-down list, select the time period over which the high water


Chapter 6. Reporting software usage information 61

mark is to be reported. The time range is considered as a period up to thedate and time specified. For example, if you specify a time range of 1 day,the high water mark values for products in the report will be the maximumconcurrent usage in the 24 hours before the date and time you specified.

5. Click Next to produce the report

Navigating the reportThe report has the following sections:v A list of products installed on the selected nodes, showing the level of usage of

each product.The list of products includes all products that fit the selection criteria, whichwere in use at the specified time or which have procured licenses. Products thatuse the default license settings are only included if they were in use at thespecified time.

v Product details for each product.v Details of the monitored nodes on which each product is installed.v Details of license pools available for each product.v A list of current sessions for each product that is in use.

Figure 3 shows the product list section of the software usage report.

This is the first section that appears when the report is produced. It shows a list ofthe products that fit the selection criteria you entered.

You can choose to export the report in an XML format. To do this, select Page orDocument from the Export drop-down list and click OK.

Figure 3. Product list in the historical software usage report



If the list extends to more than one page, click the back and forward arrows ortype a page number and click Go.

The list of product shows software usage information for products that areinstalled on the selected agents.

Note: Products that have procured licenses are included in the report even if theywere not in use at the specified time. Products that use the default licensesettings are only included if they were in use.

At the top of the list, you can change the Capacity Type for which information isdisplayed, by selecting from a drop-down list. If entries in the list do not have fulldetails, this is because they have a different capacity type to the one currentlyselected. In addition to the product name and version, each entry includes thefollowing information about the status of products at the specified reporting time:

Total InstalledThe number of instances of the product, which were installed on agents at thespecified date and time, that are included in the report.

ProcuredThe volume of licenses that were procured at the specified time. How this isexpressed depends on the capacity type. For example, if the capacity type isUser, this will be the number of licenses available. If the product uses defaultlicense settings, this is set to none.

In UseThe volume of licenses in use on the agents included in the report at the dateand time specified.

Total in UseThe volume of licenses in use on all agents at the date and time specified.

Total HWMThe maximum volume of licenses that were concurrently in use on all agentsduring the specified HWM period.

Each row of the product list includes links that allow you to jump to anothersection of the report, as follows:v Click a Product to jump to details of that product. See Figure 4 on page 64.v Click a Total Installed value to jump to information about the monitored nodes

where the product is installed.v Click a Procured value to jump to details of the license pool for the product. See

Figure 12 on page 80.v Click an In Use value to jump to details of the sessions that were open for the

product. See Figure 13 on page 81.

Figure 4 on page 64 shows the details of a selected product. The details comprisethe name of the operating system under which the product runs, the name of thesoftware vendor, whether or not the product must wait for a response from theruntime server before opening, and whether or not the product can run if there isno connection to the server.

Navigating the report


Click the arrow icon in the right of the table to return to the top of the report.

Figure 5 shows the list of monitored nodes on which a selected product is installed.

For nodes where the product was installed at the specified reporting time, thereport shows the following:v Machine information comprising the host name, IP address, node name,

operating system name, and operating system versionv Tivoli License Manager information comprising the division and the runtime

server to which the agent is assigned

You can navigate to other parts of the report as follows:v Click the arrow icon to return to the top of the report.v Click List of products to jump to the current page of the list of products. See

Figure 3 on page 62.v Click the product name at the top of the table to jump to the product details

section of the report. See Figure 4.

Figure 6 on page 65 shows the list of license pools for a selected product.

Figure 4. Product details in the historical software usage report

Figure 5. List of agents in the historical software usage report



For each license pool that the selected product can use, the following informationis displayed:

LicenseIdentifies the license whose terms are summarized here.

Products that are not subject to a license can be monitored by assigning them adefault set of conditions.

QuantityThe size of the license pool. For license agreements based on the User capacitytype, this is the number of licenses available.

ThresholdThe level of license usage, expressed as a percentage of total quantity, at whichan administrator is to be alerted about possible shortage of licenses.

Hard StopPossible values are Yes and No. Yes indicates that when all the licenses in thepool have been allocated, the next request to open a session is refused. Noindicates that the number of available licenses can be exceeded, though awarning will be issued.

Multi-instancePossible values are Disabled, Same User, Same Group, or Same Node. Ifmulti-instance is enabled, a single license can be used for multiple sessions ofthe product for the same user, for the same user group, or for the same node.Otherwise, each session must be allocated a license.

HWMThe maximum volume of licenses from this license pool concurrently in use onall agents that was reached during the specified HWM period.

In UseThe volume of licenses from this license pool in use on all agents at the dateand time specified.

Capacity TypeThis indicates how to calculate the volume of licenses required when a productis started. The most usual capacity type, Users, allocates one license each timea product starts.

Start DateThe date from which the license pool can be used.

Figure 6. License pools in the historical software usage report



Expiration DateIf set, the license pool cannot be used after this date.


Figure 3 on page 62.v Click on the product name at the top of the table to jump to the product details

section of the report. See Figure 4 on page 64.

Figure 7 shows the details of the sessions open for a selected product.

For each session that was open at the specified reporting time, the followinginformation is displayed:

Host nameIdentifies the node on which the session is open.

User NameThe ID of the user who opened the session.

Group NameThe name of the user group to which the user is assigned.

In UseThe number of licenses in use.

Grant DateThe date and time at which the license was allocated.


Figure 3 on page 62.v Click on the product name at the top of the table to jump to the product details

section of the report. See Figure 4 on page 64.v Click Licenses to jump to the license pool section of the report. See Figure 6 on

page 65.

Figure 7. Sessions in the historical software usage report



Producing a software usage trend analysis reportThe Trend Analysis report provides a graphical representation of trends in theusage of a selected product during a specified period.

You can only select one product for reporting. You can report its usage on allagents, on agents within selected divisions, or on selected agents.

The report can include several charts. If the selected product has license pools withdifferent capacity types, usage under the different capacity types must bepresented on separate charts. Optionally, you can break down the report further, sothat usage for each available license pool is reported on a separate chart.

Requesting the reportThe trend analysis report wizard consists of two forms where you can defineparameters for the report.

To produce a trend analysis report, complete the following steps:1. In the portfolio on the left side of the administration server Web page, click

Software Usage then when the Software Usage task group opens to show a listof tasks, click Trend Analysis. The first form of the trend analysis wizardappears. This form allows you to limit the products and agents that appear inthe selection lists on the next form.


SW VendorSelect All to include products from all vendors in the list on the next formor select one or more vendors and limit selection of products to productssupplied by those vendors.


Software trend analysis report




Agent NameTo limit the agents available for selection using agent name matching, typea part of a agent name preceded, followed, or enclosed by wildcardcharacters (%). Agents with names that match are available for selection onthe next form. Leave the field blank if you do not want to use agent namematching.



ProductSelect a product from the list.


Requesting a software trend report


Query bySelect one of the radio buttons.

This selection determines the level at which software usage information isto be broken down into separate charts, as follows:

CapacityA chart is produced for each different capacity type that is used for theproduct. The usage figures for all license pools of the same capacitytype are reported together. For example, if the product has some licensepools with capacity type Users and some with capacity type Memory,the report includes two charts, each of which might include usage fromseveral license pools.

LicenseA chart is produced for each license pool defined for the product.

Note: Usage levels from license pools that have been deleted are notincluded.

Start DateDefine the date and time at which the reporting period is to start.

End DateDefine the date and time for the end of the reporting period. Informationabout trends of software usage up to and including the date and timeentered will be included in the report.

Time ZoneSelect a time zone from the drop-down list. Ensure that the time zone youselect does not any part of the reporting period in the future.

5. Click Next to produce the report.

Using the reportFigure 8 on page 70 shows a chart from the Trend Analysis report in step format.The chart plots licenses used against time, over the period you specified. In lineformat, the periods of time are joined, showing the rise and fall in usage.

Note: Usage levels from license pools that have been deleted are not included.



You can navigate the report, change the content, or change the presentation:v If the report includes more than one chart, click the back and forward arrows or

type a page number and click Go.v Export the current chart in an XML format. Click OK next to the Export list.v Change the format of the chart, by selecting from the Chart Type list.

Available formats are Step, Line, and Event. Step format is shown in Figure 8.Line format shows the different levels connected by a line showing the trend ofthe change in usage. Event format shows single events, not connected by a trendline.

v Change the report period by changing the Start Date and End Date fields andclicking OK.

v Change the breakdown of the information by changing the from Capacity toLicense or from License to Capacity and clicking Submit.In Figure 8, Capacity is selected and the information shown includes usage of alllicense pools that have the capacity type Users. If you change to License, thereport shows a separate chart for each license pool.

v Show a description of the chart by clicking the D link.

Figure 8. Trend Analysis report in step format



Producing a software usage level analysis reportThe Level Analysis report provides an overview of the level of usage of softwareproducts during a specified period. The reporting options allow you to considerusage as either the high water mark or as the average usage of products.

The level analysis report wizard consists of three forms where you can defineparameters for the report. You can limit the report as follows:v Only specified productsv Only products with entitlement settingsv Only products without entitlement settingsv Only products supplied by a selected vendorv Only products installed on a specified operating systemv Only products installed on nodes that are monitored by specified agentsv Only products that have more than or less than a specified level of usage

You can sort the report in product order or in descending order of usage level.

To produce a level analysis report, complete the following steps:1. In the portfolio on the left side of the administration server Web page, click

Software Usage then when the Software Usage task group opens to show a listof tasks, click Level Analysis. The first form of the level analysis wizardappears. This form allows you to limit the products and agents that can beselected for inclusion in the report on the second form.

Software usage level report






IncludeSelect one of the radio buttons to determine whether the report includesonly products with entitlement settings, all products, or only productswithout entitlement settings.


Agent NameTo limit the agents available for selection using agent name matching, typea part of a agent name preceded, followed, or enclosed by wildcardcharacters (%). Agents with names that match are available for selection onthe next form. Leave the field blank if you do not want to use agent namematching.





ProductAccept the default, All, to include all products that match the criteria youspecified in the first form or select a product to limit the report to instancesof a single product.


End DateDefine the date for the end of the reporting period. Information aboutlevels of software usage up to and including the date and time entered willbe included in the report.

End TimeDefine the time for the end of the reporting period.




Time RangeFrom the drop-down list, select the time period over which the softwareusage levels are to be reported. The time range is considered as a period upto the date and time specified.


6. Define a usage threshold for inclusion in the report, as follows:a. From the first drop-down list, select the type of usage level: high water

mark or average usage.b. Set the threshold for reporting by selecting greater than or lower than from

the second drop-down list and typing a value in the text box. For example,you can set a threshold to include all products with a usage level greaterthan 10.

Note: The usage levels reported are only those for the selected agents.Products are only selected for the report if they had usage levels onthe selected agents that meet the threshold criteria.

c. Select the Capacity type of licenses to be included in the usage figures. Thecapacity type determines the units that are used to determine the thresholdusage level.

Note: Products with no license pools are considered as using the defaultcapacity type Users.

7. Under the Sort by banner, select one of the radio buttons to determine whetherthe report is produced in product order or in descending order of usage level.


Figure 9 on page 75 shows a level analysis report showing the high water marklevels for the selected products, sorted by product name.



You can choose to export the report in an XML format. To do this, select Page orDocument from the Export drop-down list and click OK. See “Exporting reports”on page 82 for more details.

If the report extends to more than one page, you can use the paging controls at thebottom of the current page to display further pages of the report as follows.v Click a number to display a specific page of the report and click Go.v Click the left and right arrows to move to the previous or next page of the

report.

Producing a realtime software usage reportThe software usage report, which is available from the Web interface on runtimeservers, provides current information about the software usage on monitorednodes.

The report includes detailed information about the products and their current levelof usage, the license pools that are available, and the sessions that are active.

Requesting the reportThe software usage report wizard consists of two forms where you can defineparameters for the report. You can limit the report as follows:v Only specified productsv Only products supplied by a selected vendorv Only products installed on a specified operating systemv Only products installed on nodes that are monitored by specified agents

Figure 9. The Level Analysis report



To produce a realtime software usage report complete the following steps:1. In the portfolio on the left side of the runtime server Web page, click Software

Usage. The first form of the software usage wizard appears.







Realtime software usage report




ProductAccept the default, All, to include all products that match the criteria youspecified in the first form or select on or more products to be included inthe report.

AgentAccept the default, All, to include products installed on all agents thatmatch the criteria you specified in the first form or select one or moreagents to limit the report to products installed on those agents.

Note: If the list of agents is empty, this means that the runtime server has noagents that are currently running any monitored software products.


Navigating the reportThe report has the following sections:v A list of products installed on the selected nodes, showing the level of usage of

each product.The list of products includes all products that fit the selection criteria, which arein use when the report is requested or which have procured licenses. Productsthat use the default license settings are only included if they are in use when thereport is requested.

v Product details for each product.v Details of license pools available for each product.v A list of current sessions for each product that is in use.

Figure 10 on page 78 shows the product list section of the software usage report.



This is the first section that appears when the report is produced. It shows a list ofthe products that fit the selection criteria you entered.

If the list extends to more than one page, click the back and forward arrows ortype a page number and click Go.

The list of product shows software usage information for products that areinstalled on the selected agents. At the top of the list, you can change the CapacityType for which information is displayed, by selecting from a drop-down list. Ifentries in the list do not have full details, this is because they have a differentcapacity type to the one currently selected. In addition to the product name andversion, each entry includes the following information about the current status ofproducts:

ProcuredThe volume of licenses procured. How this is expressed depends on thecapacity type. For example, if the capacity type is Users, this will be thenumber of licenses available.

In UseThe volume of licenses in use on the agents included in the report.

Total in UseThe volume of licenses in use on all agents for this runtime server.

Total HWMThe maximum volume of licenses that have been concurrently in use since thehigh water mark was last reset.

Figure 10. Product list in the realtime software usage report



You can reset this value using the buttons below the list. To reset the value fora single product, select the check box in the Select column and click Reset theselected HWMs. To reset the values for all products in the list, click Reset Allthe HWMs.

HWM Reset Date (GMT)The date and time at which the high water mark was last reset.

Each row of the product list includes links that allow you to jump to anothersection of the report, as follows:v Click a Product to jump to details of that product. See Figure 11.v Click a Procured value to jump to details of license pools for the product. See

Figure 12 on page 80.v Click an In Use value to jump to details of the sessions that are currently open

for the product. See Figure 13 on page 81.

Figure 11 shows the details of a selected product. The details comprise the name ofthe operating system under which the product runs, the name of the softwarevendor, whether or not the product must wait for a response from the runtimeserver before opening, and whether or not the product can run if there is noconnection to the server.

You can navigate to other parts of the report as follows:v Click the arrow icon to return to the top of the report.v Click List of Licenses to jump to details of the license pools in use for this

product. See Figure 12 on page 80.

Figure 12 on page 80 shows the details of the license pools for a selected product.

Figure 11. Product details in the realtime software usage report



For each license pool that the selected product can use, the following informationis displayed:

LicenseIdentifies the license whose terms are summarized here.

Products that are not subject to a license can be monitored by assigning them adefault set of conditions.

QuantityThe size of the license pool. For license agreements based on the User capacitytype, this is the number of licenses available.

ThresholdThe level of license usage at which an administrator is to be alerted aboutpossible shortage of licenses.

Hard StopPossible values are Yes and No. Yes indicates that when all the licenses in thepool have been allocated, the next request to open a session is refused. Noindicates that the number of available licenses can be exceeded, though awarning will be issued.

Multi-instancePossible values are Disabled, Same User, Same Group, or Same Node. Ifmulti-instance is enabled, a single license can be used for multiple sessions ofthe product for the same user, for the same user group, or for the same node.Otherwise, each session must be allocated a license.

Total HWMThe maximum volume of licenses that have been concurrently in use since thehigh water mark was last reset.

In UseThe volume of licenses, from this pool, in use on all agents for this runtimeserver.

Capacity TypeThis indicates how to calculate the volume of licenses required when a productis started. The most common capacity type, Users, allocates one license eachtime a product starts.

Start DateThe date from which the license pool can be used.

Figure 12. License pools in the realtime software usage report



Expiration DateIf set, the license pool cannot be used after this date.


Figure 10 on page 78.v Click Product Name to jump to the product details section of the report. See

Figure 11 on page 79.

Figure 13 shows the details of the sessions open for a selected product, reached byclicking an In Use value on the current page of the list of products.

All open sessions are listed. If the session are using license pools with differentcapacity types, the In Use figure is only shown for sessions using the capacity typethat is currently selected. You can select another capacity type from the drop-downlist.

For each session, the following information is displayed:

Host nameIdentifies the node on which the session is open.

TagThe machine tag of the node on which the session is open.

Figure 13. Open sessions in the realtime software usage report



User NameThe ID of the user who opened the session.

Group NameThe name of the user group to which the user is assigned.

In UseThe number of licenses in use.

Grant DateThe date and time at which the license was allocated.


Figure 10 on page 78.v Click Product Name to jump to the product details section of the report. See

Figure 11 on page 79.v Click Licenses to jump to the license pool section of the report. See Figure 12 on

page 80.

Exporting reportsThe option to export information to an XML format is available for the followingreports on the administration server:v Software Usage Historical Snapshotv Software Usage Trend Analysisv Software Usage Level Analysis (single chart only)

If you want to store a report, you can save it in XML format using the OK buttonunderneath the main report table or chart. There are two options for exporting:

DocumentSelect this option to export the entire report. The document option is notavailable for reports that only have one page.

PageSelect this option to export the page that is currently displayed.

When you click OK, the XML Export page appears.

Right-click the link to the file to open the context menu and save the file.



Chapter 7. Managing and reporting inventory information

One of the functions of the agent is to make regular inventories of the productsinstalled on the node it is monitoring. The information collected in the inventoryscan is passed to the runtime server, where the runtime server identifies thoseproducts which have entries in the master catalog. Only products with entries inthe master catalog are passed to the administration server and stored in theadministration server database.

This chapter provides instructions related to the inventory of monitored nodes asfollows:v Specifying the time interval between inventory scans of monitored nodes.

“Scheduling inventory scans”.v A software inventory report, which details the products that have been

discovered on monitored nodes by agent inventory scans. You can produce thereport in product or agent order. See “Producing a software inventory report” onpage 85.

You perform these tasks using a browser to access the administration serverinterface. See Chapter 2, “Getting started on the Web interfaces”, on page 7 forinstructions on logging on.

You are prompted to select the customer you want to work with when you log onto the administration server. To change the customer during a session, click theHome icon on the toolbar and select a different customer from the list thatappears.

Scheduling inventory scansYou use this function to schedule the frequency with which inventory data iscollected from monitored nodes within a specified division.

Consider the following when you decide on the timing of an inventory scan:v It is advisable to create the schedule for scanning well in advance of the time

specified for scanning. This will reduce the possibility that the schedule detailswill not reach all agents within the division.

v It is advisable to schedule the scans of different divisions at different times, asthis will spread the network instead of concentrating it around one scan time.

v Before the information is available for reporting, it must be transferred to theruntime server and then to the administration server. Time delays operate foruploads between the components. These are defined in the system.propertiesfiles for each server. See the IBM Tivoli License Manager: System Administrator’sGuide for details of the configuration file.


To schedule inventory updates, complete the following steps:1. In the portfolio, click Software Inventory. When the Software Inventory task

group opens to show a list of tasks, click Scheduling.

2. Select a division from the drop-down list and click Next.

3. Complete the requested information, as follows:

DateSpecify the date on which the first inventory scan is to be made using theseparameters.

TimeSpecify the time at which the first inventory scan is to be made using theseparameters.

Note: The time refers to the time in the time zone where the agent islocated.

Scan frequencyDefine the regularity of the inventory schedule.

If these parameters are to be used for a single inventory scan, select Once.If the parameters are to be used for a regular schedule of inventory scans,select Repeat Each, type a number in the text box, and then select a time

Scheduling scans


period from the drop-down list. For example, to perform an inventory scanevery two weeks, type 2 in the text box and select Weeks from the list.

4. Click Finish.

Producing a software inventory reportThe software inventory report provides you with information about products thatare installed on nodes monitored by Tivoli License Manager. The details includedin the report are compiled by making regular scans of the monitored nodes. Youcan define the frequency of inventory scans, see “Scheduling inventory scans” onpage 83.

Requesting the inventory reportThe software inventory report wizard consists of two forms where you can defineparameters for the report. You can limit the report as follows:v Only specified productsv Only products supplied by selected vendorsv Only products installed on specified operating systemsv Only products installed on nodes that are monitored by specified agents

You can produce the report in either product or agent order and must specify thedate and time for which inventory information is to be reported.

To produce a software inventory report complete the following steps:1. In the portfolio, click Software Inventory. When the Software Inventory task

group opens to show a list of tasks, click Report. The first form of the softwareinventory wizard appears.

Scheduling scans

Chapter 7. Managing and reporting inventory information 85







Producing an inventory report




ProductAccept the default, All, to include all products that match the criteria youspecified in the first form or select one or more products.


Order byClick the Product radio button to produce the report in product order. Clickthe Agent radio button to produce the report in agent order.

DateDefine the effective date of the report. Inventory information as at the dateand time entered will be included in the report.

TimeDefine the effective time of the report.





The software inventory reportFigure 14 shows a software inventory report, produced in product order. Thedetails of each cataloged product are followed by a list of the agents on which theproduct was installed at the moment of the most recent inventory scan prior to theselected date and time.

You can choose to export the report in an XML format. To do this, select Page orDocument from the Export drop-down list and click Export. See “Exportingreports” on page 89 for more details.

If the report extends to more than one page, you can use the paging controls at thebottom of the current page to display further pages of the report as follows.

Figure 14. Software inventory report



v Click a number to display a specific page of the report.v Click Previous to move to the page before the page that is currently displayed.v Click Next to move to the page after the page that is currently displayed.

Note: If the report does not include products that you know are installed onmonitored nodes, take account of the following:v There is a time delay between the inventory scan and the availability of

the new inventory information on the administration server. For details ofparameters that affect the time delay, see the description of thesystem.properties configuration file in the IBM Tivoli License Manager:System Administrator’s Guide.

v The inventory report only includes products that have entries in themaster catalog.

Exporting reportsIf you want to store a report, you can save it in XML format using the Exportbutton at the top of the report. There are two options for exporting:

DocumentSelect this option to export the entire report.

PageSelect this option to export the page that is currently displayed.

When you click Export, the XML Export page appears.

Right-click the link to the file to open the context menu and save the file.

The inventory report



Chapter 8. Managing product information

This chapter provides you with information about the use and management ofsoftware product information in Tivoli License Manager, as follows:v How the catalog of product information is used to enable monitoring of software

products. See “Catalogs and unknown file information”v How to add new products and change information in the master catalog. See

“Using the catalog manager to update the master catalog” on page 92

Catalogs and unknown file informationThe Tivoli License Manager master catalog contains details of all products that canbe monitored by Tivoli License Manager.

Master catalogThe master catalog is a central repository of product information. It is installedon the administration server. A copy is downloaded to each runtime server andis periodically refreshed to include new information.

The master catalog contains information about all the software componentsand related files for the products that are to be monitored. An initial mastercatalog is provided when Tivoli License Manager is installed.

The Tivoli License Manager catalog manager component allows you to addnew information to the master catalog. There are two sources of newinformation: the unknown file table, which contains entries for all applicationsthat were detected by agents, but that were not already in the master catalog,and new versions of the IBM catalog, which you can merge with the mastercatalog. Each version of the IBM catalog is based on a Tivoli signatures file.

Runtime catalogA runtime catalog is created automatically on each runtime server. It is asubset of the master catalog which contains information about only thoseproducts that are installed on the nodes that are managed by the runtimeserver.

A copy of the runtime catalog is downloaded to each node where the agent isinstalled. These copies are periodically refreshed to include new informationadded to the runtime catalog on the runtime server.

New entries are added to the runtime catalog when the runtime server receiveslicense entitlement information from the administration server and when theunknown file table identifies an application, which has been discovered on amonitored node, that is in the master catalog but not in the runtime catalog.

Unknown file table and unknown file listsThe unknown file table and unknown file lists provide a way of identifyingsoftware that is not included in the runtime catalog and which may not be inthe master catalog.

The agent, running on a node, identifies any applications that are not includedin the runtime catalog and adds them to the unknown file list. The listscompiled by all the agents are communicated to the runtime server where theyare merged to form the unknown file table. The information in the table isused to identify entries in the master catalog which should be added to theruntime catalog. Unknown file tables from the runtime servers are periodically


uploaded to the administration server, where they are merged to form a singleunknown file table. You can add the unknown files to the master catalog usingthe catalog manager.

Using the catalog manager to update the master catalogThe catalog manager is a standalone tool that you can use to expand and makechanges to the master catalog. To use it, you must extract the catalog and unknownfile table from the administration server database. You can then perform a numberof tasks, the most frequent of which is adding the unknown files, discovered bythe agents, to the master catalog. When you have finished making changes, youmust reimport the catalog to the administration server database.

To use the catalog manager, perform the following steps:1. Open the Tivoli License Manager command line interface (CLI).

On WindowsClick Start > IBM Software License Manager > Admin CLI.

On AIX

a. Open a shell window and change to the directory:<INSTALL_DIR>/admin/cli

b. Enter the command:. ./tlmcli

2. At the command line, type:expcat

A script runs to extract the master catalog and unknown file table to the filecatalog.dat in the <INSTALL_DIR>/admin/cli folder.

3. Launch the catalog manager.

On WindowsClick Start>Programs>Tivoli License Manager>Catalog Manager.

On AIX

a. Open a shell window and change to the directory:<INSTALL_DIR>/catmgr

b. Enter the command:. ./catman

Catalogs and unknown files


4. Navigate to the folder where the expcat script stored the catalog files, selectcatalog.dat, and click Open.Catalog manager loads the file and displays the following screen.

The screen shows the contents of the catalog in terms of total numbers ofproducts, modules and vendors.

5. Click OK, and the catalog manager function selection screen is displayed.

Updating the master catalog

Chapter 8. Managing product information 93

6. Choose the program functions to make the changes you require and follow theinstructions in the following sections:v “Adding unknown files to the master catalog”.v “Modifying entries in the master catalog” on page 98.v “Importing the IBM catalog” on page 97.

7. When you have completed your changes, click Save to File, and save thecatalog so that it overwrites the extracted catalog.dat file in the<INSTALL_DIR>\admin\cli folder.

Note: You can change the file under a different name. However, beforereimporting the catalog to the Tivoli License Manager administrationserver database you must rename it, as the impcat command requires afile named catalog.dat.

8. Go to the Tivoli License Manager Administration command line interface andenter, impcat to import the updated catalog to the administration serverdatabase.

Adding unknown files to the master catalogUsing this function, you can view the entries in the unknown files table that youextracted and determine whether to associate each with an existing catalog entry orto create a new entry.

To process the entries in the unknown files table, complete the following steps:1. In the initial window of the catalog manager, click Unknown Files Manager.2. Search for the entry in the unknown files list that you want to process, as

follows:a. Select a radio button to search by file name or description.b. From the drop-down list, select the platform for which you want to find

files.c. You can limit the search to entries where the name or description includes

a specific string by typing the string in the text box.d. Click Search.

The results of the search are listed in the upper part of the window.

Updating the master catalog


3. Select an entry from the list of results. The details of the file you selected aredisplayed in the lower part of the window.

4. Click Associate.

Note: You must attempt to associate the file with an existing entry in themaster catalog before you create a new entry. When the entry is firstselected, the New button is not available.

The catalog manager compiles a list of products, currently in the mastercatalog, that are possible matches for the unknown file you are trying toassociate. It compiles the list by identifying all products for which thedescription contains any of the same words as the description of the unknown

Adding unknown files


file.

5. Check the list to see if the product that the unknown file belongs to is there. Ifit is, select it and click OK.If the product is not in the list, you can change the search criteria and searchagain. To do this, edit the Search field and click Search.If you do not find the product that the unknown file belongs to, click Cancel.When you click OK or Cancel, you return to the previous window.

6. If you selected a product, click OK to associate the file with the product entryin the master catalog. The entry is removed from the unknown file table. Youcan now select another entry.



If you did not find the product that the unknown file belongs to, click New todefine a new entry for the master catalog.

7. Supply the information that is missing and edit any fields that need to bechanged.Name and Version are required fields.

8. Click Create to return to the previous window.9. Click OK to add the new entry to the master catalog and remove the entry

from the unknown file table.10. Select another entry or click Close to exit the Unknown Files Manager.

Importing the IBM catalogYou use this function to incorporate the changes in a new version of the IBMcatalog into the master catalog.

To merge the IBM catalog with the master catalog, complete the following steps:1. In the initial window of the catalog manager, click Import IBM Catalog.2. Navigate to the folder where you stored the new version of the IBM catalog.



3.

Select the IBM catalog file and click Open.4. A message appears to tell you that the import takes several minutes. Click OK

to continue.The import is completed silently, with no user interaction. When the process iscomplete the following message appears to summarize the changes that havebeen made to the master catalog export file.

5. Click OK.

Modifying entries in the master catalogYou can use the catalog manager function to make changes to existing entries inthe master catalog. The most likely uses for this function are to change incorrectinformation or add details that were not available when the entry was created, forexample, the product vendor.

Importing the IBM catalog


You can make changes to the list of files associated with the product. However, asthe catalog has already been used to monitor software products and to collectusage information, adding or removing files can result in inconsistencies inmonitoring. Therefore, use the function with caution.

To make changes to entries in the master catalog, complete the following steps:1. In the initial window of the catalog manager, click Catalog Manager.

2. From the scrollable list, select a product for which you want to change thecatalog entry and click Edit.The fields below the list can help you to find the product you want to edit. Youcan use the Fast search to move directly to products that match the charactersyou specify . You can select a Vendor or Platform to limit the list to theproducts that match your selection.

Modifying entries


By default, the list does not include disabled products. Disabled products areproducts that are not included in the IBM catalog that do not have any linkedexecutable files. They are not included in any Tivoli License Manager reports. Ifyou want to see disabled products, you must select the Show disabledproducts check box. You can re-enable a product by linking an availableexecutable file to it.

3. Change or complete the information in the editable fields. For products thathave been added to the catalog from the IBM Catalog, no fields on this screenare directly editable; all you are allowed to do is to change the linked files, asdescribed below. For all other products, the Name and Version fields arerequired.

4. If you need to make changes to the linked files, click Add/Remove.The Linked Modules Manager window appears, showing a list of files currentlylinked to the product in the Linked Executables list and a list of files that arenot linked to any product in the Linkable Executables list.

Note: A warning is displayed reminding you that changing the files that arelinked to an application may cause discrepancies in monitoring thesoftware usage.

Modifying entries


5. Change the list of linked executables, as follows:v To dissociate a file from this product, select it in the Linked Executables: list

and click Remove. The executable is transferred to the Linkable Executables:list. Click on OK to return to the Linked Modules Manager window.

Notes:

a. If you remove all the linked files from a product that has not been addedto the master catalog from the IBM catalog, its level of monitoring will bechanged to Disabled and it will not appear on any Tivoli LicenseManager reports.

b. If you remove an executable from a product that was originally importedfrom the IBM Catalog, a warning is displayed reminding you that theassociation between the product and the executable will be remade nexttime you import the IBM Catalog.

v To associate another file with the product, select a file in the LinkableExecutables list and click Add.

6. Click OK to save the changes to the catalog and return to the list of entries.7. Click Close to exit from the catalog manager.

Modifying entries



Appendix A. Messages

Messages appear in the work area of the window. Each message has the followingcomponents:v An external message text, which indicates the nature of the problem.v A message code that can be used as a reference to the error condition.v An internal message text, which provides a more detailed description of the

error and the circumstances that caused it.v A message category, which is one of the following values:

Table 3. Tivoli License Manager message categories

Category Type Description and Response

1 Input error Caused by inconsistent input data in a submitted form orby a failure to find results that match input criteria. Forexample, an input error will be generated if the selectioncriteria you define for a report do not find any matchingproducts to report.

If you get this type of error, check and correct the data yousupplied.

2 Technicalerror

Caused by an internal problem within the Tivoli LicenseManager software.

Contact customer support if this type of error occurs.

3 Business error Associated with database problems, for example, datainsubstantiality, locking errors, or loss of networkconnection.

This type of error is normally caused by a temporarydatabase problem. It may correct itself. Wait and try againlater, or reboot your system.

4 Unexpectederror

The cause of these errors is not predictable.

You should contact software support if this type of erroroccurs.

5 Access error Caused by an attempt by a user to perform anunauthorized operation.

The hideInternalErrorMessage property in the Web interface section of thesystem.properties file controls which of the four message components aredisplayed when an error condition is generated. If hideInternalErrorMessage is setto false, all four components are displayed. If hideInternalErrorMessage is set totrue (the default), the situation is as follows:v For category 1 messages, in response to input errors, only the external message

text is shown.v For all other categories, the error code and the external message text are shown.


Message detailsTable 4 shows the details of the messages that appear on the Web interfaces. Itincludes the standard and long message texts and any parameters used in thetexts, the message number, and the message category of each message. The actionyou should take when a message is displayed depends on the message category.See Table 3 on page 103.

Table 4. Tivoli License Manager messages

Errorcode

External message text andparameters

Internal message text andparameters Category

666 An internal error hasoccurred. Contact your IBMTivoli License Managersystem administrator.

Message: {0}

Parameters0 = native Java™ error message

2

1099 The profile for user {0} cannotbe found. Ask the IBM TivoliLicense Manager systemadministrator to check youruser profile.

Parameters0 = user ID

The profile file {0} for user {1},logged on at {2} cannot be found.

Parameters0 = file name1 = user ID2 = date and time of logon

5

1100 You have used an incorrectuser ID or password. Retrythe logon.

The logon has failed for user {0}.


5

1101 Your user session has timedout or there has been someother problem with your userprofile. Retry the logon.

A user timeout occurred or there hasbeen some other problem with theprofile for user {0}.

Parameters0 = user reference previouslyassigned to the user

5

1102 An internal error occurredwhen trying to create a usersession for user {0}. Contactyour IBM Tivoli LicenseManager systemadministrator.


Access Manager could not create auser session for user {0}.


2

1103 The user ID that you chosealready exists. Choose adifferent user ID.

The user ID already exists on theXML password file.

1

1105 An internal error occurredwhen performing therequested action for user {0}.


The user session is in an illegal statefor the requested action. Message {0}.

Parameters0 = native Java error message

2

Messages


Table 4. Tivoli License Manager messages (continued)

Errorcode



1500 An internal file error hasoccurred. The file {0} was notfound. Contact your IBMTivoli License Managersystem administrator.

Parameters0 = file name

The required file {0} cannot be found.More information might be found inthe log file.


2

1501 An internal I/O error hasoccurred. Contact your IBMTivoli License Managersystem administrator.

More information might be found inthe log file.

2

1502 An internal error has occurredbecause a required variablehas a NULL value. Contactyour IBM Tivoli LicenseManager systemadministrator.

A null pointer error has occurred.More information might be found inthe log file.

2

1503 An internal error has occurredbecause a required class ismissing. Contact your IBMTivoli License Managersystem administrator.

A required class cannot be found.More information might be found inthe log file. The system administratorshould also check the applicationclasspath.

2

1504 An internal error occurredwhile creating or rendering animage. Contact your IBMTivoli License Managersystem administrator.

Message {0}.

Parameters0 = native Java error message

2

1505 An internal error occurredwhile creating a chart. Contactyour IBM Tivoli LicenseManager systemadministrator.

An error occurred while creatingchart {0}. Message {1}.

Parameters0 = chart ID1 = native Java error message

2

1600 An internal error has occurredbecause there are no divisionsset up in the runtime serverdatabase. Contact your IBMTivoli License Managersystem administrator.

No further information is available. 2

1601 An internal error has occurredbecause no runtime serversare available. Contact yourIBM Tivoli License Managersystem administrator.

No servers are available from thedatabase of runtime servers on theadministration server.

2

2001 A database error has occurred.Contact your IBM TivoliLicense Manager systemadministrator.

The DB2 core message is: {0} (SQLerror code = {1}).

Parameters0 = message generated by DB21 = SQL error code

2

Messages

Appendix A. Messages 105


Errorcode



2002 An error has occurred with adatabase object. Contact yourIBM Tivoli License Managersystem administrator.

A required database object could notbe found.

2

2003 An error has occurred whensaving a database object.Contact your IBM TivoliLicense Manager systemadministrator.

The object cannot be saved because itwill break unique constraints.

3

2004 An error has occurred becausethe item you are trying tomodify has been modified byanother user since youselected it. Reselect the itemand retry the operation.

An optimistic locking error hasoccurred.

3

2005 An error occurred during adatabase transactionoperation. Contact your IBMTivoli License Managersystem administrator.

An error occurred while executing acommit, rollback, or other transactionoperation.

2

2101 A database error has occurredwith a non-persistent object.Contact your IBM TivoliLicense Manager systemadministrator.

A non-valid operation was requestedfor a non-persistent object.

3

2102 An operation has beenattempted that would affectthe validity of the database.Contact your IBM TivoliLicense Manager systemadministrator.

You are trying to delete the rootadministrator, change its properties,make a wrong profile assignment, orchange an existing licenseentitlement.

3

2801 A database requiredcomponent was not found.Contact your IBM TivoliLicense Manager systemadministrator.

The JDBC driver was not found. 2

2802 A database connection erroroccurred. Contact your IBMTivoli License Managersystem administrator.

The connection pooler failed to get adatabase connection.

2

2803 It is not possible to create aconnection to the database.Contact your IBM TivoliLicense Manager systemadministrator.

No additional information isavailable.

2

2804 The database connection hasbeen lost. Try the operationagain.

A closed database connection wasfound.

2

2805 The attempt to obtain adatabase connection failed.Try the operation again.

The administration databaseconnection pooler did not initializecorrectly.

2

Messages



Errorcode



2806 The IBM Tivoli LicenseManager database versiondoes not match with theversion of the code. Contactyour IBM Tivoli LicenseManager systemadministrator.

No further information available. 2

4000 An error occurred whileinitializing the logger. Contactyour IBM Tivoli LicenseManager systemadministrator.

An error occurred while initializingclass {0}.

Parameters0 = name of the class

2

4001 A logger error occurred.Contact your IBM TivoliLicense Manager systemadministrator.

An error occurred while performinga logger task, for example, theprocessing of an event.

2

5070 An e-mail notification couldnot be sent. Contact your IBMTivoli License Managersystem administrator.

Message {0}

Parameters0 = native Java message

4

9890 An internal class error hasoccurred. Contact your IBMTivoli License Managersystem administrator.

An exception occurred whileinstantiating class (0).

Parameters0 = full name of the Java class

2

9891 An internal method error hasoccurred. Contact your IBMTivoli License Managersystem administrator.

It was not possible to get or invokemethod (0) on class (1).

Parameters0 = name of the Java method1 = full name of the Java class

2

9900 An internal model object errorhas occurred. Contact yourIBM Tivoli License Managersystem administrator.

Incorrect instance of model object. {0}instead of {1}.

Parameters0 = actual class of object1 = expected class of object

2

9902 A field is missing or out ofrange. Check that your entriesare correct and retry theoperation.

Parameter {0} is out of range,missing, required but null, or ofunexpected type.

Parameters0 = parameter name

1

9903 The specified date and time isin the future for the selectedtime zone. Change the valueand retry the operation.

No additional information isavailable.

1

9905 You have entered one or moreincorrect dates. Change thevalue or values and retry theoperation.

User {0} entered one or moreincorrect dates.


1

Messages



Errorcode



9906 You have tried to update datathat could be out of date. Youmay have more than onewindow open to perform thesame operation. Close allwindows relating to theoperation and then open onenew window to retry it.

Missing object model in the report. 1

9910 An internal error occurredwhen trying to get theresource from bundle file {0}.Contact your IBM TivoliLicense Manager systemadministrator.


Bundle file (0) was not found or doesnot contain a required key.


2

9911 An internal error occurredbecause of an unsupportedoutput format. Contact yourIBM Tivoli License Managersystem administrator.

The unsupported output format is{0}.

Parameters0 = HTML format

2

9912 An internal error occurredbecause a class field was notset. Contact your IBM TivoliLicense Manager systemadministrator.

Field {0} was not set by the servlet.

Parameters0 = field name

2

9913 An internal error occurredbecause of a missingargument. Contact your IBMTivoli License Managersystem administrator.

The argument {0} is missing for thereport.

Parameters0 = argument name

2

9914 An internal error occurredbecause of a missing attributein the user session. Contactyour IBM Tivoli LicenseManager systemadministrator.

The attribute {0} is missing in theuser session.

Parameters0 = attribute name

2

9915 An internal error occurredbecause of a missing modelobject. Contact your IBMTivoli License Managersystem administrator.

Model object {0} is missing.

Parameters0 = class name of missing object

2

9916 The GUI task you haveselected is not available.Contact your IBM TivoliLicense Manager systemadministrator.

The flow controller could not findthe requested reply.

2

Messages



Errorcode



9917 The requested data is out ofdate. You may have morethan one window open toperform the same operation.Close all windows relating tothe operation and then openone window to retry it.

Report {0} is no longer in the usersession.

Parameters0 = report name

1

9918 No {0} is available. Youcannot proceed with theoperation unless at least oneof them exists and has beenselected. Contact your IBMTivoli License Managersystem administrator.

Parameters0 = Type of item

No (0) has been returned by thedatabase query.

Parameters0 = The type of object beingqueried.

1

9919 An internal error has occurredbecause there is no storedaction to be refreshed or towhich you can go back. Logoff and log on again.

There is no action in the user sessionto be retrieved.

2

9920 An internal error has occurredbecause the http requestheader has an incorrectformat. Contact your IBMTivoli License Managersystem administrator.

An unexpected {0} header formatwas found in HttpServletRequest.

Parameters0 = header field name

2

9930 An exception error occurredwhile initializing the DOMdocument or its factoryoccurred because it was notpossible to create the DOMdocument. Contact your IBMTivoli License Managersystem administrator.

An exception occurred whileinitializing the DOM document or itsfactory.

2

9931 An internal error has occurredbecause the DOM documentcould not be built. Contactyour IBM Tivoli LicenseManager systemadministrator.

It is not possible to append node (0)in document (1).

Parameters0 = node name1 = document name

2

9932 An internal error has occurredbecause it was not possible toparse the XML file. Contactyour IBM Tivoli LicenseManager systemadministrator.

The parser failed to parse file (0).


2

Messages



Errorcode



9940 An internal error has occurredbecause the XSL transformercould not be initialized.Contact your IBM TivoliLicense Manager systemadministrator.

The XSL transformer initializationfailed. The XSL file (0) contains oneor more serious errors.

Parameters0 = XSL file name

2

9941 An internal error has occurredbecause it was not possible totransform the XML to HTML.Contact your IBM TivoliLicense Manager systemadministrator.

The XSL file (0) does not match theDOM document or contains one ormore errors.


2

9942 An internal error has occurredbecause the HTML serializercould not be initialized.Contact your IBM TivoliLicense Manager systemadministrator.

The HTML serializer initializationfailed. Check the log file.

2

9943 An internal error has occurredbecause the HTML documentcould not be serialized.Contact your IBM TivoliLicense Manager systemadministrator.

It was not possible to serialize theHTML document using a view basedon XSL file {0}.


9945 An internal error has occurredbecause a view object couldnot be instantiated. Contactyour IBM Tivoli LicenseManager systemadministrator.

It was not possible to instantiateview class {0}: exception {1} occurred.

Parameters0 = View class name1 = Java exception type

2

9950 An internal error has occurredbecause the user entitlementcould not be determined.Contact your Tivoli LicenseManager systemadministrator.

An argument {0} needed byentitlement support for user {1} isnull.

Parameters0 = argument name1 = user ID

2

9951 An internal error has occurredbecause the operation contextis not defined. Contact yourIBM Tivoli License Managersystem administrator.

User {0} has an undefined (NULL)operation context.


2

9952 An internal error has occurredbecause the operation was notfound. Contact your IBMTivoli License Managersystem administrator.

Operation {0} cannot be found.Check the operation hierarchy.

Parameters0 = operation name

2

Messages



Errorcode



9953 You are not authorized to runthis task. Log off and checkwith the IBM Tivoli LicenseManager Super Administratorthat you have been given thecorrect role for the tasks youwish to perform.

User {0} is not entitled to executeoperation {1} in context {2}.

Parameters0 = user ID1 = name of operation2 = name of context

1

9954 User {0} is not authorized touse this application. Checkwith the IBM Tivoli LicenseManager Super Administratorthat the user in question hasbeen given the correct role forthe tasks to be performed.


User {0} is not entitled to use theapplication. Logoff required.


1

9955 User {0} is not authorized tooperate in context {1}. Checkwith the IBM Tivoli LicenseManager Super Administratorthat the user in question hasbeen given the correct role forthe tasks to be performed.

Parameters0 = user ID1 = name of context

User {0} is not entitled to operate incontext {1}, type {2}, value {3}.

Parameters0 = user ID1 = name of context2 = context type3 = context value

1

9960 No existing values of {0}match the previous selections.Please make a differentchoice.

Parameters0 = requested information

No {0} has been returned by thedatabase query.

Parameters0 = type of object

1

9961 The report does not containthe entered page number.Retry the operation,specifying a valid pagenumber.

Page {0} is out of range.

Parameters0 = number of the requestedpage

1

Messages


Messages


Appendix B. Accessibility

The tables in this appendix detail the keyboard alternatives to mouse navigation,selection, and activation on the Tivoli License Manager Web interfaces.

In addition to these key combination assignments, you can also use any standardfeatures for text resizing and keyboard access that are available for your browser.

Navigating the Web interfaceTable 5 shows the key combinations that allow you to navigate between thedifferent areas of the Web Interface.

Table 5. Key combinations for navigating the Web interface

Key combination Action

ALT + p Gives focus to the first link in the portfolio section of thewindow.

ALT + t Gives focus to the first control in the toolbar section of thewindow.

ALT + w Gives control to the first control in the work area section ofthe window.

ALT + u Expands the Software Usage task group in the portfolio.

ALT + i Expands the Software Inventory task group in the portfolio

ALT + y Expands the Topology task group in the portfolio.

ALT + d Expands the Administration task group in the portfolio.

CTRL + RIGHT ARROW Moves focus to the next section of the window.

CTRL + LEFT ARROW Moves focus to the previous section of the window

TAB Moves focus to the next link or control.

SHIFT + TAB Moves focus to the previous item or control.

ENTER Activates the link, tool bar control, or work area button thathas focus. If focus is not on a link, control, or button,pressing ENTER executes the default action.

Shortcut keys for starting tasksTable 6 shows the key combinations for starting the tasks that are listed in theportfolio. These key combinations allow you to start a task directly withoutnavigating the task groups listed in the portfolio.

Table 6. Key combinations for starting tasks

Key combination Task

ALT + SHIFT + s Software Usage Snapshot

ALT + SHIFT + t Software Usage Trend Analysis

ALT + SHIFT + l Software Usage Level Analysis

ALT + SHIFT + r Software Inventory Report

ALT + SHIFT + h Software Inventory Scheduling


Table 6. Key combinations for starting tasks (continued)

Key combination Task

ALT + e Software Entitlement

ALT + SHIFT + d Topology - Divisions

ALT + SHIFT + v Topology - Servers

ALT + SHIFT +n Topology - Nodes

ALT + SHIFT + a Topology - Agents

ALT + SHIFT + u Topology - Users

ALT + SHIFT + c Administration - Accounts

ALT + SHIFT + x Administration - Customers

Shortcut keys for performing toolbar actionsTable 6 on page 113 shows the key combinations for performing the actions that areavailable on the toolbar.

Table 7. Key combinations for toolbar actions

Key combination Action

ALT + m Toggles the view between displaying and hiding theportfolio section of the window.

ALT + f Displays the home page where you can select a differentcustomer.

ALT + r Refreshes the current window.

ALT + a Opens the accessiblity help window.

ALT + h Opens the help window for the current dialog.

ALT + n Opens the Tivoli License Manager information window.

ALT + o Signs off from the Web interface.

Shortcut keys to start tasks


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents.You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksThe following terms are trademarks of the IBM Corporation in the United States orother countries or both:

AIXDB2DB2 Universal DatabaseIBMThe IBM logoNetfinityRS/6000


TivoliTivoli EnterpriseWebSphere

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

Microsoft, Windows, Windows NT, and the Windows logo are registeredtrademarks, of Microsoft Corporation in the U.S. and other countries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the U.S., and other countries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 117


Glossary

Aaccount. See administration account.

administrator. A person who performs the followingtasks for a set of assigned customers.

v Manages the license management environmentincluding registration of runtime servers, divisions,and agents

v Manages license entitlement and license pooldefinitions

v Produces reports

v Receives and reacts to notifications of events

administration server. A component that performs thefollowing tasks:

v Maintains a database of product, license, customer,application user, and infrastructure information

v Provides a Web interface where administrators candefine and update the infrastructure and license rulesfor their customers and produce historical reports

administration server database. A DB2 databaseassociated with the administration server. This databasestores the information about customers, monitoringinfrastructure, and license entitlement that are definedon the administration server as well as the historicinventory and software usage information that is usedin the historical reports available on the administrationserver Web interface.

administration account. The record of anadministrator that is stored in the database.Administration account details include the logoninformation, e-mail address, level of access, and thecustomers that are assigned to the administrator.

agent. A component that is deployed from a runtimeserver to a customer node that is to be monitored. Anagent performs the following functions on themonitored node:

v Performs regular inventory scans and forwards theresults to the runtime server

v Identifies the starting or stopping of monitoredapplications and communicates to the runtime serverso that a license can be assigned or released

application user. A user who can start applications onmonitored nodes. Details of application users aremaintained to allow license pools to be restricted tospecified users.

Ccapacity type. The property of a license pool thatspecifies how to determine the number of requiredlicenses for an application. Depending on the capacitytype selected for the pool, the number of licensesrequired can be based on the number of usersrequesting a license or can depend on the size of thememory, number of processors, or number of harddisks on the node where the application is started.

customer. An organization whose license managementis controlled by Tivoli License Manager. Each customeris the owner of a set of the Tivoli License Managercomponents, including runtime servers, divisions,agents, and application users.

Ddivision. An administrative unit of Tivoli LicenseManager. Divisions are used to group agents so thatthey can be selected as a group, for example whenscheduling inventory scans or specifying targetdistribution rules.

Eevent. An occurrence that causes a notification to begenerated. Events can relate to license management, forexample a usage threshold is reached, or to thefunctioning of Tivoli License Manager, for example, anagent is not responding.

Hhard stop. A property of a license pool that specifieswhether the number of licenses available in the pool isan absolute maximum. If the property is set to Yes, it isan absolute maximum, which means that when alllicenses are in use, no further instances of theapplication can be opened. If the property is set to No,it means that the number of licenses available can beexceeded.

high-water mark. The maximum concurrent licenseusage for a product since the high-water mark was lastreset. Depending on the context, this can refer to usagewithin a specific license pool or to usage for all licensepools of the same capacity type.


Iinventory scan. An operation performed by agents todiscover all the software applications installed onmonitored nodes. Inventory scans can be scheduled torepeat at regular, defined intervals.

Llicense pool. A set of licenses for a specific productthat are administered as a group with a set of rulesgoverning thresholds, hard stops, license allocation tomultiple sessions of the same product, and theavailability of the product to users and nodes.

Mmaster catalog. The central repository of productinformation about all software components and relatedfiles for products that can be monitored.

metering. A process by which software usage ismeasured and recorded.

multi-instance. A property of a license pool thatdetermines whether multiple sessions of an applicationcan be opened using a single license. Multi-instancelicenses can apply to multiple sessions for the sameuser, for users in the same user group, or for sessionson the same node.

Nnode. A workstation in the network that can bemonitored by Tivoli License Manager when an agent isdeployed on it.

notification. An e-mail sent to a designatedadministrator in response to a license management orinternal event.

metering. A process by which software usage ismeasured and recorded. The data recorded (forexample, number of sessions, number of concurrentsessions, duration of sessions, capacity used, node ID,user ID) may be used by licensees to assess licenserequirements, or by software vendors to verifycompliance or to make billing calculations.

Pproduct entitlement settings. A definition thatdetermines whether or not the usage of a productshould be monitored and the level of licenseenforcement that should be applied.

Rruntime catalog. A subset of the master catalogcreated on each runtime server. Entries are added tothe runtime catalog either when user-definedentitlement settings for applications are downloadedfrom the administration server or when applications aredetected on the nodes monitored by agents that belongto the runtime server.

runtime server. A component that performs thefollowing functions:

v Assigns and releases licenses according to the rulesdefined in the license pools when it receives arequest from the agent

v Compiles inventory information about monitorednodes that it receives from its agents and forwardsthe information to the administration server

v Generates and sends notifications in response toevents that occur on the server itself or any of itsagents

v Provides Web interfaces for the deployment of agentsand the production of real-time reports

Ssoftware entitlement. Rules that define how asoftware product is monitored, the conditions underwhich licenses are allocated, and any restrictions placedon the availability of license pools to application usersand monitored nodes.

Ttarget. Any part of a license managementinfrastructure that can have exclusive use of a licensepool. A target can be a division, a node, or an agent,depending on how the target distribution rules for thelicense pool are defined.

target distribution parameters. Rules associated witha license pool that limit the availability of the licensepool to selected targets. The targets can be divisions,nodes, or agents depending on the target type propertyof the license pool.

target type. The property of a license pool thatspecifies where the license pool is available in thecustomer’s environment. The target type for a licensepool is set to one of the following values:v Enterprisev Divisionv Nodev Agent

An enterprise license pool is available throughout thecustomer organization. For division, node, and agentlicense pools, the administrator defines the target

inventory scan • target type


distribution parameters to determine the availability ofthe license pool in those locations.

threshold. A percentage of the licenses available in alicense pool; if more than this percentage of licenses fora product is in use, notifications about the level of useare generated.

topology. The structure in which a customer’s runtimeservers, divisions, and agents are organized.

Uunknown file list. A list, compiled by the agent, thatidentifies any applications detected on the monitorednode that are not included in the copy of the runtimecatalog that has been downloaded to the agent.

unknown file table. A file that is maintained on eachruntime server. It is a compilation of the applications inthe unknown file lists of all agents for that runtimeserver and identifies applications that are not in thecurrent runtime catalog. If the applications in theunknown file table correspond to entries in the mastercatalog, the entries are added to the runtime catalog.

user. See application user.

user distribution parameters. Rules associated with alicense pool that limit the availability of the licensepool to selected application users. The default setting isto allow all users of applications to access the licensepool.

threshold • user distribution parameters

Glossary 121


Index

Aaccessibility xi, 113

navigating the interface 113navigation key combinations 113task key combinations 113toolbar key combinations 114

accessingadministration server 8agent registration interface 7online publications xruntime server 9server Web pages 5Web interfaces 7

accountadding 17deleting 19updating 19

actionson the toolbar 12

addingadministrator account 17customer 16divisions 27nodes 35users 38

AdministrationAccounts 17, 19Customers 16

administration serveraccessing 8logging on 8summary of functionality 2Web interface tasks 12

administratorassigned to the customer 3change password 21

administrator accountadding 17deleting 19updating 19

agentautomatic upgrade 2, 32deleting 32installing 30reviewing 32select for license pool distribution 51self-update 32summary of functionality 2target type for license pool 49, 55

agent registration interfaceaccessing 7

agentsin software usage snapshot 64

application usersadding to the database 38deleting 39updating 39

associate functionunknown files manager 95

automaticagent upgrade 2, 32

automatic (continued)cache refresh 8event notification 18license pool deployment 5notifications 2, 5runtime catalog creation 91

Bbenefits of Tivoli License Manager 1books

accessing online xonline xordering x

browser settingsdefault 8

Ccapacity type

changing 63defining in license pool 48in level analysis report 74selecting in realtime software usage report 78selecting in software usage snapshot 63

catalogexporting master 92IBM 97importing master 94master 4, 91merging IBM catalog with master 97modifying entries in master 98runtime 4, 91updating master 92updating master with unknown files 94

catalog manager 4, 91, 98starting 92

catalog.dat file 92, 93, 94categories of messages 103changing

capacity type 63customer 16divisions 28license pools 52master catalog 98nodes 36notifications 20runtime servers 25user details 39

commandexpcat 92impcat 94

components of Tivoli License Manager 2create function

unknown files manager 96creating

a license pool 47selecting products 43

administrator account 17customer 16


creating (continued)divisions 27nodes 35users 38

customeradding to the administration server database 16deleting 16new 16

customer support xicustomers

updating 16

Ddefault

browser settings 8dynamic list size 12license pool 4

using 46license pool settings 47license settings 4port 8, 9, 26

deletingagents 32customers 16divisions 28nodes 36user details 39

directory names, notation xiidisabling software monitoring 46displaying

agents 32customers 16divisions 28nodes 36runtime servers 25user details 39

distribution detailschanging 54creating for license pool 50target selection 51

divisionadding new 27deleting 28reviewing 28select for license pool distribution 51target type for license pool 49, 55updating 28

dynamic list sizedefault 12

Eenabling software monitoring 46enterprise

target type for license pool 49, 55entitlement settings

maintaining 45selecting products for defining 43

environment variables, notation xiievent notifications

defining recipients 18event.log file 25events

summary 5expcat command 92

exportlevel analysis report 71, 75master catalog 92

exportingreports 82

Ffile

catalog.dat 92, 93, 94event.log 25system.properties 31, 32, 83, 89, 103Tivoli Catalog.INI 98Tivoli Signatures 91

frequencyof inventory scans 84

Ggenerate

notifications 2, 5

Hhard stop licenses 48, 53

IIBMcatalog 97icons

on the toolbar 12impcat command 94import

master catalog 94installing agents 30inventory

reporting 85reports 5scheduling scans 83

inventory reportsexporting 82

Kkey combinations

navigation 113tasks 113toolbar 114

Llevel analysis report

selecting products for 71level analysis software usage report 71license administration

summary 4license pool

changing distribution details for 54creating 47creating distribution details for 50default 4modifying 52restricting to selected targets 49, 50, 55restricting to selected users 49, 50, 56


license pool (continued)selecting products for creating or modifying 43

license poolsin real-time software usage report 79in software usage snapshot 65

license settingsdefault 4

loggingproblem determination 5

logging onadministration server 8runtime server 9

Mmaintaining entitlement settings 45maintaining product settings 45manuals

accessing online xonline xordering x

master catalog 4, 91changing 98exporting 92importing 94merging IBM catalog with 97modifying 98updating 92updating with unknown files 94

messagescategories 103descriptions 104on the Web interfaces 103

modifyinglicense pools 52master catalog 98

modifying license poolsselecting products 43

multi-instance licenses 49, 53

Nnavigating

usage snapshot report 62new

administrator account 17customer 16division 27node 35user 38

nodeadding new 35deleting 36reviewing 36select for license pool distribution 51target type for license pool 49, 55updating 36

nodesin software usage snapshot 64

notationenvironment variables xiipath names xiitypeface xii

notificationschanging 20defining recipients 18

notifications (continued)events 2, 5, 18summary 5

Oonline publications

accessing xordering publications x, xi

Ppassword

change for administrator 21changing for runtime servers 25

path names, notation xiiportfolio

how to use 11problem determination

logging 5support 5

productselecting for defining entitlement settings 43selecting for defining license pools 43

product detailsin realtime software usage report 79in software usage snapshot 63

product listin realtime software usage report 77in software usage snapshot 62

product settingsmaintaining 45selecting products for defining 43

propertyupdateAgentEnabled 32

publicationsaccessing online xonline xordering x

Qquantity of licenses

changing 54setting 49

Rreal-time software usage report

sessions 81realtime software usage report 75

license pools 79list of products 77product details 79selecting products for 75

recipientsof event notifications 18

reportsoftware inventory 85software usage level analysis 71software usage realtime 75software usage snapshot 59software usage trend analysis 67

reportingsoftware usage 59

Index 125

reportssummary 5

reviewingagents 32customer 16divisions 28nodes 36runtime servers 25user details 39

runtime catalog 4, 91automatic creation 91

runtime serveraccessing 9changing password 25interface tasks 12logging on 9registering 24reviewing 25software usage 75summary of functionality 2updating 25

Sscan

inventory 83server Web pages

accessing 5sessions

in real-time software usage report 81in software usage snapshot 66

snapshot software usage report 59Software Entitlement

task group 43software inventory

reporting 85scheduling scans 83

Software InventoryReport 85Scheduling 83task group 83

software inventory reportsexporting 82

software meteringsummary 4

software monitoringdisabling 46enabling 46

software support xisoftware usage

level analysis report 71on runtime server 75realtime report 75reports 5snapshot report 59trend analysis report 67

Software UsageLevel Analysis 71Snapshot 59task group 59Trend Analysis 67

software usage reportsexporting 82

software usage snapshotagents 64license pools 65list of products 62

software usage snapshot (continued)nodes 64product details 63selecting products for 59sessions 66

starting catalog manager 92system.properties file 31, 32, 83, 89

setting message display property 103

Ttables

unknown files 4unknown files table 91usage snapshot report agents table 64usage snapshot report license pools table 65usage snapshot report product list 62usage snapshot report product table 64usage snapshot report sessions table 66

target typesetting for license pool 49, 55

task groupSoftware Entitlement 43Software Usage 59Topology 23

tasksAdministration->Accounts 17, 19Administration->Customers 16on the Web interface 12Software Entitlement 43Software Inventory->Report 85Software Usage->Level Analysis 71Software Usage->Snapshot 59Software Usage->Trend Analysis 67Topology->Agents 32Topology->Divisions 27, 28Topology->Nodes 35, 36Topology->Servers 24, 25Topology->Users 38, 39

threshold in license poolchanging 54setting 49

Tivoli Catalog.INI file 98Tivoli License Manager components 2Tivoli signatures file 91Tivoli Software Information Center xtoolbar

actions 12topology

tasks for defining components 23Topology

Agents 32Divisions 27, 28Nodes 35, 36Servers 24, 25Users 38, 39

trend analysis reportselecting products for 67

trend analysis software usage report 67

Uunknown file list 4, 91unknown file table 4, 91unknown files

associating with existing catalog entry 95


unknown files (continued)creating new catalog entry 96updating master catalog 94

unknown files manager 94associate function 95create function 96

updateAgentEnabled property 32updating

customer 16divisions 28license pool 52nodes 36runtime servers 25user details 39

updating license poolsselecting products 43

usage snapshot reportnavigating 62

user defined license pools 47users

adding to the database 38deleting 39tlmroot 7, 8, 10, 20updating 39

Vvariables, notation for xii

WWeb administration server

interface tasks 12logging on 8summary of functionality 2

Web interface 11tasks 12

Web runtime serverchanging password 25interface tasks 12logging on 9registering 24reviewing 25summary of functionality 2updating 25

work areatypes of control 11

Index 127


��

Program Number: 5724-D33

GC23-4833-01

Documents

IBM Tivoli License Managerpublib.boulder.ibm.com/tividd/td/ITLM/GC23-4833-01/en_US/... · 2005-11-11 · Shortcut keys for starting tasks .....113 Shortcut keys for ... Provides descriptions