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.

SOAP Integration example

Example of SOAP Web Service Integration.

Achieve More with Combined Systems

Web Services aim at forming strong synergies between systems: When systems work together, they can achieve more. This is precisely the reason why businesses are focused on integrating systems and utilizing the power that is unleashed in manifold successful use cases. The OPC Router can give you quick access to system integration in production; for various applications.

Industrie 4.0 via Web Services

Web Services are often defined as standard interfaces for various powerful systems, such as ERP systems (SAP systems, Microsoft Navision, Pro Alpha, and others. WebServices facilitate crosslinking and Industry 4.0 network integration from an ERP system right down to production.

About the OPC Router

The OPC Router helps you connect your systems. Numerous plug-ins are available, which make the OPC Router to the ideal middleware in industrial settings.
Easy configuration, sophisticated monitoring and robustness are main distinguishing features of the OPC Router.

Linking Systems

SOAP Web Services are accessible through web protocols and it forms the foundation for an SOA infrastructure. With the OPC Router you can link them to different systems. That’s how easy it is:

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 Functions

The 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.


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.


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 Oracle, MySQL, Access, ODBC).

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.

More Plug-ins

How do Transfer Objects, Triggers and Browsing work?

The connections the OPC Router establishes between systems can be addressed with the core functions of the OPC Router.

Depending on the nature of the respective plug-in, functions vary, which is due to the functional scope of the respective connceted systems.

Run a free test now

Transfer Objects

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.

Trigger Functions

Prompting Connections

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.