[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Represents the parameters for a monitor or module type definition in XSD schema.

Schema Hierarchy



<Configuration>   <IncludeSchemaTypes>…</IncludeSchemaTypes>   <xsd:element name="ElementName" type="xsd:sometype" />

Attributes and Elements

The following sections describe attributes, child elements, and the parent elements of the Configuration element.



Child Elements

Element Description


Optional element. Contains references to internal or external complex SchemaType element types. These types are used as parameter data types in the Configuration section of the ModuleTypes or MonitorTypes element.

Parent Elements

Element Description


Represents a data source module type definition in a management pack.


Represents a condition detection module type definition in a management pack.


Represents a write action module type definition in a management pack.

Text Value

The Configuration element describes the XSD schema for the parameters of module or monitor type definition elements. Each implementation of the defined module or monitor type must supply the correct configuration parameters in accordance with this XSD schema. For more information about XML schemas, see Understanding XML Schema.


The following example illustrates the Configuration section of the Microsoft.Windows.BaseEventProvider data source module type as defined in the Microsoft.Windows.Library management pack. The configuration includes an IncludeSchemaTypes element so that it can reference the ComputerNameType complex type defined within the same Microsoft.Windows.Library management pack. To see the full definition of the data source module type, see DataSourceModuleType.

  Copy Code
  <xsd:element name="ComputerName" type="ComputerNameType" minOccurs="0" maxOccurs="1" />
  <xsd:element name="LogName" type="xsd:string" />
  <xsd:element name="AllowProxying" type="xsd:boolean" minOccurs="0" maxOccurs="1" />

The following example illustrates how an implementation of the Microsoft.Windows.BaseEventProvider data source module type would supply the correct configuration parameter values. In this sample, the $Config expression is used because this data source is part of a composite module. $Config/ComputerName is an expression that refers to the ComputerName parameter declared in the composite module’s Configuration section. For more information about the $Config variable notation, see $Config. To see the full definition of the composite module, see Composite (DataSourceModuleType).

  Copy Code
<DataSource TypeID="Microsoft.Windows.BaseEventProvider" ID="Provider">

See Also