IBM Websphere MQ Transport

[Rob Tennyson]

Do you know if any work has been put into this? I was just told at
work that MQ is our chosen enterprise messaging solution.

[Dru Sellers]

0 work. :(
That said the ActiveMQ transport should hold a lot of helpful knowledge. I believe both are JMS.

-d

On Mon, Nov 23, 2009 at 1:32 PM, Rob Tennyson <rte...@gmail.com> wrote:

Do you know if any work has been put into this? I was just told at
work that MQ is our chosen enterprise messaging solution.

--

You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To post to this group, send email to masstrans...@googlegroups.com.
To unsubscribe from this group, send email to masstransit-dis...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/masstransit-discuss?hl=.

[Chris Patterson]

Rob,

In what context? 

I mean, if they're talking about enterprise messaging, yes, that makes sense for a large organization. 

But you have different contexts. A desktop or server may not always have connectivity to WebSphere, but would have access to MSMQ. It depends upon what you're trying to do. If you're attempting to buffer commands from a remote piece of equipment (like a handheld or something) before passing into the EMS, MSMQ is a viable and solid approach.

OTOH, if you're interoperating with a bunch of backend middleware built on MQ Series, that's another animal altogether.

My problem with an EMS is that if you don't it on every node, the network again becomes the weakest link and we all know that "The network is unreliable." It's the whole reason we have a persistent command pattern in the first place - because of that network thing that goes up and down.

If you haven't picked up EIP yet (The Hohpe book), definitely pick it up and give it a read through. Don't go in order, just pick a pattern and then walk through the related patterns and let it flow naturally around. The broker vs. bus chapter is good, along with a few of the earlier parts to just get an understanding of messaging concepts.

All of these things will help.

That being said, a WebSphere MQ transport shouldn't be too hard -- TIBCO was easy to build support for based on the Apache.NMS stuff used for ActiveMQ.

CP

On Nov 23, 2009, at 1:32 PM, Rob Tennyson wrote:

Do you know if any work has been put into this? I was just told at
work that MQ is our chosen enterprise messaging solution.

--

You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To post to this group, send email to masstrans...@googlegroups.com.
To unsubscribe from this group, send email to masstransit-dis...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/masstransit-discuss?hl=.

Chris Patterson

chrisfr...@gmail.com