Metabase Configuration Service Provider Examples for OMA Client Provisioning
4/8/2010
The metabase (metadata database) contains specific information about the Configuration Service Providers on a Windows Mobile device. The metadata includes settings, possible values, information about how to display parameters that are configurable through certain Configuration Service Providers, role requirements and mappings for each setting and Configuration Service Provider, and other relevant information about them. Individual settings can be queried, updated, or deleted; however, top-level query and deletion is not supported.
Each Configuration Service Provider setting is updated as a metabase configuration file is processed. This allows new setting values in subsequent settings within the file to be used. For example, a security setting could be changed so that the next parm could make use of the new security role information.
.gif "Bb737576.security(en-us,MSDN.10).gif") Security Note: |
|---|
| The Metabase Configuration Service Provider is set to the Manager role by default. Changing this role could elevate privileges, making the metabase less secure. |
The Metabase Configuration Service Provider also supports the <language code> parm, which allows localized text to be used on the device.
The following XML examples can be used as templates to configure settings for the Metabase Configuration Service Provider. Below the Metabase characteristic type, replace the value for each parm and characteristic type with values that correspond to your system.
Note
Characteristics or parameters for the FileOperation Configuration Service Provider, Metabase Configuration Service Provider, and Registry Configuration Service Provider can contain an additional attribute called "translation". The two values for this attribute are "filesystem" and "install". A translation of type "filesystem" causes all file paths to be canonicalized (that is, double backslashes are removed). A translation of type "install" includes all the translations done for "filesystem", but also translates all CE Strings (for example, %CE2%) into the correct file path for the device. Cabwiz will automatically add the appropriate translation to file operations and registry keys in an .inf file.