In a clustered environment, you can pin the continuous JMS queue to one member of the cluster.
The following diagram shows an example of a cluster configuration on an application server. The continuous queue receives JMS producer messages and processes the JMS consumer messages.
In the example, three application servers exist in the clustered environment. The continuous JMS queue is pinned to one member of the cluster.
The processing occurs when the integration framework receives enterprise service messages by using HTTP, enterprise beans, and SOAP actions. The load balancer directs the application server to drop enterprise service messages into the continuous queue. Each member of the cluster places messages into the queue, which exists on one member of the cluster.
An integration cron task delivers enterprise service messages from flat or XML files and interface tables. The cron tasks that place messages into the queue can run on any server in the cluster.
After messages are in the queue, all application servers can simultaneously pull messages from the queue and process them into the system. Message-driven beans must be enabled on each application server in the cluster.