IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Summary of supported operating systems

This section illustrates the supported operating system platforms for the various warehousing components, the supported database products, and the connections between components.

For more specific information about supported operating systems and database products, including product names and versions, see Hardware and software requirements. In this diagram, UNIX refers to any UNIX platform supported by the RDBMS.

The diagram is not meant to suggest that each warehousing component must be installed on a separate computer. Multiple components can exist on the same computer provided there is operating system support for all installed components. Connections between components must be configured whether or not they exist on the same computer. (Although the diagram makes no assumptions about where components are installed, the procedures described in the next four chapters assume a Tivoli Data Warehouse that is remote from the portal server.)

Figure 1. Summary of support for the Tivoli Data Warehouse

In the following discussion, numbered product components correspond to the numbers on the diagram.

Tivoli Data Warehouse database

Data collected by monitoring agents is stored at intervals in short term history files. The data in the short term history files is referred to as historical data. The short term history files are located either at the agents or at the monitoring server (hub or remote) to which the agents report. (An administrator can determine where the data is stored. The monitoring agents and monitoring server are not shown in the diagram.)

The historical data is sent from its temporary storage location (at the monitoring agents or monitoring server) to the Warehouse Proxy Agent at a preset interval (either every hour or every 24 hours). The Warehouse Proxy Agent inserts the data it receives to the Tivoli Data Warehouse.

Data in the short term history files that is older than 24 hours is pruned when the monitoring agent or monitoring server receives an acknowledgment that the data has been successfully inserted into the Tivoli Data Warehouse. (The pruning of binary files is not the pruning performed by the Summarization and Pruning Agent. The Summarization and Pruning Agent prunes data in the Tivoli Data Warehouse.) The result of these operations is that, at any given time, the short-term historical files contain data that is less than 24 hours old, and the Tivoli Data Warehouse contains long-term historical data that is older than 24 hours.

The Tivoli Data Warehouse database can be created using Microsoft SQL Server, IBM DB2 Database for Linux, UNIX, and Windows, Oracle, or IBM DB2 on Z/OS on the indicated operating system platforms. Note that the warehouse database is supported on Microsoft SQL Server only if the Tivoli Enterprise Portal Server is installed on Windows. This condition applies even if the warehouse database and portal server are installed on separate computers. For example, a portal server on Linux does not support a warehouse database on Microsoft SQL Server.

Warehouse Proxy Agent

A Warehouse Proxy Agent running on Windows uses an ODBC connection to send the collected data to the warehouse database. On a 32-bit Windows system, this requires a 32-bit ODBC driver, but on 64-bit Windows, it requires a 64-bit ODBC driver by default (although sites running a 32-bit Warehouse Proxy Agent under 64-bit Windows can configure a 32-bit ODBC driver for the agent to use; the necessary instructions are provided in this manual). The type of ODBC driver your site uses is determined not by the operating system but rather by the type of Warehouse Proxy Agent your site runs: the 32-bit agent requires a 32-bit ODBC driver, whereas the native 64-bit agent requires a 64-bit ODBC driver.

A Warehouse Proxy Agent running on Linux or AIX uses a JDBC connection.

The Warehouse Proxy Agent will do the following as needed:

Firewall considerations:

Appropriate ports must be open to support these communication channels (see Firewalls).

Depending on the database system you're using with the Tivoli Data Warehouse, make sure you complete one of these steps when installing the Warehouse Proxy Agent:

If your site has previously installed the 32-bit agent and you wish to upgrade to the 64-bit agent, first uninstall the 32-bit agent; see Uninstall the Warehouse Proxy. This might also require removing the 32-bit ODBC driver you configured for the Warehouse Proxy Agent; see also Remove the ODBC data source connection.

When uninstalling a 32-bit agent so your site can upgrade to a 64-bit agent, remember that any customizations your site has made to the KHDENV configuration file must be redone. Also, a 64-bit ODBC driver must be installed for the 64-bit agent to use. Usual process for activating the 64-bit Warehouse Proxy Agent:

  1. Install the ODBC 64-bit data source, if not installed already.

  2. Install the 64-bit agent.

  3. Configure the agent to use a 64-bit data source.

  4. Start the agent.

To determine which Warehouse Proxy Agent is running (32-bit or 64-bit), open the Windows Task Manager. The 32-bit agent has "*32" next to the process name.

Tivoli Enterprise Portal Server

The Tivoli Enterprise Portal Server retrieves historical data for display in historical data views in the Tivoli Enterprise Portal and in monitoring dashboard applications for the Dashboard Application Services Hub. It retrieves short-term historical data from the binary files on the monitoring agents or monitoring server. It retrieves long-term historical data from the Tivoli Data Warehouse.

In Figure 1, the Tivoli Enterprise Portal Server is shown with the portal server database (designated as TEPS database in the diagram). The portal server database stores user data and information required for graphical presentation on the user interface. Before you install and configure the portal server, install the database platform (RDBMS) to be used for the portal server database (DB2 for Linux, UNIX, and Windows or Microsoft SQL Server) on the same computer. The portal server database is created automatically during configuration of the portal server.

Although the portal server database is not considered a warehousing component, it is included in the diagrams in this and the following chapters because it can affect the installation and configuration tasks required for the Tivoli Data Warehouse database. For example, the database client already installed for the portal server database can connect to a remote warehouse database, provided both databases use the same database platform. There is no need to manually install another client.

If the portal server is installed on Windows, it uses an ODBC connection to request and retrieve historical data from the warehouse database. If the portal server is installed on Linux or AIX, it communicates with the warehouse database through a JDBC connection, if the warehouse is installed on Oracle, or through a proprietary DB2 CLI connection if the warehouse is installed on DB2 for Linux, UNIX, and Windows.

Summarization and Pruning Agent

The Summarization and Pruning Agent retrieves detailed data from the warehouse database, aggregates or prunes the data, and returns the processed data to the warehouse. Communication takes place through a JDBC connection, regardless of the operating system on which the Summarization and Pruning Agent is installed.

The Summarization and Pruning Agent will create tables, indexes, and views as needed. This could happen in either of the following situations:

In addition, the Summarization and Pruning Agent, like the Warehouse Proxy Agent, may alter existing tables by adding new columns.

Firewall considerations:


Parent topic:

Tivoli Data Warehouse solutions

+

Search Tips   |   Advanced Search