APPLICATION Configuration Service Provider

  • Article

4/8/2010

This configuration service provider allows you to perform the following tasks:

  • Update application information
  • Update application protocol-related information.
  • Create a Device Management (DM) server account during the bootstrap process.
  • Rollback if configuration fails. A list of the created account names is maintained and if configuration fails, all created accounts are deleted.
  • Recovery Rollback. This is used for application uninstall. When an account is created the account name is handed back to Configuration Manager and Configuration Manager stores it in a file. When the application is uninstalled, Configuration Manager calls with those account names and they are deleted.

OMA considers each transport to be an application and requires a corresponding APPLICATION configuration service provider.

Note

This configuration service provider can be managed over the OMA Client Provisioning protocol.

The following list shows the supported transports:

  • w2, for adding a new favorite.
  • w4, for configuring Multimedia Messaging Service (MMS).
  • w7, for bootstrapping a device with an OMA DM account.
  • 110, for POP3
  • 143, for IMAP
  • 25, for SMTP

The APPID parameter differentiates these application transports. APPIDs must be registered with OMA.

This configuration service provider must be in the root of the provisioning document.

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

See Also

Concepts

Configuration Service Provider Reference for Windows Mobile Devices
w2 APPLICATION Configuration Service Provider
w7 APPLICATION Configuration Service Provider
E-Mail APPLICATION Configuration Service Provider