tivoli application performance management warehouse...

Tivoli Application Performance ManagementWarehouse Enablement Pack:

Implementation GuideDate of Last Update: 11 March, 2002

2

© Copyright International Business Machines Corporation 2002. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

3

About this Document .............................................................................................................................4Overview of Tivoli Enterprise Data Warehouse ..............................................................................5Design and Data Flow ............................................................................................................................6

APF_c05_Initialize_Process .................................................................................................................................6

APF_c10_CDW_Process.......................................................................................................................................6

Incremental extract implementation ...................................................................................................................6

Pruning old TAPM data .......................................................................................................................................7

Reinstalling the TAPM warehouse enablement pack ........................................................................................7

Source Database Information ..............................................................................................................9Known ETL limitations ........................................................................................................................................9

Late data load ....................................................................................................................................................................... 9Buckets set ......................................................................................................................................................................... 10

Generic Schema Implementation......................................................................................................111.1 Component Configuration.......................................................................................................................11

1.1.1 Component Type (table CompTyp).................................................................................................................... 111.1.2 Component (table Comp) ................................................................................................................................... 121.1.3 Component Relationship Type (table RelnTyp)................................................................................................. 141.1.4 Component Relationship Rule (table RelnRul) .................................................................................................. 141.1.5 Component Relationship (table CompReln)....................................................................................................... 141.1.6 Attribute Type (table AttrTyp) ........................................................................................................................... 151.1.7 Attribute Rule (table AttrRul) ............................................................................................................................ 151.1.8 Attribute Domain (table AttrDom) ..................................................................................................................... 161.1.9 Component Attribute (table CompAttr) ............................................................................................................. 16

1.2 Component Measurement .......................................................................................................................181.2.1 Measurement Group Type (table MGrpTyp) ..................................................................................................... 181.2.2 Measurement Group (table MGrp)..................................................................................................................... 181.2.3 Measurement Group Member (table MGrpMbr)................................................................................................ 181.2.4 Measurement Unit Category (table MUnitCat) .................................................................................................. 191.2.5 Measurement Unit (table MUnit) ....................................................................................................................... 191.2.6 Time Summary (table TmSum).......................................................................................................................... 191.2.7 Measurement Source (table MSrc) ..................................................................................................................... 191.2.8 Measurement Type (table MsmtTyp) ................................................................................................................. 191.2.9 Component Measurement Rule (table MsmtRul)............................................................................................... 201.2.10 Measurement (table Msmt)................................................................................................................................. 211.2.11 Extract Control (table Extract_Control) ............................................................................................................. 221.2.12 Extract Log (table Extract_Log)......................................................................................................................... 231.2.13 Helper Tables ..................................................................................................................................................... 241.2.14 Exception Tables ................................................................................................................................................ 24

4

About this DocumentThe Tivoli Enterprise Data Warehouse infrastructure enables a set of extract, transform, and load (ETL) utilitiesto extract and move data from Tivoli application data stores to a central data warehouse database. Databaseadministrators and programmers require the type of information provided in this document to install the ETL toolsand understand what data is being populated in the central data warehouse during what is referred to as thecentral data warehouse ETL.

5

Overview of Tivoli Enterprise Data WarehouseTivoli Enterprise Data Warehouse provides the infrastructure for the following:

Extract, transform, and load (ETL) processes through the IBM DB2 Data Warehouse Center toolSchema generation of the central data warehouseReport interfaces

As shown in Figure 1, Tivoli Enterprise Data Warehouse consists of a centralized data store where historicaldata from many management applications can be stored, aggregated, and correlated.

Figure 1. Tivoli Enterprise Data Warehouse overview

The central data warehouse uses a generic schema. As new components or new applications are added, moredata is added to the database; however, no new tables or columns are added in the schema.

The central data warehouse ETL reads the data from the operational data stores of the application that collectsit, verifies the data, makes the data conform to the schema, and places the data into the central data warehouse.

The data mart ETL extracts a subset of data from the central data warehouse, transforms it, and loads it into oneor more star schemas, which can be included in data marts to answer specific business questions.

A data mart is a subset of a data warehouse that contains data tailored and optimized for the specific reportingneeds of a department or team.

6

Design and Data Flow

Tivoli Application Performance Management (TAPM) summarizes transaction data at individual endpoints toproduce a single summary record at the end of the collection interval and logs individual transaction instancedata. The summary record is aggregated to hourly records uploaded, using the Tivoli RDBMS Interface Module(RIM), into a relational database. For more information, see the �Setting up the database" and "UsingPerformance Data" chapters in the Tivoli Application Performance Management User�s Guide Version 2.1.

The TAPM warehouse enablement pack for Tivoli Enterprise Data Warehouse, Version 1.1.0, is animplementation of the IBM DB2 Data Warehouse Center based on the data collected by TAPM version 2.1. Assuch, it provides a Data Warehouse Subject Area namedAPF_TivoliApplicationPerformanceManagement_v1.1.0_Subject_Area. Within this Subject Area, there are twoprocesses: APF_c05_Initialize_Process and APF_c10_CDW_Process.

Note that the TAPM ETL for TEDW will use only the aggregated data from the TAPM RIM database and not theinstance data.

Note that there is no data mart ETL processes provided. Therefore, providing Tivoli Application PerformanceManagement reports is not the purpose of this package. At this time, application performance specific reportingis provided by the �Tivoli Decision Support for Application Performance� Guide.

APF_c05_Initialize_Process

The APF_c05_Initialize_Process initializes the incremental extract logic. Run this process once to perform theinitial load of data into the warehouse. Use extreme caution when running the APF_c05_Initialize_Process asecond time. The second run of the APF_c05_Initialize_Process will attempt to load duplicate data into the TivoliEnterprise Data Warehouse. In special cases, such as a database recovery with a clean database, it might benecessary to reload all the data from the Tivoli Application Performance Management database to the TivoliEnterprise Data Warehouse schema. If the Tivoli Application Performance Management data has already beenloaded into the Tivoli Enterprise Data Warehouse, then in almost all cases the APF_c05_Initialize_Processshould not be run a second time.

This process has a step (APF_c05_s010_init) that resets the values of the Tivoli Enterprise Data WarehouseExtract_Control and Prune_Msmt_Control tables, used respectively to enable data to be incrementally extractedby the ETL processes and to remove old data from the Msmt table by a warehouse process. When you run thisstep the next process will be able to load all the data from the TAPM database into the TEDW database.

APF_c10_CDW_Process

This process loads the data from the TAPM database in the central data warehouse model. There are five stepsin this process: APF_c10_s010_rim, APF_c10_s020_comp, APF_c10_s030_compattr, APF_c10_s040_msmtand APF_c10_s050_msmt. The first one loads the TAPM data from the RIM database into the TEDW stagingtables; the second one populate the component table; the third one the component attribute table and the othersone the measurement table.

Incremental extract implementation

The incremental extract for TAPM is implemented in the following way.

7

New TAPM data in the source database are discovered looking at the integer ascending sequence IDs of thetables: HOSTS, TRANSACTIONS, ID_INFO, DATA32, DATA64 and DATABUCKETS. The select from the datasource is something like:

select x,y,x from source_table s, extract_control ec where s.marker_column > ec.from_seq and and s.marker_column <= ec.to_seq

since the join happens between the source_table (in the TAPM database) and the extract_control table (in theCDW database), a temporary version of extract_control is created in the source database, and the markervalues copied over to it (from the extract_control in the CDW) before the join happens. This takes away therequirement to store the extract_control and extract_log tables as permanent tables in the source database.

When the incremental extract is run the following actions are done:

– create a temporary table temp_extract_control to hold the extract window at TAPM– get the from_intseq value from the extract_control in the CDW and copy it to TAPM– update the temp_extract_control with the max tx_class_id, data_id, host_id and tx_id at TAPM– create the source staging tables at CDW– do the extract from TAPM to CDW– update the extract control with the to_intseq value at CDW– write extract info to the extract log. This fires the trigger that updates extract control to close the window

Pruning old TAPM data

Removing old data from the Msmt table is implemented with a combination of triggers and warehouseprocesses. CDW_C05_PurgeMsmt_Process is a process in theCDW_TivoliEnterpriseDataWarehouse_v1.1.0_Subject_Area subject area. You schedule when you want to runthe process: weekly, monthly, daily. What data gets pruned is controlled by the Prune_Msmt_Control table. Thedefault value set by TAPM is 31 days. You can modify the value by running the following SQL statement, whereX is a date duration whose format is yyyymmdd (for example: X = 00000108 for 0000 years, 01 month, 08 days).

UPDATE TWG.Prune_Msmt_Control SET PMSMTC_AGE_IN_DAYS = X WHERE TMSUM_CD = 'H' AND MSRC_CD = 'APF';

Reinstalling the TAPM warehouse enablement pack

When the TAPM warehouse enablement pack is uninstalled, TAPM data in the central data warehouse is notautomatically removed. This is because data in the central data warehouse is not tied to a specific application. Itis a historical record of activity and conditions in your enterprise. Although it might have been placed in thewarehouse by one application, it can be read by other applications, including those you write yourself. Therefore,Tivoli Enterprise Data Warehouse does not provide an automated way to delete data from the central datawarehouse, aside from the data pruning mechanisms.

If you do not delete the data, a subsequent reinstallation of the TAPM warehouse enablement pack can lead to apotential duplication of data in the central data warehouse. To avoid this situation, do the following after an ETLuninstallation:

8

1. Set PMSMTC_AGE_IN_DAYS = -1 in the PRUNE_MSMT_CONTROL table as described in �Pruning oldTAPM data.� Note that the PMSMTC_AGE_IN_DAYS value is -1 because the purge process does not delete thedata for the current day.2. Run the Warehouse PurgeMsmt process.3. Reinstall the TAPM warehouse enablement pack.4. Run the TAPM warehouse enablement pack steps.

Moreover after the step 4 TAPM warehouse enablement pack will retrieve all the data from the TAPM database.If you want a lesser amount of data in the warehouse, you must run the prune job/process after the install and itwill remove the unwanted measurements (but leaves the component data that central data warehouse need).

Figure 2. Tivoli Application Performance Management package data flow

Collect performance data on the Endpoints

Aggregate data at hour level

Upload data from Gateway to the RIM database

TAPM task

Load data from the TAPM RIM DB to CDW DB

Insert the data in the CDW generic data model

Central DataWarehouse ETL

Upload data from Endpoint to Gateway

9

Source Database Information

The source database for the ETL has to be the database in which TAPM is storing data. This means that thesource database is the database for which the Tivoli RIM object �tapm� is configured. TAPM 2.1 supports all thedatabases supported by the Tivoli Framework version 3.6.5 and 3.7.1 (Oracle, MS_SQL, Sybase, DB2 andInformix). The current TAPM ETL supports only DB2 and Oracle databases.

Before you define the warehouse source, you must verify that the TAPM database exists and that you canconnect to it. For DB2, you must catalog the database with ODBC. For Oracle, you must supply the system datasource name (DSN) by which the database is registered in ODBC on the agent site. Use the ODBC applet,accessible from the Windows NT Control Panel, to add the data source as a system data source. The ODBCdriver to be used for DB2 is "IBM DB2 ODBC DRIVER" Version 7.01.00.50 from IBM. The ODBC driver to beused for Oracle is "DataWHSE 3.60 32-bit Oracle8" Version 3.60 from MERANT.

The data source name assigned to TAPM after the installation is TAPM_RIM. Before running the ETL processes,you must be sure that the Warehouse Sources and the Warehouse Targets specific to the TAPM application arecorrectly defined (username, password, hostname, system data source).

You must also do the following:1. From the Data Warehouse Center window, expand the Warehouse Sources folder and then the item

APF_TAPM_Source.2. Click the Tables folder. The tables in the warehouse source are displayed on the right-hand side of the

window.3. If the Schema property is empty and the Name of the tables include the schema name, right-click each table

and select Properties. The Properties window opens.4. On the Source Table page, modify the Table schema and Table name properties with the values of the

TAPM database source. (This depends on how you create the TAPM database. Refer to the TAPMdocumentation for further detail). The table name should be the table name without "TAPM" to preventproblems when exporting the metadata to an ETL interchange file (*.tag), which can be imported at anotherData Warehouse Center.

See Installing and Configuring Tivoli Enterprise Data Warehouse for instructions on how to install TivoliEnterprise Data Warehouse.

Known ETL limitations

Late data load

When the TAPM ETL runs it pulls data from the TAPM database. When data is extracted from the TAPMdatabase the ETL will always pull an entire day of data instead of pulling a partial day�s data. For example, if theTAPM ETL runs at 7 p.m. on Wednesday, then the data for Wednesday will not be copied by the ETL. The datafor Wednesday will be copied to the central data warehouse when the TAPM ETL runs on Thursday.

In some error cases, there is the potential that the ETL will not copy all of the data from the TAPM database.This condition can happen when there is some delay in getting the data to the TAPM database. For example, ifTAPM is collecting data hourly, then the TAPM database may have data from an endpoint up to Wednesday at 9a.m. If the gateway goes down for 3 days, the data from that endpoint will not make it to the TAPM database for3 days. In most production environments, the TAPM ETL will run daily. This means that on Thursday the TAPMETL will pull over the measurement data up to 9 a.m. for the endpoint. On Saturday when the gateway comesback up, the data from 9 a.m. on Wednesday will arrive along with the data for Thursday and Friday. The late

10

data for Thursday and Friday will be moved into the warehouse, but the late data for Wednesday will never becopied to the Warehouse.

If all of the following conditions occur, then data will not be copied to the central data warehouse database:

1. The TAPM database has partial days data in the TAPM database relative to an application name, username, transaction name, and hostname.2. For some reason the data associated with the remainder of the day is delayed in arriving to the TAPMdatabase.3. The data has not arrived to the database when the TAPM ETL runs on the next day.

TAPM development is aware of this small window where data may not be copied to the warehouse. Additionalinformation about this problem can be obtained by contacting TAPM support and referencing Solution ID#1049180.

Buckets set

A problem could occur interpreting TAPM bucket limits stored in the central data warehouse if a TAPM collectionhas been set with a number of buckets less than 7 (the default value). The problem occurs because the TAPMstores the upper limit boundary for the unset buckets as 0. For example if you start a TAPM collection as�wmarstartcoll -a app1 -d 2 -b 2500,10000 <endpoint>� the upper limit boundary values stored in the file (anddatabase) are 2500,1000,0,0,0,0, 2147483647 while they should be 2500,1000,2147483647, 2147483647,2147483647, 2147483647, 2147483647.

The suggested workaround for this is to not leave unset values for the bucket limits in the wmarstartcollcommand (for example: wmarstartcoll -a app1 -d 2 -b 2500,1000,2147483647, 2147483647, 2147483647,2147483647 <endpoint>).

This problem will not impact the accuracy of the measurement data in the warehouse in anyway.

11

Generic Schema ImplementationRefer to the Tivoli Enterprise Data Warehouse central data warehouse generic schema before reading thissection. You will find the definitions and the relation of all the tables in this document. While the content of thetables changes from application to application, most applications will have data in all of the tables shown in thissection. All the columns may not be used. These do not contain any information

Note: Central data warehouse columns marked with an asterisk (*) indicate values that source applications areresponsible for translating and delivering corresponding Java resource bundles.

The sample data illustrated in the following tables is taken from the following TAPM data:

Hostname User name Application name Transaction namehost1 administrator IExplorer downloadhost2.dev.tivoli.com administrator Netscape downloadhost2.dev.tivoli.com goofy MSWord print

Hostname/Origin will be mapped into one of two types: IP_HOST or TAPM_HOST.IP_HOST is a component common to all applications in the warehouse. Rules specified in Enabling anApplication for Tivoli Enterprise Data Warehouse are used to determine if the Hostname or Origin slot valuesmeet these requirements. If not, a TAPM_HOST component is created.

1.1 Component ConfigurationThe following tables represent a set of devices and their interconnections.

1.1.1 Component Type (table CompTyp)

CompTyp_CdCHAR(17)

CompTyp_Parent_CdCHAR(17)

CompTyp_Nm*

VARCHAR(120)CompTyp_Strt_DtTm TIMESTAMP

CompTyp_End_DtTmTIMESTAMP

TAPM_TX TAPM Transaction 9999-01-0112:00:00.0

TAPM_APPL TAPM Application 9999-01-0112:00:00.0

TAPM_USER TAPM User 9999-01-0112:00:00.0

TAPM_HOST TAPM Host 9999-01-0112:00:00.0

The component types are: TAPM_TX, TAPM_APPL, TAPM_HOST, TAPM_USER

* Source applications must translate values in this column and deliver corresponding Java resource bundles.

12

1.1.2 Component (table Comp)

Comp_IDINTEGER

CompTyp_CdCHAR(17)

Centr_CdCHAR(6)

Cust_IDINTEGER

Comp_Corr_IDINTEGER

Comp_NmVARCHAR (254)

Comp_Corr_ValVARCHAR (254)

Comp_Strt_DtTmTIMESTAMP

Comp_End_DtTmTIMESTAMP

Comp_DsVARCHAR (254)

1 TAPM_HOST CDW 1 0 host1 9999-01-0112:00:00.0

2 IP_HOST CDW 1 0 host2.dev.tivoli.com

9999-01-0112:00:00.0

3 TAPM_USER CDW 1 1 administrator 9999-01-0112:00:00.0

4 TAPM_USER CDW 1 1 administrator 9999-01-0112:00:00.0

5 TAPM_USER CDW 1 2 goofy 9999-01-0112:00:00.0

6 TAPM_APPL CDW 1 4 IExplorer 9999-01-0112:00:00.0

7 TAPM_APPL CDW 1 5 MSWord 9999-01-0112:00:00.0

8 TAPM_APPL CDW 1 3 Netscape 9999-01-0112:00:00.0

9 TAPM_TX CDW 1 6 download 9999-01-0112:00:00.0

10 TAPM_TX CDW 1 8 download 9999-01-0112:00:00.0

11 TAPM_TX CDW 1 7 print 9999-01-0112:00:00.0

13

To retain the links between these components we need three CompReln entries per TAPM_TX:TX to APPLAPPL to USERUSER to HOST

A TX is identified by: its name the name of its parent APPL the name of its grandparent USER the name of its greatgrandparent HOST

An APPL is identified by: its name the name of its parent USER the name of its grandparent HOST

A USER is identified by: its name the name of its parent HOST

Note that Comp_Corr_Val is not required for this method.The TAPM_HOST component is modified in IP_HOST component if it is a fully qualified hostname.

14

1.1.3 Component Relationship Type (table RelnTyp)

RelnTyp_CdCHAR(6)

RelnTyp_Nm*

VARCHAR(120)PCHILD Parent Child relationship

1.1.4 Component Relationship Rule (table RelnRul)

CompTyp_Source_CdCHAR(17)

CompTyp_Target_CdCHAR(17)

RelnTyp_CdCHAR(6)

RelnRul_Strt_DtTmTIMESTAMP

RelnRul_End_DtTmTIMESTAMP

IP_HOST TAPM_USER PCHILD 9999-01-0112:00:00.0

TAPM_HOST TAPM_USER PCHILD 9999-01-0112:00:00.0

TAPM_USER TAPM_APPL PCHILD 9999-01-0112:00:00.0

TAPM_APPL TAPM_TX PCHILD 9999-01-0112:00:00.0

1.1.5 Component Relationship (table CompReln)

CompReln_IDINTEGER

Comp_Source_IDINTEGER

Comp_Target_IDINTEGER

RelnTyp_CdCHAR(6)

CompReln_Strt_DtTmTIMESTAMP

CompReln_End_DtTmTIMESTAMP

1 1 3 PCHILD 9999-01-0112:00:00.0

2 1 4 PCHILD 9999-01-0112:00:00.0

3 2 5 PCHILD 9999-01-0112:00:00.0

4 4 6 PCHILD 9999-01-0112:00:00.0

5 5 7 PCHILD 9999-01-0112:00:00.0

6 3 8 PCHILD 9999-01-0112:00:00.0

7 6 9 PCHILD 9999-01-0112:00:00.0

8 8 10 PCHILD 9999-01-0112:00:00.0

9 7 11 PCHILD 9999-01-0112:00:00.0

* Source applications must translate values in this column and deliver corresponding Java resource bundles.

15

1.1.6 Attribute Type (table AttrTyp)

AttrTyp_CdCHAR(17)

AttrTyp_Nm*

VARCHAR(120)TX_DETAIL TAPM Transaction detailMETRIC_1 TAPM Application defined metric 1 nameMETRIC_2 TAPM Application defined metric 2 nameMETRIC_3 TAPM Application defined metric 3 nameMETRIC_4 TAPM Application defined metric 4 nameMETRIC_5 TAPM Application defined metric 5 nameMETRIC_6 TAPM Application defined metric 6 nameBUCKET_1_ULB TAPM Bucket 1 Upper Limit BoundaryBUCKET_2_ULB TAPM Bucket 2 Upper Limit BoundaryBUCKET_3_ULB TAPM Bucket 3 Upper Limit BoundaryBUCKET_4_ULB TAPM Bucket 4 Upper Limit BoundaryBUCKET_5_ULB TAPM Bucket 5 Upper Limit BoundaryBUCKET_6_ULB TAPM Bucket 6 Upper Limit BoundaryBUCKET_7_ULB TAPM Bucket 7 Upper Limit BoundaryBUCKET_1_LLB TAPM Bucket 1 Lower Limit BoundaryBUCKET_2_LLB TAPM Bucket 2 Lower Limit BoundaryBUCKET_3_LLB TAPM Bucket 3 Lower Limit BoundaryBUCKET_4_LLB TAPM Bucket 4 Lower Limit BoundaryBUCKET_5_LLB TAPM Bucket 5 Lower Limit BoundaryBUCKET_6_LLB TAPM Bucket 6 Lower Limit BoundaryBUCKET_7_LLB TAPM Bucket 7 Lower Limit Boundary

1.1.7 Attribute Rule (table AttrRul)

CompTyp_CdCHAR(17)

AttrTyp_Cd CHAR(17) AttrRul_Strt_DtTmTIMESTAMP

AttrRul_End_DtTmTIMESTAMP

AttrRul_Dom_IndCHAR

TAPM_HOST LAST_IP_ADDRESS 9999-01-0112:00:00.0

N

TAPM_HOST TME_LABEL 9999-01-0112:00:00.0

N

TAPM_TX TX_DETAIL 9999-01-0112:00:00.0

N

TAPM_TX METRIC_1 9999-01-0112:00:00.0

N

TAPM_TX METRIC_2 9999-01-0112:00:00.0

N

TAPM_TX METRIC_3 9999-01-0112:00:00.0

N

TAPM_TX METRIC_4 9999-01-0112:00:00.0

N

TAPM_TX METRIC_5 9999-01-0112:00:00.0

N

TAPM_TX METRIC_6 9999-01-01 N

* Source applications must translate values in this column and deliver corresponding Java resource bundles

16

12:00:00.0

TAPM_TX BUCKET_1_ULB 9999-01-0112:00:00.0

N


N


N


N


N


N


N

TAPM_TX BUCKET_1_LLB 9999-01-0112:00:00.0

N


N


N


N


N


N


N

1.1.8 Attribute Domain (table AttrDom)THIS IS NOT USED BY TAPM.

AttrDom_IdINTEGER

CompTyp_CdCHAR(17)

AttrTyp_CdCHAR(17)

AttrDom_Strt_DtTmTIMESTAMP

AttrDom_End_DtTmTIMESTAMP

AttrDom_ValVARCHAR(254)

AttrDom_DsVARCHAR(254)

1.1.9 Component Attribute (table CompAttr)

CompAttr_IDINTEGER

Comp_IDINTEGER

AttrTyp_CdCHAR(17)

CompAttr_Strt_DtTmTIMESTAMP

CompAttr_End_DtTmTIMESTAMP

CompAttr_ValVARCHAR(254)

1 1 LAST_IP_ADDRESS

9999-01-0112:00:00.0

146.84.181.70

2 2 LAST_IP_ADDRESS

9999-01-0112:00:00.0

146.84.182.71

3 1 TME_LABEL 9999-01-0112:00:00.0

Host1_ep

4 2 TME_LABEL 9999-01-0112:00:00.0

Host2_ep

5 9 TX_DETAIL 9999-01-0112:00:00.0

HTML pagedownload

17

6 9 BUCKET_1_ULB 9999-01-0112:00:00.0 100

7 9 BUCKET_2_ULB 9999-01-0112:00:00.0 500

8 9 BUCKET_3_ULB 9999-01-0112:00:00.0 1000

9 9 BUCKET_4_ULB 9999-01-0112:00:00.0 2000

10 9 BUCKET_5_ULB 9999-01-0112:00:00.0 5000

11 9 BUCKET_6_ULB 9999-01-0112:00:00.0 10000

12 9 BUCKET_7_ULB 9999-01-0112:00:00.0 2147483647

13 9 BUCKET_1_LLB 9999-01-0112:00:00.0 0

14 9 BUCKET_2_LLB 9999-01-0112:00:00.0 100

15 9 BUCKET_3_LLB 9999-01-0112:00:00.0 500

16 9 BUCKET_4_LLB 9999-01-0112:00:00.0 1000

17 9 BUCKET_5_LLB 9999-01-0112:00:00.0 2000

18 9 BUCKET_6_LLB 9999-01-0112:00:00.0 5000

19 9 BUCKET_7_LLB 9999-01-0112:00:00.0 10000

20 9 METRIC_1 9999-01-0112:00:00.0

KBytes_transferred

21 9 METRIC_2 9999-01-0112:00:00.0

Number_of_objects

22 9 METRIC_3 9999-01-0112:00:00.0

HTTP_Server_requests

23 9 METRIC_4 9999-01-0112:00:00.0

HTTP_Client_requests

24 9 METRIC_5 9999-01-0112:00:00.0

Failed_requests

25 9 METRIC_6 9999-01-0112:00:00.0

Network_bandwith

� � � � �

18

1.2 Component Measurement

1.2.1 Measurement Group Type (table MGrpTyp)

MGrpTyp_CdCHAR(6)

MGrpTyp_Nm*

VARCHAR(120)PMIN TAPM Minimum data collectionPMED TAPM Medium data collectionPMAX TAPM Maximum data collection

TAPM can collect data according to 3 types of configurations: Min, Med and Max. If Med collection configurationis set on an application, the Min is included. If Max collection configuration is set on an application, the Med isincluded.

1.2.2 Measurement Group (table MGrp)

MGrp_CdCHAR(6)

MGrpTyp_CdCHAR(6)

MGrp_Parent_CdCHAR(6)

MsmtGrp_Nm*

VARCHAR(120)AVG_E PMIN NULL Average value existsMAX_E PMIN NULL Maximum value existsMIN_E PMIN NULL Minimum value existsTOT_E PMED NULL Total value existsTOT_E PMAX NULL Total value exists

1.2.3 Measurement Group Member (table MGrpMbr)

AVG_E PMIN 1MAX_E PMIN 1MIN_E PMIN 1TOT_E PMED 2TOT_E PMED 3TOT_E PMED 4TOT_E PMED 5TOT_E PMED 6TOT_E PMED 7TOT_E PMED 8TOT_E PMAX 9TOT_E PMAX 10TOT_E PMAX 11TOT_E PMAX 12TOT_E PMAX 13TOT_E PMAX 14


MGrp_CdCHAR(6)

MGrpTyp_CdCHAR(6)

MsmtTyp_IDINTEGER

19

1.2.4 Measurement Unit Category (table MUnitCat)

MUnitCat_CdCHAR(6)

MUnitCat_Nm*

VARCHAR(120)TM Time durationQTY Quantity

1.2.5 Measurement Unit (table MUnit)

MUnit_CdCHAR(6)

MUnitCat_CdCHAR(6)

MUnit_Nm*

VARCHAR(120)Msec TM millisecondsQTY QTY Quantity

1.2.6 Time Summary (table TmSum)

TmSum_CdCHAR

TmSum_Nm*

VARCHAR(120)H Hourly

1.2.7 Measurement Source (table MSrc)

MSrc_CdCHAR(6)

MSrc_Parent_CdCHAR(6)

MSrc_Nm*

VARCHAR(120)Tivoli NULL Tivoli ApplicationsAPF Tivoli Tivoli Application Performance Management

1.2.8 Measurement Type (table MsmtTyp)

MsmtTyp_IDINTEGER

MUnit_CdCHAR(6)

MSrc_CdCHAR(6)

MsmtTyp_Nm*VARCHAR(120)

MsmtTyp_Ds*VARCHAR(254)

1 TM APF ResponseTime Transaction Response Time2 QTY APF Bucket_1 Transactions Succeeded in

Bucket 13 QTY APF Bucket_2 Transactions Succeeded in






20


Bucket 79 QTY APF Metric_1 Application defined metric 110 QTY APF Metric_2 Application defined metric 211 QTY APF Metric_3 Application defined metric 312 QTY APF Metric_4 Application defined metric 413 QTY APF Metric_5 Application defined metric 514 QTY APF Metric_6 Application defined metric 6

1.2.9 Component Measurement Rule (table MsmtRul)

CompTyp_CdCHAR(17)

MsmtTyp_IDINTEGER

TAPM_TX 1TAPM_TX 2TAPM_TX 3TAPM_TX 4TAPM_TX 5TAPM_TX 6TAPM_TX 7TAPM_TX 8TAPM_TX 9TAPM_TX 10TAPM_TX 11TAPM_TX 12TAPM_TX 13TAPM_TX 14

21

1.2.10 Measurement (table Msmt)

Msmt_IDBIGINT

Comp_IDINTEGER

MsmtTyp_IDINTEGER

TmSum_CdCHAR

Msmt_Strt_DtDATE

Msmt_Strt_TmTIME

Msmt_Min_ValFLOAT

Msmt_Max_ValFLOAT

Msmt_Avg_ValFLOAT

Msmt_Tot_ValFLOAT

Msmt_Sampl_CntINTEGER

Msmt_Err_CntINTEGER

1 9 1 H 2001-11-08 00:00 2 4 3 2 1

2 9 2 H 2001-11-08 00:00 2

3 9 3 H 2001-11-08 00:00 0

4 9 4 H 2001-11-08 00:00 0

5 9 5 H 2001-11-08 00:00 0

6 9 6 H 2001-11-08 00:00 0

7 9 7 H 2001-11-08 00:00 0

8 9 8 H 2001-11-08 00:00 0

9 9 9 H 2001-11-08 00:00 10.2

10 9 10 H 2001-11-08 00:00 42

11 9 11 H 2001-11-08 00:00 100

12 9 12 H 2001-11-08 00:00 79

13 9 13 H 2001-11-08 00:00 2

14 9 14 H 2001-11-08

00:00 1024

15 10 1 H 2001-11-08 00:00 5 30 20 10 1

16 10 2 H 2001-11-08 00:00 2

17 10 3 H 2001-11-08 00:00 5

18 10 4 H 2001-11-08 00:00 2

19 10 5 H 2001-11-08 00:00 1

20 10 6 H 2001-11-08 00:00 0

21 10 7 H 2001-11-08 00:00 0

22 10 8 H 2001-11-08 00:00 0

22

23 10 9 H 2001-11-08 00:00 10.2

24 10 10 H 2001-11-08 00:00 42

25 10 11 H 2001-11-08 00:00 100

26 10 12 H 2001-11-08 00:00 79

27 10 13 H 2001-11-08 00:00 2

28 10 14 H 2001-11-08

00:00 1024

29 11 1 H 2001-11-08 01:00 1 5 3 6

... ... ... � � � � � � � �

The MsmtTypeID 1 is mandatory (TAPM MIN configuration). The MsmtTypeID from 2 to 8 are present only whena TAPM Med collection configuration is set and data is produced. The MsmtTypeID from 9 to 14 are present onlywhen a TAPM Max collection configuration is set and data is produced.

1.2.11 Extract Control (table Extract_Control)

ExtCtl_SourceVARCHAR(120)

ExtCtl_TargetVARCHAR(120)

ExtCtl_From_RawSeqCHAR

ExtCtl_To_RawSeqCHAR

ExtCtl_From_IntSeqBIGINT

ExtCtl_To_IntSeqBIGINT

ExtCtl_From_DtTmTIMESTAMP

ExtCtl_To_DtTmTIMESTAMP

ID_INFO_INIT

APF.STAGE_ID_INFO_COPY

3 3 9999-01-0100:00:00.0

9999-01-0100:00:00.0

DATA32_INIT

APF.STAGE_METRICDATA32_COPY

20 20 9999-01-0100:00:00.0

9999-01-0100:00:00.0

DATA64_INIT


20 20 9999-01-0100:00:00.0

9999-01-0100:00:00.0

DATABUCKETS_INIT

APF.STAGE_METRICDATABUCKETS_COPY

21 21 9999-01-0100:00:00.0

9999-01-0100:00:00.0

HOSTS_INIT

APF.STAGE_HOST_ATTR_COPY

5 5 9999-01-0100:00:00.0

9999-01-0100:00:00.0

TRANSACTIONS_INIT

APF.STAGE_TX_ATTR_COPY

2 2 9999-01-0100:00:00.0

9999-01-0100:00:00.0

23

1.2.12 Extract Log (table Extract_Log)

ExtLog_SourceVARCHAR(120)

ExtLog_TargetVARCHAR(120)

ExtLog_Done_DtTmTIMESTAMP

ExtLog_From_RawSeqCHAR

ExtLog_To_RawSeqCHAR

ExtLog_From_IntSeqBIGINT

ExtLog_To_IntSeqBIGINT

ExtLog_From_DtTmTIMESTAMP

ExtLog_To_DtTmTIMESTAMP

ID_INFO_INIT

APF.STAGE_ID_INFO_COPY

2001-12-06 16:00

0 3 1970-01-0100:00:00.0

9999-01-0100:00:00.0

DATA32_INIT


2001-12-0616:00

0 20 1970-01-0100:00:00.0

9999-01-0100:00:00.0

DATA64_INIT


2001-12-0616:00

0 20 1970-01-0100:00:00.0

9999-01-0100:00:00.0

HOSTS_INIT

APF.STAGE_HOST_ATTR_COPY

2001-12-0616:00

0 5 1970-01-0100:00:00.0

9999-01-0100:00:00.0

TRANSACTIONS_INIT

APF.STAGE_TX_ATTR_COPY

2001-12-0616:00

0 2 1970-01-0100:00:00.0

9999-01-0100:00:00.0

DATABUCKETS_INIT

APF.STAGE_METRICDATABUCKETS_COPY

2001-12-0616:00

0 21 1970-01-0100:00:00.0

9999-01-0100:00:00.0

24

1.2.13 Helper TablesNo Helper Tables are provided.

1.2.14 Exception TablesNo Exception Tables are provided.

tivoli application performance management warehouse...

Documents