The Enable Trigger check box is at the top of the Condition tab. This check box must be selected to activate a trigger.

The Trigger Condition tab has four panes in which you specify the trigger information:

The selections in the panes on the left (Condition Type and Action Type) determine what options are displayed in the panes on the right (Condition and Action). For example, the trigger editor below shows the options for a condition type of Timer Event and an action type of Send E-mail.

The contents of the Condition pane depend on the condition type selected.

Prior to use of the JMS event trigger, you need to configure a JMS connector with a queue or topic connection factory for use with TDV. See “Configuring TDV Data Connections” in the TDV Administration Guide for information about the JMS configuration requirements. See Creating a JMS Event Trigger for how to define a JMS event trigger.

You specify the system event name. See Creating a System Event Trigger.

You specify the frequency for when the trigger occurs. See Creating a Timer Event Trigger for more details.

Only once per cluster—When checked (the default), specifies that the trigger action be performed only once in the cluster. That is, if the trigger action is invoked on one node of the cluster, the other nodes are notified and the trigger action is not invoked again. When unchecked, the trigger action is invoked on every node of the cluster.

You specify the user-defined event name. See Creating a User-Defined Event Trigger for more details.

The contents of the Action pane depend on the action type (described in Action Types for a Trigger). A description of the options for each action type are as follows.

This action lets you trigger execution of a procedure without sending any notification. The Action pane lists the fields to fill in:

Procedure Path—Specify the procedure to execute:

Parameter Values—Specify any parameters and values that the procedure or view uses:

Note: Only static input parameters can be used by the trigger, but the procedure invoked can use whatever variables it might require.

Exhaust output cursors—If the procedure is a SQL script that contains a PIPE cursor, and if the pipe needs to fully execute and load all rows to complete execution of a trigger (for example, to email a result set) checking this box forces the trigger to wait until all the rows are buffered and read before completing. If you leave this unchecked, the trigger returns while the pipe is buffering, cutting off the buffering of the pipe.

Note: As soon as you begin typing text in any field of the dialog box, the NULL box for that field is unchecked. If you decide to delete all text from the field, be sure to recheck its NULL box.

This action lets you specify a data source for which to gather statistics data.

Data Source Path—Specify the data source path and name:

To see how this action works, select the data source to be scanned for data statistics. After creating the trigger, view the Triggers console in Studio Manager to check if the trigger fired as scheduled.

This action lets you specify a data source to reintrospect.

Data Source Path—Specify the data source path and name:

To, Cc, Bcc, Reply-To—These work the same as in ordinary email applications. You can specify a list of email addresses by separating them with commas (,) or semicolons (;). The email recipients are sent a notification with the result of the output of the procedure or view.

Message Subject, Message Body—These work the same as in ordinary email applications.

Do Not Persist Detected Changes—Check this if you want only a report about the changes detected in the data source, and not save the changes. This option allows the TDV developer or administrator to assess the impact of data source changes to the TDV model before actually applying them.

Do Not Send If No Changes Detected—Check this if you do not want email sent if no changes were detected.

To see how this action works, select the data source to be reintrospected. After creating the trigger, view the Triggers console in Studio Manager to check if the trigger fired as scheduled. Also verify if the notification was sent to the e-mail recipients.

This action lets you specify a procedure or view to execute and then send the results through email to one or more recipients. The Action pane lists the fields to fill in:

Resource Path—Specify a procedure or view to execute:

Parameter Values—Specify any parameters and values that the procedure or view uses:

To, Cc, Bcc, Reply-To—These work the same as in ordinary email applications. You can specify a list of email addresses by separating them with commas (,) or semicolons (;). The email recipients are sent a notification with the result of the output of the procedure or view.

Message Subject, Message Body—These work the same as in ordinary email applications.

Include Summary—Check this if you want to include a summary of the notification.

Do Not Send If No Results—Check this if you do not want to receive notification if there are no results.

To see how the Send E-mail action works, select the transformation to be executed. After creating the trigger, view the Triggers console in Studio Manager to check if the trigger was fired as scheduled. Also verify if the notification was sent to the mail recipients.