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).

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.

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.

If you are upgrading from adTempus 3 or earlier and are using scripts to filter WMI events, some changes are required: .

Filter scripts must now be .NET scripts (VB.NET or C#); WSH scripts (VBScript) are not supported. If your script is already a .NET script, the script class must be modified to derive from the WMITriggerScriptBase class. Previous versions of adTempus exposed the WMI event through a Job Variable. Starting with version 4 the event is passed in the Parameters.WMIEvent object instead, which exposes the event as a ManagementBaseObject . The event is no longer available through a Job Variable.