ACCESS Configuration Service Provider
The ACCESS Configuration Service Provider specifies destination networks to which multiple connectivity objects and proxy or Virtual Private Network (VPN) connections can connect. It also specifies the URL domain mappings for each of these destination networks.
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.
ACCESS specifies one or more domains. The collection of these domains constitutes a destination network, which you can connect to through either multiple connectivity objects, for example the Internet, or through a specific connectivity object, for example Multimedia Messaging Service (MMS). ACCESS also supports scenarios in which multiple work networks can be accessed by different sets of network connectivity objects.
Because ACCESS enables you to specify multiple domains under each entry, you can use it to add as many URL exceptions as are required for each defined network, in addition to the standard URL mappings.
In addition to supporting destination network based on URL domain mapping, ACCESS also supports destination networks based on specific applications. If an application uses a magic URL (an URL beginning with a protocol other than http), the application can be mapped to a network using only the ACCESS Configuration Service Provider. Otherwise, an application must use the ConnMgrMapConRef API or a registry key (in addition to the ACCESS Configuration Service Provider) to map to a specific network.
Note This Configuration Service Provider is part of the OMA DM protocol, with some proprietary extensions, and must be used when provisioning devices using OMA DM. To provision devices using the OMA Client Provisioning (formerly WAP) protocol, use the CM_Mappings Configuration Service Provider and the CM_Networks Configuration Service Provider instead.
ACCESS mappings to metanetworks cannot be deleted using the Windows Mobile user interface, but network access points provisioned using the NAP configuration service provider can. When reprovisioning a network access point after it has been deleted, you must delete and reprovision the corresponding ACCESS mappings before reconfiguring the network using NAP.
The following image shows the management object used by OMA DM.
.gif)
ACCESS
The root node for ACCESS object. The following table shows the default settings.Format Node Roles allowed to query and update setting Manager AuthenticatedUser
Access Type Read/Write Occurs Once ACCESS/Internet
Specifies the domain names, application-specific connection preferences and port number-specific connection preferences for the Internet metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/Work
Specifies the domain names, application-specific connection preferences and port number-specific connection preferences for the Work metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/WAP
Specifies the domain names, application-specific connection preferences and port number-specific connection preferences for the WAP metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/SecureWAP
Specifies the domain names, application-specific connection preferences and port number-specific connection preferences for the SecureWAP metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/XXX/Domains
Specifies the domain names associated with the parent metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/XXX/Domains/DomainNameXXX/DomainName
A regular expression that specifies a set of URLs associated with the great-grandparent metanetwork. The suggested name of this node is DomainNameXXX, a numbered node beginning at zero. For example, if you require two regular expressions to specify the URLs associated with the Internet metanetwork, you would use two nodes, DomainName0 and DomainName1. You would specify the regular expression in the DomainName child of the numbered node. You can use any unique name for this node, but no spaces may appear in the node name (use %20 instead).The following table shows the default settings.
Format String Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/XXX/ConRefs
Specifies all connectivity objects, proxy connections and VPN connections associated with the parent metanetwork.The following table shows the default settings.
Format Node Roles allowed to query and update setting Manager AuthenticatedUser
ACCESS/XXX/ConRefs/ConRefXXX/ConRef
Specifies one single connectivity object, proxy connection or VPN connection associated with the great-grandparent metanetwork. The value must be the entry name of a connection, which may be the initial node on a path connecting the device to the specified destination network.The suggested name of this node is ConRefXXX, a numbered node beginning at zero. For example, if you have two connectivity objects associated with a metanetwork, you would use two nodes, ConRef0 and ConRef1. You would specify the name of the object in the ConRef child of the numbered node. You can use any unique name for this node, but no spaces may appear in the node name (use %20 instead).
The following table shows the default settings.
Format String Roles allowed to query and update setting Manager AuthenticatedUser
-See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | ACCESS Configuration Service Provider Example for OMA DM | CM_Mappings Configuration Service Provider | CM_Networks Configuration Service Provider
Send Feedback on this topic to the authors