The following page elaborates on the configuration information – its XML representation and how the configuration should be applied. The root element of the XML configuration is <configurations>. It is a required element with one or many <configuration> elements.

<configuration>

The <configuration> is a required element and describes one configuration. It has required attribute "uid", which specifies the configuration UID. The following example shows the definition of configuration with UID "Custom Configuration":

<configuration uid="Custom Configuration">

It is a good practice to have the UIDs of the configurations in one namespace.

The <configuration> element has the following child elements – <config-priority>, <config-retry>, <device-filter>, <device-config> and <items>.

<config-priority>

The <config-priority> is an optional child element. It describes the configuration priority – if set of configurations matches a device, which one to be applied. The default priority is 0 and it is the lowest priority. It is not possible to have negative value. A larger number means higher priority. The <configuration-priority> tag has required attribute "value", that specifies the configuration priority.

When a set of configurations matches the Device, the configuration priority is important to choose which configuration to be applied . When a set of devices matches one configuration, then all devices are configured in a random order.

<config-retry>

The <config-retry> is an optional element and describes how the configuration to be applied. The <config-retry> tag has the following optional attributes:

• "count" – the number of retry attempts to apply the configuration. The "count" can not be negative number, expect -1 that means infinity number of attempts. The default value is 2.
• "interval" – the interval in milliseconds between attempts. The default value is 6000 milliseconds.
• "shouldResume" – defines whether to re-apply the whole configuration or only the non-configured part yet in case of failure. The default resume policy is true, which resumes the configuration from the failed point.

The following example shows how to describe a configuration with UID "Custom Configuration" and priority 5. If the configuration fails 3 times the Device Access tries to reconfigure the device in interval of 2000 milliseconds and resumes the configuration from the failed point.

<configuration uid="Custom Configuration">

  <config-priority value="5" />

  <config-retry count="3" interval="2000" shouldResume="true" />

</configuration>