You need to know the available module types when you are building a workflow in Operations Manager. The best place to start building rules, monitors, tasks, diagnostics and recoveries is to use the Operations Console. The console provides the most common types of workflow that you will need. So if you want to create an event collection rule and you are not sure how to do it in XML, create it in the console first, export the MP and see the modules it uses in the workflow.
The main purpose of this section is to provide you with a library of types that you can put together yourself when the Operations Console does not give you the workflow you need. Also you will need this section when you are building a new monitor type or composite module type.
I will be providing the schema (XSD) for each module type I list in this section. This means you can use an XML editor to reference the XSD file and build a valid configuration. You need to do this in isolation from the MP that you are building. This it is MP Verify that verifies module configuration not the management pack schema. When you build a management pack and come to configure a module, the management pack schema will accept any valid XML. It is only when you run MP Verify that we can determine the XSD for the configuration and validate what you enter against the schema.
I find it very useful to save the common complex module type configuration schemas to my local hard drive. Then when I need to write the configuration for a module of such a type I create a new XML file, point it to the XSD and get the smart tag look up and immediate configuration verification as I go.
Follow these steps to check configuration for a module type.
-
Get the XSD for the module type you are configuring and save it to a location on your hard disk
-
Create a new XML document and enter the following root element replacing the noNamespaceSchemaLocation with the location of the XSD for this module type
<Configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:noNamespaceSchemaLocation="C:\OpsMgr\\ModuleTypeSchema\Data Source\Microsoft.Windows.TimedScript.PerformanceProvider.xsd"></Configuration>
-
Now enter the configuration and you should get the smart tag look up and validation on your configuration as you go depending on your XML editor.
-
When you are done, copy the configuration section to you management pack module configuration section (you should remove the schema definitions on the configuration element before you do this.