APPLICATION Configuration Service Provider
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 (formerly WAP) protocol.
The following list shows the supported transports:
- w2, for adding a new favorite.
- 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 Open Mobile Alliance (OMA).
This Configuration Service Provider must be in the root of the provisioning document.
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | w2 APPLICATION Configuration Service Provider | w7 APPLICATION Configuration Service Provider | E-Mail APPLICATION Configuration Service Provider
Send Feedback on this topic to the authors