Important:
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.
4/8/2010

This example can be used as a template to configure settings for the APPLICATION configuration service provider when w4 is the APPID. To use this example, you must replace the values as appropriate. For more information about the syntax of the provisioning file, see OMA Client Provisioning Files.

Code Example

This example shows how to use the w4 APPLICATION configuration service provider to provision a device for MMS. It includes PXLOGICAL and NAPDEF parameters to illustrate how the TO-NAPID and TO-PROXY parameters of the w4 blob map from the PROXY-ID parameter of the PXLOGICAL blob and the NAPID parameter of the NAPDEF blob of the provisioning XML.

Copy Code 
<wap-provisioningdoc version="1.1">
  <characteristic type="PXLOGICAL">
	 <parm name="PROXY-ID" value="adatumproxy"/>
	 <parm name="PROXY-PW" value="proxypasswd"/>
	 <parm name="PPGAUTH-TYPE" value="HTTP-BASIC"/>
	 <parm name="NAME" value="DefaultProxy"/>
	 <parm name="MASTER"/>
	 <parm name="PUSHENABLED" value="1"/>
	 <parm name="STARTPAGE"
value="wsp://www.adatum.com/start.wml"/>
	 <characteristic type="PXAUTHINFO">
		<parm name="PXAUTH-TYPE" value="HTTP-BASIC"/>
		<parm name="PXAUTH-ID" value="MMSusername"/>
		<parm name="PXAUTH-PW" value="MMSuserpassw"/>
	 </characteristic>
	 <characteristic type="PXPHYSICAL">
		<parm name="PHYSICAL-PROXY-ID" value="PROXY 1"/>
		<parm name="DOMAIN" value=" "/>
		<parm name="PXADDR" value="http://www.adatum.com/"/>
		<parm name="PXADDRTYPE" value="IPV4"/>
		<parm name="TO-NAPID" value="NAP1"/>
		<characteristic type="PORT">
		<parm name="PORTNBR" value="9201"/>
		</characteristic>
	 </characteristic>
  </characteristic>
   
  <characteristic type="NAPDEF">
	 <parm name="NAPID" value="NAPID1"/>
	 <parm name="BEARER" value="GSM-GPRS"/>
	 <parm name="NAME" value="Access Point 1"/>
	 <parm name="NAP-ADDRESS" value="AP1.gprs"/>
	 <parm name="NAP-ADDRTYPE" value="APN"/>
	 <parm name="DELIVERY-ERR-SDU" value="3"/>
	 <parm name="RESIDUAL-BER" value="70"/>
	 <parm name="SDU-ERROR-RATIO" value="6"/>
	 <parm name="TRAFFIC-CLASS" value="60"/>
	 <parm name="TRAFFIC-HANDL-PRIO" value="1"/>
	 <parm name="MAX-BITRATE-DNLINK" value="8"/>
	 <characteristic type="NAPAUTHINFO">
	 <parm name="AUTHTYPE" value="PAP"/>
	 <parm name="AUTHNAME" value="wwwmmmuser"/>
	 <parm name="AUTHSECRET" value="wwwmmmsecret"/>
	 </characteristic>
  </characteristic>
   
  <characteristic type="APPLICATION">
	 <parm name="APPID" value="w4"/>
	 <parm name="NAME" value="A. Datum Corporation "/>
	 <parm name="ADDR" value="http://www.adatum.mms.com/"/>
	 <parm name="TO-PROXY" value="adatumproxy"/>
	 <parm name="TO-NAPID" value="NAPID1"/>
  </characteristic>
</wap-provisioningdoc>

Remarks

For the device to correctly decode provisioning XML that contains the APPLICATION characteristic, it 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