Moving Data to an External REST API

Transfer data from your enterprise data sources to an external REST API

Use Cases  Moving Data to an External REST API

Goals

To move data from one or more data sources (PLCs, databases, IoT devices, or any other source supported by OAS) to an external REST API for data logging, analytics, or any other function supported by the endpoint.

Supported Data Sources

  • Allen Bradley PLCs
  • Siemens PLCs
  • Modbus Devices
  • OPC Servers
  • Applications
  • OPTO Devices
  • MQTT Brokers
  • Amazon IoT
  • Azure IoT Hub
  • Databases

Solution Description

Any data source that can be connected to an OAS Universal Data Connector can have its data transferred to an external REST API. Once the data is in Tags, it can be used directly, transformed, or even be used as an input to new Calculation Tags.

Real time tag data can then be extracted from OAS using any of the available APIs. For .NET developers, the .NET Data Connector provides programmatic access and an event-driven model for updating applications when Tags change within the OAS Service. Developers who choose not to use .NET, or for developers not targeting Windows as the execution platform, the OAS REST API exposes real time Tag data as JSON structures over HTTP.

Tag data can then be further transformed and encapsulated into REST API calls required by the external system.

 

Example 1: Tag data is read from OAS using the .NET Data Connector and custom code submits REST API calls to external API

 

Example 2: Tag data is read from OAS using the OAS REST API and custom code submits REST API calls to external REST API
Download and start a free, unlimited trial, or schedule a live, interactive demo