This content has been marked as final.
Show 2 replies
-
1. Re: HornetQ stand-alone server integration with IBM Webshper
timfox Sep 23, 2009 4:49 AM (in response to tulldrift)"tulldrift" wrote:
Hi,
We are using Red Hat SOA Platform 4.3 with IBM WebSphere MQ 6.0 JCA-adapter deployed and access MQ-queues via JNDI(Works very well). We are using JBoss Messaging between SOA-P servers and WMQ to send/recieve messages to C and .Net applications.
We also have a lot of RHEL5 servers running WebSphere MQ, but not SOA-P.
Is it possible to integrate HornetQ stand-alone server with WebSphere MQ?
Can you be more specific by what you mean by "integrate" - this is one of those terms that can mean a million different things depending on context ;)
Could we brigde HornetQ with WMQ via JMS and how?
We provide a JMS bridge that can bridge any two JMS providers. See http://hornetq.sourceforge.net/docs/hornetq-2.0.0.BETA5/user-manual/en/html/appserver-integration.html#jms-bridge
Is it possible to use JCA-adapters in a stand-alone server?
I'm not sure what you mean here. The purpose of a JCA adaptor is to live in a JEE application server and interface with an EIS. (The EIS in this case is the messaging system)
E.g. the HornetQ JCA adapter allows JBoss AS to send and consume messages with HornetQ. The WSMQ JCA adapter allows JBoss AS to send and consume messages via WSMQ.
So you can't use JCA adapters *in* a standalone HornetQ (that would make no sense). But you can use the JCA adapter in JBoss AS to interface with a standalone HornetQ server (is that what you meant?)
Hope that helps :) -
2. Re: HornetQ stand-alone server integration with IBM Webshper
timfox Sep 23, 2009 6:42 AM (in response to tulldrift)One thing we don't support now, but could consider, is to allow HornetQ to directly load JCA adapters. Then we could channel incoming messages to a configurable address, and bridge outgoing messages via an adapter.
This would be pretty cool feature. But this kind of stuff is normally considered the responsibility of the app server, and I want to be careful HornetQ doesn't turn into an appserver.