MS SQL Server SOAP Web Services

Graphically connect SOAP Web Services

A web service enables communication between system on the basis of the web protocols HTTP and HTTPS. Upon connection, data is exchanged and functions are called. Each and every web service has its own unique address (URL) and is described by its very own descriptive data file (WSDL).
With the OPC Router you can link your systems graphically to any WSDL SOAP Web Service and realize read and write data exchange.

Run a free test now

SOAP Integration example

Example of SOAP Web Service Integration

That’s how easy it is.

Connecting Systems

What’s Transfer, Trigger and Browsing?

Transfer Objects

The transfer object of the Web Service plug-in gives access to the functional scope of the Web Service.

Functional Scope

Once the input values have been transmitted to the parameters, the respective selected function is called by the plug-in during transfer. A return value is rendered and sent to the object, and can then be made use of according to individual specification.

Trigger

Web Service plug-in makes use of the standard data carriers of the OPC Router, and does not have its own trigger functions.

Please contact us, for more information on recent upgrades for this plug-in.

SOAP WSDL Browsing of a WSDL resource.

Browsing

Web Services make us of a very distinct description language, which is WSDL (i.e. Web Service Description Language). The OPC Router reads WSDL descriptions directly – with no detours – and presents the strucutre of the Web Service.

Functional Scope

The WSDL description contains a list of functions contained in the Web Service. This list is made available for individual selection.

Parameter

Functions have parameters and return values. In addition to simple types, both can also contain complex structures, array and arrays of complex structures. All variants are supported by the OPC router and listed for selection.

Application examples

ERP System connection via SOAP Web Service to databases

Many ERP systems have web services. This interface allows data to be received from the ERP system, but also to be sent. In connection with databases, it is often order and recipe data or material master data that are loaded from the ERP and stored in a production database. Batch and consumption data available in the production database are transferred to the ERP via the SOAP Web Service interface.
The database is connected by the OPC Router thru the Microsoft SQL Plug-in (or OracleMySQLAccessODBC).

MS SQL Server
OPC UA Client / OPC DA Client

PLC decisions driven by SOAP Web Services

In various situations (stock movements, material usage, product control, machine settings, etc.), control systems have to decide on the basis of data that they have to retrieve just in time. SOAP Web Services offer the possibility, in a simple way according to the SOA principle, to enable access to this data and thus to implement a decision-making process on the basis of highly up-to-date data. This achieves maximum efficiency and quality. Access to the PLCs I realized thru the OPC UA Client Plug-in.

Here you will find further information
about OPC Router and Plug-ins.

Plug-ins
Run a free test now