Ruud,
Thanks again, I think you've told me all I need to know for now, you summed it
up in your first paragraph about weighing the cost/effort against the risk.
Unfortunately Iam in a support role and cannot influence the configuration to a
great degree but I believe our conversation has exposed
ave a picture - in, say, a Word document?
Cheers ... Ruud
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of John
Basevi
Sent: 06 June 2002 10:25
To: [EMAIL PROTECTED]
Subject: Re: Communication between Non-cluster Q-Managers and a Cluster
Ruud,
Many thanks -
Ruud,
Many thanks - its as I suspected. Can I summarize and get you to confirm.
A Cluster of 2 QMs will require a further 2 Gateway QMs in the cluster to accept
messages from applications/other QMs and distribute them to shared cluster
queues hosted by the main QMs.
Applications putting to the
est to ask IBM).
HTH ... regards ... Ruud
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of John
Basevi
Sent: 05 June 2002 14:39
To: [EMAIL PROTECTED]
Subject: Communication between Non-cluster Q-Managers and a Cluster
How do I configure a non-cluster Q-
How do I configure a non-cluster Q-Manager to send messages to a cluster of
queue managers in a fault tolerant manner aside from creating an overlapping
cluster?
The way I understand it the sender channel configured on the external Q-Manager
explicitly references a particular machine in the clust
