DevOps Edition for Continuous Integration 10.4 | Service Development Help | Working with JMS Triggers | Creating a JMS Trigger | Adding JMS Destinations and Message Selectors to a JMS Trigger | Creating a Destination on the JMS Provider
 
Creating a Destination on the JMS Provider
If the JMS connection alias that the JMS trigger uses to retrieve messages is configured to manage destinations, you can create a destination on the JMS provider while using the JMS trigger editor.
Keep the following points in mind when creating destinations using Designer:
*The JMS connection alias used by the JMS trigger must use Universal Messaging, Nirvana, or webMethods Broker as the JMS provider.
Note: Prior to version 9.5 SP1, Software AG Universal Messaging was named webMethods Nirvana.
*The JMS connection alias used by the JMS trigger must be configured to manage destinations.
*The JMS connection alias must be enabled when you work with the JMS trigger.
*If the JMS connection alias creates a connection on a webMethods Broker in a webMethods Broker cluster, you will not be able to create a destination at the webMethods Broker.
* To create a destination on the JMS provider
1. In the Package Navigator view of Designer, open the JMS trigger that uses a JMS connection alias that connects to the JMS provider on which you want to create the destinations.
2. In the Trigger Settings tab, under JMS destinations and message selectors, click .
3. In the Destination Name column, click .
4. In the Destination List dialog box, click Create New Destination.
5. In the Create New Destination dialog box, provide the following information:
In this field...
Specify...
Destination Name
A name for the destination.
Destination Key
A name for the destination key. If you do not specify a destination key, Integration Server uses the destination name as the destination key.
In the Destination List, when a destination has a destination key Designer displays the destination name using this format: destinationKey (destinationName)
Destination Type
The type of destination. Select one of the following:
Select...
To...
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 you want to create a durable subscriber.
Durable Subscriber Name
A name for the durable subscriber. The name must be unique for the connection, where the connection name is the client ID of the JMS connection alias. The JMS provider (webMethods Broker, Universal Messaging, or Nirvana) will create the durable subscriber name using the client ID of the JMS connection alias and the specified durable subscriber name.
This field only applies if the destination is Topic (Durable Subscriber).
Order By
How webMethods Broker distributes messages received by this destination.
This field only apples if the JMS provider used y the trigger JMS connection alias is the webMethods Broker and the destination is Queue.
Select...
To...
Publisher
Distribute messages received by this destination one at a time in the order in which they were received from the publisher.
None
Distribute the messages received by this destination in any order.
This is the default.
Note: An order mode of publisher maps to a serial message processing mode. An order mode of none maps to a concurrent message processing mode.
6. Click OK to create the destination.
7. If you want the current JMS trigger to retrieve messages from the new destination, select the destination and click OK.
Designer adds the destination to the JMS destinations and message selectors list. If the Order By mode for the new destination does not match the existing message processing mode, Designer prompts you to change the processing mode.
Notes:
*Integration Server adds the new destination to the webMethods Broker as a shared-state client.
*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.
Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release