Platform registration database

For current version of Afecs (version-1.3) agent registration database is implemented as a set of files residing in the $COOL_HOME directory.

controlSessions.xml

controlSessions.xml file stores information about the registered run control sessions. The name of the runType with the corresponding run-number, running and active in the specific run control session is stored. Below is an example of the controlSessions.xml file:

<control>

<session>

<name>EmuTest</name>

<config>Emu</config>

<runnumber>37</runnumber>

</session>

<session>

<name>rctest</name>

<config>ROC2_DP</config>

<runnumber>1611</runnumber>

</session>

</control>

clientRegistration.xml

clientRegistration.xml file contains information on all real world physical clients registered with the Afecs platform. Any time a new clients requests representation within the run control platform an in formation about its host and port will be recorded in this file. Below is an example of the clientRegistration.xml file:

<registration>

<client>

<name>ROC6</name>

<hostname>ankaa.jlab.org</hostname>

<containerhost>ankaa.jlab.org</containerhost>

<portnumber>45400</portnumber>

</client>

<client>

<name>ROC2</name>

<hostname>ankaa.jlab.org</hostname>

<containerhost>ankaa.jlab.org</containerhost>

<portnumber>45400</portnumber>

</client>

<client>

<name>EB1</name>

<hostname>ankaa.jlab.org</hostname>

<containerhost>ankaa.jlab.org</containerhost>

<portnumber>45401</portnumber>

</client>

<client>

<name>ER1</name>

<hostname>ankaa.jlab.org</hostname>

<containerhost>ankaa.jlab.org</containerhost>

<portnumber>45402</portnumber>

</client>

</registration>

config directory structure

config directory in the platform registration database has the following sub-directory structure:

• • config

    • Control

      • <top level configuration files>

    • Component

      • <runType specific sub-directories>

        • <component specific configuration files>

    • State

      • <state machine specific directories>

        • <state machine specific states>

    • Service

      • <state machine specific directories>

        • <state machine specific state transitioning services>

    • Process

      • <runType specific sub-directories>

        • <component related process description files>

    • Option

      • <runType specific sub-directories>

        • <runType specific option description files>

    • Plugin

      • <plug-in description files>

Configuration/description files are written using control oriented ontology language (COOL).