WebLogic clustering is used for scalability, high availability, and parallel processing of the user and server requests. The cluster distributes the load across the cluster's Managed Server instances, and for the JMS queues each Server instance has its own queue member of a distributed queue.

An application requirement may need a single JMS queue, pinned to a Managed Server and not configured as a distributed queue, even though the WebLogic cluster is being used.

The requirement is valid but using a queue pinned to a single Managed Server brings a single point of failure to a production environment. If the Managed Server hosting the pinned queue crashes, the queue will be unavailable.

To handle this situation, WebLogic has a feature called Service Migration where the pinned queue can be moved from one Managed Server to another automatically when needed, bringing high availability to a pinned service.

In this recipe, we are...