Share via

Transactioning Scheme

  • Article

Send Feedback

Windows Mobile-based devices support transactioning and rollback of configuration changes on the device by using either the Configuration Service Provider or Configuration Manager.

The following table shows the transactioning modes that the Windows Mobile supports.

Transaction Mode Description
Internal Transactioning The Configuration Service Provider supports transactioning. The following list shows the requirements for the Configuration Service Provider to support Internal Transactioning:

  • The Configuration Service Provider tracks and stores rollback information and is used to execute a rollback. It does not need to support querying settings.

    Note   Although query is not required for Internal Transactioning, the Configuration Service Provider must still support parm-query and characteristic-query. The only time this is not required is if querying is not supported for security purposes, or if settings are WRITE ONLY.
  • The read/write permission flags for the Configuration Service Provider are set to WRITE ONLY.
External Transactioning The Configuration Manager supports transactioning rather than the Configuration Service Provider. Compliance with External Transactioning is the easiest and most convenient way to develop a Configuration Service Provider. .

The following list shows the requirements for the Configuration Service Provider to support External Transactioning:

  • Support generation of valid responses to parm-query element and characteristic-query element for all settings that the Configuration Service Provider manages.
  • The read/write permission flags for the Configuration Service Provider are set to READ AND WRITE or READ ONLY.
  • The Metabase stores the value of the flags as part of the security information regarding the settings that the Configuration Service Provider manages.
  • The Configuration Service Provider returns values to the Configuration Manager in the mirrored query document.
  • If the Configuration Service Provider supports deletion of group settings by nocharacteristic element, it must support recursive characteristic-query. The mirrored query document becomes the basis for the rollback mechanism.

A rollback returns the device to its previously known and stable state when a transaction failure occurs.

The execution of a configuration request may require interaction with many different Configuration Service Providers. In this case, the transactions are processed serially. Successful completion of all configuration transactions is required. If a single transaction section fails, the entire transaction is rolled back to the Configuration Service Provider by means of either Internal Transactioning or External Transactioning.

For example, a configuration document could be sent to the device that attempted to change a key in the registry and then move a file. The security model implemented in the device will help protect all these operations. 'If the configuration document attempts to change a registry key to which it does not have access, Configuration Manager reports an error on this transaction. Because one section of the document has failed, the entire document and any changes it attempted to make are rolled back. The device is now in the exact state it was in before the configuration document reached the device.

See Also

Configuration Manager

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.