• Home
• Read
• Software
• Links

How To Configure DaqKit2 server

Setting up database

Before first tart  of the server we need to set up database. Information about DCOPS, ports, lasers etc. Information about these things is written to the XML file with custom name. Initialization of the database is launching special tool which converts this XML file into the database.

Typical XML file with that information looks as follows:

<data>
 <port number="1" address="ppdcmsts.fnal.gov:7001" type="NETWORK" />
 <port number="2" address="ppdcmsts.fnal.gov:7002" type="NETWORK" />
 <port number="3" address="" type="FAKE" />
 <port number="4" address="/dev/ttyS0" type="HARDWARE" />

 <slm name="SLM-1" >
 <dcops cardNumber="1" portNumber="1" />
 <dcops cardNumber="2" portNumber="1" />
 <dcops cardNumber="3" portNumber="1" />
 <dcops cardNumber="4" portNumber="2" />
 <dcops cardNumber="5" portNumber="2" />
 <dcops cardNumber="6" portNumber="2" />
 <dcops cardNumber="7" portNumber="2" />
 </slm>

 <slm name="SLM-1" >
 <dcops cardNumber="21" portNumber="1" />
 <dcops cardNumber="22" portNumber="1" />
 <dcops cardNumber="23" portNumber="1" />
 <dcops cardNumber="24" portNumber="2" />
 <dcops cardNumber="25" portNumber="2" />
 <dcops cardNumber="26" portNumber="2" />
 <dcops cardNumber="27" portNumber="2" />
 </slm>

 <transfer name="TRF-1" >
 <dcops cardNumber="11" portNumber="3" />
 <dcops cardNumber="12" portNumber="3" />
 <dcops cardNumber="13" portNumber="3" />
 <dcops cardNumber="14" portNumber="4" />
 <dcops cardNumber="15" portNumber="4" />
 <dcops cardNumber="16" portNumber="4" />
 <dcops cardNumber="17" portNumber="4" />
 </transfer>

 <transfer name="TRF-2" >
 <dcops cardNumber="111" portNumber="3" />
 <dcops cardNumber="112" portNumber="3" />
 <dcops cardNumber="113" portNumber="3" />
 <dcops cardNumber="114" portNumber="4" />
 <dcops cardNumber="115" portNumber="4" />
 <dcops cardNumber="116" portNumber="4" />
 <dcops cardNumber="117" portNumber="4" />
 </transfer>

</data>
sd
 

In here elements' names:

• port -  serial port. "number" attribute should be unique in the system. "address" - file name  if port is hardware (i.e. we server works with serial port on the machine), string like "<hostname>:<port>" - if we work with Cyclade termainal server, empty string like "" if the port is fake. Type of the port could be "HARDWARE", "NETWORK" or "FAKE"
• slm - SLM line. This is projection of the real SLM line into the bases. Only attribute - "name". It should be unique in the system. This element contains dcops elements.
• transfer - Transfer line. It, as slm, contains dcops elements and has unique "name" attribute.
• dcops - elements which provide information about dcops. All we want to know is card number (attribute "cardNumber") and port this dcops is connected to (attribute "portNumber" - is a kind of reference to one of the port already listed in this file).

Order in which elements occur in this file doesn't matter.

After file is create you should start XML2DBUtil tool. This tools converts all information from XML file to the HSQLDB database. In order to start this tool:

java -cp <list of JAR  files> gov.fnal.cms.daqkit.util.XML2DBUtil <filename>

Where parameter are next:

• list of JAR files -     list of java archive libraries. Usually all libraries are in the "lib" firectory.
• filename -     XML file contains information about DCOPS, SLM lines, Transfer lines, ports, lasers etc.
  

Note that this tool drops database tables. So, information stored in the database before launching this tool is lost.