Provisioning Schema::context
Element that encapsulates transaction-specific contextual information for a provisioning request. This element is part of the provisioning schema of Microsoft® Provisioning Framework (MPF).
The context node has two uses in MPF. In requests, context encapsulates:
- Transaction context (TIP URL, transaction ID that MPF generates for an incoming request)
- Security context (security credentials used for authentication)
- Queue context (queue ID and failure handling attributes)
- Client context (ID that the calling user uses to track the request, client's locale ID)
When the Provisioning Engine executes the request, it generates a corresponding context child node in the executeXML node it passes to the called procedure. Here, the context node contains:
- Transaction context (same as above)
- Execute context (namespace name, procedure name, and source provider name)
- Security context (same as above)
- Client context (same as above)
- Error context (if the procedure executes within a catch block)
Parents
Children
clientContext (minOccurs="0" maxOccurs="1")
errorContext (minOccurs="0" maxOccurs="1")
executeContext (minOccurs="0" maxOccurs="1")
providerContext (minOccurs="0" maxOccurs="1")
queueContext (minOccurs="0" maxOccurs="1")
securityContext (minOccurs="0" maxOccurs="1")
transactionContext (minOccurs="0" maxOccurs="1")Example
<context> <clientContext clientTransactionId="53367B03-63D3-44ae-B8AD-C1E57E876E6C" /> <securityContext impersonate="0" sensitive="0" trusted="0" /> </context>See also
Top of Page
© 1999-2002 Microsoft Corporation. All rights reserved.