| Author |
Message
|
| saneben |
 Posted: Wed Jun 14, 2006 7:11 am Post subject: MQ clustering in Windows 2003 |
 |
|
Voyager
Joined: 04 Apr 2004
Posts: 96
|
Hi,
I have two servers which have windows 2003 installed they are not in MSCS because we do not have a storage.
I have a simple MQ series set up with one queue Manager. I want to do MQ clustering for load balancing only. But I have created the created the queue managers with the same name on both the servers is it possible to cluster this MQ. Any suggestions and links are welcome.
I read the MQ clustering manual and they tell of a sample with London and Newyork queue Managers. But my scenario is that the queue manager is single with the same name on both servers.
Regards
Sanjiv |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jun 14, 2006 7:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
From the cluster manual under Terminology (page 5 in the 5.3 version I have to hand):
| Quote: |
| Each cluster queue manager must have a name that is unique throughout all the clusters of which it is a member. |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 14, 2006 11:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Clustering will not in any way make these "the same queue manager".
It will always and only make them "two queue managers". And the queues on those queue manager that are clustered will always be different queues. They will happen to have the same name, and they will happen to be available for putting from the entire cluster, but they will always be separate and you will never be able to get the same message from both queues.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| saneben |
| Posted: Fri Jun 16, 2006 12:35 am Post subject: |
|
|
Voyager
Joined: 04 Apr 2004
Posts: 96
|
Sorry for the trouble again, I have two servers 1 and server2 But If I create the queue Manager with different names how will the MQ server on AIX connect to the queue managers. It will connect to server 1 when I create the channel which serverIP I should give and which queue manager name.
Sorry but I am confused here.
Regards
Sanjiv |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 16, 2006 12:44 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| saneben wrote: |
Sorry but I am confused here.
|
That would be both of us! Are you trying to set up a cluster or a client connection table able to connect to both queue managers?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| saneben |
| Posted: Fri Jun 16, 2006 1:34 am Post subject: |
|
|
Voyager
Joined: 04 Apr 2004
Posts: 96
|
Hi Vitor,
I have set up one windows Queue Manager to connect to the Aix MQ Queue Manager and the present set up is working fine in the test set up.
Now the project manager has given me another server and wants me to go MQ clustering for the windows. I read the Manual and asked for a storage device he told it is not possible immediately.
I need your advise do MQ clustering on windows and connect to the AIX MQ queue manager or tell them it is not possible to do MQ clustering with one QM.
Regards
Sanjiv |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jun 16, 2006 1:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It's not possible to do clustering with one queue manager; or it is but it's a very small and rather pointless cluster.
What is this storage device that you talk about? An external, possibly shared disc unit? Don't confuse MQ clustering which is used for workload balancing and network outages (like channels dropping) with hardware clustering to provide high availability. They're two different things. An MQ cluster can be achieved by defining a second queue manager on the same machine as the first (though there are a raft of reasons why you would or wouldn't which is off topic for this thread).
I would say you want a new queue manager on the new server you've been provided with then cluster it with the existing windows queue manager and the AIX one. The Clustering manual will tell you everything you need to know about the placement of queues etc, and this will solve your channel by the messages going to the "reachable" queue manager.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jun 16, 2006 2:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think you need to tell the project manager that you don't understand this assignment.
Maybe they will give you enough time for you to read the clustering manual some more, and read about MQ some more, and learn some more.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| saneben |
| Posted: Fri Jul 07, 2006 10:32 pm Post subject: |
|
|
Voyager
Joined: 04 Apr 2004
Posts: 96
|
Hi,
I have successfully installed Mqseries on a MSCS on a domain controller with failover in the test system. We used EMC as a storage device for the shared disk.
One doubt if I need to connect to Unix and special rights I have to give to the user?
Below is the steps followed for MSCS
1) Install MQ on node 1
2) Install MQ on node 2
3) Create QMgr on node 1
4) Move QMgr data and log files to shared disk(as explained in manual)
5) Put Qmgr under MSCS control(as explained in manual)
6) Test QMgr on node 1
Note : prior to step 7, make sure you close MQ explorer/services windows, Cluster Administrator and register a MSCS Resource Type(IBM Websphere MQ MSCS) reboot the server
7) Simulate failover by using Move Group
 This should make the MSCS move the QMgr to node 2
9) All the necessary queues and channels must be created in the Queue Manager.
10) Check the event viewer for any errors.
Regards |
|
| Back to top |
|
|
|
|
