This is only a starting point, but you can find some informations there: http://incubator.apache.org/servicemix/creating-a-protocol-bridge-30.html This explains how to build an HTTP / JMS bridge, but you can surely make JMS / JMS bridges. If you only plan for JMS / JMS, you could also take a look at http://activemq.apache.org/jms-to-jms-bridge.html
On 4/11/07, bradburyn <[EMAIL PROTECTED]> wrote:
Hi, I have the task of going through a political nightmare where we have one department using tibco esb and another using websphere integrator with messaging. the problem i have is that while each can perform expected integration points using let's say jms etc, i need a position that allows my enterprise architecture group free reign to do both producer/consumer as well as point to point with workflow and bpm and dynamic business rules to boot. Basically i want a generic "enterprise wide" way to access generically across a broad range of dept. applications to push and pull data using a data wide approach. this means i need a more "open" and standard esb delivery platform that is agonistic to vendor lockins, while providing all the interoperability and integration of protocols and standards. I think my gut feeling is servicemix via the jbi api interface and the various key protocols and messaging etc etc etc can perform this "glue" without the who's who in vendor platforms. If any one has come across this bridge before I would like to know how to present to a team the "glue". Many thanks. -- View this message in context: http://www.nabble.com/tibco-esb-verse-servicemix-tf3557734s12049.html#a9934439 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
