Promotic
WikipediaLinkedInYoutubeTwitterFacebook

Storage - page of object PmAlarmEvent

Description:
Setting the storage type of the data rising during the run of the application in a local alarm/event group. In case of a remote group (client) (see the configurator "Remote group (client)"), setting the type of getting the data for the history viewer, eventually the state viewer.
Configuration items:
Localized textsThe procedure of saving localized text to the disk:
Keeping the multi-language form with $.text - Saving partialy evaluated localized text in multi-language form with macro expression $.text. During the saving procedure the macro expression is partially evaluated except for the $.text. Especially the $.par parameters. During the procedure of data reading (alarm history viewer, the GetHistoryData method) the macros are evaluated again for the corresponding language.
Evaluate and save in a single specified language - Saving completely evaluated localized text in a single specified language. During the saving procedure, the macro expression ($.text) is evaluated completely. While reading the data (alarm history viewer, the GetHistoryData method) the macro expression is not being evaluated for the corresponding language.
LanguageSelected language in which the localized texts will be completely evaluated and saved.
Storage typeThe storage type of state changes of alarm/event items to the disk or the type of connection to the remote alarm/event group.
Not save - The history of state changes of alarm/event items is not saved to the disk. It is used locally for the implementation of an alarm/event group, for which only immediate state of alarm/event items is important and the history of state changes of alarm/event items is not so important.
Text file (*.al, *.ev) - The history of state changes of alarm/event items is stored to the disk in the form of a text file (*.al, *.ev). It is used locally for the implementation of an alarm/event group, where both the immediate state of alarm/event items and the history of state changes of alarm/event items are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
dBASE III file (*.dbf) - The history of state changes of alarm/event items is stored to the disk in the form of a dBASE III file (*.al, *.ev). It is used locally for the implementation of an alarm/event group, where both the immediate state of alarm/event items and the history of state changes of alarm/event items are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
MS SQL database - The history of alarm/event items status changes is saved into the SQL datbase in the form of database table. It is used localy for implementation of alarm/event group, where both current status of alarm/event items and history of alarm/event items status changes are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
Oracle database - The history of alarm/event items status changes is saved into the SQL datbase in the form of database table. It is used localy for implementation of alarm/event group, where both current status of alarm/event items and history of alarm/event items status changes are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
MySQL database - The history of alarm/event items status changes is saved into the SQL datbase in the form of database table. It is used localy for implementation of alarm/event group, where both current status of alarm/event items and history of alarm/event items status changes are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
FireBird database - The history of alarm/event items status changes is saved into the SQL datbase in the form of database table. It is used localy for implementation of alarm/event group, where both current status of alarm/event items and history of alarm/event items status changes are important. In case of the group with the set configurator Remote group (client) only the history viewer is functional (be means of file or database sharing).
Remote connection over WEB - It serves for the connection to the remote alarm/event group over WEB by the HTTP protocol. It is used purely at the group with the set configurator Remote group (client) and the history viewer and the state viewer is functional.
ColumnsConfigurations of individual columns. For each column two items are set:
- Save: flag if safe to the file (X=Save).
- Size: Size of saved data in the number of characters. This cannot be changed for some columns.
 

List of columns:

Id: meaning: preset state:
TimeOn Activation time save
TimeOff Inactivation time for alarm:save, for event:not used
TimeAck Acknowledge time for alarm:save, for event:not used
GlobalId Identifier of alarm/event item in group not save
Priority Priority of alarm/event item for alarm:save, for event:not save
Area Marking area of alarm/event item not save
Source Marking source of alarm/event item save
Desc Alarm/Event item description save
Comment Alarm/event item comment not save
UserNote Alarm/event item user note not save
AckerId Identification of the user making alarm acknowledgement not save
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice