Composite (ProbeActionModuleType)

System Center

Updated: August 10, 2011

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

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


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

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

Attributes

None.

Child Elements

 

Element Description

MemberModules (ProbeActionModuleType)

Required element. Contains all module implementations used in the workflow of a module type definition.

Composition (ProbeActionModuleType)

Required element. Defines the composition of the workflow of a module type definition.

Parent Elements

 

Element Description

ModuleImplementation (ProbeActionModuleType)

Defines the implementation type for native or managed module type definitions and defines the composite elements for composite module type definitions.

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)

In the following sample, a composite probe action module modularizes the functionality of a ProbeAction (ProbeActionModuleType) module and a ConditionDetection (ProbeActionModuleType) module. In this case, the Microsoft.Windows.ProductInstallationProbe module contains a probe that is used to query WMI at a certain interval. The condition detection module filters on the ProductCode value that was passed in through the configuration parameter. The module will return System.PropertyBagData if the filter the condition detection satisfies the filter.


<ProbeActionModuleType ID="Microsoft.Windows.ProductInstallationProbe" Accessibility="Public">
  <Configuration>
    <xsd:element name="ComputerName" type="xsd:string" />
    <xsd:element name="ProductCode" type="xsd:string" />
  </Configuration>
  <OverrideableParameters>
    <OverrideableParameter ID="ComputerName" ParameterType="string" Selector="$Config/ComputerName$" />
    <OverrideableParameter ID="ProductCode" ParameterType="string" Selector="$Config/ProductCode$" />
  </OverrideableParameters>
  <ModuleImplementation>
    <Composite>
      <MemberModules>
        <ProbeAction ID="WmiProbe" TypeID="Microsoft.Windows.WmiTriggerProbe">
          <NameSpace>\\$Config/ComputerName$\Root\CIMv2</NameSpace>
          <Query>SELECT * FROM Win32_Product</Query>
        </ProbeAction>
        <ConditionDetection ID="FilterOnProductCode" TypeID="System!System.ExpressionFilter">
          <Expression>
            <SimpleExpression>
              <ValueExpression>
                <XPathQuery Type="String">Property[@Name='IdentifyingNumber']</XPathQuery>
              </ValueExpression>
              <Operator>Equal</Operator>
              <ValueExpression>
                <Value Type="String">$Config/ProductCode$</Value>
              </ValueExpression>
            </SimpleExpression>
          </Expression>
        </ConditionDetection>
      </MemberModules>
      <Composition>
        <Node ID="FilterOnProductCode">
          <Node ID="WmiProbe" />
        </Node>
      </Composition>
    </Composite>
  </ModuleImplementation>
  <OutputType>System!System.PropertyBagData</OutputType>
  <TriggerOnly>true</TriggerOnly>
</ProbeActionModuleType>

 
Show: