WMI Trigger Properties

The WMI Trigger Properties window contains the settings for a WMI Trigger.

Property Pages

General

Name for this trigger (optional)

Optionally, specify a descriptive name for the trigger.

Enabled

Uncheck this box to disable the trigger. If the trigger is not enabled, adTempus will ignore it (it will not cause the job to trigger).

Continue to evaluate during Exclusion Periods 5.2Server version 5.2 or later
Console version 5.2 or later

When a job is affected by an Exclusion Period, this option determines how the trigger behaves:

  • When the option is checked (default), adTempus continues to evaluate the trigger during the exclusion period but if any triggering events occur, execution of the job is delayed until the Exclusion Period ends. For example, a File Trigger will continue looking for file changes and if it finds any that meet the trigger criteria, the job will be queued for execution at the end of the Exclusion Period. Generally you will want this option to be checked for the most reliable monitoring.
  • When the option is unchecked, adTempus does not evaluate the trigger during the Exclusion Period but resumes evaluation after the Exclusion Period ends. For example, a File Trigger will stop watching for file changes until the Exclusion Period ends. Note that it is possible to miss trigger events as a result of this (for example, the trigger conditions may no longer be present when adTempus resumes evaluating the trigger). You might want to uncheck this option if the Exclusion Period represents a maintenance window during which the trigger will fail. For example, for an Email Trigger if the monitored mail server is not available during this time.

This option is not available for all triggers.

Minimum Interval

Specify the minimum interval (in seconds) for this trigger. Once the triggers conditions are satisfied and the job is triggered, adTempus will ignore this trigger for the specified interval.

For example, suppose you are using a File Trigger to trigger the job whenever a new file is added to a folder. If you set the interval to 60 seconds, then once adTempus triggers the job, it will ignore any new files that arrive in the next 60 seconds.

Description/Notes

Enter any extended descriptive information or notes for this trigger.

Job Variables

The Job Variables page allows you to define Job Variables that will be set for this job only when it is started by this trigger.

The Job Variable list shows variables defined for the current object as well as variables inherited from a higher level. Icons next to each variable in the list convey information about their inheritance:

The variable is inherited from a higher level
The variable is inherited from a higher level and is locked (cannot be overridden)
The variable is inherited from a higher level and has been modified at this level
The variable is new at this level
The variable is inherited from a higher level and must be overridden (a value provided) at this level
The variable has been overridden (redefined) at a lower level. This icon only appears if you have analyzed variable usage (see below).

When you hove the mouse pointer over the icon for an inherited variable, adTempus will show where the variable was inherited from.

Filtering the variable list

The variable list can be filtered to:

  • Hide inherited variables (so you only see variables defined at this level)
  • Hide variables that cannot be modified (inherited variables that are locked to prevent modification)
  • Show only variables that must be overridden

Analyzing and viewing variable usage5.0Server version 5.0 or later
Console version 5.0 or later

When you click Analyze variable usage, adTempus searches for all the places where the variables are used or overridden. After this analysis is complete, new columns are added to the list to show, for each variable:

  • Whether it has been overridden (redefined) at a lower level
  • A count of how many times it is referenced (used)

Clicking Show variable usage opens a new window showing all the references and overrides for the variables. This is the same window shown by the Find Variable and Function References tool.

Analyze variable usage only finds references and overrides that are "below" the current level. For example, if you are viewing the variables for a job, this will find all references and overrides within the job, or within jobs that may receive variables from this jobs (jobs run by Responses or Job Triggers). If you are viewing a group, this will find all references and overrides within groups and jobs below the selected group. That is, the tool only lists places that might be affected by changes to the variables in the list.

This tool does not show other places where the variables might be used. For example if you are viewing job A and some of the variables are also used in job B, those uses will not be listed unless there is a link between job A and job B.

To find all references to a variable:

  • If the variable is defined at the server level, use the Analyze variable usage tool from the variables list at the server level. This will show all uses everywhere in adTempus.
  • Use the Find Variable and Function References tool to find a specific variable or all variables.

WMI Events

Specify the WMI query parameters.

Namespace

Specify the WMI namespace to use.

Query

Specify the WMI query to execute. This must be a valid WMI event query. For information on WMI event queries refer to the Microsoft Platform SDK documentation.

Each time the query returns an event, adTempus will trigger the job.

adTempus does not validate your WMI query settings at the time you save the trigger. To test your query, use the "wbemtest" system utility.

If Windows returns an error when adTempus submits your query, adTempus will log an error message to the message log for the job and hold the job until you edit it to correct the query.

Use a script to select events

For more advanced filtering, you can use a .NET script to filter the message. For each event returned by the query, adTempus will run your script. Your script has access to the Parameters.WMIEvent object, which exposes the event as a ManagementBaseObject.

Your script must return True if adTempus should trigger for the event or False if it should not.

Related Concepts

WMI Trigger