Share via


Delivering the Provisioning XML File to the Device

4/8/2010

After manufacture, you can physically deliver provisioning XML documents to Windows Mobile devices by sending the file over the air (OTA), placing the files in device ROM after deployment, or using delivery methods that require physical access to the device.

The following table shows how OTA delivery can be pushed to or pulled by the device.

Delivery method Comments

Push the file using a one-way WAP push and the OMA Client Provisioning protocol.

This type of push is recommended for bootstrapping a device. For more information, see Pushing XML OTA Using an OMA Client Provisioning Server.

Push the file using an OMA DM server and the OMA DM protocol.

This method provides a two-way communication for subsequent provisioning. For more information, see Pushing XML OTA by Using an OMA DM Server.

Push the file using a Service Indication (SI) message, or automatically download the file using Service Location (SL).

For more information, see Pushing XML OTA by Using Service Indication (SI) and Pushing XML OTA by Using Service Loading (SL).

Pull the provisioning XML in a .cpf file in response to an e-mail message or a Short Message Service (SMS) message.

For more information, see Pulling XML OTA by Using E-Mail and Pulling XML OTA in Response to an SMS Message.

Pull the provisioning XML in a .cpf file by downloading it over HTTP or HTTPS (Internet Explorer Mobile).

For more information, see Pulling XML OTA by Using Internet Explorer Mobile.

Delivery methods requiring physical access to the device by the operator or user include:

Application developers can use the DMProcessConfigXML function to apply XML changes. For more information, see Adding XML by Using DMProcessConfigXML.

For more information, see Options for Delivering Provisioning XML Files.

See Also

Concepts

How To Configure a Device After Manufacture