WebSphere MQ HA using clustering software
We have discussed high availability clustering for the WebSphere Embedded JMS server in the previous section. This high availability solution can satisfy all J2EE messaging and HA requirements. Also, the Embedded WebSphere JMS server is as robust as WebSphere MQ.
However, as mentioned before, there are some situations when you need to use the more powerful external WebSphere MQ to extend messaging to heterogeneous environments or to more messaging application clients, as well as for message database persistency.
The queue managers in the Embedded WebSphere JMS servers are completely isolated; they have no channels either to other embedded JMS queue managers or to external WebSphere MQ queue managers.
The Embedded WebSphere JMS server cannot be used if an application requires access to heterogeneous non-JMS applications, or WebSphere MQ clustering, or the use of additional WebSphere MQ functions. WebSphere MQ can provide these functions.
The external WebSphere MQ cannot be installed in the same node with the Embedded WebSphere JMS server. The external queue manager must be Version 5.3 or above for XA coordination support.
Figure 11-8 shows a system that uses clustering software (such as HACMP, ServiceGuard, SCS, VCS, and MSCS) and hardware for a highly available WebSphere MQ system to support J2EE applications in IBM WAS Network Deployment V5.1. If the queue manager process or network or primary host fails, the queue manager as well as the queue data and log will fail over to the hot standby machine with the same service IP address. WASs can continue to process messages without message losses.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
