Custom Module Types

適用於: System Center Operations Manager 2007

Custom module types are not as restrictive as custom workflows. Each type has requirements as to the kinds of modules they can contain, and whether they require input or output data. Within those guidelines though, the custom module can contain multiple modules arranged in any specified order.

Data Source Modules

Data source modules are the most common type of custom module, because they are used for rules, regular detection on monitors, and discoveries. They frequently contain custom scripts and other logic to retrieve data from a particular application or device.

Data source modules can contain modules of the following types:

• Data source modules

• Probe action modules

• Condition detection modules

Data source modules have the following requirements:

• Must start with at least one data source module.

• Must deliver output in a single data stream. If the module contains multiple data source modules or multiple probe action modules, one or more condition detection modules must be used to consolidate or filter the data streams.

• The type of the output data will match the type output by the last included module.

Probe Action Modules

Probe action modules are used in tasks and in monitors for on-demand detection. Like data source modules, they can use to custom scripts and other logic to retrieve data from a particular application or device. The difference is that a probe action cannot be used without being embedded in a data source module in rules and in monitor regular detection. A common strategy is to use a probe action module to hold the script and then encapsulate that module in a data source module that adds a scheduler. This strategy allows the same logic to be used for rules, both on demand and regular detection monitors, and tasks.

Probe action modules can contain modules of the following types:

• Probe action modules

• Condition detection modules

Probe action modules have the following requirements:

• Must declare an input data type that matches the required input of the first module.

• Must deliver output in a single data stream. If the module contains multiple probe action modules, one or more condition detection modules must be used to consolidate or filter the data streams.

• The type of the data will match the type output by the last included module.

Probe Action Module Input Data and Triggers

Probe action modules will either require input data from a previous module or require only a trigger without data provided. Only those that are configured as Trigger Only may be used in on-demand detection for a monitor type. If a composite probe action module contains another probe action module that requires input data, however, that module must also require input data.

This may present an issue if a probe action module is required for a monitor type that uses on-demand detection but a Trigger Only probe action module is not available. The most obvious example of this is the probe action module for running a script Microsoft.Windows.ScriptPropertyBagProbe that does require input.

The solution to this issue is a special probe action module named System.PassThroughProbe. This module requires no input, performs no function, and outputs blank data. It may be used at the start of any composite probe action module that has to be Trigger Only but must also include another module requiring input.

Pass through probe

Condition Detection Modules

Custom condition detection modules are not common, although they can be created for specific scenarios.

Condition detection modules can contain modules of the following types:

• Condition detection modules

Condition detection modules have the following requirements:

• Must declare one or more input types that match the type of the expected data.

• Must deliver output in a single data stream.

• The type of the data will match the type output by the last included module.

Write Action Modules

Write action modules are used in rules to perform some final action of a workflow or in tasks that perform some action at the request of the user. The data from a write action module is never sent into the data stream. If data is output from a write action module, it is stored in the Operations Manager database or data warehouse. Custom write action modules are frequently created to contain scripts that perform some action against a particular application.

Write action modules can contain modules of the following types:

• Write action modules

Write action modules have the following requirements:

• Must declare one or more input types that match the type of the expected data.

• Must include at least one write action module.