Creating a provisioning.xml file

Using a text editor or an XML editor that does not insert any proprietary tags, you can create a provisioning file for an asset that is running an Axeda® Agent. You can name the file anything you like, as long as its extension is "xml". Remember that, when configuring the File Watcher in Axeda® Builder, you must specify a File Hint of "provisioning" (case insensitive) so that the Axeda® Platform knows how to process the file.

Important!

When choosing names for properties, you can use a maximum of 100 characters for each property name.

When assigning values to the properties that will create the hierarchy, make sure that the fully qualified path name of the asset group will not exceed 4000 characters. If the fully qualified path name exceeds 4000 characters, the asset group is NOT created. This limitation is a limitation of the database.

You can use special characters when assigning values to properties. However, if you use the forward slash character (/) in a property value, the Platform automatically replaces that slash with a vertical bar (|) or "pipe" when creating the asset group from that property value. The property value retains the forward slash character when displayed in the Properties page of the Asset wizard or Gateway wizard of the Configuration application.

In the example file below, the combination of //<Parent_Asset_Group>/VALUE_1/VALUE_2/VALUE_3 cannot exceed 4000 characters or the VALUE_3 asset group will not be created.

Here is a sample provisioning.xml file that you can copy and use for your assets and Agent projects; the XML lines for properties and property values (for dynamic group definitions) appear in this type face: Where you see variables (for example, "$USER_INPUT_CUSTOMER_1$"), substitute actual values that you want to pass to the Enterprise Server.

<SetProvisioning>

<Customer>$USER_INPUT_CUSTOMER_1$</Customer>

<Location>

<Name>$USER_INPUT_LOCATION_1$</Name>

<Line1>$USER_INPUT_ADDRESS_SET1_1$</Line1>

<Line2></Line2>

<City>$USER_INPUT_ADDRESS_SET1_2$</City>

<State>$USER_INPUT_ADDRESS_SET1_3$</State>

<Zip>$USER_INPUT_ADDRESS_SET1_4$</Zip>

<Country>$USER_INPUT_ADDRESS_SET1_5$</Country>

<Region></Region>

</Location>

<Properties>

<Property>

<Name>PROPERTY_1</Name>

<Value>VALUE_1</Value>

</Property>

<Property>

<Name>PROPERTY_2</Name>

<Value>VALUE_2</Value>

</Property>

<Property>

<Name>PROPERTY_3</Name>

<Value>VALUE_3</Value>

</Property>

</Properties>

</SetProvisioning>