Overview
ArchiveLocations provide a flexible mechanism for defining and managing where your historical data will be stored. You can assign a unique name and description to each Target Database, making it easier to identify and manage.
On this page:
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.