Technical information

4/32
Software 3
OPC data server software
OPC Factory Server
Architectures (continued) 0
Architectures supported (continued)
Remote access from an OPC .NET client
The .NET client application program and the OFS data server are on remote
stations. Communication between the client station and the OFS server is
conducted through the DCOM layer (Microsoft) via the OPC-DA protocol.
The .NET Microsoft compatibility of the OFS server has been developed to allow an
OPC .NET client to access OFS server items on an Intranet network via the OPC
.NET API interface.
This interface provides interoperability between existing OPC applications and
applications developed in the standard .NET environment.
Remote access from an OPC XML-DA client via HTTP
The client application program and the OFS server are on remote stations, using the
SOAP protocol to communicate via the Internet in conformity with the OPC XML-DA
or OPC UA specication of the OPC Foundation.
These two protocols are designed to overcome the limitations of COM/DCOM, thus
providing:
b A standardized interface for Windows and non-Windows client applications
b Beyond the Intranet perimeter, remote access via the Internet through rewalls
The OPC XML-DA specication is based on Web Services standards such as SOAP,
XML and WSDL (1). A SOAP client can access data on the OFS server via Intranet or
Internet using the SOAP protocol in conformity with the OPC XML-DA or OPC UA
specication of the OPC Foundation.
(1) SOAP: Simple Object Access Protocol
XML: Extensible Markup Language
WSDL: Web Services Description Language
Server
OFS station
Intranet
.NET client
Ethernet Modbus/TCP networkDCOM
Site server
and OFS
station
Symbol data
(Unity Pro,
Concept or PL7)
Industrial network
IIS
Internet
Industrial
PLCs
Remote client
application
program
Firewall
Presentation:
page 4/30
Setup:
page 4/33
Functions:
page 4/34
References:
page 4/35
Time stamping system:
page 4/36
2
1
3
4
5
6
7
8
9
10
2
1
3
4
5
6
7
8
9
10