OverrideableParameter (ConditionDetectionModuleType)
Updated: May 18, 2012
Applies To: System Center 2012 - Operations Manager, System Center 2012 R2 Operations Manager, System Center 2012 SP1 - Operations Manager
Represents an overrideable configuration parameter in a monitor or module type definition.
<OverrideableParameter ID=”ParameterID” ParameterType=”dataType” Selector=”$Config/ParameterID”/>
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 (ConditionDetectionModuleType) element of the parameter to be overridden. |
| 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 |
|---|---|
Contains any overrideable configuration parameters a monitor or module type definition. |
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.
The following sample shows how to define an OverrideableParameter within a ConditionDetectionModuleType module definition.
A management pack that implements this condition detection module type may hard code the Frequency parameter in one of its workflows. Because Frequency is an OverrideableParameter, the customer can override whatever value 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.
<ConditionDetectionModuleType ID="Microsoft.InformationWorker.Performance.MultiInstance.Collection.ModuleType" Accessibility="Public">
<Configuration>
<xsd:element name="Frequency" type="xsd:unsignedInt" />
<xsd:element name="Function" type="xsd:string" />
<xsd:element name="InstanceName" type="xsd:string" />
</Configuration>
<OverrideableParameters>
<OverrideableParameter ID="Frequency" ParameterType="int" Selector="$Config/Frequency$" />
</OverrideableParameters>
<ModuleImplementation>
<Native>
<ClassID>B5F80055-46B5-446d-9C71-A8B5ED74B780</ClassID>
</Native>
</ModuleImplementation>
<OutputType>SystemPerf!System.Performance.Data</OutputType>
<InputTypes>
<InputType>SystemPerf!System.Performance.Data</InputType>
</InputTypes>
</ConditionDetectionModuleType>