Adding JMS Destinations and Message Selectors to a JMS Trigger

The destination is the queue or topic to which the JMS trigger subscribes on the JMS provider. When a JMS trigger subscribes to a topic, you can also indicate whether Integration Server creates a durable subscriber or a non-durable subscriber for the topic.

3. In the Destination Name column, do one of the following to specify the destination from which you want the JMS trigger to receive messages.

If the JMS connection alias uses JNDI to retrieve administered objects, specify the lookup name of the Destination object.

If the JMS connection alias uses the native webMethods API to connect directly to webMethods Broker, specify the provider-specific name of the destination.

If the JMS connection alias creates a connection on webMethods Broker or Universal Messaging, click

to select from a list of existing destinations. You can also create a destination and then select it. After you select the destination, click OK.

Note:
If you do not see

and the Enable Destination Management with Designer option is enabled for the JMS connection alias, refresh the package that contains the JMS trigger.

If the Order By mode for the selected destination does not match the existing message processing mode, Designer prompts you to change the processing mode. This situation can occur only when the JMS provider is webMethods Broker.

For instructions for creating a destination, see Creating a Destination on the JMS Provider.

4. In the Destination Name column, in the Destination Type column, select the type of destination:

Select...	If...
Queue	The destination is a queue. This is the default.
Topic	The destination is a topic.
Topic (Durable Subscriber)	The destination is a topic for which there is a durable subscriber.

Note:Designer populates Destination Type automatically if you selected a destination from the list of existing destinations on the JMS provider.

5. In the JMS Message Selector column, click

. In the Enter JMS Message Selector dialog box, enter the expression that you want to use to receive a subset of messages from this destination and click OK.

For more information about creating a JMS message selector, see Creating a Message Selector.

6. If you specified the destination type as Topic (Durable Subscriber), in the Durable Subscriber Name column, do one of the following:

If the JMS connection alias creates a connection on webMethods Broker or Universal Messaging, click

to select from a list of existing durable subscribers for the topic. In the Durable Subscriber List dialog box select the durable subscriber and click OK.

If the durable subscriber that you want this JMS trigger to use does not exist, you can create it by entering in the name in the Durable Subscriber Name column. The name must be unique for the connection where the connection name is the client ID of the JMS connection alias. webMethods Broker or Universal Messaging, will create the durable subscriber name using the client ID of the JMS connection alias and the specified durable subscriber name.

Note:Designer populates Durable Subscriber Name automatically if you selected a Topic (Durable Subscriber) destination from the list of existing destinations on webMethods Broker or Universal Messaging.

7. If you want the JMS trigger to ignore messages sent using the same JMS connection alias as the JMS trigger, select the check box in the Ignore Locally Published column. This property applies only when the Destination Type is Topic or Topic (Durable Subscriber).

Note:
If the JMS connection alias specified for this trigger has the Create New Connection per Trigger option enabled, then Ignore Locally Published will not work. For the JMS trigger to ignore locally published messages, the publisher and subscriber must share the same connection. When the JMS connection alias uses multiple connections per trigger, the publisher and subscriber will not share the same connection.

8. Repeat this procedure for each destination from which you want the JMS trigger to receive messages.

If you specify a new durable subscriber name and the JMS connection alias that the JMS trigger uses to retrieve messages is configured to manage destinations, Integration Server creates a durable subscriber for the topic when the JMS trigger is first enabled.

If you specify a destination type of Topic (Durable Subscriber) but do not specify a durable subscriber name, Designer changes the destination type to Topic when you save the JMS trigger.