In Microsoft Provisioning Framework (MPF), a procedure is a blueprint for executing the steps of a provisioning request. A procedure can be one of the following:
Every request contains a single procedure (which can, in turn, contain calls to other procedures). MPF executes each step in the order in which it appears. The XML structure of a procedure is defined in a provider namespace or derived from a combination of lower-level procedures. For specialized needs, you can write a custom procedure that chains calls to other procedures, usually from multiple providers.
Procedures are grouped into namespaces. In order for procedures to be available to incoming requests, their namespace must be registered in the configuration database.
Using Provisioning Manager or Configuration Database WMI Provider, you can configure the following procedure properties.
|Procedure name||Identifies the name of the procedure. You can change a procedure name at any time. Modifying a procedure name can cause problems if other procedures call it, however. If you modify a procedure name, be sure to update the XML of all other procedures that call that procedure.|
|Access type||A procedure is either public or private (default). A public procedure can be called from an incoming request outside of MPF, but a private procedure can only be called from within MPF.|
|Request type||Specifies which functions a procedure can invoke.
|Execute as||Specifies the user credentials with which MPF invokes the procedure. Only credentials previously defined in Provisioning Manager can be selected. This option does not display for read-only namespaces, such as the Error Provider namespaces. In addition, the field is not enabled unless at least one user credential exists in the configuration database. For more information on Execute as, see Basic authentication.|
|Audit||Specifies whether procedure calls are saved to the audit log.
This setting corresponds to the auditEnabled attribute in the
namespace XML procedure node.
In addition to marking a procedure for audit, you can also configure the audit level for procedure calls. For more information, see Administering provisioning engines in Provisioning Manager Help.
|Auto-generate performance counters||Specifies whether to automatically implement performance counters for the procedure. Note, however, that a performance counter does not show up in the performance monitor until the first time a procedure runs.|
|Save data for rollback||Specifies whether to automatically save the input data that
enables the rollback of a failed procedure.
|XML||Implements procedure steps for calling a provider or another procedure. You can modify a procedure's XML from Provisioning Manager, but this practice is not recommended. Instead, modify and test the XML outside of the production environment, then import it once testing is complete.|
|Security||Specifies who can execute each procedure and determines the permissions to allow or deny each user. By default, permissions propagate from a namespace to its procedures, so changes to permissions apply to all procedures. You can override this default behavior for individual procedures, however.|
For information on how a procedure works and how it is implemented in Microsoft Provisioning System, see How a procedure works and Procedure implementation in Microsoft Provisioning System. For information on requests, see Request architecture. For information on namespaces, see Namespace architecture. The Microsoft Provisioning Framework Software Development Kit (SDK) contains additional resources to help you implement procedures, requests, and namespaces. This includes the complete XML schema for all elements and information on how to implement providers. For more information on the SDK and how to use it, see Microsoft Provisioning Framework SDK.