Camel support for Websphere MQ

[Bob G.-2]

Hello,

I work in a Bank and we are currently evaluating ESB/framework (Mule and other lightweight ESB) to have a common integration platform. This market is not very mature and we have a hard time finding a good fit.

We use Websphere MQ and Websphere App Server (I know).

Is there any one using Camel with WebsphereMQ in a production environment or SIBUS?

[jstrachan]

On 8/28/07, Bob G. <[hidden email]> wrote:
> Hello,
>
> I work in a Bank and we are currently evaluating ESB/framework (Mule and
> other lightweight ESB) to have a common integration platform. This market is
> not very mature and we have a hard time finding a good fit.

Just out of interest; what are the most common things you want to be
able to do easily?


> We use Websphere MQ and Websphere App Server (I know).
>
> Is there any one using Camel with WebsphereMQ in a production environment or
> SIBUS?

I know of some folks using Camel and Websphere MQ using the JMS API;
though we don't have a pure Websphere MQ API component just yet;
though the JMS API gives you access to most features of Websphere MQ
folks need.

Would you be happy using the JMS client for Websphere MQ inside Camel?

--
James
-------
http://macstrac.blogspot.com/

[Bob G.-2]

Hello,

Like most Bank and backoffice app, we receive lots of messages from different provider (over custom tcp protocol or via MQ). We need to route, augment, filter etc. these messages.  

Also often need to periodically poll a D.B Table, and put the resultset rows into a queue. We are looking for a good set of integration component. We do need to be full JBI compliant (there is still lots of debate around this kind of spec as you know) .

We did some test with Mule (witch is used in other banks) but I still not sure about it. There is a lot of good product out there but it is hard to see witch one will be the next Tomcat.

We already have Websphere App Server. Websphere ESB is simply not there.
 
Thank you for your time.

[jstrachan]

On 8/29/07, Bob G. <[hidden email]> wrote:
> Hello,
>
> Like most Bank and backoffice app, we receive lots of messages from
> different provider (over custom tcp protocol or via MQ). We need to route,
> augment, filter etc. these messages.

Sounds cool. For custom TCP protocols, we recommend MINA (or you could
just drop in your own Camel component)
http://activemq.apache.org/camel/mina.html

for MQ, we recommend the JMS component - which uses the nice spring 2
stuff under the covers
http://activemq.apache.org/camel/jms.html

though we could do a pure MQ API component too


> Also often need to periodically poll a D.B Table, and put the resultset rows
> into a queue.

from("jpa:com.foo.MyEntityBean").to("activemq:my.queue");

:)

Where com.foo.MyEntityBean is a JPA/hibernate entity bean. Or see
Nicky's new JDBC component...


> We are looking for a good set of integration component. We do
> need to be full JBI compliant (there is still lots of debate around this
> kind of spec as you know) .
>
> We did some test with Mule (witch is used in other banks) but I still not
> sure about it. There is a lot of good product out there but it is hard to
> see witch one will be the next Tomcat.

Cool, thanks for the update. The great thing about Camel is it can be
nicely deployed as a JBI service engine using servicemix-camel so
Camel can work great with JBI components. (Its been designed to work
great with JBI - the Camel API is close to JBI and hopefully will be
even closer to JBI 2) and we hope to have even tighter integration
with ServiceMix 4 and Camel). The combination of Camel as a
routing/transformation engine and ServiceMix as a JBI container is a
great one BTW.

Incidentally do you ever have to monitor multiple systems to check
monitor transaction flows (e.g. checking for straight through
processing, or performing real time reconcilliation between systems?).

If so this might be useful...
http://activemq.apache.org/camel/bam.html

--
James
-------
http://macstrac.blogspot.com/