Versions Compared

Key

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

Introduction to Datasets module

The Dataset Module is designed for exchanges data exchange with SQL databases and text files from a diverse set of sources. This module . It offers compatibility with a wide array of various database technologies, including ADO.NET, ODBC, OleDB, and native interfaces, providing straightforward configuration with prominent databases such as SQL Server, Oracle, SQLite, and PostgreSQL.Features include multi-threaded concurrent connections for efficient data handling, a dedicated SQLite editor for streamlined database management, and an intuitive visual query builder that simplifies the process of query creation and manipulation. Moreover, the Dataset module  

On this page:

Table of Contents
maxLevel3
stylenone


Datasets Functionality

The Dataset module offers streamlined access to SQL databases, facilitating a seamless exchange of values for tables and queries within the application. Utilizing data retrieved from databases, users can create custom visualizations in the Displays Module, implement complex logic in the Scripting Module, and configure dynamic alarm systems in the Alarm Module. Moreover, it is equipped to integrate real-time tags within query strings, enhancing the dynamism of data interaction. It can also manage files and recipes in ASCII, Unicode, or XML formats, broadening its applicability across different data types. 

On this page:

Table of Contents
maxLevel3
stylenone

Feature Highlights

  • Multi-threaded concurrent connections for efficient data handling,
  • A dedicated SQLite editor for streamlined database management and
  • An intuitive visual query builder that simplifies the process of query creation and manipulation.

Processing Data Requests

The Datasets Data Server Service forms an integral part of the module, ensuring high performance and seamless integration while exchanging structured data collections in real-time. It efficiently processes data requests from other modules, enabling connectivity with various components such as HMI/SCADA screens, scripting, and reporting tools.

The Dataset module also serves as the data storage configuration hub for other modules. The Alarm and Historian modules, which generate events and records for long-term retention, utilize the Dataset module for defining data storage. Similarly, the Security Module can utilize user definitions from an external database within the Dataset module.

Data Source Virtualization

Data Source Virtualization is an advanced feature that simplifies data management across multiple data sources. It provides a unified interface for accessing, querying, and manipulating data, regardless of the underlying data storage technology. This feature allows modifications to the underlying data source repositories without impacting the rest of the application. The module works seamlessly with various data storage technologies. It enables centralized management of data connections and configurations, streamlining the integration of different data sources into your projects.

For a more detailed explanation of how the Dataset module works, please refer to the Advanced Dataset Topics page.



Main Components

To configure the Datasets module, you need to understand 4 main components:

  • Datasets DBs
  • Queries
  • Tables
  • Files

You find a brief description of each feature below.

Dataset DBs

For

Purpose and Key Concepts

The purpose of the Dataset module in FrameworX is to facilitate efficient data exchange between the platform and various external databases and text files, thereby creating a robust data infrastructure that empowers other real-time modules to function effectively.

Dataset DBs

In order for the Dataset module to communicate with an external database, you must create a connection must be created with certain specific parameters. These connections, which are created within the module's Datasets → DBs section of the module section, are referred to as Dataset DBs.

Dataset Queries

In the context of the Dataset module, a Dataset Query refers not only to an SQL query string , but also to a Project object that has a logical name, an SQL query related to that logical name, and other parameters defined within the the Datasets → Queries section section. There are many ways to automatically map the results of a query execution with Tags automatically.

Dataset Tables

A Dataset Table is a logical name that is created within a project to set up access to a specific table in a connected database. These tables are listed within the the Datasets → Tables section  section of the module. The Tags in the real-time database can easily be mapped to columns in the tables to perform insert, update, or read operations.

Dataset Files

A Dataset File is a logical name that defines parameters for reading and writing files in ASCII, Unicode, or XML formats. To manage the Dataset Files, go to to Datasets → Files. 


Using Tags in

Configuring the Dataset module

In

The basic process for configurating the Dataset module

, you can utilize Tags from your project as dynamic placeholders within SQL queries or file names. This capability facilitates real-time data manipulation within the query strings. Moreover, you can map the results of the queries to Tags, or employ Tags to populate values when inserting or modifying existing records. 

Understanding the Datasets module

Overview

The Datast modules allows easy ashes to SQL database bases, so you exchange values for Tables and query its twitch tags in the a[p[plica,

Data Utilization

The data retrieved from databases can be utilized in various ways throughout your project:

  • In the Displays Module: Visualization tools like DataGrids can present query results on screens and dashboards, creating custom views of the data that are accessible and easy to understand for your users.
  • In the Scripting Module: Custom scripts can reference query results and trigger specific actions, such as sending notifications, updating tags, or performing calculations, thereby implementing complex logic based on database data.
  • In the Alarm Module: Data can be used to configure or update alarm conditions, triggers, and actions, enabling the creation of dynamic alarm systems that respond to data changes.

In a similar fashion, various modules can add data to your SQL databases. For instance, the Displays Module can log operations inputs and commands, the Scripting Module can calculate analytics, and the Alarm and Historian Module can retain long-term records and audit trails. Essentially, the Dataset module drives bi-directional real-time communication between all Project Modules and the SQL databases.

Processing Data Requests

  • Datasets Data Server Service

The Datasets Data Server Service forms an integral part of the Datasets module, ensuring high performance and seamless integration while exchanging structured collections of data in real-time. It efficiently processes data requests from other modules, enabling connectivity with various components such as HMI/SCADA screens, scripting, and reporting tools.

  • Default Databases Used when Running the Project

The Dataset module also serves as a data storage configuration hub for other modules. The Alarm and Historian modules, which generate events and records for long-term retention, utilize the Dataset module for defining data storage. Similarly, the Security Module can utilize user definitions from an external database defined within the Dataset module.

Data Source Virtualization

Data Source Virtualization is an advanced feature that simplifies data management across multiple data sources. It provides a unified interface for accessing, querying, and manipulating data, regardless of the underlying data storage technology. This feature allows modifications to the underlying data sources repositories without impacting the rest of the application.

  • Agnostic, Standards, Centralized Management

Adhering to industry standards, the module is designed to work seamlessly with various data storage technologies. It enables centralized management of data connections and configurations, streamlining the process of integrating different data sources into your projects.

For a more detailed explanation of how the Dataset module works, please refer to the page Advanced Dataset Topics.

Configuring the Dataset module

Add sequence and link to Configuring page.

is as follows:

  1. Create a Database connection. Learn more at Database DBs.
  2. Create Queries, assiging logical names and adding realtime parameters. Access Dataset Queries for more information.

  3. Manage your project tables and connect inserted data with project Tags. See the Dataset Tables for more details.
  4. Exchange data via files. Learn more at Dataset Files.

The above steps are a simplified explanation of the configuration process.  For additional information on how to configure the Datasets module, access Configuring Datasets.


More On The Datasets Module

To learn more about the Datasets module, you can use the additional documentation pages available on the documentation:

  • Learn how to use the Datasets module together with other modules accessing the Working with Datasets page.

The Advanced Dataset Topics page presents complementary information about the following: 

  • Databases Connections and Interactions
  • Data Management
  • Datasets Runtime attributes

  • Preventing SQL Injections
  • Time zone handling

Use the Datasets Best Practices And Troubleshooting pages to access best practices tips and troubleshooting guides

More On The Datasets Module

Use the Historian Module as base and do the same

.


In this section:

Page Tree
root@self
spacesV10

...