Edit

Creating a WMI Method

  • Article

To create a WMI method, define the input and output parameters for the method. The input and output parameters are represented by a special WMI system class __PARAMETERS. For more information, see Calling a Method and Writing a Method Provider.

The following sections are discussed in this topic:

Creating a WMI Class Method in MOF

In WMI, provider methods are generally distinct actions related to the object that the class represents. Rather than change the value of a property to execute an action, a method should be created. For example, you can enable or disable a network information center (NIC) that is represented by Win32_NetworkAdapter by using the Enable and Disable methods. While these actions can be represented as a read/write property, the recommended design is to create a method. Alternatively, if you want to make a state or value visible for the class, then the recommended approach is to create a read/write property rather than a method. In Win32_NetworkAdapter, the NetEnabled property makes the state of the adapter visible but changes between states are executed by the Enable or Disable methods.

Class declarations can include the declaration of one or more methods. You can either choose to inherit the methods of a parent class, or implement your own. If you choose to implement your own methods, you must declare the method and mark the method with specific qualifier tags.

The following procedure describes how to declare a method in a class that does not inherit from a base class.

To declare a method

  1. Define the name of your method between the curly braces of a class declaration, followed by any qualifiers.

    The following code example describes the syntax for a method.

    [Dynamic, Provider ("ProviderName")]
class ClassName
{
    [Implemented] <ReturnType> <MethodName>
        ([ParameterDirection, IDQualifier] 
        <ParameterType> <ParameterName>);
};

  2. When finished, insert your Managed Object Format (MOF) code into the WMI repository with a call to the MOF compiler.

    For more information, see Compiling MOF Files.

The following list defines the elements of the method declaration.

Provider

Links a specific provider to your class description. The value of the Provider qualifier is the name of the provider, which tells WMI where the code that supports your method resides. A provider should also mark with the Dynamic qualifier any class that has dynamic instances. In contrast, do not use the Dynamic qualifier to mark a class that contains a static instance with Implemented methods.

Implemented

Declares that you will implement a method, rather than inherit the method implementation from the parent class. By default, WMI propagates the implementation of the parent class to a derived class unless the derived class provides an implementation. Omitting the Implemented qualifier indicates that the method has no implementation in that class. If you redeclare a method without the Implemented qualifier, WMI still assumes that you are not going to implement that method, and invokes the parent class method implementation when called. As such, redeclaring a method in a derived class without attaching the Implemented qualifier is useful only when you add or remove a qualifier to or from the method.

ReturnType

Describes what value the method returns. The return value for a method must be a Boolean, numeric, CHAR, STRING, DATETIME, or schema object. You can also declare the return type as VOID, indicating that the method returns nothing. However, you cannot declare an array as a return value type.

MethodName

Defines the name of the method. Every method must have a unique name. WMI does not allow two methods with the same name and different signatures to exist in one class or within a class hierarchy. As such, you also cannot overload a method.

ParameterDirection

Contains qualifiers that describe if a parameter is an input parameter, output parameter, or both. Do not use the same parameter name more than one time as an input parameter or more than one time as an output parameter. If the same parameter name appears with both the In and an Out qualifiers, the functionality is conceptually the same as using the In, Out qualifiers on a single parameter. However, when using separate declarations, the input and output parameters must be exactly the same in all other respects, including the number and type of ID qualifiers, and the qualifier must be the same and explicitly declared for both. It is strongly recommended to use the In, Out qualifiers within a single parameter declaration.

IDQualifier

Contains the ID qualifier that uniquely identifies the position of each parameter within the sequence of parameters in the method. By default, the MOF compiler automatically marks parameters with an ID qualifier. The compiler marks the first parameter with a value of 0 (zero), the second parameter a value of 1 (one), and so on. If necessary, you can explicitly state the ID sequence in your MOF code.

ParameterType

Describes what data type the method can accept. You can define a parameter type as any MOF data value, including an array, schema object, or reference. When using an array as a parameter, use the array as unbound or with an explicit size.

ParameterName

Contains the name of the parameter. You can also choose to define the default value of the parameter at this point. Parameters lacking initial values remain unassigned.

The following code example describes parameter listing and qualifiers.

[Dynamic, Provider ("ProviderX")]
class MyClass
{
    [Implemented] 
    sint32 MyMethod1 ([in, id(0)] sint32 InParam);
    [Implemented] 
    void MyMethod2 ([in, id(0)] sint32 InParam, 
       [out, id(1)] sint32 OutParam);
    [Implemented] 
    sint32 MyMethod3 ([in, out, id(0)] sint32 InOutParam);
};

The following code example describes how to use an array in a MOF parameter.

[Dynamic, Provider ("ProviderX")]
class MyClass
{
    [Implemented] 
    sint32 MyMethod1 ([in, id(0)] Win32_LogicalDisk DiskParam[]);
    [Implemented] 
    sint32 MyMethod2 ([in, id(0)] Win32_LogicalDisk DiskParam[32]);
};

The following code example describes using a schema object as both a parameter and return value.

[Dynamic, Provider ("ProviderX")]
class MyClass
{
    [Implemented] sint32 MyMethod1 ([in, id(0)] Win32_LogicalDisk 
        DiskParam);
    [Implemented] 
    Win32_LogicalDisk MyMethod2 ([in, id(0)] string DiskVolLabel);
};

The following code example describes how to include two references: one to an instance of the Win32_LogicalDisk class and the other to an instance of an unknown object type.

[Dynamic, Provider("ProviderX")]
class MyClass
{
    [Implemented] 
    sint32 MyMethod1 ([in, id(0)] Win32_LogicalDisk ref DiskRef);
    [Implemented] 
    sint32 MyMethod2 ([in, id(0)] object ref AnyObject);
};

Creating a WMI Class Method in C++

The following procedure describes how to create a WMI class method programmatically.

To create a WMI class method programmatically

  1. Create the class to which the method will belong.

    You must first have a class to place the method in before you create the method.

  2. Retrieve two child classes of the __PARAMETERS system class using either IWbemServices::GetObject or GetObjectAsync.

    Use the first child class to describe the in-parameters, and the second to describe the out-parameters. If necessary, you can perform a single retrieval followed by a call to the IWbemClassObject::Clone method.

  3. Write the in-parameters to the first class, and the out-parameters to the second class, using one or more calls to IWbemClassObject::Put.

    When describing parameters to a method, observe the following rules and restrictions:

    • Treat the [in, out] parameters as separate entries, one in the object that contains the in-parameters and one in the object that contains the out-parameters.

    • Other than the [in, out] qualifiers, the remaining qualifiers must be exactly the same.

    • Specify the ID qualifiers, starting at 0 (zero), one for each parameter.

      The order of the input or output parameters is established by the value of the ID qualifier on each parameter. All input arguments must precede any output arguments. Changing the order of method input and output parameters when updating an existing method provider can cause applications that call the method to fail. Add new input parameters at the end of the existing parameters rather than inserting them in the sequence that is already established.

      Make sure to leave no gaps in the ID qualifier sequence.

    • Place the return value in the out-parameters class as a property named ReturnValue.

      This identifies the property as the return value of the method. The CIM type of this property is the return type of the method. If the method has a return type of void, then do not have a ReturnValue property at all. Also, the ReturnValue property cannot have an ID qualifier like the arguments of the method. Assigning an ID qualifier to the ReturnValue property produces a WMI error.

    • Express any default parameter values for the property in the class.

  4. Place both __PARAMETERS objects into the parent class with a call to IWbemClassObject::PutMethod.

    A single call to PutMethod can place both __PARAMETERS objects into the class.

Creating a Class