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

Represents an overrideable configuration parameter in a monitor or module type definition.

Schema Hierarchy

ManagementPack
  TypeDefinitions
    ModuleTypes
      DataSourceModuleType
        OverrideableParameters (DataSourceModuleType)
          OverrideableParameter

Syntax

Xml 
<OverrideableParameter ID=”ParameterID” ParameterType=”dataType” Selector=”$Config/ParameterID”/>

Attributes and Elements

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

Attributes

Attribute Description

ID

Required attribute. Represents the ID of the overrideable parameter. Must be unique within the module or monitor type definition.

Comment

Optional attribute. Represents commentary by the management pack author.

ParameterType

Required attribute. Represents the simple data type of the parameter to be overridden. Only simple types can be overridden.

Selector

Required attribute. Represents the XPath location within the schema defined in the Configuration (DataSourceModuleType) element of the parameter to be overridden.
ParameterType Attribute Values

Value Description

int

The overrideable parameter is of an integer type.

decimal

The overrideable parameter is of a decimal type.

double

The overrideable parameter is of a double type.

string

The overrideable parameter is of a string type.

datetime

The overrideable parameter is of a datetime type.

guid

The overrideable parameter is of a GUID type.

bool

The overrideable parameter is of a Boolean type.

Child Elements

None.

Parent Elements

Element Description

OverrideableParameters (DataSourceModuleType)

Contains any overrideable configuration parameters a monitor or module type definition.

Remarks

Because parameter overrides are displayed in the console so that users can implement the overrides, it is advised to supply a display string for each override. For more information, see DisplayStrings.

Example

The following sample shows how to define an OverrideableParameter element within a DataSourceModuleType module definition.

A management pack that implements this data source module type may hard code the Frequency parameter in one of its workflows. Because Frequency is an OverrideableParameter element, the customer can override whatever value that is set by the management pack author. If you want to implement a module type but do not want to offer its defined OverrideableParameter elements to the customer, you must write your own module type without the override definition.

  Copy Code 
<DataSourceModuleType ID="Microsoft.Windows.RegistryProviderSingle" Accessibility="Public">
  <Configuration>
	<IncludeSchemaTypes>
	<SchemaType>Microsoft.Windows.RegistryAttributeDefinitionsSchema</SchemaType>
	</IncludeSchemaTypes>
	<xsd:element name="ComputerName" type="xsd:string" />
	<xsd:element name="AttributeName" type="xsd:ID" />
	<xsd:element name="Path" type="xsd:string" />
	<xsd:element name="PathType" type="xsd:integer" />
	<xsd:element name="AttributeType" type="xsd:integer" />
	<xsd:element name="Frequency" type="xsd:unsignedInt" />
	<xsd:element name="RegistryView" minOccurs="0" maxOccurs="1" type="RegistryViewType" />
  </Configuration>
  <OverrideableParameters>
	<OverrideableParameter ID="Frequency" Selector="$Config/Frequency$" ParameterType="int" />
  </OverrideableParameters>
  <ModuleImplementation>
	<Composite>
	<MemberModules>
		<DataSource TypeID="System!System.Scheduler" ID="Scheduler">
		<Scheduler>
			<SimpleReccuringSchedule>
			<Interval Unit="Seconds">$Config/Frequency$</Interval>
			</SimpleReccuringSchedule>
			<ExcludeDates />
		</Scheduler>
		</DataSource>
		<ProbeAction TypeID="Microsoft.Windows.RegistryProbe" ID="Probe">
		<ComputerName>$Config/ComputerName$</ComputerName>
		<RegistryAttributeDefinitions>
			<RegistryAttributeDefinition>
			<AttributeName>$Config/AttributeName$</AttributeName>
			<Path>$Config/Path$</Path>
			<PathType>$Config/PathType$</PathType>
			<AttributeType>$Config/AttributeType$</AttributeType>
			<RegistryView>$Config/RegistryView$</RegistryView>
			</RegistryAttributeDefinition>
		</RegistryAttributeDefinitions>
		</ProbeAction>
	</MemberModules>
	<Composition>
		<Node ID="Probe">
		<Node ID="Scheduler" />
		</Node>
	</Composition>
	</Composite>
  </ModuleImplementation>
  <OutputType>Microsoft.Windows.RegistryData</OutputType>
</DataSourceModuleType>

See Also