In the Active/Standby configuration, Node1 is the primary LifeKeeper server. It protects the WebSphere MQ queue managers. All storage resides on a shared array between the cluster servers. While Node2 may be handling other applications/services, it acts only as a backup for the WebSphere MQ resources in LifeKeeper’s context. The directory /var/mqm is located on shared storage. The primary server can run as many queue managers as it can handle.
Figure 7 Active/Standby Configuration with Local Storage
- The clients connect to the WebSphere MQ servers using the LifeKeeper protected IP 192.168.1.100 designated to float between the servers in the cluster.
- The directory /var/mqm is located on shared storage.
- Each queue manager has modified the listener object to contain a unique port number.