Integrate Software AG Products Using Digital Event Services : Integration Server Administrator’s Guide : Configuring Integration Server for JMS Messaging : Working with JMS Connection Aliases : Creating a JMS Connection Alias : Allowing Destinations to be Managed through the JMS Connection Alias and Designer
Allowing Destinations to be Managed through the JMS Connection Alias and Designer
You can configure the JMS connection alias to enable Designer users to manage destinations and durable subscribers when working with JMS triggers. When the JMS connection alias is configured for managing destinations (i.e., the Enable Destination Management with Designer check box is selected), you can use Designer to create and modify destinations and durable subscribers on webMethods Broker or Software AG Universal Messaging.
Note:  
The ability to use Designer to manage destinations on Broker or Universal Messaging is a design-time feature. In a production environment, this functionality should be disabled.
To manage destinations on Broker, the following must be true
*The JMS connection alias must use Broker as the JMS provider.
*Broker must be Broker version 7.1 or higher.
*The versions of following three Broker jar files installed on Integration Server must be the 8.0 SP1 or higher versions of the files.
* Software AG_directory /common/lib/wm-brokerclient.jar
* Software AG_directory /common/lib/wm-jmsclient.jar
* Software AG_directory /common/lib/wm-jmsnaming.jar
To manage destinations on Universal Messaging, the following must be true:
*The JMS connection alias must use Universal Messaging as the JMS provider.
*Universal Messaging must be version 10.1.
For more information about using Designer to modify Destinations on the Broker or Universal Messaging, see webMethods Service Development Help.
Copyright © 2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback