IBM Websphere v6 and JBoss 4x MQ Connectivity - Please Help

[Azrael Noor]

On Server Side, i have IBM Websphere v6...

On Client Side, i have JBoss 4.0.3SP1....


I want to use MQ technology. I Need Client Side Settings.


1) I read that it requires "wmq.jmsra.rar" <--- Not able to find this rar file on searches but found 2 files(com.ibm.mq.jar and com.ibm.mqjms.jar) of this rar on IBM Server's folder i.e \IBM\WebSphere\AppServer\lib\WMQ\java\lib. Should i make .rar of these two files


2) I Found two files ""messaging-service.xml"" and "wsmq-ds.xml". when i put those in my Jboss jms folder "\server\default\deploy\jms". I get following error on server. "No ClassLoaders found for: org.jboss.jms.server.ServerPeer; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.ServerPeer)".

where could i get this ServerPeer .jar file?

Kindly Guide me how to make connection further i stuck on the way.

Thank you

Files are :
wsmq-ds.xml
messaging-service.xml

[Azrael Noor]

Our Green Horns are busy in eating grass

I am moving forward of my own, what i do is, i have downloaded Websphere MQ V7

and i copied following wmq.jmsra.rar (attached below) from it's folder: \IBM\WebSphere MQ\java\lib\jca

I put it in jboss deploy folder which gives following error

___________________________________________________

Problem starting service jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

com.ibm.mq.connector.DetailedResourceAdapterInternalException: MQJCA1008: An incorrect version of the WebSphere MQ classes for JMS was found. 
Deployment failed., error code: MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. 
This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. 
The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.

        at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:129)

        at com.ibm.mq.connector.services.JCAExceptionBuilder.buildException(JCAExceptionBuilder.java:86)

        at com.ibm.mq.connector.ResourceAdapterImpl.verifyJMSClasses(ResourceAdapterImpl.java:879)

        at com.ibm.mq.connector.ResourceAdapterImpl.start(ResourceAdapterImpl.java:302)

        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:107)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)

        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:110)

        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)

        at $Proxy0.start(Unknown Source)

        at org.jboss.system.ServiceController.start(ServiceController.java:428)

        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy35.start(Unknown Source)

        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:330)

        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:112)

        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)

        at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy9.deploy(Unknown Source)

        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)

        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:203)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:182)

15:38:04,137 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

 

--- Incompletely deployed packages ---

org.jboss.deployment.DeploymentInfo@885fda34 { url=file:/C:/jboss-4.0.3SP1/server/default/deploy/jms/jms-ds.xml }

  deployer: org.jboss.deployment.XSLSubDeployer@39d325

  status: null

  state: FAILED

  watch: file:/C:/jboss-4.0.3SP1/server/default/deploy/jms/jms-ds.xml

  altDD: null

  lastDeployed: 1306836080152

  lastModified: 1306836080137

  mbeans:

 

--- MBeans waiting for other MBeans ---

ObjectName: jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

  State: FAILED

  Reason: com.ibm.mq.connector.DetailedResourceAdapterInternalException: 
MQJCA1008: An incorrect version of the WebSphere MQ classes for JMS was found. Deployment failed.,
 error code: MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. 
This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. 
The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.

 

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

ObjectName: jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

  State: FAILED

  Reason: com.ibm.mq.connector.DetailedResourceAdapterInternalException: 
MQJCA1008: An incorrect version of the WebSphere MQ classes for JMS was found. Deployment failed.,
 error code: MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. 
This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. 
The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.

_____________________________________________________

So Next work i am doing now is

Downloading WebSphere MQ V6.0.2.

Let's See how it will Go.

Will Update, Boss Gonna Kick ma


wmq.jmsra.rar (V7) Download

[Jaikiran Pai]

To be honest, I have no clue what you are trying. So can't really help. Can you explain what you are trying to achieve?

[T.Rob Wyatt]

Is this a toy application or just for your own study? Because if it is going to be a real application that your business depends on then you should be aware that support from IBM requires that you actually install the full WMQ client. In addition to the WMQ Jar files, this installs utilities such as the ability to tun traces, display the version you have installed, the install verification test utilities and apply maintenance. Frankly, even if it is a toy application one wonders why anyone would attempt to get something working by guesswork rather than just run the vendor-supplied install. Also, if you run the IBM installer instead of grabbing the jar files from the V6 server you can use the V7 client. If you build the app on V7 client and run against V6 server it is compatible but it saves you from having to upgrade the client later (WMQ V6 is end of life as of Sept 2012).

Download the V7 client at http://bit.ly/SupportPacMQC7
Download the V6 client at http://bit.ly/SupportPacMQC6

WMQ V7 Using Java Manual
WMQ V6 Using Java Manual

[Azrael Noor]

Jaikiran Pai and Rob Woyatt

Server is sending JMS messages through WebsphereMQ and
client Jboss v6.0.2 is receiving the messages.

I don't know about server. what i know is the queue manager name, queuename, channel name etc.

I want to set my jboss server to receive messages from there for that what is am doing is above.

and ya it is not toy application.

What settings i have to do at jboss v4.0.3SP1 to recieve message from server(contains websphere mq to send messages)

i hope understood little bit.

Take Care and rob thank you for replying, already seen those links, you mean to say i should call IBM for settings of jboss??


Keep on updating what am i doing further. Thank you

[Azrael Noor]

So here i proceed further

After Downloading WebSphere MQ V6.0.2 i got a rar file wmq.jmsra.rar which contains only four jar files

i.e dhbcore.jar, com.ibm.mqjms.jar, com.ibm.mq.jar and mqconnector.jar and there is ra.xml in meta-inf folder inside it. I have attached that file below.

I Copied that .rar file into my deploy/jms folder and i got following exception:

____________________

[ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

java.lang.NoSuchFieldError: TITLES

        at com.ibm.mq.connector.MQJCAJMSLevel.printMQVERInfo(ResourceAdapterImpl.java:900)

        at com.ibm.mq.connector.ResourceAdapterImpl.initializeTrace(ResourceAdapterImpl.java:634)

        at com.ibm.mq.connector.ResourceAdapterImpl.start(ResourceAdapterImpl.java:235)

        at org.jboss.resource.deployment.RARDeployment.startService(RARDeployment.java:107)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)

        at org.jboss.system.ServiceDynamicMBeanSupport.invoke(ServiceDynamicMBeanSupport.java:110)

        at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)

        at $Proxy0.start(Unknown Source)

        at org.jboss.system.ServiceController.start(ServiceController.java:428)

        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy35.start(Unknown Source)

        at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:330)

        at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:112)

        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)

        at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy9.deploy(Unknown Source)

        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)

        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:192)

        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)

        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)

        at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:943)

        at $Proxy0.start(Unknown Source)

        at org.jboss.system.ServiceController.start(ServiceController.java:428)

        at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy4.start(Unknown Source)

        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)

        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)

        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)

        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)

        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)

        at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)

        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)

        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)

        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)

        at $Proxy5.deploy(Unknown Source)

        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)

        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)

        at org.jboss.Main.boot(Main.java:187)

        at org.jboss.Main$1.run(Main.java:438)

        at java.lang.Thread.run(Thread.java:662)

ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---

ObjectName: jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

  State: FAILED

  Reason: java.lang.NoSuchFieldError: TITLES

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---

ObjectName: jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'

  State: FAILED

  Reason: java.lang.NoSuchFieldError: TITLES

____________________

Don't know why this error occur, i have to check because i have chose correct version of rar file. Let's hope for the best.

Will update you guys soon.

If you have any idea then please tell.


Following attachment is of Websphere 6.0.2.10 Fix

wmq.jmsra.rar (V6)

[Jaikiran Pai]

If you are going to just randomly use some jars from here and there then it isn't ever going to work. Have you read Rob's reply in this thread?

[Azrael Noor]

Jaikiran Pai

Actually i was trying to follow this link:
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_ritchie/0710_ritchie.html

The Only link giving description of this connection. It has given the version, i have downloaded same version and copied required jar and rar to my jboss deployment. It is not picking the rar and giving that error in my previous posts. I am just using jars as mentioned there.

I read Rob, but i have nothing to take with server side, i mean i do not want MQ on my end at all. just need jars and rars to connect to server mq.
I am not building anything on Websphere MQ. i am just connectiong to a server having Websphere MQ installed, from my JBOSS.

Sir, What track you want me to follow? am i moving somewhere wrong?

Regards....

[T.Rob Wyatt]

Azrael Noor wrote:Jaikiran Pai and Rob Wyatt
...
What settings i have to do at jboss v4.0.3SP1 to recieve message from server(contains websphere mq to send messages)
...
you mean to say i should call IBM for settings of jboss??

I don't know the JBoss settings, hopefully someone else here will help with that. I'm just suggesting to start with a correctly installed version of WMQ client. My experience from working many PMRs for many clients is that a ticket gets opened with something like "my WMQ JMS client isn't working." Then when we start digging in and the IBM tech says "well take a trace" or "run this diagnostic command" the reply comes back that these are not available because instead of a full install, someone copied the jar files over and tried to cobble it together themselves. At that point the IBM support person says "well if you want support you need to install the full client so we can run these diagnostics." As soon as the client is installed, the environment variables set as per the docs and the Initial Verification Test programs successfully, run, the application problem magically disappears. Of course, this does not fix the problem in every case but in about half the cases I've personally worked simply installing the WMQ client as per the vendor specs resolves the problem. I *always* start there.

And, no, I'm not suggesting calling IBM for JBoss settings. But if you have the full client install you can use the verification test programs to connect to the QMgr and verify your install and if those fail, you can and should call IBM for support. Once the IVT programs work, then and only then should you move on to getting JBoss running with WMQ except now it will be with a known working install instead of guesswork.

For what it's worth. I realize the culture of the JMS crowd is based on "just give me the jar files" and resistant to the notion of using vendor-provided install procedures such as these. Especially those that require root. However, since the WMQ client install includes a lot of functionality not delivered in the jar files, and since the full install is the only supported configuration, I haven't given up on trying to convince you guys to try it.

[Azrael Noor]

However, since the WMQ client install includes a lot of functionality not delivered in the jar files, and since the full install is the only supported configuration, I haven't given up on trying to convince you guys to try it.

This probably be the reason it's .rar file is throwing this exception:

[RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/wmq.jmsra.rar
[ServiceController] Problem starting service jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
java.lang.NoSuchFieldError: TITLES

So Sir you mean
first, i should purchase IBM Websphere MQ or freely download it from some torrent,
have a full install it on system
and then copy require rar's and use the IVT or Diagnostic Trace to solve problems?
am i getting right

Thank you for telling that.

[T.Rob Wyatt]

Azrael Noor wrote:

However, since the WMQ client install includes a lot of functionality not delivered in the jar files, and since the full install is the only supported configuration, I haven't given up on trying to convince you guys to try it.

So Sir you mean
first, i should purchase IBM Websphere MQ or freely download it from some torrent,
have a full install it on system
and then copy require rar's and use the IVT or Diagnostic Trace to solve problems?
am i getting right

No, I'm saying that you can download the FREE WMQ client from the links provided and install that on your JBoss server. Those links again are:

FREE WMQ V7 client: http://bit.ly/SupportPacMQC7
FREE WMQ V6 client: http://bit.ly/SupportPacMQC6

Note that the Ben Ritchie article that was linked provides instructions on how to configure JBoss to talk to a LOCALLY INSTALLED QMgr using XA. Since you are not connecting to a local WMQ server using shared memory connection as described in the article but instead are using a remote network connection, the article does not directly apply to your configuration. You won't be able to use bindings mode connections and therefore will not get XA functionality.

[T.Rob Wyatt]

T.Rob Wyatt wrote:Note that the Ben Ritchie article that was linked provides instructions on how to configure JBoss to talk to a LOCALLY INSTALLED QMgr using XA. Since you are not connecting to a local WMQ server using shared memory connection as described in the article but instead are using a remote network connection, the article does not directly apply to your configuration. You won't be able to use bindings mode connections and therefore will not get XA functionality.

Sorry, I needed to read Ben's article further. He *does* show you how to configure the Extended Transactional Client but the instructions assume you have a fully licensed WMQ Server installed locally. This is probably where the disconnect lies here. In the article Ben starts by assuming that WMQ Server is installed and then has you copy mqetclient.jar (the extended transactional client) to the server lib directory. What isn't mentioned in the article is that use of mqetclient.jar (the Extended Transactional Client) incurs a full WMQ license obligation on the client host server in addition to any license on the WMQ QMgr server. Because the article assumes a fully licensed WMQ install has been performed, it is correct to simply copy this jar file from the install directory to install_path/server/default/lib on the same host. Also because the article starts with a WMQ Server already locally installed, Ben doesn't walk you through obtaining the WMQ client and installing it.

Sooooo...to follow the article and stay in full compliance you'd want a licensed WMQ server install on the JBoss host and then just use the XA client components of it. If all you want is client and don't need XA then download the installs I've linked above.

[Azrael Noor]

Thank you for sharing information.

No I need no client of IBM. Client is JBoss on my side and simply i copied .rar and.jar files available in library of Websphere MQ.
Well, i will give you update and seek your blessings in form of solutions shortly.
will keep on updating the thread the process i am going on to install the Client listening to Websphere MQ.

[Azrael Noor]

So Guys Here are settings with which i able to Receive Message from Server installed with Websphere MQ, it take more then a week to understand such easy settings..........hufffffffffffffffffffff:

In MDB, in EJB.JAR file the settings are

<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
  <enterprise-beans>
        <message-driven>
            <display-name>NewMessageBeanMDB</display-name>
            <ejb-name>NewMessageBean</ejb-name>
            <ejb-class>Beans.NewMessageBean</ejb-class>
            <messaging-type>javax.jms.MessageListener</messaging-type>
            <transaction-type>Container</transaction-type>            
            <activation-config>
                <activation-config-property>
                    <activation-config-property-name>destination</activation-config-property-name>
                    <activation-config-property-value>LONOR_1/1</activation-config-property-value>
                </activation-config-property>
                <activation-config-property>
                    <activation-config-property-name>destinationType</activation-config-property-name>
                    <activation-config-property-value>javax.jms.Topic</activation-config-property-value>
                </activation-config-property>
				<activation-config-property>
                    <activation-config-property-name>useJNDI</activation-config-property-name>
                    <activation-config-property-value>false</activation-config-property-value>
                </activation-config-property>                
                <activation-config-property>
                    <activation-config-property-name>hostName</activation-config-property-name>
                    <activation-config-property-value>1.1.1.1</activation-config-property-value>
                </activation-config-property>                                
				<activation-config-property>
                    <activation-config-property-name>port</activation-config-property-name>
                    <activation-config-property-value>1415</activation-config-property-value>
                </activation-config-property>                                
				<activation-config-property>
                    <activation-config-property-name>channel</activation-config-property-name>
                    <activation-config-property-value>SVRCONN.Sgaven</activation-config-property-value>
                </activation-config-property>            
                <activation-config-property>
                    <activation-config-property-name>queueManager</activation-config-property-name>
                    <activation-config-property-value>QM1</activation-config-property-value>
                </activation-config-property>                                                
				                                     
          </activation-config> 
      </message-driven>
        </enterprise-beans>
    <assembly-descriptor>
        <container-transaction>
            <method>
                <ejb-name>NewMessageBean</ejb-name>
                <method-name>*</method-name>
            </method>
            <trans-attribute>Required</trans-attribute>
        </container-transaction>
        <message-destination>
            <display-name>Destination for NewMessageBeanMDB</display-name>
            <message-destination-name>LONOR_1/1</message-destination-name>
        </message-destination>
        </assembly-descriptor>
    </ejb-jar>

In JBOSS.XML, we have following :

<?xml version="1.0" encoding="UTF-8"?>
<jboss>
  <enterprise-beans>
  <message-driven>
      <ejb-name>NewMessageBean</ejb-name>
	  <destination-jndi-name>topic/LONOR_1/1</destination-jndi-name>
	  <resource-adapter-name>wmq.jmsra.rar</resource-adapter-name>
	 <configuration-name>Standard Message Inflow Driven Bean</configuration-name>
</message-driven>
</enterprise-beans>	
	
</jboss>

In WMQ-ds.xml, which should be in deploy/jms folder, which is not required []:

<?xml version="1.0" encoding="UTF-8"?>

<connection-factories>
       <mbean code="org.jboss.resource.deployment.AdminObject"
		name="jca.wmq:name=IVS">
    <attribute name="JNDIName">cromaENTERPRISEQ    </attribute>
	
    <!-- this MBean depends on the WebSphere MQ resource  adapter -->
    <depends optional-attribute-name="RARName">
	jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'
    </depends>
	
    <attribute name="Type">javax.jms.Queue</attribute>

    <attribute name="Properties">
    baseQueueManagerName= QM1
    baseQueueName= CromaENTERPRISEQ
    </attribute>
  </mbean>

    <tx-connection-factory>
        <jndi-name>IVTCF</jndi-name> 
        <xa-transaction/>
        <rar-name>wmq.jmsra.rar</rar-name>
        <use-java-context>false</use-java-context>
        <connection-definition>javax.jms.ConnectionFactory</connection-definition>
        <jmx-invoker-name>jboss:service=invoker,type=jrmp</jmx-invoker-name>
        <min-pool-size>1</min-pool-size>
        <max-pool-size>10</max-pool-size>
        <blocking-timeout-millis>30000</blocking-timeout-millis>
        <idle-timeout-minutes>30</idle-timeout-minutes>
        <prefill>false</prefill>
        <background-validation>false</background-validation>
        <background-validation-millis>0</background-validation-millis>
        <validate-on-match>true</validate-on-match>
        <statistics-formatter>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter</statistics-formatter>
        <isSameRM-override-value>false</isSameRM-override-value>
        <allocation-retry>0</allocation-retry>
        <allocation-retry-wait-millis>5000</allocation-retry-wait-millis>
        <config-property name="channel" type="java.lang.String">SVRCONN.Sgaven</config-property>
        <config-property name="hostName" type="java.lang.String">1.1.1.1</config-property>
        <config-property name="port" type="java.lang.String">1415</config-property>
        <config-property name="queueManager" type="java.lang.String">QM1</config-property>
        <config-property type="java.lang.String" name="transportType">CLIENT</config-property>
        <security-domain-and-application>JmsXARealm</security-domain-and-application>
        <xa-resource-timeout>0</xa-resource-timeout>
    </tx-connection-factory>
</connection-factories>

Following is file you have to put in deploy folder:
wmq.jmsra.rar (V6.0.1 to .11)

Following file need to put in default/lib folder