------------------------------------------------
---   The Visual Warehouse Reports Sample    ---
------------------------------------------------

This sample warehouse contains nine BusinessViews, in groups of three: 
While the records in iwh.logmsgs table overlay over period of time,
these BusinessViews intend to keep a history of the most important 
events for the runs of BusinessViews.

- status_all, status_distinct and status_24hour
  The purpose of this group is to provide us with a report of all the 
  recent activities with simple failed or succeed status for each run.

- failed_all, failed_distinct and failed_24hour 
  The purpose of this group is to provide us with a report of recent 
  failed BusinessViews with the first error message for each 
  BusinessView.

- success_all, success_distinct and success_24hour
  The purpose of this group is to provide us with a report of recent 
  successful BusinessViews with statstical information about their 
  performance.

Within the three groups of the BusinessViews, the first ones 
(status_all, failed_all, success_all) have 30 editions.  Each edition
is a snapshot of relevant events of the iwh.logmsgs table.  
The second set (status_distinct, failed_distinct, success_distinct)
has 1 edition, which eliminates all duplicates from the 30 editions.
The last set (status_24hour, failed_24hour, success_24hour) has 1 
edition, which keeps the last 24 hours of the last BusinessViews.

These BusinessViews use many features of Visual Warehouse which you 
can see by opening their definitions.	 You can install this sample 
warehouse, browse them, run them (using the sample source table provided)
to see what they can do for you.  You can import the BusinessViews 
into your own Visual Warehouse control database, and use them on your 
BusinessView runs.  (The source database must first be changed to point
to your control database, whose iwh.logmsgs table contains the 
information about your BusinessView runs.) 

The BusinessViews are in LOG_STAT_REP target warehouse.


Pre-installation instructions
==============================

Backup Visual Warehouse Control Database (optional)
  o Stop Visual Warehouse
    - Use Services icon in Control Panel
  o Use DB2 Backup Utility
    NOTE: If backup fails because database connections exist,
          use DB2 FORCE command or reboot the machine.

Set DB2 Default Path
  Make sure the  default database path in the database manager
  configuration file (dftdbpath parameter) is set to where you
  want sample databases to be created:
	db2 get db manager cfg
	db2 update db manager cfg using dftdbpath <Drive>

Start DB2
  Start DB2 Server if not already started.


Installation instructions
=========================
  The Sample Installer Program can be used to install the
Reports Sample on a Visual Warehouse Server machine. The
Visual Warehouse Server does not need to be running. See
'vwsample.txt' for more information about the Sample Installer 
Program.

o At the Command prompt, change to the SAMPLE2 directory
o Enter 
       vwsample.exe reports.scr
		 
  Note: the metadata for this sample will be imported into the
current control database (the one you specified when you last
run Visual Warehouse Initialization program).  

  The Sample Installer Program leaves records the processing in 
the following log files:

o vwsample.log   Informational log file.
o impmsg.log     DB2 import log file.
o reports.log    Metadata import log file(reports.TAG is the name
                 of the metadata import file).


Handling Errors
  o See the log file for information about any errors and take
    whatever corrective action is necessary.
  o Modify Script File
	Make a copy of the script file and remove steps that completed 
	successfully or undo these steps. 
  o Restart the installation passing the modified script file.
 

Post-installation instructions
==============================
o Initial login
  The first time you log into the Visual Warehouse, use the
  userID and password you supplied when initializing the 
  control database.  This is the default user, who has access
  to all the BusinessViews in the LOG_STAT_REP warehouse.  

o Update Information Resources
  The userID/password for all source and target databases
  must be set to an authorized userID/password.  Change the
  userID/password in the sample to those recognized by the 
  database manager on your machine.
  o Open an Information Resource definition
  o Select the Database page
  o Update the userID/password

o Update Business Views
  All imported Business Views will be in Development status. To
  run these BVs, you must first use the Business View dialog to 
  create the target tables.
  o Open imported target warehouse
  o select a BV
  o From menu bar, select Status->'Promote to Test'. The BV
    status should change to Test. 

  Note: You cannot promote a Business View to Test status until
  all its 'contributing' Business Views have been promoted.
  A contributing Business View's output table is used as input
  table for this Business View.  Use the 'Tree' option in the
  'View' menu item of the Business View list window to see the
  hierarchical relationships among the Business Views.
