JMS Queues
194
Integration Guide
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.
WebLogic Server Sequential Queue Cluster
The following diagram shows one example of a cluster configuration on the
WebLogic Server. The sequential queue receives JMS producer messages and
processes the JMS consumer messages.
In the example, three application servers exist in the clustered environment. The
sequential 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
sequential 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
To Next Page
Loading...