One way of submitting requests to Microsoft® Provisioning Framework (MPF) is by calling methods of the client interfaces. This approach is appropriate for provisioning within a local data center.
The client is a COM object (mapsclient.dll) installed during MPF setup. An instance of the client must reside on any computer that sends requests to MPF. The client runs in-process to the calling application.
The client interfaces are IProvEngine and IProvQueue. IProvEngine submits real-time requests to provisioning engines. IProvQueue submits queued requests to queue managers. For scripting examples, see the documentation for the respective APIs.
Note The client only supports synchronous communication (no callback).
How MPF handles calls to provisioning engines and queue managers is configurable as follows.
You can implement client properties for both provisioning engine clients and queue manager clients, but you cannot implement different values for individual clients. These settings are also used by SOAP ISAPI.
Property | Description |
---|---|
Authentication Level | Authentication is the process of assigning a security identity
to each step in a provisioning request. MPF supports the following
authentication levels.
|
Exclusion Interval | Amount of time that a client will withhold requests to a failed
server.
Clients forward requests to queue managers and provisioning engines. If a queue manager, provisioning engine, or network connection experiences a failure, as indicated by specific error codes, MPF stops sending requests to the component for the amount of time specified in Exclusion Interval. The default interval is 300 seconds. This option minimizes unnecessary resource consumption of network bandwidth, CPU cycles, and other system resources during a failure. It also enables the provider to generate a more immediate error to alert the caller that the server is not available. You can also configure an individual request with an connectionExclusionInterval node or set an individual computer's ConnectionExclusionInterval registry value. For more information on these options, see HTTP and SOAP Provider. |
Capabilities | The Capabilities property identifies the COM+ cloaking
capability (none, static, or dynamic) to use when determining the
identity to pass from an MPF client to an external server. The
following table describes the supported cloaking capabilities. For
an extended discussion of cloaking and impersonation, see
"Cloaking" in MSDN®.
|
Connection Hold Time | Amount of time to hold connections open to unused provisioning engines and queue managers. Clients cache connections and then release them once the specified hold time elapses. The default hold time is 300 seconds. |
Impersonation Level | Indicates how much authority the client gives the provisioning
server to represent the calling user. The supported impersonation
levels are as follows:
|
Max Pool Size | This option controls the maximum number of simultaneous connections that clients hold open with provisioning engines or queue managers. MPF stores these open connections in a cache. The default value is 100 connections. |
Principal | Identifies the user principal name (UPN) of the account under which the provisioning manager or queue manager runs. Configuring the impersonation level of the client to support delegation requires a UPN for the engine or queue manager. The user name should be in the format username@domain, whereby domain is the Active Directory domain. The default user principal name is the user name specified during MPF setup. |