![]() |
![]() |
[ Bottom of Page | | Contents | Index ]
Before using this information and the product it supports, read the information in Notices.
This edition applies to Version 3, Release 1 of IBM Tivoli Business Systems Manager and to all subsequent releases and modifications until otherwise indicated in new editions.
This document describes the warehouse pack, version 3.1.0.0 for IBM(R) Tivoli(R) Business Systems Manager, version 3.1. This warehouse pack is created for IBM Tivoli Data Warehouse, Version 1.2.
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:
This section lists publications in the Tivoli Data Warehouse and the Tivoli Business Systems Manager product libraries and related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.
The Tivoli Data Warehouse Documentation CD, LK3T-8111, provides all documents in the Tivoli Data Warehouse library, except for Enabling an Application for Tivoli Data Warehouse, GC32-0745. Enabling an Application for Tivoli Data Warehouse is available only on the Tivoli Data Warehouse Support Web site. All documents are available in English; selected documents are available in other languages.
The following documents are available in the Tivoli Data Warehouse library:
The Tivoli Data Warehouse information center contains the documents from the Tivoli Data Warehouse library in PDF and HTML formats. The information center is available from the Tivoli Software Information Center Web site.
The following publications are in the IBM Tivoli Business Systems Manager library:
This document is written for network planners, system designers, systems administrators, and others who are responsible for planning and implementing the product.
This document is written for system administrators and others who are responsible for installing and configuring Tivoli Business Systems Manager.
This document is written for operators and administrators.
This document is written for system administrators and others who perform administrative tasks for Tivoli Business Systems Manager.
This document is written for system programmers.
This document is written for system administrators and others who run commands and scripts for Tivoli Business Systems Manager.
This document is written for system programmers, network planners, operations managers, system designers, system administrators, network operators, and others who need message information for Tivoli Business Systems Manager.
This document is written for system administrators and others who perform diagnostic tasks for Tivoli Business Systems Manager.
This document is written for administrators and others who plan for and install the warehouse pack, use and maintain the warehouse pack and its reports, or create new reports.
An index is provided for searching the Tivoli Business Systems Manager library. If you have Adobe Acrobat on your system, you can use the Search command to locate specific text in the library. For more information about using the index to search the library, see the online help for Acrobat.
The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site:
http://www.ibm.com/software/tivoli/library/
Access the glossary by clicking the Glossary link on the left pane of the Tivoli software library window.
The documentation CD contains the publications that are in the product library. The format of the publications is PDF and HTML.
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. Access the Tivoli software information center by first going to the Tivoli software library at the following Web address:
Scroll down and click the Product manuals link. In the Tivoli Technical Product Documents Alphabetical Listing window, click the Tivoli Business Systems Manager link to access the product library at the Tivoli software information center.
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:
In other countries, see the following Web site for a list of telephone numbers:
http://www.ibm.com/software/tivoli/order-lit/
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. With this product, you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface.
For information about installing the Tivoli Business Systems Manager product using the built-in screen reader, see the IBM Tivoli Business Systems Manager: Installation and Configuration Guide. For information about the shortcut keys that can be used with the Tivoli Business Systems Manager console, see the Accessibility appendix in IBM Tivoli Business Systems Manager: Introducing the Consoles.
For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need:
For more information about these three ways of resolving problems, see Support information.
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 Business Systems Manager:
news://news.software.ibm.com/ibm.software.tivoli.business-systems-manager
IBM Tivoli Enterprise Console(R):
news://news.software.ibm.com/ibm.software.tivoli.enterprise-console
IBM Tivoli Service Level Advisor:
news://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
IBM Tivoli Switch Analyzer:
news://news.software.ibm.com/ibm.software.tivoli.switch-analyzer
IBM Tivoli NetView(R) for UNIX(R) and IBM Tivoli NetView for Windows(R):
news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows
IBM Tivoli NetView for z/OS(R):
news://news.software.ibm.com/ibm.software.netview
This guide uses several conventions for special terms and actions and for commands and paths that vary according to the operating system.
This guide uses the following typeface conventions:
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.
For a list of terms and definitions for Tivoli and other IBM products, refer to the IBM terminology Web site:
http://www.ibm.com/ibm/terminology/
For brevity and readability, the term Tivoli NetView for z/OS refers to both the Tivoli NetView for z/OS product and the Tivoli NetView for OS/390(R) product.
The following sections provide an overview of the IBM Tivoli Data Warehouse and IBM Tivoli Business Systems Manager Warehouse Pack, Version 3.1.0.0 products.
Tivoli Data Warehouse provides the infrastructure for the following processes:
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.
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 which 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 pack.
The ETLs are typically scheduled to run periodically, usually during non-peak hours. If an ETL encounters data that it cannot correctly transform, it creates an entry in an exception table. For more information about exception tables, see Exception tables.
Tivoli Business Systems Manager is an enterprise management product that captures resource states and the events for those resources. The resource state information can be formatted as the input data for the IBM Tivoli Service Level Advisor. The integration of the Tivoli Business Systems Manager with the Tivoli Data Warehouse stores the data in the Tivoli Data Warehouse databases using the Tivoli Business Systems Manager Pack, Version 3.1.0.0. The Tivoli Service Level Advisor extracts the data for the service level agreement analysis from the Tivoli Data Warehouse databases. Tivoli Business Systems Manager Pack, Version 3.1.0.0 provides the central data warehouse ETL for the business systems and executive dashboard service resources, and the measurement data for the business systems. It extracts the data from the Tivoli Business Systems Manager database, maps and transforms the data model from the Tivoli Business Systems Manager to the Tivoli Data Warehouse, calculates the measurements, and stores the resulted data in the Tivoli Data Warehouse database (in the central data warehouse schema).
Tivoli Business Systems Manager Pack, Version 3.1.0.0 uses the Tivoli Data Warehouse architecture. It uses the OBJECT' ODBC data source for the DB2 warehouse GTM_OBJECT_Source source and the TWH_CDW ODBC data source for the DB2 warehouse GTM_TWH_CDW_Target target. The twh_objs table in the Tivoli Business Systems Manager object database is the connection table used for the GTM_OBJECT_Source warehouse source. The GTM.CENTR_LOOKUP and GTM.CUST_LOOKUP tables in the Tivoli Data Warehouse database are the connection tables used for the GTM_TWH_CDW_Target warehouse target.
The resource classes in the Tivoli Business Systems Manager database refer to component types in the Tivoli Data Warehouse database. Examples of resource classes and the common component types with which they correlate are shown in Table 1.
Tivoli Business Systems Manager resource class | Tivoli Data Warehouse component type |
---|---|
Business System | Business System |
Executive Dashboard Service | Service |
For detailed information about the executive dashboard service class definition, configuration, and usage, see the IBM Tivoli Business Systems Manager: Administrator's Guide. The Tivoli Business Systems Manager central data warehouse ETL provides the measurement data for all the business systems.
The business system and executive dashboard service resources in the Tivoli Business Systems Manager database are created in the Tivoli Data Warehouse database as components in the TWG.COMP table. The parent-child relationships of the business systems are loaded in TWG.COMPRELN table. The following information is loaded or updated in the Tivoli Data Warehouse databases:
One business system in the Tivoli Business Systems Manager database refers to one component in the Tivoli Data Warehouse database.
Dragging and dropping a business system in the Tivoli Business Systems Manager product creates a business system shortcut. In the Tivoli Business Systems Manager database, the business system shortcut has the same children as the source resource from which it was copied. The specified link type (a business system logical link) enables this function. In Tivoli Data Warehouse, there is no distinction for the source resource with the business system shortcuts. They are all modeled as components of the BUSINESS_SYSTEM component type. The relationship of the business system shortcuts with the source business system in the Tivoli Business Systems Manager is used to create the parent and child relationships of the business system shortcuts with the children of the source business system in the Tivoli Data Warehouse database.
The relationship of business systems is modeled differently in Tivoli Data Warehouse than in Tivoli Business Systems Manager for business systems shortcuts. The following example shows the children of the business system shortcut Bank 1 being resolved by a LOBL link type in Tivoli Business Systems Manager. In Tivoli Data Warehouse, the central data warehouse ETL creates a direct link.
Data Centers (business system) Eastern Complex (business system) ---Original--- Bank 1 (business system) CICS A (business system resource) CICS B (business system resource) Western Complex (business system) Bank 1 (business system shortcut) ---Dragging and Dropping--- CICS A (business system resource) CICS B (business system resource)
When the business systems from the Tivoli Business Systems Manager program are loaded into the Tivoli Data Warehouse program, the business system information is saved in the Tivoli Data Warehouse database, as described in Table 2.
Tivoli Business Systems Manager | Tivoli Data Warehouse |
---|---|
Object name | Component name |
Class ID | GTM_CID attribute |
Ctime | Component start date |
Ctime | Component start time |
Object ID | GTM_ID attribute |
Resource type | GTM_RTYPE attribute |
The service components are modeled differently from the business systems in the Tivoli Data Warehouse database. The executive dashboard service resource information is saved in the Tivoli Data Warehouse database, as described in Table 3.
Tivoli Business Systems Manager | Tivoli Data Warehouse |
---|---|
Object name | User label attribute |
_ServiceID | Component name |
_ServiceGUID | NAME_GUID attribute |
Ctime | Component start date |
Ctime | Component start time |
Class ID | GTM_CID attribute |
Object ID | GTM_ID attribute |
*_Flag of linked business system | GTM_Enable |
* When an executive dashboard service is created, it is enabled in Tivoli Data Warehouse and there is no record for the GTM_Enable attribute. Clearing the Service check box in the Tivoli Business Systems Manager executive dashboard property page changes the value for the GTM_Enable attribute of the Service component in the Tivoli Data Warehouse to 0. When the Service is marked as a service again (by selecting the Service check box in the Tivoli Business Systems Manager executive dashboard property page), then the GTM_Enable attribute value of the Service component in the Tivoli Data Warehouse database is set to 1. |
Like the parent and child (PCHILD) relationship between the service and the sub-service, the SUPPRT (Support) relationship of the service with the business system in the Tivoli Data Warehouse is also created based on the link type, executive dashboard service link, from Tivoli Business Systems Manager.
When a Tivoli Business Systems Manager business system is renamed, a new NAME attribute for the business system component is inserted with the new name as the CompAttr_Val value in the TWG.CompAttr table of the TWH_CDW database. When an executive dashboard service resource is renamed in Tivoli Business Systems Manager or in the executive dashboard list, a new USER_LABEL attribute for the service component is inserted with the new display name as the CompAttr_Val value in the TWG.CompAttr table of the TWH_CDW database. The original attribute is expired by the Tivoli Data Warehouse trigger or the Tivoli Business Systems Manager central data warehouse ETL.
When an executive dashboard service or business system is deleted from the Tivoli Business Systems Manager database, the component, attributes, and relationships in the central data warehouse database are expired in the next run of the Tivoli Business Systems Manager central data warehouse ETL. The state changes of all business systems are provided for the measurements using the state transition matrix. The alert states or resource states in the Tivoli Business Systems Manager are mapped into the Tivoli Service Level Advisor availability measurement types, as shown in Table 4.
Object state in Tivoli Business Systems Manager | Measurement type in Tivoli Service Level Advisor |
---|---|
Green | Available |
Yellow | Degrading |
Red | Unavailable |
In maintenance | Unmanaged |
Owned (Red)* | Repairing |
Unknown | Unknown |
* The Owned (Red) state is only recorded for the time period when the resource has the ownership note due to a Red event. When the resource has an ownership note because of a Yellow event, the ETL transfers it as either Degrading or Available, based on the alert state of the resource. |
Figure 2 presents a high-level view of the Tivoli Business Systems Manager central data warehouse ETL processes that make the Tivoli Business Systems Manager data available in the Tivoli Data Warehouse database.
The Tivoli Business Systems Manager 3.1.0.0 Warehouse Pack includes the following tasks:
Tivoli Business Systems Manager central data warehouse ETL also provides processes for the following tasks:
Tivoli Business Systems Manager Pack, Version 3.1.0.0 does not provide predefined reports.
This section describes the installation and configuration of the warehouse pack.
Before installing the warehouse pack for Tivoli Business Systems Manager 3.1.0.0 Warehouse Pack, install the following software:
If the previous version of the Tivoli Business Systems Manager Warehouse Pack was installed, check the version number. If the version of the Tivoli Business Systems Manager Warehouse Pack is not 2.1.1, you must upgrade to Tivoli Business Systems Manager Warehouse Pack version 2.1.1 and complete the migration procedure before installing Tivoli Business Systems Manager 3.1 Warehouse Pack. This warehouse pack supports central data warehouses on DB2 Universal Database for z/OS and OS/390, DB2 Universal Database for Windows and UNIX systems, or both. Tivoli Business Systems Manager uses the twh_install_props.cfg file to specify z/OS, distributed, or both.
Refer to the Tivoli Data Warehouse Release Notes and the Tivoli Business Systems Manager: Installation and Configuration Guide for the specific information about hardware prerequisites, database and operating system support, and product prerequisites. For late-breaking news about prerequisites, refer to the following IBM Software Support Web site: http://www.ibm.com/software/sysmgmt/products/support/.
If you are using the failover function provided by the Tivoli Business Systems Manager version 3.1 product, when the Tivoli Business Systems Manager database server is moved from one server to another, the following steps are required for completion in the Tivoli Data Warehouse control server:
The Tivoli Business Systems Manager version 3.1.0.0 warehouse pack does not support configuration using the remote warehouse agent on an AIX(R) server. The measurement data is not automatically corrected for the deviation caused by turning the daylight savings time on or off. For example, if the central data warehouse ETL runs at 10:00 p.m. April 10 and the time is moved forward one hour at 2:00 am April 11, when the central data warehouse ETL runs at 10:00 p.m. on April 11, the measurement data from at 10:00 p.m. April 10 to 2:00 am April 11 is not accurate. This can be corrected by configuring the GTM_CHANGE_TIME system variable in the Tivoli Business Systems Manager MSSQL query analyzer as shown in the following example:
_SetSystemConfiguration 'ROOT', 0, 'TWH', 'GMT_CHANGE_TIME', <date time>, DATETIME'
In this example, <date time> is the date and time that you change. The format is YYYY-MM-DD HH:MM:SS.xxx, where the xxx is fractions of seconds. For example: 2004-09-01 11:00:00.000' changes the date to September 1, 2004 and the time to 11:00 a.m. This value must be set before the time change occurs.
Ensure that you have sufficient space in the Tivoli Data Warehouse databases for the historical data collected by the warehouse pack. To estimate how much space is required for the warehouse pack, complete the worksheets in Table 5, Table 6, and Table 7. Refer to the following information and Installing and Configuring Tivoli Data Warehouse.
Component type | Count |
---|---|
Business system | |
Service | |
Total |
Use the following queries to obtain these counts from the Tivoli Business Systems Manager object database:
SELECT COUNT(*) FROM LineOfBusiness_V WHERE deleted = 0
SELECT COUNT(*) FROM EVService_V WHERE deleted = 0
Measurement matrix | Number of components | Number of MsmtTyps | Measurements per day |
---|---|---|---|
State transition | 6 |
In Table 6, the following information is to be determined:
<Number of components> *10% * <Number of times ETL runs per day>If more than 10% of your business system resources change state daily, adjust the percentage from 10 to the correct percentage.
Database | Fixed storage requirement | Variable storage requirement | Estimated total storage (fixed + variable) |
---|---|---|---|
Central data warehouse | 110 MB | ||
Control database | 10 MB | 0 | 10 MB |
The storage usage for the control database does not change much across environments. The fixed values are shown in Table 7. The storage usage for the central data warehouse varies according to your environment. The fixed storage requirement for the central data warehouse is the sum of the storage usage of components and measurements. The storage size used for the components can be obtained using the following formula:
<Total Number of components from component list> * 1.3(KB)
The storage size used for the measurement data can be obtained using the following formula:
<Measurement per day from measurement list> * 0.1(KB) * <Number days of measurement data kept in Tivoli Data Warehouse>
The fixed storage size can be obtained using the following formula:
<Total Number of components from component list> * 1.3(KB) + <Measurement per day from measurement list> * 0.1(KB) * <Number days of measurement data kept in Tivoli Data Warehouse>
The variable storage requirement for the central data warehouse varies with the your activities. Use the following formula to calculate the variable storage:
(<Number of new components for each ETL run> + <Number of renamed components for each ETL run> + <Number of deleted components for each ETL run>) * 1.3(KB) + <Total Business System Components> * <percentage of state changes> * 0.1 (KB)
Before running the warehouse pack installation program, make sure that the system has all prerequisite products installed correctly. If you have the Tivoli Business Systems Manager Warehouse Pack 2.1.1 installed and you have run the migration process to update your data, uninstall the Tivoli Business Systems Manager Warehouse Pack 2.1.1 .
To ensure that the TCP/IP network library is used for the source database connection, install the Microsoft SQL Server client on the Tivoli Data Warehouse control server, and create an alias using the Microsoft SQL server client network utility tool with the parameters shown in Table 8.
Parameter | Value |
---|---|
Server alias | Short computer name of the Tivoli Business Systems Manager database server |
Network libraries | TCP/IP |
Server name | Short or fully-qualified name of the Tivoli Business Systems Manager database server |
Install the warehouse pack, as described in Installing and Configuring Tivoli Data Warehouse, using the installation properties file twh_install_props.cfg. The installation properties file, twh_install_props.cfg, is located on the Tivoli Business Systems Manager, version 3.1 CD2 in the <etl/gtm> directory.
The default data source names for the ODBC connections are <AVA>_TWH_CDW_Source and <AVA>_TWH_Mart_target.
After you install the warehouse pack, perform the following steps:
SELECT * FROM TWG.CUR_COMP WHERE COMPTYP_CD = 'TBSM_LOB'
DB2 connect to TWH_CDW user <user name> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 90 WHERE MSRC_CD = 'GTM'Promote the GTM_c05_s010_Rebuild_ExtCTRL step in the GTM_c05_Init_Process process to test mode and then run the test manually. After the initialization process completes successfully, reset the PMsmtC_Age_In_Days value in the DB2 command window on the DB2 data warehouse control server using the following command:
DB2 connect to TWH_CDW user <user name> using <password> DB2 UPDATE TWG.Prune_Msmt_Control SET PMsmtC_Age_In_Days = 180 WHERE MSRC_CD = 'GTM'
This migration process is designed to migrate all the resources loaded with the Tivoli Business Systems Manager Pack, version 2.1.1 to the resources used in the Tivoli Business Systems Manager Pack, version 3.1.0.0 The Tivoli Business Systems Manager Pack, version 3.1.0.0 uses the common component type BUSINESS_SYSTEM for the Tivoli Business Systems Manager business system resource class (instead of the TBSM_LOB component type in the TWH_CDW database that was used in the previous release).
The measurement matrix of the Tivoli Business Systems Manager business systems is changed from a percentage (in hours) to the state transition measurement matrix. Due to these changes, the following actions are performed in this migration:
For the Tivoli Business Systems Manager Warehouse Pack 3.1.0.0. and Tivoli Service Level Advisor to function correctly, perform the following procedures:
The data in the GTM.MIGR_COPM table is used to perform the migration in the Tivoli Service Level Advisor database for the resource changes. The branch value mapping rules are described in the APAR IY48333-13 document.
Uninstall the warehouse pack as described in the Installing and Configuring Tivoli Data Warehouse guide. When the warehouse pack is uninstalled, all the staging and working tables in the GTM schema are removed, but the data in the central data warehouse remains and is still usable by other applications.
This section describes maintenance tasks for the warehouse pack.
The GTM_c10_Load_Process process loads the data incrementally using the extraction control in the Tivoli Business Systems Manager database. The GTM_c05_Init_Process and GTM_c15_Migration_Process processes are only run as documented and should not be run regularly.
For common backup procedures, see the Installing and Configuring Tivoli Data Warehouse guide.
Tivoli Business Systems Manager Warehouse Pack, version 3.1.0.0 does not require any special procedure for backing up and restoring databases.
To manage the high volume of measurement data, use the Prune_Msmt_Ctrl table to delete the data that are not needed. The TWG.Prune_Msmt_Log table keeps a history of data deletion. The Tivoli Business Systems Manager measurement data is retained in the TWH_CDW database for 180 days by default. This default value is saved in the PMsmtC_Age_In_Days column of the TWG.Prune_Msmt_Control table. The CDW_c05_Prune_and_Mark_Active process within the CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area controls the deletion. By default, this process runs daily at 6:00 am.
DB2 UPDATE TWG.Prune_Msmt_Control SET PMSMTC_AGE_IN_DAYS = 30 WHERE MSRC_CD = 'GTM' AND TMSUM_CD = 'P'
Measurement data is pruned from the Msmt table based on the age specified in the PMsmtC_Age_In_Days column.
The PMsmtC_Age_In_Days value should be set back to 180 days after completing the post initialization process described in Post installation procedures.
By default, data older than 3 months is pruned when the CDW_c05_Prune_and_Mark_Active process runs. This process is within CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area. By default, this process runs daily at 6:00 a.m.
The extraction control table, as shown in Table 9, 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.
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) |
---|---|---|---|---|---|---|---|---|
ETL1 | MSMT | 2003-01-28-11.36.54.
000000 |
2003-01-29-11.36.54.
000000 |
GTM |
For common problems and solutions, see the Installing and Configuring Tivoli Data Warehouse guide. This section only documents the guidelines and problem determination strategies specific to the Tivoli Business Systems Manager Warehouse Pack. If any of the central data warehouse ETL steps fail, there are three places to get the error messages:
For the further problem determination, use the following utilities:
Tivoli Business Systems Manager Warehouse Pack, version 3.1.0.0 requires the MSSQL network client to be installed on the server where the DB2 warehouse agent is used. You can install either the MSSQL client or the MSSQL network client, though you can use the MSSQL client for debugging. After the Tivoli Business Systems Manager Warehouse Pack, version 3.1.0.0 is installed, the connection should be tested during the installation procedure. If anything changes for the network connectivity after the installation, the following methods can be used to verify the connection:
The following extraction control tables are used in the Object database of Tivoli Business Systems Manager:
To view the data in MSSQL query analyzer use the following code:
SELECT * FROM twh_objs
SELECT * FROM twh_date
The following extraction controls are provided in the Tivoli Data Warehouse database:
Use the following DB2 command to view the data in the Tivoli Data Warehouse database:
SELECT * FROM TWG.EXTRACT_CONTROL WHERE ExtCtl_MSrc_Corr_Cd = 'GTM' SELECT * FROM GTM.Resource
The following stored procedures in the Object database of the Tivoli Business Systems Manager product can be run as diagnostic tools:
These can be run multiple times without effecting the ETL processes.
One subject area, GTM_Tivoli_Business_Systems_Manager_v3.1_Subject_Area, is defined. It contains the following processes:
For performance reasons, Tivoli Business Systems Manager central data warehouse ETL saves the extraction control in both the Tivoli Business Systems Manager and the TWH_CDW databases. It is required to synchronize the extraction controls in the databases before running the usual process. The initialization process is defined to synchronize the extraction controls. The GTM_c05_Init_Process process is defined to change the extraction markers in the Tivoli Business Systems Manager database based on the data in the Tivoli Data Warehouse database for the incremental extraction. The GTM_c10_Load_Process process loads the Tivoli Business Systems Manager resources and measurement data into Tivoli Data Warehouse. The GTM_c15_Migration_Process process is used for the migration of the data loaded with the Tivoli Business Systems Manager version 2.1.1 Warehouse Pack into the Tivoli Data Warehouse. The Tivoli Service Level Advisor migration procedure provides migration for the Tivoli Service Level Advisor definitions.
This process reloads the extraction controls for resources and measurement data in the Tivoli Business Systems Manager application database from the Tivoli Data Warehouse database. Use this process after installing the warehouse pack, applying fixes, or restoring databases to synchronize the extraction controls in the Tivoli Business Systems Manager database.
This process has the following step:
It is used for the new installation of the Tivoli Business Systems Manager warehouse pack and restoration of the databases for the existing Tivoli Business Systems Manager warehouse pack. It is defined to run on demand, as documented. The procedure to synchronize the extraction control during the installation is documented in Post installation procedures.
If you restored either the Tivoli Business Systems Manager or the Tivoli Data Warehouse databases, before you create new business systems and executive dashboard service resources, use the following procedure to synchronize the extraction control for Tivoli Business Systems Manager and Tivoli Data Warehouse:
This process extracts, transforms, and loads the business systems and executive dashboard services information and the measurement data of the BUSINESS SYSTEM components from the Tivoli Business Systems Manager database to the TWH_CDW database. The data is saved in the staging tables in the GTM schema of the TWH_CDW database first, and then the transformed data is loaded from the staging tables into the TWH_CDW database (based on the mapping of the Tivoli Business Systems Manager resources to the Tivoli Data Warehouse components). This process is designed to run incrementally after initialization using the extraction control in Tivoli Business Systems Manager application database.
Run this process after installing the warehouse pack and after running the initialization process. It is scheduled to run at an interval once a day before the Tivoli Service Level Advisor ETL runs, if applicable. All steps run based on the success of the previous steps.
This process has the following steps:
This process is designed for migrations and future improvement. The migration steps require process control in the scripts. The MIGR_CRTL control table is located in the Tivoli Business Systems Manager application database. When the steps are run for the first time, an indicator for the actions is recorded. After the first run, these steps do nothing unless new code with a different indicator is appended in the scripts. The detailed function and step description are documented in the migration instructions or the installation instructions in the readme file of the fix packs for each delivery.
Run this process as described in the migration instructions or the installation instructions in the readme file of the fix packs. This process should run on-demand.
This process has the following steps:
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.
The following sections describe the component configuration.
Table 10 shows the fields of the compTyp table.
This warehouse pack does not use the TWG.Comp_Ext table.
Table 11 shows the fields of the Comp table.
Table 12 shows the fields of the RelnTyp table.
Table 13 shows the fields of the RelnRul table.
Table 14 shows the fields of the CompReln table.
This warehouse pack does not use the TWG.CompTyp_Keyword table.
Table 15 shows the fields of the AttrTyp table.
Table 16 shows the fields of the AttrRul table.
This warehouse pack does not use the TWG.AttrDom table.
Table 17 shows the fields of the CompAttr table.
This warehouse pack does not use the TWG.CTypReln table.
This warehouse pack does not use the TWG.ATypReln table.
The following sections describe the component measurement.
Table 18 shows the fields of the MGrpTyp table.
MGrpTyp_Cd
CHAR(6) |
MGrpTyp_Nm*
VARCHAR(120) |
---|---|
GROUP | Aggregate Types or Group Functions |
TRANS | State Transition Groups |
* This column is translated. |
Table 19 shows the fields of the MGrp table.
Table 20 shows the fields of the MGrpMbr table.
Table 21 shows the fields of the MUnitCat table.
MUnitCat_Cd
CHAR(6) |
MUnitCat_Nm*
CHAR(120) |
---|---|
TM | Time Duration |
* This column is translated. |
Table 22 shows the fields of the MUnit table.
MUnit_Cd
CHAR(6) |
MUnitCat_Cd
CHAR(6) |
MUnit_Nm*
VARCHAR(120) |
---|---|---|
Min | TM | Minutes |
* This column is translated. |
This warehouse pack does not use the TWG.MTypReln table.
This warehouse pack does not use the TWG.TmSum table.
Table 23 shows the fields of the MSrc table.
This warehouse pack does not use the TWG.MSrc_History table.
Table 24 shows the fields of the MsmtTyp table.
Table 25 shows the fields of the MsmtRul table.
CompTyp_Cd
CHAR(17) |
MsmtTyp_ID
INT |
---|---|
BUSINESS_SYSTEM | 1 |
BUSINESS_SYSTEM | 2 |
BUSINESS_SYSTEM | 3 |
BUSINESS_SYSTEM | 4 |
BUSINESS_SYSTEM | 5 |
BUSINESS_SYSTEM | 6 |
Table 26 shows the fields of the Msmt table.
This warehouse pack does not use the TWG.MObj table.
This warehouse pack does not use the TWG.MObjRng table.
This warehouse pack does not use the TWG.SevLvl table.
The following section describes the component events.
This warehouse pack does not use the TWG.EventTyp table.
This warehouse pack does not use the TWG.Event table.
This warehouse pack does not use the TWG.EventAttr table.
This warehouse pack does not use the TWG.EAttrTyp table.
This warehouse pack does not use the TWG.EGrp table.
This warehouse pack does not use the TWG.EGrpMbr table.
This warehouse pack does not use the TWG.EGrpTyp table.
This warehouse pack does not use the TWG.ETypReln table.
This warehouse pack does not use the TWG.EventReln table.
This warehouse pack does not use the TWG.CEReln table.
This warehouse pack does not use the TWG.ERelnRul table.
This warehouse pack does not use the TWG.CERelnRul table.
All the helper tables are created in GTM schema.
Table 27 shows the fields of the MIGR_COMP table.
This table is used for Tivoli Service Level Advisor to migrate the component definition changes from the Tivoli Business Systems Manager Warehouse Pack 2.1.1 to the Tivoli Business Systems Manager Warehouse Pack 3.1.0.0.
The following list describes the columns in Table 27:
This warehouse pack does not use the <exception> tables.
This warehouse pack does not use the <incremental extraction> tables.
This warehouse pack does not provide data marts.
This section describes the following options for obtaining support for IBM products:
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.
IBM provides extensive documentation that can be installed on your local computer 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.
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 Web search. From this topic, you can search a variety of resources including:
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:
To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps:
For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).
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:
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. |
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:
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.
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:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
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 might 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:
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 document 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.
IBM, the IBM logo, AIX, DB2, DB2 Universal Database, developerWorks, eServer, iSeries, Lotus, NetView, OS/390, Passport Advantage, pSeries, Rational, Redbooks, Tivoli, the Tivoli logo, Tivoli Enterprise Console, WebSphere, z/OS, and zSeries are trademarks or registered trademarks of International Business Machines 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.
![]() |
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. |
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
[ Top of Page | | Contents | Index ]