![]() |
Enterprise
RTView®
User Guide |
Viewing History Data Data saved out of the Historian to the history database can be viewed from an Enterprise RTView display if you are licensed for the SQL data source. NOTE: The SQL data source may not be licensed in your Enterprise RTView installation. For step-by-step instructions on viewing and configuring historical data, see Examples for the Historian. NOTE: If you are using a direct JDBC connection or a password protected ODBC-JDBC bridge connection to communicate with the history database, you will need to configure the history database in the Display Builder before viewing your history data. To configure the history database in the Display Builder, go to the Application Options SQL tab and add a database named RTVHISTORY with the same configuration options used in the Historian. See the SQL Application Options page in the Data Sources section of this documentation for more information. To attach an object to historical data you can either enable the valueHistoryFlag object property or create an SQL data attachment. Object
Property - valueHistoryFlag
To set up a trace to load from the history database, you must have a corresponding object in a history configuration file that the Historian is using. The data attachment in the configuration file must exactly match the data attachment for your trace. The data must not be stored in a user defined table. Only data stored in the numeric table (HISTORY or the table name you specified) will be used to load historical data into your trace. Data
Attachment - SQL
NOTE: If you are using a direct JDBC
connection or a password protected ODBC-JDBC bridge connection, you will
need to go to the Application Options SQL tab and add a database named RTVHISTORY with the same
configuration options used in the Historian. See the SQL Application Options
page in the Data Sources section of this documentation for more information.
See
the section on History Tables in Historian>Database
Setup for the names of tables and columns in the history database
for use in data attachments.
|
|
|