websphere mq - IBM WAS7 Queue Factory Configuration to an MQ Cluster -

websphere mq - IBM WAS7 Queue Factory Configuration to an MQ Cluster -

i'm trying configure clustered websphere application server connects clustered mq.

however, the info have details 2 instances of mq different host names, server channels , queue manager belongs same mq cluster name.

on websphere console, can see input fields hostname, queue manager , server channel, cannot find can specify multiple mq details.

if pick 1 of mq detail, mq clustering still work? if not, how enable mq clustering given details have?

websphere mq clustering affects behavior of how queue managers talk amongst themselves. not alter how application connects or talks queue manager question asked seems assuming sort of clustering behavior not nowadays in wmq.

to set app server 2 addresses, please see configuring multi-instance queue manager connections websphere mq messaging provider custom properties in v7 knowledge center instructions on how configure connection mill multi-instance conname value.

if specify valid qmgr name in connection mill , qmgr app connects doesn't have specific name connection rejected. multi-instance conname used connect multi-instance qmgr. single highly available queue manager can @ 1 of 2 different ip addresses using real qmgr name works in case. if qmgrs app connecting 2 distinct , different-named queue managers, described, should specify asterisk (a * character) queue manager name in connection mill described here. way app not check name of qmgr when gets connection.

if pick 1 of mq detail, mq clustering still work? if not, how enable mq clustering given details have?

depends on mean "clustering". if believe app see 1 logical queue hosted 2 queue managers, no. that's not how wmq clustering works. each queue manager hosting clustered queue gets subset of messages sent queue. apps getting queue hence ever see local subset.

but if "clustering" intend connect alternately 1 or other of 2 queue managers , transmit messages queue in same cluster not hosted on either of 2 qmgrs connect, yes work fine. if connection mill knows of 1 of 2 qmgrs connect qmgr, , sending messages cluster still work. set described in links i've provided , app able connect either of 2 qmgrs , can test stopping channel on 1 connects , watching connect other one.

good luck!

update:

to clear detail provide similar hostname01, qmgr01, queuea, serverchannel01. , other hostname02, qmgr02, queuea, serverchannel02.

wmq clients connect 2 different qmgrs using multi-instance conname when...

the channel name used on both qmgrs same the application uses asterisk (a * character) or space qmgr name when connection request made (i.e. in connection factory).

it possible have wmq connect 1 of several different queue managers channel name differs on each using client connection definition table, known ccdt. ccdt compiled artifact create using mqsc commands define clntconn channels. contains entries each of qmgrs client eligible connect to. each can have different qmgr name, host, port , channel. however, when defining ccdt administrator defines entries such qmgr name replaced application high level qualifier. example, payroll app wants connect 1 of 3 different qmgrs. wmq admin defines ccdt 3 entries uses pay01, pay02, , pay03 qmgr names. note not need match actual qmgr names. application specifies qmgr name pay* selects 3 qmgrs in ccdt.

please see using client channel definition table websphere mq classes jms more details on ccdt.

is mq cluster not similar application server clusters?

no, not @ all.

wherein two-child nodes connected cluster. , f5 url used distribute load each node. not wmq come cluster url / f5 send message , partitioning of messages transparent?

no. wmq cluster provides namespace within applications , qmgrs can resolve non-local objects such queues , topics. thing ever connects websphere mq cluster queue manager. applications , human users always connect specific queue managers. there may set of interchangeable queue managers such ccdt, each independent.

with messaging engine may run on several nodes, provides single logical queue applications can messages. wmq each node hosting queue gets subset of messages , application consuming messages sees subset.

http stateless , f5 url works great. when maintain session, session exists optimize away connection overhead , tends short lived. wmq client channels stateful , coordinate both single-phase , two-phase units of work. if application fails on qmgr during uow, has no way reconcile uow.

because of nature of wmq connections, f5 never used between qmgrs. used between client , qmgr connection balancing , not message traffic balancing. furthermore, absence or presence of mq cluster exclusively transparent application which, in either case, connects qmgr and./or set messages. utilize of multi-instance conname or ccdt file makes connection more robust providing multiple equivalent qmgrs client can connect has nil whatever wmq clustering.

does help?

please see:

clustering how clusters work queue manager groups in ccdt connecting websphere mq mqi client applications queue managers

websphere-mq ibm-was