Beruflich Dokumente
Kultur Dokumente
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
ibm.com/redbooks
International Technical Support Organization Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1 February 2008
SG24-7569-00
Note: Before using this information and the product it supports, read the information in Notices on page vii.
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).
Copyright International Business Machines Corporation 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Part 1. Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Chapter 1. Solution introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 ITIL financial management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2 Tivoli Usage and Accounting Manager features . . . . . . . . . . . . . . . . . . . . . 7 1.3 Tivoli Usage and Accounting Manager value proposition . . . . . . . . . . . . . 10 1.4 Product architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4.1 Generic processing flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.4.2 The Common Source Resource format . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 2. Solution environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.1 Hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2 Software prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.1 Supported operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.2 Supported databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.3 Sizing considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.3.1 Data elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.3.2 Growth factors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.3.3 Sample growth estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 2.4 Typical deployment environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 2.4.1 Small, proof of concept, or demonstration environment . . . . . . . . . . 27 2.4.2 Medium scale production environment . . . . . . . . . . . . . . . . . . . . . . . 27 2.4.3 Large scale production environment . . . . . . . . . . . . . . . . . . . . . . . . . 28 Chapter 3. Project planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.1 Required skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.2 Solution description and assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3 Task breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.3.1 Project kick-off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.3.2 Environment preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.3.3 Database setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
iii
Tivoli Usage and Accounting Manager server installation . . . . . . . . 34 Data collection pack setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Customizing the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Demonstrating the solution and skill transfer . . . . . . . . . . . . . . . . . . 35
Part 2. Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Chapter 4. Installation and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 39 4.1 Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.2 Installing DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4.3 Installing server prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 4.3.1 Configuring Microsoft Internet Information Server . . . . . . . . . . . . . . 55 4.3.2 Install the Microsoft Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.3.3 Install Microsoft .NET Framework 2.0 . . . . . . . . . . . . . . . . . . . . . . . . 61 4.3.4 Install Microsoft SQL Server Report Viewer . . . . . . . . . . . . . . . . . . . 63 4.4 Installing server components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.5 Installing Enterprise Collector Pack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 4.6 Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 4.6.1 Defining the JDBC driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 4.6.2 Defining data sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 4.6.3 Initializing the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 4.6.4 Other configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 4.7 Installing Windows Process Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.7.1 Manual installation process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 4.7.2 Deploying with a job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Chapter 5. Usage demonstration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 5.1 Demonstration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 5.2 Defining accounting resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 5.2.1 Working with the account code structure . . . . . . . . . . . . . . . . . . . . . 95 5.2.2 Setting up clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 5.2.3 Rate table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 5.3 Running Windows collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 5.3.1 Verifying the Windows process data collector installation. . . . . . . . 103 5.3.2 Windows process data files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.4 Loading Windows process data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 5.4.1 The data collection process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 5.4.2 Account code mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 5.4.3 Running the collection job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
iv
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
5.5 Generating Windows reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 5.6 Additional demonstration scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 5.7 Financial Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Chapter 6. Troubleshooting hints and tips . . . . . . . . . . . . . . . . . . . . . . . . 125 6.1 General logging and tracing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 6.2 Installation and configuration details . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.3 Integrated Solution Console debugging . . . . . . . . . . . . . . . . . . . . . . . . . 128 6.4 Job Runner debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 6.5 Quick finder for trace and log information . . . . . . . . . . . . . . . . . . . . . . . . 132 Part 3. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Appendix A. Sample listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Sample Windows load job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Sample Windows process collector job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Appendix B. Additional material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Locating the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Using the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 System requirements for downloading the Web material . . . . . . . . . . . . . 146 How to use the Web material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Contents
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.
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.
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. Jrn 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 Howard IBM Software Group, Tivoli Systems Alfred Schwab, Editor International Technical Support Organization, Poughkeepsie Center
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: redbooks@us.ibm.com Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099 2455 South Road Poughkeepsie, NY 12601-5400
Preface
xi
xii
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Part 1
Part
Planning
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
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Service management The business The business perspective Service support ICT Infrastructure management
The technology
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.
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.
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
10
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Collection
Reporting Vmware Web Services SDK Data collector File Administration Tivoli Decision Support for z/ OS Database
Processing
File
Application Server
Reporting Server
Process engine
Web Reporting
Financial Modeler
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
11
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).
12
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Aggregation
Data Collector
Web or data base dataSource Summarized data (CSR) reprocess
Account Conversion
Account Table
Output file Output file Output (CSR+) files (CSR+) (CSR+) ITUAMDB
Database Load
Scan (Merging)
Ident file
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.
13
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. 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.
14
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
CSR Plus Header CSR+ records only start with CSR+ constant headerstartdate Usage start date headerenddate Usage end date headeraccountcodelength Length of the Account code (three digits) headeraccountcode Account Code constant headerrectype Record type or source headerstartdate Usage start date headerenddate Usage end date headerstarttime Usage start time headerendtime Usage end time headershiftcode Shift code The header information is used to identify the applicability of the record to a certain billing period and type. Tip: All header% variables can be used with the Integrator identifier functions. 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
15
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.016 AATRID10,20071030,20071030,01:15:03,01:15:03,1,2,SYSTEM_ID,"02101F170", Account_Code,"AIX 1TEST lpar04",1,AAID1002,0.004 AATRID4,20071030,20071030,02:30:07,02:30:07,1,2,SYSTEM_ID,"02101F25F",A ccount_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",Insta nce,"vm-33",Feed,"ITSC_VC",Account_Code,"WIN 1ESX",SYSTEM_ID,"srv079.it sc.austin.ibm.com",1,VMCPUUSE,10756036 VMWARE,20071017,20071017,00:00:00,23:59:59,1,5,HostName,"host-19",Insta nce,"vm-41",Feed,"ITSC_VC",Account_Code,"WIN 4ESX",SYSTEM_ID,"srv079.it sc.austin.ibm.com",1,VMCPUUSE,10688008 VMWARE,20071017,20071017,00:00:00,23:59:59,1,5,HostName,"host-8",Instan ce,"vm-31",Feed,"ITSC_VC",Account_Code,"WIN 0ESX",SYSTEM_ID,"srv106.its c.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 SYSTEM_ID WORK_ID Will be matched with the Account Code Structure and used for Rate Table selection and Reporting Aggregation Used for reading the factor from the Normalization Table during CPU normalization 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 Identifies and defines a subfolder in the process folder for data transfer
Feed
16
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
17
18
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
19
Platform RHEL 4.0 for x86 RHEL 5.0 for x86 RHEL 4.0 for AMD64 EM64T RHEL 5.0 for AMD64 EM64T RHEL 4.0 for System i RHEL 5.0 for System i RHEL 4.0 for System z (64 bit) RHEL 5.0 for System z (64 bit) RHEL 4.0 for PowerPC RHEL 5.0 for PowerPC SLES 9 for x86 SLES 10 for x86 SLES 9 for AMD64 EM64T SLES 10 for AMD64 EM64T SLES 9 for System z (64 bit) SLES 10 for System z (64 bit) SLES 9.0 for PowerPC SLES 10 for PowerPC VMware ESX i5/OS v5 zVM z/OS v 1.1 z/OS v1.2 z/OS v1.3 z/OS v1.4 z/OS v1.3, v1.4, v1.5, v1.6, v1.7, and v1.8b
Server Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No No No No
Collector Yes Yes Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Reporting No No No No No No No No No No No No No No No No No No No No No No No No No No
Web client Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No No No No No No No No
a. With support for advanced accounting collection for AIX V5.3 and AIX V6.
20
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
b. Available only with the Tivoli Usage and Accounting Manager for z/OS Option of Tivoli Decision Support for z/OS.
21
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).
Billing detail
Identifier table
Figure 2-1 on page 23 provides an overview of the relationship between these tables.
22
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Billing Detail LOADTRACKINGUID DETAILUID DETAILLINE ACCOUNTCODE AGGREGATE STARTDATE ENDDATE SHIFTCODE AUDITCODE SOURCESYSTEM RATECODE RESOURCEUNITS ACCOUNTINGSTARTDATE ACCOUNTINGENDDATE
Billing Summary LOADTRACKINGUID YEAR PERIOD SHIFT ACCOUNTCODE LENLEVEL% RATETABLE RATECODE STARTDATE ENDDATE RATEVALUE RESOURCEUNITS BREAKID MONEYVALUE USAGESTARTDATE USAGEENDDATE RUNDATE BILLFLAG%
Resource Utilization Get identifier LOADTRACKINGUID DETAILUID DETAILLINE ACCOUNTCODE AGGREGATE STARTDATE ENDDATE SHIFTCODE AUDITCODE SOURCESYSTEM RATECODE RESOURCEUNITS
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.
23
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 CIMSRESOURCE UTILIZATION CIMSSUMMARY CIMSDETAIL CIMSDETAILIDENT Row sizea 300 300 350 75 Affecting source
Source, Account_Code, Identifier mix, RateCode, Shift, #day Source, Account_Code, RateCode, Shift, #day Source, Account_Code, Identifier mix, Rate per id, Shift, #day Identifier mix x Ident count
24
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
25
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.
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.
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.
26
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Embedded WebSphere Application Server 6.1 Integrated Solution Console Microsoft Report Viewer Microsoft Internet Information Services ITUAM reporting application ITUAM processing engine ITUAM data collectors Database ITUAMDB
ITUAM server
Figure 2-4 Small scale environment
27
Embedded WebSphere Application Server 6.1 Integrated Solution Console ITUAM processing engine ITUAM data collectors
Microsoft Report Viewer Microsoft Internet Information Services ITUAM reporting application
Application server
Application server
Reporting server
ITUAMDB
28
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Embedded WebSphere Application Server 6.1 Integrated Solution Console ITUAM processing engine ITUAM data collectors
Microsoft Report Viewer Microsoft Internet Information Services ITUAM reporting application
Application server
Application server
replication
Reporting server
ITUAMDB
29
30
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
31
32
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
33
34
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
35
36
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Part 2
Part
Deployment
37
38
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Chapter 4.
39
tuamsrv
DB2 UDB 9.1 Usage Accounting Manager 7.1 EE Embedded WebSphere Application Server 6.1 Integrated Solution Console Usage Accounting Manager 7.1 ECP Usage Accounting Manager 7.1 WPC z
twin01
Windows Process Collector
twin02
Windows Process Collector
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.
40
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
41
2. Selecting the Install a Product link gives you the product installation choices shown in Figure 4-3.
3. Click Install Now. The DB2 installation wizard is started. Figure 4-4 on page 43 shows the initial DB2 installation window.
42
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
43
5. For the setup type, we chose a typical setup as shown in Figure 4-6 on page 45.
44
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
6. Figure 4-7 on page 46 indicates that we are just installing DB2 and not creating any response files.
45
7. Select the destination directory. Figure 4-8 on page 47 indicates that we use C:\IBM\SQLLIB.
46
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
8. Figure 4-9 on page 48 sets the user ID that we use, DB2ADMIN, and its password.
47
9. Figure 4-10 on page 49 shows the instance name to be created, which is DB2.
48
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
10.Figure 4-11 on page 50 shows that we do not prepare the tools catalog.
49
11.Figure 4-12 on page 51 ignores the notification option that DB2 may set up.
50
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
51
52
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
53
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. C:\>DB2 CREATE DB ITUAMDB CODESET UTF-8 PAGESIZE 16 K DB20000I The CREATE DATABASE command completed successfully.
Figure 4-16 Creating the database and buffer pools
54
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
55
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.
56
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
3. In the configuration options dialog shown in Figure 4-19, select Custom configuration.
57
4. In Figure 4-20 on page 58, select the application server and click Next.
58
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
6. The installation commenced with a progress bar. Figure 4-22 shows that the installation is then finished.
59
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.
60
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Figure 4-25 Completion of the installation for the Windows Installer software
61
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.
62
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
63
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.
64
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Figure 4-31 License agreement for Tivoli Usage and Accounting Manager
65
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.
66
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
4. We chose the virtual directory option as shown in figure Figure 4-34. Select Next.
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.
67
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.
68
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
2. The license agreement is shown in Figure 4-38 on page 70. Accept the agreement and click Next.
69
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.
4. When the installation completes, Figure 4-40 shows the completion dialog.
70
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
71
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. 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
72
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
73
3. The JDBC jar files are shown in Figure 4-44 on page 75. Click OK when done.
74
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
4. Figure 4-45 on page 76 shows the final JDBC driver configuration in our system.
75
5. After updating the JDBC driver, you should restart the Integrated Solution Console. Use the commands: C:\IBM\tuam\ewas\bin\stopServer.bat server1 C:\IBM\tuam\ewas\bin\startServer.bat server1
76
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
3. Figure 4-47 on page 78 shows the changes we made for the default data source.
77
78
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
2. Click Initialize Database. Confirm the dialog in Figure 4-50 and click Yes.
79
80
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
81
Figure 4-54 on page 83 sets up the organization property in the CIMSCONFIG table.
82
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
83
Figure 4-56 on page 85 shows the reporting properties. We did not change any of the defaults.
84
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
85
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.
86
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
87
2. Go to Usage and Accounting Manager ChargeBack Maintenance JobRunner Job files as shown in Figure 4-62 on page 89. Click New.
88
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
3. Create a new job; we called it DeployProcessCollector.xml as shown in Figure 4-63. Click OK.
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.
89
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.
90
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
91
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.
92
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
93
tuamsrv
DB2 UDB 9.1 Usage Accounting Manager 7.1 EE Embedded WebSphere Application Server 6.1 Integrated Solution Console Usage Accounting Manager 7.1 ECP Usage Accounting Manager 7.1 WPC z
twin01
Windows Process Collector
twin02
Windows Process Collector
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.
94
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Account code
Client 8 char Financial information 12 char Application 8 char Host 32 char
CSR record
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
Rate Table
Rate
VMCPUSY
Rate Group
VMware
Rate
VMDSKRD
Rate
WINCPUUS
Rate Group
Windows
Rate
WINDSKWR
Rate
WINMEMHI
Figure 5-2 Sample account code with four parts and the rate code relationship
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. 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. 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.
96
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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).
97
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.
98
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
We removed all other clients using Delete. The resulting client list is shown in Figure 5-6.
Selecting WIN from the drop-down menu, we select Add Contact. Click New. Figure 5-7 on page 100 shows the contact information entry.
99
100
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
101
Now all the basic entities in Tivoli Usage and Accounting Manager have been explored and defined.
102
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
103
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.
104
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
105
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
106
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Step 2 : Scan
AcctCSR.txt
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.
107
WIN
Server
108
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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. 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.
Example 5-1 Conversion table
NT A,NT z,SYSTEM Administrator,Administrator,ADMIN A,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>
109
</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>
110
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
You can also see that the load is performed from the Load tracking detail, as shown in Figure 5-19 on page 112.
111
The user groups default definition is shown in Figure 5-21 on page 113.
112
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
113
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.
We demonstrate some of the reports. Figure 5-24 on page 115 shows the summary usage report in a cross table.
114
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
115
116
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
117
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.
118
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
119
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.
120
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Percent allocation - assign percentage values for the rate group from the budget subpools; see Figure 5-30.
121
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%. Cost calculations - from the allocation, the modeler calculates the amount for the period for each resource; see Figure 5-31.
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.
122
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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. 4. Saving the model - click Save.
123
124
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Chapter 6.
125
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
126
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
handlers=com.ibm.tivoli.ituam.logger.MessageFileHandler,com.ibm.tivoli. ituam.logger.TraceFileHandler .level=FINEST com.ibm.tivoli.tuam.logger.MessageFileHandler.append=true com.ibm.tivoli.tuam.logger.MessageFileHandler.count=11 com.ibm.tivoli.tuam.logger.MessageFileHandler.formatter=java.util.loggi ng.SimpleFormatter com.ibm.tivoli.tuam.logger.MessageFileHandler.level=INFO com.ibm.tivoli.tuam.logger.MessageFileHandler.limit=10000000 com.ibm.tivoli.tuam.logger.MessageFileHandler.pattern=C:/ibm/tuam/logs/ server/message%g.log com.ibm.tivoli.tuam.logger.TraceFileHandler.append=true com.ibm.tivoli.tuam.logger.TraceFileHandler.count=11 com.ibm.tivoli.tuam.logger.TraceFileHandler.formatter=java.util.logging .SimpleFormatter com.ibm.tivoli.tuam.logger.TraceFileHandler.level=FINEST com.ibm.tivoli.tuam.logger.TraceFileHandler.limit=10000000 com.ibm.tivoli.tuam.logger.TraceFileHandler.pattern=C:/ibm/tuam/logs/se rver/trace%g.log As indicated in Example 6-1, the settings are for the message file and trace file. The settings include: append count formatter level limit pattern Whether to append to the log files after a restart Number of generations of the log file Log file formatter class Level of logging to be recorded in this type of log File size limit, before a new generation is created 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 n m Message or trace Archived log file serial number; the current log has the serial number of 0 Number entries for different processes that write log files
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.
128
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
For some messages (see Figure 6-3) you may not need to watch for details in the log.
129
130
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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.
Fore more details, we can search the log files shown in Figure 6-5.
[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; done 11/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 ; done 20071105_135342.txt 4 # shows the # of warnings 8 # shows the # of errors
For detailed analysis of the last log, you might issue the command: ls -tr | tail -1 | while read file; do more $file; done
131
/opt/ibm/tuam/logs/server/ Tivoli Usage and Accounting Manager trace and log files message0.log message<g>.log<#> trace0.log trace<g>.log<#> *.lck trace_net0.log Messages from tuam processing, where <g> = generation and <#> = instance. Trace details for tuam processing, where <g> = generation and <#> = instance. lock files for trace and log coordination Trace for the reporting server on Windows only.
/opt/ibm/tuam/ewas/profiles/AppSrv01SystemOut.log/logs/server1 WebSphere and Integrated Solutions Console (ISC) files SystemOut.log SystemErr.log WebSphere messages WebSphere error log
/opt/ibm/tuam/config Tivoli Usage and Accounting Manager config files logging.properties jdk_logging.properties /opt/ibm/tivoli/common/AUC/logs/install Installation and uninstallation log files settings for trace and message files not used with version 7.1
132
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Part 3
Part
Appendixes
133
134
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Appendix A.
Sample listing
The listings are: Sample Windows load job on page 136 Sample Windows process collector job on page 140
135
136
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
<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/>
137
<Parameter modifyIfExists=true/> </Parameters> </Stage> <Stage name=CreateIdentifierFromTable active=true> <Identifiers> <Identifier name=resgroup> <FromIdentifiers> <FromIdentifier name=ntuser offset=1 length=16/> </FromIdentifiers> </Identifier> </Identifiers> <Files> <File name=%ProcessFolder%/Table.txt type=table/> <File name=%ProcessFolder%/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=Feed> <FromIdentifiers> <FromIdentifier name=Server offset=1/> </FromIdentifiers> </Identifier> </Identifiers> <Parameters> <Parameter keepLength=true/> <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=ntuser offset=1 length=20/>
138
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
</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>
139
id=Cleanup description=Cleanup WinProcess type=Process programName=Cleanup programType=java active=false> <Parameters> <Parameter DaysToRetainFiles=45/> </Parameters> </Step> </Steps> </Process> </Job> </Jobs>
<Step
140
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
smtpServer=mail.ITUAMCustomerCompany.com smtpFrom=ITUAM@ITUAMCustomerCompany.com smtpTo=John.ITUAMUser@ITUAMCustomerCompany.com stopOnProcessFailure=false> <Process 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 KeyFilename = yourkeyfilename/--> <Parameter Protocol = win/> <!--Parameter RPDParameters = AccountingInterval=86400;AccountingIntervalCommand= ;AccountingIntervalTime=00:00;LogFileExtension=.txt;LogFilePath=%ITUAMI nstallPathRemote%CIMSWinProcessLogs;LogFilePrefix=CIMSProcessLog-;Sampl ingInterval=1;UseAccountingIntervalTime=No;UseLocalTime=Yes;WriteInterv alEndRecords=No;/--> <Parameter Verbose = true/> <Parameter SourcePath = %HomePath%/collectors/winprocess/> <!-- Note: For 32-bit systems, use the following Manifest tag. --> <Parameter Manifest = 32bit/DeploymentManifest.xml/> <!-- Note: For X64 64-bit systems, comment out the 32 bit Manifest tag (above), and uncomment the following line. --> id=DeployProcessCollector description=Deployment of the Process Collector
141
<!--Parameter Manifest 64bit/DeploymentManifestX64.xml/--> </Parameters> </Step> </Steps> </Process> <Process 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 KeyFilename = yourkeyfilename/--> <!--Parameter Protocol = win | ssh/--> <Parameter Verbose = true/> <Parameter SourcePath = %HomePath%/collectors/winprocess/> <!-- Note: For 32-bit systems, use the following Manifest tag. --> <Parameter Manifest = 32bit/DeploymentManifest.xml/> <!-- Note: For X64 64-bit systems, comment out the 32 bit Manifest tag (above), and uncomment the following line. --> <!--Parameter Manifest = 64bit/DeploymentManifestX64.xml/--> </Parameters> </Step> </Steps>
142
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
143
144
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Appendix B.
Additional material
This book refers to additional material that can be downloaded from the Internet as described below.
145
146
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
147
148
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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?top ic=/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/
149
150
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
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
D
daily charges 115 data sizing 21 database size 21 db2rtc.bat command 128 demonstration 35 demonstration scenarios 117 DeployProcessCollector.xml 89 deployTUAM.bat 128 deployTUAMConsole.py 128 description 32
A
Account code 95 account code mapping 108 Account_Code 16 AcctCSR 22 application server 11 assumptions 32
E
EmbeddedExpress 128 environment preparation 34 Extensible Markup Language, see XML eXtensible Markup Language, see XML
B
Billing detail 22 Billing summary 22 BIRT 8, 12 budget calculation 118 Business Intelligence and Reporting Tools, see BIRT
F
Feed 16 files C IBMuamewasbinstartServer.bat 76 IBMuamewasbinstopServer.bat 76 DeployProcessCollector.xml 89 deployTUAM.bat 128 deployTUAMConsole.py 128 trace_net0.log 128 WinPServices.exe 104 WPCInstall.log 128 Financial Modeler feature 113 financial modeler 118
C
Client 96 commands db2rtc.bat 128 ls 131 setup.exe 41 startJobRunner 106 startServer.bat 76 stopServer.bat 76 Common Source Format, see CSR Common Source Resource, see CSR configuration 94 cost calculation 118 crosstab 115 CSR 1314, 32 CSR format 106 CSR Plus Header 15 CSR+ records 14 CSRInput 109
G
group access 113
H
hardware prerequisites 18 headeraccountcode 15 headeraccountcodelength 15 headerenddate 15
151
O
Office of Government Commerce, see OGC OGC 4 operating system 34 organizational entity 95
I
Identifier table 22 Identifiers 15 IIS 8, 55 implementation skills 32 implementation tasks 33 installation configuration 94 Integrated Solution Console, see ISC Integrated Solutions Console, see ISC Integrator 109 Internet Information Services, see IIS Internet Security and Acceleration, see ISA ISA 9 ISC 11, 32, 96, 126 ISCAE71 128 IT Infrastructure Library, see ITIL ITCAM for Response Time implementation tasks 33 ITIL 4
P
paths /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 18 Process Engine 12 project initiation 33
R
rate groups 96 Rate Table 96 Redbooks Web site 150 Contact us xi Resource utilization 22 Resources 15 Return of Investment, see ROI ROI 6
J
Job validate 111 job files 130 job result 92
S
SampleWinProcess.xml 106 setup.exe command 41 sizing consideration 21 skill transfer 35 skills 32 software prerequisites 18 solution assumptions 32 solution demonstration 35 solution descriptions 32 spreadsheet 118 startJobRunner command 106 startServer.bat 76 stopServer.bat 76 SYSTEM_ID 16
K
kick off 33
L
ls command 131
M
message log files 127 Model creation wizard 120
T
Tivoli Usage and Accounting Manager skills 32 trace log files 127 trace_net0.log 128
N
network connectivity 34
152
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
W
Windows process data data files 105 loading 105 Windows reports 112 WINPGFLT 107 WinProcess.wsf 107 WINPService.exe 104 WORK_ID 16 WPCInstall.log 128
X
XML 12
Index
153
154
Deployment Guide Series: IBM Tivoli Usage and Accounting Manager V7.1
Back cover
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.
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL 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.