Developing Applications with JBoss JMS Provider - JBoss AS 7 Development - page 223

subsystem, or (suggested choice) by creating a JCA descriptor of the external re-
source.
JCA descriptors can be created by using an utility contained in JBoss' JCA imple-
mentation named IronJacamar ( http://www.jboss.org/ironjacamar ). Within IronJaca-
mar 1.1 or later distributions (accessible at http://www.jboss.org/ironjacamar/down-
loads ) , you can find a resource adapter information tool ( rar-info.sh ) that can be
used to create the resource adapter deployment descriptor by generating a report
file containing all the necessary information.
The rar-info.sh tool can be found in the doc/as folder of your IronJacamar dis-
tribution. So let's move to this folder:
$ cd doc/as
And now issue the following command, which assumes that you have saved your
resource adapter in the /usr/doc folder:
rar-info.sh /usr/doc/activemq-rar-5.7.0.rar
Tip
Troubleshooting rar-info shell
The rar-info command shell includes a set of libraries, which are used to
execute the main utility class. In order to inspect the JMS adapter however,
you need to manually edit the shell file and add jboss-jms-
api_1.1_spec-1.0.0.Final.jar to the classpath. This JAR is contained in
the main folder under JBOSS_HOME/modules/javax/jms/api/ .
This will generate a file called activemq-rar-5.7.0.txt , which can be used
to construct the JBoss' JCA configuration file that needs to be named ironjaca-
mar.xml . The file ironjacamar.xml is pretty verbose so we will just include the
core section of it with the changes required to map JMS admin objects (you can
download the full ironjacamar.xml file along with the sources of this topic):