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.

Modifying Destinations or Durable Subscribers via a JMS Trigger in Designer

If a JMS trigger uses a JMS connection alias that is configured to manage destinations, you can modify the destination or durable subscribers while editing a JMS trigger. Changes to destinations or durable subscriptions can result in unused durable subscriptions on the JMS provider. Changing destinations can make the JMS trigger out of sync with the destination. For example, when using the webMethods Broker, modifying the destination could result in out of sync Shared State or Order By mode settings.

When you make a change that results in a change to a destination or durable subscriber, Designer informs you about the necessary change and then prompts you to confirm making change to the destination or durable subscriber on the JMS provider.

For example, if you change the name of the durable subscriber for a Topic (Durable Subscriber) destination, Designer displays a message stating, “By making this change the trigger will no longer subscribe to durable subscriber oldDurableSubscriberName. Would you like to remove this durable subscriber from the JMS provider?” If you confirm the change, Integration Server removes the durable subscriber from webMethods Broker. If you do not confirm the change, the durable subscriber will remain on webMethods Broker. You will need to use the webMethods Broker interface in My webMethods to remove the durable subscriber.

Note: If another client, such as another JMS trigger, currently connects to the queue or durable subscriber that you want to modify or remove, then Integration Server cannot update or remove the queue or durable subscriber. If the JMS provider is webMethods Broker, updates must be made through My webMethods. If the JMS provider is Universal Messaging, updates must be made through Universal Messaging Enterprise Manager. If the JMS provider is Nirvana, updates must be made through Nirvana Enterprise Manager.

For more information about managing destinations and durable subscriptions on the JMS provider, see Managing Destinations and Durable Subscribers on the JMS Provider through Designer.