IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | | Contents | Index ]


Tivoli Enterprise Console Version 3.9
Warehouse Enablement Pack, Version 1.3.0.0
Implementation Guide for Tivoli Data Warehouse, Version 1.2.0.2

Version 3 Release 9
SC32-9126-00
Note

Before using this information and the product it supports, read the information in Appendix. Notices.

First Edition (June 2004)

This edition applies to version 3, release 9 of IBM Tivoli Enterprise Console (product number 5698-TEC) and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 1996, 2004. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

About this guide
Who should read this guide
Publications
IBM Tivoli Enterprise Console library
Tivoli Data Warehouse Library
Related Publications
Accessing publications online
Ordering Publications
Accessibility
Contacting IBM Software Support
Determine the business impact of your problem
Describe your problem and gather background information
Submit your problem to IBM Software Support
Searching knowledge bases
Obtaining fixes
Updating support information
Participating in newsgroups
Conventions used in this guide
Terminology
Typeface conventions
Operating system-dependent variables and paths
Command line syntax
Overview
Overview of Tivoli Data Warehouse
Overview of the Tivoli Enterprise Console warehouse pack
Data sources and targets
Reports
General information about reports
Installing and configuring the warehouse pack
Prerequisites
Product notes and limitations
Database-sizing considerations
Pre-installation procedures
Installation of the warehouse pack
Post-installation procedures
Create the event filter table
Schedule the ETLs
Migration from a previous release of the warehouse pack
Uninstallation of the warehouse pack
Multiple data centers
Multiple customer environments
Maintenance and problem determination
Backing up and restoring
Pruning data
Central data warehouse database
Data mart
Extraction control (table Extract_Control)
Reference information
Event Class Filter
Changing the Tivoli Enterprise Console server ID
Changing the schema name
Configuring database client drivers
Problem determination
ETL Processes
EC2_m05_ETL2_Initialization_Process
EC2_c05_ETL1_Process
EC2_m10_ETL2_Process
Central data warehouse information
Sample scenario
Component configuration
Component Type
Component Extension
Component
Relationship Type
Relationship Rule
Component Relationship
Component Type Keyword
Attribute Type
Attribute Rule
Attribute Domain
Component Attribute
Component Type Relationship
Attribute Type Relation
Component measurement
Measurement Group Type
Measurement Group
Measurement Group Member
Measurement Unit Category
Measurement Unit
Measurement Type Relationship
Time Summary
Measurement Source
Measurement Source History
Measurement Type
Measurement Rule
Measurement
Threshold Measurement Objective
Threshold Measurement Objective Range
Threshold Severity Level
Component events
Event Type
Event
Event Attribute
Event Attribute Type
Event Group
Event Group Member
Event Group Type
Event Type Relationship
Event Relationship
Component-Event Relationship
Event Rule Relationship
Component-Event Rule Relationship
Helper tables
Exception tables
Incremental extraction
Data mart schema information
Data mart EC2 Event Data Mart
Star schema
Event star schema
Fact table EC2.F_EVENT_PIT table
Metric dimension table
Dimension tables
Dimension table EC2.D_STATUS
Dimension table EC2.D_SEVERITY
Appendix. Notices
Trademarks
Index

About this guide

This document describes the warehouse enablement pack, version 1.3.0.0 for IBM(R) Tivoli Enterprise Console(R), Version 3.9. This warehouse enablement pack is created for IBM Tivoli(R) Data Warehouse, Version 1.2.0.2

Note:
This document only provides supplemental information that is specific to the Tivoli Enterprise Console warehouse enablement pack. It must be used in conjunction with the information that is provided for Tivoli Data Warehouse.

With this warehouse enablement pack (hereafter referred to as warehouse pack), you can store and maintain information about events. You can also use this information to create reports. Using this reporting function requires that you install and configure Tivoli Data Warehouse and the Tivoli Enterprise Console warehouse pack.

The Installing and Configuring Tivoli Data Warehouse document provides the following information:

This document provides the following information specifically for the Tivoli Enterprise Console warehouse pack:

Who should read this guide

This guide is for people who do any of the following activities:

Administrators and installers should have the following knowledge or experience:

Additionally, report designers and warehouse pack creators should have the following knowledge or experience:

Publications

This section lists publications in the Tivoli Data Warehouse library and other related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.

The following sets of documentation are available to help you understand, install and manage this warehouse pack

IBM Tivoli Enterprise Console library

The following documents are available in the IBM Tivoli Enterprise Console library:

Tivoli Data Warehouse Library

The following documents are available in the Tivoli Data Warehouse library. The library is available online, as described in Accessing publications online:

Related Publications

The following sections describe additional publications to help you understand and use Tivoli Data Warehouse.

IBM Redbooks

IBM Redbooks are developed and published by the IBM International Technical Support Organization, the ITSO. They explore integration, implementation and operation of realistic customer scenarios. The following Redbooks contain information about Tivoli Data Warehouse:

IBM DB2, DB2 Data Warehouse Center and DB2 Warehouse Manager Library

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, which is available on the following IBM Web site:

http://www.ibm.com/software/support.

After you install DB2, its library is also available on your system.

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

The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. TheTivoli Software Glossary is available at the following Tivoli software library Web site:

Access the glossary by clicking the Glossary link on the left pane of the Tivoli software library window.

http://www.ibm.com/software/tivoli/library/

Accessing publications online

The publications CD or product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Software Information Center Web site. The Tivoli Software Information Center is located at the following Web address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Note:
If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print dialog. This option is available when you click File --> Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using

Ordering Publications

You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

Accessibility

Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. For the warehouse pack, you use the interfaces of IBM DB2 and the reporting tool. See those documentation sets for accessibility information.

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:

If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location.

Follow the steps in this topic to contact IBM Software Support:

  1. Determine the business impact of your problem.
  2. Describe your problem and gather background information.
  3. Submit your problem to IBM Software Support.

Determine the business impact of your problem

When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:

Severity 1 Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is severely limited.
Severity 3 Some business impact: The program is usable with less significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.

Describe your problem and gather background information

When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:

Submit your problem to IBM Software Support

You can submit your problem in one of two ways:

If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.

For more information about problem resolution, see Searching knowledge bases and Obtaining fixes.

Searching knowledge bases

If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.

Search the information center on your local system or network

IBM provides extensive documentation that can be installed on your local machine or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents.

Tip: Update your information center with the latest support information.

Search the Internet

If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. To search multiple Internet resources for your product, expand the product folder in the navigation frame to the left and select Support on the Web. From this topic, you can search a variety of resources including:

Obtaining fixes

A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site:

  1. Go to the IBM Software Support Web site (http://www.ibm.com/software/support).
  2. Under Products A - Z, select your product name. This opens a product-specific support site.
  3. Under Self help, follow the link to All Updates, where you will find a list of fixes, fix packs, and other service updates for your product. For tips on refining your search, click Search tips.
  4. Click the name of a fix to read the description and optionally download the fix.

To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps:

  1. From the support page for any IBM product, click My support in the upper-right corner of the page.
  2. If you have already registered, skip to the next step. If you have not registered, click register in the upper-right corner of the support page to establish your user ID and password.
  3. Sign in to My support.
  4. On the My support page, click Edit profiles in the left navigation pane, and scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want.
  5. Click Submit.
  6. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).

Updating support information

Information centers typically include one or more support information plug-ins. These plug-ins add IBM technotes and other support documents to the information center. The following steps describe how to update your support information plug-ins:

  1. Go to the IBM Software Support Web site (www.ibm.com/software/support).
  2. Under Products A - Z, select your product name. This opens a product-specific support site.
  3. Under Search support for this product, type the keyword phrase: com.ibm.support. Click the Download check box, and click Submit.
  4. Check the search results for updates to support information plug-ins. All support information plug-ins follow the naming convention, "com.ibm.support.product.doc." If an update is available, select it from the list and view the download instructions.
  5. Save the attached zip file to a temporary location on your hard drive.
  6. Unzip the downloaded file, making sure that you retain the subfolders.
  7. From the location where you unzipped the file, copy the support information plug-in folder to your Eclipse plug-ins folder. For example, if your IBM software product is installed at c:\IBM\WebSphere\, copy the updated plug-in folder (com.ibm.support.product.doc) to c:\IBM\WebSphere\eclipse\plugins.
  8. To see the updated support information, start the information center (or shut it down and restart it), and expand the Support information node in the navigation tree.

Participating in newsgroups

User groups provide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet, and are available using standard news reader programs. These groups are primarily intended for user-to-user communication, and are not a replacement for formal support.

To access a newsgroup, use the instructions appropriate for your browser.

IBM Tivoli Enterprise Console

news://news.software.ibm.com/ibm.software.tivoli.enterprise-console

IBM Tivoli NetView(R) for UNIX and IBM Tivoli NetView for Windows

news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows

Conventions used in this guide

The section provides information about terminology, typeface conventions, and operating system-dependent commands that are used in this guide.

Terminology

This section provides information about terminology that is used in this guide.

Typeface conventions

This guide uses the following typeface conventions:

Bold
Italic
Monospace

Operating system-dependent variables and paths

This guide uses the UNIX convention for specifying environment variables and for directory notation.

When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in UNIX.

Note:
If you are using the bash shell on a Windows system, you can use the UNIX conventions.

Command line syntax

This document uses the following special characters to define the command syntax:

[ ]
Identifies an optional argument. Arguments not enclosed in brackets are required.
...
Indicates that you can specify multiple values for the previous argument.
|
Indicates mutually exclusive information. You can use the argument to the left of the separator or the argument to the right of the separator. You cannot use both arguments in a single use of the command.
{ }
Delimits a set of mutually exclusive arguments when one of the arguments is required. If the arguments are optional, they are enclosed in brackets ([ ]).
Notes:
  1. The maximum number of characters in an argument is 256.
  2. Enclose argument values that have embedded spaces with either single or double quotation marks.

Overview

The following sections provide an overview of Tivoli Data Warehouse and the warehouse pack for Tivoli Enterprise Console.

Overview of Tivoli Data Warehouse

Tivoli Data Warehouse provides the infrastructure for the following:

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

Figure 1. Tivoli Data Warehouse basic architecture
Tivoli Data Warehouse basic architecture

The central data warehouse uses a generic schema that is the same for all applications. 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 that is 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 simply warehouse pack.

The ETLs are typically scheduled to run periodically, usually during non-peak hours.

Overview of the Tivoli Enterprise Console warehouse pack

The Tivoli Enterprise Console product is a rule-based event management application that integrates system, network, database, and application management to help ensure the optimal availability of the IT resources in an enterprise. The Tivoli Enterprise Console product collects, processes, and automatically responds to common management events, such as a database server that is not responding, a lost network connection, or a successfully completed batch processing job. These events are stored in a relational database called the event database.

This warehouse pack stores raw Tivoli Enterprise Console events in the Tivoli Data Warehouse. A raw event is an event that is generated by a source. This warehouse enablement pack stores the raw base slot event information and it maps all of the values to event attributes in the Tivoli Data Warehouse. Except for the fully qualified hostname, fqhostname, extended attribute information is not stored in the Tivoli Data Warehouse.

Event information in the reports can be used for current problem diagnosis and for future problem trend analysis.

When the warehouse pack is installed, the following extract, transform, and load (ETL) processes are installed on the control server in the EC2_Tivoli_Enterprise_Console_v3.9.0_Subject_Area:

Process
Description
EC2_m05_ETL2_Initialization_Process
This process extracts the initial translated event status and severity data from the TWG.TRANSLATED_TERM table and stores it in the data mart severity dimension table and status dimension table.
EC2_c05_ETL1_Process
This process extracts the raw events from the Tivoli Enterprise Console event database, transforms the data, and stores it in the Tivoli Data Warehouse central data warehouse database.
EC2_m10_ETL2_Process
This process extracts the data from the central data warehouse database, transforms it, and stores it in the data mart database.

For more information, see ETL Processes.

The source of event data for the warehouse pack is the event database. The default name of the ODBC driver connection to the event database is TEC. If your event database is not a DB2 database, see Configuring database client drivers for information about installing and configuring your ODBC driver.

Source event information is contained in the following tables and views in the event database:

tec_t_evt_rep
Contains the base attributes of the events.
tec_t_status_event
Contains the mappings for the status of the events.
tec_t_severity
Contains the mappings for the severity of the events.
tec_t_slots_evt
Contains the fully qualified hostname extended attribute information if it is defined.
tec_evt_filter
Contains the event classes that are moved by the central data warehouse ETL from the source database to the central data warehouse database.
Note:
You can use the DB2 Data Warehouse Center to view or sample the source event data in the tables if your event database is a DB2 database. However, you must modify the name of the table before you can view or sample the source event data if your event database is not a DB2 database. For the procedure to modify the schema name, see Changing the schema name.

The following types of data are stored in the central data warehouse:

This warehouse pack contains predefined reports that provide information about the base event information. For more information about the predefined reports that are provided, see Reports.

Data sources and targets

A source database contains the information that an ETL uses and a target is the database in which the output data from the ETL is stored.

The Tivoli Enterprise Console warehouse pack the central data warehouse ETL supports multiple event database sources; therefore, the EC2_TEC_Source can point to multiple event databases.

The Tivoli Enterprise Console warehouse pack uses the following data sources and targets:

Table 1. Data sources and targets
Name in DB2 Data Warehouse Center Description
EC2_TEC_Source This data source points to one or more event databases.
EC2_TWH_CDW_Source This data source points to the TWH_CDW database. It is used for data mart ETL processing.
EC2_TWH_CDW_Target This data source points to the TWH_CDW database. It is used for central data warehouse ETL processing.
EC2_TWH_MART_Source This data source points to the TWH_MART database. It is used for data mart ETL processing.
EC2_TWH_MART_Target This data source points to the TWH_MART database. It is used for data mart ETL processing.

Reports

This chapter provides information about the predefined reports that are provided by the Tivoli Enterprise Console warehouse pack. For a description of the predefined reports that are provided, see Table 2.

The following data mart tables are used to create all of the predefined reports:

Figure 2 shows the relationships between the data mart tables:

Figure 2. Data mart table relationships
Relationship of data mart tables

General information about reports

This section provides general information about the predefined reports. Information in this section applies to all reports unless noted otherwise.

Table 2 provides a description of the predefined reports that are provided:

Table 2. Predefined report descriptions
Report name Description
Top Ten Event Classes by Status and Severity

This report displays the top 10 event classes that received the most events for the time frame that was specified. You can customize the query by specifying the following:

  • One, multiple, or all severities that are in the database.
  • One, multiple, or all statuses that are in the database.
  • One, multiple, or all Tivoli Enterprise Console server IDs that are in the database
  • The time range of the report

The details section (the text based information at the bottom of the report) of the report displays textual information that is represented by the bar graph. You can display one or more event details that make up any one of the bars by clicking the Event Class name in the details section. When you click the name, a subreport is run and it is displayed. The subreport contains more detailed event information and is grouped by severity and status. The subreport only contains information for one event class, which is determined by the event class that you clicked.

Events for Event Class by Status

This report displays all the events in a given time range for a specific event class.

The events are categorized by severity. A pie chart displays the total percentage of events by severity. The events used in the pie chart are only the events that match the criteria of this report. You can customize the query by specifying the following:

  • The event class
  • One, multiple, or all statuses that are in the database
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • The time range of the report
Note:
You can select only one event class per report.

The breakdown of the events is by severity received for the specified event class, which is shown in a pie chart. The details for the graph are not displayed. However, in the details sections, additional information about the events that were received for this event class is provided. The details section is grouped by severity and status, and ordered according to the report assumptions described in General information about reports.

Top Ten Sources with Most Events by Event Class, Status and Severity

This report displays the top 10 systems that have received the most events for the time frame that was specified. You can customize the query by specifying the following:

  • One, multiple, or all event severities
  • One, multiple, or all statuses that are in the database
  • One, multiple, or all event classes
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • The time range of the report

The details section contains a textual version of the information that is depicted graphically in the graph. You can display more information about a source when you click on the source. This subreport contains more detailed event information and is grouped by event class, severity and status. The subreport only contains information for one source, which is determined by the source you clicked.

Events for Source by Status

This report displays all of the events for a specific system and for the time frame that was specified. You can customize the query by specifying the following:

  • The source
  • One, multiple, or all statuses
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report
The graph that is displayed is a stacked bar chart with the breakdown of events per event class on the x axis and the stacked bars broken down by severity. The section under the graph describes the breakdown of the bars into their respective severities. Use this section to determine the percentages that the severities make up of the total events. The details section which displays more information on the events. The details are grouped by event class, status, and severity. This section includes all events that match the criteria.
Top Ten Hostnames/IP Addresses with Most Events by Event Class, Status and Severity

This report displays the top 10 hostnames or IP Addresses that have received the most events for the time frame that was specified. You can customize the query by specifying the following:

  • One, multiple, or all severities
  • One, multiple, or all statuses that is in the database.
  • One, multiple, or all event classes that is in the database.
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report
The details section (the text based information at the bottom of the report) of the report contains the textual information depicted graphically in the graph. You can display one or more hostnames that make up any one of the bars by clicking the hostname or IP address in the details section. When the you click on any hostname or IP address, a subreport is run. This subreport contains more detailed event information and is grouped by Event Class, Severity and Status. The subreport only contains information for the hostname or IP Address that you clicked.
Events for Hostname/IP Address by Status

This report displays all the events for a hostname or IP Address for the time frame that was specified. You can customize the query by specifying the following:

  • Hostname or IP Address
  • One, multiple, or all statuses
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report
The graph is a stacked bar chart with the breakdown of events per event class on the x axis and the stacked bars broken down by severity. Directly under the graph is a section that describes the breakdown of the bars into their respective severities. Use this information to determine what percentages the severities make up of the total events. Below this section is the details section which shows more information on the events, and groups them by event class, status and severity. This section contains all events that match the criteria.
Number of Events by Event Class, Severity, and Status over Time

This report displays the event volume received for a specified severity for the time frame that was specified. You can customize the query by specifying the following:

  • Volume breakdown (Hourly, Daily, Monthly, or Yearly)
  • One, multiple, or all severities
  • One, multiple, or all statuses
  • One, multiple, or all event classes
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report
The details section displays data that is aggregated into volume information.
Number of Events for Hostnames / IP Addresses by Event Class, Severity and Status over Time

This report displays the event volume received for a specified severity for the specified period of time. You can customize the query by specifying the following:

  • Volume breakdown (Hourly, Daily, Monthly, or Yearly)
  • One, multiple, or all severities
  • One, multiple, or all statuses
  • One, multiple, or all event classes
  • Hostname or IP address
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report
The details section displays data that is aggregated into volume information. You must limit the query to one specific hostname or IP address, which you can use to track specific event volumes from a specified hostname or IP address.
Average Time to Close Events by Severity

This report displays the average time it takes to close events based on their severity. You can customize the query by specifying the following:

  • Volume breakdown (Hourly, Daily, Monthly, or Yearly)
  • One, multiple, or all severities
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report

The details section provides more information about the graph. This report only runs against closed events.
Average Time to Close Events by Source

This report displays the time it takes on average to close events based on their source. You can customize the query by specifying the following:

  • Volume breakdown (Hourly, Daily, Monthly, or Yearly)
  • One, multiple, or all severities
  • One, multiple, or all Tivoli Enterprise Console server IDs
  • Time range to run the report

The details section provides more information about the graph. This report only runs against closed events.

Average Time to Close Events by Event Class

This report displays the time it takes on average to close events based on their Event Class. You can customize the query by specifying the following:

  • Volume breakdown (Hourly, Daily, Monthly, or Yearly)
  • One or more event classes
  • One, multiple, or all Tivoli Enterprise Console Server IDs
  • Time range to run the report
The details section displays additional information about the graph. An additional metric is provided to display the average time to close all events to be used as a comparison. This report only runs against closed events.

Installing and configuring the warehouse pack

This section describes the installation and configuration of the warehouse pack.

Prerequisites

Before installing the warehouse pack for Tivoli Enterprise Console, you must install the following software:

For information about the hardware and software requirements of Tivoli Data Warehouse and Crystal Enterprise, see the Tivoli Data Warehouse Release Notes.

Product notes and limitations

This section provides additional information about the Tivoli Enterprise Console warehouse pack.

Database-sizing considerations

Ensure that there is sufficient space in your databases for the data that is collected by this warehouse pack. The information in Table 3 is based on a typical installation. It is important that you analyze your installation to determine your actual requirements.

Table 3. Database-sizing example information
Database Assumptions Disk space
Central data warehouse
  • There are 100 000 events
  • The size of one event (including attributes) is 10 500 bytes
  • Each event has one relationship (including Update and Causes)
  • The size of a relationship is 40 bytes.
1 Gigabyte
Data mart
  • There are 100 000 events
  • There are 1000 event types
  • There are 10 statuses
  • There are 10 severities
  • The size of one event is 2000 bytes
  • The size of each event type is 260 bytes
  • The size of each status is 3000 bytes
  • The size of each severity is 3000 bytes
200 Gigabytes

The following formula was used to determine the central data warehouse disk space size:

number of events x 10 500 bytes + number of relationships x 
	40 bytes = total bytes

The following formula was used to determine the data mart disk space size:

number of events x 2 000 bytes + number of statuses x 
	3 000 bytes + number of severities x 3 000 bytes = total bytes

Pre-installation procedures

Review the tasks in this section before you begin to install the warehouse pack.

  1. If you are using multiple event database sources, you must change the server IDs of the Tivoli Enterprise servers. For the procedure to change the server ID, see Changing the Tivoli Enterprise Console server ID.
  2. Gather the following information. You will need it to install the Tivoli Enterprise Console warehouse pack.
    Table 4. Information for installation
    Information Description Record your information
    ODBC source name 1 The name for the ODBC connection to Tivoli Enterprise Console. The default value is TEC.
    User ID The user name of the DB2 instance owner for the event database.
    Password The password for the database user. Do not record the password.
    Database type Can be one of the following types:
    • DB2 UDB
    • Oracle
    • Sybase
    • Microsoft SQL Server 2
    • Informix
    Tivoli Enterprise Console event database server name, alias, or file path. Specifies the server that the instance for the event database is installed on.
    Tivoli Enterprise Console event database port The port number that is used by the Tivoli Enterprise Console event database.

    Notes:
    1. 1 If you are using multiple data sources for this warehouse pack or if the RIM host and the control server are installed on the same machine, the names of the ODBC data sources must be unique. For more information, see Product notes and limitations.
    2. 2 If your event database is installed on Microsoft SQL database, the ODBC connection must use TCP/IP only. Named pipes or other types of connections are not supported.
  3. Run the wtdwfilter command to create the event filter table in the Tivoli Enterprise Console database for every Tivoli Enterprise Console server that will be used as a source database.
    Attention:
    1. You must carefully plan which event classes are important to store in the central data warehouse. Store only those classes that will provide information that is important for reporting purposes. Although it is possible to store all event data in the central data warehouse, this can cause database size and performance problems. After carefully planning which event classes are the most important, insert these classes into the filter table using the wtdwfilter command.
    2. You must create the event filter table before you run the ETLs for the first time. If you do not create the event filter table before you run the ETLs, an error message is displayed.For a description of the problem, see Problem determination.
    Notes:
    1. The user that issues the wtdwfilter command must be authorized to create and delete tables, because the wtdwfilter command issues RDBMS Interface Module (RIM) commands. See Create the event filter table for more information.
    2. You must know the following information before when you issue the wtdwfilter command:
      • If you are not going to use the default table space, note the name of the table space that you are going to use. The table space must be created before you issue the wtdwfilter command.
      • Determine which event classes you want to store information about. For information to determine which events you want to store information about, see Event Class Filter.
  4. If your event database is a not a DB2 database, the database client for your database must be installed on the control server or the Tivoli Data Warehouse remote agent to enable communication with the events database. To determine which database clients are supported by the Tivoli Data Warehouse and the procedure to install the clients, see the Tivoli Data Warehouse Release Notes. Once the client has been installed, you must configure the Tivoli Data Warehouse DB2 drivers. For the procedure to configure the DB2 data warehouse drivers, see Configuring database client drivers.
  5. If your Crystal Enterprise Server is not installed on the same machine as the control server, verify that the following Windows services are started and running on the Crystal Enterprise Server:
  6. Determine what time of day you would want to schedule the ETLs to run. You might need to discuss this with your database administrator and network systems programmer. Consider your event database maintenance schedule and the wtdbclear purge schedule when you choose a time for the ETLs to run. All of these things are using the database and will affect each other and system performance.
  7. Create an index in the Tivoli Data Warehouse central data warehouse database to increase the performance of this warehouse pack and any other event-based warehouse packs. If you do not create this index, the ETLs will run for a very long time when there are numerous events in the central data warehouse.

    From a DB2 command prompt, issue the following SQL statements to create the index:

    1. db2 -v "connect to twh_cdw"
    2. db2 -v "create index twg.eventattr_x2 on twg.eventattr (event_id)"
    3. db2 "disconnect current"

Installation of the warehouse pack

Install the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse. Use the twh_install_props.cfg installation properties file that is located in the /tdw_weps/ec2/v110/ directory.

You can schedule the time that you want the ETL to run when you install the warehouse pack. If you schedule the ETL at this time, you must specify the time that you want the ETL to run. For more information about scheduling the ETL, see Schedule the ETLs.

Post-installation procedures

After you install the warehouse pack, you must perform the following procedures in the order specified. After you complete each step, return to this section and perform the next procedure that is specified until all of the procedures have been performed.

  1. Create a schedule for the ETLs. For information about scheduling ETLs, see Schedule the ETLs and for more information about the ETLs, see ETL Processes.
  2. When you finish installing the warehouse pack, the following message is displayed in the Installation Complete window:
    CDWIW0028W To complete the warehouse pack configuration,
    manually run the initialization step 
    EC2_m05_s010_mart_initialization as well as any additional
    steps documented in the warehouse pack implementation 
    guide. The ETL, while scheduled based on the options
    selected, will not run until these steps have been performed.
    Use the following procedures to perform this task:
    1. Put the EC2_m05_s010_mart_initialization step in production mode:
      1. From the left side of DB2 Data Warehouse Center window, click Subject Areas -> EC2_Tivoli_Enterprise_Console_v3.9.0_Subject_Area -> Processes -> EC2_m05_ETL2_Initialization_Process.
      2. From the right side of DB2 Data Warehouse Center window, right-click EC2_m05_s010_mart_initialization.
      3. From the drop-down list that is displayed, click Mode -> Production.
    2. Run the EC2_m05_s010_mart_initialization step:
      1. From the DB2 Data Warehouse Center window menu, click Warehouse -> Work in Progress. The Work in Progress window is displayed.
      2. From the Work in Progress window menu, click Work in Progress -> Run New Step.
      3. Double-click EC2_m05_s010_mart_initialization.
      4. Click OK.
  3. Put the central data warehouse ETL and data mart ETL into production mode:
    1. Put the EC2_c05_ETL1_Process process into production:
      1. From the left side of DB2 Data Warehouse Center window, click EC2_c05_ETL1_Process.
      2. From the right side of DB2 Data Warehouse Center window, select all of the entries that begin with EC2_c05.
      3. Right-click the selected entries.
      4. From the drop-down list that is displayed, click Mode -> Production.
    2. Put the EC2_m10_ETL2_Process process into production:
      1. From the left side of DB2 Data Warehouse Center window, click EC2_m10_ETL2_Process.
      2. From the right side of DB2 Data Warehouse Center window, select all of the entries that begin with EC2_m10.
      3. Right-click the selected entries.
      4. From the drop-down list that is displayed, click Mode -> Production.

Create the event filter table

This section provides information about creating the event filter table using the wtdwfilter command. For more information about the wtdwfilter command, see wtdwfilter.

Use the following procedure to create the event filter table:

  1. Determine which event classes you want to move from the Tivoli Enterprise Console event database to the central data warehouse.
  2. Copy the wtdwfilter file from the /tdw_weps/ec2/v110/misc directory of the installation media to the $BINDIR/bin directory of each system that the Tivoli Enterprise Console servers are running on.
  3. For Tivoli Enterprise Console servers that are running on UNIX systems, use the following command to change the permission for the wtdwfilter file to enable it to run:
    chmod 750 wtdwfilter
  4. Use one of the following methods to source the Tivoli environment settings for the wtdwfilter command:
  5. Use the wtdwfilter command to create the event filter table. See wtdwfilter for more information. If you do not want to use the default table space, ensure that table space that you want to store the event table in exists and that you know its name.

Schedule the ETLs

This section provides information about scheduling your ETL to run. Review the information in this section before you schedule the ETL.

If you did not schedule the ETLs to run when you installed the warehouse pack, you must now schedule the EC2_c05_ETL1_Process process to run periodically. Review the following information and then schedule the EC2_c05_ETL1_Process process to run using the procedure in Installing and Configuring Tivoli Data Warehouse.

Migration from a previous release of the warehouse pack

This Tivoli Enterprise Console warehouse pack is a new version. It does not replace earlier versions of the Tivoli Enterprise Console warehouse packs.

Uninstallation of the warehouse pack

Use the uninstallation procedures in the Installing and Configuring Tivoli Data Warehouse to uninstall the Tivoli Enterprise Console warehouse pack. Once you have finished that procedure, perform the following tasks:

Multiple data centers

To use the Tivoli Data Warehouse to separate data for multiple data centers, you must use SQL scripts to configure the following values:

Information for scripts Value or location
Field in source data The value that matches the hostname base attribute of the raw event. The ETL determines this by comparing the value of this attribute with the values in the EC2.CENTR_LOOKUP table.
Name of lookup table EC2.CENTR_LOOKUP table
Name of center list TWG.Centr

For the procedures and example SQL statements that are used to configure Tivoli Data Warehouse to separate data for multiple data centers, see the Installing and Configuring Tivoli Data Warehouse.

After the initial configuration for multiple data centers, you must modify the EC2.CENTR_LOOKUP table to map the hostname to the data center when data centers are added and removed.

You can use the DB2 Data Warehouse Center to view or sample the source event data in the tables if your event database is a DB2 database. However, you must modify the name of the table before you can view or sample the source event data if your event database is not a DB2 database. For the procedure to modify the schema name, see Changing the schema name.

Multiple customer environments

After you install the warehouse pack, you can configure Tivoli Data Warehouse to separate data for the multiple customer environments. To configure this, you must create SQL scripts with the following values:

Information for scripts Value or location
Field in source data The value that matches the hostname base attribute of the raw event. The ETL determines this by comparing the value of this attribute with the values in the EC2.CENTR_LOOKUP table.
Name of lookup table EC2.CUST_LOOKUP table
Column to use for lookup Cust_ID
Name of customer list TWG.Cust

For the procedural instructions and example SQL statements, see the information about warehouse pack installation in the Installing and Configuring Tivoli Data Warehouse guide.

After the initial configuration for multiple customer environment, you must modify the EC2.CUST_LOOKUP table when customers are added and removed.

You can use the DB2 Data Warehouse Center to view or sample the source event data in the tables if your event database is a DB2 database. However, you must modify the name of the table before you can view or sample the source event data if your event database is not a DB2 database. For the procedure to modify the schema name, see Changing the schema name.

Maintenance and problem determination

This section describes maintenance tasks for the warehouse pack.

Backing up and restoring

See Installing and Configuring Tivoli Data Warehouse for information about backing up and restoring your data. This Tivoli Enterprise Console warehouse pack requires no additional procedures.

Pruning data

This section provides information about pruning data from the central data warehouse database and data mart database.

Parameters are provided to control how often the databases are pruned. The parameter values represent a date duration whose format is yyyymmdd. Preceding zeros are not included in the date duration value. For example, the value 0000300 represents three months. The following are examples of other values that are used:

Table 5. Example pruning values
yyyymmdd Example value
       600 6 months
     10000 1 year
   0050000 5 years

Central data warehouse database

To manage the high volume of event data, use the Prune_Event_Ctrl table to delete that data. The Prune_Event_Log table keeps a history of data pruning.

By default, the data older than 6 months is pruned when the CDW_c05_Prune_and_Mark_Active process runs. This process is within the CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area. By default, this process runs daily at 6:00 a.m.

Pruning event data (table Prune_Event_Ctrl)

Tivoli Data Warehouse uses the event age and the event date and time to find aged events. Aged events are ones that are older than the value specified in the Event_Age column. Then, the following data is deleted in this order:

  1. The parent event that is an aged event (in the EventAttr table)
  2. Either the source or target that is an aged event (in the EventReln table)
  3. The relationship that involves an aged event (in the CEReln table)
  4. The aged event

Table 6 shows an example of the values that the Tivoli Enterprise Console specifies in the Prune_Event_Ctrl table.

Table 6. Prune_Event_Ctrl table example
MSrc_CD CHAR (6) TmSum_CD CHAR(1) Event_Age
EC2 P 600

This means that event data is retained by default for 6 months in the central data warehouse. Use the following SQL statement on the control server at the DB2 prompt to change the default value:

update twg.prune_event_ctrl set Event_Age=x where MSrc_Cd='EC2'

The value x is the new value that you want to specify. For an explanation of the value format, see Pruning data.

Data mart

Pruning data from the fact tables is implemented in the EC2_m10_s010_pre_extract step. The prune mart control table EC2.Prune_Mart_Control specifies which data are pruned and contains a date duration value for the fact table(s). By default, all fact data older than 1 year is pruned when the process step runs.

The record of data pruning is written in the EC2.Prune_Mart_log table.

Specify the data to be pruned by setting the value of the PMARTC_DURATION column of the Prune_MART_Control table. Modify the value using an SQL statement on the control server at the DB2 prompt. For example, modify and then use the following SQL command on the control server at the DB2 prompt on the data mart (EC2_MART) to change the prune values:

UPDATE EC2.PRUNE_MART_Control 
SET PMARTC_DURATION =xxx 
WHERE TABLE_NAME='EC2.F_EVENT_PIT'

The value xxx is the value you want to change. For an explanation of the value format, see Pruning data.

Extraction control (table Extract_Control)

The extraction control table assists you in incrementally extracting data from a source database. For an example of incremental extraction, see the Enabling an Application for Tivoli Data Warehouse guide. Table 7 and Table 8 provide the extract control information.

Table 7. Central data warehouse ETL extract control information
ExtCtl_
Source VARCHAR (120)
ExtCtl_
Target VARCHAR (120)
ExtCtl_
From_
RawSeq CHAR (10)
ExtCtl_
To_
RawSeq CHAR (10)
ExtCtl_
From_
IntSeq BIGINT
ExtCtl_
To_
IntSeq BIGINT
ExtCtl_
From_
DtTm TIME
STAMP
ExtCtl_
To_
DtTm TIME
STAMP
MSrc_
Corr_Cd CHAR (6)
1x.tec_t_evt_rep EC2.stage_events 0 0 0 0
1970-01-01-00.00.
00.000000

1970-01-01-00.00.
00.000000
EC2

1 The central data warehouse ETL can be sourced from multiple databases. Each source has a different value specified for x in ExtCtl_Source.

Table 8. Data mart ETL extract control information
ExtCtl_
Source VARCHAR (120)
ExtCtl_
Target VARCHAR (120)
ExtCtl_
From_
RawSeq CHAR (10)
ExtCtl_
To_
RawSeq CHAR (10)
ExtCtl_
From_
IntSeq BIGINT
ExtCtl_
To_IntSeq BIGINT
ExtCtl_
From_
DtTm TIME
STAMP
ExtCtl_
To_
DtTm TIME
STAMP
MSrc_
Corr_Cd CHAR (6)
TWG.EVENTTYP EC2.D_EVTTYP_
METRIC
0 0 0 0
1970-01-01-00.00.
00.000000

9999-01-01-00.00.
00.000000
EC2
TWG.EVENT EC2.F_EVENT_PIT 0 0 0 0
1970-01-01-00.00.
00.000000

9999-01-01-00.00.
00.000000
EC2
TWG.EVENTATTR EC2.F_EVENT_PIT 0 0 0 0
1970-01-01-00.00.
00.000000

9999-01-01-00.00.
00.000000
EC2

Reference information

This section provides supplemental information about the Tivoli Enterprise Console warehouse pack.

Event Class Filter

The wtdwfilter command is used to create and modify the event filter. The event filter is used to determine which classes of events are moved from the Tivoli Enterprise Console event database to the central data warehouse database. The event filter is an inclusive filter, which means that only events that belong to the event classes that are specified in the event filter table are moved.

Notes:
  1. You must create the event filter table before you run the ETLs for the first time. If you do not create the event filter table before you run the ETLs, an error message is displayed.For a description of the problem, see Problem determination.
  2. On Windows systems, the wtdwfilter command must run in the bash shell. Run the script %SystemRoot%\WINNT\system32\drivers\etc\Tivoli\setup_env.cmd from the command line, and then enter bash to enter the bash shell environment.

wtdwfilter

Create and modify the event filter table.

Syntax

wtdwfilter [option [suboption]]

Description

Use the wtdwfilter command to perform the following tasks:

See Command line syntax for a description of the characters that are used to specify wtdwfilter command syntax.

Authorization

The user that issues the wtdwfilter command must be authorized to create and delete tables, because the wtdwfilter command issues RDBMS Interface Module (RIM) commands. If an unauthorized user tries to issue the wtdwflter command, it fails when you try to create or delete the associated event filter table.

Options

-crttb [-tblspace tablespace_name] [-debug]
Creates the event filter table in the event database.
-tblspace tablespace_name
The name of the table space that the event filter table should be created in. If this value is not specified, the event filter table is created in the default table space.
Notes:
  1. The -tblspace option does not create table spaces. Table spaces must be created before they can be specified with the -tblspace option.
  2. The term table space is used by the IBM DB2 and Oracle products. Other RDBMS vendors use different terminology for this concept. See Terminology for information about terminology that is used by other database vendors.
-debug
Run the option in debug mode. Informational messages are displayed.
-deltb [-debug]
Deletes the event filter table from the event database.
-debug
Run the option in debug mode. Informational messages are displayed.
-impclass {-file filename | -rb rule_base} [-debug]
Add event classes to the event filter table.
-file filename
Add event classes that are listed in filename file to the event filter table. The name of the event class is case sensitive. Event class names must be listed on separate lines. The following is an example of file that lists classes:
TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop
Note:
You can use the wrb command to create a file that lists the event classes that belong to any loaded rule base. For the procedure to create this file, see Usage Notes.
-rb rule_base
Add event classes that are loaded in the rule_base rulebase to the event filter table.
-debug
Run the option in debug mode. Informational messages are displayed.
-delclass {-file filename | -rb rule_base | -all} [-debug]
Delete classes from the event filter table.
-file filename
Delete event classes that are listed in filename file from the event filter table. The name of the event class is case sensitive. Event class names must listed on separate lines. The following is an example of file that lists classes:
TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop
Note:
You can use the wrb command to create a file that lists the event classes that belong to any loaded rule base. For the procedure to create this file, see Usage Notes.
-rb rule_base
Delete event classes that are loaded in the rule_base rulebase from the event filter table.
-all
Delete all classes from the event filter table. This option can only be specified with the -delclass option.
-debug
Run the option in debug mode. Informational messages are displayed.
-lsclass [-debug]
List the names of the event classes that are loaded in the event filter table. The output list of names is sorted alphabetically by class name.
-debug
Run the option in debug mode. Informational messages are displayed.

Usage Notes

Use the following procedure to create a file that lists the event classes that belong to any loaded rule base:

  1. Issue the following command to create the file:
    wrb -lsrbclass Default > new.file  
    Default is the name of your rule base and new.file can be any name you choose.
  2. Remove the following lines from the file:
    Class Name 
    --------------------------------- 
  3. Add or remove event classes to include only those event classes that you want to list.

For more information on the wrb command, see the Tivoli Enterprise Console Command and Task Reference.

Examples

The following example creates an event filter table in a table space named yourtablespace:

wtdwfilter -crttb -tblspace yourtablespace 

The following example imports into the event filter table the event classes listed in a file named class.list:

wtdwfilter -impclass -file class.list 

The following is an example of the default file that lists the classes:

TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop

The following example deletes the classes that are loaded in the rulebase named Default from the event filter table. Note that the -debug option is also specified to provide informational messages.

wtdwfilter -delclass -rb Default -debug

Changing the Tivoli Enterprise Console server ID

This warehouse enablement pack ETL can read data from multiple instances of Tivoli Enterprise Console event databases. However, each of the Tivoli Enterprise Console servers must have a different server ID to differentiate them. The server ID is 1 by default. Use the following procedure to change the server ID:

  1. Issue the following command to stop the Tivoli Enterprise Console server:
    wstopesvr
  2. Issue the following command to purge the event database:
    wtdbclear -efl -t 0
    Note:
    This command purges your event server database. It is necessary to remove any existing events because they have server ID of 1. To ensure data integrity, the central data warehouse ETL must only read events from this database when it has the new server ID value.
  3. Edit the $BINDIR/TME/TEC/.tec_config file and change server ID as follows:
    1. Uncomment the following line:
      #tec_server_handle=1
    2. Change the server ID. For example, if you are using the server ID 6, change the line as follows:
      tec_server_handle=6
  4. Save the .tec_config file.
  5. Issue the following command to start the Tivoli Enterprise Console server:
    wstartesvr

Changing the schema name

During installation of this warehouse pack, the user name that is used to install the warehouse pack is the default schema name for each of the tables that contain the source event information in the event database. Although this does not affect the behavior of the warehouse pack, it prevents you from sampling or viewing the table contents using the DB2 Data Warehouse Center. For more information about the source tables, see Overview of the Tivoli Enterprise Console warehouse pack.

To sample or view the table contents for event databases, perform the following procedure for all data sources with a name similar to EC2_xxx_Source. EC2_TEC_Source is the default name and is used in the following procedure.

  1. From the DB2 Data Warehouse Center on the control server, click Warehouse Sources.
  2. Do the following for the EC2_TEC_Source data source:
    1. Click the + symbol next to the source name.
    2. For the tec_t_evt_req tables listed in the right pane, do the following:
      1. Right click the table name.
      2. From the pop-up menu, click Properties.
      3. Modify the Table Schema value. The name you use depends on the your event database type. For the value to use, see Table 9.
      4. Click OK.

Table 9. Schema names
Database type Name More information
1 You cannot sample or view the contents of a table if your event database is a Sybase database.
DB2 Database administrator name Specify the name of the database administrator that was used to create the event database and the source tables.
Informix None Do note specify a name.
Sybase None Do not specify a name. 1
Oracle Database administrator name Specify the name of the database administrator that was used to create the event database and the source tables.
Microsoft SQL database administrator name Specify the name of the database administrator that was used to create the event database and the source tables.

Configuring database client drivers

If your event database is not a DB2 database, the database client for your database must be installed on the control server or the Tivoli Data Warehouse remote agent to enable communication with the events database. To determine which database clients are supported by the Tivoli Data Warehouse and the procedure to install the clients, see the Tivoli Data Warehouse Release Notes. Once the client has been installed, you must configure the control server DB2 drivers as described in this section.

Do one of the following procedures on the control server for your event database type:

Configuring an Informix client

If your event database is an Informix database, you must configure the control server DB2 Data Warehouse drivers to communicate with the Informix database.

  1. Click Start -> Settings ->Control Panel. The Control Panel window is displayed.
  2. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  3. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  4. From the ODBC Data Source Administrator window, click the System DSN tab.
  5. Click Add. The Create New Data Source window is displayed.
  6. Select the DataWHSE 3.60 32-bit INFORMIX driver.
  7. Click Finish. The ODBC Informix Driver Setup window is displayed.
  8. From the ODBC Informix Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type TEC in the Data Source Name field.
    3. Type the name of the event database in the Database Name field.
    4. Click the Connection tab.
    5. Type the hostname of the system on which the event database is installed in the Host Name field.
    6. Type onsoctcp in the Protocol Type field.
  9. Click Test Connect to test the connection to your event database.
  10. Click OK.

Configuring a Sybase client

If your event database is a Sybase database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Sybase database using the following procedure:

  1. Use the DSEdit utility that was installed with the Sybase client to create a client connection to the event database. Note the text that you type in the server field for your client connection for later use. For more information about the DSEdit Utility, see the Sybase documentation.
  2. Click Start -> Settings ->Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit Sybase driver.
  8. Click Finish. The ODBC Sybase Driver Setup window is displayed.
  9. From the ODBC Sybase Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Server field for step 1 in the Data Source Name field.
    3. Type the name of the event database in the Database Name field.
    4. Type TEC in the Database Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.

Configuring a Microsoft SQL client

If your event database is a Microsoft SQL database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Microsoft SQL database using the following procedure:

  1. Use the SQL Server Client Network Utility that is installed with your MS SQL Server client to configure a connection to the event database as follows:
    1. Click the General tab.
    2. Ensure the TCP/IP is enabled. The Tivoli Data Warehouse does not support any other protocol for connecting to the source database.
    3. Click the Alias tab.
    4. Create a connection to the event database. Note the Server Alias value for later use.
  2. Click Start -> Settings ->Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit SQL driver.
  8. Click Finish. The ODBC SQL Driver Setup window is displayed.
  9. From the ODBC Informix Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Server Alias field for step 1 in the Data Source Name field.
    3. Type the name of the event database in the Database Name field.
    4. Type TEC in the Database Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.

Configuring an Oracle client

If your event database is a Oracle database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Oracle database using the following procedure:

  1. Use the Net8 Assistant that was installed with the Oracle client to configure a connection to the event database. Note the Net Service Name used to configure the client connection for later use.
  2. Click Start -> Settings ->Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit Oracle driver.
  8. Click Finish. The ODBC Oracle Driver Setup window is displayed.
  9. From the ODBC Oracle Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Net Service Name field for step 1 in the Data Source Name field.
    3. Type TEC in the Database Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.

Problem determination

For common problems and solutions, see Installing and Configuring Tivoli Data Warehouse.

If you have a problem with this warehouse pack, review the information in this section.

ETL Processes

The warehouse pack has the following processes:

EC2_m05_ETL2_Initialization_Process

This process contains the initialization step that extracts the translated event severity and status values from the TWG.TRANSLATED_TERM tables and loads the data into the EC2.D_SEVERITY and EC2.D_STATUS tables.

The process step must be manually run only once before the EC2_c05_ETL1_Process and EC2_m10_ETL2_Process processes are run.

Notes:
  1. This process must be run only once manually. Do not schedule this process to run.
  2. Do not run this process more than once.
  3. You must create the event filter table before you run the ETLs for the first time. For more information, see Problem determination.

This process has the following step:

EC2_m05_s010_mart_initialization
This step loads the translated event severity and status values into the D_SEVERITY and D_STATUS tables.

EC2_c05_ETL1_Process

This process contains the steps that are responsible for extracting raw events from the Tivoli Enterprise Console event database, transforming this data to fit into the schema, and loading the data into Tivoli Data Warehouse.

This process should be scheduled to run on a nightly basis. The process steps can run manually also. For information about how to run the steps manually, see Installing and Configuring Tivoli Data Warehouse.

This process has the following steps:

EC2_c05_s010_src_pre_extract
This step drops and recreates the staging tables.
EC2_c05_s020_src_extract
This step updates the Extract_control table and extracting the relevant event information from the Tivoli Enterprise Console event database using the event class filter. This step populates the temporary tables that are created in the previous step with the extracted information.
EC2_c05_s030_src_transform
This step transforms the temporary event information and relationship information into a format that is comparable to the central data warehouse schema. It also creates any new attribute update events or repeat count events and the necessary relationships.
EC2_c05_s040_src_load
This step moves the data from the staging or translation tables into the central data warehouse tables.

If errors occur in this process, they are displayed in the Work In Progress window in the DB2 Data Warehouse Center. A red X is displayed for the step that failed during this process. To determine more information about the error, see the log files for the step that are located in the $TIVOLI_COMMON_DIR\cdw\logs\etl directory under the root directory of your DB2 installation. For more information about the error information, see Installing and Configuring Tivoli Data Warehouse.

EC2_m10_ETL2_Process

This process contains four steps that extract event data from the central data warehouse, transform the data to fit into the Tivoli Enterprise Console 3.9 data mart schema, and loads the data into the data mart.

Note:
Do not schedule or manually run the EC2_m10_ETL2 process. It is started automatically when the EC2_c05_ETL1_Process sucessfully completes running.

This process has the following steps:

EC2_m10_s010_mart_pre_extract
This step drops and recreates the staging tables in the data mart.
EC2_m10_s020_mart_extract
This step extracts the relevant event information from the central data warehouse based on the updated Extract_control table and puts the data into temporary tables in the data mart.
EC2_m10_s030_mart_transform
This step transforms the temporary event information and relationships into a format for the star schema for the data mart.
EC2_m10_s040_mart_load
This step moves the data from the staging tables into the static data mart tables, which makes the data available for the Crystal reports. This step also updates the extract_control table in the central data warehouse.

If errors occur in this process, they are displayed in the Work In Progress window in the DB2 Data Warehouse Center. A red X is displayed for the step that failed during this process. To determine more information about the error, see the log files for the step that are located in the $TIVOLI_COMMON_DIR\cdw\logs\etl directory under the root directory of your DB2 installation. For more information about the error information, see Installing and Configuring Tivoli Data Warehouse.

Central data warehouse information

Before reading this section, read about the generic schema for the central data warehouse, which is described in Enabling an Application for Tivoli 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. These columns are also marked with an asterisk (*) after the column name.

Sample scenario

This section provides a sample scenario that provides an example of how information about Tivoli Enterprise Console events is stored in Tivoli Data Warehouse. The event information in this chapter is based on the following example scenario:

  1. The following events are generated by the Tivoli Enterprise Console: For the event information, see Table 10.
  2. An active correlation rule identified the TEC_Error event as the cause of the TEC_Notice event and correlated these two events.
  3. An operator used the Tivoli Enterprise Console to close the TEC_Start event.
  4. Two TEC_Notice events are generated by the Tivoli Enterprise Console.
  5. A duplication filter rule dropped these two events.
  6. The repeat count attribute of the TEC_Notice event was updated.

Table 10 provides the event information that was generated in step 1.

Table 10. Original Events
Event Table or view Column value
Event 1 TEC_T_EVT_REP
CLASS - TEC_Start
DATE_RECEPTION - 1075915924 
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SEVERITY -  20
STATUS -  0
LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:04 AM
SOURCE -  TEC
HOSTNAME -  ibmuser.ibm.com
REPEAT_COUNT - 0
DATE_EVENT - Feb 04 11:32:04 2004
MSG - TEC Event Server Initialized 
MSG_INDEX - 0
NUM_ACTIONS - 0
CREDIBILITY - 1
ACL-[admin]
CAUSE_DATE_RECEPTION - 0
CAUSE_EVENT_HANDLE - 0
TEC_T_SLOTS_EVT
 DATE_RECEPTION - 1075915924
 SERVER_HANDLE - 1
 EVENT_HANDLE - 1
 SLOT_NAME - fqhostname
 SHORT_SLOT_VALUE  - ibmuser.ibm.com
 LONG_SLOT_VALUE - NULL        
TEC_T_SEVERITY
10 - UNKNOWN
20 - HARMLESS
30 - WARNING
40 - MINOR
50 - CRITICAL
60 - FATAL
TEC_T_STATUS_EVENT
0 - OPEN
10 - RESPONSE
20 - ACK
30 - CLOSED
Event 2 TEC_T_EVT_REP
CLASS - TEC_Error
DATE_RECEPTION - 1075915941 
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SEVERITY -  30
STATUS -  0
LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:21 AM
SOURCE -  TEC
HOSTNAME -  ibmuser.ibm.com
REPEAT_COUNT - 0
DATE_EVENT - Feb 04 11:32:21 2004
MSG - TEC encountered error processing rule xyz
MSG_INDEX - 0
NUM_ACTIONS - 0
CREDIBILITY - 1
ACL-[admin]
CAUSE_DATE_RECEPTION - 0
CAUSE_EVENT_HANDLE - 0
TEC_T_SLOTS_EVT
DATE_RECEPTION - 1075915941
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SLOT_NAME - fqhostname
SHORT_SLOT_VALUE  - ibmuser.ibm.com
LONG_SLOT_VALUE - NULL        
TEC_T_SEVERITY
10 - UNKNOWN
20 - HARMLESS
30 - WARNING
40 - MINOR
50 - CRITICAL
60 - FATAL
TEC_T_STATUS_EVENT
0 - OPEN
10 - RESPONSE
20 - ACK
30 - CLOSED
Event 3 TEC_T_EVT_REP
CLASS - TEC_Notice
DATE_RECEPTION - 1075915942 
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SEVERITY -  30
STATUS -  0
LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:22 AM
SOURCE -  TEC
HOSTNAME -  ibmuser.ibm.com
REPEAT_COUNT - 0
DATE_EVENT - Feb 04 11:32:22 2004
MSG_INDEX - 0
NUM_ACTIONS - 0
CREDIBILITY - 1
ACL-[admin]
CAUSE_DATE_RECEPTION - 1075915941
CAUSE_EVENT_HANDLE - 1
TEC_T_SLOTS_EVT
 DATE_RECEPTION - 1075915942
 SERVER_HANDLE - 1
 EVENT_HANDLE - 1
 SLOT_NAME - fqhostname
 SHORT_SLOT_VALUE  - ibmuser.ibm.com
 LONG_SLOT_VALUE - NULL        
	      
TEC_T_SEVERITY
10 - UNKNOWN
20 - HARMLESS
30 - WARNING
40 - MINOR
50 - CRITICAL
60 - FATAL
TEC_T_STATUS_EVENT
0 - OPEN
10 - RESPONSE
20 - ACK
30 - CLOSED

The next group of events provides an example of how updated events are moved into Tivoli Data Warehouse for steps 2 through 6.

There are two classifications of updated events:

The event information in Table 11 provides an example of both types of updates to the original events. The entire event is listed, however, only the highlighted fields have been modified.

Notes:
  1. Extraction control is based on the last_modified_time field in the event database. This warehouse pack knows that events are updated when the event already exists in Tivoli Data Warehouse and the last_modified_time field has been updated. This warehouse pack then determines which field changed, and stores the appropriate updated value if one exists
  2. Not all base attributes are specified for the events.
Table 11. Modified Events
Event Table or view Column value
Event 1 TEC_T_EVT_REP
CLASS - TEC_Start
DATE_RECEPTION - 1075915924 
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SEVERITY -  20
STATUS -  30
LAST_MODIFIED_TIME - Feb. 4, 2004 11:35:05 AM
SOURCE -  TEC
HOSTNAME -  ibmuser.ibm.com
REPEAT_COUNT - 0
DATE_EVENT - Feb 04 11:32:04 2004
MSG - TEC Event Server Initialized 
MSG_INDEX - 0
NUM_ACTIONS - 0
CREDIBILITY - 1
ACL-[admin]
CAUSE_DATE_RECEPTION - 0
CAUSE_EVENT_HANDLE - 0
DURATION - 181
TEC_T_SLOTS_EVT
DATE_RECEPTION - 1075915924
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SLOT_NAME - fqhostname
SHORT_SLOT_VALUE  - ibmuser.ibm.com
LONG_SLOT_VALUE - NULL        
TEC_T_SEVERITY
10 - UNKNOWN
20 - HARMLESS
30 - WARNING
40 - MINOR
50 - CRITICAL
60 - FATAL
TEC_T_STATUS_EVENT
0 - OPEN
10 - RESPONSE
20 - ACK
30 - CLOSED
Event 3 TEC_T_EVT_REP
CLASS - TEC_Notice
DATE_RECEPTION - 1075915942 
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SEVERITY -  30
STATUS -  0
LAST_MODIFIED_TIME - Feb. 4, 2004 11:36:56 AM
SOURCE -  TEC
HOSTNAME -  ibmuser.ibm.com
REPEAT_COUNT - 2
DATE_EVENT - Feb 04 11:32:22 2004
MSG_INDEX - 0
NUM_ACTIONS - 0
CREDIBILITY - 1
ACL-[admin]
CAUSE_DATE_RECEPTION - 1075915941
CAUSE_EVENT_HANDLE - 1
TEC_T_SLOTS_EVT
DATE_RECEPTION - 1075915942
SERVER_HANDLE - 1
EVENT_HANDLE - 1
SLOT_NAME - fqhostname
SHORT_SLOT_VALUE  - ibmuser.ibm.com
LONG_SLOT_VALUE - NULL   
TEC_T_SEVERITY
10 - UNKNOWN
20 - HARMLESS
30 - WARNING
40 - MINOR
50 - CRITICAL
60 - FATAL
TEC_T_STATUS_EVENT
0 - OPEN
10 - RESPONSE
20 - ACK
30 - CLOSED

Component configuration

The following sections describe the component configuration.

Component Type

The Tivoli Enterprise Console warehouse pack does not use this table.

Component Extension

The Tivoli Enterprise Console warehouse pack does not use this table.

Component

The Tivoli Enterprise Console warehouse pack does not use this table.

Relationship Type

Table 12. Relationship Type (TWG.RelnTyp Table)
RelnTyp_
Cd
*RelnTyp_Nm MSrc_
Corr_Cd
* This column is translated
CAUSES This represents a generic relationship where an entity causes another entity. MODEL1
UPDATE This represents a relationship where one entity updates another entity. EVENTS

Relationship Rule

The Tivoli Enterprise Console warehouse pack does not use this table.

Component Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Component Type Keyword

The Tivoli Enterprise Console warehouse pack does not use this table.

Attribute Type

The Tivoli Enterprise Console warehouse pack does not use this table.

Attribute Rule

The Tivoli Enterprise Console warehouse pack does not use this table.

Attribute Domain

The Tivoli Enterprise Console warehouse pack does not use this table.

Component Attribute

The Tivoli Enterprise Console warehouse pack does not use this table.

Component Type Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Attribute Type Relation

The Tivoli Enterprise Console warehouse pack does not use this table.

Component measurement

The following sections describe the component measurement.

Measurement Group Type

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Group

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Group Member

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Unit Category

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Unit

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Type Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Time Summary

Table 13. Time Summary (TWG.TmSum Table)
TmSum_Cd *TmSum_Nm
* This column is translated
P Point

Measurement Source

Table 14. Measurement Source (TWG.MSrc Table)
MSrc_Cd MSrc_Parent_Cd MSrc_Nm
* This column is translated
Tivoli NULL Tivoli Application
EVENTS NULL Events
EC2 Tivoli Tivoli Enterprise Console

Measurement Source History

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Type

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement Rule

The Tivoli Enterprise Console warehouse pack does not use this table.

Measurement

The Tivoli Enterprise Console warehouse pack does not use this table.

Threshold Measurement Objective

The Tivoli Enterprise Console warehouse pack does not use this table.

Threshold Measurement Objective Range

The Tivoli Enterprise Console warehouse pack does not use this table.

Threshold Severity Level

The Tivoli Enterprise Console warehouse pack does not use this table.

Component events

The following section describes the component events.

Event Type

Table 15. Event Type (TWG.EventTyp Table)
EventTyp_ID EventTyp_Nm MSrc_Cd EventTyp_Ds *
Notes:
  1. * This column is translated
  2. The following EventTyp_Nm values are loaded by the central data warehouse ETL when it is run, not when the Tivoli Enterprise Console is installed:
    • TEC_Start
    • TEC_Notice
    • TEC_Error
1 Attribute Update EVENTS This event represents an update to an existing event attribute(s).
2 Repeat Count EVENTS This event represents an update to the initial Repeat_cnt in the Event Table.
3 TEC_Start EC2
4 TEC_Notice EC2
5 TEC_Error EC2

Event

Table 16. Event (TWG.Event Table)
Event
_ID
Event
Typ
_ID
Event_
DtTm
Tm
Sum_Cd
MSrc_
Cd
Repeat
_Cnt
Centr_
Cd
Cust
_ID
Event_
Corr_ID
Event_
Corr_Val
1 3 2004-02-04-17:32:04.000000 P EC2 0 CDW 1 NULL 1-1-1075915924
2 5 2004-02-04-17:32:21.000000 P EC2 0 CDW 1 NULL 1-1-1075915941
3 4 2004-02-04-17:32:22.000000 P EC2 0 CDW 1 NULL 1-1-1075915942
4 2 2004-02-04-17:35:05.000000 P EC2 0 CDW 1 NULL 1-1-1075915924
5 1 2004-02-04-17:36:56.000000 P EC2 2 CDW 1 NULL 1-1-1075915942

Event Attribute

Table 17. Event Attribute (TWG.EventAttr Table)
Event_ID EventAttr_Id EAttrTyp_Cd MSrc_Cd EventAttr_Val
1 1 EC2_ACL EC2 [admin]
1 2 EC2_CREDIBILITY EC2 1
1 3 EC2_DATE_EVENT EC2 Feb 04 11:32:04 2004
1 4 EC2_HOSTNAME EC2 ibmuser.ibm.com
1 5 EC2_MESSAGE EC2 TEC Event Server Initialized
1 6 EC2_MESSAGE_
INDEX
EC2 0
1 7 EC2_NUMBER_OF_
ACTIONS
EC2 0
1 8 EC2_SEVERITY EC2 Harmless
1 9 EC2_SOURCE EC2 TEC
1 10 EC2_STATUS EC2 Open
1 11 IP_HOSTNAME EC2 ibmuser.ibm.com
2 12 EC2_ACL EC2 [admin]
2 13 EC2_CREDIBILITY EC2 1
2 14 EC2_DATE_EVENT EC2 Feb 04 11:32:21 2004
2 15 EC2_HOSTNAME EC2 ibmuser.ibm.com
2 16 EC2_MESSAGE EC2 TEC encountered error processing rule xyz
2 17 EC2_MESSAGE_
INDEX
EC2 0
2 18 EC2_NUMBER_OF_
ACTIONS
EC2 0
2 19 EC2_SEVERITY EC2 Warning
2 20 EC2_SOURCE EC2 TEC
2 21 EC2_STATUS EC2 Open
2 22 EC2_HOSTNAME EC2 ibmuser.ibm.com
3 23 EC2_ACL EC2 [admin]
3 24 EC2_CREDIBILITY EC2 1
3 25 EC2_DATE_EVENT EC2 Feb 04 11:32:22 2004
3 26 EC2_HOSTNAME EC2 ibmuser.ibm.com
3 27 EC2_MESSAGE_
INDEX
EC2 0
3 28 EC2_NUMBER_OF_
ACTIONS
EC2 0
3 29 EC2_SEVERITY EC2 Warning
3 30 EC2_SOURCE EC2 TEC
3 31 EC2_STATUS EC2 Open
3 32 IP_HOSTNAME EC2 ibmuser.ibm.com
5 33 EC2_STATUS EC2 Closed
5 34 EC2_DURATION EC2 181

Event Attribute Type

Table 18. Event Attribute Type (TWG.EAttrTyp Table)
EAttrTyp_Cd EAttrTyp_Nm * MSrc_Cd
* This column is translated
IP_HOSTNAME Fully Qualified Hostname EVENTS
EC2_ACL Tivoli Enterprise Console Authorization Roles EC2
EC2_ADAPTER_HOST Tivoli Enterprise Console Adapter Host EC2
EC2_ADMINISTRATOR Tivoli Enterprise Console Administrator EC2
EC2_CREDIBILITY Tivoli Enterprise Console Credibility EC2
EC2_DURATION Tivoli Enterprise Console Duration EC2
EC2_DATE_EVENT Tivoli Enterprise Console Date EC2
EC2_HOSTNAME Tivoli Enterprise Console Hostname EC2
EC2_MESSAGE Tivoli Enterprise Console Message EC2
EC2_MESSAGE_CATALOG Tivoli Enterprise Console Message Catalog EC2
EC2_MESSAGE_INDEX Tivoli Enterprise Console Message Index EC2
EC2_NUMBER_OF_
ACTIONS
Tivoli Enterprise Console Number of Tracked Actions EC2
EC2_ORIGIN Tivoli Enterprise Console Origin EC2
EC2_SERVER_HANDLE Tivoli Enterprise Console Server Handle EC2
EC2_SEVERITY Tivoli Enterprise Console Severity EC2
EC2_SOURCE Tivoli Enterprise Console Source EC2
EC2_STATUS Tivoli Enterprise Console Status EC2
EC2_SUB_ORIGIN Tivoli Enterprise Console Sub Origin EC2
EC2_SUB_SOURCE Tivoli Enterprise Console Sub Source EC2

Event Group

Table 19. Event Group (TWG.EGrp Table)
EGrp_Cd EGrpTyp_Cd EGrp_Parent_Cd *EGrp_Nm
* This column is translated
EC2EVT TIVOLI NULL Contains Tivoli Enterprise Console events

Event Group Member

Table 20. Event Group Member (TWG.EGrpMbr Table)
EGrp_Cd EGrpTyp_Cd EventTyp_ID
EC2EVT TIVOLI 1
EC2EVT TIVOLI 2
EC2EVT TIVOLI 3
EC2EVT TIVOLI 4
EC2EVT TIVOLI 5

Event Group Type

Table 21. Event Group Type (TWG.EGrpTyp Table)
EGrpTyp_Cd *EGrpTyp_Nm
* This column is translated
TIVOLI Event Group for Tivoli Products

Event Type Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Event Relationship

Table 22. Event Relationship (TWG.EventReln Table)
Event_Source_ID Event_Target_ID RelnTyp_Cd MSrc_Cd
5 1 UPDATE EC2
4 3 UPDATE EC2
2 3 CAUSES EC2

Component-Event Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Event Rule Relationship

Table 23. Event Rule Relationship (TWG.ERelnRul Table)
ETyp_Source_ID ETyp_Target_ID RelnTyp_Cd ERul_Strt_DtTm ERul_End_DtTm
1 3 UPDATE 2004-02-04-11:35:05.000000 9999-01-01-00.00.00.00
2 4 UPDATE 2004-02-04-11:36:56.000000 9999-01-01-00.00.00.00
2 3 UPDATE 2004-02-04-11:35:05.000000 9999-01-01-00.00.00.00
1 4 UPDATE 2004-02-04-11:36:56.000000 9999-01-01-00.00.00.00
1 5 UPDATE 2004-02-04-11:32:22.000000 9999-01-01-00.00.00.00
2 5 UPDATE 2004-02-04-11:32:22.000000 9999-01-01-00.00.00.00
2 3 CAUSES 2004-02-04-11:32:21.000000 9999-01-01-00.00.00.00

Component-Event Rule Relationship

The Tivoli Enterprise Console warehouse pack does not use this table.

Helper tables

The Tivoli Enterprise Console warehouse pack does not use helper tables.

Exception tables

The Tivoli Enterprise Console warehouse pack does not use exception tables.

Incremental extraction

The Tivoli Enterprise Console warehouse pack supports incremental extraction. For more information about incremental extraction, see Extraction control (table Extract_Control).

Data mart schema information

The following sections contain the definition of star schemas, metric dimension tables, and data marts provided with the warehouse pack. This Tivoli Enterprise Console warehouse pack uses one star schema for all of the reports. The following sections contain the definition of the star schema. This chapter is intended primarily for report designers and warehouse pack creators. For information about reports, see Reports.

Although event correlation relationship information is stored in the central data warehouse, this information is not inserted into the Tivoli Enterprise Console 3.9 data mart.

Data mart EC2 Event Data Mart

This data mart uses the EC2 event star schema

Star schema

Before using this section, read about the star schemas in Enabling an Application for Tivoli Data Warehouse. That document defines the content of each table and explains the relationships between the tables in this document.

The warehouse pack provides the following star schemas.

Event star schema

The following table defines the star schema.

Description of star schema (in IWH_STARSCHEMA)
Name of fact tables
  • EC2.F_EVENT_PIT
  • EC2.F_EVENT_MSG
  • EC2.F_EVENT_ACL
Name of metric dimension table
  • EC2.D_EVTTYP_METRIC
Name of other dimension tables
  • EC2.D_SEVERITY
  • EC2.D_STATUS

The following data mart tables are used to create all of the predefined reports:

Fact table EC2.F_EVENT_PIT table

The EC2.F_EVENT_PIT table contains all of the events and base event Tivoli Enterprise Console attribute information for all events that are stored in the central data warehouse, except the acl and message attributes.

Table 24. EC2.F_EVENT_PIT table
Column name Data type Description

Event_ID

BIGINT

This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse.

EventTyp_ID

INTEGER

This is a foreign key relationship to the EC2.D_EVTTYP_METRIC table. It references the event class of the event.

EventStatus_ID

INTEGER

This is a foreign key relationship to the EC2.D_STATUS table. It references the event status.

EventSev_ID

INTEGER

This is a foreign key relationship to the EC2.D_SEVERITY table. It references the event severity.

Server_ID

INTEGER

Tivoli Enterprise Console server handle of the event.

Event_DtTm

TIMESTAMP

This is the time the original event occurred.

Repeat_Cnt

INTEGER

Repeat count of the event.

Source

VARCHAR(128)

Base attribute of Tivoli Enterprise Console event

Origin

VARCHAR(128)

Base attribute of Tivoli Enterprise Console event

Hostname

VARCHAR(255)

Base attribute of Tivoli Enterprise Console event

Adapter_Host

VARCHAR(255)

Base attribute of Tivoli Enterprise Console event

Administrator

VARCHAR(128)

Base attribute of Tivoli Enterprise Console event

Date_Event

VARCHAR(30)

Base attribute of Tivoli Enterprise Console event

Duration

DOUBLE

Base attribute of Tivoli Enterprise Console event

Msg_Index

INTEGER

Base attribute of Tivoli Enterprise Console event

Num_Actions

INTEGER

Base attribute of Tivoli Enterprise Console event

Credibility

INTEGER

Base attribute of Tivoli Enterprise Console event

Sub_Origin

VARCHAR(128)

Base attribute of Tivoli Enterprise Console event

Sub_Source

VARCHAR(128)

Base attribute of Tivoli Enterprise Console event

Msg_Catalog

VARCHAR(64)

Base attribute of Tivoli Enterprise Console event

Fqhostname

VARCHAR(255)

Base attribute of Tivoli Enterprise Console event

Centr_Cd

CHAR(6)

Center from where original event came.

Cust_ID

INTEGER

Customer from where original event came.

The EC2.F_Event_MSG table contains all of the messages for the events that are contained in the EC2.F_EVENT_PIT table.

Table 25. EC2.F_EVENT_MSG table
Column name Data type Description
Event_ID BIGINT

This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse.

MSG VARCHAR(3500)

Base attribute of Tivoli Enterprise Console event

The EC2.F_Event_ACL table contains all of the access control lists (ACLs) for the events that are contained in the EC2.F_EVENT_PIT table.

Table 26. EC2.F_EVENT_ACL table
Column name Data type Description
Event_ID BIGINT

This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse.

ACL VARCHAR(3500)

Base attribute of Tivoli Enterprise Console event

Metric dimension table

This section describes the metric dimension table that is used by the event star schema in the warehouse pack.

The EC2.D_EVTTYP_METRIC table contains the event types for each event class in the EC2.F_EVENT_PIT table. These event types are dynamically loaded into the central data warehouse by the central data warehouse ETL. The event type is the same as the Tivoli Enterprise Console event class in the Tivoli Enterprise Console event database.

Table 27. EC2.D_EVTTYP_METRIC table
Column name Data type Description

EventTyp_ID

INTEGER

This is the internal central data warehouse identifier for the event type, or Tivoli Enterprise Console event class.

EventTyp_Nm

VARCHAR(254)

This is the event type ( event class ) name.

Dimension tables

The following sections describe the dimension tables (other than metric dimension tables) used by the star schemas in the warehouse pack.

Dimension table EC2.D_STATUS

The EC2.D_STATUS table contains the status for each of the events in the EC2.F_EVENT_PIT table. These statuses are loaded dynamically by the central data warehouse ETL. The following default status values that are shipped with the Tivoli Enterprise Console product are loaded by the EC2_m05_ETL2_Initialization_Process process:

Usage Notes:
  1. The EventStatus_ID is not the same value as the enumerated field in the Tivoli Enterprise Console event database. The numbers are different because Tivoli Enterprise Console event database values are not stored in the central data warehouse.
  2. The EC2_m05_ETL2_Initialization_Process process loads the base statuses and assigns a number to them to enable sorting in the reports. Any new statuses that you add receive an incrementing number and might not be in the order you expect. The table contains the translated strings for nine languages. Any statuses that you add have the same value in each field.
Table 28. EC2.D_STATUS table

EventStatus_ID

INTEGER

This is an integer value that represents the status of the event. This is used as a foreign key relationship by the EC2.F_EVENT_PIT table to capture the appropriate translated value for the status.

StatusNm_En

VARCHAR(255)

This is the English status value.

StatusNm_De

VARCHAR(255)

This is the German status value.

StatusNm_Es

VARCHAR(255)

This is the Spanish status value.

StatusNm_Fr

VARCHAR(255)

This is the French status value.

StatusNm_It

VARCHAR(255)

This is the Italian status value.

StatusNm_Ja

VARCHAR(255)

This is the Japanese status value.

StatusNm_Ko

VARCHAR(255)

This is the Korean status value.

StatusNm_Pt

VARCHAR(255)

This is the Brazilian Portuguese status value.

StatusNm_CN

VARCHAR(255)

This is the simplified Chinese status value.

StatusNm_TW

VARCHAR(255)

This is the traditional Chinese status value.

Dimension table EC2.D_SEVERITY

The EC2.D_SEVERITY table contains all of the severities for the events that stored in the EC2.F_EVENT_PIT table. These severities are dynamically loaded by the central data warehouse ETL; however, the severities are rearranged, so that proper sorting can be accomplished by the reports.

Usage Notes:
  1. The EventSev_ID is not the same value as the enumerated field in the Tivoli Enterprise Console event database. The numbers are different because Tivoli Enterprise Console event database values are not stored in the central data warehouse.
  2. The EC2_m05_ETL2_Initialization_Process process loads the base severities and assigns a number to them to enable sorting in the reports. Any new severities that you add receive an incrementing number and might not be in the order you expect. The table contains the translated strings for nine languages. Any severities that you add have the same value in each field. The following default severity values, listed in order of increasing severity, are shipped with the Tivoli Enterprise Console product and are loaded by the EC2_m05_ETL2_Initialization_Process process:
Table 29. EC2.D_SEVERITY table
Column name Data type Description

EventSev_ID

INTEGER

This is an integer value that represents the severity of the event. This is used as a foreign key relationship by the EC2.F_EVENT_PIT table to capture the appropriate translated value for the severity.

SevNm_En

VARCHAR(255)

This is the English severity value.

SevNm_De

VARCHAR(255)

This is the German severity value.

SevNm_Es

VARCHAR(255)

This is the Spanish severity value.

SevNm_Fr

VARCHAR(255)

This is the French severity value.

SevNm_It

VARCHAR(255)

This is the Italian severity value.

SevNm_Ja

VARCHAR(255)

This is the Japanese severity value.

SevNm_Ko

VARCHAR(255)

This is the Korean severity value.

SevNm_Pt_BR

VARCHAR(255)

This is the Brazilian Portuguese severity value.

SevNm_Zh_CN

VARCHAR(255)

This is the simplified Chinese severity value.

SevNm_Zh_TW

VARCHAR(255)

This is the traditional Chinese severity value.

Appendix. Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY  10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX  78758  U.S.A

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

This publication documents no intended Programming Interfaces that allow the customer to write programs to obtain services of IBM Tivoli Enterprise Console.

Trademarks

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

IBM, the IBM logo, Tivoli, the Tivoli logo, AIX(R), DB2, DRDA, Informix, Tivoli Enterprise Console, and TME(R) are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.

Intel(TM), the Intel Inside logos, MMX(TM), and Pentium(R) are trademarks of Intel Corporation in the United States, other countries, or both.

Microsoft and Windows are registered 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.

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

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

Index

A B C D E F I K L M N P R S T U V W
A B C D E F I K L M N P R S T U V W

[ Top of Page | | Contents | Index ]