[ Bottom of Page | Previous Page | Next Page | Contents | Index ]
Installing and configuring a warehouse pack
This section describes warehouse pack installation procedures.
Prerequisites
Before installing this fix pack for the Tivoli Enterprise Console(R) product (or both the base warehouse pack and
this fix pack), 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 both the Tivoli Enterprise Console product base warehouse pack and this fix pack.
- This warehouse pack is configured by default to have one ODBC
source database. This ODBC data source is configured as a client connection
to your event database. The default name for this ODBC data source is TEC. You can modify this name when the warehouse pack is installed,
or you can use the Windows(R) ODBC Source Administrator window
to modify this value after installation.
- If the RDBMS Interface Module (RIM) host and the Tivoli Data Warehouse
control server are installed on the same machine, do not use the default ODBC
data source name TEC. Use a different default ODBC data source
name. If the default value of TEC is used, both the RIM host and Tivoli Data Warehouse are configured to use the same ODBC data source. During
uninstallation of the warehouse pack, the data source is removed and this
will cause the RIM host and Tivoli Enterprise Console server to fail.
- If you are using the Tivoli Enterprise Console warehouse pack in
a z/OS(R) environment, the central data warehouse and data mart databases
must be created in a DB2 location where the default encoding is UTF8.
- The central data warehouse ETL process only extracts the first
3500 bytes of an event message or the first 3500 bytes of an extended attribute
value. The remaining bytes are not extracted.
- The central data warehouse ETL process only extracts the
first 255 characters of the fqhostname attribute value. The remaining bytes
are not extracted.
- If you use the set_event_status predicate in the active rulebase to close
any events, the duration value is set to 0. If these events are then extracted
and loaded into the central data warehouse, their duration values skew the
results for the following reports:
- Average Time to Close Events by Severity
- Average Time to Close Events by Source
- Average Time to Close Events by Event Class
To avoid this problem, use the change_event_status predicate instead.
For more information, see the IBM Tivoli Enterprise Console Rule Developer's Guide.
- Fix pack 11 is required for the control server if your Tivoli Enterprise Console event database is a Sybase database. For more information, see the next
bullet in this list.
- If DB2 fix packs 10, 10a, or 11 are installed
after the Tivoli Data Warehouse control server, has been installed, the following
tasks must also be performed:
- Perform the tasks listed for APAR JR19393 in the Tivoli Data Warehouse,
Release Notes, Version 1.2
- From the DB2 command line on the control server, issue the following commands:
db2 connect to twh_mart
db2 drop view RPI.ss_joincols
db2 create view RPI.ss_joincols as SELECT
ss.name as ssname,
a1.largedrschemaname as schema,
a1.largedrtablename as tabname,
a1.largename as colname
FROM
IWH.AttributeLink at,
IWH.Relationship r1,
IWH.StarSchema ss,
IWH.Relationship r2,
IWH.attribute a1
WHERE
at.type='JOIN' and
at.iwhid = r1.source_iwhid and
r1.relation_name = 'StarSchema_TO_AttLnk' and
r1.target_iwhid = ss.iwhid and
r2.relation_name = 'AttLink1_TO_Attr_Rel' and
r2.source_iwhid = at.iwhid and
a1.iwhid = r2.target_iwhid
UNION
SELECT
ss.name as ssname,
a1.largedrschemaname as schema,
a1.largedrtablename as tabname,
a1.largename as colname
FROM
IWH.AttributeLink at,
IWH.Relationship r1,
IWH.StarSchema ss,
IWH.Relationship r2,
IWH.attribute a1
WHERE
at.type='JOIN' and
at.iwhid = r1.source_iwh id and
r1.relation_name = 'StarSchema_TO_AttLnk' and
r1.target_iwhid = ss.iwhid and
r2.relation_name = 'AttLink2_TO_Attr_Rel' and
r2.source_iwhid = at.iwhid and
a1.iwhid = r2.target_iwhid
- If your event database is installed on Microsoft(R) SQL
database, the ODBC connection must
use TCP/IP only. Named pipes or other types of connections are not supported.
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 and assumption of ETL runs on a 24 hour period.
It is important that you analyze your installation to determine your actual
requirements.
Table 3. Database-sizing example information
Database |
Assumptions |
Initial load disk space |
Daily update disk space |
* 1
GB = approximately 1 073 741 824 bytes. |
Central data warehouse |
- There are 100 000 events.
- The size of one event (including attributes) is 10 500 bytes.
- Each event has 6 relationships (including Update and Causes).
- The size of a relationship is 40 bytes.
- Each event has 5 customer-selected extended attributes.
- The size of each customer-selected extended attribute is 3600 bytes.
|
3 GB* |
6 GB |
Data mart |
- There are 100 000 events.
- The size of each event is 9000 bytes.
- There are 1000 event types.
- The size of each event type is 260 bytes.
- There are 10 statuses.
- The size of each status is 3000 bytes.
- There are 10 severities.
- The size of each severity is 3000 bytes.
- There are 5 customer-selected extended attributes.
- The size of each customer-selected extended attribute is 3600 bytes.
|
3 GB |
3 GB |
The following formula was used to determine the central data
warehouse disk space size for an initial load. Note that when an initial load
is followed by an update (all attributes are updated), the disk size requirement
doubles.
(number of events x 10 500 bytes) + (number of events x number of relationships per
event x 40 bytes) + (number of events x number of extended attributes x 3600 bytes)
= total bytes
The following formula was used to determine the data mart disk
space size for an initial load. Note that when an initial load is followed
by an update, updated information overlays any existing information. Therefore,
the size requirement does not change. The size requirement only changes with
new events.
(number of events x 9000 bytes) + (number of event types x 260 bytes) +
(number of statuses x 3000 bytes) + (number of severities x 3000 bytes) +
(number of events x number of extended attributes x 3600 bytes) = total bytes
Preinstallation procedures
Review the tasks in this section before you begin to install the warehouse
pack.
- If you are using multiple event database sources, you must change
the server IDs of the Tivoli Enterprise(TM) servers. For the procedure
to change the server ID, see Changing the Tivoli Enterprise Console server ID.
- 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 database 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(R)
|
|
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 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 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.
|
- The wtdwfilter command creates
both the event filter table and the extended attribute filter table in the Tivoli Enterprise Console database for every Tivoli Enterprise Console server that is used as a source database.
Planning note:
You must carefully plan which event classes
and extended attributes are important to store in the central data warehouse.
Store only those classes and extended attributes that provide information
that is important for reporting purposes. Although it is possible to store
all event and attribute data in the central data warehouse, this can cause
database size and performance problems. After carefully planning which event
classes and extended attributes are the most important, insert them into their
respective filter tables using the
wtdwfilter command.
You must create these tables before you run the ETLs for the first time. If
you do not create them before you run the ETLs, an error message is displayed.
For a description of the problem, see Problem determination.
Usage notes:
- The user who issues the wtdwfilter command must
be authorized to create and delete tables, because the wtdwfilter command issues RDBMS Interface Module (RIM) commands. See Creating the event filter table for
more information.
- You must know the following information before 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 and extended attributes you
want to store information about. For information to determine which events
you want to store information about, see Event Class and Extended Attribute filters.
- 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.
After the client has been installed, you must configure the ODBC data sources
using the Tivoli Data Warehouse supplied drivers. For the procedure to configure
the ODBC data sources, see Configuring database client drivers.
- 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:
- SQL Server Distributed Transaction Coordinator
- SQL Server SQLServerAgent
- 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.
- Create two indexes 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 these indexes,
the ETLs 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 these indexes:
- db2 -v "connect to twh_cdw"
- db2 -v "create index twg.eventattr_x2 on twg.eventattr (event_id)"
- db2 -v "create index twg.eventreln_x2 on twg.eventreln (event_source_id)"
- db2 "disconnect current"
Installing the base warehouse pack
This section provides information for installing the Tivoli
Enterprise Console base warehouse pack and post-installation procedures for
this installation. If the base warehouse pack is already installed, you can skip this section and immediately install this warehouse
fix pack. For the procedure to install this warehouse fix pack see Installing this warehouse fix pack and creating the extended
attribute filter table.
If the base warehouse pack is not already
installed, you must install it first and then install this warehouse fix pack.
Install the base 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 Scheduling the ETLs.
Post-installation procedures for the base warehouse pack
installation
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.
- Create a schedule for the ETLs. For information about scheduling ETLs,
see Scheduling the ETLs and for more information about the ETLs, see ETL Processes.
- 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:
- Put the EC2_m05_s010_mart_initialization step in production mode:
- 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.
- From the right side of DB2 Data Warehouse Center window, right-click EC2_m05_s010_mart_initialization.
- From the drop-down list that is displayed, click Mode -> Production.
- Run the EC2_m05_s010_mart_initialization step:
- From the DB2 Data Warehouse Center window menu, click Warehouse -> Work in Progress. The Work in Progress
window is displayed.
- From the Work in Progress window menu, click Work in
Progress -> Run New Step.
- Double-click EC2_m05_s010_mart_initialization.
- Click OK.
- Put the central data warehouse ETL and data mart ETL into production mode:
- Put the EC2_c05_ETL1_Process process into production:
- From the left side of DB2 Data Warehouse Center window, click EC2_c05_ETL1_Process.
- From the right side of DB2 Data Warehouse Center window, select all of the entries
that begin with EC2_c05.
- Right-click the selected entries.
- From the drop-down list that is displayed, click Mode -> Production.
- Put the EC2_m10_ETL2_Process process into production:
- From the left side of DB2 Data Warehouse Center window, click EC2_m10_ETL2_Process.
- From the right side of DB2 Data Warehouse Center window, select all of the entries
that begin with EC2_m10.
- Right-click the selected entries.
- From the drop-down list that is displayed, click Mode -> Production.
Creating 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.
Note:
If you are also installing this fix pack
after you complete the installation of the base warehouse pack, you can skip
this procedure to create the event filter table. When you install this fix
pack, you create the extended attribute filter table, which also creates the
event filter table.
Do the following procedure to create the event filter table:
- Determine which event classes you want to move from the Tivoli Enterprise Console event database to the central data warehouse.
- 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.
- For Tivoli Enterprise Console servers that are
running on UNIX(R) systems, use the following command to change the permission for
the wtdwfilter file to enable it to run:
chmod 750 wtdwfilter
- Use one of the following methods to source the Tivoli environment
settings for the wtdwfilter command:
- On UNIX systems, run the /etc/Tivoli/setup_env.sh script from the command
line.
- On Windows systems, run the script %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
from the command line and then enter bash to enter the bash shell
environment.
- 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.
Scheduling 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.
- Schedule the EC2_c05_ETL1_Process process to run once a day either at
12 a.m. (midnight) or at some other off-peak time.
- Do not schedule the EC2_m10_ETL2_Process process to run. It is started
automatically when the EC2_c05_ETL1_Process process runs successfully.
- The subject area for the warehouse pack is located in the
EC2_Tivoli_Enterprise_Console_v3.9.0_Subject_Area subject area.
- The EC2_c05_ETL1_Process process fails if the event filter
table is not created. For more information, see Post-installation procedures for the base warehouse pack
installation.
Installing this warehouse fix pack and creating the extended
attribute filter table
This section explains what you need to do before you install
this fix pack, the procedure for installing the fix pack, and how to create
the extended attribute filter table.
Installing this fix pack
Before you install this fix pack, you must first install
the base warehouse pack. If the base warehouse pack is not already installed, see Installing the base warehouse pack. If the base warehouse
pack is already installed, then install this fix 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/patch/ directory.
Creating the extended attribute filter table
This section provides information about creating the extended
attribute filter table using the wtdwfilter command.
For more information about the wtdwfilter command, see wtdwfilter.
Run the following command to create the extended attribute
filter table.
wtdwfilter -crttb
If you are installing both the base warehouse pack and this
fix pack, use the following procedure to create the event filter table and
extended attribute table. Note that if the base warehouse pack is already
installed and you are only installing this fix pack, this procedure creates
the extended attribute filter table and displays a message explaining that
the event filter table already exists.
- Determine which event classes and extended attributes you want to move
from the Tivoli Enterprise Console event database to
the central data warehouse.
- Copy the wtdwfilter file from the /tdw_weps/ec2/patch/misc
directory of the installation media to the $BINDIR/bin directory of each system
that the Tivoli Enterprise Console servers are running
on.
- 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
- Use one of the following methods to source the Tivoli environment
settings for the wtdwfilter command:
- On UNIX systems, run the /etc/Tivoli/setup_env.sh script from the command
line.
- On Windows systems, run the script %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd
from the command line and then enter bash to enter the bash shell
environment.
- Use the wtdwfilter command to create both tables.
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 tables in exists and that you know its name.
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. After you finish that procedure, do the following tasks:
- Delete the Crystal Reports folder. For more information, see Installing and Configuring Tivoli Data Warehouse.
- Delete the event filter table and the extended attribute filter
table. For more information, see wtdwfilter.
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 schema of the table before you can view or sample the
source event data. 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 schema of the table before you can view or sample the
source event data. For the procedure to modify the schema name, see Changing the schema name.
[ Top of Page | Previous Page | Next Page | Contents | Index ]