Yes the instructions for this page are correct. If you get stuck you might also look at http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossASPart4 . I'm in the process of updating the jboss wiki page with some of the Websphere MQ troubleshooting and verification tips. I've used it in 4.0.5 and 4.2.
Yes I know this wiki Pages.
But in this description the pcf-Classes for Java and the WSMQ-Inital Context Factory was used. (Both also recommended to use with the JMS-ADmin Tool). If you are using pcf-Classes the SYSTEM.ADMIN.COMMAND.QUEUE ... Admin-Command are written an the MQ-Command Server ist processing them. I tried to use it without administrative permission to the QM ... doesnt work.The ICtxF is creating dynamic Reply QueueÂ´s aso. ... So we cant use this in our Env, bcause aof Security Policies. But It helped a lot to figure out how to Register MQ in JB! (diffs told a lot)
So we decided to use the wmq.jmsra.rar.
We have got some time left to get it running.
May I will post an Config-Example these days.
May you take a look at the DeveloperWorks Document (link above). If you agree with the idea to use the JCA-Adapter from MQ youÂ´ll may add it to the wiki. ;-)
I'm a little unsure of what your saying. The wiki page that I posted IS about using the JCA adatper. There are 3 other wiki pages, but this one is the one for the JCA adapter. The information found in the jboss wiki page is the same as the ibm link absent the troubleshooting and the Install verification. The same instructions are to create an Admin object and then create your connection factory using the JCA adapter published by IBM. I am planning on rewriting them and when I do, I will add a link to the ibm wiki page from the jboss wiki page.
Sorry i was a little bit confused with all the examples I tried to get working. Absolutely correct. The wiki-Page you talked about decribes the usage of the jca.
There was a Problem with the Examples on the IBM-Page. The XML have some bugs. If you just use them the CF will not be registered correctly. We fixed that and now it works on 4.2.1 also. (I posted a comment regarding this Bugs in the Doc. to IBM)