Mission:Messaging, Migration, failover, and scaling in a WebSphere MQ cluster
From the developerWorks archives
Date archived: May 15, 2019 | First published: November 12, 2008
Certain aspects of service orientation are best served using an IBM® WebSphere® MQ cluster. The cluster provides the location independence, run time resolution of names, and concurrency required by SOA applications. For these reasons, adoption of SOA is driving migrations from point-to-point messaging networks to clustered environments. This article looks at how migration, failover, and the scaling of queue managers are affected in an SOA context. This content is part of the IBM WebSphere Developer Technical Journal.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.