| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What's different the local queue compare with remote queue? |
« View previous topic :: View next topic » |
| Author |
Message
|
| jackysu |
 Posted: Wed Dec 19, 2001 6:39 pm Post subject: |
 |
|
Novice
Joined: 10 Dec 2001
Posts: 13
|
Dear Support,
As I know queue is like the data pool and any application could put or get data from that.But what's different local and remote queue? and what kind the environment will be use local queue in both machine exchange data and what kind the environment could be use remote queue(location in sender side) in both machine?
Thanks
Regards!
Jacky Su |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Dec 19, 2001 6:58 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Jacky,
A quote taken from the manual:
Queues can exist either in your local system, in which case they are called local queues, or at another queue manager, in which case they are called remote queues.
End quote.
When your application connects to a queue manager, you can then do GETs from and PUTs to a local queue.
On this queue manager you can also have a 'pointer' to a queue on another queue manager. This is a Remote queue definition. You can only PUT to this. MQSeries then takes care (provided everything is configured correctly) of the transmission of the message from your local queue manager to the remote queuemanager, and then on to the romote queue.
Cheers,
_________________
Eddie Atherton
IBM Certified Specialist - MQSeries
IBM Certified Specialist - MQSeries Integrator
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jackysu |
| Posted: Wed Dec 19, 2001 10:15 pm Post subject: |
|
|
Novice
Joined: 10 Dec 2001
Posts: 13
|
Dear Support,
Thanks your explain! I think I can understand your mean.
But incase,each machine just only a local queue and without a remote queue define there whether can exchange data via channel to each machine(or queue manager)? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Dec 20, 2001 7:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Let's say u have Queue Manager 1 (QM1) with a local queue (QA). There is also a second Queue Manager called QM2, with a local queue of its own called QB. There are channels set up between both. QM1 has a XMIT queue called QM2, which is serviced by the channel from QM1 to QM2, and QM2 has a XMIT queue called QM1, which is serviced by a channel from QM2 to QM1.
If your app is on QM1, and wants to put a message to QB on QM2, you do not need a remote queue definition on QM1 (although you could have one). Without a remote def, simply connect to QM1, specify the MQOD-OBJECTNAME as QB and the MQOD-OBJECTQMGRNAME
as QM2 on the open and put your message. QM1 sees that there is a XMIT queue with the same name as your MQOD-OBJECTQMGRNAME, and puts the message there, thus sending it to QB on QM2.
Or, have your app client connect directly to QM2.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
