certification guide series ibm tivoli usage and accounting manager v7.1 implementation sg247692

ibm.com/redbooks

Certification Guide Series:IBM Tivoli Usage and Accounting Manager V7.1 Implementation

Budi Darmawan

Detailed architecture and components discussion

Installation and configuration processing

Monitoring IT usage and chargebacks

Front cover

http://www.redbooks.ibm.com/


Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

March 2009

International Technical Support Organization

SG24-7692-00

© Copyright International Business Machines Corporation 2009. All rights reserved.Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

First Edition (March 2009)

This edition applies to Version 7, Release 1 of IBM Tivoli Usage and Accounting Manager (product number 5724-033).

Note: Before using this information and the product it supports, read the information in “Notices” on page vii.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixThe team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixBecome a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xComments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Chapter 1. Certification overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 IBM Professional Certification Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

1.1.1 Benefits of certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1.2 Tivoli Software Professional Certification . . . . . . . . . . . . . . . . . . . . . . 4

1.2 Tivoli Usage and Accounting Manager V7.1 . . . . . . . . . . . . . . . . . . . . . . . . 61.2.1 Job role description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.2 Key areas of competency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.3 Prerequisite skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.4 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.3 Certification objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3.3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.3.4 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.5 Job creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.3.6 Problem determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.3.7 Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.4 Recommended study resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.4.1 IBM Redbooks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.1 Planning the implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.2 Account code structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.3 Collector selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.4 Implementation platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.5 Database sizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.5.1 CIMSLOADTRACKING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342.5.2 CIMSSUMMARY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.5.3 CIMSDETAIL and CIMSDETAILIDENT . . . . . . . . . . . . . . . . . . . . . . 362.5.4 CIMSRESOURCEUTILIZATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.6 Report requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

© Copyright IBM Corp. 2009. All rights reserved. iii

Chapter 3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.2 Installation prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

3.2.1 Platform requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.2.2 Configuring Microsoft Internet Information Services . . . . . . . . . . . . . 453.2.3 Install the Microsoft Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.2.4 Install Microsoft .NET Framework 2.0 . . . . . . . . . . . . . . . . . . . . . . . . 513.2.5 Install Microsoft SQL Server Report Viewer . . . . . . . . . . . . . . . . . . . 52

3.3 Application server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543.4 Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

3.4.1 Database creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593.4.2 Defining JDBC driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603.4.3 Defining data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.4 Initializing database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3.5 Enterprise Collector Pack implementation . . . . . . . . . . . . . . . . . . . . . . . . 673.6 Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.7 Installation verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

3.7.1 Verify the tables created during initialization. . . . . . . . . . . . . . . . . . . 723.7.2 Verify the contents of the CIMSRate table . . . . . . . . . . . . . . . . . . . . 733.7.3 Verify the application status in IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . 743.7.4 Connect to the reporting Web application . . . . . . . . . . . . . . . . . . . . . 74

3.8 Sample collection verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 4. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.1 The Common Source Resource format. . . . . . . . . . . . . . . . . . . . . . . . . . . 804.2 Account code hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.3 User administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4.3.1 User creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.3.2 User role definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864.3.3 User and group mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.4 Clients and scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884.4.1 Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884.4.2 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.4.3 Client budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904.4.4 Client contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4.5 Working with rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.5.1 Rate group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.5.2 Rate codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.5.3 Alternate rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.5.4 Proration table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954.5.5 CPU normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964.5.6 Rate shift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

iv Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

Chapter 5. Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995.1 Integrated Solution Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005.2 Load tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.3 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

5.3.1 Tuning Web console for administration. . . . . . . . . . . . . . . . . . . . . . 1045.3.2 Tuning job processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.3.3 Tuning report generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5.4 Operating and updating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.4.1 Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.4.2 Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.4.3 Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 6. Job creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096.1 XML job creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

6.1.1 Job file structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106.1.2 Generic processing overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

6.2 Syntax of main Job Runner directives. . . . . . . . . . . . . . . . . . . . . . . . . . . 1146.2.1 Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156.2.2 Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156.2.3 Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176.2.4 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176.2.5 Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186.2.6 Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

6.3 Integrator program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196.3.1 Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216.3.2 Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216.3.3 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6.4 Account code mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236.5 Non-integrator steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

6.5.1 Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.5.2 Acct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.5.3 Bill . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.5.4 Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316.5.5 Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.5.6 DBLoad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.5.7 DBPurge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336.5.8 Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1336.5.9 File transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1346.5.10 Wait file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356.5.11 Remote product deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356.5.12 Job conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356.5.13 Windows script file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1366.5.14 Java. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Contents v

6.5.15 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 7. Problem determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1377.1 Job failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

7.1.1 Job logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1387.1.2 Output files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

7.2 Database connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407.3 Web reporting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417.4 Trace level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 8. Web reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1438.1 Web reporting interface and user authority . . . . . . . . . . . . . . . . . . . . . . . 1448.2 Web reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1458.3 Producing reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1538.4 Defining a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1558.5 Batch reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Appendix A. Sample test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Sample test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Answer key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

vi Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product 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 it believes appropriate without incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2009. All rights reserved. vii

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both:

AIX 5L™AIX®CICS®DB2 Universal Database™DB2®IBM®Lotus Notes®

Lotus®Notes®Passport Advantage®PowerPC®Redbooks®Redbooks (logo) ®System p®

System z®Tivoli®TotalStorage®WebSphere®z/OS®z/VM®

The following terms are trademarks of other companies:

ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.

SUSE, the Novell logo, and the N logo are registered trademarks of Novell, Inc. in the United States and other countries.

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation and/or its affiliates.

SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries.

VMware, the VMware "boxes" logo and design are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Java, JDBC, JVM, Solaris, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Internet Explorer, Microsoft, MS, OpenType, SQL Server, Visual Basic, Windows Server, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

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

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

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

viii Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

http://www.ibm.com/legal/copytrade.shtml

Preface

This IBM® Redbooks® publication is a study guide for the IBM Tivoli® Usage and Accounting Manager V7.1 certification. It is aimed for IT professional who want to be an IBM Certified Professional for this product.

IBM Tivoli Usage and Accounting Manager V7.1 certification is offered through the IBM Professional Certification program. It is designed to validate the skills required of technical professionals who work in the implementation and deployment of IBM Tivoli Usage and Accounting Manager V7.1.

This book provides the necessary information to understand this topic. It includes sample questions that help evaluate personal progress. It familiarizes the readers with the types of questions that may be encountered in the exam.

This guide does not replace practical experience. This is not designed to be a stand-alone guide for this topic. Instead, this guide should be combined with educational activities and experiences and used as a very useful preparation guide for exam.

For your convenience, the chapters are based on the certification objectives of the IBM Tivoli Usage and Accounting Manager V7.1 implementation certification test. Those requirements are planning, prerequisites, installation, configuration, administration, and problem determination. Studying each chapter helps you prepare for each objective of the exam.

The team that wrote this book

This book was produced by a team of specialists from around the world working at the International Technical Support Organization, Austin Center.

Budi Darmawan is a project leader at the International Technical Support Organization, Austin Center. He writes extensively and teaches IBM classes worldwide on all areas of Tivoli and systems management. Before joining the ITSO 10 years ago, Budi worked in IBM Global Services, IBM Indonesia as a solution architect and lead implementer. His current interests include service management, application management, business services management, and Java™ programming.

© Copyright IBM Corp. 2009. All rights reserved. ix

Thanks to the following people for their contributions to this project:

Wade WallaceInternational Technical Support Organization, Austin Center

Terry CopelandIBM Software Group

Jörn Siglen, Lennart Lundgren, Roy CatterallAuthors of Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1, SG24-7569 and IBM Tivoli Usage Accounting Manager V7.1 Handbook, SG24-7404

Become a published author

Join us for a two- to six-week residency program! Help write a book dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You will have the opportunity to team with IBM technical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you will develop a network of contacts in IBM development labs, and increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about this book or other IBM Redbooks in one of the following ways:

� Use the online Contact us review Redbooks form found at:

ibm.com/redbooks

� Send your comments in an e-mail to:

[email protected]

x Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

http://www.redbooks.ibm.com/residencies.html

http://www.redbooks.ibm.com/residencies.html



http://www.redbooks.ibm.com/contacts.html

� Mail your comments to:

IBM Corporation, International Technical Support OrganizationDept. HYTD Mail Station P0992455 South RoadPoughkeepsie, NY 12601-5400

Preface xi

xii Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

Chapter 1. Certification overview

This chapter provides an overview of the skills requirements needed to obtain an IBM Certified Deployment Specialist - IBM Tivoli Usage and Accounting Manager V7.1 certification. This chapter provides a comprehensive review of topics that are essential for obtaining the certification:

� 1.1, “IBM Professional Certification Program” on page 2

� 1.2, “Tivoli Usage and Accounting Manager V7.1” on page 6

� 1.3, “Certification objectives” on page 8

� 1.4, “Recommended study resources” on page 22

1

© Copyright IBM Corp. 2009. All rights reserved. 1

1.1 IBM Professional Certification Program

Having the right skills for the job is critical in the growing global marketplace. IBM Professional Certification is designed to validate skill and proficiency in the latest IBM solution and product technology. It can help provide that competitive edge. The IBM Professional Certification Program Web site is available at:

http://www.ibm.com/certify/index.shtml

The Professional Certification Program from IBM offers a business solution for skilled technical professionals seeking to demonstrate their expertise to the world.

The program is designed to validate your skills and demonstrate your proficiency in the latest IBM technology and solutions. In addition, professional certification may help you excel at your job by giving you and your employer confidence that your skills have been tested. You may be able to deliver higher levels of service and technical expertise than non-certified employees and move on a faster career track.

The certification requirements are difficult, but they are not overwhelming. It is a rigorous process that differentiates you from everyone else. The mission of IBM Professional Certification is to:

� Provide a reliable, valid, and fair method of assessing skills and knowledge.

� Provide IBM with a method of building and validating the skills of individuals and organizations.

� Develop a loyal community of highly skilled certified professionals who recommend, sell, service, support, and use IBM products and solutions.

The Professional Certification Program from IBM has developed certification role names to guide you in your professional development. The certification role names include IBM Certified Specialist, IBM Certified Solutions/Systems Expert, and IBM Certified Advanced Technical Expert. These role names are for technical professionals who sell, service, and support IBM solutions. For technical professionals in application development, the certification roles include IBM Certified Developer Associate and IBM Certified Developer. An IBM Certified Instructor certifies the professional instructor.

The Professional Certification Program from IBM provides you with a structured program leading to an internationally recognized qualification. The program is designed for flexibility by allowing you to select your role, prepare for and take tests at your own pace, and, in some cases, select from a choice of elective tests best suited to your abilities and needs. Some roles also offer a shortcut by giving credit for a certification obtained in other industry certification programs.

2 Certification Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 Implementation

http://www.ibm.com/certify/index.shtml

You can be a network administrator, systems integrator, network integrator, solution architect, solution developer, value-added reseller, technical coordinator, sales representative, or educational trainer. Regardless of your role, you can start charting your course through the Professional Certification Program from IBM today.

1.1.1 Benefits of certification

Certification is a tool to help objectively measure the performance of a professional on a given job at a defined skill level. Therefore, it is beneficial for individuals who want to validate their own skills and performance levels, their employees, or both. For the optimum benefit, the certification tests must reflect the critical tasks required for a job, the skill levels of each task, and the frequency by which a task needs to be performed. IBM prides itself in designing comprehensive, documented processes that ensure that IBM certification tests remain relevant to the work environment of potential certification candidates.

In addition to assessing job skills and performance levels, professional certification can also provide such benefits as:

� For employees:

– Promotes recognition as an IBM certified professional

– Helps to create advantages in interviews

– Assists in salary increases, corporate advancement, or both

– Increases self-esteem

– Provides continuing professional benefits

� For employers:

– Measures the effectiveness of training

– Reduces course redundancy and unnecessary expenses

– Provides objective benchmarks for validating skills

– Makes long-range planning easier

– Helps to manage professional development

– Aids as a hiring tool

– Contributes to competitive advantage

– Increases productivity

– Increases morale and loyalty

Chapter 1. Certification overview 3

� For IBM Business Partners and consultants:

– Provides independent validation of technical skills

– Creates competitive advantage and business opportunities

– Enhances prestige of the team

– Contributes to IBM requirements for various IBM Business Partner programs

Specific benefits can vary by country (region) and role. In general, after you become certified, you should receive the following benefits:

� Industry recognition

Certification may accelerate your career potential by validating your professional competency and increasing your ability to provide solid, capable technical support.

� Program credentials

As a certified professional, you receive, by e-mail, your certificate of completion and the certification mark associated with your role for use in advertisements and business literature. You can also request a hardcopy certificate, which includes a wallet-size certificate.

The Professional Certification Program from IBM acknowledges the individual as a technical professional. The certification mark is for the exclusive use of the certified individual.

� Ongoing technical vitality

IBM Certified Professionals are included in mailings from the Professional Certification Program from IBM.

1.1.2 Tivoli Software Professional Certification

The IBM Tivoli Professional Certification program offers certification testing that sets the standard for qualified product consultants, administrators, architects, and partners.

The program also offers an internationally recognized qualification for technical professionals seeking to apply their expertise in today's complex business environment. The program is designed for those who implement, buy, sell, service, and support IBM Tivoli solutions and want to deliver higher levels of service and technical expertise.


Benefits of being Tivoli certifiedTivoli certification provides the following benefits:

� For the individual:

– IBM Certified certificate and use of logos on business cards

– Recognition of your technical skills by your peers and management

– Enhanced career opportunities

– Focus for your professional development

� For the IBM Business Partner:

– Confidence in the skills of your employees

– Enhanced partnership benefits from the IBM Business Partner program

– Billing your employees out at higher rates

– Strengthens your proposals to customers

– Demonstrates the depth of technical skills available to prospective customers

� For the customer:

– Confidence in the services professionals handling your implementation

– Ease of hiring competent employees to manage your Tivoli environment

– Enhanced return on investment (ROI) through more thorough integration with Tivoli and third-party products

– Ease of selecting a Tivoli Business Partner that meets your specific needs

Certification checklistThe certification process is as follows:

1. Select the certification that you want to pursue.

2. Determine which test or tests are required by reading the certification role description.

3. Prepare for the test, using the following resources provided:

– Test objectives, discussed in 1.3, “Certification objectives” on page 8

– Recommended educational resources, discussed in 1.4, “Recommended study resources” on page 22

– Sample/assessment test, discussed in Appendix A, “Sample test” on page 157

– Other reference materials

– Opportunities for experience


4. Register to take a test by contacting one of our worldwide testing vendors:

– Thomson Prometric

– Pearson Virtual University Enterprises (VUE)

5. Take the test. Be sure to keep the Examination Score Report provided upon test completion as your record of taking the test.

6. Repeat steps three through five until all required tests are successfully completed for the desired certification role. If additional requirements are needed (such as another vendor certification or exam), follow the instructions on the certification description page to submit these requirements to IBM.

7. After you complete your certification requirements, you will be sent an e-mail asking you to accept the terms of the IBM Certification Agreement before receiving the certificate.

8. Upon acceptance of the terms of the IBM Certification Agreement, an e-mail will be sent containing the following electronic deliverables:

– A Certification Certificate in PDF format, which can be printed in either color or black and white

– A set of graphic files of the IBM Professional Certification mark associated with the certification achieved

– Guidelines for the use of the IBM Professional Certification mark

9. To avoid unnecessary delay in receiving your certificate, ensure that we have your current e-mail on file by keeping your profile up to date. If you do not have an e-mail address on file, your certificate will be sent through postal mail.

After you receive a certificate by e-mail, you can also contact IBM at mailto:[email protected] to request that a hardcopy certificate be sent by postal mail.

1.2 Tivoli Usage and Accounting Manager V7.1

This section explains certification requirements and objectives. The following topics are discussed:

� 1.2.1, “Job role description” on page 7� 1.2.2, “Key areas of competency” on page 7� 1.2.3, “Prerequisite skills” on page 7� 1.2.4, “Requirements” on page 8


mailto:[email protected]

1.2.1 Job role description

An IBM Certified Deployment Professional - IBM Tivoli Usage and Accounting Manager V7.1 implementation is a technical professional responsible for planning, installing, configuring, administering, and problem determination of an IBM Tivoli Usage and Accounting Manager V7.1 solution. This individual will be expected to perform these tasks with limited assistance from peers, product documentation, and support resources.

1.2.2 Key areas of competency

The following key areas of competency are required:

� Describe the IBM Tivoli Usage and Accounting Manager V7.1 architecture and components.

� Plan and design an IBM Tivoli Usage and Accounting Manager V7.1 solution based on customer requirements and environment.

� Install and configure IBM Tivoli Usage and Accounting Manager V7.1 infrastructure components.

� Use the Integrated Solutions Console to administer and manage the IBM Tivoli Usage and Accounting Manager V7.1 environment.

� Perform problem determination for IBM Tivoli Usage and Accounting Manager V7.1.

1.2.3 Prerequisite skills

The following are the required prerequisite skills for this certification:

� Strong working knowledge of IBM Tivoli Usage and Accounting Manager V7.1 infrastructure components

� Working knowledge of operating systems, networking, and firewall concepts

� Working knowledge of XML

� Working knowledge of shell and scripting

� Basic knowledge of WebSphere® Application Server

� Basic knowledge of databases, such as DB2®, Microsoft® SQL Server®, and Oracle®

� Basic knowledge of security (SSL, data encryption, system user accounts, and credentials)

� Basic knowledge of IIS


� Basic knowledge of LDAP

Additionally, we recommend having working knowledge of BIRT.

1.2.4 Requirements

This certification requires one test: test 012 - IBM Tivoli Usage and Accounting Manager V7.1 Implementation.

1.3 Certification objectives

The certification has the following objectives:

� 1.3.1, “Planning” on page 8� 1.3.2, “Installation” on page 11� 1.3.3, “Configuration” on page 13� 1.3.4, “Administration” on page 16� 1.3.5, “Job creation” on page 17� 1.3.6, “Problem determination” on page 19� 1.3.7, “Reporting” on page 21

For the most updated objectives of the IBM Tivoli Usage and Accounting Manager V7.1 Deployment Certification Test, refer to the following link:

http://www-03.ibm.com/certify/certs/24108801.shtml

1.3.1 Planning

Given the customer requirements and the financial organization prerequisites, discuss the key parameters and methods for installing IBM Tivoli Usage and Accounting Manager, so that a design document for the implementation of the IBM Tivoli Usage and Accounting Manager environment has been created, with emphasis on performing the following tasks:

� Discuss the customer requirements in a workshop to show up the critical path.

– Understand the financial system of the customer.

– Define the account code structure to fit current and future plans for the customer environment.

– Select the key parameters needed for accounting.


http://www-03.ibm.com/certify/certs/24108801.shtml

� Plan IBM Tivoli Usage and Accounting Manager setup actions to be done.

– Identify the data sources, identifiers, and rates to be used.

– List the default collectors to be used and new collectors to be written.

– Estimate the size of the database to be expected.

� Use the system management functions available.

– Determine the method of scheduling jobs.

– Define the data transfer solution to be implemented.

– Determine the monitoring solution to be used for the environment.

� Clarify the operational view of the environment.

– Define the reporting solution to be used (BIRT, Crystal or IIS reporting).

– Check server placement in the secured network environment, regarding data collection.

– Decide whether to use the financial modeler.

� Determine the licenses held or to be bought by the customer.

Given a list of planed collectors and data sources, determine if the required collectors are available and supported for the proposed environment, so that a list of collectors to be used has been documented, with emphasis on performing the following tasks:

� Check for a sample collector reading the type of source (for each data source).

� Check the documentation for platform dependent components (for each collector), such as the Windows® Script File (WSF) collector for Windows only collection.

� List the result of all checks.

Given an overview of the current IT environment and the IBM Tivoli Usage and Accounting Manager implementation design, check several parameters of the different platforms regarding the functions and knowledge, which we recommend for the platform to be used has been documented, with emphasis on performing the following tasks:

� Determine the platform skill of the designate operations and administration team.

� Determine the database skill of the administration team.

� Check for mandatory collectors depending on a single platform.

� Check that the reporting solution to be used is supported.

� Determine if the use of Financial modeler is mandatory.


� Verify the required size of the environment and whether it enforces the separation of application parts (WebSphere, database, and reporting server).

� Check for scalability needed in the environment.

Given that the client understands the purpose of the Account Code structure, define the account code structure so that it can be configured into the product, with emphasis on performing the following tasks:

� Educate the client management team about the purpose and use of the Account Code structure.

� Review with the client management team any current business accounting structure and determine if that is how they desire to map the IBM Tivoli Usage and Accounting Manager structure.

� Define the Account Code structure.

Given that the Account Code structure has been defined, determine, for each collector feed, which identifiers should be used for creating Account Code lookup tables for each collector, with emphasis on performing the following tasks:

� For each collector feed, review the documented available identifiers.

� Determine which identifiers should be used to map resource records to the appropriate Account Code.

� Determine how the Account Code lookup table will be built and maintained.

Given the amount of collector input, calculate the amount of data stored base and the retention period, so that an estimate of the database size can be determined, with emphasis on performing the following tasks:

� Identify the usage for the most critical tables

– Determine if resource utilization has to be collected.

– Estimate the number of account codes to be collected in the billing summary.

– Count the data from the billing detail, which is based on the number of rates and identifiers.

– Count the lines in ident.txt that feeds directly into the identifier table.

� Identify the parameters multiplying the data sets.

– Determine the retention period in days.

– List the number of shifts for a day that needs different rate codes.

– Count the collection sources providing data.

– Estimate the number of distinct account codes.

– Estimate the number of resources used.


– Estimate the number of identifiers used.

– Estimate the Identifier mix number based upon an understanding of the collection process.

� Multiply all parameters.

� Define the point of archiving needed based on the capacity of the database system planned.

Given the customer requirements, determine which reports will be required so that a list of all reports to be designed and published has been created, with emphasis on performing the following tasks:

� Define the Invoice reports to be used.

� Define the Account reports to be used.

� Check if Top usage reports are needed.

� Check if Variance reports are required.

� Determine the use of Trend reports in the environment.

� Check for valid Resource detail reports.

� Define all other and custom reports to be used.

1.3.2 Installation

Given IBM Tivoli Usage and Accounting Manager planning has been completed, determine if the required IBM Tivoli Usage and Accounting Manager prerequisites have been met so that the installation can be executed, with emphasis on performing the following tasks:

� Check application server prerequisites, such as Microsoft Internet Information Server and .NET Framework.

� Check database and connection to IBM Tivoli Usage and Accounting Manager.

� Determine the JDBC™ jar files for the appropriate database:

– SQL database: sqljdbc.jar (From the Microsoft Web site)

– Oracle database: ojdbc14.jar (From the Oracle Web site)

– DB2 database for Linux®, UNIX®, and Windows: db2jcc.jar and db2jcc_license_cu.jar

– DB2 database for z/OS® UDB: db2jcc.jar and db2jcc_license_cisuz.jar


� Check reporting prerequisites.

– Microsoft Report Viewer application for Web reporting

– Business Intelligence and Reporting Tools (BIRT) Report Engine and Report Designer

� Confirm additional requirements with the customer.

� Check operating system requirements.

� Check Web browser requirements.

� Check hard drive space.

� Check processor speed requirement.

� Check memory requirement.

� Check supported database versions.

� Check database server system specifications.

Given that the prerequisites have been met and the implementer has the appropriate privileges, install the IBM Tivoli Usage and Accounting Manager Server according to the customer’s requirements, so that the IBM Tivoli Usage and Accounting Manager server has been installed, with emphasis on performing the following tasks:

� Obtain the software.

– Download it from the Passport Advantage® Web site.– Load the IBM Tivoli Usage and Accounting Manager Installation CD.

� Run the Enterprise Edition installation file and follow the installation wizard.

Given that the database and IBM Tivoli Usage and Accounting Manager data source have been created, initialize the database so that database has the status of being initialized, with emphasis on performing the following tasks:

� Initialize the IBM Tivoli Usage and Accounting Manager database.

� Upgrade the IBM Tivoli Usage and Accounting Manager database from previous versions.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed, install the Enterprise Collector Pack (ECP), so that ECP has been installed, with emphasis on performing the following tasks:

� Obtain the software.

– Download it from the Passport Advantage Web site.– Load the IBM Tivoli Usage and Accounting Manager installation CD.

� Run the Enterprise Collector Pack (ECP) installation file and follow the installation wizard.


Given that ECP is installed, and new processes folder is created, check the connection path for data collection, so that the collection path set for processing is set and verified, with emphasis on performing the following tasks:

� Navigate the Integrated Solutions Console (ISC) for Configuration page.

� Confirm that the correct paths in the configuration page are listed for:

– Processes– Job Files– Sample Job Files– Job Log Files– Collector Log Files

Given that the database has been initialized, run sample collector data so that the database can be populated with test collector data, with emphasis on performing the following tasks:

� Run RunSamples.bat to load sample data collection for verification.

� Check sample data collection results.

Given that the IBM Tivoli Usage and Accounting Manager installation has been performed, validate the installation so that the installation can be verified as successfully executed, with emphasis on performing the following tasks:

� Verify the database initialization.

� Verify the connection to the Web reporting URL.

� Use the result of RunSamples.bat to verify installation.

1.3.3 Configuration

Given that IBM Tivoli Usage and Accounting Manager has been installed and an account code structure has been designed with the customer, set up the account code structure using the Integrated Solution Console so that the Final Account Code hierarchy has been set, with emphasis on performing the following tasks:

� Define account code structure.

� Add account code levels’ starting offset, description, and length.

� Modify Standard account code structure.

� Create secondary or alternate account code structures.


Given that IBM Tivoli Usage and Accounting Manager server has been installed and an administrator account has been created in the Integrated Solutions Console (ISC), use the ISC to add new users, so that users can log on to Web Reports, with emphasis on performing the following tasks:

� Log on to the Integrated Solutions Console (ISC).

� Define new users.

Given that IBM Tivoli Usage and Accounting Manager server has been installed and an administrator user account has been created in the Integrated Solutions Console, add users to the ISC security group, so that the user can access the ISC, with emphasis on performing the following tasks:


� Assign user to roles.

� List existing default security roles.

� Enable security for the Embedded WebSphere Application Server.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and an administrator account has been created in the Integrated Solutions Console, add users to groups, so that the users are allowed to view only select reports, with emphasis on performing the following tasks:


� Define a new user group.

� Add a user to the user group.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured, use the ISC to set up the calendar, with emphasis on performing the following tasks:


� Define a calendar for a particular year.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and a configured, use the ISC to add clients to the client table so that the client table has been updated, with emphasis on performing the following tasks:


� Remove sample clients before adding clients to the customer’s organization.

� Add new client organization.


Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured, and the clients have been added, add the client budgets to the corresponding client, so that the client budgets have been created, with emphasis on performing the following tasks:


� Assign a new budget to a client.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured and clients have been added, add the client contacts to the client, so that the client has been updated, with emphasis on performing the following tasks:


� Add client that needs to be added as a contact or contacts need to be added to it.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured, create a new rate group using the ISC, with emphasis on performing the following tasks:


� Define a new rate group.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and a configured and rate groups have been added, add rate codes using the ISC, so that new rate codes are available, with emphasis on performing the following tasks:


� Define a new rate code.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured and rate groups have been created, add an alternate table so that alternate rates are available, with emphasis on performing the following tasks:


� Define new rate table

Given that IBM Tivoli Usage and Accounting Manager server has been installed and configured, create a proration table so that a proration table is available, with emphasis on performing the following tasks:


� Define a proration table for a rate code.


� Use prorate for collecting usage data for a rate code.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured, using the ISC, configure CPU normalization so that CPU Normalization has been set up, with emphasis on performing the following tasks:


� Use CPU normalization in Job files.

� Define the CPU normalization percentage.

� Select the rate codes to be normalized.

Given that the IBM Tivoli Usage and Accounting Manager server has been installed and configured, use the ISC to set rate shifts so that the rate shifts have been set to meet the customer’s requirements, with emphasis on performing the following tasks:


� Define rate shifts.

1.3.4 Administration

Given the connection data, navigate to the IBM Tivoli Usage and Accounting Manager menu so that the user can perform administration tasks in the ISC IBM Tivoli Usage and Accounting Manager environment, with emphasis on performing the following tasks:

� Connect to the Integrated Solution Console using a Web browser.


� Find the appropriate menu options in the portfolio navigation bar.

Given the current environment data, the administrator can perform tasks to optimize the IBM Tivoli Usage and Accounting Manager environment so that the IBM Tivoli Usage and Accounting Manager environment will run faster, with emphasis on performing the following tasks:

� Determine the current database usage.

� Plan runstats on a regular basis.

� List long running reports.

� Determine the tables and columns used for sorting.

� Define indices on heavy used columns.


� Determine the memory usage of the WebSphere Application Server. Add physical memory if it is needed.

� Determine the CPU load.

� Add virtual or logical CPUs for parallel processing.

� For hardware limitations, evaluate the separation of the database and application servers, but keep the network limitations in mind.

Given the Feed source name, set up load tracking so that the list of loaded data can be filtered to get an overview of specific data loads for selected jobs, with emphasis on performing the following tasks:


� Work with Load Tracking information.

� Perform filtering on the Load Tracking information for searching a collection.

Given the access permissions and IBM Tivoli Usage and Accounting Manager location, stop and start the application server so that all updates implemented will be activated in the files systems for further usage, with emphasis on performing the following tasks:

� Restart the procedure for the user interface.

� Verify application availability.

1.3.5 Job creation

Given the parameters of data sources, use the XML job file language to generate a job so that the data is incorporated into the IBM Tivoli Usage and Accounting Manager process file structure and database, with emphasis on performing the following tasks:

� Determine that sample job files that best suits the task.

� Copy the sample job file to the job file directory.

� Define or modify the integrator step for data input and processing.

� Run the job file validation to ensure that the syntax is correct.

� Before activating or adding any further steps, run the job and check the logs and the CSR file for correct content.


Given input data source and manipulation instructions, create a setup where the job(s) will prepare the data, do account conversion, process billing, and finally load data so that reports are ready to be run, with emphasis on performing the following tasks:

� Determine the sample job files that best suits the task.

� Copy the sample job file to the job file directory.

� Split the processing into more than one job for better handling.

� Create and modify process steps as needed.

– Create integrator steps for reading data and performing data manipulations.

– Set up resource conversion to recalculate values.

– Define the parameters of the billing step.

– Verify that the db load step is correct.

– Define the cleanup step parameters to clear old files from the process directory.

� Verify the job file.

– Ensure that the syntax is correct.

– Verify the operation without database loading.

– Check the actual load for errors and warnings.

– Verify that the data is loaded using the LoadTracking function.

� Run a report to verify that data is loaded correctly.

Given a raw data file or other data source and manipulation instructions, set up the integrator step to recalculate, aggregate, or manipulate the resources and filter for identifiers so that a CSR file is prepared for further processing, with emphasis on performing the following tasks:

� Define the input section of an integrator step. Use Input, Files, or Collector directives.

� Add integrator stages to create, delete, or modify identifiers and do calculation on resources.

– Create an aggregator for combining data for one identifier or for a time frame.

– Create new resources or identifiers.

– Do not use drop fields, as they are not needed.

– Exclude or include data by any criteria.

– Do a ResourceConversion for recalculating resource values.


– Sort CSR data for output.

� Define an output stage to create a CSR or CSR+ file.

Given identifiers and the account code table, use the integrator step to add an account code field mapping to determine who is using which resources, so that an account code conversion has been executed, with emphasis on performing the following tasks:

� Define the integrator step before billing and DBload.

� Use the integrator function CreateIdentifierFromTable to add an Account_Code identifier.

� Perform additional necessary conversions, such as an Aggregator stage.

1.3.6 Problem determination

Given a validated job that does not execute successfully, review the corresponding log file to locate the error and resolve it so that the job can execute successfully, with emphasis on performing the following tasks:

� Execute a jobfile using either a job scheduler or manually through the Integrated Solutions Console.

� Check the job execution status using the Integrated Solutions Console.

� Read output messages for that job file execution.

� Find steps that are unsuccessful.

� Find error message for the unsuccessful step.

� Correct job errors and rerun the job.

Given a validated jobfile that completes with a warning, review the corresponding log file to locate the error and resolve it so that the job can execute successfully, with emphasis on performing the following tasks:

� Execute the jobfile using either a job scheduler or manually through the Integrated Solutions Console.

� Check the job execution status using the Integrated Solutions Console.

� Read output messages for that job file execution.

� Find steps that have warning messages.

� Check warning message for the step.

� Correct job warnings and rerun the job.

� Determine rate code warning actions and whether to define the rate or ignore it.


Given that within ISC the database connection fails, diagnose the issue so that the database connection can be reestablished, with emphasis on performing the following tasks:

� Review the current trace and message log records.

� Use the database management interface to check the database’s status.

� Ensure that the user ID and password used by IBM Tivoli Usage and Accounting Manager to connect is correct.

Given that Web reporting is implemented and a report is timing out, review report values in the ISC and determine if the network connection is sufficient so that the issue can be identified, with emphasis on performing the following tasks:

� Set the Web reporting interface timeout value.

� Limit date selection for report execution.

� Set up batch reporting for reporting.

Given IBM Tivoli Usage and Accounting Manager is operational, define the default file names produced by process engines so that the names and their purposes are understood, with emphasis on performing the following tasks:

� Identify the default output file for the Scan program.

� Identify files for the Acct program, output file, and exception files.

� Identify files for the Bill program, identifier file, billing detail, and billing summary files.

Given that the client wants to adjust the amount of information in the trace file, modify the detail level written out so that the message and trace logs provide the level of detail that the client requires, with emphasis on performing the following tasks:

� Set the logging configuration from the Integrated Solutions Console.

� Set the Trace file setting. The Trace message level can be set to FINE, FINER, or FINEST.

� Set the Log file setting. The Log message level can be set to SEVERE, WARNING, or INFORMATION.


1.3.7 Reporting

Given the need to produce an invoice or analyze billing or usage data, generate an IBM Tivoli Usage and Accounting Manager report according to the customer’s requirement so that billing or usage data can be loaded into a spreadsheet for analysis or invoices can be produced, with emphasis on performing the following tasks:

� Log in to the reporting Web application.

� Understand the report types in the Report list.

� Run spreadsheets for standard or crosstab types.

� Supply the desired report parameters.

Given requirements to produce a report, define parameters so that the output satisfies the requirements. Given the requirement to produce a new report, define a new IBM Tivoli Usage and Accounting Manager report according to the new requirement so that a new report or spreadsheet can be generated, with emphasis on performing the following tasks:

� Log on to the reporting Web application.

� Select a new report type.

� Define the new report arguments.

� Save the new report or new spreadsheet.

Given the need to manage the reporting Web interface, create and assign a role and remove the user used to access the reporting Web interface, and modify the security scheme for the Web interface so that appropriate users can access the reporting Web interface with the appropriate access, with emphasis on performing the following tasks:

� Define user access restriction.

� Define new user groups without administrative access.

� Activate report access security.

� Assign a report for user groups:


1.4 Recommended study resources

Courses and publications are offered to help you prepare for the certification tests. The courses are recommended, but not required, before taking a certification test. If you wish to purchase Web-based training courses or are unable to locate a Web-based course or classroom course at the time and location you desire, please feel free to contact one of our delivery management teams at:

� Americas: [email protected]

� EMEA: [email protected]

� AP: [email protected]

Note that course offerings are continuously being added and updated. If you do not see the course(s) listed in your geography, please contact the delivery management team.

1.4.1 IBM Redbooks

The following IBM Redbooks can be used as additional information sources:

� IBM Tivoli Usage Accounting Manager V7.1 Handbook, SG24-7404

Financial management of IT resources allows an IT department to be transformed from a cost center to a service provider. One aspect of this is usage accounting, which helps the IT department understand the usage patterns of its customers or users and allows for service charges that reflect that usage. In addition, usage data demonstrates how IT operations can be optimized to increasing efficiency.

Tivoli Usage and Accounting Manager provides the tools to perform data collection and accounting for IT-related usage from various sources. It even allows the custom integration of data from nonstandard format sources. It supports the whole life cycle of financial management from budgeting to usage accounting and billing, and reporting. This book will help you understand, install, configure, and use the new IBM Tivoli Usage and Accounting Manager V7.1.

The book starts with an overview of Tivoli Usage and Accounting Manager concepts and capabilities along with the structure of the product. The installation and verification of each component is presented in detail. Sample scenarios are executed and explained, including operating system usage collection, virtual environment collection (VMware® ESX server and IBM System p® partitioning), and Tivoli Decision Support for z/OS interface.


� Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1, SG24-7569

This book is part of the Deployment Guide series. It provides a step-by-step guide for deploying Tivoli Usage and Accounting Manager V7.1. It is intended to help an IBM or Business Partner service person plan and perform the deployment of the product.

The discussion of Tivoli Usage and Accounting Manager includes an explanation of its architecture and components. Some planning and sizing considerations before you implement the product are given, and some guidelines on setting up service engagement for the product are also included.

The deployment discussed in the book would be appropriate for a demonstration or a small deployment system, although the information is highly relevant for larger deployments also. This book also offers some usage scenarios that can be used for demonstrating the product.


Chapter 2. Planning

This chapter discusses planning of the implementation of IBM Tivoli Usage and Accounting Manager V7.1. The discussion consists of the following:

� 2.1, “Planning the implementation” on page 26

� 2.2, “Account code structure” on page 27

� 2.3, “Collector selection” on page 29

� 2.4, “Implementation platform” on page 31

� 2.5, “Database sizing” on page 32

� 2.6, “Report requirements” on page 38

2


2.1 Planning the implementation

There are several important preparations that must be performed before implementing IBM Tivoli Usage and Accounting Manager. The solution must be clearly understood by the implementation team. The solution is typically described in a design document.

The design document takes its input from the client’s requirements and match them to the capability of the product. The IBM Tivoli Usage and Accounting Manager implementation design document should consist of the necessary details about how the implementation should be performed. It should contain the following design items:

� Customer requirements in a workshop to show the critical path.

– Understand the financial system of the customer.

– Define the account code structure that most closely fits the near future plans for the customer environment.

– Select the key parameters needed for accounting (limit them to a suitable minimum for the pilot).

� A project plan for the IBM Tivoli Usage and Accounting Manager setup actions to be done.

– Identify the data sources, identifiers, and rates to be used.

– List the default collectors to be used and new collectors to be written.

– Estimate the size of the database to be expected.

� A definition about how to perform these available system management functions.

– Determine the method of scheduling jobs.

– Define the data transfer solution to be implemented.

– Determine the monitoring solution to be used for the environment.

� Describe the network architecture of the implementation. This includes the platform selection and connectivity requirements.

� Explain the reporting method needed and report requirements as dictated by customer.

� Determine the licenses held or to be bought by the customer.

We discuss some of the important aspect of this design document in more detail in the subsequent sections.


2.2 Account code structure

One of the most important aspects of planning is to decide on the account code structure. The account code structure determines the charging hierarchy of the target enterprise. All collected data must be mapped to the correct structure based on the defined account code structure.

The account code structure must be defined early in the implementation because:

� It determines how to map the identifier to the account code.

� Account code granularity strongly influences database size calculation.

� Reporting and billing are all based on the account code structure.

� Changing the account code structure and mapping invalidates all the data that has been collected in IBM Tivoli Usage and Accounting Manager.

The charging hierarchy must match the enterprise’s financial and business accounting practices. It may have additional detail levels than the hierarchies needed by accounting.

In Table 2-1, we use the department name as the top level. There are one or more department numbers possible for each department and the hosts are grouped by an application perspective. The billing requirement may only need to distinguish the department name and number, but usage monitoring may need the application and host information if they are available.

Table 2-1 Account code for a department organization

Description Length

Department (short name) 8

Department number 6

Application 8

Host 32

Chapter 2. Planning 27

For a multi-customer environment, the customer name is the top level. We define two additional levels in case the customer needs separated bills or rates for his projects and splitting up of follow-up contracts. See Table 2-2.

Table 2-2 Account code for a multi customer environment

Account codes are mapped from identifiers. The mapping can be performed by parsing the identifier to extract the appropriate levels or using a lookup table for mapping the identifier to the account code. You must identify the appropriate mapping process for each type of collected data. Mapping for UNIX servers may be based on process name and path, while mapping for Windows client machines may be based on IP address or host name.

The lookup tables have to be maintained for currency. Processes must be in place to ensure proper updating of the tables is performed. The table can be based on database tables that have to be extracted regularly or from a static text that must be maintained by an administrator.

More about account code usage is discussed in 4.2, “Account code hierarchy” on page 82.

Description Length

Customer (short name) 8

Master contract number 12

Service contract number 12

Application 8

Host 32

Tip: Changing the account code structure make processed data invalid, as it is based on different account code fields. You must plan the structure carefully before you start processing data.


2.3 Collector selection

We must determine if the required collectors are available and supported for the proposed environment. Some collectors run as a Windows Script File (WSF) and must run on a processing server on Windows-based platforms.

The existing collectors for IBM Tivoli Usage and Accounting Manager V7.1 are:

� AIXAAInput: AIX® Advanced Accounting for a logically partitioned IBM System p installation that includes support for AIX 5L™ V5.3 or later, AIX V6, and the Virtual I/O (VIO) server.

� Base UNIX collector: The UNIX collector runs on most UNIX platforms using the built-in accounting (acct) features.

� CSRInput: Input with Common Source Format. This is typically an output from the Tivoli Usage and Accounting Manager data collector or previous processing from Tivoli Usage and Accounting Manager.

� IBM System i: Only available for Tivoli Usage and Accounting Manager on Windows, as a Windows script file. Data is collected from i/OS V5.1.

� TDSz: Extracting data from Tivoli Decision Support for z/OS database (DRLDB).

� Transaction: A transaction is a mechanism to adjust data in IBM Tivoli Usage and Accounting Manager. This collector gets the input from a table within the Tivoli Usage and Accounting Manager database, and adds one time charges and monthly fixed charges to the accounts based on the input from ISC.

� z/VM®: This collects data from the z/VM environment, including connect time, CPU time, virtual SIOs, virtual cards read, virtual lines printed, virtual cards punched, and temporary disk space.

� VMware: This can pull data from either the VMware Virtual Center Server or directly from VMware ESX servers using the VMware SDK Web interface.

� Windows Disk Data: This program runs on the Windows server every time you want to have a snapshot of disk usage.

� Windows Process collector: A service that is installed and run in a Windows environment to collect data on processor usage. This collector uses Windows Script File processing.


� Universal data collector is a converter function to convert data into CSR or CSR+ format. The input can be from:

DATABASE Databases providing a SQL interface. The source must be defined as a data source.

DELIMITED Delimited files, such as comma separated values (CSV).

FIXEDFIELD Fixed field files.

Additional data collectors are available with IBM Tivoli Usage and Accounting Manager V7.1 Enterprise Collector Pack, which are:

� ApacheCommonLogFormat: Apache HTTP server common log collection for analyzing Web page hit counts.

� DB2: Collects DB2 database accounting in Windows, UNIX, and Linux.

� DBSpace: Collects the size of a Microsoft SQL or Sybase database only. This collector uses Windows Script File.

� Lotus® Notes®: Gathers data directly from Notes database files log.nsf, loga4.nsf, and catalog.nsf, such as NotesDatabaseSizeInput, NotesEmailInput, and NotesUsageInput.

� Microsoft Exchange: Based on the different logs for the Exchange server, usage data and mailbox size are collected. This collector uses Windows Script File.

� Microsoft Internet Information Services (IIS): The W3C Extended Log from IIS can be retrieved for processing. This collector uses Windows Script File.

� Microsoft SQL server: Uses the trace log and direct database access to get usage data from SQL server. This collector uses Windows Script File.

� Oracle: Uses the event log and direct database access to get usage data from Oracle server.

� SAP®: SAP Transaction Profile report (ST03N) is used for collecting from SAP. ST03N is a specific transaction in SAP that provides performance and workload analysis data.

� Tivoli Storage Manager: Uses Tivoli Storage Manager ODBC calls (Windows only, but other versions can be requested).

� TotalStorage® Productivity Center (TPC): A flexible data collector to collect any data from the TPC log files.

Note: IBM Tivoli Usage and Accounting Manager V7.1.1 supports an additional data collector for Tivoli Data Warehouse from IBM Tivoli Monitoring.


� WebSphere: A variety of WebSphere usage metrics can be collected and processed.

� Windows Event Log data collector for print: Gets usage data from a Windows print server extracted from the event log.

2.4 Implementation platform

Based on the design document and the required collectors, you must choose the implementation platform. There are some differences about the platform usage and parameters. You must check for the following:

� Skill of existing operation personnel on:

– Operating system platform.

– Database platform.

� Reporting solution:

– Windows uses Internet Information Server for Web reporting.

– UNIX/Linux uses Business Intelligence and Reporting Tools (BIRT).

� Evaluate some platform dependent options:

– Financial Modeler is only supported in Windows.

– Windows Script File collector is only supported in Windows. The collectors that use WSF are:

• WinProc • DBSpace• MSIIS• MSSQL• MSExchangeMbx• SystemIr52/SystemIr51

� Solution sizing, that is, whether the application parts run on a single or multiple machines. You must consider application scalability for future processing.

– Database size (refer to 2.5, “Database sizing” on page 32).

– Processing or collection runs. The recommended minimum is 3 GHz.

– Memory requirement for reporting and administration application. The minimum recommendation is 2 GB.


2.5 Database sizing

Sizing the IBM Tivoli Usage and Accounting Manager database is critical for the implementation process. Adequate allocation for the database ensures the sustainability of the solution so it can perform in a satisfactory manner. The IBM Tivoli Usage and Accounting Manager manual recommends 40 GB of available hard drive space.

Once the database is initialized, the base database would be more or less constant in size. Additional grouping, users, and reporting changes can happen, but the size would not be significant. The total size of an empty IBM Tivoli Usage and Accounting Manager database is less than 0.5 MB.

The primary contributor to the growth of a an IBM Tivoli Usage and Accounting Manager database is the data loaded from the output of the billing process. The size of the IBM Tivoli Usage and Accounting Manager database is dependent on many different parameters. The database is populated based on the database load process of the processing engine (refer to 6.1.2, “Generic processing overview” on page 112). The database load gets its input from the billing program. It loads data from the following files:

� BillDetail.txt: Billing detail data. This data is loaded into the CIMSDETAIL table.

� BillSummary.txt: Billing summary data. This data is loaded into the CIMSSUMMARY table.

� Ident.txt: The list of identifiers. This data is loaded into the CIMSDETAILIDENT table.

� Optionally, resource utilization data can be loaded into the CIMSRESOURCEUTILIZATION table.

Additional growth can be added to the load tracking information that records each of the data sources being loaded and processed. The load tracking information is stored in the CIMSLOADTRACKING table.

The size of these tables also relates directly to information in messages from the Database Load step. In Example 2-1 on page 33, we see the number of records (rows) added to the three tables as a result of processing the 65 CSR records.


Example 2-1 Database Load messages extract

06:37:14.852: INFORMATION Summary Load: Load Started06:37:14.938: INFORMATION Loaded Records: 9706:37:14.941: INFORMATION Summary Load: Load Completed Successfully06:37:14.943: INFORMATION Detail Load: Load Started06:37:15.524: INFORMATION Loaded Records: 65 Resources 25706:37:15.524: INFORMATION Detail Load: Load Completed Successfully06:37:15.528: INFORMATION Ident Load: Started06:37:15.596: INFORMATION Loaded Records: 35206:37:15.605: INFORMATION Ident Load: Load Completed Successfully06:37:15.610: INFORMATION Number of Detail Records Loaded: 25706:37:15.610: INFORMATION Number of Ident Records Loaded: 35206:37:15.610: INFORMATION Number of Summary Records Loaded: 9706:37:15.610: INFORMATION DBLoad Completed Successfully

You should also consider any necessary archiving, based on the capacity of the database system planned. Let us look at the individual tables in these sections:

� 2.5.1, “CIMSLOADTRACKING” on page 34� 2.5.2, “CIMSSUMMARY” on page 35� 2.5.3, “CIMSDETAIL and CIMSDETAILIDENT” on page 36� 2.5.4, “CIMSRESOURCEUTILIZATION” on page 37

Note: The number of rows loaded can be reduced when the source AcctCSR.dat file is sorted by account code before doing the bill processing. This sorting can be facilitated when you are using the AcctCSR+ format.


2.5.1 CIMSLOADTRACKING

The load tracking table structure is shown in Figure 2-1.

Figure 2-1 Load tracking table

You can estimate the row size using the following assumptions:

� All nullable columns add 1 byte. Some of the rows that are null may not have any length.

� All variable columns have 2 bytes for length.

� Graphic data types uses 2 bytes for each character.

� Time stamp columns have a length of 8 bytes.

� Integer columns have a length of 4 bytes.

The Load Tracking table contains three or four rows of data for each one of the data source collection types, depending on whether resource utilization information is collected. The size growth can be estimated from how may database load jobs would be run each day. This may be the same as the number of collection sources if each source is collected once a day.

Once you have performed some collections, this load tracking can be a good indicator in further estimating the database size. The CIMSLOADTRACKING table contains the column TOTALRECSLOADED, which can indicate the growth of the tables.


2.5.2 CIMSSUMMARY

The CIMSSUMMARY table has the structure shown in Figure 2-2.

Figure 2-2 CIMSSUMMARY table

The CIMSSUMMARY table has a row for each rate and account code combination for that billing cycle and shift. This summary table can be qualified with multiple billing flags.

To estimate the size of the CIMSSUMMARY table, we must consider the following items for each data collection:

� How many rate codes for which we are collecting� How many distinct account codes would be collected for those rate codes� How many shifts for which we are collecting


All of these items are multiplied together to provide the number of rows for the CIMSSUMMARY table.

2.5.3 CIMSDETAIL and CIMSDETAILIDENT

The CIMSDETAIL table is shown in Figure 2-3.

Figure 2-3 CIMSDETAIL table

The CIMSDETAILIDENT table is shown in Figure 2-4.

Figure 2-4 CIMSDETAILIDENT table

This CIMSDETAIL table contains a row for each rate code and each unique identifiers combination. The identifiers are listed separately in the CIMSDETAILIDENT table.


The size of the CIMSDETAIL table would be determined from:

� The number of rate codes collected for each collection� The number of different identifier combinations for each rate code� How many shift for which we are collecting

The CIMSDETAILIDENT table can be calculated from each row of the CIMSDETAIL table and multiplied with the number of qualifying identifiers for the CIMSDETAIL row.

2.5.4 CIMSRESOURCEUTILIZATION

The CIMSRESOURCEUTILIZATION table’s structure is shown in Figure 2-5.

Figure 2-5 CIMSRESOURCEUTILIZATION table

The CIMSRESOURCEUTILIZATION table data, if collected, would contain similar content to the CIMSDETAIL table data. The difference is that this would not contain billing information and no CPU normalization is performed. The estimate for the CIMSRESOURCEUTILIZATION table data is the same as the CIMSDETAIL table data.

The CIMSRESOURCEUTILIZATION table data is collected from the Resource.txt file. This file is produced only when the bill’s resourceFile attribute is provided in the job file, and is loaded into the database only when the DBLoad’s loadType attribute is set to Resource in the job file.


2.6 Report requirements

There are several predefined reports that IBM Tivoli Usage and Accounting Manager uses. You must identify the reports that will be used in the implementation. There are several categories of reports that may be needed:

� Invoice reports, which are actually usage invoices that can be billed to the service consumer. The format and content of the invoices must be defined and prepared in the implementation stage. IBM Tivoli Usage and Accounting Manager provides some sample invoice reports. Figure 2-6 shows a sample invoice.

Figure 2-6 Invoice report

� Account reports, which contain usage information that specifies the customer accounts against the usage items. The account reports do not include rate conversion. A typical account report is given in a cross-table format, as shown in Figure 2-7 on page 39.


Figure 2-7 A sample report on daily usage data

� Other reports may be generated based on the needs of the IT department and consumers. Some typical reports are:

– Top usage reports for highlighting the top users of a certain rate

– Variance reports for showing usage anomalies from consumers and identifying usage patterns

– Trend reports for finding and predicting capacity requirements

– Resource detail reports for analyzing resource usage


Chapter 3. Installation

This chapter discusses the installation of IBM Tivoli Usage and Accounting Manager V7.1. The discussion is covered in the following sections:

� 3.1, “Installation overview” on page 42

� 3.2, “Installation prerequisites” on page 43

� 3.3, “Application server installation” on page 54

� 3.4, “Database configuration” on page 59

� 3.5, “Enterprise Collector Pack implementation” on page 67

� 3.6, “Initial configuration” on page 70

� 3.7, “Installation verification” on page 71

� 3.8, “Sample collection verification” on page 75

3


3.1 Installation overview

The description of the installation in this chapter is performed in a single server environment. The deployment is performed on machines loaded with Windows 2003 Standard Edition with Service Pack 1, as shown in Figure 3-1.

Figure 3-1 Installation environment

The steps are:

1. Database installation and creation, as discussed in 3.4, “Database configuration” on page 59.

2. Microsoft Internet Information Server, Microsoft .NET framework, and Microsoft Report Viewer are needed for the Web reporting application, and are discussed in 3.2, “Installation prerequisites” on page 43.

3. IBM Tivoli Usage and Accounting Manager Enterprise Edition server, which includes an embedded WebSphere Application Server and Integrated Solution Console application, is installed, as shown in 3.3, “Application server installation” on page 54.

4. The supported collectors are installed in a bundle called the Enterprise Collector Pack, as discussed in 3.5, “Enterprise Collector Pack implementation” on page 67.

5. Some setup of the IBM Tivoli Usage and Accounting Manager application using the Integrated Solution Console is needed, as discussed in 3.7, “Installation verification” on page 71.

z

tuamsrv

DB2 UDB 9.1Usage Accounting Manager 7.1 EE

Embedded WebSphere Application Server 6.1Integrated Solution Console

Usage Accounting Manager 7.1 ECPUsage Accounting Manager 7.1 WPC

twin01

Windows Process Collector

twin02

Windows Process Collector


3.2 Installation prerequisites

We install the server on a Windows 2003 Server system (system SRV177, in our example). Prior to installing IBM Tivoli Usage and Accounting Manager, several prerequisites are required:

� Microsoft Internet Information Services (IIS) is required for the execution of the reporting application of IBM Tivoli Usage and Accounting Manager. See 3.2.2, “Configuring Microsoft Internet Information Services” on page 45.

� A current version of the Microsoft Installer package. We install MSI30-KB884016. If you are already running Microsoft Windows 2003 Service Pack 1, you do not need this package. See 3.2.3, “Install the Microsoft Installer” on page 49.

� Microsoft .NET Framework Redistributable 2.0 is required for installing the Microsoft Report Viewer. See 3.2.4, “Install Microsoft .NET Framework 2.0” on page 51.

� Microsoft Report Viewer Redistributable 2005 is required for the standard Usage and Accounting Manager reports. See 3.2.5, “Install Microsoft SQL Server Report Viewer” on page 52.

3.2.1 Platform requirements

The following are the platform hardware, operating system and middleware requirements for the IBM Tivoli Usage and Accounting Manager application server.

� Operating system.

– Windows Server® 2003 x64 or x86

– Windows Server 2008 x86

– Linux and UNIX server platforms

– AIX 5L V5.3 and V6.1

– Solaris™ 9 and 10

– HP-UX 11.23 and 11.31 on the pa-RISC platform

– Red Hat Enterprise Linux (RHEL) 4 and 5 for IA32

– RHEL 4 and 5 for PowerPC®

– RHEL 4 and 5 (64-bit) for IBM System z®

– RHEL 4 and 5 for x64 (AMD64/EM64T)

– SUSE® Linux Enterprise Server (SLES) 9 and 10 for IA-32

Chapter 3. Installation 43

– SLES 9 and 10 for PowerPC

– SLES 9 (31-bit and 64-bit) for System z

– SLES 10 (64-bit) for System z

– SLES 9 and 10 for x64 (AMD64/EM64T)

� Web browser requirements.

– Internet Explorer® 6 or 7

– Firefox 2

� Hard drive space: 0.5 GB minimum, 40 GB recommended available hard drive space. The hard drive space requirements for the organization might vary.

� Processor speed: 3 GHz minimum.

� Memory: 2 GB minimum.

� Databases supported.

– DB2 Universal Database™ (UDB) for Linux, UNIX, and Windows Version 8.1, 8.2, 9.1, or 9.5

– DB2 UDB for z/OS Version 8

– Microsoft SQL Server 2000 or 2005 with the latest service pack

– Oracle 9 or 10 for UNIX or Windows

� Database server system specifications.

– 80 GB minimum available hard drive space.

– 3 GHz or faster processor (multi-processors are helpful)

– 2 GB minimum of memory

� Database and connection to IBM Tivoli Usage and Accounting Manager: Determine with customer/DBA if jar file downloaded.

– SQL database: sqljdbc.jar (From MS® Web site)

– Oracle database: ojdbc14.jar (From Oracle Web site)

– DB2 database for Linux, UNIX, Windows: db2jcc.jar and db2jcc_license_cu.jar

– DB2 database for z/OS UDB: db2jcc.jar and db2jcc_license_cisuz.jar


3.2.2 Configuring Microsoft Internet Information Services

This section discusses setting up Microsoft Internet Information Services using the Manage Your Server application.

Do these steps:

1. The program can be started by selecting All Programs → Administrative Tools → Manage Your Server. The window shown in Figure 3-2 will appear.

Figure 3-2 Manage your server


2. Click the Add or remove a role link and the Configure Your Server Wizard will start, as shown in Figure 3-3.

Figure 3-3 Configure server wizard

3. In the Configuration Options window shown in Figure 3-4 on page 47, select Custom configuration.


Figure 3-4 Configuration selection

4. In Figure 3-5, select the Application Server role and click Next.

Figure 3-5 Server role selection


5. In Figure 3-6, check the Enable ASP.NET check box and click Next.

Figure 3-6 Feature selection

6. The installation commences with a progress bar. Figure 3-7 shows that the installation is finished.

Figure 3-7 Installation completed


3.2.3 Install the Microsoft Installer

An up to date version of the Windows Installer software needs to be available on the Report server system. Do these steps:

1. Download the Windows Installer from:

http://www.microsoft.com/downloads/details.aspx?FamilyID=5fbc5470-b259-4733-a914-a956122e08e8&DisplayLang=en

2. We execute the program WindowsInstaller-KB884016-v2-x86.exe to run the installation of the Windows Installer. The Welcome window is displayed (Figure 3-8.) Select Next.

Figure 3-8 Welcome window for the Windows Installer installation

Note: Our Windows 2003 SP1environment (Windows 2003 SP1 is required by DB2 V9.1) does not need the installation of Microsoft Installer. However, we also notice that the .NET Framework 2.0 requires this installation.


http://www.microsoft.com/downloads/details.aspx?FamilyID=5fbc5470-b259-4733-a914-a956122e08e8&DisplayLang=en

3. Agree to the license shown in Figure 3-9 and select Next.

Figure 3-9 License agreement for the Windows Installer

4. Selected files on your system are backed up. The Windows Installer is installed and the completion window is shown (Figure 3-10). Select Finish to end the installation.

Figure 3-10 Completion of the installation for the Windows Installer software


3.2.4 Install Microsoft .NET Framework 2.0

The .NET Framework is required if you install Microsoft Report Viewer to view the standard IBM Tivoli Usage and Accounting Manager reports in RDL format. Do these steps:

1. Download the installation package for the Report Viewer from the following address:

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&DisplayLang=en

2. Execute the downloaded program to start the installation and select Next in the Welcome window. Accept the license agreement and select Install, as shown in Figure 3-11. The installation progress window is displayed.

Figure 3-11 Accept the .NET license agreement and start the installation




3. The Setup Complete message is displayed when the installation completes (Figure 3-12.) Select Finish to end the installation.

Figure 3-12 Setup complete for the .NET framework software

3.2.5 Install Microsoft SQL Server Report Viewer

The Microsoft Report Viewer is required for the standard IBM Tivoli Usage and Accounting Manager reports (RDL format). Do these steps:

1. Download the installation package for the Report Viewer from the following address:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8a166cac-758d-45c8-b637-dd7726e61367

2. Save the downloaded file as ReportViewer.exe.

3. Execute ReportViewer.exe to install the Report Viewer. The Welcome window is displayed (Figure 3-13 on page 53). Select Next.




Figure 3-13 Welcome window for the Report Viewer installation

4. Accept the license agreement and select Install, as shown in Figure 3-14.

Figure 3-14 License agreement for the Report Viewer and installing the software


5. Once successfully installed, the Setup Complete window is displayed, as shown in Figure 3-15. Select Finish to end the installation.

Figure 3-15 Successful installation of the Report Viewer

3.3 Application server installation

Install the reporting server using the IBM Tivoli Usage and Accounting Manager enterprise edition Windows installation package. This installation package contains the reporting server as well as the IBM Tivoli Usage and Accounting Manager Application server software, the ISC, embedded WebSphere Application Server, and the DB2 Universal Database V9.1 runtime client.

IBM Tivoli Usage and Accounting Manager Enterprise Edition can be downloaded from the Passport Advantage Web site.

Make sure that you have the Microsoft Internet Information Server installed and active.

All the following files must exists in the same directory:

� EmbeddedExpress_wintel_ia32.zip� ISCAE71_4_EWASv61.zip� setup-tuam-ee-7-1-0-wintel_ia32.exe� setup-tuam-wpc-7-1-0-windows_32_64.exe� v9fp2_ALL_LANG_setup_32.exe


Do the following installation steps:

1. Execute setup-tuam-ee-7-1-0-wintel_ia32.exe to install the Report server. Select Next at the Welcome window. Accept the license agreement and select Next, as shown in Figure 3-16.

Figure 3-16 License agreement for IBM Tivoli Usage and Accounting Manager


2. We install the application server into the C:\IBM\tuam\ directory, as shown in Figure 3-17; the default directory is C:\Program Files\ibm\tuam. Select Next.

Figure 3-17 Define the installation directory for the Report server software

3. Check the Windows Web Reporting option, as shown in Figure 3-18. Select Next.

Figure 3-18 Select the windows Web Reporting option


4. We choose the virtual directory option, as shown in figure Figure 3-19, and select Next.

Figure 3-19 Select a new virtual directory for Web reports

5. Select Install in the summary information window. The installation progress indicator is displayed.


6. A task is automatically initiated to unpack the installed files, as shown in Figure 3-20.

Figure 3-20 Unpacking of the application server software on the Report server

7. The window shown in Figure 3-21 shows successful completion of the installation and the summary information. Select Finish to end the installation.

Figure 3-21 Successful installation of the Report server software


3.4 Database configuration

There are several initial configurations that you need to do before you can use IBM Tivoli Usage and Accounting Manager. These can be done from the Integrated Solution Console. Figure 3-22 shows the console welcome window.

Figure 3-22 Welcome page

This section explains the following:

� 3.4.1, “Database creation” on page 59� 3.4.2, “Defining JDBC driver” on page 60� 3.4.3, “Defining data sources” on page 63� 3.4.4, “Initializing database” on page 66

3.4.1 Database creation

The database (in Windows) must be defined as UTF-8. The definition of the default page size of 16 K allows us to have an overall 16 K page size. For a production environment, we recommend using the default 4 K page size and creating an additional definition of a buffer and table spaces for larger page sizes, such as 16 K.


Figure 3-23 shows the creation of the database.

Figure 3-23 Creating the database and bufferpools

3.4.2 Defining JDBC driver

The configuration of the JDBC driver for IBM Tivoli Usage and Accounting Manager depends on the database software that has been installed. The DB2 Universal Database that we use comes with the JDBC drivers. We use the db2jcc.jar and db2jcc_license_cu.jar files for the JDBC driver. The following steps configure IBM Tivoli Usage and Accounting Manager to use the JDBC driver:

1. From the ISC menu, select Usage and Accounting Manager → System Maintenance → Configuration. See Figure 3-24.

Figure 3-24 Configuring the JDBC driver

C:\>DB2 CREATE DB ITUAMDB CODESET UTF-8 PAGESIZE 16 KDB20000I The CREATE DATABASE command completed successfully.


2. In the Driver tab, click New to define the driver. Find the driver file in the tree shown in Figure 3-25. Click OK when you are done.

Figure 3-25 Finding the JDBC driver


3. The JDBC jar files are shown in Figure 3-26. Click OK when you are done.

Figure 3-26 JDBC driver

4. Figure 3-27 on page 63 shows the final JDBC driver configuration in our system.


Figure 3-27 Final JDBC driver configuration

5. After updating the JDBC driver, you should restart the Integrated Solution Console. Use the following commands:

C:\IBM\tuam\ewas\bin\stopServer.bat server1C:\IBM\tuam\ewas\bin\startServer.bat server1

3.4.3 Defining data sources

Once you have a definition of the JDBC drivers, we can define the data sources. Using the ISC, you add the data source. We add the IBM Tivoli Usage and Accounting Manager database as a Server data source as follows:

1. From the ISC menu, select Usage and Accounting Manager → System Maintenance → Data Sources.


2. In the data source window, right-click the default data source and select Edit DataSource. See Figure 3-28.

Figure 3-28 Editing the default data source

3. Figure 3-29 on page 65 shows the changes that we did for the default data source.


Figure 3-29 Default data source

4. Figure 3-30 shows that the changes are complete.

Figure 3-30 Default data source changes


3.4.4 Initializing database

Once the data source is defined, you must initialize the database. Initializing the IBM Tivoli Usage and Accounting Manager database creates and populates database tables and other database objects. Initializing the database is invoked from the ISC and the initialization is performed against the databases that are identified as the default administration data source.

Do these steps:

1. To initialize the IBM Tivoli Usage and Accounting Manager database using the ISC menu, select Usage and Accounting Manager → System Maintenance → Database → Initialize Database, as shown in Figure 3-31.

Figure 3-31 Initialize database

2. Click the Initialize Database button. Confirm the action by clicking Yes, as shown in Figure 3-32.

Figure 3-32 Confirmation window


3. Figure 3-33 on page 67 shows that the initialization of the database is complete.

Figure 3-33 Initialize the database

3.5 Enterprise Collector Pack implementation

The Enterprise Collector Pack (ECP) is a separate licensed component from IBM Tivoli Usage and Accounting Manager that must be installed for some of the collectors to run. You can get the Enterprise Collector Pack from the Passport Advantage Web site.

The Enterprise Collector Pack is a separate installable component that provides all available collection for usage data that is supported for the platform. The Enterprise Collector Pack must be installed on the machine with the IBM Tivoli Usage and Accounting Manager Enterprise Edition. The installation is performed by setup-tuam-ecp-7-1-0-wintel_ia32.exe.


Do these steps:

1. The welcome window is shown in Figure 3-34. Click Next.

Figure 3-34 Welcome window

2. The license agreement is shown in Figure 3-35. Accept the agreement and click Next.

Figure 3-35 License agreement


3. The Enterprise Collector Pack is always installed in the directory in which the enterprise edition is installed. Figure 3-36 shows the summary window for the installation. Click Install.

Figure 3-36 Summary window

4. When the installation completes, Figure 3-37 shows the completion window.

Figure 3-37 Completion window


3.6 Initial configuration

The processing directories define the path to find and store files for processing of usage and accounting data.

Do these steps:

1. Configure the path using the ISC options, that is, select Usage and Accounting Manager → System Maintenance → Configuration → Processing. Update the path according to your installation. Figure 3-38 shows our path definitions.

Figure 3-38 Configuring the paths used during processing


2. On the server, create the directories according to the path definitions that you have just configured. We do this from the command line, as shown in Figure 3-39. Note that the default directories for the Job File Path, Sample Job File Path, Job Log Files Path, and Collector Log Files Path are already created when the Application server is installed.

Figure 3-39 Create the processes directory

3.7 Installation verification

You can verify the IBM Tivoli Usage and Accounting Manager database initialization from the ISC console. The following sections discuss this action:

� 3.7.1, “Verify the tables created during initialization” on page 72

� 3.7.2, “Verify the contents of the CIMSRate table” on page 73

Note: The original processing path from the sample directory is used by the runSamples program to generate sample data.

# cd /opt/ibm/tuam# mkdir processes


3.7.1 Verify the tables created during initialization

Select Usage and Accounting Manager → System Maintenance → Database → Table Manager. Figure 3-40 shows the table list of the default administration database. There should be 42 tables in the list.

Figure 3-40 Table list


3.7.2 Verify the contents of the CIMSRate table

To verify the contents of the CIMSRate table, select Usage and Accounting Manager → System Maintenance → Database → Table Viewer. Expand the Database Tables tree and select the CIMSRate table from the Table Viewer main window. Select the View Table button to see the contents of the CIMSRate table selected in Figure 3-41.

Figure 3-41 View the contents of the CIMSRate table


3.7.3 Verify the application status in IIS

On the Report server, open the Microsoft Internet Information Services (IIS) Manager by selecting Start → All Programs → Administrative Tools → Internet Microsoft Internet Information Services (IIS) Manager. Expand the trees to display the application pools and the Web sites, as shown in Figure 3-42. Confirm the existence of the IBM Tivoli Usage and Accounting Manager entries.

Figure 3-42 Verify the installation of the IBM Tivoli Usage and Accounting Manager Web components

3.7.4 Connect to the reporting Web application

Open a browser, and point it at the IBM Tivoli Usage and Accounting Manager Web application URL. In our case, this is:

http://srv177/tuam/

The browser window displays the initial Web reporting option window, as shown in Figure 3-43 on page 75.


Figure 3-43 Web reporting interface

3.8 Sample collection verification

Before doing any further configurations in IBM Tivoli Usage and Accounting Manager, we run the provided samples:

/opt/ibm/tuam/bin/RunSamples.sh | tee RunSamples.log

We can ignore the warning messages, such as the one shown in Figure 3-44, as SMTP is not configured in our environment.

Figure 3-44 Ignoring the warning from RunSamples.sh

WARNING: AUCCM5019E The process failed when sending e-mail through [email protected] from to [email protected]. Review the trace log to get detailed information.


To check the results, select Usage and Accounting Manager → Chargeback Maintenance → Job Runner → Log Files, as shown in Figure 3-45.

Figure 3-45 Checking the Log Files viewer after RunSamples.sh has finished


In our example, the Notes job failed with a db2 error message during loading:

AUCPE0202E The DBLoad process completed unsuccessfully with the following exception: com.ibm.db2.jcc.c.lh: [ibm][db2][jcc][102][10040] Non-atomic batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.

The other errors are caused by not having the Enterprise Collector Package (ecp) installed:

AUCIN0365E The following collector is not authorized to run in the Usage and Accounting Manager Enterprise Edition: MS Exchange 2007AUCIN0365E The following collector is not authorized to run in the Usage and Accounting Manager Enterprise Edition: Apache

To do a final cleanup of the database, run an initialization, as described in 3.4.4, “Initializing database” on page 66.


Alternatively, you can unload the data by selecting Usage and Accounting Manager → Chargeback Maintenance → Load Tracking, as shown in Figure 3-46. Uncheck the End Date filter check box and mark all of the entries by using the check box button.

Figure 3-46 Unloading the RunSamples.sh data from the database

Press Delete Load and confirm the security question about deleting the data.


Chapter 4. Configuration

This chapter discusses the configuration of the IBM Tivoli Usage and Accounting Manager V7.1 installation. The discussion is covered in the following sections:

� 4.1, “The Common Source Resource format” on page 80

� 4.2, “Account code hierarchy” on page 82

� 4.3, “User administration” on page 84

� 4.4, “Clients and scheduling” on page 88

� 4.5, “Working with rates” on page 92

4


4.1 The Common Source Resource format

IBM Tivoli Usage and Accounting Manager uses two file formats called Common Source Resource (CSR) and Common Source Resource plus (CSR+). The CSR+ is enhanced by a static header, including the account code for sorting purposes. CSR+ and CSR files are comma separated files, in which each record has these three sections:

� Header

The header of the record contains the following:

CSR Plus Header CSR+ records only start with:“CSR+ Constantheaderstartdate Usage start dateheaderenddate Usage end dateheaderaccountcodelength

Length of the Account code (three digits)headeraccountcode Account Code“ Constant

headerrectype Record type or sourceheaderstartdate Usage start dateheaderenddate Usage end dateheaderstarttime Usage start timeheaderendtime Usage end timeheadershiftcode Shift code

The header information is used to identify the applicability of the record to a certain billing period and type.

A sample header segment for CSR is:

UNIXSPCK,20071016,20071016,00:00:00,23:59:59,1

A sample header for CSR+ starts with:

“CSR+2007101620071016009AIX 0Test“,UNIXSPCK,20071016,..

� Identifiers segment

The identifiers segment lists the resource identifier. These identifiers are used to distinguish one resource from the other before mapping them to an account code. The account code itself is considered an identifier. The structure of this segment is:

number of identifiers, identifier name, identifier value, ...

Tip: All header% variables can be used with the Integrator identifier functions.


An example identifier segment with three identifiers is:

3,SYSTEM_ID,"lpar04",Account_Code,"AIX 1TEST lpar04", USERNAME,"root"

� Resources segment

The resources segment lists the resource metrics. These metrics are used to meter the usage information for the resource. If the resource metric value is zero, the resource metric will not be written to the output CSR file. The resource metric is structured as follows:

# of resources, resource metric name, resource metric value ...

An example resources segment with three metrics is:

3,LLG102,17.471,LLG107,6.914,LLG108,3

Example 4-1 shows the data from two AIX LPARs on two different systems.

Example 4-1 CSR file for AIX Advanced Accounting data

AATRID10,20071030,20071030,01:10:03,01:10:03,1,2,SYSTEM_ID,"02101F170",Account_Code,"AIX 1TEST lpar04",1,AAID1002,0.016AATRID10,20071030,20071030,01:15:03,01:15:03,1,2,SYSTEM_ID,"02101F170",Account_Code,"AIX 1TEST lpar04",1,AAID1002,0.004AATRID4,20071030,20071030,02:30:07,02:30:07,1,2,SYSTEM_ID,"02101F25F",Account_Code,"AIX 0SAP ohm01",2,AAID0402,120,AAID0407,2048

In Example 4-2, we find the data from two VMware ESX servers (SYSTEM_ID) and three VMware guests (Instance) that was collected using a single VirtualCenter Server (Feed).

Example 4-2 CSR file for VMWare processing

VMWARE,20071017,20071017,00:00:00,23:59:59,1,5,HostName,"host-19",Instance,"vm-33",Feed,"ITSC_VC",Account_Code,"WIN 1ESX",SYSTEM_ID,"srv079.itsc.austin.ibm.com",1,VMCPUUSE,10756036VMWARE,20071017,20071017,00:00:00,23:59:59,1,5,HostName,"host-19",Instance,"vm-41",Feed,"ITSC_VC",Account_Code,"WIN 4ESX",SYSTEM_ID,"srv079.itsc.austin.ibm.com",1,VMCPUUSE,10688008VMWARE,20071017,20071017,00:00:00,23:59:59,1,5,HostName,"host-8",Instance,"vm-31",Feed,"ITSC_VC",Account_Code,"WIN 0ESX",SYSTEM_ID,"srv106.itsc.austin.ibm.com",1,VMCPUUSE,637429

Chapter 4. Configuration 81

The IBM Tivoli Usage and Accounting Manager defines some reserved identifiers that are used for special processing. Those identifiers are:

Account_Code Will be matched with the Account Code Structure and used for Rate Table selection and Reporting Aggregation.

SYSTEM_ID Used for reading the factor from the Normalization Table during CPU normalization.

WORK_ID Optionally used for CPU normalization on a z/OS data collector specifying a subsystem like TSO, JES2, or any other application (also not z/OS) if needed.

Feed Identifies and defines a sub folder within the process folder for data transfer.

4.2 Account code hierarchy

The account code is the primary identifier that signifies who should get billed for the specified system usage. The account code structure has to be defined early on before you perform any data collection and processing. All the data items would be labelled by the account code, so it would be very hard to change the structure. This section explains the usage of the account code within IBM Tivoli Usage and Accounting Manager and should help you define the account code structure according to your needs.

The account code is a string with a fixed width field that defines the hierarchy of the accounting breakdown. The fields would be used to split the account string used for charging different organizational entities. Figure 4-1 on page 83 shows a sample account code and its relation to the charging rate.


Figure 4-1 Sample account code with four parts and the rate code relationship

The first part of the account code is the Client, representing the top level of your organization. The other parts are hierarchical information for aggregating the data during reporting. All parts of the account code is used to search the Clients table to get a rate table. The lookup is performed based on each level of the account code hierarchy level; if no match is found, it will use the STANDARD rate table. We can set up a specific Rate Table for any account if necessary. The Rate in the specific rate table is matched to the resource name in the resources segment of CSR file to get the appropriate rate information.

Rates are also organized in rate groups. The rate group allows you to report summary usage based on rate groups. Each rate has the definitions for the format, type, conversion factor, and money value for all shifts.

If a rate has the type CPU, the normalization will be done for this value during billing based on the identifiers SYSTEM_ID or WORK_ID.

Consideration: When you define a new rate group using the ISC Rate menu, the group name is limited to eight characters. Using the ISC Rate Group menu, you can rename the group later or create longer names, as the examples shipped with IBM Tivoli Usage and Accounting Manager show.

Rate Table Rate GroupVMware

RateVMDSKRD

Rate GroupWindows

Rate VMCPUSY

Rate WINCPUUS

RateWINDSKWR

RateWINMEMHI

Client8 char

Host32 char

Application8 char

Financial information12 char

Account code

VMWARE,20071025,20071025,00:00:00,23:59:59,1,

3,Feed,VM1,Account_Code,”ABCDEFG000012340000FINUSAGEsrv106.itsc.austin.ibm.com“,SYSTEM_ID,srv106,

2,VMCPUSY,200,VMDSKRD,345

CSR record


The default account code structure looks like Figure 4-2. This can be maintained using the Integrated Solutions Console (ISC) menu by selecting Usage and Accounting Manager → System Maintenance → Account Code Structure.

Figure 4-2 Default IBM Tivoli Usage and Accounting Manager account code structure

4.3 User administration

The user administration topic for IBM Tivoli Usage and Accounting Manager is divided into the following sections:

� 4.3.1, “User creation” on page 85� 4.3.2, “User role definition” on page 86� 4.3.3, “User and group mapping” on page 86


4.3.1 User creation

User administration actions are performed right from the Integrated Solutions Console (ISC). The following procedure adds new users for Web reporting:

1. Log on to the Integrated Solutions Console (ISC).

2. Select Usage and Accounting Manager → System Maintenance → Users.

3. On the User List Maintenance page, click New.

4. On the User Maintenance page, complete the following:

User ID Type an ID for the user.

Full Name Type the user’s full name.

E-mail Address Type the user’s e-mail to enable the user to receive reports through the automatic report distribution feature. If this feature is not required or if users should not receive distributed reports, leave this box blank.

Group Select the group that the user should be added to from the drop-down list or accept the default ADMIN group.

Configuration Options MaintenanceClick to add user configuration options that can be used for custom reports and Web pages.

Domain Name and Domain User IDType the user’s Windows domain name and user ID. Usage and Accounting Manager Web Reporting and other Usage and Accounting Manager Web-based applications provide an automatic logon feature. To enable a user to use this feature, the user’s Windows domain name and user ID are required. In addition, Enable Intranet Auto Login must be enabled on the Configuration—Reporting page and IIS security for the Usage and Accounting Manager Web Reporting Web site and any other Usage and Accounting Manager sites must be set to Integrated Windows authentication.

Password If the automatic logon feature for Usage and Accounting Manager Web applications is not being used, use this box to type a password for the user or to change an existing password. The password is alphanumeric and case-sensitive and can be a maximum of 16 characters.

5. Click OK to save the new user.


4.3.2 User role definition

A user role can be used to arrange user access for reports. The users with access to the same role have access to the same set of reports. This section explains user role creation from the Integrated Solutions Console.

Do these steps:


2. Select Usage and Accounting Manager → System Maintenance → Users and Groups → Administrative User Roles.

3. On the Administrative User Roles page, click Add.

4. On the Administrative User Roles page, type in a User ID defined to the local operating system and then select the Usage and Accounting Manager security group or groups that the user should be assigned to:

tuammaint Clients, Rates, Rate Groups, Reports, Report Groups, Report Distribution, and all sub pages

tuamchargebackadminAll pages with the exception of Initialize Database, Database Upgrade, Objects Manager, Database Manager, Table Manager, Table Viewer, and all sub pages

tuamadmin All pages

tuamtransaction Miscellaneous, Recurring, or Credit Transaction List Maintenance and all sub pages

5. Click Next to enable the security.

4.3.3 User and group mapping

User group is another way of grouping users with the same role so that authority is given to the group, not individual users. After you define the group and the users, you can associate the user with the new group that you define. This section explain the procedure:


2. Select Usage and Accounting Manager → System Maintenance → Users Groups.

3. On the User Group List Maintenance page, click the View pop menu icon to the right of User Group and click New User Group.


4. On the User Group Maintenance page, complete the following:

Group ID Type an ID for the user group.

Description Type a description of the group. The description is shown on the User Group List Maintenance page.

Account Code Structures Selected and Available You can add and remove structures from the Selected and Available boxes. All structures that are displayed in the Selected box are accessible to users in the group from the Usage and Accounting Manager Web site. This feature enables users to dynamically selected the account code structure that they want to use to generate reports. If there are multiple account code structures in the Selected box, set one of the structures as the default structure by clicking the structure and then clicking Make Default.

Group Select the group for which the user should be added to from the drop-down list or accept the default ADMIN group.

Configuration Options MaintenanceClick to add user configuration options that can be used for custom reports and Web pages.

Domain Name and Domain User IDType the user’s Windows domain name and user ID. Usage and Accounting Manager Web Reporting and other Usage and Accounting Manager Web-based applications provide an automatic logon feature. To enable a user to use this feature, the user’s Windows domain name and user ID are required. In addition, Enable Intranet Auto Login must be enabled on the Configuration—Reporting page and IIS security for the Usage and Accounting Manager Web Reporting Web site and any other Usage and Accounting Manager sites must be set to Integrated Windows authentication.

Allow Financial Modeler access Select this check box to allow users in this group to access Usage and Accounting Manager Financial Modeler.


Allow administrative accessSelect this check box to give the users in this group administrative configuration options in Usage and Accounting Manager Web Reporting.

Configuration Options Maintenance Click to add user group configuration options that can be used for custom reports and Web pages.

4.4 Clients and scheduling

This section discusses additional management resources that exists in IBM Tivoli Usage and Accounting Manager. The resources are discussed in these sections:

� 4.4.1, “Calendar” on page 88� 4.4.2, “Client” on page 89� 4.4.3, “Client budget” on page 90� 4.4.4, “Client contact” on page 91

Rate related information is discussed in 4.5, “Working with rates” on page 92.

4.4.1 Calendar

Calendar is a mechanism in IBM Tivoli Usage and Accounting Manager for defining billing periods. There is a maximum of 52 periods to be defined, correspond to a weekly billing cycle. To work with Calendar, perform the following tasks:


2. Select Usage and Accounting Manager → System Maintenance → Calendar.

3. On the Calendar page, select the year from the Year drop-down list and complete the following:

Year Select the appropriate year.

New Year Click to add a new year to the calendar.

Delete Year Click to delete the currently shown year.

Period Shows 12 periods for the year, or 13 periods if Use 13 Periods is enabled on the Configuration—Processing page.


Beginning Date Type a beginning date for the period, use the View Calendar icon to select a beginning date, or accept the default date.

Ending Date Type an ending date for the period, use the View Calendar icon to select a ending date, or accept the default date.

Close Date Shows the close date for the period if a day-of-month close date has been set on the Configuration—Processing page. The close date is displayed for the period in which it was set, the previous period, and future periods. If a specific date close date or no close date has been set, the Close Date is not shown.

Set From Period 1 Click to have all periods proceed sequentially from the first period.

4. Click Apply to save the settings.

4.4.2 Client

Clients are organizational units in the billing part of IBM Tivoli Usage and Accounting Manager that can be represented by an account code. These clients are stored in the client table. To work with the client table, perform the following tasks:


2. Select Usage and Accounting Manager → Chargeback Maintenance → Clients.

3. Usage and Accounting Manager includes sample clients. Remove these sample clients before adding clients for the customer’s organization.

4. On the Client List Maintenance page, click New.

5. On the Client Maintenance page, complete the following:

Account Code Type the account code to assign to the client.

Account Name Type the name of the client as it should be shown in invoices and other reports.

Alternate Account CodeType an alternate account code if the client account will be used for reporting systems that have different standard account codes, such as General Ledger systems and other reporting formats.


Rate table Select a rate table that is used to calculate client charges. The STANDARD table is used by default.

Action Codes The use of these options is user-specified. These codes are available for custom reports and can be used for selecting data.

4.4.3 Client budget

Client budget for individual resources can be specified to compare budget against an actual usage report. This report allows easy comparison of any financial line item against the budgeted usage. The client budget definition is performed using the following tasks:



3. On the Client List Maintenance page, click the View pop-up menu icon to the right of the client to assign the budget to and then click Budgets.

4. On the Budget Maintenance page, complete the following:

Year Select the appropriate year if it is not shown. You can add or delete year information.

Overall Account BudgetClick to set the overall budget for the client account. To set budgets for individual resources, click the View pop-up menu icon to select the rate code or codes for the resources required. The rate codes are displayed under Overall Account Budget. Click the individual rate codes to set the budget for the resource. To remove the resource budget, click the View pop-up menu icon to the right of the rate code, and then click Remove Resource Budget.

Total Budget AmountType the total monetary amount to be budgeted for the consumed resources.

Note: To use a rate table other than STANDARD for a client, the CLIENT SEARCH ON control statement in the BillCntl.txt file must be enabled in each process definition. Invoice Contact - Shows the contact for the client (if a contact has been specified). If there are multiple contacts for the client, select the appropriate contact from the drop-down list.


Divide Total Click to divide the value in the Total Budget Amount or Total Budget Units box by the number of periods and automatically populate the Period 1 through Period 12 boxes with the result. Note that if the amounts are changed in either the Total Budget Amount or Total Budget Units box, this step must be performed again.

Sum Periods Click to add the values that are displayed in the Period 1 through Period 12 boxes and automatically enter the sum in the Total Budget Amount or Total Budget Units box. Note that if the amount is changed for a period or periods, this step must be performed again.

Periods Type in a budget amount for one or more periods to create a value in the Total Budget Amount or Total Budget Units box using the Sum Periods button. If you use the Divide Total box to calculate the period amounts, leave these boxes blank.

4.4.4 Client contact

Client contacts are client descriptions, such as addresses, phone numbers, and contact persons. A client contact can be managed from the Integrated Solution Console by doing the following steps:



3. On the Client List Maintenance page, select the check box for the client that needs to be added as a contact or contacts to and then click Contacts.

4. On the Client Contact List Maintenance page, click New.

5. On the Client Contact Maintenance page, complete the following tabs:

Address The name, address, and e-mail address for the contact.

Phone Phone numbers, such as voice, fax, and pager for the contact.

Other Department, office, any comments, and the Web site URL for the contact.

6. Click OK to save the contact information and return to the Client List Maintenance page where the new client is shown.


4.5 Working with rates

Rates are managed using the procedures discussed in this section. We discuss this topic in the following sections:

� 4.5.1, “Rate group” on page 92� 4.5.2, “Rate codes” on page 92� 4.5.3, “Alternate rates” on page 94� 4.5.4, “Proration table” on page 95� 4.5.5, “CPU normalization” on page 96� 4.5.6, “Rate shift” on page 97

4.5.1 Rate group

Rate group is a way to apply a different set of rates for different clients. Each client is mapped to a rate group. The rate group definition is as follows:


2. Select Usage and Accounting Manager → Chargeback Maintenance → Rate Groups.

3. On the Rate Group List Maintenance page, click the View pop-up menu icon to the right of Rate Groups and then click New Rate Group.

4. On the Rate Group Maintenance page, complete the following:

Name Type the name to assign to the rate group.

Description Type a description of the rate group. This is the value that is shown on the Rate Group List Maintenance page and the value that appears for the rate group in the standard reports that are provided with Usage and Accounting Manager.

4.5.2 Rate codes

Rate codes can be managed by doing the following steps:


2. Select Usage and Accounting Manager → Chargeback Maintenance → Rates.

3. On the Rate List Maintenance page, click New and input the following information:

– Rate Code: Type a code to represent the rate. You have a maximum of eight characters.


– Description: Type a meaningful description of the rate code. The description is displayed on reports, graphs, and spreadsheets. It is recommended that units of measurement are included (GB, MB, hours, minutes, and so on) as applicable.

– Rate Value: Type the amount to be charged for the consumption of the resource represented by this rate code. The value is multiplied by the resource amount contained in the matching CSR or CSR+ file.

– Rate Index; Shows the order in which the rate code is displayed in reports. The order can be changed; however, an index number that is already in use cannot be typed.

– Rate Table; Select the rate table to add the rate code to from the drop-down list.

– Rate Group: Select the rate group for the rate code from the drop-down list or click New Rate Group to create a new rate group. All rate codes must be assigned to a rate group; if none is specified, it belongs to the All Unassigned rate group.

– New Rate Group: Click to open the New Rate Group page and create a new rate group.

– Use 4 decimals for rate: This option determines the number of decimal digits that appear in the rate value in reports. If this check box is selected, the rate value includes four decimal digits. If this check box is not selected, the rate value includes eight decimal digits.

– Resource Conversion: Adjust the total resource units value in reports using the following conversion factors:

Default No conversion is performed.

Divide By or Multiply ByThe total resource units are divided or multiplied by a set conversion factor (for example, Divide By 1000, Multiply By 60, and so on).

Multiply By Conversion FactorThe total resource units are multiplied by the factor in the Conversion Factor box.

– Rate is per thousand: Select this check box to change the rate in reports from per resource unit to per thousand units.

– Do not adjust for zero cost: Select this check box if the associated rate code should not be included in zero cost calculations.


– Conversion Factor: This box is available only when Multiply By Conversion Factor is selected in the Resource Conversion box. Type a number by which to multiply the total resource units for the rate code. This factor can be up to 16 digits, including a decimal.

– Flat fee money charges: Select this check box if the resource units for the rate code are considered a monetary amount rather than units of utilization. In this situation, the resource units and the charges are the same in reports.

– Resource Decimals: Select the number of decimal digits that appear in the resource units value in reports, for example, 0=99, 2=99.99, 4=99.9999. The default is two decimal digits.

– CPU value: Select this check box to normalize CPU usage for this rate.

– Report Flag 1 and 2: The use of these boxes is user-specified. These boxes allow you to type a one-character value that can be used in custom reports.

– Currency Symbol: The use of this box is user-specified. This box allows you to type a currency symbol that can be used in custom reports.

– Detail Description: The use of this box is user-specified. This box allows you to type a description of the rate code that can be used in custom reports.

– Comments: Type any comments regarding the rate code.

– Add Rate Shifts: Click to add rate shifts for the rate code. This button shows only when adding a new rate code. Rate shifts allow you to set different rates based on the time.

– Edit Rate Shifts: Click to edit rate shifts for the rate code. This button shows only when you are editing an existing rate code.

– Delete Rate Shifts: Click to delete rate shifts for the rate code. This button shows only when rate shifts have been created.

– Shift: Shows shift numbers 2 through 9. The rate code has one shift by default.

– Rate Value: Type the monetary rate value for the shift.

– Description: Type a description of the rate shift.

4.5.3 Alternate rates

Rates are grouped in rate tables. IBM Tivoli Usage and Accounting Manager provides a standard rate table that is typically used for billing processing. Alternate rate tables can be defined to provide different rate schemes for other clients.


To define a new rate table, do these steps:



3. On the Rate List Maintenance page, click New Table or Duplicate Table.

4. On the New Rate Table or Duplicate Rate Table page, type the name to assign to the rate table.

4.5.4 Proration table

If certain usage cannot be measured from the input data, rates can be calculated by assigning parts of the overall usage by percentage to different account codes. This process is called prorating the usage. The translation of the usage is performed using a proration table.

The proration table is an ASCII text file that defines the identifier values and rate codes used in the proration process. The proration table must contain records with the following comma-delimited fields: input identifier value, output identifier value, percentage, and rate code.

Copy the prorate.txt from the \sample\processes\Prorate sample directory. Modify the prorate.txt table to include the information for each identifier or account code for which proration needs to be performed. Change these values:

� The input identifier value to prorate from. The identifier value is matched against the following information in the input file:

� An identifier name that has been defined in the job file.

� The values for that identifier name.

Assume that you have an application that controls print in a centralized environment and that you want to split all resources used by account code AAABB among three different accounts: A1, A2, and A3. A1 on average uses about 50 percent of the resources assigned to the AAABB account, A2 uses about 30 percent, and A3 uses about 20 percent. To prorate the costs associated with this application among the three accounts, create the table shown in Example 4-3.

Example 4-3 Proration table sample

AAABB,A1,50,AllAAABB,A2,30,AllAAABB,A3,20,All


You can also split individual resources among multiple accounts. Using the preceding example, assume that the only resources from account AAABB that you want to prorate are represented by the rate codes Z001 and Z002, as shown in Example 4-4.

Example 4-4 Proration with specific rate codes

AAABB,A1,50,Z001AAABB,A2,30,Z001AAABB,A3,20,Z001AAABB,A1,50,Z002AAABB,A2,30,Z002AAABB,A3,20,Z002

In this example, all resources other than Z001 and Z002 would still be charged to the AAABB account.

If you want to charge account AAABB for a portion of the resources used, for example, you want to charge account AAABB 60 percent for all resources and account AACCC 40 percent, create the table shown in Example 4-5.

Example 4-5 Proration with percentage point

AAABB,AAABB,60,AllAAABB,AAACC,40,All

4.5.5 CPU normalization

Another modification of the rate can be applied to CPU values. Different machines can have relatively different CPU speeds. The CPU usage must be normalized so that we can charge each usage in a comparable fashion. This CPU normalization is performed by doing the following steps:

1. Include the NORMALIZE CPU VALUES control statement in one of the following locations:

a. The job file used to collect and process the data. Use the Bill program controlCard attribute (that is, <Parameter controlCard="NORMALIZE CPU VALUES" />).

b. The control file for the Bill program. The control file must be defined in the job file using the Bill program controlFile attribute. For example, controlFile=”MyBillCntl.txt”. The default file name is called BillCntl.txt.


c. For each rate code for which you perform normalization, open the Integrated Solutions Console Rate Maintenance page and select the CPU value check box.

2. Select Usage and Accounting Manager → System Maintenance → CPU Normalization.

3. On the CPU Normalization List Maintenance page, click New.

4. On the CPU Normalization Maintenance page, complete the following:

System ID Type the name of the system. For z/OS, this is the four-character System Model ID. For UNIX and Windows, it is the computer name. Note that the input file must contain an identifier named System_ID to identify the system name.

Application or subsystemType the application or subsystem name. This is any other system value that can narrow the normalization (for example, the CICS® region name, the DB2 plan name, or the Oracle instance). Note that the input file must contain an identifier named Work_ID to identify the application or subsystem name.

Normalization factor Type the normalization factor. For example, an organization has two z/OS systems, AL90 and AL95. System AL95 is 20 percent faster than AL90. If using AL95 as the base system, use a factor of .80 to normalize AL90 to reflect the speed of AL95.

4.5.6 Rate shift

Rates can be provided on different shifts. A rate shift can be defined as follows:


2. On the Rate List Maintenance page, click the View pop-up menu icon to the right of the rate code to assign the rate shifts to and then click Edit Rate Shifts. On the Rate Shift Maintenance page, complete the following:

Rate Value Type the monetary rate value for the shift.Description Type a description of the rate shift.

Shift numbers 2 through 9 are shown. The rate code has one shift by default.


Chapter 5. Administration

This chapter discusses administering IBM Tivoli Usage and Accounting Manager V7.1. The discussion is covered in the following sections:

� 5.1, “Integrated Solution Console” on page 100

� 5.2, “Load tracking” on page 102

� 5.3, “Tuning” on page 103

� 5.4, “Operating and updating” on page 105

5


5.1 Integrated Solution Console

The Integrated Solution Console is the primary administration interface for IBM Tivoli Usage and Accounting Manager. You access the Web console using the address http://hostname:11052/ibm/console/ using a Web browser. After logging in, the initial window shown in Figure 5-1 appears. We verify that the product information matches the version that we have installed.

Figure 5-1 Verifying the installation of the application server

The tasks or navigation menu is on the left side of the window. Figure 5-2 on page 101 shows the IBM Tivoli Usage and Accounting Manager related menu items.


Figure 5-2 Usage and Accounting Manager tasks

The tasks are:

� Chargeback Maintenance, which provides data processing options:

Job Runner To control and modify the data processing.

Job Files To maintain the data processing jobs.

Log files For daily checks.

Samples View samples for creating new job files.

Load Tracking Check for data loaded into the database.

Clients Set up the parameters for an client used by accounting.

Rates Define the parameter and costs for a resource.

Rate Groups Group the rates for reporting purposes.

� System Maintenance, which defines basic configurations:

Data Source Define database and WEB service connection information.

User Access control.

User groups Organize the roles for the users.

Calendar Set up the calendar.

Account Code StructureDefine the structure for accounting data identifiers.

Chapter 5. Administration 101

CPU Normalization Updating the table for normalization based on the identifier named here.

Identifiers Listing used and unused Identifiers and deleting unused Identifiers.

Rate Identifier Run automatic update of Rate Identifiers.

Configuration For most basic configuration data, such as paths and trace level.

Reports Define and list reports available.

Report Groups Organize the reports in groups.

Report Distribution Define the distribution of reports.

Transaction A wizard for editing of the transaction table for frequently used non-usage input data.

Database To control or check the database settings:

• Initialize Database: Do the initial setup of the database.

• Upgrade Database: Upgrade a database after updating the IBM Tivoli Usage and Accounting Manager application server software.

• Object Manager: Define and maintain indices, stored procedures, tables, and views.

• Table Viewer: Check the content of a table. If an ISC session is pending for some time, it will be disconnected and the last action may be lost.

5.2 Load tracking

One of the major administration items for IBM Tivoli Usage and Accounting Manager is the data loading to the database. Before the data load, all source data are just files on the file systems. Once the data is loaded into IBM Tivoli Usage and Accounting Manager, it is tracked and controlled by the application.

The loading information is stored in the Load Tracking table (CIMSLOADTRACKING). You can access the Load Tracking information from the Integrated Solution Console by selecting Usage and Accounting Manager → Chargeback Maintenance → Load Tracking.

The load tracking information can be filtered using the Source Feed, Load Type, or other fields. The filtering can use Exact Match or Contains as necessary.

A sample load tracking window is shown in Figure 5-3 on page 103.


Figure 5-3 Load Tracking content

5.3 Tuning

As with any database-based solution, IBM Tivoli Usage and Accounting Manager must be continuously tuned. The tuning process ensures that it works at least at an acceptable performance. The main tuning activities relate to having fast access to usage and accounting data for reporting. It should also ensure acceptable response time for administration and job processing.

Tuning aspects are covered in the following sections:

� 5.3.1, “Tuning Web console for administration” on page 104� 5.3.2, “Tuning job processing” on page 104� 5.3.3, “Tuning report generation” on page 105


5.3.1 Tuning Web console for administration

The Web console is based on WebSphere Application Server. While the application does not have any tuning parameters, there are still some performance options to be performed:

� Determine the memory usage of WebSphere Application Server. Add physical memory if needed. The more the user accesses the Integrated Solution Console, the more memory WebSphere needs. You can set or limit the WebSphere Application Server Java heap size in its configuration.

� Determine the CPU load. Add virtual or logical CPUs for parallel processing.

� If there is performance contention for memory or processing, consider separating the database and application server. However, this can generate additional network traffic between them. Having the database and application server separate but on a local sub-net based on high speed network, such as Gigabyte Ethernet, would help.

5.3.2 Tuning job processing

Job processing includes reading source data for collection, performing transformation, and then loading the data into an IBM Tivoli Usage and Accounting Manager database. Most of the steps and stages of the job are running Java Virtual Machine. There are some performance considerations for the job processing:

� Add virtual or logical CPUs for parallel processing or run jobs on different machines to increase the processing power. However, running the jobs on multiple machine can affect network load and produce a need for job synchronization if the jobs are dependent on each other.

� Memory contention from a large number of running jobs can be alleviated by having separate processing servers. This also helps with network load and synchronization problems.

� Database loading performance can be improved by having the database properly tuned for insertion. IBM Tivoli Usage and Accounting Manager is typically used in a database in Insert and Query mode only. The job mainly performing insertions, not updates. The performance of inserting data into tables can be ensured by doing the following tasks:

– Pruning old unused data regularly ensures that data remains manageable.

– Ensuring tables have good organization using the REORG utility.

– Ensuring the table statistics are current using the RUNSTAT utility.


– Having the heavily used tables (CIMSSUMMARY, CIMSDETAIL, CIMSDETAILIDENT, and maybe CIMSRESOURCEUTILIZATION) on their own fast disk storage.

5.3.3 Tuning report generation

Report generation of usage and accounting data is the end deliverable of IBM Tivoli Usage and Accounting Manager. This is the function that must be defined for outputting data that has been processed. Report tuning is mainly tuning the access to data tables (CIMSSUMMARY, CIMSDETAIL, CIMSDETAILIDENT, and maybe CIMSRESOURCEUTILIZATION).

� Database tuning actions that must be performed on a regular basis:

– Pruning old unused data regularly to ensure a manageable data size; this can be performed using the DBpurge job step.

– Ensuring tables have good organization using the REORG utility.

– Ensuring the table statistics are current using the RUNSTAT utility.

– Having the heavily used tables on their own fast disk storage.

� Report SQL tuning

SQL tuning for specific reports can be performed independently. Collect information about regularly used and long running reports. For those reports, determine the tables and columns used for sorting. You may define additional indices for heavy used columns.

5.4 Operating and updating

This section discusses some operational aspect of IBM Tivoli Usage and Accounting Manager. The topics are discussed in the following sections:

� 5.4.1, “Startup” on page 106� 5.4.2, “Shutdown” on page 1065.4.3, “Updating” on page 107

Note: Creating additional indices may reduce the insertion performance of a table.


5.4.1 Startup

The startup of IBM Tivoli Usage and Accounting Manager is performed by the administration server system. There are several startup methods for the embedded WebSphere Application Server:

� Windows systems:

– \Program Files\ibm\tuam\bin\startServer.exe– \Program Files\ibm\tuam\ewas\bin\startServer.bat server1

� UNIX/Linux systems:

– /opt/ibm/tuam/bin/startServer.sh– /opt/ibm/tuam/ewas/bin/startServer.sh server1

Figure 5-4 details the messages produced by the application as it starts.

Figure 5-4 Starting ISC

When the Integrated Solution Console WebSphere is started, open a Web browser and direct it to the Integrated Solution Console at the following address:

http://srv105:11052/ibm/console

5.4.2 Shutdown

The startup IBM Tivoli Usage and Accounting Manager is performed by the administration server system. There are several startup methods for the embedded WebSphere Application Server:

� Windows systems:

– \Program Files\ibm\tuam\bin\stopServer.exe– \Program Files\ibm\tuam\ewas\bin\stopServer.bat server1

� UNIX/Linux systems:

– /opt/ibm/tuam/bin/stopServer.sh– /opt/ibm/tuam/ewas/bin/stopServer.sh server1

[root@srv105 bin]# ./startServer.sh server1ADMU0116I: Tool information is being logged in file /opt/ibm/tuam/ewas/profiles/AppSrv01/logs/server1/startServer.logADMU0128I: Starting tool with the AppSrv01 profileADMU3100I: Reading configuration for server: server1ADMU3200I: Server launched. Waiting for initialization status.ADMU3000I: Server server1 open for e-business; process id is 29586


5.4.3 Updating

When updating the IBM Tivoli Usage and Accounting Manager, do these steps:

1. Inform all users of the planned outage.

2. Wait for running jobs to be finished.

3. Stop the IBM Tivoli Usage and Accounting Manager server.

4. Stop any scheduling tools for job processing.

5. Perform an update of the software.

6. Start the IBM Tivoli Usage and Accounting Manager server.

7. Start the scheduling of job processing.

8. Check that the application is accessible using the ISC Web interface.


Chapter 6. Job creation

This chapter discusses job file creation for IBM Tivoli Usage and Accounting Manager V7.1. The discussion is covered in the following sections:

� 6.1, “XML job creation” on page 110

� 6.3, “Integrator program” on page 119

� 6.4, “Account code mapping” on page 123

� 6.5, “Non-integrator steps” on page 126

6


6.1 XML job creation

This section discusses job file structures and a generic processing overview.

6.1.1 Job file structure

XML is a tagged file format similar to Hypertext Markup Language (HTML). XML only enforces the usage of a pair of start and end tags; the value of the tag and their attributes are enforced by the referenced extensible style document (.xsd file). For Job Runner’s job, the style is TUAMJobs.xsd, which is stored in the /config/schemas directory of IBM Tivoli Usage and Accounting Manager.

The structure of the XML file is shown in Figure 6-1.

Figure 6-1 Job file structure

The components of a job file are:

Jobs This is the primary XML container for a Job Runner job file.

Job A definition of a job provides some global parameters of the job and some e-mail notification parameters. There is typically one job per jobs.

Jobs

Job

Process

Steps

StepStage

Process

Step Step

Stage

Steps

StepStage

Step Step

Stage


Process A process represents a sequentially processed items. You can have multiple processes within a job. Each process group would invoke a separate job runner instance to run in parallel.

Steps The steps construct is a container for step items.

Step A step is the actual definition of what the individual processing would perform. A step runs an actual program. Typically, a step would perform a single processing task, such as billing, scanning, sorting, cleanup, or database loading; however, there is a special step called integrator that can be comprised of multiple stages.

Stage A stage is a construct within the integrator step that signifies an action within the integrator step.

For regular jobs, you can use the command-line Job Runner statements to integrate IBM Tivoli Usage and Accounting Manager jobs into your scheduling system, as shown in Example 6-1.

Example 6-1 Job Runner command line usage in scheduler definitions

/opt/ibm/tuam/bin/startJobRunner.sh LoadVMware.xml >> LoadVMware.log 2>&1/opt/ibm/tuam/bin/startJobRunner.sh LoadTDSz1.xml -date today >> LoadVMware.log 2>&1

The return code for Job Runner might be:

0 No warning or error4 Warning16 Error during processing255 Syntax error within the parameters

Figure 6-2 on page 112 shows the graphical user interface (GUI) for the job handling. If you select Usage and Accounting Manager → Chargeback Maintenance → Job Runner → Job Files, you can validate the XML syntax, run the job, and make small changes to an existing job. For editing and creating larger job files, we recommend using an specialized XML editor.

Chapter 6. Job creation 111

Figure 6-2 shows the Job Files menu.

Figure 6-2 The Job Runner Job maintenance

6.1.2 Generic processing overview

The data processing in IBM Tivoli Usage and Accounting Manager is similar for all data sources. Figure 6-3 on page 113 shows the general processing steps for data handling with IBM Tivoli Usage and Accounting Manager. The order or mix of the steps may be different, depending on the collectors used.

Note: As the job file must reside in the jobfiles directory in the processing server, the XML editor should have access to this folder or path.


Figure 6-3 Generic process overview with common steps

The process steps in Figure 6-3 are:

1. Many systems already have a resource usage collection function and IBM Tivoli Usage and Accounting Manager will use this data for further processing. The main processing in IBM Tivoli Usage and Accounting Manager is based on the Common Source Resource (CSR) format. The initial processing step converts the existing data (SQL table, delimited file, or others) into CSR format prior to IBM Tivoli Usage and Accounting Manager processing.

a. If the metering data is collected in files, these will be transferred to the application server and converted to CSR format if needed. Some converters may also include pre-aggregation.

Collected data files Aggregation

Account Conversion

Scan(Merging)

Normalization &Billing (applying rate)

Common Source Resource (CSR) file

Merged output(CSR+)

Output file(CSR+)

Exception file(CSR)

Summarized data(CSR)

Billing Output file

Billing Summary file

Database Load

Account Table

Normalization& Rate Table

ITUAMDB

Output file(CSR+)

reprocessWeb or data base

dataSource

DataCollector

Ident file

Output files(CSR+)


b. If the metering data can be accessed on a database or Web page, the data extract made by IBM Tivoli Usage and Accounting Manager will be directly from the CSR format.

The IBM Tivoli Usage and Accounting Manager Integrator can include CSR conversion, aggregation, account code conversion, and sorting in one step, thereby producing only one output file.

2. CSR data is aggregated mostly on a daily basis. Aggregation means summarizing the data based on given identifiers. It calculates the sum of the data of resource fields based on the identifier values.

3. Account conversion matches the metering data to the account code structure, and all records that do not fit are put in an exception file, and this exception file may be reprocessed later after some intervention.

4. CSR or CSR+ files of the same type can be scanned into one file at any time during the processing.

5. Normalization of CPU values and multiplying by the Rate code is the next step. The selected Rate Table will be used for calculating the money value. If the Rate is of the type CPU, the recalculation based on the Normalization Table is done as well.

Summarize data on the financial and organization level, which provides the billing files: billing detail, billing summary, and identifier list.

6. Loading all output data into the IBM Tivoli Usage and Accounting Manager DB completes the processing. There is an automatic duplicate detection that prevents us from duplicate data loading.

6.2 Syntax of main Job Runner directives

The main Job Runner job file directives are jobs, job, process, steps, and step. Additionally, there is the default directive that provides default parameters on each level. We explain these directives here.

Note: We recommend creating CSR+ records as input for the billing step, or, alternatively, use the Integrator Sort on the account code. The number of billing summary rows in the database can be reduced on a CSR file sorted by the account code. CSR+ data is automatically sorted by the bill process.


6.2.1 Jobs

The jobs directive is the primary directive structure of the job file. It contains global directives for the whole job. Typically, a job file only contains a single job, so a jobs directive is directly followed by only a job directive.

The arguments of a jobs directive are:

xmlns The name space for the XML file. You would put in xmlns=”http://www.ibm.com/TUAMJobs.xsd” for an IBM Tivoli Usage and Accounting Manager job. This is required for the jobs directive.

smtpServer The smtpServer that would be used to send notifications.

smtpFrom The indication for the source’s e-mail address.

smtpTo The destination’s e-mail address.

smtpSubject Subject line.

smtpBody Body text.

smtpSendJobLog Boolean parameter on whether or not include the job log in the body of the e-mail.

joblogFolder Explicitly specifying the log folder for the Job output. The default path is %HomePath%/logs/jobrunner/<jobid>.

processFolder Explicitly specifying where to write or read source and generated files. The default is under %HomePath%/processes/. This process folder is accessible by the %ProcessFolder% variable.

The jobs directive can only contain the job directive.

6.2.2 Job

The job directive is similar to the jobs directive. The specification on the jobs level applies. Most of the time, this is where you would specify these parameters.

The arguments of a job directive are:

id The name of the job (required). This name is used to determine the job log output folder.

description A descriptive name for the job.

dataSourceId An optional data source ID that specifies which database should be used for the job database connection, including the configuration settings and loading data. The value


defaults to the Default.Processing data source, as specified in the local registry.tuam.xml file.

processPriorityClassPriority of the job.

stopOnProcessFailureWhether or not to stop the processing if a step fails.

active Whether or not the job is active.

joblogShowStepOutputWhether or not to write the step output to the job log result.

joblogShowStepParametersWhether or not to show the step parameter in the job log output.

joblogWriteToDB This is not implemented in IBM Tivoli Usage and Accounting Manager V7.1.

joblogWriteToTextFileWhether or not a text file is created in the job log output directory.

joblogWriteToXMLFileWhether or not an XML file is created in the job log output directory, the ISC only uses the XML file for displaying the output; if this option is set to false, you cannot see the result from ISC.

smtpServer The smtpServer that would be used to send a notification.

smtpFrom The indication for the source’s e-mail address.

smtpTo The destination’s e-mail address.

smtpSubject Subject line.

smtpBody Body text.

smtpSendJobLog Boolean parameter for whether or not include the job log in the body of the e-mail.

joblogFolder Explicitly specifying the log folder for the Job output. The default path is %HomePath%/logs/jobrunner/<jobid>.

processFolder Explicitly specifying where to write or read source and generated files. The default is under %HomePath%/samples/processes/; this process folder is accessible by the %ProcessFolder% variable.


The job directive can contain the following directives:

� Defaults: Provides additional default parameters for the job elements.

� Process: This is the most common direct node under the job directive. You can have multiple processes that execute in parallel.

� Steps: Collection of step directives that must be executed sequentially for this job. This is typically put under a process directive.

6.2.3 Defaults

The defaults directive provides name value pairs for the containing level (job, process, or step). The defaults directive can contain any name and value pairs as arguments.

The defaults directive can contain the default directive. The default directive has the attribute name and value that can also be used to set any default name and value pairs. The reserved names that has special processing function are LogDate, RetentionFlag and programName.

6.2.4 Process

The process directive is used to signify a collection of steps directives that must be executed sequentially. It is common practice to put a process directive under a job (instead of steps directly) to allow flexibility when adding other process directives.

The arguments of a process directive are:

id The name of the process (required). This also indicates the sub folder for data files in the processes directory.

description A descriptive name for the process.

processPriorityClassProcess priority.

buildProcessFolder Whether or not the process folder is created (if it does not already exist).



active Whether or not to execute this process.


The process directive can contain the following directives:

� Defaults� Steps

6.2.5 Steps

The steps directive is a container for step directives. It only has a single argument, which is:

stopOnStepFailure Whether or not to stop the execution in a step that is considered failed or in error.

The steps directive can only contain the step directive.

6.2.6 Step

The step directive is the main specification of what the job is doing. It can be written differently depending on the function you are invoking. A step can also be invoked directly using the StepRunner Java program with the arguments of nodename, programName, and programType.

The arguments for the step directive are:

id A unique name for the step is required.

description A descriptive name for the step.

programName The name of the program.

type Program type. The only acceptable values are ConvertToCSR or process.

programType The type of program. Some types are Java, WSF, or console.

processPriorityClassStep priority.

buildProcessFolder This provides an override for the build process folder.



active Whether or not to execute this step.


The combination of only programName and programType determines the program or action that this step would invoke.

The step can contain the following directives:

� parameters: Collection of step parameters.

� Step specific directives. Depending on the programName and programType combination, these directives are mutually exclusive, and are only used with the corresponding program invoked:

– integrator– generateexternalfile – acct– bill– dbload– dbpurge– jobfileconversion– generatexmlfile – cimswindisk or windisk– cimswineventlog or wineventlog

6.3 Integrator program

The integrator program is a specialized Java program that can contain multiple stages. This program is used to manipulate and convert a CSR or CSR+ formatted file. The first stage is an input definition, while the last stage is called CSROutput. Each stage of the integrator program is a record processor; they process each record and pass it to the next stage, similar to pipeline processing.

An integrator step has both required and optional sections:

� <Input> is required and must have at least one of the following elements:

– <Collector>

– <Parameter>

– <File>

� <Stage name=”function”> processing stage is needed, and you may use as many as are needed.

� <Stage name=”CSROutput”> or <Stage name=”CSRPlusOutput”> is required.


The structure of an integrator step is illustrated in Figure 6-4.

Figure 6-4 A selection of the most common ConvertToCSR integrator functions

The processing of the integrator step depicted in Figure 6-4 is shown in Figure 6-5.

Figure 6-5 Integrator processing

The following sections discuss the stages of the integrator program.

<Step id=”integrator” programType=”java” type=”Process”><Integrator>

<Input name="CSRInput"> <Files><file name=”CSRinput.txt” /></files>

</Input><Stage name="CreateIdentifierFromValue" active="true"><Stage name="CreateIdentifierFromRegEx" active="true"><Stage name="Aggregator" active="true"></Stage>

<Parameters><Parameter defaultAggregation="false" /></Parameters>

</Stage><Stage name="ResourceConversion" active="true"><Stage name="CreateResourceFromValue" active="true"><Stage name="RenameFields" active="true"><Stage name="CreateIdentifierFromTable" active="true"></Stage><Stage name="CreateIdentifierFromIdentifiers" active="true"><Stage name="DropFields" active="true"><Stage name="Sort" active="true"></Stage>

<Stage name="CSROutput" active="true">

<Files><File name="CSRoutput.txt"/></Files></Stage>

</Integrator></Step>

StageCreateIdentifier

Lookup mapping

StageAggregate

StageSort

StageCreateIdentifierAccount_Code

CSR.txtInput

Collector/CSR

6.3.1 Input

We can choose one of several types for input. The keywords for input names are:

AIXAAInput AIX Advanced AccountingApacheCommonLogFormat

Apache HTTP server common logCollectorInput Specifying a collector program by the Collector nameCSRInput Standard CSR fileNCSAInput WebSphere collectorNotesDatabaseSizeInput

Lotus Notes collectorNotesEmailInput Lotus Notes collectorNotesUsageInput Lotus Notes collectorW3CWinLog Microsoft Internet Information Server collector

Specifically for the CollectorInput type, you can have the collector defined as follows:

DATABASE DatabaseDELIMITED Comma or tab delimited fileEXCHANGE2007 Microsoft Exchange serverFIXEDFIELD Fixed field filesTDS Tivoli Decision Support for z/OS database TPC TotalStorage Productivity CenterTRANSACTION CIMSTransaction table converterVMWARE Web Services SDK call to VMware Virtual Center WEBSPHEREXDFINEGRAIN

WebSphere collectorWEBSPHEREXDSERVER WebSphere collector

To specify the default folder for transferred collector files, we use the variable %CollectorLogs% in the path definition.

6.3.2 Processing

The processing stages can be read from <TUAM reference>. The stage functions are:

� Aggregator

Merging data where all the identifiers are the same and merging them into a single record by summarizing the resource values.

� CreateIdentifierFromIdentifiers

Copying, parsing, and merging identifiers into a new one.


� CreateIdentifierFromRegEx

Copying, parsing, and merging identifiers using a regular expression.

� CreateIdentifierFromTable

Using a text lookup table to search a matching entry and put it into an identifier.

� CreateIdentifierFromValue

Writing an identifier from a fixed string.

� CreateResourceFromConversion

Calculate a new resource from other resources.

� CreateResourceFromValue

Create a fixed values resource (we can create resource names longer than eight characters, but once we want to define them as a rate, the limitation of eight characters will stop us from using them).

� DropFields

Drop a field, either an identifier or a resource.

� DropIdentifiers

� Drop the identifiers field.

� DropResources

Drop the resources field.

� ExcludeRecsByDate

Filter some records by a certain date.

� ExcludeRecsByPresence

Filter some records because of the presence of a field.

� ExcludeRecsByValue

� Filter some records by the value for a field.

� IdentifierConversionFromTable

Change an identifier using the conversion from the table.

� IncludeRecsByDate

Filter records that do not have a certain date.

� IncludeRecsByPresence

Filter some records that does not have a certain field.

� IncludeRecsByValue

Only get the records that have a certain value.


� MaxRecords

Include only a number of records from the CSR file. This function is best for debugging a collection job.

� Prorate

Calculate a resource value based on prorating the value of the other resource.

� RenameFields

Rename an identifier or a resource in bulk.

� ResourceConversion

� Calculating a new value for a resource based on one or more resource values.

� Sort

Sort the CSR file records based on a certain identifiers’ value.

6.3.3 Output

The output types can only be in the CSROutput or CSRPlusOutput format. The output encloses a Files directive with a single File directive. A sample Output stage is shown in Example 6-2.

Example 6-2 Sample CSRPlusOutput stage

<Stage name="CSRPlusOutput" active="true"><Files>

<File name="%ProcessFolder%/server1/%LogDate_End%.txt" /></Files>

</Stage>

6.4 Account code mapping

Matching the CSR record identifier from the collected source to a proper account code that adheres to the account code structure is required for proper reporting. We collect the data in the CSR format, typically from the input collection process, as discussed in 6.3, “Integrator program” on page 119.

The recommended way of creating the Account_Code field is by using the Integrator. An older program called Acct is still valid for backward compatibilities. However, older programs like Acct should be made obsolete as you roll out new components, in favor of the integrator account conversion.


Figure 6-6 show the overview of an Account Code conversion.

Figure 6-6 The Account Code conversion using Integrator

CreateIdentifierFromTable

B,G, ITSOFINANCE_____WINDOWS_____H,R, ITSOADMIN_______LINUX_______S,Z, ITSOBACKOFFICE__MVS_________

CreateIdentifierFromIdentifier

Account_Code = ACCTMP + SYSID

DropFields

ACCTMP

SYSID,SC67 ACCTMP:ITSOBACKOFFICE__MVS_________

SYSID,LNXT ACCTMP:ITSOADMIN_______LINUX_______

ITSOBACKOFFICE__MVS_________SC67____

ITSOADMIN_______LINUX_______LNXT____

SYSID,SC67

SYSID,LNXT

SYSID,ABC

SYSID,SC67 ACCTMP:ITSOBACKOFFICE__MVS_________

SYSID,LNXT ACCTMP:ITSOADMIN_______LINUX_______

SYSID,ABC

SYSID,SC67 Account_Code:ITSOBACKOFFICE__MVS_________SC67____

SYSID,LNXT Account_Code:ITSOADMIN_______LINUX_______LNXT____

Exception


In Figure 6-6 on page 124, we show that the SYSID is used as the key to look up the value of the ACCTMP field based on the conversion table (AcctTabl.txt). If there is a record that does not have a matching result, the record is sent to the exception file. The next stage appends the SYSID to ACCTMP to create the Account_Code identifier. Then we can remove the ACCTMP field. Example 6-3 shows the integrator implementation of Figure 6-6 on page 124.

Example 6-3 Account conversion using Job Runner Integrator

<Stage name="CreateIdentifierFromTable" active="true">

<Identifiers><Identifier name="ACCTMP">

<FromIdentifiers><FromIdentifier name="SYSID" offset="1" length="10"/>

</FromIdentifiers></Identifier>

</Identifiers><Files>

<File name="/opt/ibm/tuam/processes/Accttabl.txt" type="table"/><File name="Exception-%LogDate_End%.txt" type="exception"

format="CSROutput"/></Files><Parameters>

<Parameter exceptionProcess="true"/><Parameter writeNoMatch="false"/><Parameter sort="true"/><Parameter upperCase="false"/><Parameter modifyIfExists="true"/>

</Parameters></Stage><Stage name="CreateIdentifierFromIdentifiers" active="true">

<Identifiers><Identifier name="Account_Code">

<FromIdentifiers><FromIdentifier name="ACCTMP" offset="1" length="28"/><FromIdentifier name="SYSID" offset="1" length="8"/>

</FromIdentifiers></Identifier>

</Identifiers><Parameters>

<Parameter modifyIfExists="true"/><Parameter keepLength="true"/>

</Parameters></Stage><Stage name="DropFields" active="true">

<Fields> <Field name="ACCTMP"/>

</Fields></Stage>

Using the CreateIdentifierFromTable function, you can specify whether to use exception processing with the parameter exceptionProcess. If it is true, all unmatched identifiers will be collected in a exception file, keeping the structure of the input file for this step; otherwise, the identifier is added with a blank value.

The conversion table for CreateIdentifierFromTable is case sensitive. You can use the upperCase=true parameter to indicate that the FromIdentifier field is converted to upper case before matching occurs.

The file specified will be overwritten unless you add the variable %LogDate_End% to the definition. There will be no accumulation from the last processing, and we do recommend a separate reprocessing job; otherwise, you would need to unload all the data and reprocess the complete job once the account table is updated.

6.5 Non-integrator steps

The step is mainly governed by the progamType and programName attributes. These attributes determine the way processing is performed. Our test indicates that the type attributes, though they is required, does not affect processing. Table 6-1 shows a combination of programName and programType and the associated program they actually invoke. Other combinations may exist for maintaining backward compatibilities.

Table 6-1 Program combinations

programType programName Invoked program

Java Integrator integrator.StepRunIntegrator

Java SendMail mail.StepRunMail

Java Acct acct.StepRunAcct

Java Bill bill.StepRunBill

All the directives under steps have the following general attributes:



processFolder Provides an override for the process folder. This does not apply to the mail program. Note that scan, sort CleanUp, Scan, FileTransfer, and WaitFile uses ProcessFolder (an uppercase P).

dataSourceId Provides an override for data source access in the associated step. This is only used for Load, Purge, and JobConversion.

dbConfigurationFile Database configuration file for Acct and Bill. This does not seem to be used.

Java Sort sort.StepRunSort

Java DBLoad load.StepRunLoad

Java DBPurge purge.StepRunPurge

Java JobFileConversion jobfileconversion.StepRunJBConversion

Java Rpd rpd.StepRunRpd

Java Scan scan.StepRunScan

Java Cleanup cleanup.StepRunCleanupScan

Java FileTransfer filetransfer.StepRunFileTransfer

Java WaitFile waitfile.StepRunWaitFile

Java <java program name> java.StepRunJava

Console <program name> console.StepRunConsole

WSF <WSF script name> wsf.StepRunWSF

Java SingleProcessStepa StepRunAcct - StepRunSort - StepRunBill

a. A special step that has the programName of SingleProcessStep and programType of Java would generate an automatic job with a set of accounting processing (StepRunAcct), sorting (StepRunSort), and billing (StepRunBill) steps.

programType programName Invoked program


We discuss, in the following sections, the detailed parameters and processing function of each invoked program:

� “Mail” on page 128� “Acct” on page 128� “Bill” on page 130� “Cleanup” on page 131� “Sort” on page 132� “DBLoad” on page 132� “DBPurge” on page 133� “Scan” on page 133� “Windows script file” on page 136� “File transfer” on page 134� “Wait file” on page 135� “Remote product deployment” on page 135� “Job conversion” on page 135� “Java” on page 136� “Console” on page 136

The discussion of the integrator is provided in 6.3, “Integrator program” on page 119.

6.5.1 Mail

The mail step allows you to send an e-mail message. The applicable parameters are:

SMTPServer The SMTP server that would be used to send notificationFromEmail The indication for the source’s e-mail addressToEmail The destination’s e-mail addressSubject Subject lineBody Contents of the e-mailAttachFileLocation Files that you would attach to the e-mail

6.5.2 Acct

The acct process derives account code information based on an account code lookup file (Accttbl.txt). This program is provided as a backward compatibility option to existing jobs. The newer recommended method is to use the integrator step’s CreateIdentifierFromTable stage to derive a new identifier for the account code field.

Before the acct program is run, a temporary step XML file is created. The file is created in the ProcessFolder with the step’s ID as a name. This program can be


invoked directly using the Java class com.ibm.tuam.acct.AcctMain and supplying <processFolder> and step.xml as arguments.

The applicable parameters are:

inputFile Input file name (The default is CurrentCSR.txt.).

outputFile Output file name (The default is AcctCSR.txt.).

inputFileEncoding Encoding of input file.

outputFileEncoding Encoding of output file.

controlFile Control parameters (The default is AcctCntl.txt.).

exceptionFile Exception file name (records that cannot be matched).

ControlCard Content of control file in line.

ProcessFolder Processing folder name.

Trace Set tracing to true or false.

accCodeConvTable Account code conversion table text file (The default is Accttbl.txt.).

accCodeConvTableEncodingEncoding of the conversion table file

The account processing is illustrated in Figure 6-7.

Figure 6-7 Accounting process

AcctTabl.txt

A, E, acct1F, N, acct2O, Z, acct3

CurrentCSR.txt AcctCSR.txt

Exception.txt


6.5.3 Bill

The bill process processes the usage data that already has an account code to generate billing information. As discussed in 4.2, “Account code hierarchy” on page 82, an account code is used to get the rate table and find the rate for each resource in the CSR file. The result of this process is three files:

BillSummary.txt Billing summary in which each account and resource has the usage and money value shown.

BillDetail.txt Billing detail in which a record is provided that contains account code and usage entries referring to the identifier.

Ident.txt Identifiers that are referred to by the billing files.

Before the bill program is run, a temporary step XML file is created. The file is created in the ProcessFolder with the step’s ID as its name. This program can be invoked directly using the Java class com.ibm.tuam.bill.BillMain and supplying <processFolder> and step.xml as arguments.


inputFile Input file name (the default is AcctCSR.txt). CSR+ files are recommended, as they can be sorted by the billing program for optimization.

Figure 6-8 on page 131 shows an overview of the bill process.


Figure 6-8 The bill process overview

6.5.4 Cleanup

The cleanup step defines the option to clean up the processing directory for older files. It can either remove the files by date or by age. The applicable parameters are:

DaysToRetainFiles The age of the files to retain. DaysToRetainFiles and DateToRetainFiles are mutually exclusive. If both are specified, DaysToRetainFiles will be used.

DateToRetainFiles The date that denotes the oldest file to retain.

Folder Folder name to clean up. The default is ProcessFolder/jobid.

Note: We recommend using a CSR file sorted by the account code as the input file or use a CSR+ file, which is sorted by the billing automatically.

ITUAM DatabaseBill process

controlCardNORMALIZE CPU

Billing

Rate Table including

CPU check mark .

BillSummary.txt

CPU Normalization Table

Normalization

AcctCSR.txt

BillDetail.txtIdent.txt

CIMSClient Table

selectRate Table

resources

identifiers1 resources1

identifiers2 resources2

identifiers1

identifiers2

resources1

resources2


Clean Sub Folders Whether or not to clean all sub folders.

6.5.5 Sort

The sort step provides a mechanism for sorting a CSR file line by line. This sort program does not allow you to select the identifiers to sort on. The applicable parameters are:

Input File Name Input file. The default is AcctCSR.txt.Output File Name Output file name. The default is AcctCSR.txt.

6.5.6 DBLoad

The load step provides the capability to load data into the database. Data is typically loaded from billing output files.

Before the database load program is run, a temporary step XML file is created. The file is created in the processFolder with the step’s ID as its name. This program can be invoked directly using the Java class com.ibm.tuam.load.DBLoadMain and supplying <processFolder> and step.xml as arguments.


resourceFile File name for the resource data.

processFolder Folder to get the files.

Trace Whether or not to perform tracing.

detailFile File name for the detail data.

allow Detail DuplicatesWhether or not to allow duplicate loads on the detail file.

summaryFile File name for the summary data.

allow Summary DuplicatesWhether or not to allow duplicate loads on the summary file.

onEmptyFile Status that indicates if an empty file is found. Possible values are Success, Warning, or Fail.

identFile File name for the identifier.

encoding File encoding.

Tip: For a more specific sort, based on identifiers, we use the Integrator sort, which is described in 6.3, “Integrator program” on page 119.


loadType Detail, Summary, Ident, All, or Resource.

bulkLoad Whether to invoke the load as a bulk process.

6.5.7 DBPurge

The purge step provides the method to purge data in the IBM Tivoli Usage and Accounting Manager database.

Before the purge program is run, a temporary step XML file is created. The file is created in the processFolder with the step’s ID as its name. This program can be invoked directly using the Java class com.ibm.tuam.purge.DBPurgeMain and supplying <processFolder> and step.xml as arguments.


Months To Keep Number of months to retain data, if specified. The start and end date are ignored.

StartDate Optional start date for purging.

EndDate Optional end date for purging.

Purge Summary Whether or not to purge the summary table.

Purge Bill Detail Whether or not to purge the billing detail table.

PurgeIdent Whether or not to purge the identifier table.

Purge Acct Detail Whether or not to purge the account detail table.

PurgeClient Whether or not to purge the client table.

PurgeRate Whether or not to purge the rate table.

DataSourceID ID of the data source to be accessed.

6.5.8 Scan

The scan step provides the facility of merging multiple CSR files in the processing folder into a single CSR file. The applicable parameters are:

Use LogDate Range Log date range to be merged.

LogDate A single log date to merge.

Retain File Date Determine the output file name. If Retain File Date is true, the file name is set to the end date of the log date. If false, the output file name is CurrentCSR.txt.

Retain Date Flag Whether or not to retain the file date (same as Retain File Date).


ExcludeFile Exclude merging specified files.

Exclude Folder Exclude merging specified folders.

IncludeFile Include specific files.

Use Step Files Use files generated from previous steps.

Allow Missing Files Allow any files that are not found.

Allow Empty Files Allow files to be empty.

6.5.9 File transfer

The file transfer program provides a facility to perform file transfer between systems. It provides several different methods for performing file transfer, such as ftp, scp, sftp, or smb.


continue On Error Whether to stop or continue when an error occurs.

type Transfer type. The keywords are ftp, file, win, windows, ssh, rsh, and rexec.

overwrite Whether to overwrite the file if it is already there.

ServerName The target server name.

UserId The user ID to be used.

UserPassword The password to be used.

from* Source directories.

to* Target directories.

Some additional parameters for ftp:

OpenType® FTP site typeTransferType Ascii or binary transfer

Additional parameter for secure transfer:

Key Store File Name File to store SSL certificates


6.5.10 Wait file

This waitfile step waits until a file becomes available. The applicable parameters are:

FileName File name to wait for arrival.

Polling Interval The duration between checks for the file.

TimeOut The total time to wait for the file. This is the value that is used if both TimeOut and TimeOut Date Time exists.

TimeOut Date Time The time stamp when the program should stop waiting.

6.5.11 Remote product deployment

The remote product deployment (rpd) provides a mechanism to perform file transfer and product installation. This program is mainly used for deployment of collector and AIX advanced accounting collection. This uses the same mechanism as the file transfer process discussed in 6.5.9, “File transfer” on page 134.

The applicable arguments are:

Host Target host.

UserId User ID to use.

Password Password to use.

Manifest The XML file name that describe the action sequences to do.

RPD Parameters Various parameters for RPD program as requested by the Manifest. This is in the form of keyword value pairs.

SourcePath The path where the files to be transferred reside.

6.5.12 Job conversion

This job conversion step is a stand-alone Job runner step for converting IBM Tivoli Usage and Accounting Manager V6.x job files into a V7.1 job format. The applicable parameters are:

input Folder Input conversion folderoutput Folder Output conversion folderover Write Output Folder

Whether or not to overwrite any files that already exist


6.5.13 Windows script file

The Windows script file (WSF) step is a special step that runs Windows Script File. It typically contains a Microsoft Visual Basic® program. The execution uses the csript.exe command. The Visual Basic program is embedded in the programName argument of the step. The parameters for this step are passed to the script directly.

6.5.14 Java

The Java step allows you to run arbitrary Java programs. This is typically to invoke your own Java function or conversion step. You must supply the appropriate library and command-line options for the Java program. The applicable parameters are:

Use Command ProcessorWhether to invoke the command processor or invoke the Java class directly

Use Standard ParametersWhether or not to use standard JVM™ parameters

Java Command Line Command-line argument for the Java Virtual Machine

JavaHome Home directory of the Java executable

6.5.15 Console

The console step allows you to invoke a program on the operating system level. The applicable parameter is:

Use Command ProcessorWhether or not to invoke the command processor

Note: There is another conversion for old Conversion Builder files into an Integrator stage, which will be not discussed in this book.


Chapter 7. Problem determination

This chapter discusses troubleshooting procedures for IBM Tivoli Usage and Accounting Manager V7.1. The discussion is covered in the following sections:

� 7.1, “Job failures” on page 138

� 7.2, “Database connection” on page 140

� 7.3, “Web reporting problems” on page 141

� 7.4, “Trace level” on page 141

7


7.1 Job failures

One of the most important aspects of IBM Tivoli Usage and Accounting Manager are the jobs used to collect usage information from the system log. There are several steps that can be performed whenever you run into problems with jobs.

When performing problem determination for jobs, there are several problem determination sources:

� Job logs output from the running jobs

Job logs can be in plain text format or XML format. The XML job log is for display in the Integrated Solutions Console, while the plain text job log is easier for us to read. For job log analysis details, refer to 7.1.1, “Job logs” on page 138.

� Output files from the processing stages

Analyzing the output of the processing stages allows for deeper problem determination about logic problems of the job. You must identify the default file names for some stages, as some of the files are produced by default. Refer to 7.1.2, “Output files” on page 139 for more information.

7.1.1 Job logs

Job logs can be read from the Integrated Solutions Console menu by selecting Usage and Accounting Manager → Chargeback Maintenance → Job Runner → Log Files. The log files are organized based on the date the job was executed. You can then open the job log by expanding the job.

Job log messages are arranged in a job - processes - step - stage hierarchy. You can quickly identify problems in a specific step or stage by looking at items identified by a red X for error or a yellow triangle for warning. A sample log file is shown in Figure 7-1 on page 139.


Figure 7-1 The Job Runner log viewer GUI for analyzing the detailed job output

Finding the error message and correcting it is the objective of the problem determination process. You can look this message up in IBM Tivoli Usage and Accounting Manager Reference manual, found at the following address:

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.ituam.doc/ref/tuam_pdf_reference.pdf

A common example is AUCPE02000W – The rate id xxxxxx is not defined. For this message, you must decide whether this resource (rate ID) is needed or not for recording. Define the unidentified rate in the database, as discussed in 4.5, “Working with rates” on page 92.

7.1.2 Output files

Some of the programs have a default output file name. The output files are stored under the processing directory path defined by the IBM Tivoli Usage and Accounting Manager configuration. The sub-path for the output file is the process name.

� The scan program is used to consolidate data from feed subdirectories into one processing file. The default output file is CurrentCSR.txt.

Chapter 7. Problem determination 139

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.ituam.doc/ref/tuam_pdf_reference.pdf

� The acct program is used to perform account code conversion on data. It generates the file AcctCSR.txt that contains the records with the account_code string. If the record cannot be matched from the lookup table, the record is written to the exception file in Exception.txt file.

� The bill program is used to collect resource usage information and applies rate information. The bill program generates billing information in BillDetail.txt, which consists of detailed usage for each identifiers combination, and BillSummary.txt, which contains summary billing information for a specific account_code. It also generates identifier lists, which qualifies each usage detail with a identifier mix in the file Ident.txt.

7.2 Database connection

The Integrated Solution Console is heavily dependent on the database. Any problem with the database reduced the console’s functionality. Some of the IBM Tivoli Usage and Accounting Manager configuration information, such as path information, is stored in the database.

While the jobs only access the database during the DBload and DBpurge stages, the ISC requires a database connection. When the ISC database connection fails, you must diagnose and correct the issue so that the database connection can be reestablished.

You can discover the cause of the problem by reading the current Trace and Message log records:

� If the database is inaccessible, log into the Database Management interface and check the status of the database server. If the database server is stopped, restart it.

� When the problem is an authorization one, ensure that the user ID and password used by IBM Tivoli Usage and Accounting Manager to connect to the database is correct. You can check the data source connection by selecting Usage and Accounting Manager → System Maintenance → Data Source, and then modify the user ID or password and test the connection.


7.3 Web reporting problems

One of the most common problems of the Web Reporting interface is report generation timing out. Some of the IBM Tivoli Usage and Accounting Manager tables can be quite large, so the processing to generate a report can sometimes exceed the established timeout. the timeout can be caused by several things:

� A network issue, such as a slow connection for report data transfer.

� A data volume issue. You can correct this issues by limiting the time range of the selection.

To change this timeout value, start the Integrated Solutions Console, select Usage and Accounting Manager → System Maintenance → Configuration, and select the Reporting tab. Verify the Report Script Timeout value, which can be 600 – 2700 seconds. Then you can reverify the running of the report.

7.4 Trace level

Logging and tracing for general processing of IBM Tivoli Usage and Accounting Manager can be managed as follows:

� Start the Integrated Solutions Console, select Usage and Accounting Manager → System Maintenance → Configuration, and click the Logging tab.

� Set Trace file setting. The trace message level can be set to FINE, FINER, or FINEST. We recommend starting with FINEST, which will output all messages, and then adjust the setting later as necessary. Look in the trace file and see which messages are controlled by this setting. The messages controlled by this setting will start with FINE, FINER, or FINEST.

� Set Log file setting. The log message level can be set to SEVERE, WARNING, or INFORMATION. We recommend starting with INFORMATION, which will output all messages, and then adjust the setting later as necessary. Look in the log file and see which messages are controlled by this setting. The messages controlled by this setting will start with SERVER, WARNING, or INFORMATION.

Chapter 7. Problem determination 141

Chapter 8. Web reporting

This chapter discusses about reporting in IBM Tivoli Usage and Accounting Manager V7.1. The discussion is covered in the following sections:

� 8.1, “Web reporting interface and user authority” on page 144

� 8.3, “Producing reports” on page 153

� 8.4, “Defining a new report” on page 155

8


8.1 Web reporting interface and user authority

To access the Web reporting interface, do the following steps:

1. Log in to the reporting Web application by going to the address http://localhost/login.aspx. Alternatively, on the Windows platform where IBM Tivoli Usage and Accounting Manager is installed, select Start → All Programs → IBM Usage and Accounting Manager → Windows Web Reporting.

2. When the reporting login page appears with the manual logon option, enter admin in the User ID field and password in the Password field. If you have auto logon configured for Web reporting, you would be automatically signed on with the message:

Welcome username, you are currently signed on as user ID.

The user ID for the reporting system is stored in the IBM Tivoli Usage and Accounting Manager database. During database initialization, IBM Tivoli Usage and Accounting Manager adds a default user and user group that has administrative privileges in IBM Tivoli Usage and Accounting Manager Web Reporting and can view all reports and clients. The ID for the default user is admin and the password is password. The user admin belongs to the default user group named Admin.

3. To change the password for the user, select the Change Password check box and then click OK. On the Change User Password page, type the current password and the new password as directed. The password is alphanumeric and case-sensitive and can be a maximum of 16 characters. Click OK to change the password and return to the home page.

4. User access to the reporting interface is administered from the Integrated Solution Console. Select Usage and Accounting Manager → System Maintenance → Users to manage and add users, and select Usage and Accounting Manager → System Maintenance → User Groups to manage user groups and to associate a user to a user group.

5. By default, new users are added to the Admin group, which has administrative access enabled and full access to all reports (that is, members of the group have access to all reports). You can restrict user access to reports by:

a. Creating a group or groups that do not have administrative access enabled (the Allow Administrative Access check box is not selected).

b. Clicking the View pop-up menu icon for Reports Allowed and either add the Report Opens the Available Reports page, where individual reports can be added to the user group, or select Allow All Reports to add all reports to the user group. In this window, you can also remove an assigned report by clicking Remove.


c. Adding the appropriate users (users that belong to a group that have administrative access enabled have access to all reports).

d. Ensuring that the Use Report Access Security check box on the Configuration—Reporting page is selected (this check box is selected by default). If this check box is not selected, all users can access all reports regardless of whether administrative access is enabled for their group.

8.2 Web reports

The following are the available Web reporting reports that are provided by IBM Tivoli Usage and Accounting Manager.

Account Budget for Period and YTD reportThe Account Budget for Period and YTD report provides actual, budget, and difference charges by account code for the parameters selected. This report includes totals for the calendar period selected and year to date (YTD).

Account Summary by Week reportThe Account Summary by Week report provides the total weekly and monthly charges by account code and rate code description for the parameters selected.

Account Summary by Week-Wide reportThe Account Summary by Week-Wide report is similar to the Account Summary by Week report, except that the weeks are displayed across the top of the page.

Account Summary Daily 2 reportThe Account Summary Daily 2 report is similar to the Account Summary Daily report, except that the month (rather than the account code) appears at the top level of the report.

Account Summary Daily reportThe Account Summary Daily report provides total daily and monthly charges by account code and rate code description for the parameters selected.

Account Summary Week spreadsheetThe Account Summary Week spreadsheet provides account summary weekly information by account code for the parameters selected.

Chapter 8. Web reporting 145

Account Summary YTD Cost by Rate Group spreadsheetThe Account Summary YTD Cost by Rate Group spreadsheet provides account summary YTD information by rate code description for the rate group selected for the parameters selected.

Account Summary YTD by Rate spreadsheetThe Account Summary YTD by Rate spreadsheet provides account summary YTD information by rate code description for the parameters selected.

Account Summary YTD reportThe Account Summary YTD report provides the total monthly and YTD charges by account code, rate group, and rate code description for the parameters selected.

Account Summary YTD spreadsheetThe Account Summary YTD spreadsheet provides year-to-date account summary information, by account code, for the parameters selected.

Account Summary YTD-Wide reportThe Account Summary YTD-Wide report is similar to the Account Summary YTD report; however, the months are displayed across the top of the page.

Account Total Invoice reportThe Account Total Invoice report provides the total charges by each level of the account code structure for the parameters selected.

Alternate Invoice reportThe Alternate Invoice report provides charges by account code and rate code description for the parameters selected. An optional graph showing total expenses by account code is also included.

Batch report The Batch report provides z/OS batch job data for the parameters selected. This data is taken from the CIMSDetail table.

CICS Transaction reportThe CICS Transaction report provides data for CICS transactions by transaction ID for the parameters selected. This data is taken from the CIMSDetail table.

Client report The Client report provides the information contained in the CIMSClient table for the parameters selected.

Configuration report The Configuration report provides information contained in the CIMSConfig table.


Cost Trend report The Cost Trend report provides total charges by account code for each month of the year for the parameters selected. Monthly charges for each account code are presented on a single line. To print this report, use landscape mode on legal paper.

Cost Trend-Accounts Graph reportThe Cost Trend Accounts Graph report provides the total charges for all account codes for each month for the parameters selected followed by charges for individual account codes for each month.

Cost Trend by Rate reportThe Cost Trend by Rate report provides total charges by rate code description and rate group for each month of the year for the parameters selected. To print this report, use landscape mode on legal paper.

Cost Trend-Rates Graph reportThe Cost Trend Rates Graph report provides the total charges for all rate codes for each month for the parameters selected followed by charges for individual rate codes for each month.

Cost Variance Drill Down reportThe Cost Variance Drill Down report provides a comparison of charges by rate code description and rate group for a specified month and the month prior for the parameters selected.

Cost Variance report The Cost Variance report provides a comparison of charges by account code, rate code description, and rate group for a specified month and the month prior for the parameters selected.

Daily Crosstab Charges reportThe Daily Crosstab Charges report provides total daily charges by account code and rate code description for the parameters selected.

Daily Crosstab Usage reportThe Daily Crosstab Usage report provides total daily resource usage by account code and rate code description for the parameters selected.

DB2 Summary reportThe DB2 Summary report provides DB2 data for the parameters selected. This data is taken from the CIMSDetail table.


Detail by Identifier Crosstab reportThe Detail by Identifier Crosstab report provides total charges by rate code for a selected identifier value or values for the date range selected.

Detail by Identifier by Date Crosstab reportThe Detail by Identifier by Date Crosstab report provides total and total daily charges by rate code for a selected identifier value or values for the date range selected.

Detail by Rate Group/Identifier reportThe Detail by Rate Group/Identifier report is similar to the Detail by Rate Group report. However, in the Rate Group/Identifier report, the resource units are broken down by identifier value for the identifier name selected.

Detail by Rate Group reportThe Detail by Rate Group report provides total resource units used for the first eight rate code descriptions in a rate group for the parameters selected. If applicable, a total for the next highest level of the account code appears.

Detail Rate Codes by Identifiers reportThe Detail Rate Codes by Identifiers report shows resource units consumed for a maximum of five rate codes and five identifiers.

Detail Rate Codes by Identifiers/Account reportThe Detail Rate Codes by Identifiers/Account report shows resource units consumed by account code for a maximum of five rate codes and five identifiers.

Disk Directory Resource reportThe Disk Directory Resource report provides Windows disk storage data for the parameters selected. This data is taken from the CIMSDetail table.

Invoice by Account Code spreadsheetThe Invoice by Account Code spreadsheet provides invoice information by account code for the parameters selected.

Invoice by Account Level reportThe Invoice by Account Level report provides charges by account code, rate group, and rate code description for the parameters selected. An optional graph showing total expenses by account code is also included.


Invoice by Rate Group spreadsheetThe Invoice by Rate Group spreadsheet provides invoice information for the rate codes within a selected rate group for the parameters selected.

Invoice Drill Down for Rate Group reportThe Invoice Drill Down for Rate Group report enables drill down of the charges for a rate group by identifier name.

Invoice Drill Down for Rate Group by Date reportThe Invoice Drill Down for Rate Group by Date report is similar to the Invoice Drill Down for Rate Group report. However, it also provides a breakdown of the data by date.

Invoice Drill Down for Units reportThe Invoice Drill Down for Units report enables drill down of resource units by up to five identifier names.

Invoice report The Invoice report provides charges by account code, rate code description, and rate group for the parameters selected.

Invoice spreadsheet The Invoice spreadsheet provides invoice information for the parameters selected.

Invoice with Shifts reportThe Invoice with Shifts report provides charges by account code, rate group, and rate code description broken down by shift for the parameters selected, if the CIMSSummary table contains multiple shift codes for a rate code.

Line Item Budget for Period and YTD reportThe Line Item Budget for Period and YTD report provides actual, budget, and difference charges by account code, rate group, and rate code description for the parameters selected.

Monthly Crosstab Charges reportThe Monthly Crosstab Charges report provides total monthly charges by account code and rate code description for the parameters selected.

Monthly Crosstab Usage reportThe Monthly Crosstab Usage report provides total monthly resource usage by account code and rate code description for the parameters selected.


MS Exchange 2000 Resource reportThe MS Exchange 2000 Resource report provides Exchange 2000 Server data for the parameters selected. This data is taken from the CIMSDetail table.

MS SQL Server 2000 Resource reportThe MS SQL Server 2000 Resource report provides SQL Server 200 trace file data for the parameters selected. This data is taken from the CIMSDetail table.

Percentage report The Percentage report provides the total charge by account code for the parameters selected and specifies the percentage of that charge in relationship to the total charges for all account codes. This report also provides a breakdown of the percentage by rate group and rate code description for each account code.

Rate report The Rate report provides the information contained in the CIMSRate and CIMSRateGroup tables.

Report Both templateThe Report Both template produces Both reports that show resource usage and charges by account codes and rate code description for the parameters selected.

Report Cost templateThe Report Cost template produces Cost reports that show charges by account code and rate code description for the parameters selected.

Report Resource templateThe Report Resource template produces resource reports that show resource usage by account code and rate code description for the parameters selected.

Resource Trend Graph reportThe Resource Trend Graph report provides the total resource usage for all rate codes for each month for the parameters selected followed by resource usage for individual rate codes for each month.

Resource Usage Trend reportThe Resource Usage Trend report provides total resource usage by rate code for each month of the year for the parameters selected. It is ordered by account code, rate group, and rate code. To print this report, use landscape mode on legal paper.


Resource Variance reportThe Resource Variance report provides a comparison of resource usage by account code, rate group, and rate code description for a specified month and the month prior for the parameters selected.

Run Total Invoice reportThe Run Total Invoice report provides total charges by rate group and rate code description for the parameters selected.

Run Total Invoice spreadsheetThe Run Total Invoice spreadsheet provides total invoice information by rate code for the parameters selected.

Run Total Invoice with Shifts reportThe Run Total Invoice with Shifts report shows the units, rates, and charges for each rate code description, by shift. The CIMSSummary must contain more than one shift code for a rate code before that information can be broken down by each shift.

Run Total Percent reportThis report is the same as the Run Total Invoice report, except that the drill down includes percent total by account code in addition to units, rate, and charge.

Run Total Rate Group Percent reportThis report provides charges and percentage by rate groups for the parameters selected.

Spreadsheet Both templateThe Spreadsheet Both template produces Both spreadsheets that show resource usage and charges by account code and rate code description for the parameters selected.

Spreadsheet Cost templateThe Spreadsheet Cost template produces Cost reports that show charges by account and rate code description for the parameters selected.

Spreadsheet Resource templateThe Spreadsheet Resource template produces Resource spreadsheets that show resource usage by account and rate code description for the parameters selected.


Summary Crosstab Charges reportThe Summary Crosstab Charges report provides total charges by account code and rate code description for the parameters selected.

Summary Crosstab Usage reportThe Summary Crosstab Usage report provides total resource usage by account code and rate code description for the parameters selected.

Summary by Rate Group Crosstab Charges reportThe Summary by Rate Group Crosstab Charges report provides total charges by account code and rate code description for the rate codes within a selected rate group for the parameters selected.

Summary by Rate Group Crosstab Usage reportThe Summary by Rate Group Crosstab Usage report provides total resource usage by account code and rate code description for the rate codes within a selected rate group for the parameters selected.

Top 10 Accounts for Rate spreadsheetThe Top 10 Accounts for Rate spreadsheet provides the account codes with the highest usage of a specified rate code for the parameters selected. For example, if you type 3 as the Top N parameter, the three account codes with the highest rate code usage appear. If you leave the Top N parameter blank, the account codes with the ten highest rate code usage appear.

Top 10 Bar Graph reportThe Top 10 Bar Graph report is similar to the Top Cost report. However, it provides accounts codes with the 10 highest charges for the parameters selected and it provides the data in bar graph as well as table format.

Top 10 Pie Chart reportThis report is similar to the Top Cost Report. However, it provides accounts codes with the 10 highest charges for the parameters selected, and it provides the data in pie chart as well as table format.

Top Accounts for Rate reportThe Top Accounts for Rate report provides the account codes with the highest usage of a specified rate code for the parameters selected. For example, if you type 3 as the Top N parameter, the three account codes with the highest rate code usage appear. If you leave the Top N


parameter blank, the account codes with the ten highest rate code usage appear.

Top Cost report The Top Cost report provides the account codes with the highest charges for the parameters selected. For example, if you type 3 as the Top N parameter, the three account codes with the highest charges appear. If you leave the Top N parameter blank, the account codes with the ten highest charges appear.

Transaction report The Transaction report provides the Miscellaneous, Recurring, and Credit transactions for the parameters selected.

Weekly Crosstab Charges reportThe Weekly Crosstab Charges report provides total weekly charges by account code and rate code description for the parameters selected.

Weekly Crosstab Usage reportThe Weekly Crosstab Usage report provides total weekly resource usage by account code and rate code description for the parameters selected.

8.3 Producing reports

There are two types of reports in IBM Tivoli Usage and Accounting Manager. Reports that can contain usage data for processing in a spreadsheet application or can contain invoices for billing to customers or departments. To produce the reports, do these steps:

1. Log in to the reporting Web application. Go to the address http://localhost/login.aspx.

2. When the reporting login page appears, enter admin in the User ID field and password in the Password field.

3. From the reports tool bar, click Run Reports. This shows the list of available reports, which is shown as an expandable tree. The categories are:

– Invoices– Account Reports– Top Usage Reports– Trend, Resource Detail– Other– Custom


4. You can also select Run Spreadsheets. There are two types of spreadsheet: Standard and Crosstab.

5. Select the desired report or spreadsheet. Clicking it will bring up the Parameter page. Provide the appropriate report parameters. Some of the typical parameters are:

Account Code Structure nameThis can be the standard structure or any other alternative structure.

Account Code Level The account code level that is required to view the report. For example, the account code AABBBBCCC might contain three levels: the two-digit company code AA, the 6-digit division code AABBBB, and the 9-digit department code AABBBBCCC. The resource use and charge data in the generated report reflects the level that has been select.

Starting and Ending Account Code This parameter works in conjunction with the Account Code Level parameter and specifies the range of account codes for that level that appear in the report. If all account codes for that level are to appear in the report, click Lowest Possible Account for the starting account code and Highest Possible Account for the ending account code. If specific account codes are required, click the appropriate start and end codes, or click Custom and input the start and end codes.

Invoice Number Some invoice reports contain separate invoices for the selected account codes. If this parameter is blank (the default), invoice numbering begins with 1. Use this parameter to begin invoice numbering from another number, if necessary. The administrator determines whether this parameter is displayed for invoices. If this parameter is not available, the invoice number set in the CIMSConfigOptions table in the database is used, and invoice numbers continue to increase sequentially each time an invoice is run. For example, if the last invoice in a report was 99, the next invoice that is run will begin with invoice number 100.

Date Range The date range filters the view of the report. Dates for a report refer to the reporting period that was assigned when the report was created.

6. Click OK. The report runs and appears.


8.4 Defining a new report

Although IBM Tivoli Usage and Accounting Manager provides plenty of predefined reports, eventually you may need to define additional reports that only select a subset or a super-set of data that is not available in the standard reports. Thus, you must define a new report or a new spreadsheet. To define a new report, do these steps:

1. Log in to the reporting Web application at the address http://localhost/login.aspx. Select the report that most closely matches the one you need.

2. Select Reports → Create a Report. The Create a Report page opens. Specify or update the following parameters for the report:

Report Select New to create a new report or spreadsheet or select an existing report or spreadsheet to update the report or spreadsheet.

Type Select the report or spreadsheet type that you want to create. You can select one of the following types:

• Resource (resource usage by account and rate code description)

• Cost (charges by account and rate code description)

• Both (resource and cost information)

Name Specify a name that you want to assign to the report or spreadsheet. The name is used to identify the report or spreadsheet in the list of published reports or spreadsheets, search queries, or designated as a favorite report or spreadsheet on the Home page.

Description Enter a descriptive summary of the report or spreadsheet.

Visible to all users Check to make the report or spreadsheet available to all Web users. Deselect to make the report or spreadsheet available only to you. This check box is unchecked by default.

Resource For each column box, select the rate code that you want to appear in that column. You can select up to four columns for Resource reports and eight columns for Cost or Resource reports.


Decimal Places Specify the number of decimal digits that you want to appear in the resource units. For example, if you specify two decimal digits, the resource usage amount is displayed as follows: 65.03.

3. If you are creating a new report, click New or click Update if you are updating a report or spreadsheet. The name and at least one rate code for an existing report or spreadsheet must be shown before you click Update.

4. After you create a report or spreadsheet, the report or spreadsheet is shown on the Reports or Spreadsheets page under a report group determined by the administrator.

8.5 Batch reporting

IBM Tivoli Usage and Accounting Manager provides an alternative way to produce reports. You do not need to log in and go through the Web reporting pages to create the report if you want to have the report run regularly. This capability is provided with batch reporting.

Batch reporting enables you to automate the generation of published reports. A published report is a report that has been saved with the data that was generated at the time the report was run. Publishing a report enables users to view a report without having to regenerate it. The report displays quickly because the data has already been read from the database and formatted.

Batch reporting also enables you to provide published reports to users in a way that best meets the needs of users, including attaching the report to an e-mail or including a link to the report in an e-mail.

The batch reporting is provided as an executable BatchReporting program under the lib subdirectory. To invoke batch reporting, you must publish the report you run and define its distribution list and distribution cycle from the Integrated Solution Console.


Appendix A. Sample test

This appendix provides a sample test and an answer key for the IBM Tivoli Usage and Accounting Manager implementation certification.

A


Sample test

Answer the following questions:

1. When creating and editing IBM Tivoli Usage and Accounting Manager V7.1 job files, which skill set is needed?

a. Working knowledge of XML

b. Working knowledge of Shell and .BAT scripting

c. Basic knowledge of database-stored procedures

d. Basic knowledge of Business Intelligence and Reporting Tools (BIRT) Report Designer

2. Consider the following 36-byte account code:

AAAABBBBBBBBBBBBBBBBCCCCCCCCCCCCCCCC

How can this be broken in to three account code levels?

a. Level 1, AAFull Length = 2 bytesDescription = Application

Level 2, AAAABBBBBBBBBBBBBBBBFull Length = 20 bytesDescription = Resource group

Level 3, AAAABBBBBBBBBBBBBBBBCCCCCCCCCCCCCCCCFull Length = 36 bytesDescription = Platform

b. Level 1, AAAAFull Length = 4 bytesDescription = Application

Level 2, AAAABBBBBBBBBBBBBBBBFull Length = 20 bytesDescription = Resource group

Level 3, AAAABBBBBBBBBBBBBBBBCCCCCCCCCCCCCCCCFull Length = 36 bytesDescription = Platform

c. Level 1, AAAAFull Length = 4 bytesDescription = Application

Level 2, AAAACCCCCCCCCCCCCCCCFull Length = 20 bytesDescription = Resource group


Level 3, AAAACCCCCCCCCCCCCCCCBBBBBBBBBBBBBBBBFull Length = 36 bytesDescription = Platform

d. Level 1, CCCCCCCCCCCCCCCCFull Length = 16 bytesDescription = Application

Level 2, CCCCCCCCCCCCCCCCBBBBBBBBBBBBBBBBFull Length = 32 bytesDescription = Resource group

Level 3, CCCCCCCCCCCCCCCCBBBBBBBBBBBBBBBBAAAAFull Length = 36 bytesDescription = Platform

3. Which report provides the Miscellaneous, Recurring, and Credit transactions for the parameters selected?

a. Cost Trend report

b. Transaction report

c. Percentage report

d. Run Total Percent report

4. To verify installation, after running sample collector data, where can database loads be tracked in Load Tracking?

a. Database

a. Job Runner

a. System Maintenance

a. Chargeback Maintenance

5. There is an application that controls print in a centralized environment, and there is a need to split all resources used by overhead account code AAABB among three different accounts: A1, A2, and AA1. On average, A1uses about 50 percent of the resources assigned to the AAABB account, A2 uses about 30 percent, and A3 uses about 20 percent. To prorate the costs associated with this application among the three accounts, which comma-delimited table would need to be created?

a. AAABB,A1,50,AllAAABB,A2,30,AllAAABB,A3,20,All

b. AAABB,A1,50,Z001AAABB,A2,30,Z002AAABB,A3,20,Z003

Appendix A. Sample test 159

c. AAABB,AAABB,50,AllAAABB,AAACC,30,AllAAABB,AAADD,20,All

d. AAABB,A1,50,Z001AAABB,A2,30,Z001AAABB,A3,20,Z001AAABB,A1,50,Z002AAABB,A2,30,Z002AAABB,A3,20,Z002AAABB,A1,50,Z003AAABB,A2,30,Z003AAABB,A3,20,Z003

6. What is the purpose of running the UNIX command ${TUAM_HOME}/bin/startServer.bin?

e. Starts Embedded WebSphere Application Server.

f. Starts database and starts Embedded WebSphere Application Server.

g. Starts Embedded WebSphere Application Server and verifies it is running.

h. Checks that the database is running and starts Embedded WebSphere Application Server.

7. What is the purpose of transaction collectors?

i. To convert data for TDS for z/OS

j. To add manual or regularly applied usages

k. To get usage data from application systems

l. To generate statistics on the IBM Tivoli Usage and Accounting Manager V7.1 usage

8. Which Integrator stage is always required?

a. Sort

b. Input

c. Aggregator

d. CSROutput


9. If the value for the Report Timeout Script is set to a high value in the Integrated Solutions Console and reports continue to time out, what is the next step to take?

a. Delete and recreate the report.

b. Have users run the report at a less busy time.

c. Create two reports from the one report that is timing out.

d. Log in directly to the Web Reporting Server and execute the report that is timing out.

10.What is the minimum requirement before creating or updating a report or spreadsheet?

a. The name and at least one rate code

b. Only the name of the new report or spreadsheet

c. The name, and ensure Visible to All Users is checked

d. The name and description of the new report or spreadsheet

11.During database initialization, IBM Tivoli Usage and Accounting Manager V7.1 (TUAM) adds a default user and user group for Web Reporting. What is the name of the default user group?

a. Admins

b. TUAMUsers

c. TUAMAdmins

d. Administrators

Appendix A. Sample test 161

Answer key

The following are the answers for the questions in “Sample test” on page 158.

1. A

2. B

3. B

4. D

5. A

6. C

7. B

8. D

9. D

10.A

11.D


acronyms

AIX Advanced Interactive eXecutive

AIXAA AIX Advanced Accounting

ARM Application Response Measurement

BIRT Business Intelligence and Reporting Tools

CMDB Configuration Management Database

CPU Central Processing Unit

CSR Common Source Format

DB2 Database 2

DDF Distributed Data Facility

FTP File Transfer Program

GB Gigabytes

GUI Graphical User Interface

HFS Hierarchical File System

HTML Hypertext Markup Language

HTTP Hypertext Transfer Protocol

HTTPS HTTP Secure

I/O Input/Output

IBM International Business Machines Corp.

IIS Internet Information Server

IP Internet Protocol

ISC Integrated Solution Console

IT Information Technology

ITIL® Information Technology Infrastructure Library

ITSO International Technical Support Organization

JCL Job Control Language

JDBC Java Database Connectivity

JVM Java Virtual Machine

Abbreviations and

© Copyright IBM Corp. 2009. All rights reserved.

LPAR Logical Partition

LU Logical Unit

MB Megabyte

MVS Multiple Virtual Storage

ODBC Open Database Connectivity

OGC Office of Government Commerce

OS Operating System

POC Proof of Concept

RAF Resource Accounting Facility

ROI Return on Investment

RPD Remote Product Deployment

SDK Software Development Kit

SFTP Secure FTP

SMF System Measurement Facility

SOA Service-Oriented Architecture

SQL Structured Query Language

SSH Secure Shell

SSL Secure Socket Layer

TDS Tivoli Decision Support

TPC TotalStorage Productivity Control

TSO Time Sharing Option

TUAM Tivoli Usage and Accounting Manager

TWS Tivoli Workload Scheduler

UDB Universal Database

URL Universal Resource Locator

VCDB Virtual Center database

VIOS Virtual I/O Server

XML eXtensible Markup Language

163

Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this book.

IBM Redbooks

For information about ordering these publications, see “How to get Redbooks” on page 166. Note that some of the documents referenced here may be available in softcopy only.

� Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1, SG24-7569

� IBM Tivoli Usage Accounting Manager V7.1 Handbook, SG24-7404

Other publications

These publications are also relevant as further information sources:

� Handbuch zur Server-Konfiguration ESX Server 3.0.1 und VirtualCenter 2.0.1, Artikelnummer: VI-DEU-Q406-314

� Installation and Upgrade Guide ESX 3.0.1 and VirtualCenter 2.0.1, VMware Item: VI-ENG-Q306-292

� Program Directory for Tivoli Decision Support for z/OS (English) V01.08.00, GI11-4249

� Server Configuration Guide ESX Server 3.0.1 and VirtualCenter 2.0.1, VMware Item: VI-ENG-Q206-215

� Tivoli Usage and Accounting Manager Data Collectors for Microsoft Windows User’s Guide Version 6.1.1, SC32-1557

� Tivoli Usage and Accounting Manager Data Collectors for UNIX and Linux User’s Guide Version 6.1.1, SC32-1556

� Tivoli Usage and Accounting Manager Quick Start Guide, GC23-6188

� Virtual Infrastructure Web Access Administrator’s Guide ESX Server 3.0.1 and VirtualCenter Server 2.0.1, VMware Item: VI-ENG-Q306-294


Online resources

These Web sites are also relevant as further information sources:

� IBM Tivoli Usage and Accounting Manager publication center

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/welcome.htm

� IBM Tivoli Usage and Accounting Manager Web site

http://www-306.ibm.com/software/tivoli/products/usage-accounting/

How to get Redbooks

You can search for, view, or download Redbooks, Redpapers, Technotes, draft publications and Additional materials, as well as order hardcopy Redbooks, at this Web site:

ibm.com/redbooks

Help from IBM

IBM Support and downloads

ibm.com/support

IBM Global Services

ibm.com/services




http://www.ibm.com/support/

http://www.ibm.com/support/

http://www.ibm.com/services/

http://www.ibm.com/services/

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/welcome.htm

http://www-306.ibm.com/software/tivoli/products/usage-accounting/

Index

Symbols/opt/ibm/tuam/bin/RunSamples.sh command 75/opt/ibm/tuam/ewas/profiles/AppSrv01/bin 106

Aaccount code 82account code hierarchy 82account code mapping 123account code structure 27account conversion 123Account_Code 82Acct 128acct 119acct process 128AcctCntl.txt 129AcctCSR.txt 129Aggregator 121AIXAAInput 121alternate rate 94ApacheCommonLogFormat 121auto logon 144

BBill 130bill 119BillDetail.txt 130BillSummary.txt 130BIRT 12, 31, 158Business Intelligence and Reporting Tools, see BIRT

Ccalendar 88certification

benefits 3checklist 5job role description 7key areas of competency 7objectives 8prerequisite skills 7recommended study resources 22requirements 8

© Copyright IBM Corp. 2009. All rights reserved.

certification overview 1CIMSDETAIL 36CIMSDETAILIDENT 36CIMSLOADTRACKING 34, 102CIMSRATE 73CIMSRate 73CIMSRESOURCEUTILIZATION 37CIMSSUMMARY 35Cleanup 131Client 83client budget 90client contact 91clients 88–89collector selection 29CollectorInput 121commands

csript.exe 136RunSamples.bat 13RunSamples.sh 75startServer.bat 63stopServer.bat 63

Common Source Resource, see CSRConsole 136CPU normalization 96CreateIdentifierFromIdentifiers 121CreateIdentifierFromRegEx 122CreateIdentifierFromTable 122CreateIdentifierFromValue 122CreateResourceFromConversion 122CreateResourceFromValue 122CSR 113CSR Plus Header 80CSRInput 121csript.exe command 136CurrentCSR.txt 129

Ddata sources 63DATABASE 121database 32database configuration 59database initialization 66database sizing 32

167

DBLoad 132dbload 119DBPurge 133dbpurge 119defaults directive 117DELIMITED 121DropFields 122DropIdentifiers 122DropResources 122

EECP 12, 67Enterprise Collector Pack, see ECPEXCHANGE2007 121ExcludeRecsByDate 122ExcludeRecsByPresence 122ExcludeRecsByValue 122

FFeed 82File transfer 134files

C:\IBM\tuam\ewas\bin\opServer.bat 63C:\IBM\tuam\ewas\bin\startServer.bat 63LoadVMware.xml 111startJobRunner.sh 111

FIXEDFIELD 121

Ggraphical user interface, see GUIGUI 111

Hheaderaccountcode 80headeraccountcodelength 80headerenddate 80headerendtime 80headerrectype 80headershiftcode 80headerstartdate 80headerstarttime 80heap size 104HTML 110Hypertext Markup Language, see HTML

IIBM Professional Certification Program 2

Ident.txt 130IdentifierConversionFromTable 122Identifiers 80IIS 30, 43, 74implementation platform 31IncludeRecsByDate 122IncludeRecsByPresence 122IncludeRecsByValue 122installation

application server 54database configuration 59Enterprise Collector Pack 67overview 42platform 43prerequisites 43verification 71

Integrated Solutions Console, see ISCintegrator 119integrator program 119Internet Information Services, see IISISC 13–14, 84

JJava

jobJava 136

JDBC driver 60job

Acct 128Bill 130Cleanup 131–132Console 136conversion 135DBLoad 132DBPurge 133File transfer 134Mail 128rpd 135Scan 133Wait file 135WSF 136

Job conversion 135job directive 115job file 110

structure 110job logs 138job processing 104job role description 7


jobs directive 115

Kkey areas of competency 7

Lload tracking 102LoadVMware.xml 111logs 138

MMail 128mail step 128MaxRecords 123memory 104Microsoft .NET Framework 2.0 51Microsoft Installer 49Microsoft SQL Server Report Viewer 52

NNCSAInput 121NotesDatabaseSizeInput 121NotesEmailInput 121NotesUsageInput 121

Oobjectives 8

administration 16configuration 13installation 11job creation 17planning 8problem determination 19reporting 21

output files 139overview 1

Ppaths

/opt/ibm/tuam/ewas/profiles/AppSrv01/bin 106platform requirements 43prerequisite skills 7process directive 117processing overview 112Prorate 123proration table 95

Rrate 92rate codes 92rate group 92rate groups 83rate shift 97Rate Table 83Redbooks Web site 166

Contact us xRemote product deployment 135RenameFields 123REORG 103report generation 105report requirements 38Report Viewer 52reporting 74ResourceConversion 123Resources 81return on investment, see ROIROI 5RunSamples.bat command 13RUNSTATS 103

Ssample collection verification 75Scan 133schedule 88shift 97shutdown 106Simple Mail Transfer Protocol, see SMTPSMTP 75Sort 123, 132startJobRunner.sh 111startServer.bat 63startup 106step directive 118steps directive 118stopServer.bat 63SYSTEM_ID 82

TTDS 121Tivoli Software Professional Certification 4Tivoli Usage and Accounting Manager 6TPC 121TRANSACTION 121tuning 103

Index 169

Uuser administration 84user and group mapping 86user creation 85user role definition 86

VVIO 29Virtual I/O, see VIOVirtual University Enterprises, see VUEVMWARE 121VMware ESX server 81VUE 6

WW3CWinLog 121Wait file 135Web application 74Web reporting 74WEBSPHEREXDFINEGRAIN 121WEBSPHEREXDSERVER 121Windows script file 136WORK_ID 82

XXML editor 111XML job 110


(0.2”spine)0.17”<

->0.473”

90<->

249 pages

Certification Guide Series: IBM Tivoli Usage and Accounting M

anager V7.1 Implem

entation

®

SG24-7692-00 ISBN 0738432482

INTERNATIONAL TECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.

For more information:ibm.com/redbooks

®

Certification Guide Series:IBM Tivoli Usage and Accounting Manager V7.1 ImplementationDetailed architecture and components discussion

Installation and configuration processing

Monitoring IT usage and chargebacks

This IBM Redbooks publication is a study guide for the IBM Tivoli Usage and Accounting Manager V7.1 certification. It is aimed for IT professional who want to be an IBM Certified Professional for this product.

IBM Tivoli Usage and Accounting Manager V7.1 certification is offered through the IBM Professional Certification program. It is designed to validate the skills required of technical professionals who work in the implementation and deployment of IBM Tivoli Usage and Accounting Manager V7.1.

This book provides the necessary information to understand this topic. It includes sample questions that help evaluate personal progress. It familiarizes the readers with the types of questions that may be encountered in the exam.

This guide does not replace practical experience. This is not designed to be a stand-alone guide for this topic. Instead, this guide should be combined with educational activities and experiences and used as a very useful preparation guide for exam.

For your convenience, the chapters are based on the certification objectives of the IBM Tivoli Usage and Accounting Manager V7.1 implementation certification test. Those requirements are planning, prerequisites, installation, configuration, administration, and problem determination. Studying each chapter helps you prepare for each objective of the exam.

Back cover




certification guide series ibm tivoli usage and accounting manager v7.1 implementation sg247692

Technology

ibm tivoli usage

copyright ibm

ibm redbooks

ibm corp

database configuration

accounting manager v7

database creation

user creation