IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Tivoli Data Warehouse solutions: common procedures > Run the warehouse agents autonomously
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Configure a Summarization and Pruning Agent to run autonomously
For a Summarization and Pruning Agent to run without connecting to a Tivoli Enterprise Portal Server, it must be configured to run autonomously and it must be able to locate the application support files for the monitoring agents.
To configure a Summarization and Pruning Agent to run in autonomous mode, complete the following steps:
- If you have not already installed done so, install a Tivoli Enterprise Portal Server, and add application support for all types of monitoring agents that will be collecting historical data.
- Install and configure Summarization and Pruning Agent following the instructions in the appropriate chapter:
- Tivoli Data Warehouse solution using DB2 for Linux, UNIX, and Windows
- Tivoli Data Warehouse solution using Microsoft SQL Server
- Tivoli Data Warehouse solution using Oracle
- If the Summarization and Pruning Agent is not installed on the same machine as the portal server, copy the required application support files to the machine on which the Summarization and Pruning agent resides.
These files are named dockpc, where pc is the two-letter product code for the monitoring agent (see IBM Tivoli product, platform, and component codes).
The files are located in install_dir\cnps directory; on The files are located in the installdir/arch/cq/data directory.
By default, the Summarization and Pruning Agent looks for the ODI files in the install_dir\TMAITM6 directory (on Windows) or the install_dir/arch/cq/data directory (on UNIX and Linux). If you do not create this directory and copy the files to it, you must add the KSY_AUTONOMOUS_ODI_DIR variable to the Summarization and Pruning Agent environment file and specify the alternative location.
There is no need to copy the dockcj file; it is not used when reconfiguring the Summarization and Pruning Agent. If you do copy this file, the following error will occur and can be ignored.
Validation failed: Column name exceeds 10 characters: ACKNOWLEDGED. ODI File contents not loaded: /install_dir/dockcj
- On the machine where the Summarization and Pruning Agent is installed, open its environment file in a text editor:
- install_dir\TMAITM6\KSYENV
- install_dir/config/sy.ini
- Edit the following variables:
- To enable the Summarization and Pruning Agent to run without connecting to the Tivoli Enterprise Portal Server, set KSY_AUTONOMOUS=Y.
- If you did not install the application support files in the default directory (see step 3), set KSY_AUTONOMOUS_ODI_DIR=<alternative location of application support files>.
- Restart the Summarization and Pruning Agent agent. The WAREHOUSESUMPRUNE table is automatically created when the Summarization and Pruning Agent is started.
- If you are upgrading from a previous version and already have summarization and pruning settings stored in the Tivoli Enterprise Portal Server database, restart the Tivoli Enterprise Portal Server.
The first time the portal server is started after the WAREHOUSESUMPRUNE table has been created, any previously existing data collection and summarization and pruning configuration settings are migrated to the WAREHOUSESUMPRUNE table in the warehouse data base. Subsequently, any settings configured using the portal server are stored directly in the warehouse.
- Configure summarization and pruning without the Tivoli Enterprise Portal Server
You can configure historical data collection and summarization and pruning using the Tivoli Enterprise Portal, or you can configure them directly in the warehouse database WAREHOUSESUMPRUNE table using SQL commands.
Parent topic:
Run the warehouse agents autonomously