Building Your Event-Driven Architecture : Using Integration Server to Build a Client for JMS : Working with JMS Triggers : Managing Destinations and Durable Subscribers on the JMS Provider through Designer : Modifying Destinations or Durable Subscribers via a JMS Trigger in Designer
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 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 Broker. If you do not confirm the change, the durable subscriber will remain on Broker. You will need to use the 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 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 .
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback