1.4.1.1 Components

The system consists of four distinct programs:

• auc-md

  auc-md is the central server of the system and the nexus for overall operations of OpenAUC. It is currently runs only on Linux.

• auc-cd

  auc-cd is the client-server (or ``Cliever'') which is a client of auc-md and a server for the devices on the right hand side of Figure 1. It has both unix and Windows versions.

• mdclient

  mdclient is a client program which provides programmatic access to the auc-md, used for testing, operational, and development purposes and is unix only.

• md_device

  mddevice is a DLL embedded in the devices in Figure 1 which is the actual point of operation control and data acquisition. It currently is targetted for XPe.

• dvdriver.cpp

  dvdriver.cpp is the exemplar device driver. md_device.dll's facilities are used thru it.

auc-md and auc-cd are essentially peers from an operational perspective, the others are clients. Unless otherwise specified or clear from context (where it might refer to the overall system), ``MD'' refers auc-md and ``CD'' is used to refer auc-cd. mddevice instances are embedded in devices and can communicate with both servers but in actual operations it is assumed that the devices and auc-cd are in the same LAN but the auc-md may be remote.

The system has two distinct layers of communications, a high level one mediated by the rules sytem (CLIPS) and a low level one implemented with just boost, CEHT, XMLRPC-C and standard C++ stuff like STL. The rules system can operate either at the Cliever, at the MD or both. The rules enabled versions are auc-kb and auc-Cd.