Configuration (UnitMonitorType)
Applies To: Operations Manager 2007 R2, System Center Operations Manager 2007
Represents the parameters of the unit monitor type as the XSD schema.
Schema Hierarchy
ManagementPack
TypeDefinitions
MonitorTypes
UnitMonitorType
Configuration (UnitMonitorType)
Syntax
<Configuration> <IncludeSchemaTypes>…</IncludeSchemaTypes> <xsd:element name="ElementName" type="xsd:sometype" />
</Configuration>
Attributes and Elements
The following sections describe attributes, child elements, and the parent element of the Configuration element.
Attributes
None.
Child Elements
| Element | Description |
|---|---|
Optional element. Contains references to internal or external complex SchemaType elements that are used in the configuration section of the UnitMonitorType. |
Parent Elements
| Element | Description |
|---|---|
Represents a monitor type definition modeled to reflect the operational state of an entity. |
Text Value
The Configuration element describes the XSD schema for the parameters of the UnitMonitorType. Every implementation of the UnitMonitorType must supply the correct configuration parameters in accordance with the XSD schema. For more information regarding XML schemas, see the Understanding XML Schema topic.
Example
The following example illustrates the Configuration section of the Microsoft.Windows.2SingleEventLog2StateMonitorType unit monitor type as defined in the Microsoft.Windows.Library management pack. The configuration includes an IncludeSchemaTypes (UnitMonitorType) element so that it can reference the ExpressionType complex type defined in the external System.Library management pack. To see the full definition of the unit monitor type, see the UnitMonitorType topic.
<Configuration>
<IncludeSchemaTypes>
<SchemaType>System!System.ExpressionEvaluatorSchema</SchemaType>
</IncludeSchemaTypes>
<xsd:element name="FirstComputerName" type="xsd:string" />
<xsd:element name="FirstLogName" type="xsd:string" />
<xsd:element name="FirstExpression" type="ExpressionType" />
<xsd:element name="SecondComputerName" type="xsd:string" />
<xsd:element name="SecondLogName" type="xsd:string" />
<xsd:element name="SecondExpression" type="ExpressionType" />
</Configuration>
The following example illustrates how an implementation of the Microsoft.Windows.2SingleEventLog2StateMonitorType unit monitor type would supply the configuration values:
<Configuration>
<FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>Application</FirstLogName>
<FirstExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">801</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">EventCreate</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</FirstExpression>
<SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>Application</SecondLogName>
<SecondExpression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">802</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">EventCreate</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</SecondExpression>
</Configuration>