A task is a workflow that is run on demand and normally initiated by a user through the Operations Console or other SDK call. A task consists of a single module of a pre-defined module type. It is either a probe action or a write action. If a more complex workflow is required, it is possible to build a composite module type and use that module type in the task.
A task has the following attributes:
|
Name
|
Type
|
Use
|
Description
|
|
ID
|
ManagementPack
UniqueIdentifier
|
Required
|
The identity of the element. This must be unique within all elements of the management pack.
|
|
Comment
|
ManagementPackString
|
Optional
|
Use for author comments.
|
|
Enabled
|
ManagementPack
MonitoringLevel
|
Optional
|
Defines if the task is enabled by default. Set to true or false. Other values allowed are OnEssentials, OnStandard, OnAdvanced. These will only be enabled in conjunction with category overrides.
|
|
Target
|
ManagementPack
IdentifierReference
|
Required
|
The target class. The workflow can be run against instances of the targeted class
|
|
Timeout
|
xsi:int
|
Optional
|
The time in seconds that the task can run. The task will be terminated if it exceeds this limit
|
|
Remoteable
|
xsi:boolean
|
Optional
|
Defines whether this workflow will run for agentless monitoring. If it is not specified it is assumed to be true.
|
Category
The category of a task must be one of the following strings:
-
PerformanceCollection
-
Operations
-
EventCollection
-
StateCollection
-
SoftwareAndUpdates
-
Alert
-
System
-
Custom
-
AvailabilityHealth
-
PerformanceHealth
-
ConfiguraitonHealth
-
SecurityHealth
-
Notification
-
Maintenance
Although the following are allowed categories you should not used them as they are used for other purposes:
-
Discovery
-
DSIntegration
-
ConnectorFramewory
-
ExceptionMonitoring
The category field is not really used for anything in Operations Manager 2007. Category overrides can take advantage of this field but this concept is not exposed in the Ops Mgr UI.
Probe Action
If the task is a probe action (does not change system state) then this element is present. This element references a pre-defined probe action module type.
The attributes on a probe action are:
|
Name
|
Type
|
Use
|
Description
|
|
ID
|
ManagementPackLocal
IdentifierReference
|
Required
|
The identity of the sub-element. This must be unique within the containing element i.e. the task.
|
|
Comment
|
ManagementPackString
|
Optional
|
Use for author comments.
|
|
RunAs
|
ManagementPack
IdentifierReference
|
Optional
|
References a secure reference. You should use this attribute only if you want to associate this module with a Run As profile.
|
|
TypeID
|
ManagementPack
IdentifierReference
|
Optional
|
The ID of the probe action module type that is to be used.
|
The probe action module must contain the necessary configuration for the module type. This configuration will be validated during MP Verify.
Illustration from Altova XML Spy
Write Action
If the task is a write action (changes system state) then this element is present. The element references a pre-defined write action module type.
The attributes on a write action are:
|
Name
|
Type
|
Use
|
Description
|
|
ID
|
ManagementPackLocal
IdentifierReference
|
Required
|
The identity of the sub-element. This must be unique within the containing element i.e. the task.
|
|
Comment
|
ManagementPackString
|
Optional
|
Use for author comments.
|
|
RunAs
|
ManagementPack
IdentifierReference
|
Optional
|
References a secure reference. You should use this attribute only if you want to associate this module with a Run As profile.
|
|
TypeID
|
ManagementPack
IdentifierReference
|
Optional
|
The ID of the write action module type that is to be used.
|
|
Target
|
ManagementPack
IdentifierReference
|
Optional
|
You can optional specify a different class to run the write action against. The main options for this are:
Microsoft.SystemCenter.ManagementServer
Microsoft.SystemCenter.RootManagementServer
This will have the effect of running a server side response.
|
The write action module must contain the necessary configuration for the module type. This configuration will be validated during MP Verify.
Illustration from Altova XML Spy