deployment guide series ibm tivoli usage and accounting manager v7.1 sg247569

ibm.com/redbooks

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

Budi DarmawanJörn Siglen

Lennart LundgrenRoy Catterall

Financial management solution for IT-related services

Extensive deployment and demonstration examples

Planning and services information

Front cover

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


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

February 2008

International Technical Support Organization

SG24-7569-00

© Copyright International Business Machines Corporation 2008. 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 (February 2008)

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

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Part 1. Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Solution introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 ITIL financial management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Tivoli Usage and Accounting Manager features . . . . . . . . . . . . . . . . . . . . . 71.3 Tivoli Usage and Accounting Manager value proposition . . . . . . . . . . . . . 101.4 Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4.1 Generic processing flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.2 The Common Source Resource format . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Solution environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.2.1 Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.2.2 Supported databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.3 Sizing considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3.1 Data elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.3.2 Growth factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3.3 Sample growth estimation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.4 Typical deployment environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.4.1 Small, proof of concept, or demonstration environment . . . . . . . . . . 272.4.2 Medium scale production environment . . . . . . . . . . . . . . . . . . . . . . . 272.4.3 Large scale production environment . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3. Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.1 Required skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.2 Solution description and assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3 Task breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.3.1 Project kick-off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.2 Environment preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.3 Database setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

3.3.4 Tivoli Usage and Accounting Manager server installation . . . . . . . . 343.3.5 Data collection pack setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.3.6 Customizing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.3.7 Demonstrating the solution and skill transfer . . . . . . . . . . . . . . . . . . 35

Part 2. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 4. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 394.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.2 Installing DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.3 Installing server prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.3.1 Configuring Microsoft Internet Information Server . . . . . . . . . . . . . . 554.3.2 Install the Microsoft Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.3.3 Install Microsoft .NET Framework 2.0 . . . . . . . . . . . . . . . . . . . . . . . . 614.3.4 Install Microsoft SQL Server Report Viewer . . . . . . . . . . . . . . . . . . . 63

4.4 Installing server components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.5 Installing Enterprise Collector Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.6 Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.6.1 Defining the JDBC driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.6.2 Defining data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764.6.3 Initializing the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.6.4 Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

4.7 Installing Windows Process Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.7.1 Manual installation process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.7.2 Deploying with a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 5. Usage demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935.1 Demonstration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 945.2 Defining accounting resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

5.2.1 Working with the account code structure . . . . . . . . . . . . . . . . . . . . . 955.2.2 Setting up clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975.2.3 Rate table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

5.3 Running Windows collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.3.1 Verifying the Windows process data collector installation. . . . . . . . 1035.3.2 Windows process data files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5.4 Loading Windows process data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.4.1 The data collection process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.4.2 Account code mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.4.3 Running the collection job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

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

5.5 Generating Windows reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.6 Additional demonstration scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175.7 Financial Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Chapter 6. Troubleshooting hints and tips . . . . . . . . . . . . . . . . . . . . . . . . 1256.1 General logging and tracing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1266.2 Installation and configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1286.3 Integrated Solution Console debugging . . . . . . . . . . . . . . . . . . . . . . . . . 1286.4 Job Runner debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306.5 Quick finder for trace and log information . . . . . . . . . . . . . . . . . . . . . . . . 132

Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Appendix A. Sample listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Sample Windows load job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Sample Windows process collector job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

System requirements for downloading the Web material . . . . . . . . . . . . . 146How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Contents v

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

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. 2008. All rights reserved. vii

Trademarks

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

AIX®DB2 Universal Database™DB2®IBM®i5/OS®Lotus Notes®Lotus®

Notes®PowerPC®pSeries®Redbooks®Redbooks (logo) ®System i™System p™

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

The following terms are trademarks of other companies:

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

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

IT Infrastructure Library, IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce.

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.

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

Microsoft, SQL Server, Visual C++, Windows Server, Windows Vista, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Itanium, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries 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 Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1

Preface

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 to 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 consideration before you implement the product is 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.

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.

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

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 eight years ago, Budi worked in IBM Indonesia as solution architect and lead implementer. His current interests are Java™ programming, application management and general systems management.

Jörn Siglen is System Management Architect at IBM Global Services Germany. He has 16 years of experience in the Information Technology field. He holds a degree in Information Technology Engineering from Berufsakademie Stuttgart, Germany. His areas of expertise include AIX® on pSeries® and Tivoli software for monitoring, availability and storage products.

Lennart Lundgren is an IT Specialist in IBM Software Group, Sweden. He has 30 years of experience in the Systems Management area on mainframe computers. He holds a degree in Computer Sciences from the University of Lund, Sweden. He has worked at IBM for more than 20 years. His areas of expertise include performance and capacity management, z/OS® systems programming, and tools development.

Roy Catterall is a Team Leader for Tivoli Decision Support for z/OS in Australia. He has 20 years of experience in the Information Technology field. He holds a degree in Business Studies and Computing Science from the University of Zimbabwe. His main area of expertise is z/OS; he also has some programming experience with most other operating systems. He has contributed extensively to the Tivoli Decision Support for z/OS documentation.

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

Terry Copeland, Rodolfo Ambrosetti, Page L. Hite, Greg HowardIBM Software Group, Tivoli Systems

Alfred Schwab, EditorInternational Technical Support Organization, Poughkeepsie Center

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.

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

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]

� Mail your comments to:

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

Preface xi

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

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



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

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

Part 1 Planning

Part 1

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

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

Chapter 1. Solution introduction

IBM Tivoli Usage and Accounting Manager V7.1 is a new version of a financial management tool for IT resources from Tivoli. It allows dynamic chargeback accounting, reporting, and analysis to be performed for enterprises. This chapter consists of the following:

� 1.1, “ITIL financial management” on page 4

� 1.2, “Tivoli Usage and Accounting Manager features” on page 7

� 1.3, “Tivoli Usage and Accounting Manager value proposition” on page 10

� 1.4, “Product architecture” on page 10

1


1.1 ITIL financial management

In today’s environment, businesses are very dependent on IT. Requirements from customers for standard compliance are apparent and IT services are required to better align with business objectives. The IT Infrastructure Library® (ITIL®) is a set of best practices that can help address these issues.

ITIL is a collection of IT best practices designed to help organizations overcome current and future technology challenges. Originally created by the UK Office of Government Commerce (OGC) in 1988, ITIL currently has evolved as a result of years of experience contributed by major IT organizations and companies, including IBM.

ITIL is a library of books that document industry-accepted best practices for IT service, infrastructure, and application management. ITIL is an excellent starting point from which to adopt and adapt best practices for implementation in any IT environment.

ITIL’s models show the goals, general activities, inputs, and outputs of the various processes. They help to address the most common questions asked by IT managers worldwide:

� How do I align IT services with business objectives? � How do I lower the long term costs of IT services? � How do I improve the quality of IT services?

ITIL is currently on its Version 3 release. However, the discussion of ITIL in this book is mainly based on ITIL Version 2. In the Version 2 publication, the contents of ITIL are shown in Figure 1-1 on page 5.


Figure 1-1 The contents of ITIL

The most popular books of the ITIL are Service Support and Service Delivery. These two books together form the Service Management discipline. The financial management process is part of Service Delivery. This is apparent because financial management is strategic for aligning IT to perform as a business entity and providing the ability to manage IT as a business.

The Service Delivery aspect uses the configuration data for building IT services.

� Service Level Management manages service level agreements with IT consumers. Service level agreement is the base measurement of IT services that are provided to consumers.

� Financial management manages the day-to-day IT finances and quantifies IT investment into IT Service improvement. It also generates a balance report of IT budget and accounting.

� Availability management ensures that IT services are available to the business users. It identifies and mitigates risks involved with unavailability due to an IT resource failure.

� Capacity management ensures that IT can provide its services with reasonable performance as dictated by the service level agreement. This requires an adequate capacity of IT resources.

The business

The technology

Planning to implement service management

Application management

The business

perspective

ICT Infrastructure management

Service management

Service delivery

Service support

Security managementSoftware Asset

management

Chapter 1. Solution introduction 5

� IT continuity management ensures that IT would continue to function even when a major disruption happens to the business (such as a natural disaster).

The financial management of ITIL, as a typical financial discipline, does the budgeting and accounting of IT services cash flow. With proper financial management, the IT budget can be related directly to each IT service. Thus, it supports the transformation of IT from a cost center into a business unit that can charge for its services to the customers.

The primary goal of financial management is for IT to fully account for the money spent and attribute these costs to the IT services delivered. In order to achieve this goal, financial management must monitor usage and record cost of IT resources, as well as provide an investment business case.

The financial management of IT is more effective if IT charges for usage based on a business entity instead of an IT entity. This is more meaningful for calculating the business cost of an IT service. The total CPU time for running a financial application would not be apparent to the CFO. However, the number of ledger entries processed would be a more meaningful measurement of the financial application usage.

Initially, formulating and calculating these business aspects of the IT services necessitates a steep learning curve. However, as more information is collected and analyzed, the task will become easier.

The primary activities of financial management are:

� Budgeting

It must obtain a budget from the enterprise. It administers and controls the costs related to the budget.

� Accounting

It performs financial accounting of IT. It must develop a cost model with its associated cost types. It apportions service cost, calculates cost, and performs Return of Investment (ROI) analysis.

� Charging

It develops charging policies, identifies charging items, calculates pricing, and performs billing.

Tivoli Usage and Accounting Manager allows the collection of usage data, provides a mechanism to input pricing, and performs billing. It generates various reports for IT usages and provides financial tools for IT financial modelling.


1.2 Tivoli Usage and Accounting Manager features

Tivoli Usage and Accounting Manager is a general purpose tool for:

� Collecting resource usage data� Assigning account codes for each resource� Providing a billing (charging) rate for each unit

Additionally, it provides reports for analysis of the charging environment to ensure that charges are correct and fair. It also offers a financial modeler feature that allows rate analysis based on IT expenditure.

IBM Tivoli Usage and Accounting Manager Enterprise Edition V7.1 is a resource accounting product that enables you to track, manage, allocate, and optionally bill end users for IT resources. Tivoli Usage and Accounting Manager Enterprise Edition assists with:

� Usage-based accounting and chargeback� IT cost allocation and analysis� Application allocation and availability� Resource utilization reporting� Easy reporting through a Web interface

Tivoli Usage and Accounting Manager Enterprise Edition consolidates different types of usage metering data into an integrated reporting structure. It can then generate reports, invoices, and summary files that show resource consumption and cost for the various functional units of an organization. This information is presented in Web, print, or file formats for easy availability. IBM Tivoli Usage and Accounting Manager Enterprise Edition contains the following:

� Administration Server, the central component, consisting of the following:

– Tivoli Usage and Accounting Manager Enterprise Edition Console

This is the Abstract User Interface Markup Language rendering in ISC over the Web Administrator tool.

– Tivoli Usage and Accounting Manager Engine

This consists of many components, including a batch processing facility called Job Runner that launches and controls the underlying processes that convert raw usage data into usable Tivoli Usage and Accounting Manager Enterprise Edition information. It also contains the main rules engine processing components and other data transformation tools.

– Generic collection functionality

This consists of the Integrator and the Universal Collection tools that allow clients to build their own collectors.


– Tivoli Usage and Accounting Manager Windows® Web Reporting - from Internet Information Services (IIS) under Windows only

This reports directly from the Microsoft® SQL Server™, Oracle®, or DB2® database using Microsoft Reporting Services runtime viewer as the underlying reporting engine and Microsoft IIS as the Web server. This Microsoft Reporting Services viewer must be separately downloaded from Microsoft and installed. It is not supplied with Tivoli Usage and Accounting Manager Enterprise Edition.

� Limited Business Intelligence and Reporting Tools (BIRT) reporting directly from the database

If non-Windows reporting is desired, there is a prerequisite that the client will download and install BIRT/IES prior to installation. This reporting can be run from UNIX® or Linux®. While it can also be run from Windows, the more powerful Tivoli Usage and Accounting Manager Windows Web Reporting is the preferred Windows reporting method.

The Tivoli Usage and Accounting Manager Enterprise Edition - Core Data Collection Entitlements product, delivered in the same installation as Tivoli Usage and Accounting Manager Enterprise Edition, contains:

� Windows disk usage� Windows CPU processor usage� VMware usage collector support� z/VM®� AIX Advanced Accounting, including support for Workload Partition, Virtual

I/O Server, and any other Advanced Accounting features� UNIX, Linux, Linux on System z™ operating system� UNIX, Linux, Linux on System z file system� System i™ (collects all usage from System i, but the actual collector must be

run from Windows)� Tivoli Decision Support on z/OS extract (similar to the Accounting Workstation

Option or IBM Tivoli Usage and Accounting Manager Enterprise Edition for z/OS)

� Generic Collection (also known as Universal Collection)� Miscellaneous and Recurring Adjustment Transaction Maintenance

The Tivoli Usage and Accounting Manager Enterprise Collector Pack (a separate purchasable option) contains the following collectors. A designation of sample only means that the collector is not fully documented, is not globalized or tested, and may not run on all platforms. It is provided as a starting point only, but the sample collectors will be supported, via the Level 2/Level 3 support process. A notation of Windows only means that the collector or sample runs only under Windows, not under Linux or UNIX.

� TotalStorage® Productivity Center


� Tivoli Storage Manager (Windows only)� SAP®� WebSphere® XD� WebSphere XD HTTP� Squid (Windows only, sample only)� Veritas (Windows only, sample only)� Windows System Resource Monitor (Windows only, sample only)� Microsoft Reporting Services (Windows only, sample only)� Evolve (Windows only, sample only)� Citrix (Windows only, sample only)� NetWare (Windows only, sample only)� Oracle� Oracle Space� DB2 Usage� DB2 Space� Apache Web Server Usage� FTP transfer usage (Windows only, sample only)� Lotus® Notes®� SQL Server (Windows only)� DBSpace� Sybase (Windows only, sample only)� Apache� Microsoft IIS� Microsoft Internet Security and Acceleration (ISA) (Windows only, sample

only)� Microsoft Proxy (Windows only, sample only)� Netscape Proxy (Windows only, sample only)� Exchange (Windows only)� SendMail (Windows only, sample only)� Windows Print (Windows only)� NetBackup (Windows only, sample only)� NetFlow (Windows only, sample only)

New in IBM Tivoli Usage and Accounting Manager Enterprise Edition V7.1 are the following:

� A fully globalized product� A platform-independent reporting option� New data collectors� Improved integration with Tivoli Decision Support for z/OS for mainframe

resource accounting� A Web-based administration tool


1.3 Tivoli Usage and Accounting Manager value proposition

Tivoli Usage and Accounting Manager helps IT to control and manage operation and resource costs by collecting, analyzing, reporting, and billing based on usage and costs of shared Windows, UNIX (AIX, HP/UX, Sun™ Solaris™), Linux (Red Hat and Novell SUSE), i5/OS®, and VMware computing resources. Tivoli Usage and Accounting Manager helps you improve IT cost management. With it you can understand your costs and track, allocate, and invoice based on actual resource use by department, user, and many additional criteria.

Tivoli Usage and Accounting Manager consolidates a wide variety of usage data with data collectors associated with Operating Systems, Databases, Internet Infrastructure, E-mail Systems, Network & Printing, and customized usage Data Import collection from any application or system. This broad set of customer-proven data collectors across multiple platforms, combined with a powerful business rules-driven capability to transform raw IT data into business information, enables cost allocation across business units, cost centers, applications, and users.

Tivoli Usage and Accounting Manager allows you to do the following:

� Support virtualization and server consolidation to help manage costs

� Align IT with business goals by revealing who consumes which resources

� Easily administer cost allocation initiatives with little human intervention

� Improve flexibility and cost management by charging for IT resource use in accordance with popular methods

1.4 Product architecture

The main components used by IBM Tivoli Usage and Accounting Manager are shown in Figure 1-2.


Figure 1-2 Tivoli Usage and Accounting Manager components in use and their dependencies

The major components of are:

� Collection

The collection of metering data is mostly handled by the operating systems and other applications. Tivoli Usage and Accounting Manager data collectors read this data or provide access to the databases where the data is stored. The data collection can be performed from a database table, a file to be converted into Tivoli Usage and Accounting Manager format, or by calling Web Services to collect metrics.

� Application server

The Tivoli Usage and Accounting Manager application server consists of two primary functions: the administration server and processing server.

– Administration

This is performed using the Integrated Solutions Console (ISC). ISC is an application running on top of an embedded WebSphere Application

Collection

Application ServerProcessing

Reporting Server

Tivoli Decision Support for z/

OS

ITUAMDBJDBC

Microsoft Internet Information Server

Web ReportingEmbedded WebSphere

Application Server

Integrated Solution Console

Processengine

Database

ODBC (.NET)Ad

min

istra

tion

Rep

ortin

g

Reporting with BIRT

File

FinancialModeler

Data collector

File

Vmware

Web Services

SDK


Server. It provides the front end for all administration of the Tivoli Usage and Accounting Manager server.

– Gathering and processing of usage and accounting

The collection of Tivoli Usage and Accounting Manager collector files can be done with a file transfer method or accessed directly from a database or Web Services.

Processing of this data is performed using the ProcessEngine and the Tivoli Usage and Accounting Manager integrator function. It handles all data processing and data loading into the Tivoli Usage and Accounting Manager database. The Java-based Job Runner controls the processing steps. All job descriptions are stored in Extensible Markup Language (XML) files.

� Database server

A relational database system is required for storing the administration, metering, and accounting data. The database is accessed using the JDBC™ driver, except for reporting, which uses the DB2 .NET interface. This driver must be provided for each component that needs access to the database.

� Reporting server

All reports are generated from the Tivoli Usage and Accounting Manager database and can be stored on a file system for publishing or distribution. Tivoli Usage and Accounting Manager provides reporting using Microsoft Report Viewer under Microsoft Internet Information Server or using Business Intelligence and Reporting Tools (BIRT).

1.4.1 Generic processing flow

The data processing in Tivoli Usage and Accounting Manager is similar for all data sources. Figure 1-3 on page 13 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.


Figure 1-3 Generic process overview, including common steps

The process steps in Figure 1-3 are:

1. Many systems already have a resource usage collection function. Tivoli Usage and Accounting Manager uses this data for further processing. The main processing in 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 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 in a database or on a Web page, the data extract made by Tivoli Usage and Accounting Manager will be direct CSR format.

The Tivoli Usage and Accounting Manager Integrator can include CSR conversion, aggregation, account code conversion, and sort in one step, 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 data of resource fields based on the identifier values.

3. Account conversion matches the metering data to the account code structure (see 5.2, “Defining accounting resources” on page 95) and all records that do not fit are put into an exception file, which 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 is used for calculating the money value. If the rate is of type CPU, the recalculation based on the Normalization Table is done in addition.

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

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

1.4.2 The Common Source Resource format

Tivoli Usage and Accounting Manager uses two file formats, Common Source Resource (CSR) and Common Source Resource plus (CSR+). 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:

Note: We recommend to create CSR+ records as input for the billing step, or alternatively to 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.


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 identifiers. These identifiers are used to distinguish one resource from another 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...

A sample 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. The resource metric is structured as follows:

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

A sample resources segment with three metrics is:

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

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


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

Example 1-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 1-2 we find the data from two VMware ESX servers (SYSTEM_ID) and three VMware guests (Instance) collected via one VirtualCenter Server (Feed).

Example 1-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

The Tivoli Usage and Accounting Manager defines some reserved identifiers that are used for special processing. These 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 the z/OS data collector specifying a subsystem such as TSO, JES2, or any other application (also not z/OS), if needed

Feed Identifies and defines a subfolder in the process folder for data transfer


Chapter 2. Solution environment

This chapter explains the Tivoli Usage and Accounting Manager solution environment. The discussion covers the following:

� 2.1, “Hardware prerequisites” on page 18

� 2.2, “Software prerequisites” on page 18

� 2.3, “Sizing considerations” on page 21

� 2.4, “Typical deployment environment” on page 27

2


2.1 Hardware prerequisites

The most up-to-date prerequisites (hardware and software) for Tivoli Usage and Accounting Manager can be retrieved from the following Web page:

http://www-306.ibm.com/software/tivoli/products/usage-accounting/platforms.html

The following hardware is recommended for running Tivoli Usage and Accounting Manager V7.1:

� Processor with speed of 3 GHz or more for application server or Web reporting server.

� An additional 2 GB of free memory for application server or Web reporting server.

� The database server uses 80 GB of hard drive space.

� Web reporting server uses 40 GB of hard drive space.

2.2 Software prerequisites

The software prerequisites are divided into:

� 2.2.1, “Supported operating systems” on page 19

� 2.2.2, “Supported databases” on page 21

All other required software components, such as WebSphere Application Server and Integrated Solution Console, are packaged with the software itself. See also:

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/install/r_app_server_specs_win.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/install/r_app_server_specs_unix.html

Note: The space requirement may vary; see 2.3, “Sizing considerations” on page 21 for more information.


http://www-306.ibm.com/software/tivoli/products/usage-accounting/platforms.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/install/r_app_server_specs_win.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/install/r_app_server_specs_unix.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.ituam.doc_7.1/install/r_app_server_specs_unix.html

2.2.1 Supported operating systems

Table 2-1 lists the supported operating systems.

Table 2-1 Supported operating systems

Platform Server Collector Reporting Web client

AIX 5.2 Yes Yes No Yes

AIX 5.3 Yes Yes BIRT only

AIX 6.1 a Yes Yes BIRT only Yes

Solaris 9 – SPARC Yes Yes No Yes

Solaris 10 – SPARC Yes Yes No Yes

Solaris 10 – x64 No Yes No Yes

HP-UX 10.20 No Yes No Yes

HP-UX 11i Yes Yes No Yes

HP-UX 11.23 Itanium® No Yes No No

Windows 2000 Pro No Yes No No

Windows 2000 Server No Yes No No

Windows 2000 Advanced Server No Yes No No

Windows 2000 Data Center Server No Yes No No

Windows XP Professional – x86 No No No Yes

Windows XP Professional – x64 No No No Yes

Windows Server® 2003 Standard – x86 Yes Yes Yes Yes

Windows Server 2003 Enterprise – x86 Yes Yes Yes Yes

Windows Server 2003 Datacenter – x86 Yes Yes Yes Yes

Windows Server 2003 Web Edition – x86 Yes Yes Yes Yes

Windows Server 2003 Standard – x64 Yes Yes Yes Yes

Windows Server 2003 Enterprise – x64 Yes Yes Yes Yes

Windows Server 2003 Datacenter – x64 Yes Yes Yes Yes

Windows Server 2003 Web Edition – x64 Yes Yes Yes Yes

Windows Vista® No Yes No Yes

Chapter 2. Solution environment 19

RHEL 4.0 for x86 Yes Yes No Yes

RHEL 5.0 for x86 Yes Yes No Yes

RHEL 4.0 for AMD64 ¤ EM64T Yes Yes No Yes

RHEL 5.0 for AMD64 ¤ EM64T Yes Yes No Yes

RHEL 4.0 for System i No No No Yes

RHEL 5.0 for System i No No No Yes

RHEL 4.0 for System z (64 bit) Yes Yes No Yes

RHEL 5.0 for System z (64 bit) Yes Yes No Yes

RHEL 4.0 for PowerPC® Yes Yes No Yes

RHEL 5.0 for PowerPC Yes Yes No Yes

SLES 9 for x86 Yes Yes No Yes

SLES 10 for x86 Yes Yes No Yes

SLES 9 for AMD64 ¤ EM64T Yes Yes No Yes

SLES 10 for AMD64 ¤ EM64T Yes Yes No Yes

SLES 9 for System z (64 bit) Yes Yes No Yes

SLES 10 for System z (64 bit) Yes Yes No Yes

SLES 9.0 for PowerPC Yes Yes No Yes

SLES 10 for PowerPC Yes Yes No Yes

VMware ESX No Yes No No

i5/OS v5 No Yes No No

zVM No Yes No No

z/OS v 1.1 No Yes No No

z/OS v1.2 No Yes No No



z/OS v1.3, v1.4, v1.5, v1.6, v1.7, and v1.8b No Yes No No

a. With support for advanced accounting collection for AIX V5.3 and AIX V6.

Platform Server Collector Reporting Web client


2.2.2 Supported databases

Table 2-2 lists the supported databases.

Table 2-2 Supported databases

2.3 Sizing considerations

The sizing considerations for Tivoli Usage and Accounting Manager deployment are mainly related to the data size. The initial Tivoli Usage and Accounting Manager server database using DB2 Universal Database™ in Windows uses approximately 350 MB.

This section provides an overview for estimating the Tivoli Usage and Accounting Manager database growth. The estimation has not been tested with actual customer environments—it is only used for estimating our database size in our sample environment.

b. Available only with the Tivoli Usage and Accounting Manager for z/OS Option of Tivoli Decision Support for z/OS.

Database Server Collector

DB2 UDB 7.1 No Yes

DB2 UDB 7.2 No Yes

DB2 UDB 8.1 Yes Yes

DB2 UDB 8.2 Yes Yes

DB2 UDB 9.1 Yes Yes

DB2 8.1 System z Yes No

MS SQL Server 2000 Yes Yes

MS SQL Server 2005 Yes Yes

Oracle 8i No Yes

Oracle 9i Yes Yes

Oracle 9i v2 Yes Yes

Oracle 10 Yes Yes


We start by checking our database size in our Windows directory or Linux file system just after it is initialized. The data size is roughly 350 MB, including the database catalog and database log files.

However, as Tivoli Usage and Accounting Manager is a data collection and processing tool, it collects and loads data into the database and keeps it for some period of time. Estimating its growth is critical for ensuring that the space is properly allocated and the resulting performance impact can be addressed (such as the time to back up the data, query response time, replication need, and so on).

2.3.1 Data elements

The primary growth of data is for usage and accounting data. These are:

Resource utilization The collection of the resource metric usage from the AcctCSR file; collection is provided by identifier for each resource (rate code). This is an optional collection. You do not need to collect the resource usage.

Billing summary This provides a summary usage for each resource (rate code) by account code. It is important that the input to the billing cycle is sorted by account code to minimize duplicate summary records. The data is a one-to-one mapping from the BillSummary.txt file.

Billing detail This provides individual entries from the AcctCSR file. It gives individual occurrences of source usage by resource name (rate code). This links to the identifier table for getting the identifier key for each of the entries. The data is a one-to-one mapping from the BillDetail.txt file.

Identifier table This lists the identifiers that are used by each Billing detail entry. The data is a one-to-one mapping from the Ident.txt file.

Figure 2-1 on page 23 provides an overview of the relationship between these tables.


Figure 2-1 Table relationships

Some important tips for database size are:

� You should run the DBpurge program using Job runner to remove old data. Because Tivoli Usage and Accounting Manager data is an accounting financial tool, you may want to archive the data first. The data details can be huge and less useful than the summary data. You may want to purge detail data more often.

� Use the CSR+ format, and perform a sort before you run the Bill processing. The sorting with the CSR+ format is based on the account code and optimizes the billing process.

� Only collect the identifiers and resources that you are interested in. Modify the sample collection jobs, change the mapping, and remove any unwanted identifiers and resource fields. The number of identifiers and resources is a size multiplier for the tables.

Resource Utilization

LOADTRACKINGUIDDETAILUIDDETAILLINEACCOUNTCODEAGGREGATESTARTDATEENDDATESHIFTCODEAUDITCODESOURCESYSTEMRATECODERESOURCEUNITS

Billing Detail

LOADTRACKINGUIDDETAILUIDDETAILLINEACCOUNTCODEAGGREGATESTARTDATEENDDATESHIFTCODEAUDITCODESOURCESYSTEMRATECODERESOURCEUNITSACCOUNTINGSTARTDATEACCOUNTINGENDDATE

Billing Summary

LOADTRACKINGUIDYEARPERIODSHIFTACCOUNTCODELENLEVEL%RATETABLERATECODESTARTDATEENDDATERATEVALUERESOURCEUNITSBREAKIDMONEYVALUEUSAGESTARTDATEUSAGEENDDATERUNDATEBILLFLAG%

Detail Ident

LOADTRACKINGUIDDETAILUIDDETAILLINEIDENTNUMBERIDENTVALUE

Getidentifier

Summarize, aggregate on

Account_Code

Getidentifier


2.3.2 Growth factors

Now let’s look at each of the tables and analyze what the parameters are that affect their sizes. The following are the size multipliers:

Number of days The retention period of your data before you run the purge step to remove them.

Number of shift The number of shifts in a day that need different rate codes.

Collection source Each collection source is processed with a different job. Each will generate a different set of data.

Account code All billing and resource tables are indexed by the account code entry. This is the primary retrieval mechanism for Tivoli Usage and Accounting Manager data. You must estimate the number of distinct account codes.

Number of resources The resources are mapped directly as rate code. These rate codes are the secondary search mechanism for Tivoli Usage and Accounting Manager.

Number of identifiers Each identifier is put in a different row in the CIMSDETAILIDENT table.

Identifier mix This is the number of unique identifiers in each collection. You should be able to estimate this number by your understanding of the collection process. As an example, for Windows, you can count the number of running processes in the day as the identifier mix.

Now regarding the tables themselves, which of the above items maps? Table 2-3 lists the affecting factors and estimates the row size of the tables.

Table 2-3 Table estimation

Name Row sizea

Affecting source

CIMSRESOURCE UTILIZATION

300 Source, Account_Code, Identifier mix, RateCode, Shift, #day

CIMSSUMMARY 300 Source, Account_Code, RateCode, Shift, #day

CIMSDETAIL 350 Source, Account_Code, Identifier mix, Rate per id, Shift, #day

CIMSDETAILIDENT 75 Identifier mix x Ident count


2.3.3 Sample growth estimation

For the purpose of this sample, the following are the collected facts:

� Data is kept for two years, except that the detail data is for one year.

� Two shifts are collected.

� The account structure is in the form client - department - application - host.

� Collected usage information is for UNIX processes and Windows processes only.

� Average identifier length is 20 characters.

� Audit code is not used.

� Percentage of complete records, since some of the accounting data only has partial data. Some of the metrics may not appear in all records. We just use 75%.

For the UNIX processes, collection is performed on 15 machines. There are 12 resource metrics that are collected. The identifier fields are Feed, Account_Code, hostname, userName, and process. The estimated number of processes per day is 250.

For Windows processes, collection is performed on 20 machines. There are 8 resource metrics that are collected. The identifier fields are Feed, Account_Code, Server, User, processName (we assume that BasePriority, PriorityClass and ProgramPath fields are dropped). The estimated number of processes per day is 100.

The number of unique identifiers in both UNIX and Windows processes will be the estimated number of processes.

The number of account codes would then be derived from the account code structure. As mentioned above, the account code structure is client - department - application - host. It is important to plan this structure and how these items can be identified. This example assumes that the account code elements are retrieved as follows:

� Host is retrieved from hostname or Server identifiers.� Application is derived using a lookup table based on the server, user, and

program name.� Department is derived from the application.� Client is derived from the department.

a. The row size is an estimate based on the table structure and using the assumption that a VARCHAR or VARGRAPHIC column uses half its capacity.


Based on the specification, we conclude that the number of unique account codes would be the same as the number of applications (or applications by host). We just assume here that the number of applications represents the number of unique account codes.

Now we can start performing the calculation. First, we collected the multipliers as shown in Figure 2-2.

Figure 2-2 Estimating the multipliers

In Figure 2-2, the account structure is estimated by listing the component occurrences. We used the number of applications as the number of unique account codes. All the other numbers are collected from the discussion.

The resulting table sizes are shown in Figure 2-3.

Figure 2-3 Table size result

As shown in Figure 2-3, the total data size is around 309 GB. We assume that we do not collect the resource utilization table.


2.4 Typical deployment environment

Based on the architecture of Tivoli Usage and Accounting Manager discussed in 1.4, “Product architecture” on page 10, we can identify the following deployment environment structures:

� 2.4.1, “Small, proof of concept, or demonstration environment” on page 27

� 2.4.2, “Medium scale production environment” on page 27

� 2.4.3, “Large scale production environment” on page 28

2.4.1 Small, proof of concept, or demonstration environment

This small scale environment installs all components in a single Windows-based server that allows hosting of the database, application server, and Web reporting server on a single machine. This is not recommended in a larger environment because the load for the processing may interfere with the reporting activities.

The configuration of this environment is shown in Figure 2-4.

Figure 2-4 Small scale environment

2.4.2 Medium scale production environment

The medium scale production environment still employs a single database. However, the processing and Web reporting functionality have been moved into different servers to allow better load distribution. There may also be the need to have a processing server on a different platform. The configuration of this environment is shown in Figure 2-5 on page 28.

Embedded WebSphere Application Server 6.1Integrated Solution ConsoleMicrosoft Report ViewerMicrosoft Internet Information ServicesITUAM reporting applicationITUAM processing engineITUAM data collectorsDatabase

ITUAMDB

ITUAMserver


Figure 2-5 Medium scale deployment

2.4.3 Large scale production environment

In a large scale environment, data size may become quite large. Isolation between different reporting applications and processing applications may be necessary. An external data replication mechanism (such as DB2 replication) may be employed to synchronize database copies. Data load processing would not impact report generation, and, conversely, report generation is not hindered by data loading. This environment is depicted in Figure 2-6 on page 29.

Embedded WebSphere Application Server 6.1Integrated Solution ConsoleITUAM processing engineITUAM data collectors

Microsoft Report ViewerMicrosoft Internet Information ServicesITUAM reporting application

ITUAMDB

Applicationserver

ReportingserverApplication

server


Figure 2-6 Large scale environment

Embedded WebSphere Application Server 6.1Integrated Solution ConsoleITUAM processing engineITUAM data collectors

Microsoft Report ViewerMicrosoft Internet Information ServicesITUAM reporting application

ITUAMDB

Applicationserver

ReportingserverApplication

server

ITUAMDB

replication


Chapter 3. Project planning

This chapter discusses the necessary preparation for running a deployment project for Tivoli Usage and Accounting Manager. The discussion is divided into:

� 3.1, “Required skills” on page 32

� 3.2, “Solution description and assumptions” on page 32

� 3.3, “Task breakdown” on page 33

3


3.1 Required skills

For the implementation of Tivoli Usage and Accounting Manager V7.1, you would want to have the following prerequisite skills:

� Database skill for the database that you are using

� Operating system skill for the platform that you are using

� Usage data collection from the source platform

� Microsoft Reporting Server skill for developing new reports

� Understanding of the accounting and charge back system

Apart from the above requirements, you would have to know the Tivoli Usage and Accounting Manager itself. This includes:

� Working with Integrated Solution Console (ISC)

� Working with Tivoli Usage and Accounting Manager job runner

� Performing file transformation into Common Source Format (CSR)

IBM Tivoli Usage and Accounting Manager V7.1, SG24-7404 can also be used to get more information about these items.

3.2 Solution description and assumptions

The Tivoli Usage and Accounting Manager solution performs the following:

� Collects usage information from a customer’s system� Stores usage and accounting data in its database � Generates reports or invoices for usage data

The data collection methodology must be established using a series of planning sessions with the customer. In these sessions, the following items should be addressed:

� List of the data sources and their access methods to get the usage data, or if a supported method is available, this has to be understood. Some collection requires a certain feature to be enabled and certain authority may be needed to get access to this usage information.

� Understand the departmental structure of the customer to correctly define the account code structure that would allow a breakdown of accounting information to the appropriate department entity.


� Identify the granularity of data collection from the customer to correctly calculate the data space requirements

� Identify the required charging items from the customer and how to get the data unit from the raw usage data

� Identify the reporting and maybe invoice requirements from the customer

Based on the above requirements from the customer, you can start developing the solution configuration and implementation methods. The configuration involves defining where to put critical components, such as application server and Web reporting server; the implementation method, including deployment of the server and data collectors.

Sometimes you can perform only a sub-set of the identified final configuration. The complete configuration would be up to the customer to implement. You must predetermine the initial sub-set to implement that is representative of the final configuration.

3.3 Task breakdown

The detailed tasks for Tivoli Usage and Accounting Manager implementation are divided into:

� 3.3.1, “Project kick-off” on page 33� 3.3.2, “Environment preparation” on page 34� 3.3.3, “Database setup” on page 34� 3.3.4, “Tivoli Usage and Accounting Manager server installation” on page 34� 3.3.5, “Data collection pack setup” on page 34� 3.3.6, “Customizing the product” on page 35� 3.3.7, “Demonstrating the solution and skill transfer” on page 35

3.3.1 Project kick-off

The kick-off of the project is a critical task during which the participants are identified, the roles and responsibilities are presented, and a generic project plan is laid out.

The kick-off is also an important milestone to promote the project to the customer’s user base and generate interest for the project.

Chapter 3. Project planning 33

3.3.2 Environment preparation

The initial environment preparation has these objectives:

� Installing and preparing the new server machines with the appropriate operating system and network connectivity. This applies to the machines that will run the database, the application server, and the Web reporting server.

� Identifying client or agent machines on which data collectors will be installed. This includes tabulating their IP addresses, hostnames, owners, access to the machine, and other relevant information.

� Collecting installation media and required software for the installation.

Depending on the size of the implementation and the readiness of the environment, this can take several hours or several days.

3.3.3 Database setup

Once the environment preparation is done, you can install the supported database product. The database will be used as the center of processing for Tivoli Usage and Accounting Manager. Depending on the database configuration, you may set up additional features such as replication to improve the data availability. We will demonstrate DB2 Enterprise Server Edition V9.1 in 4.2, “Installing DB2” on page 41.

3.3.4 Tivoli Usage and Accounting Manager server installation

Depending on how many servers you want to configure, you may need to run the Tivoli Usage and Accounting Manager installation program several times. The installation program installs all the necessary components including an embedded WebSphere Application Server and, in Windows, it also installs the Web reporting application. The detailed procedure of this installation is provided in 4.4, “Installing server components” on page 65.

3.3.5 Data collection pack setup

Data collection pack installation is platform dependent. We demonstrate the Windows collector pack installation in 4.7, “Installing Windows Process Collector” on page 85. Some of the collector pack can be deployed using the Tivoli Usage and Accounting Manager job interface.


3.3.6 Customizing the product

Product customization includes:

� Defining Tivoli Usage and Accounting Manager configuration objects� Defining Tivoli Usage and Accounting Manager rates, rate groups, calendar,

clients, and schedules� Collecting usage data � Creating data loading jobs� Customizing reports

This is where the design of the solution is implemented. The identified requirement from 3.2, “Solution description and assumptions” on page 32 should be realized in this task. This task is discussed in 4.6, “Initial configuration” on page 71.

3.3.7 Demonstrating the solution and skill transfer

After the customization has been completed and the solution is in place, you can demonstrate the result to the customer. This demonstration can serve as your completion milestone. You must also perform skill transfer so the customer’s personnel can operate and maintain the solution on a day-to-day basis. This is an important task that ensures smooth handover of the project.

The demonstration tasks are provided in Chapter 5, “Usage demonstration” on page 93.

Chapter 3. Project planning 35

Part 2 Deployment

Part 2


Chapter 4. Installation and configuration

This chapter discusses the installation and configuration of Tivoli Usage and Accounting Manager. The discussion is divided into the following topics:

� 4.1, “Installation overview” on page 40

� 4.2, “Installing DB2” on page 41

� 4.3, “Installing server prerequisites” on page 54

� 4.4, “Installing server components” on page 65

� 4.5, “Installing Enterprise Collector Pack” on page 69

� 4.6, “Initial configuration” on page 71

� 4.7, “Installing Windows Process Collector” on page 85

4


4.1 Installation overview

The installation in this chapter is done in a single-server environment. The deployment is done on a Windows 2003 Standard Edition with Service Pack 1 machine as shown in Figure 4-1.

Figure 4-1 Installation environment

The steps are:

1. Installation of the server:

a. DB2 Universal Database installation and database creation as discussed in 4.2, “Installing DB2” on page 41.

b. Microsoft Internet Information Server, Microsoft .NET framework and Microsoft Report Viewer are needed for the Web reporting application; see 4.3, “Installing server prerequisites” on page 54.

c. Tivoli Usage and Accounting Manager Enterprise Edition server, which includes an embedded WebSphere Application Server and Integrated Solution Console application, is installed in 4.4, “Installing server components” on page 65.

d. The supported collectors are installed in a bundle called the Enterprise Collector Pack as discussed in 4.5, “Installing Enterprise Collector Pack” on page 69.

e. Some setup of the Tivoli Usage and Accounting Manager application using the Integrated Solution Console is needed; see 4.6, “Initial configuration” 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



2. Deploying collectors to all participating machines is discussed in 4.7, “Installing Windows Process Collector” on page 85; we present both the manual and the Job runner deployment.

4.2 Installing DB2

We used the DB2 database in our server. The DB2 Universal Database Enterprise Server Edition V9.1 is installed as follows:

1. The initial DB2 installation panel when you invoke the setup.exe or from the autorun is the Launchpad shown in Figure 4-2.

Figure 4-2 Launchpad

Attention: To use the DB2 database in the same Windows machine with Tivoli Usage and Accounting Manager, you have to ensure that the DB2 .NET driver that is used by Microsoft Internet Information Server is the supplied DB2 Run Time Client. The current distribution uses DB2 V9.1 with Fix Pack 2. Typically, this is set at the DB2 installation time.

Chapter 4. Installation and configuration 41

2. Selecting the Install a Product link gives you the product installation choices shown in Figure 4-3.

Figure 4-3 Installation choices

3. Click Install Now. The DB2 installation wizard is started. Figure 4-4 on page 43 shows the initial DB2 installation window.


Figure 4-4 DB2 installation - welcome dialog

4. After you click Next, Figure 4-5 on page 44 shows the DB2 license agreement. Select to accept the license agreement and click Next.


Figure 4-5 License agreement

5. For the setup type, we chose a typical setup as shown in Figure 4-6 on page 45.


Figure 4-6 Setup type

6. Figure 4-7 on page 46 indicates that we are just installing DB2 and not creating any response files.


Figure 4-7 Response file option

7. Select the destination directory. Figure 4-8 on page 47 indicates that we use C:\IBM\SQLLIB.


Figure 4-8 Destination directory

8. Figure 4-9 on page 48 sets the user ID that we use, DB2ADMIN, and its password.


Figure 4-9 DB2 user ID and its password

9. Figure 4-10 on page 49 shows the instance name to be created, which is DB2.


Figure 4-10 Instance name

10.Figure 4-11 on page 50 shows that we do not prepare the tools catalog.


Figure 4-11 Tools catalog creation option

11.Figure 4-12 on page 51 ignores the notification option that DB2 may set up.


Figure 4-12 Setup notification

12.Operating system authentication is chosen in Figure 4-13 on page 52.


Figure 4-13 Operating system authentication

13.Figure 4-14 on page 53 shows a summary of the installation options.


Figure 4-14 Installation options summary

14.Figure 4-15 on page 54 indicates that setup is complete.


Figure 4-15 Setup completion

15.Creating the database is shown in Figure 4-16. 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 the default 4 K page size and to create an additional definition of buffer and tablespaces for larger page sizes such as 16 K.

Figure 4-16 Creating the database and buffer pools

4.3 Installing server prerequisites

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

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


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

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

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

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

4.3.1 Configuring Microsoft Internet Information Server

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

1. The program can be started from: All Programs → Administrative Tools → Manage Your Server. See Figure 4-17 on page 56.


Figure 4-17 Manage your server dialog

2. Click the Add a role link and it will start the configure your server wizard as shown in Figure 4-18 on page 57.


Figure 4-18 Configure server wizard

3. In the configuration options dialog shown in Figure 4-19, select Custom configuration.

Figure 4-19 Configuration selection


4. In Figure 4-20 on page 58, select the application server and click Next.

Figure 4-20 Server role selection

5. In Figure 4-21, select ASP.NET and click Next.

Figure 4-21 Feature selection


6. The installation commenced with a progress bar. Figure 4-22 shows that the installation is then finished.

Figure 4-22 Installation completed

4.3.2 Install the Microsoft Installer

An up-to-date version of the Windows Installer software needs to be available on the Report server system.

1. Download the Windows Installer from:

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

2. We executed the program WindowsInstaller-KB884016-v2-x86.exe to run the installation of the Windows Installer. The Welcome screen is displayed (Figure 4-23). Select Next.

Note: In our environment with Windows 2003 SP1 (as required by DB2 V9.1) we do not need the installation of Microsoft Installer. However, we also noticed that the .NET Framework 2.0 requires this installation.


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

Figure 4-23 Welcome screen for the Windows Installer installation

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

Figure 4-24 License agreement for the Windows Installer

4. Selected files on your system are backed up. The Windows Installer is installed; the completion window is shown in Figure 4-25. Select Finish to end the installation.


Figure 4-25 Completion of the installation for the Windows Installer software

4.3.3 Install Microsoft .NET Framework 2.0

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

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

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

2. Run the downloaded program to start the installation and select Next at the Welcome screen. Accept the license agreement and select Install as in Figure 4-26. The installation progress window is displayed.




Figure 4-26 Accept the .NET license agreement and start the installation

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

Figure 4-27 Setup complete for the .NET framework software


4.3.4 Install Microsoft SQL Server Report Viewer

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

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

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

2. Save the downloaded file as ReportViewer.exe.

3. We ran the program ReportViewer.exe to install the Report Viewer. The Welcome screen is displayed (Figure 4-28). Select Next.

Figure 4-28 Welcome screen for the Report Viewer installation

4. Accept the license agreement and select Install as in Figure 4-29.




Figure 4-29 License agreement for the Report Viewer and install the software

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

Figure 4-30 Successful installation of the Report Viewer


4.4 Installing server components

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

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

All the following files must exist 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

The installation steps are:

1. Run the program setup-tuam-ee-7-1-0-wintel_ia32.exe to install the Report server. Select Next on the Welcome screen. Accept the license agreement and select Next as in Figure 4-31.

Figure 4-31 License agreement for Tivoli Usage and Accounting Manager


2. We installed the application server into the C:\IBM\tuam\ directory; see Figure 4-32. The default directory is C:\Program Files\ibm\tuam. Select Next.

Figure 4-32 Define the installation directory for the Report server software

3. Check the Windows Web Reporting option as shown in Figure 4-33. Select Next.

Figure 4-33 Select the Windows Web Reporting option


4. We chose the virtual directory option as shown in figure Figure 4-34. Select Next.

Figure 4-34 Select a new virtual directory for Web reports

5. Select Install on the summary information screen. The installation progress indicator is displayed.

6. A task is automatically initiated to unpack the installed files, shown in Figure 4-35.


Figure 4-35 Unpacking of the Application server software on the Report server

7. Successful completion of the installation is indicated with the summary information shown in Figure 4-36. Select Finish to end the installation.

Figure 4-36 Successful installation of the Report server software


4.5 Installing Enterprise Collector Pack

The Enterprise Collector Pack is a separate installable component that provides all available collections for usage data that are supported for the platform. The Enterprise Collector Pack must be installed on the machine with the Tivoli Usage and Accounting Manager Enterprise Edition. The installation is performed from the file setup-tuam-ecp-7-1-0-wintel_ia32.exe. The installation dialog is as follows:

1. The Welcome window is shown in Figure 4-37. Click Next.

Figure 4-37 Welcome dialog

2. The license agreement is shown in Figure 4-38 on page 70. Accept the agreement and click Next.


Figure 4-38 License agreement

3. The Enterprise Collector Pack is always installed in the directory that the Enterprise Edition is installed in. Figure 4-39 shows the summary window for the installation; click Install.

Figure 4-39 Summary window

4. When the installation completes, Figure 4-40 shows the completion dialog.


Figure 4-40 Completion dialog

4.6 Initial configuration

There are several initial configurations that you need to do before you can use Tivoli Usage and Accounting Manager. These can be done from the Integrated Solution Console. Figure 4-41 on page 72 shows the console Welcome page.


Figure 4-41 Welcome page

This section explains the following:

� 4.6.1, “Defining the JDBC driver” on page 72� 4.6.2, “Defining data sources” on page 76� 4.6.3, “Initializing the database” on page 78

4.6.1 Defining the JDBC driver

The configuration of the JDBC driver for Tivoli Usage and Accounting Manager depends on the database software that has been installed. The DB2 Universal Database that we used comes with the JDBC drivers. We used the db2jcc.jar and db2jcc_license_cu.jar files. The following configures 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 4-42 on page 73.

Note: Tivoli Usage and Accounting Manager does not install the database We created the database when we installed DB2 in 4.2, “Installing DB2” on page 41.


Figure 4-42 Configuring the JDBC driver

2. In the Driver tab, click New to define the driver. Find the driver file in the tree in Figure 4-43 on page 74. Click OK when done.


Figure 4-43 Finding the JDBC driver

3. The JDBC jar files are shown in Figure 4-44 on page 75. Click OK when done.


Figure 4-44 JDBC driver

4. Figure 4-45 on page 76 shows the final JDBC driver configuration in our system.


Figure 4-45 Final JDBC driver configuration

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

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

4.6.2 Defining data sources

Once you have the definition of the JDBC drivers, you can define the data sources. Using the ISC, add the data source. We added the 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 4-46 on page 77.


Figure 4-46 Editing the default data source

3. Figure 4-47 on page 78 shows the changes we made for the default data source.


Figure 4-47 Default data source

4. Figure 4-48 on page 78 shows that the changes completed.

Figure 4-48 Default data source changes

4.6.3 Initializing the database

Once the data source is defined, you must initialize the database. Initializing the Tivoli Usage and Accounting Manager database creates and populates database tables and other database objects. Initializing the database is invoked from the


ISC and is performed against the databases that are identified as the default administration data source.

1. To initialize the Tivoli Usage and Accounting Manager database using the ISC menu, we select Usage and Accounting Manager → System Maintenance → Database → Initialize Database; see Figure 4-49.

Figure 4-49 Initialize the database

2. Click Initialize Database. Confirm the dialog in Figure 4-50 and click Yes.

Figure 4-50 Confirmation dialog

3. Figure 4-51 shows that the initialization of the database is complete.


Figure 4-51 Initializing the database

4.6.4 Other configurations

Once the database is initialized, the configuration dialog shows more options than just JDBC drivers, as shown in Figure 4-52 on page 81.


Figure 4-52 Configuration options

The Logging option is shown in Figure 4-53 on page 82.


Figure 4-53 Logging options

Figure 4-54 on page 83 sets up the organization property in the CIMSCONFIG table.


Figure 4-54 Organization properties

Figure 4-55 on page 84 shows the job runner processing properties. These properties are recorded in the CIMSCONFIGOPTION table. These directories have to exist. We change the process definition path from the samples sub-directory, so we have to create that directory.


Figure 4-55 Processing properties

Figure 4-56 on page 85 shows the reporting properties. We did not change any of the defaults.


Figure 4-56 Reporting properties

4.7 Installing Windows Process Collector

The Windows Process Collector must be installed on the machines on which we are performing usage accounting. We now demonstrate the Windows Process Collector installation.

4.7.1 Manual installation process

The Windows Process Collector is installed as follows:

1. Manually install the Windows Process Collector by executing the setup-tuam-wpc-7-1-0-windows_32_64.exe file. Make sure that the setup.jar and wpc.rsp files are located in the directory from which you are running the installer, as shown in Figure 4-57.


Figure 4-57 Manually execute the Windows Process data collector installer

2. If a security warning is displayed, select Run.

3. The Install wizard starts. Select Next in the Welcome window.

4. Accept the license agreement and select Next.

5. If required, modify the directory name of the installation path and select Next (Figure 4-58.)

Figure 4-58 Set the directory path for the Windows Process data collector

6. If required, update the data collector configuration according to your requirements, as shown in Figure 4-59. We accepted the defaults and selected Next. The option to Start application after installation and during reboot allows the job to run automatically.


Figure 4-59 Customize the Windows Process Collector

7. Review the summary information and select Install.

8. The installation progress window is displayed. Review the information in the summary information window and select Finish to complete the installation. Figure 4-60 shows the successful completion window.

Figure 4-60 Successful installation of the Windows Process Collector


4.7.2 Deploying with a job

The Windows Process Collector can also be deployed with a job. The job is copied from the SampleDeployProcessCollector.xml file.

1. Go to Usage and Accounting Manager → ChargeBack Maintenance → JobRunner → Sample jobs and select the SampleDeployProcessCollector.xml file as shown in Figure 4-61. Select the XML file and press Ctrl-C to copy the content.

Figure 4-61 The SampleDeployProcessCollector.xml file

2. Go to Usage and Accounting Manager → ChargeBack Maintenance → JobRunner → Job files as shown in Figure 4-62 on page 89. Click New.


Figure 4-62 New job file

3. Create a new job; we called it DeployProcessCollector.xml as shown in Figure 4-63. Click OK.

Figure 4-63 Define a new job

4. When the job file is created, replace its content with the paste key Ctrl-V and validate the job using Validate Job as shown in Figure 4-64 on page 90.


Figure 4-64 Validated new job

5. Modify the job by specifying the correct hostname, user ID, and password for accessing the target machine. For deploying this, you must run the job on another Windows machine. Click Run Job and answer the prompt in Figure 4-65 on page 91.


Figure 4-65 Job run options

6. After the job has completed successfully, you can check the result from Usage and Accounting Manager → ChargeBack Maintenance → JobRunner → Log files, as shown in Figure 4-66 on page 92.


Figure 4-66 Verifying the job result

Note: If you notice that the deployment took a long time, check whether there is a process called vcredist_x86.exe running in the target machine. This may be an incompatibility of the Tivoli Usage and Accounting Manager distributed Visual C++® library and the Windows version that you are using. Stop the process and install Visual C++ library SP1 from the Microsoft Web site.


Chapter 5. Usage demonstration

This chapter explores the use of Tivoli Usage and Accounting Manager. We demonstrate collecting Windows process accounting. The description is provided in the following sections:

� 5.1, “Demonstration overview” on page 94

� 5.2, “Defining accounting resources” on page 95

� 5.3, “Running Windows collection” on page 102

� 5.4, “Loading Windows process data” on page 105

� 5.5, “Generating Windows reports” on page 112

� 5.6, “Additional demonstration scenarios” on page 117

5


5.1 Demonstration overview

In the usage demonstration, we show the process of collecting usage data for the running Windows processes. These running processes are collected using the Windows process collection package of Tivoli Usage and Accounting Manager. The configuration is shown in Figure 5-1.

Figure 5-1 Demonstration environment

The demonstration should be performed after the collectors run for a day, so we recommend to run the demonstration the day after the installation completed. Some of the data collection files are written with the date changes. The steps are as follows:

1. Configuring Tivoli Usage and Accounting Manager accounting resources is discussed in 5.2, “Defining accounting resources” on page 95.

2. Verifying that the Windows collection is running as shown in 5.3, “Running Windows collection” on page 102.

3. Configuring and running the data collection job as discussed in 5.4, “Loading Windows process data” on page 105.

4. Generating usage reports and sample invoices for the data is demonstrated in 5.5, “Generating Windows reports” on page 112.

Finally, in 5.6, “Additional demonstration scenarios” on page 117 we present some other possible demonstration scenarios that you may use, depending on client requirements.

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


twin02



5.2 Defining accounting resources

In Tivoli Usage and Accounting Manager, you must prepare the environment for account processing. The following demonstrate some of the functions:

� 5.2.1, “Working with the account code structure” on page 95� 5.2.2, “Setting up clients” on page 97� 5.2.3, “Rate table” on page 101

5.2.1 Working with the account code structure

Account code is the primary identifier that signifies who should be 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 are labelled by the account code, hence it would be very hard to change the structure. This section explains the usage of the account code in Tivoli Usage and Accounting Manager, which should help you to define the account code structure according to your needs.

Account code is a string with a fixed width field that defines the hierarchy of the accounting breakdown. The fields are used to split the account string for charging different organizational entities. Figure 5-2 shows a sample account code and its relation to charging rate.

Figure 5-2 Sample account code with four parts and the rate code relationship

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

Chapter 5. Usage demonstration 95

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 are 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, as needed. The rate in the specific rate table is matched to the resource name in the resources segment of the 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 about 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 and/or WORK_ID.

The default account code structure is shown in Figure 5-3. This can be maintained using the Integrated Solutions Console (ISC) menu and selecting Usage and Accounting Manager → System Maintenance → Account Code Structure.

Restriction: Defining a new rate group using the ISC Rate menu is limited to eight characters. Using the ISC Rate Group menu, you can rename a group later or create longer names, such as the examples shipped with Tivoli Usage and Accounting Manager are using.


Figure 5-3 Default Tivoli Usage and Accounting Manager Account Code Structure

The structure is adequate for our demonstration environment. However, for most production implementations, you may need a longer client name (the sample in Figure 5-2 on page 95 shows an 8-character client name).

5.2.2 Setting up clients

Client information is used to map the existing account code into a selection of rate tables. Initially there is only one rate table, called STANDARD. You can see the client list under Usage and Accounting Manager → ChargeBack Maintenance → Clients. The default clients are shown in Figure 5-4.


Figure 5-4 Default clients list

In our demonstration, we do not need these clients, which are based on application names. It may be useful to change the client list into departmental names to generate a better illustration. We define a new client called WIN for our Windows process information. Click New and fill in the form in Figure 5-5.

Note: The client is typically a department or a division within an enterprise. It can also be a real customer for a service provider environment. We use a department called WIN to represent Windows users.


Figure 5-5 New client name

We removed all other clients using Delete. The resulting client list is shown in Figure 5-6.

Figure 5-6 The modified client list

Selecting WIN from the drop-down menu, we select Add Contact. Click New. Figure 5-7 on page 100 shows the contact information entry.


Figure 5-7 Contact information

Figure 5-8 shows the updated contact list.

Figure 5-8 Contact list


5.2.3 Rate table

The rates are defined under Usage and Accounting Manage → ChargeBack Maintenance → Rates. We filter the rate table to show only the rates that start with WIN* as shown in Figure 5-9.

Figure 5-9 Windows rate table

In Figure 5-9, all the rates are defined in the STANDARD rate table.

For reporting purposes, rates are grouped into rate groups. The menu Usage and Accounting Manage → ChargeBack Maintenance → Rate groups for Windows processing is shown in Figure 5-10 on page 102.


Figure 5-10 Windows process rate group

Now all the basic entities in Tivoli Usage and Accounting Manager have been explored and defined.

5.3 Running Windows collection

We now describe the Windows collection processing.


5.3.1 Verifying the Windows process data collector installation

Three techniques are used to verify the deployment, namely a directory listing, a listing of the services installed, and a display of an executing task. You perform these from the system where the Windows process data collector was installed.

� List the contents of the directory that contains the data collector software. Use the directory path specified during the install. The files located in the directory are listed in Figure 5-11.

Figure 5-11 Directory listing of the Windows process data collector install path

� Using the Windows menus, select Control Panel → Administrative Tools → Services. Confirm that the Usage and Accounting Manager Process Collector has been added as a service, as shown in Figure 5-12.


Figure 5-12 Tivoli Usage and Accounting Manager Windows collector service

� Start the Windows Task Manager and select the Processes tab. Verify that the WINPService.exe task is running, as indicated in Figure 5-13.

Figure 5-13 Tivoli Usage and Accounting Manager executable


5.3.2 Windows process data files

The result of the collection are data files. These data files are located depending on the log file path parameter that is specified at installation time. A sample of a file list created by the Windows data collector is displayed in Figure 5-14.

Figure 5-14 List of files created by the Windows data collector

The file produced by the Windows data collector must be transferred to the processing server. These daily files should be transferred after midnight on the day they are produced, because the file is switched at midnight. Use the technique most suited to your environment to perform the transfer.

If the processing server is a Windows-based machine, you can simply use a network share to connect and transfer, or run a FileTransfer step for Job Runner. If the processing server is not a Windows-based machine, you may need to use SSH to collect data from the Windows server. A non-Windows processing server requires that you use an Integrator program instead of WSF to process the data. The default processing out-of-the-box is using WSF. For an alternative use of an Integrator program for Windows processing data, see IBM Tivoli Usage and Accounting Manager V7.1 Handbook, SG24-7404. Once the data is in the processing server, you can start loading the data.

5.4 Loading Windows process data

The loading process uses the Job Runner, which provides an XML-based batch job definition that allows multiple job steps. You can run the job using the


startJobRunner command or from the Integrated Solution Console. You may also employ a job scheduling system to schedule the Job Runner execution.

The discussion consists of the following:

� 5.4.1, “The data collection process” on page 106� 5.4.2, “Account code mapping” on page 108� 5.4.3, “Running the collection job” on page 111

5.4.1 The data collection process

The SampleWinProcess.xml job supplied with Tivoli Usage and Accounting Manager uses the WinProcess.wsf. The WinProcess.wsf is a Windows script file that converts the input data to CSR format. This script will not work in a non-Windows processing server.

The WinProcess.wsf script performs the following actions:

� Extracts type “S” (start) and type “I” (interval) records.

� Removes header and entries for System Idle Processes that are not used for accounting purposes.

� Formats the data into CSR format for output; input field mapping depends on the record type.

The overall processing flow is demonstrated in Figure 5-15. The complete listing of the job file is provided in Appendix A, “Sample listing” on page 135.


Figure 5-15 Overview of Windows processing

The steps are:

1. Using WinProcess.wsf, map the process file into CSR format.

2. The scan process merges output files into a single file called CurrentCSR.txt.

3. The Integrator computes the account code and removes unused fields. In this case we drop the page fault (WINPGFLT) measurement, which generates the AcctCSR.txt file.

4. Billing processing allocates the resources, applies rates, and performs CPU normalization. It generates the summary, detail, and identifier files.

5. The billing files are loaded into the Tivoli Usage and Accounting Manager database.

In 5.4.2, “Account code mapping” on page 108, we present a bit more of the account code processing since we wanted to demonstrate the account code usage. This also requires a modification in the SampleWinProcess.xml job file.

Windows Process data

20071008.txt

Step 2 : Scan

CurrentCSR.txt

Step 4 : Bill

BillDetail.txtBillSummary.txt

Ident.txt

Step 5: DBLoad

AcctCSR.txt

Step 1 : WSFWinProcess.wsf

Step 3: Integrator

CreateIdentifierFromIdentifier

DropFields

CSR Output


5.4.2 Account code mapping

The default account code mapping for Windows process data is a concatenation from the fields Server and User. This may not be sufficient for most processing. The account code structure is shown in Figure 5-16.

Figure 5-16 Account code structure

We planned to use the mapping shown in Figure 5-17.

Figure 5-17 Account code mapping

Application (4)

Resource group (16)

Platform (16)

Server (20)

“WIN “

Mapping from the user name, to be either of:

SYSTEMDRIVERUSER

Server

Parsing of the User field


To generate this mapping, we performed the following integrator processing:

1. Defined static fields called appl and platform with the values of WIN and Windows using the stage CreateIdentifierFromValue.

2. Mapped the user name to the resource group using CreateIdentifierFromTable, which maps the executing user into the resource group. The conversion table that we used is shown in Example 5-1.

Example 5-1 Conversion table

NT A,NT z,SYSTEMAdministrator,Administrator,ADMINA,z,USER

3. Created the account code identifier using CreateIdentifierFromIdentifiers and mapped the identifier fields appl, resourcegroup, platform, and Feed.

4. Dropped unused fields using the DropFields stage, including dropping appl, platform, and resourcegroup fields as they have been recorded in the Account_Code field.

The overall integration stages are shown in Example 5-2.

Example 5-2 Integrator stage

<Integrator><Input name=”CSRInput”>

<Files><File name=”CurrentCSR.txt”></Files></Input><Stage name=”CreateIdentifierFromValue” active=”true”>

<Identifiers> <Identifier name="appl" value="WIN"/><Identifier name="platform" value="Windows”/>

</Identifiers></Stage><Stage name=”CreateIdentifierFromTable” activ=”true”>

<Identifiers><Identifier name="resgroup">

<FromIdentifiers><FromIdentifier name="User" offset="1" length="16"/>

</FromIdentifiers></Identifier>

Note: The conversion table format is three-part, comma-separated values. The first two values identify the source range (low to high) and the third value is the conversion output.


</Identifiers><Files>

<File name="Table.txt" type="table"/><File name="Excp.txt" type="exception" format="CSROutput"/>

</Files><Parameters>

<Parameter exceptionProcess="true"/><Parameter sort="true"/><Parameter upperCase="false"/><Parameter writeNoMatch="false"/><Parameter modifyIfExists="true"/>

</Parameters></Stage><Stage name="CreateIdentifierFromIdentifiers" active="true">

<Identifiers><Identifier name="Account_Code">

<FromIdentifiers><FromIdentifier name="appl" offset="1" length="4"/><FromIdentifier name="resgroup" offset="1" length="16"/><FromIdentifier name="Server" offset="1" length="16"/><FromIdentifier name="User" offset="1" length="20"/>

</FromIdentifiers></Identifier>

</Identifiers><Parameters>

<Parameter keepLength="true"/><Parameter modifyIfExists="true"/>

</Parameters></Stage><Stage name="DropFields" active="true">

<Fields><Field name="appl"/><Field name="platform"/><Field name="resgroup"/><Field name="WINPGFLT"/>

</Fields></Stage><Stage name="CSROutput" active="true">

<Files><File name="%ProcessFolder%/AcctCSR.txt"/></Files></Stage>

</Integrator>


5.4.3 Running the collection job

The collection job is created from the SampleWinProcess.xml sample. Use the copy process discussed in 4.7.2, “Deploying with a job” on page 88. Copy the content of SampleWinProcess.xml into a new job file called WinProcess.xml.

Modify Step 3, the integrator step with the account code mapping logic from Example 5-2. Validate the job using the Validate Job button, and correct any syntax error in the job.

Click Run Job to run the job. It should finish successfully. Again, correct any errors that you may encounter before proceeding. Figure 5-18 shows the output of the job.

Figure 5-18 Job log result

You can also see that the load is performed from the Load tracking detail, as shown in Figure 5-19 on page 112.


Figure 5-19 Load tracking result

5.5 Generating Windows reports

Once the data is collected, we can start demonstrating the usage report. The reporting application is based on user authentication from the Users setting. The ISC definition of the default users is shown in Figure 5-20.

Figure 5-20 User list

The user group’s default definition is shown in Figure 5-21 on page 113.


Figure 5-21 User group

The setting of a group determines access to the Financial Modeler feature. From on the drop-down of the group and select Edit. See the setting in Figure 5-22. We enable financial modeler and administrative access.

Figure 5-22 Group setting


The report is accessed using the URL:

http://tuamsrv/tuam

Log in using the userid admin and the default password password. See the login steps in Figure 5-23.

Figure 5-23 Login to the Web reporting

We demonstrate some of the reports.

� Figure 5-24 on page 115 shows the summary usage report in a cross table.


http://tuamsrv/tuam

Figure 5-24 Summary crosstab for usage

� Figure 5-25 on page 116 shows the daily charges.


Figure 5-25 Daily charges

� Figure 5-26 on page 117 shows a generated invoice report.


Figure 5-26 Invoice

5.6 Additional demonstration scenarios

Tivoli Usage and Accounting Manager provides a wide range of data collection and processing routines. You may want to demonstrate some other data collection capabilities. Some important collections that you may want to consider are:


� Other platforms that you may want to collect usage accounting from, such as a Linux or UNIX platform.

� Virtualization environment accounting, such as System p™ partitioning or VMware ESX server.

� Application-specific collection, such as Lotus Notes application usage and size, SAP data or others.

� User-defined data collection, which may be the toughest option, but with the appropriate experience, this can demonstrate the best flexible solution that Tivoli Usage and Accounting Manager can offer.

One important aspect of running these demonstrations is the mapping of the Account Code, which must be carefully considered because this provides the best way of illustrating charge breakdown of the usage data.

5.7 Financial Modeler

The Financial Modeler is a spreadsheet model that allows manipulation of financial cost and budget calculations. It performs analysis that can lead to correction of the rate table.

This section walks you through the steps of using the Financial Modeler. In this sample, we are working with the following:

� A budget system that has 2 pools— 200,000 for mainframe maintenance and 250,000 for distributed systems.

� We analyze z/OS, Windows and UNIX server rates; we assume CPU usage is the chargeback criteria.

1. Logging into the Financial Modeler

– The URL for our Financial Modeler is:http://tuamsrv/FinancialModeler

– Log in with the user ID and password that has access to the Financial Modeler; we use the admin user.

– Click Cancel when prompted for opening a model, because we will create a new model. See the steps in Figure 5-27 on page 119.


http://tuamsrv/FinancialModeler

Figure 5-27 Starting Financial Modeler

2. Creating a new model wizard by clicking New; see Figure 5-28 on page 120. The wizard collects information about:

– Budget pools– Budget subpools– Rate codes


Figure 5-28 Model creation wizard

3. Working with the allocation view. Once the model is created, we get the spreadsheet view. The view has 4 tabs, which are:

– Budget values - this allows the budget to be entered; see Figure 5-29 on page 121.


Figure 5-29 Budget values

– Percent allocation - assign percentage values for the rate group from the budget subpools; see Figure 5-30.

Figure 5-30 Rate allocation


– Cost calculations - from the allocation, the modeler calculates the amount for the period for each resource; see Figure 5-31.

Figure 5-31 Cost calculation

– Rate calculation - the usage data is then retrieved from the database to match the budget allocation; see Figure 5-32 on page 123. The value can be refreshed after changing the date selection using Calculate Rates. The computed values are shown in the yellow-shaded background.

Note: A subpool relates to one or more Rate Codes. You can choose any percentage you want; but make sure it adds up to 100%.


Figure 5-32 Rate calculation

4. Saving the model - click Save.

Note: The default rate calculation calculates for a zero profit. Adjust the time period that you retrieved the data from. You can change the uplift Factor to adjust the rate. Click on Update Rates to save the calculated rates.


Chapter 6. Troubleshooting hints and tips

This chapter provides some tips on problem solving when using Tivoli Usage and Accounting Manager. The discussion is divided into:

� 6.1, “General logging and tracing options” on page 126

� 6.2, “Installation and configuration details” on page 128

� 6.3, “Integrated Solution Console debugging” on page 128

� 6.4, “Job Runner debugging” on page 130

� 6.5, “Quick finder for trace and log information” on page 132

6


6.1 General logging and tracing options

The logging and tracing settings for Tivoli Usage and Accounting Manager are stored in the logging.properties configuration file, which is located in /opt/ibm/tuam/config.

The logging.properties file can be accessed from the Integrated Solution Console (ISC) Web interface in the Configuration page, as shown in Figure 6-1, by selecting Usage and Accounting Manager → System Maintenance → Configuration → Logging.

Figure 6-1 Logging options

You can set the file size for tracing and logging files, number of generations, and logging levels. These trace files are written to the /opt/ibm/tuam/logs/server directory.

Our sample logging.properties file is shown in Example 6-1.

Example 6-1 Sample logging.properties

#Oct 31, 2007 12:16:08 PM


handlers=com.ibm.tivoli.ituam.logger.MessageFileHandler,com.ibm.tivoli.ituam.logger.TraceFileHandler.level=FINESTcom.ibm.tivoli.tuam.logger.MessageFileHandler.append=truecom.ibm.tivoli.tuam.logger.MessageFileHandler.count=11com.ibm.tivoli.tuam.logger.MessageFileHandler.formatter=java.util.logging.SimpleFormattercom.ibm.tivoli.tuam.logger.MessageFileHandler.level=INFOcom.ibm.tivoli.tuam.logger.MessageFileHandler.limit=10000000com.ibm.tivoli.tuam.logger.MessageFileHandler.pattern=C:/ibm/tuam/logs/server/message%g.logcom.ibm.tivoli.tuam.logger.TraceFileHandler.append=truecom.ibm.tivoli.tuam.logger.TraceFileHandler.count=11com.ibm.tivoli.tuam.logger.TraceFileHandler.formatter=java.util.logging.SimpleFormattercom.ibm.tivoli.tuam.logger.TraceFileHandler.level=FINESTcom.ibm.tivoli.tuam.logger.TraceFileHandler.limit=10000000com.ibm.tivoli.tuam.logger.TraceFileHandler.pattern=C:/ibm/tuam/logs/server/trace%g.log

As indicated in Example 6-1, the settings are for the message file and trace file. The settings include:

append Whether to append to the log files after a restart

count Number of generations of the log file

formatter Log file formatter class

level Level of logging to be recorded in this type of log

limit File size limit, before a new generation is created

pattern File name of the log file, the default is using Trace%g.log or Message%g.log (%g indicates the generation number)

The trace and log files are written from the Integrated Solution Console and job processes. Every time a process is accessing the trace or message file, a lock file (.lck) is created. If another process wants to write to a log file, it creates an additional trace file with a numbered suffix.

The trace and message log files name is in the format <type><n>.log.<m>; where:

type Message or tracen Archived log file serial number; the current log has the serial

number of 0 m Number entries for different processes that write log files

Chapter 6. Troubleshooting hints and tips 127

The reporting application uses a different log file called trace_net0.log. This is generated from the application under the Microsoft Internet Information Server.

6.2 Installation and configuration details

The installation process has a different logging default than the program itself. It is typically the Tivoli common logging directory, which in Windows is \Program Files\ibm\tivoli\common\AUC\logs\install. However, in UNIX it is /opt/ibm/tivoli/common/AUC/logs/install.

The log file for the Enterprise Edition and Enterprise Collector Pack is called TUAMInstall.log. In Windows, there is an additional DB2RTCInstall.log file for the DB2 UDB V9.1 run time client. The Windows Process Collector creates an additional log file called WPCInstall.log.

The installation stages for the Enterprise Edition are performed mostly from the setup\console directory:

1. The files are transferred into the installation directory.

2. The wizard installs an embedded WebSphere Application Server and the Integrated Solution Console, which is performed by simply unzipping the EmbeddedExpress and ISCAE71 zip files.

3. The wizard deploys the Tivoli Usage and Accounting Manager application using the deployTUAM.bat command to run deployTUAMConsole.py, which installs the aucConsole.war file.

4. In Windows only, the wizard invokes db2rtc.bat to install the DB2 runtime client.

5. Post installation is performed using the tuamPostInstall.bat. In Windows, it installs the report application using iisconfig.vbs, and installation of the FinancialModeler using financialModelerConfig.bat.

6.3 Integrated Solution Console debugging

The Integrated Solution Console is based on a WebSphere Application Server. Apart from the standard Tivoli Usage and Accounting Manager logging files, some information can also be retrieved from the WebSphere logs.

WebSphere logs are the standard output and standard error of the WebSphere’s JVM™. These are in $TUAM_home/ewas/profiles/AppSrv01/logs/server1 with the file name of SystemOut.log and SystemErr.log, respectively.


Doing configuration tasks, you might get a message as in Figure 6-2. You should check for the Tivoli Usage and Accounting Manager server logs first. Then you might need to check your database logs. In certain cases it might help to watch for the WebSphere logs, to get some information on connectivity.

Figure 6-2 Error message about a database task

For some messages (see Figure 6-3) you may not need to watch for details in the log.


Figure 6-3 Error message about a configuration task

6.4 Job Runner debugging

For the Tivoli Usage and Accounting Manager processing engine, the trace option can be set, in addition, in the XML job files at the step and stage level.

� Acct step parameter trace=”true”

� Bill step parameter trace=”true”

� Integrator step will set it on the stage level: <Stage name="function" trace="true">

� For the Integrator collector section, use <parameter name=”trace” value=”on” />

Note: The trace options are not consistent yet, so you may try using upper or lowercase and ON instead of true in some cases.


Two types of output are produced when a job is running:

� A Job Runner log file, which is located in the /opt/ibm/tuam/logs/jobrunner directory in a directory named according to the Job ID parameter value in the job file. The XML version is for the ISC to display the log file, and a text version can be used for searching on the command line level or viewing with an editor.

� The Trace and message files, located in the /opt/ibm/tuam/logs/server directory, are active for the entire life of the application server running under the embedded WebSphere Application Server.

Running a job from the ISC, failures will cause an error message as shown in Figure 6-4.

Figure 6-4 Error message due to a job failure

Fore more details, we can search the log files shown in Figure 6-5.

Figure 6-5 Searching the logs on the command line level

For detailed analysis of the last log, you might issue the command:

ls -tr | tail -1 | while read file; do more $file; done

[root@srv105 /]# cd /opt/ibm/tuam/logs/jobrunner/AIXAA_aggregated[root@srv105 AIXAA_aggregated]# ls -tr *txt | tail -3 | while read file ; do grep -E .*AUCJR003[1-2].* $file; done11/5/07 13:32:11.197: INFORMATION AUCJR0032I The job AIXAA_aggregated completed at Nov 5, 2007 1:32:11 PM with 1 warning, 0 errors.11/5/07 13:52:47.560: INFORMATION AUCJR0031I The AIXAA_aggregated process completed successfully at the following time: Nov 5, 2007 1:52:47 PM.11/5/07 13:53:44.934: INFORMATION AUCJR0032I The job AIXAA_aggregated completed at Nov 5, 2007 1:53:44 PM with 0 warnings, 1 error.[root@srv105 AIXAA_aggregated]# ls -tr *txt | tail -1 | while read file ; do echo $file ; grep -i warn $file | wc -l; grep -i error $file | wc -l ; done20071105_135342.txt4 # shows the # of warnings8 # shows the # of errors


6.5 Quick finder for trace and log information

Table 6-1 is a summary of where to change settings and search for files.

Table 6-1 Overview for trace and log files

Path or file name Function

/opt/ibm/tuam/logs/jobrunner/<JobId>Job runner log files separated per JobID

<timestamp>.txt Job log output

<timestamp>.xml Job log for use with the ISC

/opt/ibm/tuam/logs/server/Tivoli Usage and Accounting Manager trace and log files

message0.log message<g>.log<#>

Messages from tuam processing, where<g> = generation and <#> = instance.

trace0.logtrace<g>.log<#>

Trace details for tuam processing, where<g> = generation and <#> = instance.

*.lck lock files for trace and log coordination

trace_net0.log Trace for the reporting server on Windows only.

/opt/ibm/tuam/ewas/profiles/AppSrv01SystemOut.log/logs/server1WebSphere and Integrated Solutions Console (ISC) files

SystemOut.log WebSphere messages

SystemErr.log WebSphere error log

/opt/ibm/tuam/configTivoli Usage and Accounting Manager config files

logging.properties settings for trace and message files

jdk_logging.properties not used with version 7.1

/opt/ibm/tivoli/common/AUC/logs/installInstallation and uninstallation log files


Part 3 Appendixes

Part 3


Appendix A. Sample listing

The listings are:

� “Sample Windows load job” on page 136

� “Sample Windows process collector job” on page 140

A


Sample Windows load job

<?xml version=”1.0” encoding=”utf-8”?><Jobs xmlns=”http://www.ibm.com/TUAMJobs.xsd”> <Job id=”SampleWinProcess” description=”Daily collection” active=”true” joblogShowStepParameters=”true” joblogShowStepOutput=”true” processPriorityClass=”Low” joblogWriteToTextFile=”true” joblogWriteToXMLFile=”true” smtpSendJobLog=”true” smtpServer=”mail.ITUAMCustomerCompany.com” smtpFrom=”[email protected]” smtpTo=”[email protected]” stopOnProcessFailure=”false”> <Process id=”WinProcess” description=”Process for Windows Process Collection” active=”true”> <Steps stopOnStepFailure=”true”> <Step id=”Server1 Collection” description=”Server1 WinProcess” type=”ConvertToCSR” programName=”WinProcess/WinProcess.wsf” programType=”wsf” active=”true”> <Parameters> <Parameter Feed=”Server1”/>

<Parameter LogFolder=”%CollectorLogs%/WinProcess”/> </Parameters> </Step> <Step id=”Scan” description=”Scan WinProcess” type=”Process” programName=”Scan” programType=”java” active=”true”> <Parameters> <Parameter retainFileDate=”false”/> <Parameter allowMissingFiles=”false”/> <Parameter allowEmptyFiles=”false”/> <Parameter useStepFiles=”false”/> </Parameters> </Step> <Step id=”Integrator” description=”Standard Processing for WinProcess” type=”Process” programName=”integrator” programType=”java” active=”true”><Integrator> <Input name=”CSRInput”> <Files><File name=”%ProcessFolder%/CurrentCSR.txt”/></Files> </Input> <Stage name=”CreateIdentifierFromValue” active=”true”> <Identifiers> <Identifier name=”appl” value=”WIN”/> <Identifier name=”platform” value=”Windows”/> </Identifiers> </Stage> <Stage name=”CreateIdentifierFromRegEx” active=”true”> <Identifiers> <Identifier name=”ntuser”> <FromIdentifiers> <FromIdentifier name=”User” regEx=”(\w+)\\(\w+)” value=”$2”/> </FromIdentifiers> </Identifier> </Identifiers> <Parameters> <Parameter keepLength=”true”/>

Appendix A. Sample listing 137

</FromIdentifiers> </Identifier> </Identifiers> <Parameters> <Parameter keepLength=”true”/> <Parameter modifyIfExists=”true”/> </Parameters> </Stage> <Stage name=”DropFields” active=”true”> <Fields> <Field name=”appl”/> <Field name=”platform”/> <Field name=”resgroup”/> <Field name=”ntuser”/> <Field name=”WINPGFLT”/> </Fields> </Stage> <Stage name=”CSROutput” active=”true”> <Files><File name=”%ProcessFolder%/AcctCSR.txt”/></Files> </Stage></Integrator> </Step> <Step id=”Process” description=”Standard Processing for WinProcess” type=”Process” programName=”Bill” programType=”java” active=”true”> <Bill> <Parameters> </Parameters> </Bill> </Step> <Step id=”DatabaseLoad” description=”Database Load for WinProcess” type=”Process” programName=”DBLoad” programType=”java” active=”true”> <DBLoad> <Parameters> </Parameters> </DBLoad> </Step>


<Step id=”Cleanup” description=”Cleanup WinProcess” type=”Process” programName=”Cleanup” programType=”java” active=”false”> <Parameters> <Parameter DaysToRetainFiles=”45”/> </Parameters> </Step> </Steps> </Process>

</Job></Jobs>

Sample Windows process collector job

<?xml version=”1.0” encoding=”utf-8”?><Jobs xmlns=”http://www.ibm.com/TUAMJobs.xsd”> <Job id=”DeployProcessCollector” description=”Deploy the Process Collector Agent” active=”true” joblogShowStepParameters=”true” joblogShowStepOutput=”true” processPriorityClass=”Low” joblogWriteToTextFile=”true” joblogWriteToXMLFile=”true” smtpSendJobLog=”false”

smtpServer=”mail.ITUAMCustomerCompany.com” smtpFrom=”[email protected]” smtpTo=”[email protected]” stopOnProcessFailure=”false”> <Process id=”DeployProcessCollector” description=”Deployment of the Process Collector Agent” joblogShowStepOutput=”true” joblogShowStepParameters=”true” active=”true”>

<Steps stopOnStepFailure=”true”> <Step id=”Server1 Deployment” description=”Server1 Deployment” type=”ConvertToCSR” programName=”rpd” programType=”java” active=”true”> <Parameters> <Parameter Action = “install”/> <Parameter Host = “twin01”/> <Parameter UserId = “Administrator”/> <Parameter Password = “its0g00d”/>  <Parameter Protocol = “win”/>  <Parameter Verbose = “true”/> <Parameter SourcePath = “%HomePath%/collectors/winprocess”/>

 <Parameter Manifest = “32bit/DeploymentManifest.xml”/>

</Parameters> </Step> </Steps> </Process>

<Process id=”RemoveProcessCollector” description=”Removal of the Process Collector Agent” joblogShowStepOutput=”true” joblogShowStepParameters=”true” active=”false”>

<Steps stopOnStepFailure=”true”> <Step id=”Server1 Removal” description=”Server1 Removal” type=”ConvertToCSR” programName=”rpd” programType=”java” active=”true”> <Parameters> <Parameter Action = “remove”/> <Parameter Host = “test-remove”/> <Parameter UserId = “someid”/> <Parameter Password = “somepassword”/>   <Parameter Verbose = “true”/> <Parameter SourcePath = “%HomePath%/collectors/winprocess”/>

 <Parameter Manifest = “32bit/DeploymentManifest.xml”/>   </Parameters> </Step> </Steps>

</Process> </Job></Jobs>


Appendix B. Additional material

This book refers to additional material that can be downloaded from the Internet as described below.

Locating the Web material

The Web material associated with this book is available in softcopy on the Internet from the IBM Redbooks Web server. Point your Web browser at:

ftp://www.redbooks.ibm.com/redbooks/SG247569

Alternatively, you can go to the IBM Redbooks Web site at:

ibm.com/redbooks

Select the Additional materials and open the directory that corresponds with the IBM Redbooks form number, SG247569.

B


ftp://www.redbooks.ibm.com/redbooks/



Using the Web material

The additional Web material that accompanies this book includes the following files:

File name DescriptionSG247569.zip Zipped code samples

System requirements for downloading the Web material

The Web material is used in conjunction with the IBM Tivoli Usage and Accounting Manager. You should follow the hardware requirement for the product. The Web material itself used:

Hard disk space: 20 KB

How to use the Web material

Create a subdirectory (folder) on your workstation, and unzip the contents of the Web material zip file into this folder.


acronyms

AIX Advanced Interactive eXecutive

BIRT Business Intelligence and Reporting Tool

CPU Central Processing Unit

CSR Common Source Format

FTP File Transfer Protocol

GB Giga bytes

HTTP Hyper Text Transfer Protocol

I/O Input Output

IBM International Business Machine Corp.

IIS Internet Information Server

IP Internet Protocol

ISC Integrated Solution Console

IT Information Technology

ITIL IT Infrastructure Library

ITSO International Technical Support Organization

JDBC Java Data Base Connectivity

JVM Java Virtual Machine

LPAR Logical Partition

MB Mega Byte

OGC Office of Goverment Commerce

OS Operating System

ROI Return on Investment

SQL Structured Query Language

SSH Secure Shell

UDB Universal Database

URL Universal Resource Locator

WSF Windows Script File

XML eXtended Markup Language

Abbreviations and

© Copyright IBM Corp. 2008. All rights reserved.
147

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 150. Note that some of the documents referenced here may be available in softcopy only.

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

� Accounting and Chargeback with Tivoli Decision Support for OS/390, SG24-6044

Other publications

These publications are also relevant as further information sources:

� Tivoli Usage and Accounting Manager Quick Start Guide, GC23-6188

Online resources

These Web sites are also relevant as further information sources:

� 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

� 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/

Index

Symbols/opt/ibm/tivoli/common/AUC/logs/install. 128/opt/ibm/tuam/config 126/opt/ibm/tuam/logs/jobrunner 131/opt/ibm/tuam/logs/server 126, 131

AAccount code 95account code mapping 108Account_Code 16AcctCSR 22application server 11assumptions 32

BBilling detail 22Billing summary 22BIRT 8, 12budget calculation 118Business Intelligence and Reporting Tools, see BIRT

CClient 96commands

db2rtc.bat 128ls 131setup.exe 41startJobRunner 106startServer.bat 76stopServer.bat 76

Common Source Format, see CSRCommon Source Resource, see CSRconfiguration 94cost calculation 118crosstab 115CSR 13–14, 32CSR format 106CSR Plus Header 15CSR+ records 14CSRInput 109

© Copyright IBM Corp. 2008. All rights reserved.

Ddaily charges 115data sizing 21database size 21db2rtc.bat command 128demonstration 35demonstration scenarios 117DeployProcessCollector.xml 89deployTUAM.bat 128deployTUAMConsole.py 128description 32

EEmbeddedExpress 128environment preparation 34Extensible Markup Language, see XMLeXtensible Markup Language, see XML

FFeed 16files

CIBMuamewasbinstartServer.bat 76IBMuamewasbinstopServer.bat 76

DeployProcessCollector.xml 89deployTUAM.bat 128deployTUAMConsole.py 128trace_net0.log 128WinPServices.exe 104WPCInstall.log 128

Financial Modelerfeature 113

financial modeler 118

Ggroup access 113

Hhardware prerequisites 18headeraccountcode 15headeraccountcodelength 15headerenddate 15

151

headerendtime 15headerrectype 15headershiftcode 15headerstartdate 15headerstarttime 15

IIdentifier table 22Identifiers 15IIS 8, 55implementation skills 32implementation tasks 33installation

configuration 94Integrated Solution Console, see ISCIntegrated Solutions Console, see ISCIntegrator 109Internet Information Services, see IISInternet Security and Acceleration, see ISAISA 9ISC 11, 32, 96, 126ISCAE71 128IT Infrastructure Library®, see ITILITCAM for Response Time

implementation tasks 33ITIL 4

JJob

validate 111job files 130job result 92

Kkick off 33

Lls command 131

Mmessage log files 127Model creation wizard 120

Nnetwork connectivity 34

OOffice of Government Commerce, see OGCOGC 4operating system 34organizational entity 95

Ppaths

/opt/ibm/tivoli/common/AUC/logs/install. 128/opt/ibm/tuam/config 126/opt/ibm/tuam/logs/jobrunner 131/opt/ibm/tuam/logs/server 126, 131

prerequisites 18Process Engine 12project initiation 33

Rrate groups 96Rate Table 96Redbooks Web site 150

Contact us xiResource utilization 22Resources 15Return of Investment, see ROIROI 6

SSampleWinProcess.xml 106setup.exe command 41sizing consideration 21skill transfer 35skills 32software prerequisites 18solution assumptions 32solution demonstration 35solution descriptions 32spreadsheet 118startJobRunner command 106startServer.bat 76stopServer.bat 76SYSTEM_ID 16

TTivoli Usage and Accounting Manager skills 32trace log files 127trace_net0.log 128


WWindows process data

data files 105loading 105

Windows reports 112WINPGFLT 107WinProcess.wsf 107WINPService.exe 104WORK_ID 16WPCInstall.log 128

XXML 12

Index 153

(0.2”spine)0.17”<

->0.473”

90<->

249 pages

Deployment Guide Series: IBM

Tivoli Usage and Accounting Manager

®

SG24-7569-00 ISBN 0738485659

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

®

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

Financial management solution for IT-related services

Extensive deployment and demonstration examples

Planning and services information

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 to 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 consideration before you implement the product is 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.

Back cover




deployment guide series ibm tivoli usage and accounting manager v7.1 sg247569

Technology

usage demonstration

windows process data

loading windows process

solution environment

windows collection102

windows reports

sample windows load

data elements222