RESTful Web Services.
The REST data protocal can be connected with various highly differentiated systems. Protocols can be combined and intertwined in various ways. REST is entirely web-based, which means that it only uses http constructs and web technology, which is based on stateless logic between request-response cycles when conducting queries and edits in systems. Modern application platforms often prefer a REST-based protocol, as this allows easy data access and straightforward data transfers for external systems.
Achieve More with Combined Systems
REST is helpful for data transactions into or from a wide variety of systems. The number of REST-ready interfaces is gowing continually.
Industry 4.0 via REST
Via REST, systems are able to offer a standardized open interface for easy interlinking. The OPC Router ensures that connectedness and cross-linking works throughout the interconnected production environment by connecting everything with each other.
About the OPC Router
The OPC Router offers a visual network configuration interface for successful cross-linking of your systems. A high variety of plug-ins turns the OPC Router into a powerful data hub for industrial applications.
Easy configuration, sophisticated monitoring and robustness are main distinguishing features of the OPC Router.
That’s how easy it is.
The Rest transfer object accesses the resource via endpoints, while the method used indicates allowed interactions.
The method is selected via any given endpoint path. The method can be determined by request parameters. The method result is generated as response. The data in the response field can have any desired format; and is often returned as XML or JSON.
The respective scope of various methods is often documented by Swagger. Call results in XML or JSON can be further processed via XPath and JPath plug-ins.
The REST plug-in uses the standard trigger available in the OPC Router to prompt the transfers.
For direct connection triggering by external systems, the REST plug-in provides an interface for calling REST functions in the OPC router. Thus, the REST trigger serves as a direct call target. Parameters can be passed to the REST call which are used in the connection after the call.
The methods of any given endpoint are read out via Swagger or OpenApi.
All methods are provided in a methods results list, made available as a list of all usable Rest Service paths, for convenient selection. Various procedures are supported, among them: GET, PUT, POST und DELETE.
How do Transfer Objects, Triggers and Browsing work?
The OPC Router establishes connections between systems that address core functions of the OPC Router.
Functions of the respective plug-ins may vary, due to the different nature of each connected system.
Sources and Destinations
Transfer objects are the sources and destinations inside the OPC Router. They contain data fields with read and write functions. Depending on the respective interconnected system, the possible configuration scope of sources and destinations may vary.
Homegeinity on the Outside – Heterogeinity on the Inside
Inside the OPC Router configuration, the transfer object abstracts the respective system of any connected system into a simple data input and data output block. Thus, the functions can be treated in the same way although each connected system has very individual features.
Triggers determine execution time of data connections. Various triggers can be used for these connections, independent of transfer object type. Within each connection, several triggers can be used together via AND/OR-connections. Triggers can also be useful as data sources if the prompting event is combined with data reception.
Searching and Finding Data Fields
Easy browsing also makes data field configuration easy when establishing transfer objects in order to establish the respective interface connection. The browsing mechanisms may vary, depending on the system and its available plug-in.
Reading out Structures
Many plug-ins that are available for the OPC Router offer easy search and selection tools for quick identification of respective data fields without the need for specific knowledge about inherent subsystems. The user can easily browse through the data. Data source structures may vary according to the specification of each respective plug-in.