Java Reference
In-Depth Information
<config-property name="PhysicalName">
activemq/queue/TicketQueue
</config-property>
</admin-object>
</admin-objects>
</ironjacamar>
As you can see, this file contains the definition of ActiveMQ connection factories along
with the mapping of JMS administration objects, which will be imported by the resource
adapter. The
ironjacamar.xml
file needs to be copied into the
META-INF
folder of
activemq-rar-5.9.0.rar
(you can open the RAR file using the compressed files
manager of your choice, for example, 7-Zip).
Tip
Additional configuration requirements of the resource adapter
Along with the
ironjacamar.xml
file, there is another configuration file that is con-
tained in the
META-INF
folder of your
activemq-rar-5.9.0.rar
file. The
ra.xml
file is the standard JCA configuration file and describes the resource-adapter-re-
lated attribute's type and its deployment properties. We, however, do not need to alter its
contents for our basic sample.
Now that we have completed the configuration, let's deploy the resource adapter
(
activemq-rar-5.9.0.rar
) into our WildFly and check that the JCA factories and
objects have been correctly bound to the application server. After the deployment, you
should see the following similar messages in WildFly's console:
19:52:51,521 INFO [org.jboss.as.connector.deployment] (MSC
service thread 1-5) JBAS010401: Bound JCA AdminObject
[java:jboss/activemq/queue/TicketQueue]
19:52:51,521 INFO [org.jboss.as.connector.deployment] (MSC
service thread 1-5) JBAS010401: Bound JCA ConnectionFactory
[java:jboss/jms/TopicConnectionFactory]
19:52:51,521 INFO [org.jboss.as.connector.deployment] (MSC
service thread 1-8) JBAS010401: Bound JCA ConnectionFactory
[java:jboss/jms/ConnectionFactory]
19:52:51,542 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) JBAS018559: Deployed
