ibm tivoli monitoring for transaction performance: web...

IBM Tivoli Monitoring for Transaction Performance:

Web Transaction Performance Warehouse Enablement Pack

Implementation Guide

Version 1.1.0

SC09-7793-00

IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance Warehouse Pack Implementation Guide

2

Edition notice First Edition

Copyright Notice

© Copyright IBM Corporation 2002. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Enterprise, Tivoli Enterprise Console, Tivoli Ready, and TME are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation and/or IBM Corporation in the United States or other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.

PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. For a complete list of Intel trademarks, see http://www.intel.com/sites/corporate/tradmarx.htm. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see http://www.setco.org/aboutmark.html.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.

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

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.


3

Contents 1 About this document .......................................................................................................5

1.1 Related Documentation ..........................................................................................................5 1.1.1 IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance........................................ 5 1.1.2 Tivoli Enterprise Data Warehouse .................................................................................................................... 5 1.1.3 DB2................................................................................................................................................................... 6

2 Overview ...........................................................................................................................7 2.1 Overview of Tivoli Enterprise Data Warehouse ....................................................................7 2.2 Overview of Tivoli Monitoring for Transaction Performance: Web Transaction Performance .....................................................................................................................................8

Data Flow.................................................................................................................................10 3 Installing and Configuring.............................................................................................11

3.1 Prerequisites .........................................................................................................................11 3.2 Supported hardware and software.......................................................................................11 3.3 Limitations.............................................................................................................................11 3.4 Database sizing considerations...........................................................................................11 3.5 Data sources and targets......................................................................................................12 3.6 Pre-installation steps ............................................................................................................13 3.7 Installation procedure...........................................................................................................13 3.8 Post-installation steps ..........................................................................................................13

4 Maintaining .....................................................................................................................14 4.1 Backing up and restoring .....................................................................................................14 4.2 Pruning ..................................................................................................................................14 4.3 Other maintenance topics ....................................................................................................14

5 ETL processes................................................................................................................15 5.1 BWM_c05_Initialize_Process ...............................................................................................15 5.2 BWM_c10_Load_Warehouse_Process ................................................................................15 5.3 ETL process step descriptions ............................................................................................16

6 Generic schema implementation ..................................................................................19 6.1 Component configuration.....................................................................................................19

6.1.1 Component type (table CompTyp) .................................................................................................................. 19 6.1.2 Component (table Comp)................................................................................................................................ 19 6.1.3 Component relationship type (table RelnTyp)................................................................................................. 21 6.1.4 Component relationship rule (table RelnRul) .................................................................................................. 21 6.1.5 Component relationship (table CompReln) ..................................................................................................... 21 6.1.6 Attribute type (table AttrTyp) ........................................................................................................................... 22 6.1.7 Attribute rule (table AttrRul) ............................................................................................................................ 22 6.1.8 Attribute domain (table AttrDom)..................................................................................................................... 23 6.1.9 Component attribute (table CompAttr) ............................................................................................................ 23

6.2 Component measurement ....................................................................................................24 6.2.1 Measurement group type (table MGrpTyp) ..................................................................................................... 24


4

6.2.2 Measurement group (table MGrp)................................................................................................................... 25 6.2.3 Measurement group member (table MGrpMbr) .............................................................................................. 25 6.2.4 Measurement unit category (table MUnitCat) ................................................................................................. 25 6.2.5 Measurement unit (table MUnit)...................................................................................................................... 25 6.2.6 Time summary (table TmSum) ....................................................................................................................... 25 6.2.7 Measurement source (table MSrc).................................................................................................................. 26 6.2.8 Measurement type (table MsmtTyp) ............................................................................................................... 26 6.2.9 Component measurement rule (table MsmtRul) ............................................................................................. 26 6.2.10 Measurement (table Msmt) ............................................................................................................................. 26

6.3 Helper tables..........................................................................................................................27 6.4 Exception tables....................................................................................................................27 6.5 Incremental extraction ..........................................................................................................27

7 Data mart schema information......................................................................................28


5

1 About this document This document describes the warehouse enablement pack for Tivoli Monitoring for Transaction Performance: Web Transaction Performance. It covers the following topics:

• Installing and configuring the warehouse pack

• The data flow and data structures used by the warehouse pack

With this warehouse pack, you can enable a set of extract, transform and load (ETL) utilities to extract and move data from a Web Transaction Performance database to a central data warehouse database. Database administrators and programmers require the type of information provided in this document to install the ETL tools and understand what data is moved into the central data warehouse during what is referred to as the central data warehouse ETL.

1.1 Related Documentation You can access many Tivoli® publications online using the Tivoli Information Center, which is available on the Tivoli Customer Support Web site:

http://www.tivoli.com/support/documents/

1.1.1 IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance

The following IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance documents are available on the IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance documentation CD:

• IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance Installation Guide, GC23-4801

Provides prerequisite information and instructions for installing the Web Transaction Performance component. This guide also contains information that you might find useful after installing the product, such as uninstallation instructions and reference information about digital certificates.

• IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance User’s Guide, GC23-4802

Provides detailed procedures for using each of the Web Transaction Performance applications. The guide also describes the browser-based graphical user interface (GUI), the help system, and how to use Tivoli Decision Support to produce graphical reports from Web Transaction Performance data.

• IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance Release Notes, GI11-0939

Describes the features of the Web Transaction Performance component.

• IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance Limitations and Workarounds Supplement, SC23-4800

Provides the latest information about known product limitations and workarounds for the Web Transaction Performance component. To ensure that the information is the latest available, this document is provided only on the Web, where it is updated as needed. You can access the Limitations and Workarounds Supplement through the Tivoli Monitoring for Transaction Performance link on the Tivoli Information Center Web site:

http://www.tivoli .com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

1.1.2 Tivoli Enterprise Data Warehouse

The following Tivoli Enterprise™ Data Warehouse documents are available on the Tivoli Enterprise Data Warehouse Documentation CD:

• Tivoli Enterprise Data Warehouse Release Notes, GI11-0857

Provides late-breaking information about Tivoli Enterprise Data Warehouse and lists hardware requirements and software prerequisites.

• Installing and Configuring Tivoli Enterprise Data Warehouse, GC32-0744

http://www.tivoli.com/support/documents/http://www.tivoli .com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html


6

Describes how Tivoli Enterprise Data Warehouse fits into your enterprise, explains how to plan for its deployment, and gives installation and configuration instructions. It provides an introduction to the built-in program for creating and running reports, and contains maintenance procedures and troubleshooting information.

• Enabling an Application for Tivoli Enterprise Data Warehouse, GC32-0745

Provides information about connecting an application to Tivoli Enterprise Data Warehouse. This book is for application programmers who use Tivoli Enterprise Data Warehouse to store and report on their application’s data, data warehousing experts who import Tivoli Enterprise Data Warehouse data into business intelligence applications, and customers who use their local data in the warehouse.

1.1.3 DB2

The DB2 library contains important information about the database and data warehousing technology provided by IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager. Refer to the DB2 library for help in installing, configuring, administering, and troubleshooting DB2. The DB2 library is available on the Tivoli Customer Support Web site. After you install DB2, its library is also available on your system.

The following DB2 documents are particularly relevant for people working with Tivoli Enterprise Data Warehouse:

• IBM DB2 Universal Database for Windows Quick Beginnings, GC09-2971

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on Microsoft Windows.

• IBM DB2 Universal Database for UNIX Quick Beginnings, GC09-2970

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on UNIX.

• IBM DB2 Universal Database Administration Guide: Implementation, SC09-2944

Covers the details of implementing your database design. Topics include creating and altering a database, database security, database recovery, and administration using the Control Center, a DB2 graphical user interface.

• IBM DB2 Universal Database Data Warehouse Center Administration Guide, SC26-9993

Provides information on how to build and maintain a data warehouse using the Data Warehouse Center.

• IBM DB2 Warehouse Manager Installation Guide, GC26-9998

Provides the information to install the following Warehouse Manager components: Information Catalog Manager, warehouse agents, and warehouse transformers.

• IBM DB2 Universal Database and DB2 Connect Installation and Configuration Supplement, GC09-2957

Provides advanced installation considerations and guides you through the planning, installation, migration (if necessary), and set up a platform-specific DB2 client. Once the DB2 client is installed, you then configure communications for both the client and server, using the DB2 GUI tools or the Command Line Processor. This supplement also contains information on binding, setting up communications on the server, the DB2 GUI tools, DRDA™ AS, distributed installation, the configuration of distributed requests, and accessing heterogeneous data sources.

• IBM DB2 Universal Database Message Reference Volume 1, GC09-2978 and IBM DB2 Universal Database Message Reference Volume 2, GC09-2979

Lists the messages and codes issued by DB2, the Information Catalog Manager, and the Data Warehouse Center, and describes the actions you should take.


7

2 Overview The following sections provide an overview of Tivoli Enterprise Data Warehouse and the Tivoli Monitoring for Transaction Performance: Web Transaction Performance warehouse pack.

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

• Extract, transform, and load (ETL) processes through the IBM DB2 Data Warehouse Center tool

• Schema generation of the central data warehouse

• Historical reporting

As shown in Figure 1, Tivoli Enterprise Data Warehouse consists of a centralized data store where historical data 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, more data is added to the database; however, no new tables or columns are added in the schema.

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

The central data warehouse ETL reads the data from the operational data stores of the application that collects it, 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 one or more star schemas, which can be included in data marts to answer specific business questions.

A program that provides these ETLs is called a warehouse enablement pack, or warehouse pack.


8

2.2 Overview of Tivoli Monitoring for Transaction Performance: Web Transaction Performance

The warehouse pack for IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance extracts, processes and loads Web Transaction Performance data into the Tivoli Enterprise Data Warehouse.

The Web Transaction Performance component of IBM Tivoli Monitoring for Transaction Performance is a centrally managed suite of applications that monitor the availability and performance of Web-based services. Web Transaction Performance measures how users experience your Web sites by monitoring response times and availability under different conditions and by traversing the sites to ensure properly functioning links and accurate content. Collected data can be passed to enterprise management applications, which provide additional capability for analysis and corrective action.


9

Note: The data mart ETL process is not provided. Tivoli Decision Support for Enterprise Transaction Performance provides application performance specific reporting.

The Web Transaction Performance warehouse enablement pack gathers metrics for the Quality of Service (QoS) and Synthetic Transaction Investigator (STI Player) applications of the Tivoli Monitoring for Transaction Performance: Web Transaction Performance application.

Quality of Service (QoS)

• Granularity of Data

The Tivoli Enterprise Data Warehouse gathers QoS data on a per task, per endpoint, per URL, and per hour basis. Metrics captured on a per URL basis are granular to the Web site path name.

• Metrics (measured in Milliseconds)

o Round Trip Time – Minimum, Maximum, Average

o Service Time – Minimum, Maximum, Average

o Page Render Time – Minimum, Maximum, Average

Synthetic Transaction Investigator (STI)

• Granularity of data

The Tivoli Enterprise Data Warehouse gathers STI data on a per job, per endpoint, and per hour basis. Therefore, a component in a measurement table for STI refers to a particular job on a particular endpoint.

• Metrics

o Round Trip Time – Minimum, Maximum, Average (measured in Milliseconds)

o Service Time – Minimum, Maximum, Average (measured in Milliseconds)

o Number Threshold Exceeded – Total (Quantity)

The following table shows the flow of data between Tivoli Monitoring for Transaction Performance: Web Transaction Performance and Tivoli Enterprise Data Warehouse.


10

Data Flow

Tivoli Monitoring for Transaction Performance: Web Transaction Performance to Tivoli Enterprise Data Warehouse Web Services Courier processes and persists data to the Web Services Courier data warehouse

• Enabled Web Services Courier endpoints process and persist Tivoli Monitoring for Transaction Performance: Web Transaction Performance data into the Web Service Courier database

----Transition to the Tivoli Enterprise Data Warehouse----

The Web Transaction Performance warehouse pack populates static data in the Tivoli Enterprise Data Warehouse

• The Web Transaction Performance warehouse pack populates the central data warehouse with component and attribute information. In particular, it populates the task and endpoint information as described in section 5.

Create staging tables

• The Web Transaction Performance warehouse pack imports all the raw application records from the source database into the staging tables for the ETL.

Insert data into tables in rolled up, hourly basis from top of the hour

Perform Min/Max/Avg/Total Calculations on data

Insert rolled/calculated data into the Tivoli Enterprise Data Warehouse

• Rolled up calculations are inserted into the Tivoli Enterprise Data Warehouse twg.msmt table. Each entry represents a particular metric


11

3 Installing and Configuring 3.1 Prerequisites

• IBM DB2 Universal Database Enterprise Edition Version 7.2

• IBM DB2 Universal Database Enterprise Edition Version 7.2 FixPack 6

• Tivoli Enterprise Data Warehouse required e-fixes to IBM DB2 UDE v7 FixPak 6 (1.1-TDW-0002)

• Tivoli Enterprise Data Warehouse Version 1.1

• Tivoli Enterprise Data Warehouse 1.1 Fix Pack 1 (1.1-TDW-FP01a)

• Tivoli Enterprise Data Warehouse 1.1 E-fix 2 (1.1-TDW-0005E)

Note: Tivoli Enterprise Data Warehouse 1.1 Fix Pack 2 (1.1-TDW-FP02) supersedes e-fix 1.1-TDW-0005E. When 1.1-TDW-FP02 becomes available, install 1.1-TDW-FP02 instead of 1.1-TDW-0005E. You can obtain the Tivoli Enterprise Data Warehouse e-fixes and fix pack from the Tivoli Enterprise Data Warehouse Web site:

http://www.ibm.com/software/sysmgmt/products/support/TivoliEnterpriseDataWarehouse.html

Click the Downloads link in the Self-help section. Refer to the Tivoli Enterprise Data Warehouse required e-fixes to IBM DB2 UDE v7 FixPak 6 documentation (1.1-TDW-0002.README) for instructions on obtaining IBM DB2 Universal Database Enterprise Edition Version 7.2 Fixpak 6.

3.2 Supported hardware and software Tivoli Monitoring for Transaction Performance: Web Transaction Performance warehouse pack, Version 1.1.0, supports IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance, Version 5.1.0. It supports all versions of DB2 7.x and Oracle 8i and 9 database products as documented in the Tivoli Monitoring for Transaction Performance: Web Transaction Performance Installation Guide.

3.3 Limitations The Tivoli Monitoring for Transaction Performance: Web Transaction Performance (Version 5.1.0) warehouse pack is not compatible with the Tivoli Web Services Monitoring (Version 1.7.0) warehouse pack. In order for the Web Transaction Performance warehouse pack to function correctly, the Tivoli Web Services Monitoring warehouse pack must be uninstalled. After the installation and execution of the Web Transaction Performance warehouse pack, Tivoli Web Services Monitoring data in the warehouse becomes invalid.

3.4 Database sizing considerations You will need to consider the volume of data you expect to collect for the execution of the Web Transaction Performance ETL and define an appropriate amount of space for the central data warehouse database.

The amount of data that will be moved from the Web Transaction Performance source database to the Tivoli central data warehouse database can be computed using the following formulas. The tables that are greatly impacted from the Web Transaction Performance amount of data are: the Component, the Component Attribute, the Measurement, and the Web Transaction Performance staging tables.

The number of rows inserted into the Tivoli Enterprise Data Warehouse central data warehouse database is different for the QoS and STI components of Web Transaction Performance. The number of rows inserted into the central data warehouse equals the number of rows inserted for STI plus the number of rows inserted for QoS. Therefore, each case is considered separately. The following formulas are used to compute the number of rows stored in tables of the central data warehouse:

http://www.ibm.com/software/sysmgmt/products/support/TivoliEnterpriseDataWarehouse.html


12

Table Formula

Synthetic Transaction Investigator

Component Components = Number of Web Transaction Performance endpoints + Number of jobs per endpoint

Component Attribute Component Attribute = Number of Web Transaction Performance endpoints * 1 + Number of jobs per endpoint * 3

Measurement Ψ Number of rows inserted for STI = Components + Component Attribute + Measurements per day

Measurement (maximum number of measurements per day) λ Measurements Per Day = (Number of jobs per endpoint) * 24

Quality of Service

Component φ Components = Number of Web Transaction Performance endpoints + Number of jobs per endpoint + Number of URLs visited per job per endpoint

Component Attribute Component Attribute = Number of Web Transaction Performance endpoints * 1 + Number of jobs per endpoint * 5

Measurement Ψ Number of rows inserted for QoS = Components + Component Attribute + Measurements per day

Measurement (maximum number of measurements per day) λ Measurements Per Day = (Number of unique Web site paths per job per endpoint per Web site) * 24

Ψ Estimate additional space for the central data warehouse database because of the staging tables utilized by the Web Transaction Performance ETL φ URLs in the Tivoli Enterprise Data Warehouse are defined in three parts: a Web site, a Web site path, and a Web site query string. Therefore, you can insert as many as 3 components into the central data warehouse for one URL. To compute the number of URLs per job per endpoint, use the following formula:

Number of URLs visited per job per endpoint = Number of unique Web sites per job per endpoint + Number of unique Web site paths per job per endpoint per Web site + Number unique Web site queries per job per endpoint per Web site per Web site path λ This assumes that all the jobs imported into the central data warehouse are active. Active jobs continue to collect metrics at a frequency greater than once an hour. If jobs imported into the central data warehouse are not active, the number of measurements per day is less.

3.5 Data sources and targets

The Web Transaction Performance warehouse pack source database is the Tivoli Monitoring for Transaction Performance: Web Transaction Performance’s Web Services Courier data warehouse. Ensure that you can connect to the Web Services Courier data warehouse before defining it as a source database.

• For DB2, catalog the database using ODBC. Use the “IBM DB2 ODBC DRIVER” Version 7.01.00.50 ODBC driver from IBM.

• For Oracle, supply the system data source name (DSN) where the database is registered in ODBC on the agent site. Use the ODBC applet, accessible from the Control Panel, to add the data source as a system data source. Use the “DataWHSE 3.60 32-bit Oracle8” Version 3.60 ODBC driver from MERANT. The name of the data source must be BWM_TWSM.


13

3.6 Pre-installation steps The Web Transaction Performance ETL is not a replacement for the Tivoli Web Services Manager ETL shipped with Tivoli Service Level Advisor, Version 1.1. If you already have installed the Tivoli Web Services Manager ETL that shipped with the Tivoli Service Level Advisor, you need to uninstall the Tivoli Web Services Manager warehouse pack before installing the Web Transaction Performance warehouse pack. Note that any data collected using the Tivoli Web Services Manager ETL will be invalid after the uninstallation of the Tivoli Web Services Manager ETL as described in section 3.3.

The uninstallation procedure for the IBM Tivoli Monitoring for Transaction Performance ETL warehouse enablement pack is described in Installing and Configuring Tivoli Enterprise Data Warehouse.

3.7 Installation procedure Perform the following steps to install the IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance warehouse pack:

1. Make sure that IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance is installed and the Web Transaction Performance data source is available.

2. Make sure that all prerequisite Tivoli Monitoring for Transaction Performance: Web Transaction Performance product patches are applied.

3. Make sure that Tivoli Enterprise Data Warehouse is installed, including prerequisites specified in section 3.1. For instructions about installing Tivoli Enterprise Data Warehouse, refer to Installing and Configuring Tivoli Enterprise Data Warehouse. Perform any pre-installation steps as described in Pre-installation steps.

4. Install the warehouse pack as described in the instructions in Installing and Configuring Tivoli Enterprise Data Warehouse. The installation media for this warehouse pack is located on the IBM Tivoli Monitoring for Transaction Performance, Version 5.1.0: Web Transaction Performance Component Software CD in the /TEDW/tedw_apps_etl/ctq directory.

5. Perform the post-installation steps described in Section 3.8.

3.8 Post-installation steps Before running the ETL process, you must ensure that the warehouse sources and warehouse targets specific to the Web Transaction Performance application are correctly defined (user name, password, host name, system data source).

Perform the following steps:

1. Expand the Warehouse Sources folder from the Data Warehouse Center window.

2. Expand BWM_TWSM_Source folder.

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

4. If the Schema property is empty and the name of the tables includes the schema name, right-click each table and select Properties to open the Properties window.

5. On the Source Table page, modify the Table schema and Table name properties with the values of the Web Transaction Performance database source.


14

4 Maintaining 4.1 Backing up and restoring There are no special considerations for backing up and restoring this warehouse pack.

4.2 Pruning

Old data is removed from the Msmt table using a combination of triggers and warehouse processes. The CDW_C05_PurgeMsmt_Process is a process in the CDW_TivoliEnterpriseDataWarehouse_v1.1.0_Subject_Area subject area. This process has the following characteristics:

• Allows you to schedule when you want to run the process: weekly, monthly, or daily.

• The Prune_Msmt_Control table specifies the data that is pruned.

• The default value set by for this warehouse pack is 31 days.

• Allows you to modify the value by running the following SQL statement, where X 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 = 'BWM'

4.3 Other maintenance topics

When the Web Transaction Performance warehouse enablement pack is uninstalled, Web Transaction Performance data in the central data warehouse is not automatically removed. The Web Transaction Performance data in the central data warehouse is not tied to a specific application, but is a historical record of activity and conditions in your enterprise. Applications other than the application used to place the Web Transaction Performance data in the warehouse can read the data. Therefore, Tivoli Enterprise Data Warehouse does not provide an automated way to delete data from the central data warehouse, aside from the data pruning mechanisms.

If you do not delete the data, a subsequent reinstallation of the Web Transaction Performance warehouse enablement pack can lead to a potential duplication of data in the central data warehouse. If you plan to reinstall, perform the following steps after uninstalling the warehouse pack:

1. Set PMSMTC_AGE_IN_DAYS = -1 in the PRUNE_MSMT_CONTROL table as described in “Pruning.”

The PMSMTC_AGE_IN_DAYS value is set to -1 because the purge process does not delete the data for the current day.

2. Run the Tivoli Enterprise Data Warehouse PurgeMsmt process, CDW_C05_PurgeMsmt_Process

3. Reinstall the Web Transaction Performance warehouse pack.

4. Run the Web Transaction Performance warehouse pack process.


15

5 ETL processes This warehouse pack has the following processes.

5.1 BWM_c05_Initialize_Process

You should only run this process the first time that data is collected by the ETL. Do not schedule this process to run daily. This process uses the data from the Prune_Msmt_Control table to determine how much data should be retrieved when running. See 5.3 for details on the ETL process steps.

This process consists of the following steps:

• BWM_c05_s010_comp

• BWM_c05_s020_init_extract_sti

• BWM_c05_s030_transform_sti

• BWM_c05_s040_sti_rtt

• BWM_c05_s050_sti_st

• BWM_c05_s060_sti_th

• BWM_c05_s070_init_extract_qos

• BWM_c05_s080_extract_url

• BWM_c05_s090_transform_qos

• BWM_c05_s100_qos_bst

• BWM_c05_s110_qos_prt

• BWM_c05_s120_qos_rtt

5.2 BWM_c10_Load_Warehouse_Process

Schedule this process to run each day so that all new data in the Web Services Courier data warehouse is moved to the TWH_CDW database. It is set up to locate only the incremental changes since the last time the ETL has run. See 5.3 for details on the ETL process steps.

This process consists of the following steps:

• BWM_c10_s010_comp

• BWM_c10_s020_init_extract_sti

• BWM_c10_s030_transform_sti

• BWM_c10_s040_sti_rtt

• BWM_c10_s050_sti_st

• BWM_c10_s060_sti_th

• BWM_c10_s070_init_extract_qos

• BWM_c10_s080_extract_url


16

• BWM_c10_s090_transform_qos

• BWM_c10_s100_qos_bst

• BWM_c10_s110_qos_prt

• BWM_c10_s120_qos_rtt

5.3 ETL process step descriptions The following table shows the description, source, and target for the ETL process steps for this warehouse pack.

Description Source Target

BWM_c05_s010_comp and BWM_c10_s010_comp

Inserts endpoint and task information into the central data warehouse.

bwm_twsm.tdendpoint

bwm_twsm.tdtask

bwm_twsm.taskmap

bwm_twsm.tdstmtaskconstraints

bwm_twsm.tdeaataskparameters

bwm_twsm.tdeaataskconstraints

twh_cdw.comp for compTyp of:

• IP_HOST

• BWM_EP

• BWM_QOS

• BWM_STI

twh_cdw.compReln

• RUNSON relationship between BWM_EP and IP_HOST

• PCHILD relationship between BWM_EP and BWM_QOS and between BWM_EP and BWM_STI

twh_cdw.compAttr

• IP_DOMAIN for BWM_EP

• BWM_TASKID for BWM_QOS

• BWM_TASKID for BWM_STI

• BWM_VIRTUAL_HOST for BWM_QOS

• BWM_ST_CONST for BWM_QOS

• BWM_RTT_CONST for BWM_QOS

• BWM_PRT_CONST for BWM_QOS

• BWM_ST_CONST for BWM_STI

• BWM_RTT_CONST for BWM_STI

update twh_cdw.extract_control for:

• BWM_TDENDPOINT


17


• BWM_TASKMAP

• BWM_TDTASK

• BWM_TDEAATASKPARAMETERS

• BWM_TDEAATASKCONSTRAINTS

• BWM_TDSTMTASKCONSTRAINTS

BWM_c05_s020_init_extract_sti and BWM_c10_s020_extract_sti

Stages the sti data into a temporary table bwm.stage_sti

bwm_twsm.tfstmoverall bwm.stage_sti

update twh_cdw.extract_control for:

BWM_TFSTMOVERALL

BWM_c05_s030_transform_sti and BWM_c10_s030_transform_sti

Processes, rolls-up the staged data in bwm.stage_sti on an hourly basis according to the job, and endpoint

bwm.stage_sti

bwm.stage_sti_good

bwm.stage_sti_bad

BWM_c05_s040_sti_rtt and BWM_c10_s040_sti_rtt

Inserts Round Trip Time

bwm.stage_sti_good

bwm.stage_sti_bad

twg.msmt

BWM_c05_s050_sti_st and BWM_c10_s050_sti_st

Inserts Service Time

bwm.stage_sti_good

bwm.stage_sti_bad

twg.msmt

BWM_c05_s060_sti_th and BWM_c10_s060_sti_th

Inserts Threshold Exceeded

bwm.stage_sti_good

bwm.stage_sti_bad

twg.msmt

BWM_c05_s070_init_extract_qos and BWM_c10_s070_extract_qos

Extracts QoS data form BWM_TWSM

bwm_twsm.tfqosdetail bwm.stage_qos

update twg.extract_control for

BWM_TFQOSDETAIL

BWM_c05_s080_extract_url and BWM_c10_s080_extract_url


18


Extracts urls necessary for QoS extract

bwm_twsm.tdurl

bwm.stage_qos

twh_cdw.comp for compTyp of:

• WEBSITE

• WEBSITE_PATH

• WEBSITE_QUERY

twh_cdw.compReln

• PCHILD relationship between WEBSITE and WEBSITE_PATH

• PCHILD relationship between WEBSITE_PATH and WEBSITE_QUERY

• MONITR relationship between BWM_QOS and WEBSITE

twh_cdw.compAttr

• URL_PROTOCOL for WEBSITE

bwm.comp_long for WEBSITE_PATH and WEBSITE_QUERY > 244 characters

bwm.stage_qos_final

BWM_c05_s090_transform_qos and BWM_c10_s090_transform_qos

Processes, rolls-up qos data on a per hour basis on a website and web_path

bwm.stage_qos_final bwm.stage_roll_rtt

bwm.stage_roll_st

bwm.stage_roll_prt

BWM_c05_s100_qos_bst and BWM_c10_s100_qos_bst

Inserts Service Time into msmt for QoS

bwm.stage_roll_st

twg.comp

BWM_c05_s110_qos_prt and BWM_c10_s110_qos_prt

Inserts Page Render Time into msmt for QoS

bwm.stage_roll_prt twg.comp

BWM_c05_s120_qos_rtt and BWM_c10_s120_qos_rtt

Inserts Round Trip Time into msmt for QoS

bwm.stage_roll_rtt

twg.comp


19

6 Generic schema implementation Before reading this section, read about the generic schema for the Tivoli Enterprise Data Warehouse central data warehouse, which is described in Enabling an Application for Tivoli Enterprise Data Warehouse. That document defines the content of each table and explains the relationships between the tables in this document.

Shaded columns in the following tables are translated by the application. Translated columns are also identified with an asterisk (*) in the column heading.

6.1 Component configuration 6.1.1 Component type (table CompTyp)

CompTyp_Cd CHAR(17)

CompTyp_Parent_CdCHAR(17)

CompTyp_Nm * VARCHAR(120)

CompTyp_Strt_DtTm TIMESTAMP

CompTyp_End_DtTmTIMESTAMP

IP_HOST NULL IP Host 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_EP NULL Tivoli Web Transaction Performance Endpoint

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_QOS NULL Tivoli Web Transaction Performance QoS Job

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_STI NULL Tivoli Web Transaction Performance STI Job

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

WEBSITE NULL Website 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

WEBSITE_PATH NULL Website Path 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

WEBSITE_QUERY NULL Website Query String 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

6.1.2 Component (table Comp)

Comp_ID INTEGER

CompTyp_Cd CHAR (17)

Centr_Cd CHAR(6)

Cust_ID INTEGER

Comp_Corr_IDINTEGER

Comp_Nm VARCHAR (254)

Comp_Corr_Val VARCHAR (254)

Comp_Strt_DtTm TIMESTAMP

Comp_End_DtTm TIMESTAMP

Comp_Ds VARCHAR (254)

1 IP_HOST CDW 1 rsomeshw.dev.tivoli.com

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

2 IP_HOST CDW 1 shockwave.dev.tivoli.com

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

3 IP_HOST CDW 1 abcdef.raleigh.tivoli.com

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000


20

Comp_ID INTEGER

CompTyp_Cd CHAR (17)

Centr_Cd CHAR(6)

Cust_ID INTEGER

Comp_Corr_IDINTEGER

Comp_Nm VARCHAR (254)

Comp_Corr_Val VARCHAR (254)

Comp_Strt_DtTm TIMESTAMP

Comp_End_DtTm TIMESTAMP

Comp_Ds VARCHAR (254)

4 BWM_QOS

CDW 1 QOS Job 1

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

QOS Job 1 Description

5 BWM_STI CDW 1 STM Job 1

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

STI Job 1 Description

6 BWM_STI CDW 1 STM Job 1

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

STI Job 1 Description

7 WEBSITE CDW 1 w3.ibm.com:80

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

8 WEBSITE_PATH

CDW 1 /bluepages

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

9 WEBSITE_QUERY

CDW 1 ?Selection=Name&selectOn=Farley,+Sean&Submit+search.x=15&Submit+search.y=8

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

10 WEBSITE_PATH

CDW 1 /feedback/index.html

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

11 BWM_EP CDW 1 rsomeshw

473d7dc0a531a662

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

Endpoint A Description

12 BWM_EP CDW 1 shockwave

1a3cd348ks3454js

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

Endpoint B Description

13 BWM_EP CDW 1 abcdef 1a3cd348ks3454js

2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

Endpoint C Description


21

6.1.3 Component relationship type (table RelnTyp)

RelnTyp_Cd CHAR(6)

RelnTyp_Nm * VARCHAR(120)

PCHILD Parent Child Relation

RUNSON Runs on Relation

MONITR Monitors

6.1.4 Component relationship rule (table RelnRul)

CompTyp_Source_Cd CHAR(17)

CompTyp_Target_Cd CHAR(17)

RelnTyp_Cd CHAR(6)

RelnRul_Strt_DtTm TIMESTAMP

RelnRul_End_DtTm TIMESTAMP

BWM_EP BWM_QOS PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_EP BWM_STI PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

WEBSITE WEBSITE_PATH PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

WEBSITE_PATH WEBSITE_QUERY PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_EP IP_HOST RUNSON 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

BWM_QOS WEBSITE MONITR 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

6.1.5 Component relationship (table CompReln)

CompReln_ID INTEGER

Comp_Source_ID INTEGER

Comp_Target_IDINTEGER

RelnTyp_Cd CHAR(6)

CompReln_Strt_DtTm TIMESTAMP

CompReln_End_DtTm TIMESTAMP

1 11 1 RUNSON 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

2 12 2 RUNSON 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

3 13 3 RUNSON 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

4 11 4 PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

5 12 5 PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

6 13 6 PCHILD 2002-06-30- 9999-01-01-


22

CompReln_ID INTEGER

Comp_Source_ID INTEGER

Comp_Target_IDINTEGER

RelnTyp_Cd CHAR(6)

CompReln_Strt_DtTm TIMESTAMP

CompReln_End_DtTm TIMESTAMP

12.30.30.000000

00.00.00.000000

7 7 8 PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

8 8 9 PCHILD 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

9 7 10 PCHILD 2002-06-30-12.30.30.000000

2002-06-30-12.30.30.000000

10 4 7 MONITR 2002-06-30-12.30.30.000000

2002-06-30-12.30.30.000000

6.1.6 Attribute type (table AttrTyp)

AttrTyp_Cd CHAR(17)

AttrTyp_Nm * VARCHAR(120)

IP_DOMAIN Sub Domain

URL_PROTOCOL URL Protocol

BWM_ST_CONST Tivoli Web Transaction Performance Service Time Constraint

BWM_RTT_CONST Tivoli Web Transaction Performance Round Trip Time Constraint

BWM_PRT_CONST Tivoli Web Transaction Performance Render Time Constraint

BWM_VIRTUAL_HOST Tivoli Web Transaction Performance Virtual Host

BWM_TASKID Tivoli Transaction Performance Monitoring task identifier

6.1.7 Attribute rule (table AttrRul)

CompTyp_Cd CHAR(17)

AttrTyp_Cd CHAR(17)

AttrRul_Strt_DtTm TIMESTAMP

AttrRul_End_DtTm TIMESTAMP

AttrRul_Dom_Ind CHAR

BWM_QOS BWM_VIRTUAL_HOST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

WEBSITE URL_PROTOCOL 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_QOS BWM_ST_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_QOS BWM_RTT_CONST 2002-06-30-12.30.30.000

9999-01-01-00.00.00.000

N


23

CompTyp_Cd CHAR(17)

AttrTyp_Cd CHAR(17)

AttrRul_Strt_DtTm TIMESTAMP

AttrRul_End_DtTm TIMESTAMP

AttrRul_Dom_Ind CHAR

000 000

BWM_QOS BWM_PRT_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_STI BWM_ST_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_QOS BWM_TASKID 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_STI BWM_TASKID 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_EP IP_DOMAIN 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

N

BWM_STI BWM_RTT_CONST 2002-06-30-12.30.30.000000

2002-06-30-12.30.30.000000

N

6.1.8 Attribute domain (table AttrDom)

AttrDom_ID INTEGER

CompTyp_Cd CHAR(17)

AttrTyp_Cd CHAR(17)

AttrDom_Strt_DtTm TIMESTAMP

AttrDom_End_DtTm TIMESTAMP

AttrDom_Val VARCHAR(254)

AttrDom_Ds VARCHAR(254)

6.1.9 Component attribute (table CompAttr)

CompAttr_ID INTEGER

Comp_ID INTEGER

AttrTyp_Cd CHAR(17)

CompAttr_Strt_DtTm TIMESTAMP

CompAttr_End_DtTm TIMESTAMP

CompAttr_Val VARCHAR(254)

4 4 BWM_ST_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

300

5 4 BWM_RTT_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

200

6 4 BWM_PRT_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

100

7 5 BWM_ST_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

100


24

CompAttr_ID INTEGER

Comp_ID INTEGER

AttrTyp_Cd CHAR(17)

CompAttr_Strt_DtTm TIMESTAMP

CompAttr_End_DtTm TIMESTAMP

CompAttr_Val VARCHAR(254)

8 5 BWM_RTT_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

300

9 6 BWM_ST_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

100

10 6 BWM_RTT_CONST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

300

11 7 IP_PROTOCOL 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

HTTP

12 4 BWM_VIRTUAL_HOST 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

webservera.ibm.com

13 4 BWM_TASKID 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

101

14 5 BWM_TASKID 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

110

15 6 BWM_TASKID 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

110

16 11 IP_DOMAIN 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

dev.tivoli.com

17 12 IP_DOMAIN 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

dev.tivoli.com

18 13 IP_DOMAIN 2002-06-30-12.30.30.000000

9999-01-01-00.00.00.000000

raleigh.tivoli.com

6.2 Component measurement 6.2.1 Measurement group type (table MGrpTyp)

MGrpTyp_Cd CHAR(6)

MGrpTyp_Nm * VARCHAR(120)

CATEG Category

GROUP Aggregate Types or Group Functions

STATE State


25

6.2.2 Measurement group (table MGrp)

MGrp_Cd CHAR(6)

MGrpTyp_Cd CHAR(6)

MGrp_Parent_Cd CHAR(6)

MGrp_Nm * VARCHAR(120)

AVG_E GROUP NULL Average value exists MIN_E GROUP NULL Minimum value exists MAX_E GROUP NULL Maximum value exists

TOT_E GROUP NULL Total value exists

6.2.3 Measurement group member (table MGrpMbr)

MGrp_Cd CHAR(6)

MGrpTyp_Cd CHAR(6)

MsmtTyp_ID INTEGER

AVG_E GROUP 1 AVG_E GROUP 2 AVG_E GROUP 3 MAX_E GROUP 1 MAX_E GROUP 2 MAX_E GROUP 3 MIN_E GROUP 1 MIN_E GROUP 2

MIN_E GROUP 3

TOT_E GROUP 4

6.2.4 Measurement unit category (table MUnitCat)

MunitCat_Cd CHAR(6)

MunitCat_Nm * VARCHAR(120)

TM Time Duration

QTY Quantity

6.2.5 Measurement unit (table MUnit)

MUnit_Cd CHAR(6)

MUnitCat_Cd CHAR(6)

Munit_Nm * VARCHAR(120)

QTY QTY Quantity MSec TM milliseconds 6.2.6 Time summary (table TmSum)

The period over which a measurement may be summarized.

TmSum_Cd CHAR

TmSum_Nm * VARCHAR(120)

H Hourly


26

6.2.7 Measurement source (table MSrc)

MSrc_Cd CHAR(6)

MSrc_Parent_Cd CHAR(6)

MSrc_Nm * VARCHAR(120)

Tivoli NULL Tivoli Application

BWM Tivoli IBM Tivoli Monitoring for Transaction Performance: Web Transaction Performance 5.1

6.2.8 Measurement type (table MsmtTyp)

MsmtTyp_ID INTEGER

MUnit_Cd CHAR(6)

MSrc_Cd CHAR (6)

MsmtTyp_Nm * VARCHAR(120)

MsmtTyp_Ds * VARCHAR(254)

1 MSec BWM Round Trip Time Round Trip Response Time

2 MSec BWM Service Time Backend Service Response Time

3 MSec BWM Page Render Time Page Render Response Time

4 QTY BWM Number Threshold Exceeded Number of Transactions Threshold Exceeded

6.2.9 Component measurement rule (table MsmtRul)

CompTyp_Cd CHAR(17)

MsmtTyp_ID INTEGER

BWM_STI 1

BWM_STI 2

BWM_STI 4

WEBSITE_PATH 1

WEBSITE_PATH 2

WEBSITE_PATH 3

6.2.10 Measurement (table Msmt)

Msmt_ID BIGINT

Comp_ID INTEGER

MsmtTyp_ID INTEGER

TmSum_Cd CHAR

Msmt_Strt_DtDATE

Msmt_Strt_Tm TIME

Msmt_Min_Val FLOAT

Msmt_Max_Val FLOAT

Msmt_Avg_Val FLOAT

Msmt_Tot_Val FLOAT

Msmt_Smpl_Cnt INTEGER

Msmt_Err_Cnt INTEGER

4 5 1 H 2002-06-30

13:00:00

300 1078 502 248 8

5 5 2 H 2002-06-30

13:00:00

358 6052 3054 248 8

6 5 4 H 2002-06-30

13:00:00

20 256 0

7 6 1 H 2002-06-30

13:00:00

300 1078 502 253 3

8 6 2 H 2002- 13:00:0 358 6052 3054 253 3


27

Msmt_ID BIGINT

Comp_ID INTEGER

MsmtTyp_ID INTEGER

TmSum_Cd CHAR

Msmt_Strt_DtDATE

Msmt_Strt_Tm TIME

Msmt_Min_Val FLOAT

Msmt_Max_Val FLOAT

Msmt_Avg_Val FLOAT

Msmt_Tot_Val FLOAT

Msmt_Smpl_Cnt INTEGER

Msmt_Err_Cnt INTEGER

06-30 0

9 6 4 H 2002-06-30

13:00:00

15 255 1

10 8 1 H 2002-06-30

13:00:00

100 200 150 356

11 8 2 H 2002-06-30

13:00:00

406 1000 675 356

12 8 3 H 2002-06-30

13:00:00

26 6300 5000 356

13 10 1 H 2002-06-30

13:00:00

100 200 150 356

14 10 2 H 2002-06-30

13:00:00

406 1000 675 356

15 10 3 H 2002-06-30

13:00:00

26 6300 5000 356

6.3 Helper tables The WEBSITE_PATH and WEBSITE_QUERY component can exceed the 254 character limit on component names. Therefore, Tivoli Web Transaction Performance has the following helper component table that stores component names greater than 254 characters. BWM.LONG_COMP ( comp_id integer not null, comp_nm varchar(4000) not null )

6.4 Exception tables This warehouse pack does not generate exception tables.

6.5 Incremental extraction This warehouse pack does not provide incremental extraction.


28

7 Data mart schema information This warehouse pack does not provide data marts or reports.

About this documentRelated DocumentationIBM Tivoli Monitoring for Transaction Performance: Web Transaction PerformanceTivoli Enterprise Data WarehouseDB2

OverviewOverview of Tivoli Enterprise Data WarehouseOverview of Tivoli Monitoring for Transaction Performance: Web Transaction Performance

Data FlowPrerequisitesSupported hardware and softwareLimitationsDatabase sizing considerationsData sources and targetsPre-installation stepsInstallation procedurePost-installation steps

MaintainingBacking up and restoringPruningOther maintenance topics

ETL processesBWM_c05_Initialize_ProcessBWM_c10_Load_Warehouse_ProcessETL process step descriptions

Generic schema implementationComponent configurationComponent type (table CompTyp)Component (table Comp)Component relationship type (table RelnTyp)Component relationship rule (table RelnRul)Component relationship (table CompReln)Attribute type (table AttrTyp)Attribute rule (table AttrRul)Attribute domain (table AttrDom)Component attribute (table CompAttr)

Component measurementMeasurement group type (table MGrpTyp)Measurement group (table MGrp)Measurement group member (table MGrpMbr)Measurement unit category (table MUnitCat)Measurement unit (table MUnit)Time summary (table TmSum)Measurement source (table MSrc)Measurement type (table MsmtTyp)Component measurement rule (table MsmtRul)Measurement (table Msmt)

Helper tablesException tablesIncremental extraction

Data mart schema information

ibm tivoli monitoring for transaction performance: web...

Documents