What is Client-Side Clustering for JMS Client Applications?
The webMethods client-side clustering for JMS feature includes a capability that allows you to group multiple Brokers into a single unit of functioning called a Broker cluster. All the Brokers in a cluster share the same metadata. The Broker metadata consists of document-type (Broker events) and client-group information. If you change the metadata of one Broker in the cluster, the metadata of all the Brokers in the cluster is updated and synchronized.
You can use a Broker cluster:
To
scale your messaging system horizontally, allowing it to handle larger messaging loads (load-balancing).
Note:
Delivery of messages in the published order is not guaranteed for all the supported load balancing policy. Use the webMethods client-side clustering for JMS feature when the message ordering is not important.
To increase the
availability of your messaging system. In the event of an outage, when the JMS client application reconnects after receiving the connection exception from the
webMethods API for JMS, the
webMethods API for JMS switches the publishing task to another
Broker in the cluster based on the policy.