Composite (DataSourceModuleType)

Article
05/16/2012

Applies To: Operations Manager 2007 R2, System Center Operations Manager 2007

Contains the module implementations and linear workflow composition in a module type definition.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    ModuleTypes
      DataSourceModuleType
        ModuleImplementation (DataSourceModuleType)
          Composite (DataSourceModuleType)

Syntax

<Composite>
   <MemberModules>…</MemberModules>
   <Composition>…</Composition>
</Composite>

Attributes and Elements

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

Attributes

None.

Child Elements

Element	Description
MemberModules	Required element. Contains all module implementations used in the workflow of a module type definition.
Composition (DataSourceModuleType)	Required element. Defines the composition of the workflow of a module type definition.

Parent Elements

Element	Description
ModuleImplementation (DataSourceModuleType)	Defines the implementation type for native or managed module type definitions, and the composite elements for composite module type definitions.

Remarks

Composite modules comprise one or more modules, as opposed to being implemented in native or managed code. Each module type requires or expects specific member modules in a specific order. For more information about the correct member modules for specific module types, see each MemberModules topic listed in the following table.

Module Type	MemberModules
ConditionDetectionModuleType	MemberModules (ConditionDetectionModuleType)
DataSourceModuleType	MemberModules (DataSourceModuleType)
ProbeActionModuleType	MemberModules (ProbeActionModuleType)
WriteActionModuleType	MemberModules (WriteActionModuleType)

Example

In the following sample, a composite data source module modularizes the functionality of a DataSource (DataSourceModuleType) module and a ProbeAction (DataSourceModuleType) module. In this case, the Microsoft.Windows.Discovery.RegistryProvider data source module contains a scheduler that is used to get registry values at a certain interval. The data source module then returns the results of the probe action as a Microsoft.Windows.RegistryData data type.

<DataSourceModuleType ID="Microsoft.Windows.Discovery.RegistryProvider" Accessibility="Public">
  <Configuration>
    <IncludeSchemaTypes>
      <SchemaType>Microsoft.Windows.RegistryAttributeDefinitionsSchema</SchemaType>
    </IncludeSchemaTypes>
    <xsd:element name="ComputerName" type="xsd:string" />
    <xsd:element name="RegistryAttributeDefinitions" type="RegistryAttributeDefinitionsType" />
    <xsd:element name="Frequency" type="xsd:unsignedInt" />
  </Configuration>
  <OverrideableParameters>
    <OverrideableParameter ID="Frequency" Selector="$Config/Frequency$" ParameterType="int" />
  </OverrideableParameters>
  <ModuleImplementation>
    <Composite>
      <MemberModules>
        <DataSource TypeID="System!System.Discovery.Scheduler" ID="Scheduler">
          <Scheduler>
            <SimpleReccuringSchedule>
              <Interval Unit="Seconds">$Config/Frequency$</Interval>
            </SimpleReccuringSchedule>
            <ExcludeDates />
          </Scheduler>
        </DataSource>
        <ProbeAction TypeID="Microsoft.Windows.RegistryProbe" ID="Probe">
          <ComputerName>$Config/ComputerName$</ComputerName>
          <RegistryAttributeDefinitions>$Config/RegistryAttributeDefinitions$</RegistryAttributeDefinitions>
        </ProbeAction>
      </MemberModules>
      <Composition>
        <Node ID="Probe">
          <Node ID="Scheduler" />
        </Node>
      </Composition>
    </Composite>
  </ModuleImplementation>
  <OutputType>Microsoft.Windows.RegistryData</OutputType>
</DataSourceModuleType>