Microsoft. Provisioning Framework (MPF) executes provisioning tasks in response to requests.
There are two types of requests: simple and trusted. Simple requests can contain data, security context, and the name of a procedure to call. For security reasons, simple requests are the standard approach for invoking MPF for both COM and HTTP/SOAP applications. In some situations, it can be desirable to submit a trusted request that explicitly defines the procedure steps as well as any data or security context. By default, only members of the groups Administrators, MPFAdmins, and MPFTrustedUsers can submit trusted requests. The schema for both kinds of requests is described in more detail in XML Schema for Requests.
There are two ways to submit requests:
- By calling methods in the client. This approach supports provisioning within a local data center (synchronous communication without callback). The client has two interfaces, IProvEngine and IProvQueue. IProvEngine contains methods for submitting real-time requests to a provisioning engine. IProvQueue has methods to submit and manage requests for processing by a queue manager. Both IProvEngine and IProvQueue have separate methods for submitting untrusted and trusted requests.
- Sending SOAP requests to the client via SOAP ISAPI. This approach supports communication between data centers for remote requests submitted over the Internet. SOAP ISAPI processes synchronous requests to provisioning engines. Requests sent to SOAP ISAPI require a SOAP header in the format described in SOAP Envelope Schema.
When MPF executes a request, it generates an executeXml node internally to pass the request data as XML to the called procedure in the respective provider. When a provider finishes processing a request, it returns an XML response node (containing either a successful result or an error) to the calling user.
Architecture, Authorization During Request Submittal
Top of Page
) 1999-2002 Microsoft Corporation. All rights reserved.