26.5. Running an EJB Performing JMS Operations

All that is necessary to have an Enterprise Bean perform JMS operations is:

jonas start

The Message-Oriented Middleware (the JMS provider implementation) is automatically started (or at least accessed) and the JMS-administered objects that will be used by the Enterprise Beans are automatically created and registered in JNDI.

Then, the EJB can be deployed as usual with:

jonas admin -a XX.jar

26.5.1. Accessing the Message-Oriented Middleware as a Service

If the JOnAS property jonas.services contains the jms service, the JOnAS JMS service will be launched and will eventually try to launch a JMS implementation (for example, the JORAM MOM or the SwiftMQ MOM) through the JMS service in the JOnAS properties file.

For launching the MOM, consider the following possibilities:

26.5.2. Accessing the Message-Oriented Middleware as a J2EE1.4 Adapter

With JOnAS, a JMS server can be accessed through a resource adapter that can be deployed.

To deploy such a resource adapter, put the corresponding archive file (*.rar) in JOnAS's rars/autoload directory, declare it at the end of the jonas.properties file, or deploy it manually through the jonasAdmin tool.

Configuring and deploying such adapters is explained in Section 3.7 Configuring JMS Resource Adapters.