A server interface enables a SOAP (Simple Object Access Protocol) client application to communicate directly with a BMXNOR0200H Web server module.
SOAP / XML Communications
SOAP Web services are fully compliant with the W3C WS-I Web services standards. These services provide an open and standard communication means for control level devices to interact directly with information management applications using non proprietary SOAP protocol.
Web services are based on standards such as:
BMXNOR0200H SOAP Web services act as SOAP server interfaces. They allow developers to easily design client applications that can exchange data directly with BMXNOR0200H Web servers. Applications such as Microsoft.NET, SQL Server, Microsoft Office (Excel), IBM (WebSphere), SUN (Java, Eclipse), Lotus, Oracle, SAP, MES, ERP and so forth can be interfaced directly with BMXNOR0200H using SOAP Web services.
Two kinds of Web services are provided in BMXNOR0200H modules as SOAP server interfaces:
-
ModbusXMLDA: Web service to implement data access to Modbus variables,
-
SymbolicXMLDA: Web service to implement Symbolic data access.
The Web services provided by BMXNOR0200Hare compatible with the WS-I basic profile 1.1.
The following table describes the process of designing a SOAP client interface:
|
Stage
|
Action
|
|
1
|
Create the client application:
The development environment (for example, Visual Studio.net) connects to a WEB server module where it can access a list of available WEB services. The WEB server returns descriptions of the requested services as WSDL objects.
|
|
2
|
Develop the client application:
The developer integrates the WEB service APIs using the code retrieved in the previous stage as a WEB reference and generates the client application.
|
|
3
|
Execute the client application:
In run mode, the client application communicates in real time with the WEB server module using the SOAP protocol.
|
