| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Remote Get |
« View previous topic :: View next topic » |
| Author |
Message
|
| visionofindia |
 Posted: Mon Feb 23, 2004 7:54 am Post subject: Remote Get |
 |
|
Newbie
Joined: 20 Nov 2003
Posts: 9
Location: Mysore, India
|
Have attended many trainings and participated in many projects on WMQ.
But the question that I have not found an answer to is WHY is a REMOTE GET not a feature of WMQ ??
_________________
Later,
Sughosh |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon Feb 23, 2004 4:08 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What do you mean by REMOTE GET??
If you are talking about getting a message from a Remote queue then
I believe the answer would be:
Queue manager doesn't "store" a message on a remote queue, so there is nothing to GET.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Missam |
| Posted: Tue Feb 24, 2004 3:16 pm Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
| Because The transmission queue are intended to put messages to remote queue.not to get messages from remote queue |
|
| Back to top |
|
|
| vijiraghav |
| Posted: Wed Feb 25, 2004 3:07 am Post subject: Remote Get |
|
|
Novice
Joined: 11 Nov 2003
Posts: 18
|
Remote queue is called so because it is available on the remote queue manager and it is, in fact, a local queue for that queue manager. Its actual name is mentioned (RQNAME) in the remote queue definition (defined in the local q.m) along with the name of the transmission queue and remote queue manager name . Please remember it is only a definition not the queue iteself. When the application wants to put the message to the queue available on the remote queue manager, it simply refers to it in the form of definition name available in the local q.m which resolves to the actual queue name, puts in the transmission queue along with the necessary extra header information. Ultimately the message has to reach only the local queue from where the applications can retrieve (MQGET) it.
Hence please note that the so called remote queue is referred only by the definition and so there is question of storing message into it. Hence the question of remote GET does not arise.
Vijiraghav |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed Feb 25, 2004 6:00 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
I think its a design question and only someone from IBM can answer this. In my early days i too had this doubt, but never got a definitive answer and never really bothered because we use the features that are provided rather than digging for those that arent there.
You can usually submit a request to IBM if you want any changes to the product, but you need to have a valid reason for the change request. I never got one, for this particular case.
I think most of the posts here pointed to REMOTE queue and the storage of messages where the actual question was, whether a Remtoe GET can be performed.
If there was such an option, then you wouldn't really need any storage requirements for it. Since you are doing a get, the get would consume the message. Interesting question would be what if you were trying to do a browse, which again would be a bit out of the way, since puts should be compared with gets and not browses. :).
I think looking at the design it is very much possible, since your get probably would open the remote queue to do a get and the MCA would get the message for you. Of course, all this with design changes.
But again, what would you achieve out of it. And what would force such a design change for IBM is the big question.
Cheers
Kumar |
|
| Back to top |
|
|
| bduncan |
| Posted: Thu Feb 26, 2004 1:14 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
I'll submit what I think is the answer:
You don't NEED remote get.
I bet you that any system/workflow you come up with I can implement in MQSeries without saying "I can't do this without a remote get".
If an application running on machine A needs to process a message that is sitting on a queue on machine B, it begs the question why the message is on machine B in the first place.
Even *if* you can come up with a good reason for it, the workaround is simple. Just have an application on machine B send the message to machine A if it needs to be processed on A. This will be no less efficient than a remote get anyway, because there is network overhead involved in either case.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
