DAQ network schematics
by
Daniel Sentenac
—
last modified
2009-03-10 08:41
Daq network schematics can be accessed through the Web HWII interface
Daq network schematics can be accessed through the Web HWII interface. The latter contains a link to the CFGDB database which contains information about the server configuration. In general, one may query for a machine name to access them. Two types of information are provided, the process list running on a machine and the process interdependency from the DAQ point of view.
Lets suppose we want to know about olserver1. In the HWII interface we search the alia/name olserver1 in the search page to obtain the location of the machine in the Integratrion Chain :
![olserver1 process list](resolveuid/08ec88e5e3454b749a3296a4db86c229)
Then, by clicking in the circle close to olserver1 one obtains the process list running on olserver1:
![olserver1](resolveuid/71e32f8a14ad5bcde24a278a43cd1adb)
FbmMain itself is in blue meaning that this process controls a share memory segment.
Then, by clicking on a server name one obtain the DAQ dependency with other processes running on other machines. For example the FbmMain dependency is:
![FbmMain DAQ links](resolveuid/0c13c82f4caed4fc9ab1dee60279599b)
Here we can see that the FbMain accept two input server using Cm communication from olserver5, and delivers data to several Alp servers on the same machine.
More possibilities are:
1) access to diagrams with more then one depth level.
2) access to the Cfg file of any process
3) access to the log file of a given process
Lets suppose we want to know about olserver1. In the HWII interface we search the alia/name olserver1 in the search page to obtain the location of the machine in the Integratrion Chain :
Then, by clicking in the circle close to olserver1 one obtains the process list running on olserver1:
FbmMain itself is in blue meaning that this process controls a share memory segment.
Then, by clicking on a server name one obtain the DAQ dependency with other processes running on other machines. For example the FbmMain dependency is:
Here we can see that the FbMain accept two input server using Cm communication from olserver5, and delivers data to several Alp servers on the same machine.
More possibilities are:
1) access to diagrams with more then one depth level.
2) access to the Cfg file of any process
3) access to the log file of a given process