Versions Compared

Old Version 11

changes.mady.by.user user-8416b

Saved on

compared with

New Version Current

changes.mady.by.user otavio.santos@tatsoft.com

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Storage Locations are designated databases that store historical data from Tags on their HistorianTables.

Each Storage Location is a repository for time-series data, enabling long-term trending and analysis.

When defining which Tags will store time-series data, those Historian Tags are grouped into Historian Tables, and each Historian Table is located in a Historian Archive Location defined in this interface. 

By Default, the system has an SQL database defined for Storage Location, Historian Tools and Script Classes that can be added to the solution, as alternate, or concurrent, storage locations. 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:

Table of Contents
maxLevel3
stylenone

Tip
titleSolution Example

Historian Examples


Understanding

Archive Location

Storage Locations

The Archive Storage 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 When configuring the Storage Location, you can use:

  • SQL databases

  • Script Classes

  • Connections with Third-Party Historians, Like Canary and others. 

When you set the Storage Location, you specify the storage system for Tag , 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 the platform uses an SQLite database. You have the option to can change the default database or add additional databases , in case if you need to use different databasesones.

Configuring

The

the Default SQL Database

You have several options to choose from when defining the default database. In case If you would like to change the default SQLite option does not work for you, you can change it by following database to be something other then the initial SQLite built-in database, follow the steps below:

  1. Access Historian

    → Archive

    / Storage Locations.

  2. Click on the

    gear icon

    Image Added to open the Dialog.

  3. Define the default database configuration, defining Provider, Database, and Server IP.

  4. Test the database connection. Provide the necessary authentication information and click Test.

  5. Click OK to update the default database.

Image RemovedImage Added

Available Databases

The next following table provides a list all of accepted Providers providers and Databases when databases for configuring the default databaseoptions.

Provider

Databases

SQLite

SQLite

Odbc

Firebird

MSAccess2003

MSExcel2003

MySql

ODBC_DSN

ODBC_FileDsn

Oracle

SQLServer

SQLServer_WA

OleDb

CSVFile

MSAccess2003

MSAccess2007

MSExcel2003

MSExcel2007

Oracle

SQLServer

SQLServer_WA

OracleClient

Oracle

SqlClient

SQLServer

SQLServer_WA

PostgreeSQL

PostgreSQL

PostgreeSQL

PostgreSQL


Add a new

Archive Location

Storage Location

Solutions can store data using an external Historian package, or support SQL and multiple Historians concurrently, according to your requirements.

Follow In case you need additional databases, you can follow the steps below to add and configure themnew storage locations.

  1. Access

    Historian→ Archive Location

    Historian / Storage Locations.

  2. Click on the

    plus icon

    Image Added.

  3. On the

    4. Dialog

  4. dialog, configure the new database.

    5. The

  5. You find the description of each option available

    6. option is described

  6. in the next

    7. session

  7. section of this documentation page.

  8. Click Ok.

Archive location

Image Added

Storage Location Properties

The table below describes the configuration options available when adding a new Archive Storage Location.

Property

Description

Name

A unique name to identify the new Arquive Storage Location.

Description

Optional description to provide more context or information.

Store and ForwardStoreAndForward

If you check this option, FrameworX the platform will store data locally in case of connection failure with the external database. The data is transfer transferred when the connection is restablishedestablished.

Archive Storage System

The types Types available to configure the Archive locationStorage Location. Currently, two options ar are available:

TagProvider

Tag Provider: Enables you to use external solutions to archive Tag

's

data.

ScriptClass

Script Class: For this option, you need to

either

create a script class or point to existing classes

that will

to define how the data will be handled and stored. For help creating classes, see the

Script, Classes and Tasks

Scripts (Tasks and Classes) documentation.

Object

The tag provider or script class to use as a storage location. You may also create a new tag provider or script class from this option.

Protocol (Only available if using TagProviderTag Provider)

Defines the protocol used by the External TagProviderTag Provider. Currently, you can use the following options:

Station Editor   (Only available if using TagProviderTag Provider)

Configure the connection string to the selected provider and run a test to ensure the setup is correct. Visit the links above to find out how to configure each tag provider's connection string.


In this section

...

:

Page Tree
root@parent
spacesV10