Before running CMW server, the CMWSerevr manager must be added to the project and properly configured. Configuration is started by selecting Configuration -> CMWServer from UNCIOS application menu:
The following panel will shown up after selecting this item from the menu:
The main elements of this panel are:
Element | Description |
---|---|
Spin button labeled New manager number | select the number for new manager that will be added to the project> |
![]() | Creates internal DP for manager configuration and fills that DP with default settings for new manager. Note that CMWServer manager is not added to the project |
Local CMW Servers list | List of all CMWServer managers which are already added to the local project |
![]() | Delete all internal DPs for this manager (manager configuration, plus system integrity if this was configured for manager). Note that CMWServer manager is not deleted from the project if it was added |
Internal configuration | View/edit default settings which will be applied to all new CMWServer managers in the project |
Status visualization | Open the panel where one can see online the status of all CMWServer managers in the project (both in local project and in other projects forming distributed system) |
Let's consider default settings before adding new CMWServer manager to the project, the following panel is opened by clicking Internal configuration button shown on previous picture:
The following table describes default settings for CMWServer manager which can be edited:
Value | Description |
---|---|
Configuration path | The path to file with CMW server configuration (DPEs and corresponding CMW devices/properties). Note that file must lie in proj_path/data directory. The name of file can be any arbitrary name. |
CMW Server | The name of CMW server. This name will be registered in CMW name server(s), this name will be used by CMW clients to connect to server. Hence, the name of specific CMW server must be CERN-wide unique. The default name, shown in this panel, can be any name. |
Integrity period | When CMWSErver manager is running, it must periodically write the value to one of internal DPEs (heartbeat). In particular, system integrity uses this heartbeat DPE to check if CMWServer manager is alive or not. This value specifies heartbeat period.
|
CMW data tag name | Each property of device in this CMW server may contain two tags:
This is a common data tag name for all properties of all devices. |
CMW time tag name | All time tags in all propeties of all CMW devices have the same name (this is limitation of CMWServer manager, not of CMW itself). This is a common time tag name for all properties of all devices. |
EV response timeout | When SET request arrives from CMW client, this CMW server sends dpSet() request to Event Manager and waits for response from Event Manager. The response can be either 'success' or 'error', and only after receiving the EV response this CMW server sends response to client's SET request. This value is a time interval this CMW server waits for response from event manager.
|
Min. alarm duration | During operation of CMW server manager, some failures can occur; they must be reported by manager as alarms. One evident example of such events is overflow of internal queue(s) such that values from/to DPEs are lost. Usually such 'failure events' have relatively short duration: the queue is full right now, but just in fraction of millisecond next item from queue can be processed, and queue is not full again. This value determines minimum duration of 'bad' state of such alarm DPEs. With example of 1000 msec: even if 'queue full' condition only occured for franction of millisecond, the alarm DPE will have 'bad' state for at least 1000 msec. |
Disable partial setting | This flag determines how CMW server will react to 'partial' SET requests. If device property has two tags (data and time) and partial sets are disabled, then only client's SET requests, containing both data and time tags, will be accepted. |
These default settings are stored in dedicated internal DP in the project. The 'reload' button
If there are already some CMWServer managers configurations in the system, or after adding new one, the list of 'Local CMW Server' on the picture is not empty. Selecting the item in this list displays configuration for selected manager in the bottom part of panel:
Upper part of this panel was already considered before, let's consider now the bottom part of this panel. The numbered items on the picture above are:
Similar to default configuration, the configuration for specific manager is stored in dedicated internal DP. Reload button
The part of panel for editing settings has the following major differences from the panel for editing default settings:
Clicking on Status visualiation button in 'main' configuration panel opens the following panel:
Here all CMWServer managers in selected system are shown together with their statuses. The table contains one row per CMWServer manager, each row shows all critical status information for this manager:
Pressing right mouse button on the table pops up menu for manager in this table row:
Using this menu, usual commands for manager can be executed (start/stop etc.), plus settings for selected manager can be shown - the panel equal to the bottom part of this panel:
What is the reason for opening the configuration panel from this menu 'once more'? The answer is simple: in this panel one can select any system of distributed system, then opening configuration panel from the popup menu will show configuration of selected manager in selected system. There are some limitations for editing configuration of CMWServer manager in remote system: part of configuration related to the configuration file can't be edited.