Changes between Version 1 and Version 2 of HetDescriptions/jrf/tu_intro


Ignore:
Timestamp:
Aug 30, 2016 8:06:07 PM (8 years ago)
Author:
admin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HetDescriptions/jrf/tu_intro

    v1 v2  
    1111== Definitions of Terms ==
    1212
    13 * Control System --
    14   A Control System is a stand alone program that performs a set of functions. It may receive commands from other systems and will emit events containing information that it
    15   knows about.  It may send commands to other systems and may listen to events from other systems. A Control System
     13* Control System ---
     14  A Control System is a stand alone program that performs a set of functions. It may receive commands
     15  from other systems and will emit events containing information that it
     16  knows about.  It may send commands to other systems and may listen to events from other systems.
     17  Current Control Systems are tracker_server, tcs_server, pasServer, pfipServer, tcsGui, apcGui, and tcsnamed.
     18  Other Control Systems will be developed in the future to replace older operations systems.
    1619
    17 * Subsystems --
    18   A Subsystem
     20* Subsystems ---
     21  A Subsystem is essentially a smaller self-contained system with in a Control System. An example would
     22  be the Structure Subsystem with in the legacy Control System.
     23
     24* Route ---
     25  A Route is a Uniform Resource Identifier (URI) that is used by Control System clients to talk to other
     26  Control Systems. Commands and requests to Control System handlers are
     27  sent to the route address. The URI is of the form
     28  tcp://xxx.xxx.xxx.xxx:nnnnn where xxx.xxx.xxx.xxx is an IP address
     29  and nnnnn is a port number. For example, the Route to the tcs_server
     30  is tcp://192.168.66.31:30300. The 'tcp' is the protocol and may be a
     31  different protocol, however, all control systems within Tcs use the
     32  TCP protocol.
     33
     34* Event Route ---
     35  An Event Route is a URI that is used by a control system to emit
     36  events.  Clients and other control systems may listen to these events
     37  to obtain state information about the control systems.  The URI's port
     38  number is normally one higher than the control system route port. For
     39  example, the tcs_server route is on port 30300 and its event route is
     40  on port 30301.
     41
     42* Handler ---
     43  A handler is a function with in a Control System that may be run be
     44  a client.  A Handler is commanded via the Route to the Control System.
     45  When the Handler completes, a return message is sent to the client.