Reference, Daserver architecture – Omron ETHERNET DIRECT DR 170 14 User Manual
Page 67
Klinkmann Automation Omron Ethernet DAServer
65
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
CHAPTER 6
Reference
Contents
• DAServer Architecture
• Component Environments
DAServer Architecture
Note: DAServers are supported on Microsoft Windows 2000 and Windows XP only.
NetDDE protocol is not supported by DAServers.
This DAServer is a collection of components that work in concert to provide
communications access with hardware field devices. These components include:
• DAServer Manager: This is the Microsoft Management Console (MMC) snap-in, that is
part of the ArchestrA System Management Console suite of utilities, supplied with the
DAServer. It provides the necessary user-interface
for diagnostics, configuration, and activation.
• Client Plug-ins: These are the components that are added to a DAServer to enable
communications with clients. Examples are: OPC, DDE/Suitelink, and so on.
• DAS Engine: This is the library that contains all the common logic to drive data access.
• Device Protocol: This is the custom code provided by this DAServer to define the
communications with a particular device
.
DAServers
A DAServer is comprised of three physical parts (see the following figure). They are the
following:
• Plug-in Component(s): Responsible for communicating with clients.
• DAS Engine: This common component is used by all DAServers.
• PLC Protocol Layer, DAServer-specific: This component is responsible for
communicating with the hardware.