Clustering MSG 7.0 u3 + Indexing and Search Service

Question

Messaging Server 7 Update 3
Indexing and Search Service 1
Indexing and Search service requires IMQ broker configured.
In clustered msg srv deployments with ISS enabled, what is the correct way to deploy IMQ:
- as a clustered service with affinity configured between msg and imq
or
- imq instance running on each node of the cluster
Thanks,
D.

Answer 1

JMQ should be installed on each cluster node with something like this:
Grab mq4_1-installer-SunOS.zip (SPARC) or mq4_1-installer-SunOS_X86.zip (x86)
Slap JMQ installer somewhere like /usr/local/src and unzip it
mq4_1-installer/installer or mq4_1-installer/installer -nodisplay
Hammer through the install and you should be ready to go
Now the actual setup of JMQ:
vi /etc/imq/imqborkerd.conf
Change {color:#0000ff}*AUTOSTART=NO*{color} to {color:#0000ff}*AUTOSTART=YES*{color}
If your host has Sun Java Application Server (SJAS) or GlassFish on it (or will) set {color:#0000ff}*ARGS=port 7777*{color}
Note: SJAS 9.x and GlassFish come with their own install of JMQ and if you are mixing Messaging Server with SJAS/GlassFish you will want the Messaging Server JMQ to have its own port
Start JMQ -*{color:#0000ff} /etc/init.d/imq start{color}*
Reset the admin password:*{color:#0000ff} imqusermgr update -u{color}* {color:#0000ff}*admin*{color} *{color:#0000ff}-p{color}* *{color:#ff0000}<password>{color}*
Disable the guest account: *{color:#0000ff}imqusermgr update -u guest -a false{color}*
Setup a user account (jesuser in this example) to use for Messaging Server integration: {color:#0000ff}*imqusermgr add -u*{color} *{color:#ff0000}jesuser{color}{color:#0000ff}{color:#ff0000} {color}-g user -p* {color:#ff0000}*jesuser*
{color:#000000}cd /opt/sun/coms/messaging/sbin (or messaging64 if rolling 64-bit Messaging Server)
./configutil -o local.store.notifyplugin.jmqnotify.NewMsg.enable -v 1
./configutil -o local.store.notifyplugin.jmqnotify.UpdateMsg.enable -v 1
./configutil -o local.store.notifyplugin.jmqnotify.DeleteMsg.enable -v 1
./configutil -o local.store.notifyplugin.jmqnotify.maxHeaderSize -v 1024
./configutil -o local.store.notifyplugin.jmqnotify.jmqHost -v *"*127.0.0.1*"*{color}
{color}{color:#000000} (this could also be the IP address of your cluster node, not the service address but the actual IP address of the node)
./configutil -o local.store.notifyplugin.jmqnotify.jmqPort -v "7777"{color:#ff0000} {color}(if you have changed from the default port of 7676 enter it here)
{color}./configutil -o local.store.notifyplugin.jmqnotify.jmqUser -v
"jesuser" (substitute the JMQ user that you created earlier)
{color:#000000}./configutil -o local.store.notifyplugin.jmqnotify.jmqPwd -v "jesuser" (substitute the password for the JMQ user that you specified earlier)
./configutil -o local.store.notifyplugin.jmqnotify.DestinationType -v "queue"
./configutil -o local.store.notifyplugin.jmqnotify.jmqQueue -v "jesms"
./configutil -o local.store.notifyplugin.jmqnotify.Priority -v 3
./configutil -o local.store.notifyplugin.jmqnotify.ttl -v 1000
./configutil -o local.store.notifyplugin.jmqnotify.Persistent -v 1
./configutil -o local.store.notifyplugin.jmqnotify -v '/opt/sun/comms/messaging/lib/libjmqnotify$jmqnotify'{color}
Repeat on each node that will master HA Messaging Server.
Edited by: nate_keegan on Feb 17, 2010 1:42 PM - the rich text editor is acting strangely, reverting to text for configutil section