Mechanisms for collecting historical data
For configuring the historical reporting component in OMEGAMON® for Storage, you must be aware of the mechanisms for collecting historical data.
| Name of configuration method | Storage place for the data | Typical type of data* | Procedure | Purpose |
|---|---|---|---|---|
| PARMGEN or Configuration Manager Note: It is
recommended to use Configuration Manager though PARMGEN is also
supported.
|
Persistent data store (PDS) | Short-term history * | Configure the runtime environment (RTE). The configuration process includes the option to turn on collection of historical data for certain tables. | Collect data at a fixed interval, when the RMF (Resource Measurement Facility) interval ends. |
| Tivoli® Enterprise Portal | IBM® Tivoli Data Warehouse | Long-term history * | Use the Historical Configuration dialog box in the Tivoli Enterprise Portal to turn on collection of historical data for all other tables. | Collect data at varied intervals. Note: You have the option to
turn collection on or off only.
|
| * This column identifies the type of data that is typically configured. However, there are cases where each of the two configuration mechanisms affect the other type of data, long-term or short-term data, respectively. | ||||
To decide how to size the datasets for these tables, consider the amount of data that you are collecting and the amount of 'short-term history' that you want to maintain. For more information regarding sizing, see Table of metrics for persistent data store.