Re: [nv-l] NV Data Warehouse Enablement
2003-09-10 18:49:04
Framework is not required for the NetView
integration with the Tivoli Enterprise Data Warehouse (TEDW) and thus RIM
is not used. You do not need to have a DB2 Server on the same box as the
NetView Server but you would need a DB2 Client configured to communicate
with a DB2 Server in this case. You would also need the DB2 Java component
installed on the NetView Server machine (which adds the db2java.zip file
among other things) and a CLASSPATH variable set to include the location
of the db2java.zip file. This CLASSPATH variable must be included in the
environment in which the NetView daemons are started. The new "tdwdaemon"
daemon would inherit this environment so as to be able to use the db2java.zip
file (the DB2 Device Driver) to connect to a DB2 database (via JDBC).
The netmon daemon has been modified
to send notifications to a new daemon called "tdwdaemon" whenever
is detects a status change. The tdwdaemon then writes records to the DB2
based NetView availability database. As for flat files, it depends what
you mean. The answer is no generally speaking but lets say that the tdwdaemon
was not available because the DB2 Server was down, then netmon would write
the availability records to files called TDWError<mmdd>.log. These
are the only flat files that would ever contain availability data in this
solution. They would be read by tdwdaemon when it was brought up again.
They would be read in the order they were created by netmon and the information
written to the DB2 base NetView availability database.
If you have a DB2 Client/Server setup,
you would need to catalog the node and database information so that the
remote database that NetView will be using appears local to NetView Server
box (standard DB2 stuff).
There isn't really anything above that
has anything to do with the TEDW side of the equation. The NetView Warehouse
Enablement Pack, also known as the NetView WEP (also known as the ETLs)
is installed on the TEDW Control Server (always a Windows box). From the
DB2 Control Center, the "Data Warehouse Center" can be opened,
and the NetView "Warehouse Sources/Targets" for ANM (NetView)
can be configured with the DB2 userid and password to access the various
databases. An ODBC Data Source of ANM_SOURCE (must be named this !!) must
be defined for the NetView availability database. You will probably already
have ODBC Data Sources defined for the TEDW databases, TWH_MD, TWH_CDW,
TWH_MART.
The NetView ETL1 should be scheduled
to run (generally after midnight). The successful completion of its execution
will automatically trigger the start of the NetView ETL2. FYI, the ETL1
moves data from the NetView availability database into the Central Data
Warehouse (TWH_CDW). The NetView ETL2 moves database from TWH_CDW into
the TEDW Reporting datamart (TWH_MART).
There are 3 steps of NetView's ETL1
that must be moved from "Test" mode into "Production"
mode after you schedule the ETL1. There are 7 steps of the NetView ETL2
that must also be moved from "Test" mode to "Production"
mode. The ETL2 must not be scheduled.
Finally step would be to use the IBM
Console to manage/create/view reports after the ETLs have completed moving
data for you. Generally speaking the ETLs should be scheduled to run daily.
The reports will make as much sense as the data that is available
or the amount of data that is available.
Hope to helps make a little clearer.
Gareth Holl
Staff Software Engineer
gholl AT us.ibm DOT com
IBM Software Group - Tivoli Brand
Research Triangle Park, North Carolina.
| "Karl Prinelle" <Karl.Prinelle AT elyzium.co DOT uk>
09/10/2003 06:01 PM
|
To:
<nv-l AT lists.tivoli DOT com>
cc:
Subject:
[nv-l] NV Data Warehouse Enablement |
Hi list,
NV 7.1.3+fp1, Linux rh 7.2
I'd just like to clarify something I've seen
in the archive (same title as this post, reply by Gareth
Holl) about the tedw enablement pack.
From the docs & the archive note I'm
not clear if the enablement pack needs Netview to be using an rdbms itself
(via RIM) already before installing the pack or not?
The tdw doc's don't mention RIM at all, but
they do mention the Availability database and point to sql scripts to re-create
this (a) database.
I'm wondering if that means the tdw pack
runs something like ovtopoconv to pull data from netview flat files &
somehow?
I'm also a little unclear if I need to have
a full db2 server on my netview machine, or just a configured db2 client?
The (confused) picture in my head says;
On netview (Linux);
Netview,
non-framework install - no RIM
_No_ DB2
server
tdwdaemon process
db2 client
configured to point at my w2k db2 server & the NETVIEW database on
that which has been created using netview_tdw.sql
This machine
will be periodically writing availability info through the db2 client connection
to the database on the windows server.
On Windows;
DB2
TEDW -
all components
Configure
the Sources and Targets in the Data Warehouse Ctr
Assorted
tedw tasks will re-process the NETVIEW database populated by the Linux
box & write it on to the CDW and Data Marts
Can anyone clarify...... If the answer
is not on Linux, then replace Linux for AIX - is the process the same?
Ta
K
---------------------------------------------------------------------------
Karl Prinelle
Elyzium Ltd
Office: +44 (0)1753 515000
Mobile: +44 (0)7813 189198
E-mail: karl.prinelle AT elyzium.co DOT uk
Website:www.elyzium.co.uk
---------------------------------------------------------------------------
Elyzium Disclaimer:
This email transmission is confidential and intended solely for the person
or organisation to whom it is addressed. If you are not the intended
recipient, you must not copy, distribute or disseminate the information,
or
take any action in reliance of it. Any views expressed in this message
are
those of the individual sender, except where the sender specifically states
them to be the views of any organisation or employer.
If you have received this message in error,
do not open any attachment
but please notify the sender (above) deleting
this message from your system.
Please rely on your own virus check no responsibility
is taken by the
sender for any damage arising out
of any bug or virus infection.
---------------------------------------------------------------------------
|
|
|