Transactioning Scheme
Smartphone and Pocket PC support transactioning and rollback of configuration changes on the device by using either the CSP or Configuration Manager. A rollback returns the device to its previously known and stable state when a transaction failure occurs. When supported by the Configuration Service Provider, transactioning is referred to as Internal Transactioning. When supported by Configuration Manager, transactioning is referred to as External Transactioning.
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. These operations are all protected by the device's security model. 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
Last updated on Friday, April 22, 2005
© 2005 Microsoft Corporation. All rights reserved.
Send feedback on this topic to the authors.