Revision 7.10
2/28/2012
Figure 73. Result of running the inspectdataserver function.
The inspectdataserver function is the primary method for monitoring Data Server’s
behavior and the place to start when diagnosing Data Server problems.
3. Type controlC followed by the Q key to stop the realtime display of the log contents
and close the shell window.
7.5 Configuring glider data Managed by Data Server
A user can specify the data to be stored by Data Server using file dataServerState.xml
in folder /var/opt/gmc. For example, the dataServerState.xml file in Figure 74
configures a Data Server to store data from two gliders (wt01 & wt02) accessed from
two Dock Servers (running on localhost & on machine with IP address 172.16.2.206). If
no gliders are specified, then data from all available gliders on the specified Dock
Servers is stored. Also, if no Dock Server is specified, then data from any Dock Server
running on the same machine as the Data Server is stored. Restarting Data Server with
this configuration will ensure that only data from the specified Dock Servers and gliders
is stored, which is useful if the total data stored by Data Server needs to be limited.
Previously stored data from other gliders remains on the Data Server.
The <parser> element defines where
dbd2asc
, the application used for parsing the
content of glider data files, is stored. Typically, this need not be updated since
dbd2asc
is placed in the specified folder when the Data Server is installed.
The <insertPause> element defines a minimum time (in milliseconds) that the Data
Server pauses between database record inserts. This can be useful when a high level
Page 103 of 228