The webMethods clustering API for JMS provides support for Message Driven Beans (MDB). The webMethods API for JMS enables asynchronous communication between loosely coupled components.

Setting an MDB as a listener on the Broker cluster will result in an MDB listening on the specified destination of all the Brokers in the cluster. When a message arrives on any one of the destinations in the cluster, the MDB listener will be invoked and the messages will be passed to the consumer on a first-come-first-serve basis.

The webMethods Broker client-side clustering for JMS client applications relies on the JCA for communicating with the application server. As a JMS provider, we do not provide a JCA compliant resource adapter for communicating with the application servers. You must use a JCA Resource Adapter that implements the JCA 1.5 API standard for inbound communication and outbound communication.

As per the current technology trends, it is recommended that you use JCA (resource adapters) to communicate between an application server and the webMethods Broker used as a JMS provider.

The webMethods Broker used as a JMS provider installation includes the Generic Resource Adapter for JMS that uses the JMS client library and integrates the webMethods Broker used as a JMS provider (Broker) with an application server. The Generic Resource Adapter for JMS uses ASF functionality for inbound connections.