| Author |
Message
|
| sushilsingh27 |
 Posted: Sun Nov 05, 2006 4:35 am Post subject: Connecting AIX from windows MQseries Client |
 |
|
Novice
Joined: 05 Nov 2006
Posts: 13
|
Can somebody guide my ,Why Advice is being provided on the use of WebSphere MQ clients, instead of queue managers, on several Windows systems connecting to a WebSphere MQ queue manager on an AIX system.
Thanks in advance |
|
| Back to top |
|
 |
| zpat |
| Posted: Sun Nov 05, 2006 4:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| They are free and they require little or no management. |
|
| Back to top |
|
|
| sushilsingh27 |
| Posted: Sun Nov 05, 2006 5:31 am Post subject: Connecting AIX from windows MQseries Client |
|
|
Novice
Joined: 05 Nov 2006
Posts: 13
|
Thanks zpat,
zpat,is it could be reason that "websphere MQ clients will enable applications on the windows system to continue to PUT and GET messages from the AIX system , even if the network is down" because ther are . High Availability Cluster Multiprocessing (HACMP) systems. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Nov 05, 2006 6:25 am Post subject: Re: Connecting AIX from windows MQseries Client |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sushilsingh27 wrote: |
Thanks zpat,
zpat,is it could be reason that "websphere MQ clients will enable applications on the windows system to continue to PUT and GET messages from the AIX system , even if the network is down" because ther are . High Availability Cluster Multiprocessing (HACMP) systems. |
There is no such thing as an MQ client working "even if the network is down".
To keep working with a network problem you need a "bindings" or server connection...and be on the same box as the server if you are a client... though even this won't work if there is a problem such that you can't access the "localhost" over the network ...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 06, 2006 12:45 am Post subject: Re: Connecting AIX from windows MQseries Client |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sushilsingh27 wrote: |
Thanks zpat,
zpat,is it could be reason that "websphere MQ clients will enable applications on the windows system to continue to PUT and GET messages from the AIX system , even if the network is down" because ther are . High Availability Cluster Multiprocessing (HACMP) systems. |
To slightly clarify, as you seem to be mixing 2 concepts - if you have an application using a client connection it is possible to define multiple target queue managers & have your application reconnect in the event of trouble; a sort of poor man's HACMP.
If you have HACMP this is irrelevant because the "same" queue manager will be restarted on a failover box & your application will reconnect to it.
If you're using a client and the network is down then nothing will enable you to reconnect!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 06, 2006 2:16 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Client applications don't automatically reconnect - they must be programmed to do so in the event of a 2009.
Having a local queue manager versus having a HACMP clustered remote queue manager, which is more available?
Depending how you look at it, using clients does introduce a network dependency when you use MQI calls.
My answer would be that for "Synchronous" request/reply message designs use the HACMP model as you are dependent on the network anyway.
For true Asynchronous models the ability to always put messages without any dependency outside your own application server may have advantages, so a local queue manager is a good thing in that case.
Some vendor supplied applications don't work well with client connections whereas in-house ones can be more easily made to do so.
I am personally a big fan of (well-written) client connected MQ applications and the cost advantage is another factor. You can always insert a local queue manager later without programming changes. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 06, 2006 3:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
Client applications don't automatically reconnect - they must be programmed to do so in the event of a 2009.
|
I stand clarified
| zpat wrote: |
| I am personally a big fan of (well-written) client connected MQ applications and the cost advantage is another factor. You can always insert a local queue manager later without programming changes. |
I wouldn't disagree with that. You so seldom get well written code though... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 06, 2006 3:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
| I am personally a big fan of (well-written) client connected MQ applications and the cost advantage is another factor. You can always insert a local queue manager later without programming changes. |
One big exception though to the aforementioned:
You will need either a bindings connection or the extended transactional client if you need to do a multiphase commit. The cost factor difference is not relevant in this case as the etc license costs as much as a server license and many people opt for the server license....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
