Overview
Archive Locations offers a flexible way to define and manage where historical data is stored. You can define a default Tag Historian Database and also add external options, if necessary.
On this page:
Understanding Archive Location
The Archive Location defines where Tag's data will be archived considering the Historian Tables arrangement. establishing a clear linkage between tags and the storage infrastructure. You can use SQL databases, ScriptClasses, or connections with a Third-Party Historian when configuring the Archive Location. In other words, when you set the Archive Location, you're specifying the storage medium for Tag's data.
By default, FrameworX uses an SQLite database. You have the option to change the default database or add additional databases, in case you need to use different databases.
Configuring The Default Database
You have several options to choose from when defining the default database. In case the default SQLite option does not work for you, you can change it by following the steps below:
- Access Historian → Archive Locations.
- Click on the gear icon to open the Dialog.
- Define the default database configuration, defining Provider, Database, and ServerIP.
- Test the database connection. Provide the necessary authentication information and click Test.
- Click OK to update the default database.
Available Databases
The next table list all accepted Providers and Databases when configuring the default database.
| Provider | Databases |
|---|---|
| SQLite | SQLite |
| Odbc |
|
| OleDb |
|
| OracleClient | Oracle |
| SqlClient |
|
| PostgreeSQL | PostgreeSQL |
Configuration
On Historian tab, click on ArchiveLocation and the + button.
Fields:
- Name: Unique name for the Target Database.
- Description: Optional description to provide more context or information.
- Store and Forward: Option to temporarily store data in case of connection failure to the destination.
Target Type:
You have two options to choose from:
ExternalTagSource: In this option, you can select from different ExternalTag Providers such as CanaryLabs, InfluxDB, and GEProficy.
- Station: Here, you configure the connection string to the selected provider and run a test to ensure the setup is correct.
ScriptClass: If you opt for this type, you'll need to either create a script class or point to existing classes that will define how the data will be handled and stored. For help creating classes, see the Script, Classes and Tasks documentation.