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

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

Schema Hierarchy

ManagementPack
  TypeDefinitions
    ModuleTypes
      ConditionDetectionModuleType
        ModuleImplementation (ConditionDetectionModuleType)
          Composite

Syntax

Xml 
<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 (ConditionDetectionModuleType)

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

Composition (ConditionDetectionModuleType)

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

Parent Elements

Element Description

ModuleImplementation (ConditionDetectionModuleType)

Defines the implementation type for native or managed module type definitions and defines 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 and in a specific order. For more information about the correct member modules for specific module types, see each MemberModules listed in the following table.

Module Type MemberModules

ConditionDetectionModuleType

MemberModules (ConditionDetectionModuleType)

DataSourceModuleType

MemberModules (DataSourceModuleType)

WriteActionModuleType

MemberModules (WriteActionModuleType)

Example

In the following XML sample, a composite condition detection module modularizes the functionality of two ConditionDetection (ConditionDetectionModuleType) modules. The System.Discovery.FilteredClassSnapshotDataMapper module first filters the input data stream based on the value of the Expression parameter. If the filter returns result data, that data is used as the input for the mapper condition detection module, which maps the input data type to discovery data.

  Copy Code 
<ConditionDetectionModuleType ID="System.Discovery.FilteredClassSnapshotDataMapper" Accessibility="Public" PassThrough="false" Batching="false" Stateful="false">
  <Configuration>
	<IncludeSchemaTypes>
	<SchemaType>System.ExpressionEvaluatorSchema</SchemaType>
	<SchemaType>System.Discovery.MapperSchema</SchemaType>
	</IncludeSchemaTypes>
	<xsd:element name="Expression" type="ExpressionType"/>
	<xsd:element name="ClassId" type="xsd:string"/>
	<xsd:element name="InstanceSettings" minOccurs="0" maxOccurs="1" type="SettingsType"/>
  </Configuration>
  <ModuleImplementation Isolation="Any">
	<Composite>
	<MemberModules>
		<ConditionDetection ID="Filter" TypeID="System.ExpressionFilter">
		<Expression>$Config/Expression$</Expression>
		</ConditionDetection>
		<ConditionDetection ID="Mapper" TypeID="System.Discovery.ClassSnapshotDataMapper">
		<ClassId>$Config/ClassId$</ClassId>
		<InstanceSettings>$Config/InstanceSettings$</InstanceSettings>
		</ConditionDetection>
	</MemberModules>
	<Composition>
		<Node ID="Mapper">
		<Node ID="Filter"/>
		</Node>
	</Composition>
	</Composite>
  </ModuleImplementation>
  <OutputType>System.Discovery.Data</OutputType>
  <InputTypes>
	<InputType>System.BaseData</InputType>
  </InputTypes>
</ConditionDetectionModuleType>

See Also