| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ cluster Setup - Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| sbabbar98 |
 Posted: Tue Mar 15, 2005 10:52 am Post subject: MQ cluster Setup - Question |
 |
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
Hello ,
I have couple of questions regarding MQ Cluster Setup.I am trying to setup a new MQ CLuster .
In the Current setup we have 3 Systems running Sun Solaris , with MQ 5.3 CSD09 which are WAS Clustered, two of them are App Servers ( ap01 , ap02) and third one is the MQ Server(mq01) . we will be adding the second MQ Server (mq02) later .
What I want to achieve is when ever message is Put in to any of the AppServer ( ap01 , ap02) it should get delivered to MQ Server( mq01) .
As per the IBM setup Install docs steps are :
- create QM on all three hosts.
- Alter QM defination to hold Full repos.
- Setup Rcvr Channel on each QM - In this CONNAME will be the fullname of the host creating channel on.
- Setup sender channel on each QM - In this setup I am putting CONNAME to be name of the MQ Server (mq01) for each of the App Server apq01 and apq02 .
So my Question is when I create Sender channel on the MQ Server (mq01) what CONNAME should I use ? Should it be the name of its own hostname or ?
Also even if anyone knows how can I take Backup dump of the Current MQ Config including all Queues/channel / Repos etc so in case if my System Crashed , I can just restore the Current Config .Any Pointers appreciated.
Thanks much in advance
SB |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Mar 15, 2005 10:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your last question is answered with a support pack.
What are you trying to achieve with this MQ Cluster?
You say
| Quote: |
| What I want to achieve is when ever message is Put in to any of the AppServer ( ap01 , ap02) it should get delivered to MQ Server( mq01) . |
And if that's true, why do you need an MQ Cluster at all?
Are you trying to create a FAILOVER cluster? or a Redundant MQ Server?
Because you can't use MQ Clustering for that.
Are you trying to load balance the work that your mq01 does? Because that IS what MQ Clustering is for. But in your case how it works depends on what you have running on ap01 and ap02.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sbabbar98 |
| Posted: Tue Mar 15, 2005 12:28 pm Post subject: |
|
|
Newbie
Joined: 13 Mar 2005
Posts: 9
|
| jefflowrey wrote: |
Your last question is answered with a support pack.
What are you trying to achieve with this MQ Cluster?
You say
| Quote: |
| What I want to achieve is when ever message is Put in to any of the AppServer ( ap01 , ap02) it should get delivered to MQ Server( mq01) . |
And if that's true, why do you need an MQ Cluster at all?
Are you trying to create a FAILOVER cluster? or a Redundant MQ Server?
Yes, I would be creating a FAIOVER CLuster so just in case if one MQ server fails , messages can be picked from Second MQ Server and Processed.but Right now I have only one MQ Server (mqs0) in plan and would be adding second Failover MQ Server (mqs02) shortly IF I had 2 MQ Server then it would have been easier I could have just given CONNAME of the second MQ Server while creating sender channel but since I have only one MQ Server currently , I am wondering what to put the name of CONNAME Hostname when creating sender channel
Because you can't use MQ Clustering for that.
Are you trying to load balance the work that your mq01 does? Because that IS what MQ Clustering is for. But in your case how it works depends on what you have running on ap01 and ap02. |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 15, 2005 12:43 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, you want a redundant MQ on one physical machine...?
You can't do that.
If you want "immediate" availability of messages after a qmgr failure, then you have to use Hardware clustering, not MQ Clustering. And you can't do hardware cluster failover with one piece of hardware!
If you want LIMITED failover, with new messages going to a different qmgr after a qmgr failure, then you can do that with MQClustering. But messages already on the failed qmgr will STAY on that qmgr until that qmgr is recovered.
Even with one piece of hardware, you have to have each queue manager using a different Port for it's listener. So the conname is still different, since the conname includes Port information.
And again, how you set up the limited failover you get with MQClustering depends on what you have installed on your APP servers. If you have an MQClient, then you have to write your application to take care of the failover when the client connection goes away.
If you have an MQServer on the app box, then you don't have to worry about it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
