Overview – Programmatic Interface

There are five different methods of interfacing with the Programmatic Interfaces of the OAS server, each targeted at a specific set of needs.

Universal Driver Interface

Create data sources for OAS with target to both .NET Standard 2.0 for cross platform deployment and .NET Framework 4.6 or greater and .NET Framework 4.0 to deploy Windows Services locally and remotely.
Define your own properties that are automatically added to the OAS engine.
See the UDI Technical Overview on how to create a Universal Driver.

.NET Connector and Windows Components

For .NET developers who wish to create HMIs or system automations on a windows platform, these components provide visual and programmatic access to real time and historical data, as well as interfaces into automated configuration of the OAS server.

OAS PCL for Native Mobile Applications

The OAS PCL (Portable Class Library) is a programmatic interface designed to be used in a Xamarin Application, which allows developers to compile native applications for iOS and Android devices with a single code base.

REST API

Using standard REST patterns and JSON over HTTP, the REST API provides a programmatic interface for any platform that supports those technologies, including Linux servers, RaspberryPI and Arduino devices, and more.

Web HMI

For developers interested in creating HMIs in HTML5 web applications, the OAS Web HMI includes libraries for displaying real time and historical data in any web browser, using both a markup technique as well as a programmatic Javascript API.

The following graphic shows how Open Automation Software provides programmatic access for real time and historical data and shows the protocols and tools to create specific applications.

For more details on how to use any of these interfaces, see below:



More: