Using Templates to Create Correlations

  • Article

Correlation templates provide you with a means of creating updating consumers and correlation scenarios that use parameters. Using templates greatly simplifies the task of creating a correlation scenario.

For more information about support and installation of this component on a specific operating system, see Operating System Availability of WMI Components.

Although template functionality is independent of the updating consumer functionality, the following advantages occur when constructing correlation scenarios using WMI templates :

  • Parameterization

    A correlation scenario based on a template can use parameters that allow the template to apply to a range of parameter values. For example, you can construct a "throughput" template that can be applied to any numeric property of any class. For more information, see Creating Templates That Use Parameters.

  • Manageability

    A single template instance can represent all of the instances that make up a correlation scenario (updating consumer instance, event filters, bindings, and so on). This means that manipulation of this instance affects all instances of the scenario. For example, you can deactivate, activate, or delete a template instance, thereby deactivating, activating, or deleting all the instances associated with the correlation scenario.

Supporting Classes for the Updating Consumer are missing the state class needed in any correlation scenario and so must be combined with a user-defined state class and other consumer templates to construct a scenario. You can create a correlation scenario without templates as described in Correlating Events Without Templates, or you can define your own custom templates which you then use to create your correlation scenario. For more information, see Correlation Template Design Guidelines.