| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Differences between different MQ products |
« View previous topic :: View next topic » |
| Author |
Message
|
| fqureshi |
 Posted: Wed Jul 28, 2004 6:00 am Post subject: Differences between different MQ products |
 |
|
Newbie
Joined: 26 May 2004
Posts: 6
|
Since I am a new MQ learner, I am just getting confused with all MQ products,
like what are the main differences between:
1) WebSphere MQSeries
2) WebSphere MQSeries Integrator
3) WebSphere MQSeries Integrator Broker
4) WebSphere MQSeries Workflow
I tried to search on a web but could not get the good picture.
If there is any information on the web like article, notes, ... on the
differences of the MQ products, please let me know. Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jul 28, 2004 6:10 am Post subject: Re: Differences between different MQ products |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fqureshi wrote: |
Since I am a new MQ learner, I am just getting confused with all MQ products,
like what are the main differences between:
1) WebSphere MQSeries
2) WebSphere MQSeries Integrator
3) WebSphere MQSeries Integrator Broker
4) WebSphere MQSeries Workflow
I tried to search on a web but could not get the good picture.
If there is any information on the web like article, notes, ... on the
differences of the MQ products, please let me know. Thanks |
If you tried to search on the web, you probably didn't start at www.ibm.com.
WebSphere MQ is a messaging product. It allows different applications to communicate with each other, regardless of what platform and where the applications are located.
WebSphere MQSeries Integrator and WebSphere MQSeries Integrator Broker are extremely slightly different versions of the same product. This product is also known as WebSphere Business Integration Message Broker. Broker uses WebSphere MQ as a transport, and provides tools for transforming (changing) the content of messages, and for routing messages based on content. It also provides a publication/subscription broker engine, that allows many receivers to get copies of the same message, dynamically.
WebSphere MQ Workflow also uses WebSphere MQ as a transport. Workflow is a business process coreographer - it executes and manages processes that go throw many different steps and types of steps. So, I can use Workflow to build a process that takes an order from a Web form, passes it to a processing system, pass it to a Person for approval, and then pass it to a fulfillment system - and Workflow will ensure that everything happens and is managed properly if errors occur.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Jul 28, 2004 6:11 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
WebSphere MQ is the base messaging product. It routes messages around and doesn't really look inside of them to see what they contain.
WebSphere MQ Integrator and WMQI Broker (and WBI Event/Message Broker) are products that look inside of the message and can transform/change the message data and perform routing. They are also used for publish and subscribe. This product sits on top of WMQ.
WMQ WorkFlow is a workflow product that allows you to create processes and then have work assigned to people. This product also sits on top of WMQ. |
|
| Back to top |
|
|
| fqureshi |
| Posted: Wed Jul 28, 2004 6:19 am Post subject: |
|
|
Newbie
Joined: 26 May 2004
Posts: 6
|
| Thanks a lot, it really helps. One more quick question, currently I have Webshere MQSeries (5.1 or 5.2) installed and I am developing a wrapper around MQ API's according to our business requirements. The questions is, can I put and/or receive binary format message instead of as String format, since I am using Java for the development. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jul 28, 2004 6:31 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You can put anything you want in an MQ message. Text, pdfs, jpgs, etc.
If your program can read it into a buffer, you can stick it into an MQMessage (up to 100 MB).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bduncan |
| Posted: Wed Jul 28, 2004 1:53 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
No offense to fqureshi, because I know he's just starting out, but it seems like we have to answer the question "can I put file format FOO in my message instead of a string?" over and over and over again...
Why is it such a difficult concept for people to understand? That MQSeries is concerned with the transmission of data, not the format of that data? Perhaps my knowledge of MQSeries makes me biased, but if I recall, when I was first starting out and told that MQSeries was a messaging system, I immediately assumed that there must be some other application on each end that makes sense of the messages.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Jul 29, 2004 5:46 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
My group also has to answer this question over and over. My answer is always:
| Quote: |
| WMQ takes a pointer to data. It is up to you what is in the data. |
We even try to proactively head off simple questions.
I'd also like to say that MQ 5.1 and 5.2 aren't supported. If you are starting out, you might as well use WMQ 5.3 since it is supported. |
|
| 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
|
|
|
|
