Versions Compared

Key

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

Overview

You can use a PostgreSQL database using with the Tag Historian feature. The steps to achieve this involve:

  1. Rename
databases
  1. Databases.
  2. Create and
testing
  1. Test the PostgreSQL
connection
  1. Connection.
  2. Configure Tags and
tasks
  1. Tasks.
  2. Write
specific queries
  1. Specific Queries for
select
  1. Select,
insert
  1. Insert,
update
  1. Update, and
delete operations
  1. Delete Operations.
 

On this page:

Table of Contents
maxLevel3


Configuration PostgreSQL Via Tag Historian

Follow the steps below to configure PostgreSQL using Tag Historian.

  1. Access Datasets > DBs.
  2. Rename the SQLite database TagHistorian to TagHistorian2 or any other name. You should rename it because the system will use the TagHistorian name to configure the Postgre SQL.
  3. In DBs, click the plus icon to create a new Database Connection.
  4. In the Name field, enter TagHistorian.
  5. Choose PostgreSQL Data Provider as the Provider for the database.
  6. Click OK.
  7. In the data grid, click the Connection String column of the newly created row.
  8. Configure the connection. For the Server field, enter the IP address of the

    Postgre Server

    PostgreSQL server. In addition, you need to provide the Port, Database name, and User

    Id

    ID. After filling in all fields,

    click

    click Test to ensure the connection with the

    Postgre Server

    PostgreSQL server is working correctly.





Configuration Example

[WE NEED MORE INFORMATION ABOUT THIS EXAMPLE. IT LACKS INFORMATION TO CONNECT EVERYTHING]

This example presents necessary steps to connect and start using a PostgreSQL DB. To run the example, it is necessary to created objects in other modules of the platform. Below you find a list of modules used and the necessary configurations.

In Datasets > Queries you need to create the queries below. Access Datasets Queries to learn how to configure queries.

  • QuerySelect
  • QueryInsert
  • QueryDelete
  • QueryUpdate

In Unified Namespace > Tags → Tags, we created some Tags tags to save values in the DBdatabase. To learn how to create and configure Tags tags, access Unified Namespace. The created tags are described below:

  • Integer01, Integer02, and Integer03 are used to send values to the PostgreSQL DBdatabase.
  • TriggerUpdate, TriggerSelect, TriggerInsert, and TriggerDelete are used to trigger script tasks created for the example.
  • QuerySelect is used to receive the result of the Select query.

In Historian > Historian Tags, configure the Integer01, Integer02, and Integer03 Tags tags to Table1. Remember that to configure the PostgreSQL is connected to connection must be configured to work with Tag Historian, which is standard.

In addition to the above configuration, you need to access Scripts > Tasks and create we created some tasks to for Select, Delete, Update, and Insert, and configured configuring the Trigger column with the marks created beforeearlier. Below, you will find all required scripts:

  • Select Query

    Code Block
    languagec#
    @Tag.QuerySelect = @Dataset.Quey.QuerySelect.SelectCommand();
    @Info.Trace("Select OK:" + @Tag.QuerySelect);


  • Insert Query

    Code Block
    languagec#
    int i = @Dataset.Query.QueryInsert.ExecuteCommand();
    @Info.Trace("Insert OK:" + i);


  • Update Query

    Code Block
    languagec#
    int i = @Dataset.Query.QueryUpdate.ExecuteCommand();
    @Info.Trace("Update OK:" + i);


  • Delete query:

    Code Block
    languagec#
    int i = @Dataset.Query.QueryDelete.ExecuteCommand();
    @Info.Trace("Delete OK:" + i);


After finishing the configuration and creating the scripts, you can run the project and provide different values to the Tags created. Thus, if you access the PostgreSQL Server, you can access Table1 which was createdaccess the created Table1. You can also check that all values you provided are within Table1 due to the execution of previously created queries.



In this section...

Page Tree
root@parent
spacesV10