Software AG Products 10.5 | Administering Integration Server | Configuring Integration Server for JMS Messaging | Working with JMS Connection Aliases | Creating a JMS Connection Alias | Allowing Multiple Connections for a JMS Connection Alias | About the Connection Client ID
 
About the Connection Client ID
The connection client ID is the JMS client identifier associated with the connections established by a JMS connection alias. The connection client ID that Integration Server uses for a connection created from a JMS connection alias depends on one or more of the following:
*The value of the Connection Client ID field for the JMS connection alias.
*The connection client ID specified in the Connection Factory used by the JMS connection alias.
*Whether the JMS connection alias is configured to create a new connection for each JMS trigger. That is, whether or not the Create New Connection per Trigger check box is selected.
Using the above information, Integration Server determines the connection client ID as follows:
*If only the JMS connection alias specifies the connection client ID, Integration Server uses this value for any connections created from the alias. When connecting to the webMethods Broker natively (the Create Connection Using list is set to Native webMethods API), Integration Server always uses the connection client ID from the JMS connection alias.
*If only the Connection Factory specifies the connection client ID, Integration Server uses this value for any connections created from the alias.
*If the JMS connection alias and the Connection Factory specify the connection client ID, Integration Server uses the value in the Connection Factory. This is true when working with all JMS providers, including the webMethods Broker.
*When the Create New Connection per Trigger check box is not selected, each JMS trigger that uses the JMS connection alias will use the same connection. Each connection will have the same connection client ID.
*When the Create New Connection per Trigger check box is selected, each JMS trigger that uses the JMS connection alias will create its own connection to the JMS provider.
*If Integration Server uses the connection client ID in the Connection Factory, each connection for a JMS trigger will have the same connection client ID.
*If Integration Server uses the connection client ID from the JMS connection alias, each connection for a JMS trigger will be unique to the JMS trigger. The connection client ID will consist of the value of the Connection Client ID field in the JMS connection alias plus the fully qualified name of the JMS trigger.
Note:
To receive messages in a load balanced manner, each JMS trigger must connect to the webMethods Broker using the same connection client ID. Because the Create New Connection per Trigger option can change the connection client ID, you must be sure that use of this option is consistent across all Integration Servers across the Integration Server group.