Conceptos básicos de HTML

Here we describe the installation procedures of IBM Tivoli Monitoring for Web Infrastructure Warehouse modules, also known as IBM Tivoli Monitoring for Web Infrastructure ETLs. They are:

򐂰 IBM Tivoli Monitoring for Web Infrastructure: Apache HTTP Server Warehouse ETL.

򐂰 IBM Tivoli Monitoring for Web Infrastructure: iPlanet Server Warehouse ETL.

򐂰 IBM Tivoli Monitoring for Web Infrastructure: Internet Information Server Warehouse ETL.

򐂰 IBM Tivoli Monitoring for WebSphere Application Server Warehouse ETL.

All the IBM Tivoli Monitoring for Web Infrastructure ETLs provide a set of metadata to drive the ITM Generic ETL1 to retrieve data collected by the IBM Tivoli Monitoring 5.1.1 resource models, as well as general-purpose reports.

IBM Tivoli Monitoring for Web Infrastructure ETLs extracts data from the TWH_CDW database and loads it into the Web Infrastructure data marts.

Therefore they are called as a target ETLs. Each warehouse module has a measurement code as shown in Table 6-1.

Table 6-1 Measurement code

Warehouse Module Name Measurement Code

Apache HTTP Server gwa

iPlanet Web server gwp

The installation can be done using the Tivoli Enterprise Data Warehouse CLI or the GUI installation program. Here we describe the process using the GUI method. The following steps should be performed in the Tivoli Enterprise Data Warehouse Control Center server.

The installation is similar for all ETLs.

1. Select Start -> Run. Type in D:\setup.exe and click OK to start the installation, where D is the CDROM directory.

2. When the InstallShield Wizard dialog window for TEDW Installation appears, click Next.

3. The dialogue window for the type of installation appears. Select Application installation only and the directory name where the TEDW components are installed. We used C:\TWH. Click Next to continue.

4. The host name dialogue window appears. Verify that this is the correct host name for the TEDW Control Center server. Click Next.

5. The local system DB2 configuration dialog window appears. The installation process asks for a valid DB2 user ID. Enter the valid DB2 user ID and password that were created during the DB2 installation on your local system.

In our case, we used db2admin. Click Next.

6. The path to the installation media for the application packages dialog window appears. You should provide the location of the Web Infrastructure ETL package. Change the TEDW CD in the CD-ROM drive with the IBM Tivoli Monitoring for Web Infrastructure installation CD. Specify the path to the twh_app_install_list.cfg file in the directory name field. By default the path is

<CD_drive:>\tedw_apps\<Mesaurment_Code>, where:

<CD_drive:> Is directory of the IBM Tivoli Monitoring for Web Infrastructure CD

<Mesaurment_Code> Is the directory for the module you are installing.

7. Check the Now option (prevents typing errors) to verify that the source directory is immediately accessible and that it contains the correct files. Click Next. The Figure 6-17 shows the installation of IBM Tivoli Monitoring for Web Infrastructure: Apache HTTP Server ETL as an example.

Internet Information Server gwi WebSphere Application Server izy

Note: You need both the TEDW and the IBM Tivoli Monitoring for Web Infrastructure products installation media.

Warehouse Module Name Measurement Code

Figure 6-17 Path to the installation media for the Apache ETL program

8. The overview of selected features dialog window appears as shown in Figure 6-18. Click Install to start the installation.

Figure 6-18 Apache ETL programs installation

9. Once the installation is finished the Installation summary window appears.

Figure 6-19 on page 143 shows a successful installation.

If the installation was not successful, check the TWHApp.log file for any errors.

This log file is located at the <TWH_inst_dir>\apps\<Mesaurment_Code>.

<TWH_inst_dir> is the TEDW installation directory and <Mesaurment_Code>

are the directory names in Table 6-1.

Figure 6-19 Installation Summary Window

10.After the pack installation conclusion, you must reboot the TEDW Control Center server.

Post-installation steps

In order to ensure that the IBM Tivoli Monitoring for Web Infrastructure

Warehouse modules are functioning properly, a few changes must be applied to their configuration settings. The following steps should be performed for all installed IBM Tivoli Monitoring for Web Infrastructure ETLs:

1. Define user authority to the Warehouse Sources and Targets 2. Schedule the ETL

3. Change the ETL status to Production

Defining user authority to the Warehouse Sources and Targets You should inform the TEDW Control Center server of user access information for every source and target ETL process installed by the IBM Tivoli Monitoring for Web Infrastructure ETL. Follow these steps:

1. Start the IBM DB2 Control Center utility by selecting Start -> Programs ->

IBM DB2 -> Control Center.

2. On the IBM DB2 Control Center utility, start the IBM DB2 Data Warehouse Center utility by selecting Tools -> Data Warehouse Center. The Data Warehouse Center logon window appears.

Tip: To reinstall a failed installation, you need to first un-install the module from TEDW,

3. Log into the IBM DB2 Data Warehouse Center utility using the local DB2 administrator user ID. In our case, db2admin.

4. In the Data Warehouse Center window, expand the Warehouse Sources folder. As shown in Figure 6-20, there is one entry for each of the IBM Tivoli Monitoring for Web Infrastructure ETL. You have to configure the warehouse source corresponding to your Web server.

Table 6-2 Warehouse Source Modules

Figure 6-20 IBM Tivoli Monitoring for Web Infrastructure ETL Sources

Edit the properties of each entry in Table 6-2 corresponding to your module.

In order to do this, right-click it and select Properties and then select the Database tab. Fill in the database instance owner user ID information. The values used in the ITSO lab environment are shown in Figure 6-21, using the GWA_TWH_CDW_Source as example.

Warehouse Module Name Warehouse Source

Apache HTTP Server GWA_TWH_CDW_Source

iPlanet Web server GWP_TWH_CDW_Source

Internet Information Server GWI_TWH_CDW_Source WebSphere Application Server IZY_TWH_CDW_Source

Figure 6-21 GWA_TWH_CDW_Source user ID information

5. Finally, configure the warehouse target ETL’s. As shown in Figure 6-22, there is one entry for the IBM Tivoli Monitoring for Web Infrastructure for Apache, iPlanet and IIS. There are two entries for the IBM Tivoli Monitoring for Web Infrastructure for WebSphere. The target ETL programs listed in Figure 6-3, which corresponds to your Web server, need to be configured, as follows:

Table 6-3 Warehouse Target Modules

Warehouse Module Name Warehouse Target

Apache HTTP Server GWA_TWH_MART_Target

iPlanet Web server GWP_TWH_MART_Target

Internet Information Server GWI_TWH_MART_Target

WebSphere Application Server

IZY_TWH_MART_Target IZY_TWH_MART_Target

Figure 6-22 IBM Tivoli Monitoring for Web Infrastructure ETL Targets

Edit the properties of each entry in Table 6-3 corresponding to your module.

In order to do that, right-click it and select Properties and then select the Database tab. Fill in the database instance owner user ID information. The values use in the ITSO lab environment are shown in Figure 6-23, using the GWA_TWH_MART_Target as example.

Figure 6-23 GWA_TWH_MART_Target user ID information

Scheduling the ETL

The table below list the process that needs to be scheduled for the IBM Tivoli Monitoring for Web Infrastructure ETL’s to run. You have to schedule the processes corresponding to the module you have installed.

Table 6-4 Warehouse processes

The following steps are similar for all above processes and we use GWA_m05_CleanDataMart_Process to describe them.

1. On the TEDW Control Center server using Data Warehouse Center window expand Subject Areas.

2. Select GWA_IBM_Monitoring_for_Apache_HTTP_Server_v5.1.0__Subject_Area -> Processes and right-click GWA_m05_CleanDataMart_Process.

Choose Schedule, as shown in Figure 6-24.

Warehouse Module Name Process

Apache HTTP Server

GWA_m05_CleanDataMart_Process GWA_m10_ETL2_Process

iPlanet Web server

GWP_m05_CleanDataMart_Process GWP_m10_ETL2_Process

Internet Information Server

GWI_m05_CleanDataMart_Process GWI_m10_ETL2_Process

WebSphere Application Server

IZY_m05_Dimension_Process IZY_m10_Fact_Process

Figure 6-24 Scheduling GWA_m05_CleanDataMart_Process This will open up a dialog as shown in Figure 6-25.

Figure 6-25 Schedule configuration for GWA_m05_CleanDataMart_Process

Changing the ETL status to Production

All IBM Tivoli Monitoring for Web Infrastructure processes are composed by components that have Development status set as default. In order for them to run, their status needs to be changed from Development to Production.

Table 6-5 Warehouse processes and components

The following steps must be performed for all processes corresponding to your IBM Tivoli Monitoring for Web Infrastructure module. The Table 6-5 describes the complete list. Here we use GWA_m05_s010_CleanDataMart as an example to describe the process.

On the TEDW Control Center server using Data Warehouse Center window select the above processes and right-click on them. Choose Mode ->

Production, as shown in Figure 6-26.

Figure 6-26 Promoting scheduled ETL processes to Production status

Now all the processes are ready and scheduled to be run in production mode.

When the data collection is done we can use the reports provided by IBM Tivoli Monitoring for Web Infrastructure to view the data.