If you don't select one of the pre-configured JMS providers, you'll need to start by selecting the JMS provider RAR. A JMS server vendor may provider their own RAR, or you may find a third-party RAR know to be able to connect to a particular JMS server product. In either case, the RAR should be installed in the Geronimo repository (e.g. saved to a file such as repository/vendor/rars/some-jms-provider-1.0.rar).

Figure 7.3. Console: Select JMS Provider

This screen gives you a list of the RAR files in the repository to select from. Pick the RAR file for your JMS provider, and click Next to advance to the initial configuration screen.

This configuration screen is driven by the configuration parameters for the selected JMS provider RAR, but normally the settings here are used to identify the server to connect to:

Figure 7.4. Console: JMS Resource Group Configuration

The one field that's always present on this screen is:

All the other fields on this screen vary according to the selected JMS provider. Figure 7.4, “Console: JMS Resource Group Configuration” shows the settings for ActiveMQ, which is the most common JMS provider used with Geronimo.

From here, click the Next button to move on to the resource group progress screen.

The next screen display the connection factories and destinations created for the resource group so far. The first time you get here, it just displays some help text as nothing has been created yet:

Figure 7.5. Console: JMS Resource Group Progress (First Time)

At this point, you can use the Add Connection Factory or Add Destination buttons to add resources to the resource group.

After you create each connection factory or destination, you'll return to this screen and see a list of the progress so far:

Figure 7.6. Console: JMS Resource Group Progress

The summary shows the resources added to the group so far. In addition to the buttons to add new resources, you can select Show Plan to see the Geronimo deployment plan for the resource group, or Deploy Now to finalize the resource group and deploy it to the current Geronimo server.

To add a connection factory to the resource group, you must first select the connection factory type. Different JMS providers may support different types of connection factories, but the standard options are:

Figure 7.7. Console: Select JMS Connection Factory Type

To proceed, select the desired JMS Factory Type and click Next. This brings up the configuration screen for the selected connection factory type:

Figure 7.8. Console: Configure JMS Connection Factory

The standard settings here are:

	Note
	Some JMS providers may offer additional configuration parameters for their connection factories. However, ActiveMQ uses only the standard settings described here.

From here, you can click Next to return to the resource group progress screen (see Section 7.2.2.3, “Create Resource Group Progress”).

To add a destination to the resource group, you must first select the destination type. The standard options are:

Figure 7.9. Console: Select JMS Destination Type

To proceed, select the desired JMS Destination Type and click Next. This brings up the configuration screen for the selected destination type:

Figure 7.10. Console: Configure JMS Destination

The one field that's always present on this screen is:

All the other fields on this screen vary according to the selected JMS provider. Figure 7.10, “Console: Configure JMS Destination” shows the additional setting for ActiveMQ, which is the most common JMS provider used with Geronimo.

From here, you can click Next to return to the resource group progress screen (see Section 7.2.2.3, “Create Resource Group Progress”).

To deploy via the command-line deploy tool, save the plan to a file on disk. Then that file can be used along with the listed RAR file to deploy the pool. (Note that the RAR file may be different for different JMS providers, but the RAR file displayed on the screen in Figure 7.11, “Console: JMS Resource Group Deployment Plan” is always the correct one based on the way the resource group was configured.)

For example, if the plan was saved as GERONIMO_HOME/jms-resources.xml, and it was a standard resource group using the RAR file activemq/rars/activemq-ra-3.2.1.rar, then a deploy command might look like this:

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

To deploy the resource group as part of an EAR, save the plan to a file in the EAR, and copy the RAR file into the EAR as well. Again, note that the RAR file may be different for different JMS providers, but the RAR file displayed on the screen in Figure 7.11, “Console: JMS Resource Group Deployment Plan” is always the correct one based on the way the resource group was configured.

The next step is to create or update the J2EE deployment descriptor and Geronimo EAR deployment plan to include the new module. The Geronimo deployment plan will also use an alt-dd element to indicate that the deployment plan for the RAR is actually in the EAR but not in the RAR file itself. For full details on this procedure, see Section 7.3.2.2, “Application-Scoped Deployment”.

To deploy the resource group as part of an application client module, you'll need to copy the plan content into the client deployment plan, and refer to the correct RAR file from the client deployment plan as well. Again, note that the RAR file may be different for different JMS providers, but the RAR file displayed on the screen in Figure 7.11, “Console: JMS Resource Group Deployment Plan” is always the correct one based on the way the resource group was configured.

For full details on this procedure, see Section 7.3.2.3, “Client-Scoped Deployment”.