| Author |
Message
|
| exerk |
 Posted: Thu May 27, 2010 12:59 pm Post subject: |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jeevan wrote: |
| ramires wrote: |
| jeevan wrote: |
| So, there is no concept of two queue managers and two server/client conn channels with separate host/ip |
ok, its the same queue manager and it can run on different machines. Is your mq cluster v7 qmgrs only?
Regards |
No. it does not have to be. But the MI qmgr needs to be on MQ7.0.1 or higher.
Also, the repository has to be in the highest version always. |
Pre-version 7.0.1 WMQ has NO concept of chaining in multiple CONNAME's, so your statement doesn't scan. Everything will work fine with a < V7.0.1 queue manager until your standby instance takes over - so what do you do then?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
 |
| fatherjack |
| Posted: Thu May 27, 2010 2:15 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| exerk wrote: |
| jeevan wrote: |
| ramires wrote: |
| jeevan wrote: |
| So, there is no concept of two queue managers and two server/client conn channels with separate host/ip |
ok, its the same queue manager and it can run on different machines. Is your mq cluster v7 qmgrs only?
Regards |
No. it does not have to be. But the MI qmgr needs to be on MQ7.0.1 or higher.
Also, the repository has to be in the highest version always. |
Pre-version 7.0.1 WMQ has NO concept of chaining in multiple CONNAME's, so your statement doesn't scan. Everything will work fine with a < V7.0.1 queue manager until your standby instance takes over - so what do you do then? |
I think the
| jeevan wrote: |
| No. it does not have to be |
relates to
| ramires wrote: |
| Is your mq cluster v7 qmgrs only? |
But not sure why MQ clusters have been introduced here unless ramires is confusing clustering with multi-instance queue managers.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu May 27, 2010 2:35 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| fatherjack wrote: |
| exerk wrote: |
| jeevan wrote: |
| ramires wrote: |
| jeevan wrote: |
| So, there is no concept of two queue managers and two server/client conn channels with separate host/ip |
ok, its the same queue manager and it can run on different machines. Is your mq cluster v7 qmgrs only?
Regards |
No. it does not have to be. But the MI qmgr needs to be on MQ7.0.1 or higher.
Also, the repository has to be in the highest version always. |
Pre-version 7.0.1 WMQ has NO concept of chaining in multiple CONNAME's, so your statement doesn't scan. Everything will work fine with a < V7.0.1 queue manager until your standby instance takes over - so what do you do then? |
I think the
| jeevan wrote: |
| No. it does not have to be |
relates to
| ramires wrote: |
| Is your mq cluster v7 qmgrs only? |
But not sure why MQ clusters have been introduced here unless ramires is confusing clustering with multi-instance queue managers. |
You are right. We do not need to introcude cluster here as these two are totally different topics.
You are also right in that my answer relates to the question that all cluster member does not have to be v7.0.1. But both MQ server that hold MI active and standby instance must be running MQ 7.0.1 or higher.
Last edited by jeevan on Thu May 27, 2010 2:40 pm; edited 1 time in total |
|
| Back to top |
|
|
| ramires |
| Posted: Thu May 27, 2010 2:40 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
no fatherjack, I'm not confusing mq cluster with MI queue manager 
Cluster was introduced by:
| jeevan wrote: |
| ...( we use it in cluster)... |
In fact doesn't matter if this is a cluster with mixed mq versions or a single v6 queue manager talking to a v7 MI queue manager.
I was trying to understand how jeevan addresses the hostname/ip switchover when the MI queue manager moves from one machine to the other. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu May 27, 2010 2:45 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| ramires wrote: |
no fatherjack, I'm not confusing mq cluster with MI queue manager
Cluster was introduced by:
| jeevan wrote: |
| ...( we use it in cluster)... |
In fact doesn't matter if this is a cluster with mixed mq versions or a single v6 queue manager talking to a v7 MI queue manager.
I was trying to understand how jeevan addresses the hostname/ip switchover when the MI queue manager moves from one machine to the other. |
It is very simple. in the conname of the channel, you will have like this:
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
But be carefull, there is slight difference in 7.0.1.0 and 7.0.1.1. I do not remember exactly, but I think, the first reqires the conname be in single quote but later does not. |
|
| Back to top |
|
|
| ramires |
| Posted: Thu May 27, 2010 2:51 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| jeevan wrote: |
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
|
but a v6 queue manager doesn't recognize that syntax with two hostnames. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu May 27, 2010 2:53 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| jeevan wrote: |
| ramires wrote: |
no fatherjack, I'm not confusing mq cluster with MI queue manager
Cluster was introduced by:
| jeevan wrote: |
| ...( we use it in cluster)... |
In fact doesn't matter if this is a cluster with mixed mq versions or a single v6 queue manager talking to a v7 MI queue manager.
I was trying to understand how jeevan addresses the hostname/ip switchover when the MI queue manager moves from one machine to the other. |
It is very simple. in the conname of the channel, you will have like this:
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
But be carefull, there is slight difference in 7.0.1.0 and 7.0.1.1. I do not remember exactly, but I think, the first reqires the conname be in single quote but later does not. |
Once more, and with feeling...
YOU CANNOT, REPEAT CANNOT, CHAIN IN CONNAME's IN CHANNEL CONFIGURATIONS FOR QUEUE MANAGERS BELOW V7.0.1!
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Thu May 27, 2010 2:54 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
So had you asked this
| ramires wrote: |
| I was trying to understand how jeevan addresses the hostname/ip switchover when the MI queue manager moves from one machine to the other. |
rather than this
| ramires wrote: |
| ok, its the same queue manager and it can run on different machines. Is your mq cluster v7 qmgrs only? |
we might have got there a bit sooner. 
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu May 27, 2010 2:54 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| ramires wrote: |
| jeevan wrote: |
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
|
but a v6 queue manager doesn't recognize that syntax with two hostnames. |
Thank you! I, and fatherjack were obviously not making ourselves crystal clear enough 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Thu May 27, 2010 3:03 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| ramires wrote: |
| jeevan wrote: |
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
|
but a v6 queue manager doesn't recognize that syntax with two hostnames. |
Can we start this thread again please when I'm sober 
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| J.D |
| Posted: Thu May 27, 2010 3:07 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| In the Cluster, if qmgr's are mix of v6.0 and v7.0.1 then blank CONNAME has to be used on multi instance qmgr...it is not recommended to use MI qmgr as full repository. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu May 27, 2010 3:11 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| J.D wrote: |
| In the Cluster, if qmgr's are mix of v6.0 and v7.0.1 then blank CONNAME has to be used on multi instance qmgr...it is not recommended to use MI qmgr as full repository. |
I think I must have had a few of what fatherjack had - please explain how a blank CONNAME value would work...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| J.D |
| Posted: Thu May 27, 2010 3:13 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| exerk wrote: |
| J.D wrote: |
| In the Cluster, if qmgr's are mix of v6.0 and v7.0.1 then blank CONNAME has to be used on multi instance qmgr...it is not recommended to use MI qmgr as full repository. |
I think I must have had a few of what fatherjack had - please explain how a blank CONNAME value would work... |
Look in page 22 in the below link.
http://www-01.ibm.com/support/docview.wss?uid=swg27018127&aid=1 |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu May 27, 2010 3:23 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| exerk wrote: |
| jeevan wrote: |
| ramires wrote: |
no fatherjack, I'm not confusing mq cluster with MI queue manager
Cluster was introduced by:
| jeevan wrote: |
| ...( we use it in cluster)... |
In fact doesn't matter if this is a cluster with mixed mq versions or a single v6 queue manager talking to a v7 MI queue manager.
I was trying to understand how jeevan addresses the hostname/ip switchover when the MI queue manager moves from one machine to the other. |
It is very simple. in the conname of the channel, you will have like this:
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
But be carefull, there is slight difference in 7.0.1.0 and 7.0.1.1. I do not remember exactly, but I think, the first reqires the conname be in single quote but later does not. |
Once more, and with feeling...
YOU CANNOT, REPEAT CANNOT, CHAIN IN CONNAME's IN CHANNEL CONFIGURATIONS FOR QUEUE MANAGERS BELOW V7.0.1! |
I am tryinig to clarify but I am not sure why we are still confused.
Point summary:
1. MI queue manager can be a part of cluster which could have v6 qmgr and v7 qmgr. But both instance of MI qmgr has to run jn vesion 7.0.1 or higher
2. in the MI qmgr conname, the entry are like:
CONNAME(activeinstancehostname(port). standbyinstancehostname(port))
3. I never said, v6 qmgr accept two entries in CONNAME
4. MI qmgr is not two separate queue manager, it is a qmgr with multiinstance ( multi means two here)
creating second instance is just change in configuration in second server not creating with crtmqm command.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/be13670_.htm
5. The sharable stoarage has to be capable of file locking as MI works based on file locking and unlocking mechanism
# Run amqmfsck, without any options, on each system to check basic locking
# Run amqmfsck on both WebSphere MQ systems simultaneously, using the -c option, to test writing to the directory concurrently.
# Run amqmfsck on both WebSphere MQ systems at the same time, using the -w option, to test waiting for and releasing a lock on the directory concurrently.
http://josephamrithraj.wordpress.com/2010/04/22/multi-instance-queue-managers-websphere-mq-v7/
6. Client and channel reconnection feature is reqauired to transfer WebSphere MQ connections to second/failover node when active node fails. So all app needed to use mq client v7.
Last edited by jeevan on Thu May 27, 2010 3:58 pm; edited 2 times in total |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu May 27, 2010 3:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| J.D wrote: |
| exerk wrote: |
| J.D wrote: |
| In the Cluster, if qmgr's are mix of v6.0 and v7.0.1 then blank CONNAME has to be used on multi instance qmgr...it is not recommended to use MI qmgr as full repository. |
I think I must have had a few of what fatherjack had - please explain how a blank CONNAME value would work... |
Look in page 22 in the below link.
http://www-01.ibm.com/support/docview.wss?uid=swg27018127&aid=1 |
Well, I see what you are referring to on page 22, but I don't see how it could work. There is nothing else in that presentation that talks about how a blank conname could work. In fact the only other examples (on page 15), do have connames filled in.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
