JMS Bridge between IBM MQ and JBM

[vmeghraj]

Hi, How to create a JMS Bridge between IBM MQ and JBM? Please clarify...

[gaohoward]

please take a look at the bridge example that comes with JBM download.

[vmeghraj]

Hi gaohoward, Thanks for your reply. I followed the examples but there is no sample with IBM MQ. I tried with the below conf without luck.

I get the "java.lang.IllegalArgumentException: Connection factory must be XAConnectionFactory" with the following conf.

Please let me know how to make IVTCF XA enabled.

wmq.jmsra-ds.xml
---------------------

<connection-factories>
 <!-- connection factory definition -->
 <tx-connection-factory>
 <jndi-name>IVTCF</jndi-name>
 <xa-transaction />
 <rar-name>wmq.jmsra.rar</rar-name>
 <connection-definition>javax.jms.ConnectionFactory</connection-definition>
 <config-property name="channel" type="java.lang.String">WAS</config-property>
 <config-property name="queueManager" type="java.lang.String"></config-property>
 <config-property name="transportType" type="java.lang.String">BINDINGS</config-property>
 <security-domain-and-application>JmsXARealm</security-domain-and-application>
 </tx-connection-factory>

[gaohoward]

you probably need to change to XAConnectionFactory

<connection-definition>javax.jms.XAConnectionFactory</connection-definition>

I don't know the WAS adapter configuration, you can refer to their doc for help.

[vmeghraj]

Hi Yong, Thank you for your reply. javax.jms.XAConnectionFactory is not exposed in wmq.jmsra.rar. It always returns the object that implements javax.jms.ConnectionFactory. Do you have any other suggestion on this?

[tiian]

XA support for WebSphere MQ is available when one of the following conditions is met:

1. JMS connects to the queue manager using "binding mode" (this implies you are running in the same host of the queue manager and you are implicitly using JNI to communicate using shared memory like System V IPC)
2. JMS connects to the queue manager using the Extended Transactional Client (ETC): it's provided inside the WebSphere MQ server packaging, not the standard WebSphere MQ client packaging; ETC costs and you need the right IBM license to use it.

This URL http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaw.doc/jm41160_.htm?resultof=%22%58%41%22%20%22%78%61%22%20 explains the matter, but the words "or within an application server environment" are probably related to WebSphere Application Server (it has its own embedded transactional client for WebSphere MQ).

This URL http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzaw.doc/jm40060_.htm?resultof=%22%49%6e%73%74%61%6c%6c%61%74%69%6f%6e%22%20%22%69%6e%73%74%61%6c%22%20%22%57%65%62%53%70%68%65%72%65%22%20%22%77%65%62%73%70%68%65%72%22%20%22%4d%51%22%20%22%6d%71%22%20%22%72%65%73%6f%75%72%63%65%22%20%22%72%65%73%6f%75%72%63%22%20%22%61%64%61%70%74%65%72%22%20%22%61%64%61%70%74%22%20 explains the details.

Additional info: the package for Linux is "MQSeriesTXClient-7.1.0-0.x86_64.rpm" (or something like it) and it should install jar "mqetclient.jar" (and other stuff...).

Regards

Ch.

[dgrove_redhat.com]

Please see attachment.  This is a one file configuration for the messaging bridge - no other configuration is required.