| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| newbie: Queuemanagers, queues and all that joy. |
« View previous topic :: View next topic » |
| Author |
Message
|
| dunesand |
 Posted: Mon Nov 17, 2003 4:03 am Post subject: newbie: Queuemanagers, queues and all that joy. |
 |
|
Acolyte
Joined: 17 Nov 2003
Posts: 65
Location: Cambridgeshire, UK
|
Hi all,
I've creating a router program that picks up messages from multiple queues (uses multithreading) in a certain XML format, then maps those messages, and routes them out to other queues.
The program is running as a middle tiered server on a multiple tier progject.
I'm used to using MSMQ, where you can simply specify the server, and the queue name, then send (put), or receive (get) messages, but am unsure how this principle relates to Queue managers.
First thougts were that I'd have a queue manager on each server I'm checking, and that my program would connect to multiple queuemanagers, sending and receiving messages on queues existing on those queuemanages, but this doesn't appear to be the way MQ Series works?
I can't create more than one instance of a queue manager for my application using IBM's .Net MQ API or the ActiveX interface, so i gather it's a static member and is not a restriction, but requirement on the use of MQ Series. 
Do I simply get and put messages onto queues on my local queue manager, which are then shared/clustered with other queues on other queuemanagers on remote machines? 
Thanks for your time. 
Dan. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Nov 17, 2003 5:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would recommend that you set up a hub-and-spoke model for your MQSeries network. As you say, have a queue manager on each of your main servers. Set up another server with a queue manager as your 'routing' server (the hub), and then either use cluster queues or remote definitions to have every application put to a queue that is local to the hub. The routing application then puts back to remote or clustered queues for delivery.
I believe you can create multiple queue managers inside a single VB/.NET program, but they have to be in different threads. But again, I wouldn't make your routing program have to know the architecture of your entire queue network - use the queue network to move work to wherever the routing program lives instead.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dunesand |
| Posted: Mon Nov 17, 2003 6:15 am Post subject: |
|
|
Acolyte
Joined: 17 Nov 2003
Posts: 65
Location: Cambridgeshire, UK
|
| JeffLowrey wrote: |
| But again, I wouldn't make your routing program have to know the architecture of your entire queue network - use the queue network to move work to wherever the routing program lives instead. |
Do i do this using the MQ Explorer that comes with Websphere MQ?
Don't suppose you could possibly point me in the direction of some reading material/books to understand how to do this
Thanks again.
Dan. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 17, 2003 6:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, what I mean is this.
Suppose you have three queue managers - A, B, and C - running on your application servers. What I'm suggesting is setting up a fourth queue manager D running on your middle tier server.
You then create a local queue on D from which your router program will read, let's call it ROUTER, so we have D.ROUTER.
You then set up a sender-receiver channel pair between A and D, B and D, and C and D each. Create a remote definition of D.ROUTER on A, B, and C.
Then all your applications will output their messages to the appropriate remote queue - A.ROUTER or whatever. MQSeries will automatically move the message over to D.ROUTER where your router application will pick it up. You can then have remote definitions of the various destination queues for the ROUTER to output - so A.DESTINATION1, B.DESTINATION2, A.DESTINATION3, C.DESTINATION4.
You can create all these objects with the MQExplorer, as you say.
As for documentation - I'd recommend the Quick Beginnings guide for Windows, followed by the Intercommunications Guide, and then the System Administration Guide and the Application Programming Guide. These are all availabe at the 'Documentation' button at the top of your screen. The Quick Beginnings guide is a platform-specific manual, the rest are multiplatform.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dunesand |
| Posted: Mon Nov 17, 2003 6:47 am Post subject: |
|
|
Acolyte
Joined: 17 Nov 2003
Posts: 65
Location: Cambridgeshire, UK
|
Great, thanks for your time!
I'll look into those.
Dan. |
|
| 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
|
|
|
|
