MemberModules (DataSourceModuleType)
Applies To: System Center Service Manager 2010
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
Contains all modules used in the linear workflow of a module type definition.
Schema Hierarchy
ManagementPack
TypeDefinitions
ModuleTypes
DataSourceModuleType
ModuleImplementation (DataSourceModuleType)
Composite (DataSourceModuleType)
MemberModules
Syntax
<MemberModules>
<DataSource>…</DataSource>
<ProbeAction>…</ProbeAction>
<ConditionDetection>…</ConditionDetection>
</MemberModules>
Attributes and Elements
The following sections describe attributes, children, and the parent element of the MemberModules element.
Attributes
None.
Child Elements
| Element | Description |
|---|---|
Optional element. The implementation of a predefined ConditionDetectionModuleType module. |
|
Required element if probe action module is not included. The implementation of a predefined DataSourceModuleType module. |
Parent Elements
| Element | Description |
|---|---|
Contains the module implementations and linear workflow composition in a module type definition. |
Remarks
The MemberModules element of a DataSourceModuleType module contains the modules that are used to structure its internal workflow. The internal workflows within a DataSourceModuleType module do not take any input and must return data of the type defined in the OutputType (DataSourceModuleType) element. Because a DataSourceModuleType definition must always return data for use by the next module in the workflow, its MemberModules element does not include modules that are of the WriteActionModuleType definition. WriteActionModuleType definitions never return any data and must always be the last module in a workflow. The last module in a DataSourceModuleType workflow must be a DataSource (DataSourceModuleType) or a ConditionDetection (DataSourceModuleType) module. The first module in a DataSourceModuleType module must be a DataSource module that initiates the workflow either because of a scheduler or because of a trigger.
The ID attribute of each member module must be unique only in the scope of the module type, not the management pack.