Set alarm key fields for a hot backup pair

To synchronize alarm acknowledgements between the primary and backup providers, you must identify a combination of tag alarm record fields. This combination of fields generates a unique mapping key to the paired alarm records stored in each provider’s current alarm repository.

You can set alarm key fields and map alarms only for InTouch alarm providers.

The figure below shows a synchronized alarm acknowledgement request based on alarm record fields in a standard query.

A mapping key can be a combination of design-time and run-time alarm records. Design-time alarm records are based upon alarm properties of a tag when it is defined from the Tagname Dictionary.

For example, an alarm name field is known at design time because it takes on the name of the tag defined in the primary and backup node applications. QuickScripts or operators actions define or modify alarm properties stored as records while an application is running.

You can create a map key from any combination of design-time or run-time alarm record fields. The map key must select only a single record from each provider’s current alarm repository. The key field must create a unique query.

You use the Hot Backup Manager to create a mapping key list from alarm record fields.

Note: When you specify a Galaxy or Galaxy_<GalaxyName> alarm provider, both the Set KeyFields and the Map Alarms options are disabled.

Create an alarm field mapping list for a hot backup pair

1. Open the Alarm Hot Backup Manager. Do the following:

   1. In the Tools view, expand Applications.

   2. Double-click Alarm Hot Backup Manager.

2. Select a hot backup pair from the list.

3. Select Set Key Fields. The Select Key Fields dialog box appears.

   

4. In the Alarm Record Fields area, select the alarm record fields that you want to include in the mapping key list.

   The selected alarm record fields appear in the Selected Fields list box.

5. Select Design-Time or Run-Time for the alarm record fields you selected.

6. Select OK.

7. Restart WindowMaker.