| Author |
Message
|
| cpeele |
 Posted: Wed Apr 04, 2007 11:06 am Post subject: Can I use WebSphere MQ client for Publish/Subscribe |
 |
|
Acolyte
Joined: 04 Apr 2007
Posts: 53
|
Hey guys,
I'm a little confused. We are going to use WebSphere MQ for a publish and subscribe environment.
Can I use WebSphere MQ server for the Publisher and MQ client for the subscriber? Or do they both have to be the server edition because of the need for queue managers?
Thanks,
Chris |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Apr 04, 2007 11:16 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
The Publisher and Subscriber are both applications. They need to connect to a QM, which can be done in either Bindings mode or as a Client.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| cpeele |
| Posted: Wed Apr 04, 2007 11:21 am Post subject: |
|
|
Acolyte
Joined: 04 Apr 2007
Posts: 53
|
Thanks for the reply, I'm still a little confused.
Here's our setup.
3 computers, 1 is going to publish a topic and 2 are going to subscribe to it.
Are you saying that all 3 can be running WebSphere MQ client and they access a central MessageQueue (a 4th computer running WebSphere MQ server) ?
Am I on the right track? I'm not sure what bindings are?
Thanks for the help! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 04, 2007 11:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There's an entire manual on Publish/Subscribe with MQ.
The basics are this:
1) a "Publisher" is a normal application that uses the MQ API to connect to a queue manager, and sends a specific kind of message (a ... Publication... message)
2) A "subscriber" is a normal application that uses the MQ API to connect to a queue manager, and sends a specific kind of message ( a subscription request), and then receives Publications on some queue or another.
3) There is another application, usually not written by the customer, that acts as the Broker - this receives publications and distributes them to subscribers, and receives subscription requests and processes them.
You should spend a bunch more time reading stuff before you start to do even high level architecture for this. Or hire a consultant.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| cpeele |
| Posted: Wed Apr 04, 2007 11:47 am Post subject: |
|
|
Acolyte
Joined: 04 Apr 2007
Posts: 53
|
Thanks for the help. I have been looking through the manuals but they don't specify if a client can be used or what (or at least I haven't found that part yet)
Thanks again,
Chris |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 04, 2007 2:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| cpeele wrote: |
Thanks for the help. I have been looking through the manuals but they don't specify if a client can be used or what (or at least I haven't found that part yet)
Thanks again,
Chris |
Which part of
| jefflowrey wrote: |
| normal application that uses the MQ API |
do you not understand ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
