Share via


Composite (WriteActionModuleType)

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 the module implementations and linear workflow composition in a module type definition.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    ModuleTypes
      WriteActionModuleType
        InputType (WriteActionModuleType)
          ModuleImplementation (WriteActionModuleType)
            Composite

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 (WriteActionModuleType)

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

Composition (WriteActionModuleType)

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

Parent Elements

Element Description

ModuleImplementation (WriteActionModuleType)

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 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)

WriteActionModuleType

MemberModules (WriteActionModuleType)

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.

<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

Reference

ModuleImplementation (WriteActionModuleType)