| Author |
Message
|
| zpat |
 Posted: Wed Aug 17, 2011 2:05 am Post subject: |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Use of MI requires all connected clients and QMs to have multiple connection strings.
Whilst v7 may support this - many client applications don't use a CCDT and can't accept a list of connection addresses. Also auto-reconnect may not work for reasons like using base Java classes. So MI not a pancea (assuming that you have NFS v4 storage anyway).
If you want the newly active queue manager to have the same IP, then the best option with MI is to use a DNS name (not a hostname) for all connections to that QM.
Update the DNS name after failover - this is a manual process although you could run a command from a MQ service - if you can code a command to perform the DNS update (fairly complex).
You say this is not a HA environment - do you have SAN?
And you still didn't tell us the QM platform (the OS)! |
|
| Back to top |
|
 |
| kalyandharanikota |
| Posted: Wed Aug 17, 2011 2:08 am Post subject: |
|
|
Novice
Joined: 16 Aug 2011
Posts: 11
|
| can i know why the IP address changes after the failover. |
|
| Back to top |
|
|
| kalyandharanikota |
| Posted: Wed Aug 17, 2011 2:10 am Post subject: |
|
|
Novice
Joined: 16 Aug 2011
Posts: 11
|
|
| Back to top |
|
|
| zpat |
| Posted: Wed Aug 17, 2011 2:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
The IP changes because the second (standby) copy of the same queue manager is running on a different host.
It's not a problem if MQ client apps can use a CCDT - can they?
What connects directly to this QM, apps - other QMs? What sort of apps (language).
If the client apps connect to a local QM and that QM connects to the MI one - then again not a problem. |
|
| Back to top |
|
|
| kalyandharanikota |
| Posted: Wed Aug 17, 2011 2:42 am Post subject: |
|
|
Novice
Joined: 16 Aug 2011
Posts: 11
|
Yes,the client appl will use the ccdt.
The appl will connect directly to qm,xml |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Aug 17, 2011 2:56 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| kalyandharanikota wrote: |
| Yes,the client appl will use the ccdt. |
OK, so that solves your issue in regard to the different CONNAME values for an MI queue manager.
| kalyandharanikota wrote: |
| The appl will connect directly to qm,xml |
Presumably this is the application that has a duplicate of itself residing on the passive server, and that you have considered how to fail-over the application too?
_________________
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 |
|
|
| zpat |
| Posted: Wed Aug 17, 2011 3:52 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Use the V7 client and place both hostnames in the connection string in the CCDT for this QM.
You can also use the V7 client auto-reconect feature if you want to. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Aug 17, 2011 3:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| zpat wrote: |
| Use the V7 client and place both hostnames in the connection string in the CCDT for this QM. |
Or define them as 'separate' channels for non-V7.0.1 clients 
_________________
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 |
|
|
| kalyandharanikota |
| Posted: Wed Aug 17, 2011 5:10 am Post subject: |
|
|
Novice
Joined: 16 Aug 2011
Posts: 11
|
| Thanks for the valued feedback.. |
|
| Back to top |
|
|
|
|
