176 Messaging Solutions in a Linux Environment
Figure 5-14 Scenario three under normal operation
For WebSphere MQ high availability to work in this scenario, the following
configurations are required on both brk1 and brk2.
1. We will again be using the MQ scripts that were discussed earlier in “Shell
scripts to manage MQ resources” on page 80. Make these scripts available
on the hosts brk1 and brk2. In addition, copy the script mqsMod.pl to
/etc/ha.d/resource.d.
2. Because the heartbeat software is already installed and configured on the
hosts brk1 and brk2 for scenario two, we only need to make slight
modifications to the setup. Refer to 4.2.3, “Configuring Linux-HA” on
page 125 for complete configuration of linux-ha.
3. Modify the etc/ha.d/haresources file on both brk1 and brk2 to include the
start and stop for the queue managers. Also there is no need to include the
ServeRAID failover script (see Example 4-9 on page 136) because both
machines have simultaneous access to the shared fiber enclosure. See
Example 5-14 for the final version of this configuration file.
Example 5-14 /etc/ha.d/haresources
brk1 IPaddr::192.168.10.201/24 mqsMod.pl::/var/mqm/::primary
brk2 IPaddr::192.168.10.202/24 mqsMod.pl::/var/mqm/::secondary
5.3.10 HA configuration summary
In summary, our high availability configuration works as shown in Table 5-2 on
page 177.
brk1
qmgr4
brk2
qmgr5
HeartBeat
/var/mqm/qmgrs/qmgr4
/var/mqm/qmgrs/qmgr5
/var/mqm/log/qmgr4
/var/mqm/log/qmgr5

Get Messaging Solutions in a Linux Environment now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.