[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
      WriteActionModuleType
        ModuleImplementation (DataSourceModuleType)
          Composite (DataSourceModuleType)
            MemberModules (DataSourceModuleType)

Syntax

Xml 
<MemberModules>
   <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

WriteAction (WriteActionModuleType)

Required element. A write action type’s internal workflow usually consists of one WriteAction (WriteActionModuleType) module.

Parent Elements

Element Description

Composite (WriteActionModuleType)

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

Remarks

The MemberModules element of a WriteActionModuleType module contains the modules that are used to structure its internal workflow.

The write action module type may define output data of the type defined in the OutputType (WriteActionModuleType) element but does not provide data to modules in a workflow. Generally, a write action module type definition contains only one write action module.

The ID attribute of each member module must be unique only in the scope of the module type, not the management pack.

Example

The following XML sample shows a WriteActionModuleType element that is defined in the System.Windows.Library management pack. This particular write action module is used to start a service on the specified computer name. The reason for defining this module type is to provide a specialized version of the System.CommandExecuter write action module type.

  Copy Code 
<WriteActionModuleType ID="Microsoft.Windows.ServiceControlManager.StartService" Accessibility="Public">
  <Configuration>
	<xsd:element name="ComputerName" type="xsd:string" />
	<xsd:element name="ServiceName" type="xsd:string" />
  </Configuration>
  <OverrideableParameters>
	<OverrideableParameter ID="ComputerName" ParameterType="string" Selector="$Config/ComputerName$" />
	<OverrideableParameter ID="ServiceName" ParameterType="string" Selector="$Config/ServiceName$" />
  </OverrideableParameters>
  <ModuleImplementation>
	<Composite>
	<MemberModules>
		<WriteAction ID="StartService" TypeID="System!System.CommandExecuter">
		<ApplicationName><![CDATA[%WinDir%\System32\sc.exe]]></ApplicationName>
		<WorkingDirectory />
		<CommandLine>\\$Config/ComputerName$ start $Config/ServiceName$</CommandLine>
		<TimeoutSeconds>60</TimeoutSeconds>
		<RequireOutput>true</RequireOutput>
		</WriteAction>
	</MemberModules>
	<Composition>
		<Node ID="StartService" />
	</Composition>
	</Composite>
  </ModuleImplementation>
  <OutputType>System!System.CommandOutput</OutputType>
  <InputType>System!System.BaseData</InputType>
</WriteActionModuleType>

See Also