Designing and Managing Behavior Models - Importing and Exporting NerveCenter Nodes and Objects - More About Exporting Behavior Models -
Exporting Behavior Models to a File      Exporting NerveCenter Objects and Nodes to Other Servers

More About Exporting Behavior Models

When you export a behavior model to another NerveCenter server or to a file, you export an alarm (or alarms) and all of the objects associated with that alarm. These associated objects include:

• Any object that can fire a trigger that can cause a transition in the alarm, including polls, masks, and other alarms.
• Any alarm that can be affected by a trigger fired by the alarm.
• Any properties used by any of the exported objects.
• Any property groups that contain any of the properties mentioned above.
• Any property groups used in AssignPropertyGroup() functions in polls, masks, and Perl Subroutine expressions. Also, any property groups used in SetAttribute alarm actions in alarm transitions. No properties are included from the group.
• All triggers fired by any exported object.
• The severities used by the exported alarms.
• Any Perl subroutines called by a Perl Subroutine action in an exported alarm.

NerveCenter does not export the following objects with behavior models:

• Alarms that listen to Clear Trigger alarm actions.
• Objects that fire triggers used only in Clear Trigger alarm actions of the exported alarms.
• Polls, trap masks, and OpC masks that fire triggers used only in Fire Trigger alarm actions of the exported alarms. (Perl subroutines in this situation are exported.)
• Perl subroutines that are not used as an action in one of the exported alarms.
• Action Router rules.