Metabase Configuration Service Provider
Use the Metabase Configuration Service Provider to add, modify, and remove entries from the metabase.
The metabase (metadata database) contains specific information about the Configuration Service Providers on a Windows® phone. 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 parameter could make use of the new security role information.
|The Metabase Configuration Service Provider is set to the Manager role by default. Changing this role could elevate privileges, making the metabase less secure.|
This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP Client Provisioning) protocol.
|Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.|
The Metabase Configuration Service Provider also supports the <language code> parameter, which allows localized text to be used on the device.
The following table shows the default settings for all parameters in this Configuration Service Provider. The default security role maps to each subnode unless specific permission is granted to the subnode.
Roles allowed to query and update setting
- <language code>
This parameter is used in the label characteristic to identify the text for the label in a specific language, and in the option characteristic to identify the code for that language. The following table lists the possible hexadecimal values for this parameter.
Arabic (Saudi Arabia)
English (United States)
Spanish (Traditional Sort)
Scottish Gaelic (United Kingdom)
English (United Kingdom)
Chinese (Hong Kong SAR)
Spanish (International Sort)
English (New Zealand)
Spanish (Costa Rica)
English (South Africa)
Spanish (Dominican Republic)
Spanish (El Salvador)
Spanish (Puerto Rico)
This parameter is used with the label and options characteristics as a decimal value that identifies access roles. Access roles determine which security roles are allowed to access a metabase entry. Each access role is a number formed by a bitwise or from the security roles that have access to the entry. More than one role can be set for the entry. This parameter cannot be used directly under the root characteristic.
For a list of possible security roles and corresponding role values, see Security Roles.
This parameter is used with the label and options characteristics to identify the type of data handled by this setting. This parameter cannot be used directly under the root characteristic. The following table lists the possible values.
Binary. The setting contains a stream of binary data (octet stream).
Boolean. The setting contains a boolean value.
Date. The setting contains a date. Both basic and extended date formats are supported.Note:The setting for date should be specified by date only, and not by date+time, according to the ISO-8601 standard.
If the value is a date, only the date portion will be returned.
Float. The setting contains a floating point value.
Integer. The setting contains an integer value.
Multiplestring. The setting contains a multiplestring value.
chr or string
String. The setting contains a string value.
Time. The setting contains a time. Both basic and extended time formats are supported.
The setting can specify either a date + time, or a time only format. If the date + time format is used then a 'T' must appear between the date and time as a delimiter.
This parameter is used with the local and options characteristics to represent the maximum number of characters the value of this parameter may have. This parameter cannot be used directly under the root characteristic.
This parameter is used with the label and options characteristics to identify the maximum value for the entry. This parameter cannot be used directly under the root characteristic.
This parameter is used with the label and options characteristics to identify the minimum value for the entry. This parameter cannot be used directly under the root characteristic.
This parameter is used with the local and options characteristics to specify whether the user is allowed to select multiple options. This parameter cannot be used directly under the root characteristic. The following table lists the possible values.
The user is not allowed to select multiple options.
The user is allowed to select multiple options.
If there are no options specified or if the control specified does not allow multi-select, then this parameter is ignored. If there are multiple values in the value attribute, this parameter is also set to 1.
This parameter is used with the local and options characteristics to identify the role(s) with Read/Write access to the entry. This parameter cannot be used directly under the root characteristic. The following table lists the possible values.
Nodes in Configuration Service Providers that support external transaction should not be set as write-only.
This parameter is used with the local and options characteristics. It allows the UI to provide a specialized control to better match the actual semantic type of the setting. The value of this attribute is not confined to a list. This parameter cannot be used directly under the root characteristic. Some of the values used by UI control are as follows: email, alphanumeric-password, numeric-password, currency, url, file, text, phone-number, invisible.
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
Top level: No
Top level: No
Use these elements to build standard OMA Client Provisioning (formerly WAP Client Provisioning) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to use the Microsoft custom elements, see OMA Client Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.