ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Local vs. Remote Queues

Post new topic  Reply to topic
 Local vs. Remote Queues « View previous topic :: View next topic » 
Author Message
skikeowee
PostPosted: Fri Apr 21, 2006 8:51 am    Post subject: Local vs. Remote Queues Reply with quote

Newbie

Joined: 21 Apr 2006
Posts: 2

Is there any documentation on best practices surrounding the use of local vs. remote queues? Some in my company are indicating that we always must have a local queue manager in all situations. I understand that when an application is a publisher of messages that it is beneficial to have a qm as close as possible. But it seems to me that if an application is simply a consumer of asynchronous messages that it would be ok to have a remote queue.
Back to top
View user's profile Send private message
wschutz
PostPosted: Fri Apr 21, 2006 8:57 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

When you say "remote queues", I think you really mean: access the queues via the MQ client versus a server bound application. You can't GET messages from remote queues.

Is that what you are asking?
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
skikeowee
PostPosted: Fri Apr 21, 2006 9:18 am    Post subject: QM Local vs. Remote Reply with quote

Newbie

Joined: 21 Apr 2006
Posts: 2

Yes I'm saying using a MQ client that gets messages from a queue managed by a QM across the network instead of getting it from a QM that is on the same box or in the LAN.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Apr 21, 2006 9:26 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

The only reason an application MUST have a queue manager local is if it is using 2-phase commit - XA coordinated transactions between MQ and a database.

There are even some cases where the Extended Transactional Client will negate that requirement.

There is more logic that should be put into a client, including more errors to handle properly and the requirement to retry the connection in case of certain types of failures. So it's a little more complicated to write.

But requiring a queue manager local on the machine as every application is going to be very expensive license wise. And very expensive to administer.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
wschutz
PostPosted: Fri Apr 21, 2006 9:27 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

and..if you search here for "clients", "pros", "cons" (search for all the terms), you'll get additional opinions....
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Local vs. Remote Queues
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.