DMI Provider

[This is preliminary documentation and subject to change.]

The WBEM SDK includes a single DMI provider capable of acting as:

A dynamic class provider that enumerates all classes in the DmiNodes namespace and generates class definitions.
An instance provider that enumerates all instances of a particular class in the DmiNodes namespace.
An event provider that provides DMI events for the DmiNodes namespace.

A WBEM namespace must be created for each managed node. Each node's namespace resides in the \Default\DmiNodes namespace.

The DMI provider manipulates CIM class definitions. Therefore, the DMI Management Information Format (MIF) Components, Groups, and Attributes map to CIM classes, instances, and properties, respectively. For more information on how this mapping is done, see Mapping DMI to the CIM Schema

With the DMI provider, WBEM applications will be able to perform the following operations:

Access all DMI 2.0 Component, Group, and Attribute data.
Add and Delete DMI Components.
Add and Delete DMI Groups.
Add and Delete the Rows of a DMI tablular group.
Modify the writeable Attribute data.
Set the language mapping of a DMI Component.
Add or Delete Languages from a DMI Component.
Handle DMI Events.

The MOF file and executables for the DMI Provider are in the WBEM directory.

The software components of the DMI Provider are as follows:

DMI Provider Component	Description
WBEMDMIP.DLL	Main DMI Provider module responsible for schema translation, communication with WBEM and DMI, and construction of dynamic classes and instances.
WBEMDMIP.MOF	Sample MOF file shipped with the DMI Provider describing the DMI node namespace for the local node and registering the DMI Provider with WBEM.
MOTDMIENGINE.OCX	ActiveX Control used by the DMI Provider to establish communications and interactions with the DMI Service Providers.
WCDMI.DLL, WCDMIDCE.DLL, and WDMIUTIL.DLL	DLL modules used by MOTDMIENGINE.OCX to handle RPC connection and tear down with DMI 2.0 Service Providers on the local and remote nodes.