Integration Server 10.3 | JMS Client Development Guide | Consuming JMS Messages Concurrently in a Load-Balanced Fashion | Configuring JMS Triggers, Integration Server, and webMethods Broker for Load-Balancing
 
Configuring JMS Triggers, Integration Server, and webMethods Broker for Load-Balancing
 
Automatic Load Balancing Configuration for Durable Subscribers when Using the webMethods Broker
To perform load-balancing while consuming messages concurrently from destinations on the webMethods Broker, the following must be true:
*The JMS trigger must receive messages from a topic using a durable subscriber or from a queue.
*The JMS trigger must specify a JMS connection alias that configures a connection to the webMethods Broker.
*The JMS trigger must process messages concurrently.
*The JMS trigger must be configured identically on all of the Integration Servers across which you are load-balancing message consumption.
*The queue or durable subscriber must be configured to share state. Sharing client state allows multiple clients, each using its own session, to process messages from a single destination in parallel, on a first-come, first-serve basis. To configure state sharing for a queue or durable subscriber, use the Broker user interface in My webMethods. You can also configure state sharing as part of creating the destination or durable subscriber in Designer. For more information about configuring queues and durable subscribers, see Administering webMethods Broker.
If the JMS trigger specifies a JMS connection alias that is configured to manage destinations on the webMethods Broker, Integration Server and Designer can configure state sharing for the durable subscriber automatically.
*The JMS connection alias must be configured identically on all of the Integration Servers across which you are load-balancing message consumption.