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

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

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.

Chapter 1. Solution introduction 15

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.

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.

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

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