An [ALARM_MANAGER] section can be added to your application's Config.ini configuration file. The [ALARM_MANAGER] section defines the format of alarm records, and the format of the default Alarm Filtering dialog (see "VTS Developer's Guide: Filter Dialog Button".
The [ALARM_MANAGER] section may also be used for filtering alarm tags according to their Area property so that only the alarm tags belonging to certain areas are loaded on specific workstations. Alarm area filtering on specific workstations can be performed by adding the [ALARM_MANAGER] section to workstation.ini configuration files on specific machines. Information on alarm area filtering is described in Workstation.ini Alarm Area Filtering.
The [ALARM_MANAGER] section and its variables can be customized in one of three locations:
• In your application's Config.ini configuration file.
• In a custom AlarmManager.ini configuration file (see Introduction to AlarmManager.ini.
• In custom workstation.ini configuration files on specific workstations (see Introduction to Workstation.ini).
It is equally acceptable to configure the [ALARM_MANAGER] section and its variables in any of these locations; however, you must also direct VTS to the location from which you wish the [ALARM_MANAGER] section and its variables to be read by setting a related Config.ini [SYSTEM] section variable, called "AlarmExternalConfig" (see Config.ini [SYSTEM] Section Variables for Alarms).
• If AlarmExternalConfig is set to 0, VTS loads the [ALARM_MANAGER] initialization variables from Config.ini (or from a workstation.ini configuration file if the name of the workstation.ini file is the same as the name of the workstation on which it resides – for example, "MyWorkstation.ini" on the machine MyWorkstation.)
• If AlarmExternalConfig is set to 1, VTS loads the [ALARM_MANAGER] initialization variables from AlarmManager.ini (see Introduction to AlarmManager.ini).
Note: If it is your intention to have VTS read the variables from an AlarmManager.ini configuration file, be sure to save the AlarmManager.ini text file to your application directory in the upper-most application layer, as VTS always reads the information found in the first section found.
By default, the AlarmExternalConfig variable is set to 0, indicating that VTS should read the [ALARM_MANAGER] section and its variables from the Config.ini configuration file. Therefore, the [ALARM_MANAGER] section variables are described below.
Topics in this section: