Documentation

As most other objects in the SKOOR Engine (refer to chapter Export/import XML), templates may be exported and imported as XML files. This functionality is separately mentioned here as a reduced scope applies to templates compared to the standard XML export/import functionality.

Supported configuration objects for XML imports/exports of templates:

• Group
• Device
• Job
• Collector
• Process
• SLO

All other objects such as Schedulers, Alarm recipients and non template object references such as Alarm Parent to any non template instance are ignored and listed as unresolved dependencies.

The following rules apply to any XML import/export of templates:

• An error is generated when trying to import a template as an instance or vice versa
• It’s not allowed to share any template objects between two different templates
• Many further rules prevent the user from violating data integrity when dealing with imports.
• Descriptive messages help users to understand any violations

The configuration of XML exports/imports is identical to the XML export/import configuration described in chapter Export/import XML.

For XML imports of templates, 2 import modes are available:

• Update template
  • Like update for normal SKOOR objects, TIDs are assigned to the template objects so parameters or structure changes may be updated with a subsequent import
    
• Add template
  • The template is created without TIDs. No further updates are possible with XML imports