Using Resource and Device Templates

Top  Previous  Next

It may be often necessary to use the same configuration for more than one Device or system resource (e.g. alert or report). AggreGate uses two methods for allowing to set up similar configuration for different objects:

Replication of configuration
Cloning objects

Sometimes you may want several Devices or resources to be used as sources for cloning. These resources are disabled and do not perform any activities within the system (e.g. a disabled alert will never be raised). Such resources are called templates.

This article describes how to create Device templates for quickly setting up devices with similar configuration. The same method may be used for making templates for any other resource type.

1. Creating a Group to store templates

First, let's create a Device Group to store our templates. This step is not necessary but it may be useful for separating active devices from templates.

In the System Tree of AggreGate Client, right-click Device Groups (st_groups) and select Create Group (cm_create):

ht_templates_1

Enter group Name and Description. Check Hide Members From Primary Location to separate templates from normal devices:

ht_templates_2

Click OK to create new group.

2. Creating a template

We need to clone a Device to use its copy as a template.

Right-click on the Device (st_device) that you want to be used as a template and select Make Copy (cm_make_copy):

ht_templates_3

Enter a name and description for the template:

ht_templates_4

Click OK to proceed. Now we have a new created normal (active) Device. Let's convert it to a template by suspending it. Right-click the Device (st_device) and select Edit Device Properties (cm_device_properties):

ht_templates_5

Switch to General Device Properties (var_properties) tab and check Suspend Device:

ht_templates_6

Click OK to suspend the Device. Its icon will become gray to indicate that it's not active anymore:

ht_templates_7

note_further-wt

The methods for deactivating a system resource when converting it to to a template may differ. Alerts, trackers, and most of other "active" resources have an Enabled property. It must be switched off when resource is used as a template. Non-active resources, i.e. resources that do not perform any activities themselves (such as reports), do not need deactivation.

note_tip-wt

Our template is just a normal suspended device for AggreGate. Another reason to suspend a Device (other than make a template out of it) is to temporarily pause all operations with a certain piece of hardware.

Now drag our template and drop it to (over) the Device Templates group (st_group):

ht_templates_8

The template will be added to the group:

ht_templates_9

3. Using the template

To create a new Device based on a template, we need to clone the template itself:

Right-click it and select Make Copy (cm_make_copy)
Enter name and description for the Device to be created
Click OK to create the Device

Finally, it's necessary to activate the new Device:

Right-click the Device and select Edit Device Properties (cm_device_properties)
Switch to General Device Properties (var_properties) tab and check Suspend Device
Click OK to save properties

Your new Device, based on the template, will now operate normally:

ht_templates_10

note_tip-wt

Another method to use a template is drag-and-dropping a template to any "container" context and executing Create From Template action.