Enterprise RTView® 
User Guide


Configuring History Data

There are two types of Data Configuration (.rtv) files that can be used to determine what data will be archived by the Historian. See Running the Historian for information on how to use these files to configure the Historian.

NOTE: Before running the Historian, you must complete the Database Setup. The Historian communicates with your database using either a direct JDBC connection or an ODBC-JDBC bridge connection. Both connections require some setup before the Historian can communicate with your database.
 
Display Files Cache Definition Files
This option allows you to use dashboards you have already created in the Display Builder to also define the data you want to archive, so you can configure the Historian with the same displays you are using to view your data.

Display (.rtv) files created in the Display Builder contain objects attached to the data you would like to store. A record is stored in the history database every time new data is received by the Historian for each data attachment in your configuration display.

For data to be stored and retrieved properly, you must attach data to the appropriate type of object property for the corresponding value. Numeric values must be attached to numeric object properties and text values to string object properties. For example, if you attach a numeric value to a meter's label (which is a string object property), the numeric value will be stored in the database as a string instead of a number and therefore will not be available on trend graphs. Numeric values are stored in a numeric table (HISTORY or the table name you specify). Textual values are stored in a string table (HISTORY_S or the table name you specify). See Historian Database Setup section for information on configuring history tables.

When you attach data to a tabular object property, such as valueTable, it is recommended that you create a table in the history database to store that data. If you do not create a table, data from your tabular element will be stored in standard history tables and, in the case of tabular data with multiple columns, row integrity will be lost. See Historian Database Setup section for information on how to store tabular data.

For step-by-step instructions on creating data configuration files for the Historian or to learn how to create a table in the history database to store tabular data, go to Examples>Archiving Data.

  In more complex situations, it is not desirable to archive every piece of data accessed by a particular dashboard. In those cases, the Historian can be configured using cache definition (.rtv) files that contain Cache objects specifically defined to point to the historical data you wish to archive.

Cache definition (.rtv) files created in the Display Builder contain objects from the Caches tab in the Object Palette. Object properties defined for these Cache objects can indicate what sources of current and/or historical data you would like to keep in memory. Specify which of these cached values to archive in a history database and then use these cache definition (.rtv) files to configure the Historian.

Go to Caches>Introduction for information on creating a cache definition (.rtv) file and to learn about which Cache object properties are required to configure the Historian.

 


 
Enterprise RTView contains components licensed under the Apache License Version 2.0.

 

Treemap Algorithms v1.0  is used without modifications and licensed by MPL Version 1.1. Copyright © 2001 University of Maryland, College Park, MD

 

Datejs is licensed under MIT. Copyright © Coolite Inc.

 

JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

jQuery is licensed under MIT. Copyright © John Resig,

 
JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

 
SL, SL-GMS, GMS, Enterprise RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2009 Sherrill-Lubinski Corporation. All Rights Reserved.