CM_Mappings Configuration Service Provider
The CM_Mappings Configuration Service Provider configures the URL mapping table that determines the network where the URL resides. You can configure URL exceptions using CM_Mappings - that is, you can use many URL patterns for one network.
It is necessary to provision a network GUID using the CM_Mappings Configuration Service Provider before provisioning anything that requires a network GUID. If the GUID already exists, it will be overwritten.
Note This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP) protocol. To provision devices using the OMA DM protocol, use the ACCESS Configuration Service Provider instead.
Note 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 following table shows the default settings. The default security role maps to each subnode unless specific permission is granted to the subnode.
| Permissions | Read/Write |
| Roles allowed to query and update setting | Manager |
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
.gif)
Characteristics
<MappingIndex>
Specifies settings for the <MappingIndex> parameter. Entries in the mapping table are provisioned and ordered by their MappingIndex value. When mapping URLs, the URL mapper searches the table, starting at the lowest table ID and moving up the list of values until a matching pattern is found. Entries do not need to be contiguous.The first 500 index numbers (0-500) are reserved for internal use only. Do not use these numbers. The order of the networks as specified by the index number in the mapping table reflects their relative priority in a descending order. Connection Manager uses the first matching network to establish a connection.
Entries with more specific pattern must be assigned a lower index number than more general entries. The index numbers 1000, 1200, 1400 and 1500 are used to map the most general patterns, as shown in the following table.
Parameter pattern value Network name *://*.*/* The Internet *://*/* My Corporate Network wsp://*/* WAP Network wsps://*/* Secure WAP Network To make a more specific entry map to a different network (GUID), the index of that entry should be lower than the entries in the default XML example.
Parameters
Network
Used in the <MappingIndex> characteristic to provide the Network GUID where the URL resides.The following table shows the default settings.
Permissions Read/Write Data type String Label Network GUID Roles allowed to query and update setting Manager Pattern
Used in the <MappingIndex> characteristic to provide the URL pattern in a wildcard pattern that is used to match the URL string. The string must be in canonicalized URL format. For example, a blank space in the URL should be converted to the escape sequence %20.The following table shows the default settings.
Permissions Read/Write Data type String Label URL Pattern Semantic Type url Roles allowed to query and update setting Manager
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
| Elements | Available |
|---|---|
| noparm | No |
| nocharacteristic | Yes |
| characteristic-query | Yes recursive query: Yes |
| parm-query | Yes |
Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | CM_Mappings Configuration Service Provider Examples for OMA Client Provisioning | Connection Manager Configuration
Send Feedback on this topic to the authors