1.- INTRODUCCION

IBM Tivoli Monitoring data collection needs to have the data collection feature installed in the Tivoli Framework. The data collection collects data in the historical database, typically called ITM_DB, using a set of RIM objects. A RIM object is a Tivoli Management Framework resource used to communicate with a relational database. The IBM Tivoli Monitoring data is collected from the Tivoli Management Framework gateway. The gateway collects historical information from the endpoints and stores them locally. Every midnight, it loads the historical data into the ITM_DB using a RIM object called itm_rim_<nodename>. For example, our gateway ibmtiv1 collects data using RIM itm_rim_ibmtiv1.

1. Define the database schema using the files under

$BINDIR/TME/Tmw2k/TDS/rdbcfg; the files are:

cr_db Creating the database

cr_tbl Creating the schema

twh_enabl_update Enabling update for warehouse database

2. Define the RIM object using the wcrtrim command. For our DB2 UDB in the AIX environment, we run the following command:

wcrtrim -v DB2 -h ibmtiv1 -d ITM_DB -u db2inst1 -H /usr/lpp/db2_07_01 -I /home/db2inst1 itm_rim_ibmtiv1

3. Define data collection parameters using the wdmconfig command:

wdmconfig -m ibmtiv1 -D datacollector.db_purge_interval = 40 -D datacollector.rim_name = itm_rim_ibmtiv1

-D datacollector.delay = 1 -D datacollector.sleep_time = 1

The configuration is stored in the file $DBDIR/dmml/.config.

4. Initiate data collection using the wdmcollect command; to initiate collection from endpoint BSM2 every two hours, use the command:

wdmcollect -e BSM2 -s 2

You can see the XML file result under

$DBDIR/dmml/tedw/datacollector.status.

4.8.2 Collecting information from Web Services Courier

Data collected by the IBM Tivoli Monitoring for Transaction Performance can be collected into the historical database hosted by the Web Services Courier. The collection set up is performed using the Web browser interface. Use the following procedure:

1. Use a Web browser and log on to the IBM Tivoli Monitoring for Transaction Performance’s Internet Management Server. Supply the appropriate user ID and password; click Logon.

2. From the portfolio menu, select Historical Data Collection -> Configure Data collection.

3. Set the time that the data collection job will run and load the relational database into the Web Services Courier, then click Save. See Figure 4-55 on page 154.

Figure 4-55 Configure Data collection for Internet Management function

4.8.3 Enabling ETL in Tivoli Data Warehouse

The ETL programs are installed using the Tivoli Data Warehouse installation programs. ETL programs and processes are managed using the IBM DB2 Data Warehouse Center. Data Warehouse Center is launched from the DB2 control center.

You start the DB2 control center using the command db2cc. From the DB2 control center, select Tools -> Data Warehouse Center.

The following steps need to be followed after the ETLs have been installed.

1. Setting up ODBC connection to data sources

– For the DB2 database, use the DB2 Client Configuration Assistant. Issue the command db2cca to start it. Click the Add button to start the Add database wizard. Our DB2 Client Configuration Assistant window is shown in Figure 4-56 on page 155.

Figure 4-56 DB2 Client Configuration Assistant

– For the IBM Tivoli Business Systems Manager Objects database in Microsoft SQL Server, use the ODBC Connection Manager applet under Administrative Tools -> Data Sources (ODBC). The ODBC applet is shown in Figure 4-57.

Figure 4-57 ODBC System DSN list

2. Start DB2 Control Center using the command db2cc. From the DB2 control

Figure 4-58 DB2 Control Center to invoke Data Warehouse Center

3. Enter your DB2 administrator user ID and password. Select the Advanced button and ensure that the control database name is TWH_MD instead of DWCTRLDB. Click OK and then OK again. This is shown in Figure 4-59.

Figure 4-59 Login to Data Warehouse Center

4. From the Data Warehouse Center, expand the Warehouse Sources and Warehouse Targets folders and update all the database definitions.

Right-click each definition and select Properties as shown in Figure 4-60 on page 157.

Figure 4-60 Opening database property

5. Change the database property pages for all the database sources and targets under the folders Warehouse Source and Warehouse Target. Enter the appropriate user ID for the databases. A sample property page for a source database is shown in Figure 4-61.

6. Now expand the Subject Areas folder. It will show the ETL processes. Expand the processes until you reach the specific steps. Right-click and select Schedule as shown in Figure 4-62.

Figure 4-62 Defining schedule

7. Put in the daily schedule with a specific start time. The overview schedule is shown in Figure 4-8 on page 98. Since it is based also on the time estimate in Figure 4-7 on page 98, we will use the schedule in Table 4-10. The table only contains processes necessary for IBM Tivoli Service Level Advisor.

Table 4-10 Time schedule for collection process

The schedule definition dialog is shown in Figure 4-63 on page 159.

Process name Start time

AMX_c05_ETL1_Process 00:20 BWM_c10_Load_Warehouse_Process 23:40 DYK_m05_Populate_Registration_Datamart_Process 01:00 DYK_m10_Populate_Measurement_Datamart_Process 01:30 GTM_c05_LOBState_Process 23:00

Figure 4-63 Schedule definition dialog

8. Back in the ETL processes, now we can promote the mode of processing to Production. Setting the mode to Production means that all the changes are final and the ETL will be processed by schedule. The promote menu is shown in Figure 4-64 on page 160.

Figure 4-64 Promoting ETL process