AlarmScreenNg 0.9.6
|
The AS components are installed without any access control presets - any user is allowed to perform all actions available from the AS interface, including changing its configuration. Such mode of operation may be convenient for test and development setups, but is rarely appropriate for production systems.
It is expected that for production projects, different access rights will be assigned to different users. This section describes configuration actions that in most cases will be performed by administrators and system experts. Therefore, they are called 'admin settings' throughout this document.
Admin settings are available through the popup menu of the 'Settings...' button in the toolbar of the AS footer:
Access Control is probably one of the very first things to be configured after the AS is installed. Every action that can be performed from the AS EWO, or from other panels that come with it, is identified by a unique action name. See Action names for more information.
The following panel is used to edit the access rights required to execute different actions:
The table displays all action names and a 'short summary' of restrictions for each action.
Note that action names are used not only for access control, but also to identify the requested action in CTRL code, see Action names. For this reason, there are two action names in the table which are not subject to access control by their nature; there are no buttons for these actions in the Access column; instead the column just displays green cells.
For all other actions, the Access column displays a short summary of access control settings:
All actions are divided into two major categories, as indicated in the Fixed column of the table:
The functionality of the Add/Remove buttons (on the right of the table), as well as the Apply/Close buttons at bottom part of panel follow the typical conventions.
Clicking on the button in the Access column will open the following panel, allowing to edit access control restrictions for the clicked action:
The table contains the list of privileges in domains, required for executing the selected action. The Domain and Privilege columns use combo boxes for editing, allowing the user to select one of the domains defined in the project, and one of the privileges defined in the selected domain. If several domain/privilege pairs are specified, they will be joined by the OR operator, i.e. the action is allowed for all users who match any of the criteria.
Usually actions are initiated from elements of the UI, like buttons and menu items. The combo box below the table allows choosing how such widgets shall look for users who do not have the necessary privileges. Two possibilities exist:
The functionality the remaining buttons in the panel is self-explanatory.
The second item of the Admin Settings menu opens the the panel used to edit the popup menu that appears when the user clicks on the Alarm Table with the right mouse button:
The rows in the table contain the labels for the items in the popup menu. For the moment, only push button items are supported. The controls below the table are used to view/edit the processing method for the selected row.
Both CTRL functions must have certain signatures - see the EWO's Events. Examples can be found in the CTRL library AlarmScreenMenuJCOP.ctl.
In order to query archived alarms from ORACLE archives, the AS EWO needs to know how to connect to the corresponding DB. The following panel is used to configure the connection:
The Test button in lower left corner of panel can be used to try connection to ORACLE database using supplied connection parameters.
In addition to the database credentials, the AS EWO needs three more settings:
The standard (JCOP-style) configuration assumes that the project can contain a number of device/value specific help files that can be shown to the user. The locations and names for such help files must follow certain rules (see Help files). In addition:
The following panel, opened by clicking 'Help File types' in the Admin Settings menu, is used to modify the set of supported file types and to specify the command to open the files of a given type:
The configuration is performed directly in the table cells. If no specific command is written for a given file type (i.e. if corresponding cell says '(default)'), then the JCOP-default command will be used. The default JCOP commands are displayed for reference in the text fields below the table.