A JMS trigger group is a collection of two or more JMS triggers whose names match a particular naming convention. Typically, the JMS triggers are nearly identical, with the main difference being the JMS connection alias used to retrieve messages. A JMS trigger group can be beneficial when the same message type is sent to more than one queue or topic across multiple JMS providers. This can occur when the JMS provider supports a load balancer on the producer side. In such a scenario, the receiving Integration Server would need to poll for messages across each of the providers. That is, the subscribing Integration Server needs to have a subscriber for each queue or topic on each provider. A JMS trigger group provides a way to more easily create and manage these triggers.

Integration Server considers a JMS trigger to be a member of a JMS trigger group when the trigger name portion of the fully qualified name includes the following suffix:

_groupTag_Id

Where

groupTag is the unique tag used to indicate a trigger group. By default, the groupTag is WMTG. You can change the groupTag using the watt.server.jms.trigger.groupTag server configuration parameter.

Id is a unique identifier for the trigger in the trigger group. This might be a number or text that indicates what differentiates the trigger from others in the group. For example, Integration Server considers the following two JMS triggers to be in the same JMS trigger group:

Additionally, Integration Server considers a JMS trigger to be a member of a JMS trigger group if other JMS triggers have the same fully qualified name followed by the _groupTag_Id suffix.

For example, Integration Server considers the following three triggers to be in the same JMS trigger group: