The devices section in the mcs-config.xml file contains the location of standard (and possibly custom) device repository policies. Within each of these elements you can specify either a jdbc-repository or a file-repository element. A JDBC repository entry contains the name of the project, whereas an XML repository contains the location of either the device repository directory, or the device repository file. Device repository files have the extension .mdpr.
The devices section in the mcs-config.xml file contains the location of standard (and possibly custom) device repository policies. Within each of these elements you can specify either a jdbc-repository or a file-repository element. A JDBC repository entry contains the name of the project, whereas an XML repository contains the location of either the device repository directory, or the device repository file. Device repository files have the extension .mdpr.
If the preload attribute is set to 'true' the repositories are loaded when MCS starts.
Device identification patterns are always preloaded.
In the logging element, you can configure MCS to log information from devices that are not recorded in the device repository, and to generate email reports to your device service provider. Refer to Device logging and the MCS configuration elements for further information.
<devices preload="false">
<standard>
<jdbc-repository project="NamedProject"/>
</standard>
<custom>
<file-repository location="/custom/devicerepositories/"/>
</custom>
<logging>
<log-file>device_log.txt</log-file>
<e-mail>
...
</e-mail>
</logging>
</devices>