$('a[name]').remove(); $('#ic-homepage__footer').before('
'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Cognos data model generation > Create reports IBM Tivoli Monitoring, Version 6.3
Populate the ManagedSystem Table
The MangedSystem table is populated using the kqz_populate_msn stored procedure.
See Run the DB2 stored procedure. This procedure must be run periodically so that the ManagedSystem table contains the current list of managed system names.
The stored procedure reads the following historical tables in the Tivoli Data Warehouse if they exist:
- The agent's Performance Object status table
- The agent's availability table. Agents that monitor processes or services have an availability table.
- The agent's discovery tables. Subnode agents create discovery tables.
Historical collection must be started on a particular set of attribute groups. A set of scripts is generated that creates and starts historical collection for these attribute groups. If you do not want to use the scripts, the list of attribute groups is listed in the comment header block of the script.
Sample scripts are created that show which tables must have historical collection enabled:
- reports/configuretdw.sh
- reports/configuretdw.bat
The following table describes the required arguments:
You must specify either -n or -m, but not both.
Required arguments
Argument Description -h candle_home The Tivoli Monitoring installation path. -u teps_user The Tivoli Enterprise Portal Server user to log in as when you create the historical collections. -n tems_name The Tivoli Enterprise Monitoring Server where the collections must be started. More than one Tivoli Enterprise Monitoring Server can be specified by using a space separated list. If you specify more than one Tivoli Enterprise Monitoring Server, put the list in quotation marks. For example, -n “tems1 tems2” -m managed_system_group_or_manged_system The managed system group or managed system name against which the collection must be started. More than one managed system group or managed system can be specified by using a space separated list. If you specify more than one managed system group or managed system, put the list in quotation marks. For example, -m “msg1 msg2”
The following table describes the optional arguments:
Optional arguments
Argument Description -s teps_host The host name or IP address of the Tivoli Enterprise Portal Server. If not specified, the default is localhost. -p teps_password Password for the Tivoli Enterprise Portal Server user that is specified with the -u option. If not specified, the script prompts for the password -c historical_collection_interval The historical collection interval to use when you start the historical collections. If not specified, the default is 1h (1 hour). The valid values are: 15m, 30m, 1h, 12hor 1d, where m is minutes, h is hours and d is days. -r pruning_interval Pruning interval to use for the historical data. The historical data must be pruned so that the tables do not continue to grow in size. If not specified, the default is 2d(2 days). Use d for days, m for months, y for years.
After historical collection is started, the kqz_populate_msn stored procedure must be run periodically. The stored procedure is run periodically so that the ManagedSystem table contains the most current list of managed systems in the Tivoli Monitoring environment.
- Run the DB2 stored procedure
Run a stored procedure on DB2.
- Run the Oracle stored procedure
Run a stored procedure on Oracle.
- Run the stored procedure on SQL Server 2005 and 2008
Run a stored procedure on SQL Server.
Parent topic:
Create reports