In order to help you we need more info regarding your issue. Can you share any log or the actual exception stack trace?
The best approach is to implement a JCA Resource Adapter with the required business interface to replace the CommonJ code. The JCA Resource Adapter specification can be found here: JSR 322: JavaTM EE Connector Architecture 1.6 . The IronJacamar tool can help you get started writing a Resource Adapter. IronJacamar provides a WorkManager Resource Adapter in its test suite. Information about the WorkManager Interface can be found here:
Current WAS 8 application with workmanagers.
Deploying to JBOSS eap 6.4
the error is: javax.naming.NameNotFoundException: workmanagerName. service jboss.naming.context
I used the admin console to add the JCA bootstrap context and a custom workmanager with the correct name but I still get the error. I have the jndi name as the name of the Workmanager.
only working with JBOSS about 2 days. The Datasource and MQ setups work fine but this seems is giving me issues but it should be rather straight forward according to the docs I see.
So, do I need to download a *.rar file for the resource adaptor and deploy to JBOSS to get this to work, like one would do for ActiveMQ for instance?
DEPLOY THE WEBSPHERE MQ RESOURCE ADAPTER:https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/Deploy_the_WebSphere_MQ_Resource_Adapter.html
Integration of JBoss AS 7 with ActiveMQ: Integration of JBoss AS 7 with ActiveMQ
That was great. Active MQ setup is pretty straight forward.
If these links are useful then mark it as helpful/ like it or choose it as correct answer.