The important elements in the connector header are:

The resourceadapter-instance block contains the settings used to connect to the message broker. They are:

Tip

The work manager handles providing worker threads to a J2EE Connector, typically using a thread pool instead of (in the case of JMS) creating a separate thread to deliver every message. A custom work manager might be used to provide different threading behavior, such as higher-priority threads for a certain JMS configuration. However, this sort of change has not been tested with the current release.

The outbound-resourceadapter block contains the ConnectionFactory settings. In general, not much needs to be customized for the ConnectionFactory other than the name. However, note that you are actually configuring a pool of ConnectionFactory instances that will be shared across the JMS clients. The important elements in this block are:

For a more extensive discussion of the connectionmanager settings, see Section 13.3.2.2.1, “Connection Manager Configuration”.

The adminobject block contains a reference to a Topic or Queue. Any number of adminobject blocks may be included, to configure as many destinations as you like. In many cases, multiple adminobjects may be present for the same underlying Topic or Queue -- this is because the adminobject is essentially the glue between message-destination objects declared in J2EE deployment descriptors, and the actual physical destinations. In the case where several J2EE modules use different names to refer to the same destination, you'll need several adminobject definitions to map all of those to the same destination.

The important settings in this block are:

First you should save the JMS Resource deployment plan to a file like jms-resource-plan.xml (the name can be anything you like). Then you can deploy the resource configuration using a command like this:

java -jar bin/deployer.jar deploy jms-resource-plan.xml \
        repository/activemq/rars/activemq-ra-3.2.1.rar

Note that this example assumes that the server is running, and it can be run from any directory, so long as you point it to the deployer JAR in geronimo/bin and the correct plan file and RAR locations. The two arguments should point to the ActiveMQ RAR file and the JMS deployment plan (the order doesn't matter). If the server is not running, you can use the command distribute instead of deploy, though then you'll still have to start the configuration once the server is running. For more information on deployment commands, see Section 10.4, “The Deploy Tool”.

To deploy application-scoped JMS Resources, you'll include the ActiveMQ RAR as a module in your application EAR. First you should save the JMS Resource deployment plan to a file like jms-resource-plan.xml (the name can be anything you like). Then you need to add that along with the ActiveMQ RAR to your EAR.

For example, the EAR structure might look like this:

jar -tf my-app.ear
  my-web-app.war
  my-ejbs.jar
  activemq-ra-3.2.1.rar
  jms-resource-plan.xml
  META-INF/application.xml
  META-INF/geronimo-application.xml

Notice the ActiveMQ RAR and the JMS Resource deployment plan. You should add a reference to the ActiveMQ RAR to the standard META-INF/application.xml deployment descriptor, and add a reference to the JMS Resource deployment plan to the META-INF/geronimo-application.xml deployment plan. This might be the only entry in the geronimo-application.xml file, so you'll need to create that file if you don't have one already.

The application.xml file for the EAR above would look like this:

META-INF/application.xml

<application 
       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/application_1_4.xsd"
       version="1.4">
    <module>
        <ejb>my-ejbs.jar</ejb>
    </module>
    <module>
        <web>
            <web-uri>my-web-app.war</web-uri>
            <context-root>/my-web-app</context-root>
        </web>
    </module>
    <module>
        <connector>activemq-ra-3.2.1.rar</connector>
    </module>
</application>

Notice the final module entry for the RAR.

The geronimo-application.xml file identifying the JMS Resource deployment plan would look like this:

META-INF/geronimo-application.xml

<application
  xmlns="http://geronimo.apache.org/xml/ns/j2ee/application-1.0"
  configId="MyApplication">
    <module>
        <connector>activemq-ra-3.2.1.rar</connector>
        <alt-dd>jms-resource-plan.xml</alt-dd>
    </module>
</application>

Using the alt-dd element, the deployment plan for the application indicates that the JMS Resource deployment plan for the connector is included as a separate file in the EAR, instead of being packaged into the RAR. The elements here look very similar to the elements in the standard application.xml deployment descriptor, but if we specify an alt-dd there it means an alternate standard J2EE deployment descriptor, whereas specifying the alt-dd here means an alternate Geronimo deployment plan for the connector.

With this configuration, the JMS resources will be started when the application is started.

	Tip
	For more information on the geronimo-application.xml file, see Chapter 15, Enterprise Applications (EARs) [DRAFT (1.0)].

To deploy client-scoped JMS Resources, you'll refer to a common copy of the ActiveMQ RAR. Make sure it appears in geronimo/repository/activemq/rars for the client's Geronimo installation.

Module-scoped JMS Resources are declared in the Geronimo deployment plan for the module that should have access to the resources. The plan will have an additional resource element containing the entire JMS Resource deployment plan. A deployment plan that declared JMS resources using the same configuration shown in Example 7.1, “JMS Resource Group Deployment Plan” would look like this:

META-INF/geronimo-application-client.xml

<application-client xmlns=
  "http://geronimo.apache.org/xml/ns/j2ee/application-client-1.0"
  configId="MyClientConfig"
  clientConfigId="MyClient">
  ...
  <resource>
    <external-rar>
      activemq/activemq-ra/3.2.1/rar
    </external-rar>
    <connector
     xmlns="http://geronimo.apache.org/xml/ns/j2ee/connector-1.0"
     configId="MyJMSResources"
     parentId="geronimo/activemq-broker/1.0/car">
      ...
    </connector>
  </resource>
</application-client>

The important elements here are:

In this case, when the application module is started, the JMS resources will be started as well.