Creating MDI file templates

One way to implement the MDI interface is to create separate file templates to handle remove operations and create or update operations. The template contains the elements and attributes that are required to perform the operation, and can include hard-coded values for any value that is the same for all configurations. For example, if all of the configurations are for gas endpoints, then you can hard-code CommodityType=Gas.

In the CIS, schedule recurring export jobs to populate these templates with data. Create schedules that allow the remove operations to be processed before the create and update operations are processed. Separating the operations in this way helps reduce the potential for an MDI file to provide conflicting operations for the same device.

Each implementation is different and requires custom templates that work for that specific implementation. The samples in this section are provided as examples to illustrate the concept. The samples are not intended to be copied exactly for use in any actual implementation.

Note: The maximum length of the MDI file name is 41 characters.