This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This example shows how to use the w7 APPLICATION configuration service provider to create an OMA DM account during the bootstrap process. W7 is the APPID.

Code Example

Copy Code
<wap-provisioningdoc version="1.1">
  <characteristic type="APPLICATION">
	<parm name="APPID" value="w7"/>
	<parm name="PROVIDER-ID"
	<parm name="NAME" value="Mgmt Server"/>
	<parm name="ADDR"
	<parm name="ROLE" value="24"/>
	<characteristic type="APPAUTH">
	<parm name="AAUTHLEVEL" value="APPSRV"/>
	<parm name="AAUTHTYPE" value="DIGEST"/>
	<parm name="AAUTHNAME" value="clientname"/>
	<parm name="AAUTHSECRET" value="clientsecret"/>
	<parm name="AAUTHDATA" value="clientnonce"/>
	<characteristic type="APPAUTH">
	<parm name="AAUTHLEVEL" value="CLIENT"/>
	<parm name="AAUTHTYPE" value="DIGEST"/>
	<parm name="AAUTHSECRET" value="serversecret"/>
	<parm name="AAUTHDATA" value="servernonce"/>
  <! — other characteristic -- >


For the device to decode correctly, provisioning XML that contains the APPLICATION characteristic must support OMA Client Provisioning version 1.1.

One provisioning XML file typically contains configuration information for multiple configuration service providers. To use this example, you must replace the values as appropriate, and add the node as a child of the OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

See Also