We do this all of the time. We have TIBCO's EMS product as an interface
layer between our HTTPS endpoints and TIBCO BW. Then, the TIBCO BW engine
retrieves a message from EMS, transforms it, and puts it to an MQ queue
via the MQJMS methods.
I am not a developer, but I can say that the connections to the JMS
provider is where all of the class paths are critical, and from that point
on, the BW engine just "uses" whatever JMS connection it needs depending
on what activity is being performed.
However, we are performing a very valuable task in this layer - that of
message transformation - in both directions - not just passing it through.
Thanks,
David Corbett
IBM Certified Solution Designer - WebSphere MQ V7.0
IBM Certified System Administrator - WebSphere MQ V7.0
From: "Meekin, Paul" <paul.meekin-***@public.gmane.org>
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org,
Date: 03/12/2014 08:47 AM
Subject: Re: WebSphere MQSeries (WMQ) integration with Open Source
messaging product
Sent by: MQSeries List <MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>
We nearly had a requirement for an MQ<->other JMS bridge like this but in
the end it wasn?t needed. Nevertheless it?s something I?ve thought about
but never actually tried. My thinking was that you could use the MQ JMS
transport by explicitly using the MQ-specific objects in your program such
as MQConnectionFactory, MQQueue etc and use the other JMS transport in the
same program by either using its vendor-specific classes or if it doesn?t
provide them, by using the standard JMS ones but putting these before the
MQ ones in your classpath etc.
Has anyone done this using 2 different JMS providers in the same program?
MQTT, if my understanding is correct, is both an API and wire standard so
presumably you could simply replace the QMgr with an open source MQTT
broker and carry on with no further changes required.
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf
Of Tim Crossland
Sent: 12 March 2014 13:25
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: WebSphere MQSeries (WMQ) integration with Open Source
messaging product
Absolutely, Dominique. IF their application is JMS, it would be
relatively straight forward to interface with MQ and another messaging
system.
However, the original email didn't specify this information, which is why
I asked the question.
It would also be fairly simple to write a JMS bridge that could take
messages off of MQ queues and put them onto another messaging system.
Trying to this at the transmission protocol level sounds like another
level of complexity (although the MQTT suggestion sounded interesting).
Regards,
Tim Crossland
Senior Consultant
M: +44 (0)7725 208776
T: +44 (0)207 147 9955
Solutions Ltd www.iconsolutions.com
-----Original Message-----
From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf
Of Dominique Courtois
Sent: 12 March 2014 11:54
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: WebSphere MQSeries (WMQ) integration with Open Source
messaging product
Hi Tim,
I am not sure this fully answers the question. JMS is not tied to WMQ or
any messaging system at the API level but the provider layer must be
compatible at the protocol level on both ends.
Regards
Dominique
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and, in the
message body (not the subject), write: SIGNOFF MQSERIES Instructions for
managing your mailing list subscription are provided in the Listserv
General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation.
---------------------------------------------------------------------
To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html