Managing Destinations and Durable Subscribers on the JMS Provider through Designer
When editing a JMS trigger in Designer, you can create and manage destinations and durable subscribers on Software AG Universal Messaging, webMethods Nirvana, or webMethods Broker. Specifically, you can do the following:
Create a destination.
Create and delete a durable subscriber.
Select the destination from which you want the JMS trigger to receive messages from a list of existing destinations.
Select a durable subscriber that you want the JMS trigger to use from a list of existing durable subscribers for a specified topic.
Change the Shared State or Order By mode for a queue or durable subscriber by changing the message processing mode of the JMS trigger. You can do this only when
webMethods Broker is the JMS provider only.
Designer uses the JMS connection alias specified by the JMS trigger to make the changes on the JMS provider. To manage destinations on the JMS provider, the JMS connection alias that the JMS trigger uses must be
Configured to manage destinations
Enabled when you create and edit the JMS trigger.
To manage destinations on
webMethods Broker,
Integration Server must be version 8.0 SP1 or higher.
To manage destinations on
Universal Messaging,
Integration Server must be version 9.0 SP1 or higher.
Note:
Prior to version 9.5 SP1, Software AG Universal Messaging was named webMethods Nirvana.
For a complete list of the requirements for using Designer to manage destinations and durable subscribers on the JMS provider, see webMethods Integration Server Administrator’s Guide.
Note:
The ability to use Designer to manage JMS destinations on webMethods Broker, Nirvana, and Universal Messaging is a design-time feature. In a production environment, this functionality should be disabled.