...
TimeSeries reader for a database. The general identifier for this reader is "database". This import allows a FSS or stand alone system to import data from a database. The import reads this database directly.
To allow for special behaviour of the database import, it is also possible to use the import type "DatabaseSingleLocationSingleDayPerQuery".
The different types do:
- database: one query to the database to retrieve all available data within the relativeViewPeriod.
- databaseSingleLocationSingleDayPerQuery: one query per wanted timeseries, per day to the database to retrieve all available data within the relativeViewPeriod.
Sometimes it may be required to install additional drivers to be able to read some Historian databases, like iHistorian from General Electric Januc.
Configuration
This reader supports the tableMetadata element in the general section of the timeseriesImportrun:
...
An example file is attached to this page.
Example to read iHistorian
Example to import from iHistorian database
...
<general>
<importType>databaseSingleLocationSingleDayPerQuery</importType>
<jdbcDriverClass>com.inzoom.jdbcado.Driver</jdbcDriverClass>
<jdbcConnectionString>jdbc:izmado:Provider=ihOLEDB.iHistorian;Data Source=srvHistorian</jdbcConnectionString>
<user>*****</user>
<password>******</password>
<relativeViewPeriod unit="hour" start="-24" startOverrulable="true" end="0"/>
<table name="ihRawData">
<dateTimeColumn name="TimeStamp"/>
<locationColumn name="Tagname"/>
<flagColumn name="quality"/>
<valueColumn name="Value" unit="SI"/>
</table>
<idMapId>IdKETEN</idMapId>
<flagConversionsId>ImportKETENFlagConversions</flagConversionsId>
<importTimeZone>
<timeZoneOffset>+01:00</timeZoneOffset>
</importTimeZone>
<dataFeedId>iHistorian</dataFeedId>
</general>
Note that special drivers should be installed at the servers, additionally from FEWS, to enable the access to iHistorian database