Creating a JMS Event Trigger
These steps describe how to configure a JMS event trigger.
To create a JMS event trigger
1. If not already done, configure a JMS connector with a queue or topic connection factory for use with TDV. See the TDV Administration Guide for more information.
2. Right-click where you can add a new resource in the resource tree, and select New Trigger.
3. In the Input window, supply a name for the trigger, and click OK.
4. In the trigger editor that opens on the right, enable the trigger by selecting the Enable Trigger check box.
5. For Condition Type, select JMS Event.
6. In the Condition pane, enter values in these fields:
Field | Description |
Connector | The name of your JMS connector (containing the configuration for initial context factory, JNDI Provider URL, and Queue Connection Factory) as it appears on the CONNECTOR MANAGEMENT page in Web Manager. |
Destination | The name of the connection factory destination (queue or topic). |
Selector | A JMS message selector allows a client to specify, by header field references and property references, the messages it is interested in. Only messages whose header and property values match the selector are delivered. For example, a selector condition using SQL WHERE clause syntax might look like: 'uname'='admin' |
What it means for a message not to be delivered depends on the MessageConsumer being used.
— A message selector matches a message if the selector evaluates to true when the message's header field values and property values are substituted for their corresponding identifiers in the selector.
— A message selector is a String whose syntax is based on a subset of the SQL92 conditional expression syntax. If the value of a message selector is an empty string, the value is treated as a null and indicates that there is no message selector for the message consumer.
8. On the trigger
Info tab, specify the trigger properties. See
Getting Information about a Resource for all fields except Maximum Number In Queue which is described below and works different for JMS triggers:
Maximum Number In Queue—For JMS triggers, this field is always set to 0 by the TDV server and you cannot change it. This is done to indicate that each JMS trigger can hold at most one message in memory at a time until it has been fully processed before receiving another pending message from the JMS server. That is, no message queuing is done inside TDV.
9. Save the trigger. If the Save option is not enabled, select File > Refresh All to refresh the resources and enable the Save option.