Datasource

The Datasource object in the I/O Model of DataStudio informs a Connector object about the foreign servers to which it should connect on its host computer and how it should do this.

Use Cases

  • Establish the actual connection between the Connector service and various foreign 'servers' on the computer where it is running.

Quick Configuration

1. In the I/O Model panel, right-click on the Connector object to which you want to add the Datasource and select Admin  New  External Interfaces  Datasource from the context menu.

2. In the Create Object Wizard, give a name to the object and click Next to move on.

3. In the Server Type section of the wizard, select the intended server type from the drop-down selection.

4. The next steps will vary, depending on the Server Type. Check the "Mandatory Properties only" checkbox at the bottom of the wizard, to see which mininmum information you have to provide to configure the intended server type successfully.

More information about the individual Datasource types and their individual configurations can be found here:

5. Finally, click Create to create the object in the I/O Model.

Object Properties

Common

Object Name

The user-modifiable object name. This name overrides the name which has been supplied by the external system. It must be unique within the collection of objects of the parent object.

Object Description

This is the user-modifiable object description. This text overrides the description which has been supplied by the external system.

System Alias

The system alias is an additional name for an object, which can be used as a shortcut for identification and has to be unique in the system.

Display Alias

Alternate label for objects to be used for easier identification in the displays.

Attachments

File attachments stored in MongoDB file store.

Usecases

Lists the usecases that apply to this object.

Server Type

Endpoint Server Type selector.

OPC UA

OPC Unified Architecture.

OPC DA

OPC Data Access for communicating real-time data from data acquisition devices such as PLCs.

OPC DA + AE

OPC Data Access and Alarm & Events for communicating real-time and event triggered data from data acquisition devices such as PLCs.

OPC DA + HAD

OPC Data Access and Historical Data Access for communicating real-time and historical data from data acquisition devices such as PLCs.

OPC DA + AE + HAD

OPC Data Access and Alarm & Events and historical Data access for communicating real-time and event triggered and historical data from data acquisition devices such as PLCs.

OPC AE

OPC Alarms & Events for communicating event triggered data.

OPC AE + HAD

OPC Alarm & Events and historical Data access for communicating event triggered and historical data from data acquisition devices such as PLCs.

OPC HDA

OPC Historical Data Access to exchange archived process data.

OPC XML DA

OPC XML DA Builds on the OPC DA specifications to communicate data in XML, incorporates SOAP and Web services.

Dropzone

File-based Data Imports via Dropzone.

Generic TCP Stream

Simple generic TCP-based event stream.

Virtual Data Source

Virtual Data Source.

ODBC Datasource

Manages a relational database source connection.

PLC

Programmable Logic Controller.

IT Log Data Source

This subclass manages datasource for IT Log monitoring.

Batch Record

Acquire complete batch records from an external source.

MQTT Subscriber

MQTT based subscriber as a datasource subclass.

Kafka Datasource

Kafka based datasource subclass.

Modbus

Modbus.

Activity Monitoring

Monitoring of the vital signs of the object.

Enable

Enable the activity monitoring.

Monitoring Period

The time period which is monitored to determine a sustained drop of the item update rate as a missing vital sign of the object.

Frequency Drop

A drop of the item update rate in percent which determines a missing vital sign of the object.

Warning Only

If this option is set the severity level of the alert is downgraded from 'Error' to 'Warning'.

Launch Reconnect

Instructs the object to reconnect if the alarm is raised.

Location

The location of the object.

Strategy

Definition of the location strategy.

  • No location: This object is not interpreted in a location context.

  • Static (or manually changed) location: You may set the location data manually, by Engineering Script or by selecting the location visually using the Location Finder feature.

  • Inherited location: The object inherits the location from the owning object in the system hierarchy.

  • Dynamic location: The object location is supplied by other I/O Items. You may drop other I/O items into the location fields of this object.

  • Location properties: The endpoint server has distinct properties for I/O item location data. Please note, that this option works only for I/O items .

Name

The optional name of a location.

Latitude

The north-south position of a point on the Earth’s surface.

Longitude

The east-west position of a point on the Earth’s surface.

Altitude

The height above sea level of the location.

Track Location

Enables historization of Location data.

Script Library

The script library compound contains Lua-Script libraries.

Module Name

The Lua module name of the library that will be used to reference the library by its users.

Lua Script Body

Script editor to enter an advanced Lua script.

Mandatory Execution

Execute the script library when initializing the Lua environment for child objects.

Auxiliary State Management

Configurable settings for auxiliary state management.

Strategy

Specifies how auxiliary state changes are handled.

  • Inherit: Inherit the setting from the parent object. In case of no parent object, the "Persist" mode is used.

  • Persist: All object auxiliary states are indicated and persisted to the archive.

  • Volatile: Auxiliary state changes are volatile and not persisted.

  • Inhibit: Inhibit all auxiliary state changes.

Custom Options

Compound to hold various structures to customize the object and to be read and written to by Lua-Script code or external interfaces.

Custom String

A generic string buffer to be used programmatically for custom purposes.

Custom Properties

This is an extensible set of named strings which can be used programmatically for custom purposes.

Property Name

A custom property name which can be used programmatically.

Property Value

The value of the custom property which can be read and written programmatically.

Custom Tables

This is an extensible set of named tables which can be used programmatically for custom purposes.

Table Name

A custom table name which can be used programmatically.

Table Data

Handles an entire table organized in columns and rows. The data can easily (cut, copy and paste) be exchanged with table-oriented data of other software products, e.g. MS Excel.