0. Introduction

Versions of ActiveMQ that has been reported to work:

• ActiveMQ 4.1.0-incubator

Before you proceed, don't forget to copy the JMS Driver's jar into $CATALINA_HOME/lib. In that case it is apache-activemq-4.1.0-incubator.jar.

1. ActiveMQ configuration

ActiveMQ doesn't need any particular configuration. It's possible to get it work from a binary distribution.

2. server.xml configuration

Configure the JNDI DataSource in Tomcat by adding a declaration for your resource to $CATALINA_HOME/conf/server.xml.

Add this in between the </Context> tag of the examples context and the </Host> tag closing the localhost definition. If there is no such tag, you can add one as illustrated in the Context and Host configuration references, and repeated below for your convenience.

You can find more connection parameters and their descriptions on this page. <Context path="/JMSTest" docBase="JMSTest" debug="5" reloadable="true" crossContext="true"> <!-- factory: The class who's going to create the objects we need. --> <!-- brokerURL: The broker URL to set. --> <!-- brokerName: The name of the broker to use if creating an embedded broker. --> <!-- userName and password: ActiveMQ username and password for JMS connections. --> <!-- useEmbeddedBroker: Allows embedded brokers to be associated with a connection factory. --> <!-- clientID: String identification to use when connection to a topic. --> <!-- physicalName: The name for the JMS destination. --> <Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.ActiveMQConnectionFactory" description="JMS Connection Factory" factory="org.apache.activemq.jndi.JNDIReferenceFactory" brokerURL="vm://localhost" brokerName="LocalActiveMQBroker" userName="activemq" password="activemq" useEmbeddedBroker="false" clientID="TomcatClientID" /> <Resource name="jms/myQueue" auth="Container" type="org.apache.activemq.command.ActiveMQQueue" description="JMS Queue" factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="TEST.FOO" /> <Resource name="jms/myTopic" auth="Container" type="org.apache.activemq.command.ActiveMQTopic" description="JMS Topic" factory="org.apache.activemq.jndi.JNDIReferenceFactory" physicalName="TEST.BAR"/> </Context>

3. web.xml configuration

Now create a WEB-INF/web.xml for this test application. <web-app 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/web-app_2_4.xsd" version="2.4"> <description>ActiveMQ Test App</description> <servlet> <servlet-name>Test</servlet-name> <servlet-class>test</servlet-class> </servlet> <servlet-mapping> <servlet-name>Test</servlet-name> <url-pattern>/test.do</url-pattern> </servlet-mapping> <message-destination-ref> <message-destination-ref-name>jms/myQueue</message-destination-ref-name> <message-destination-type>javax.jms.Queue</message-destination-type> <message-destination-usage>ConsumesProduces</message-destination-usage> <message-destination-link>MyQueue</message-destination-link> </message-destination-ref> <message-destination> <message-destination-name>MyQueue</message-destination-name> </message-destination> </web-app>

4. Test code

Now create a simple WEB-INF/classes/test.java class for use later. import java.io.*; import java.text.*; import java.util.*; import javax.servlet.*; import javax.servlet.http.*; import javax.jms.*; import javax.naming.InitialContext; public class test extends HttpServlet { public void doGet(HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException { response.setContentType("text/html"); PrintWriter out = response.getWriter(); String body = ""; try { InitialContext init = new InitialContext(); javax.jms.Queue destination = (javax.jms.Queue) init.lookup("java:comp/env/jms/myQueue"); ConnectionFactory connectionFactory = (ConnectionFactory) init.lookup("java:comp/env/jms/ConnectionFactory"); Connection connection = connectionFactory.createConnection(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); TextMessage message = session.createTextMessage(); message.setText("My text message was send and received"); connection.start(); MessageProducer producer = session.createProducer(destination); producer.setDeliveryMode(DeliveryMode.PERSISTENT); producer.send(message); message = null; MessageConsumer consumer = session.createConsumer(destination); message = (TextMessage) consumer.receive(1000); if( message!=null ) { body = message.getText(); } producer.close(); consumer.close(); session.close(); connection.close(); } catch (Exception e) { System.out.println(e.toString()); } out.println("<html>"); out.println("<head>"); String title = "JMS Test"; out.println("<title>" + title + "</title>"); out.println("</head>"); out.println("<body bgcolor=\"white\">"); out.println("<h1>" + title + "</h1>"); out.println("<p>The message contains \"" + body + "\".</p>"); out.println("</body>"); out.println("</html>"); } }

Finally deploy your web app into $CATALINA_HOME/webapps either as a warfile called JMSTest.war or into a sub-directory called JMSTest

Once deployed, point a browser at http://localhost:8080/JMSTest/test.do to view the fruits of your hard work.

0. Introduction

Versions of Joram that has been reported to work:

• Joram 4.3.21

Before you proceed, don't forget to copy the JMS Driver's jar into $CATALINA_HOME/lib. In that case it is joram-client.jar, joram-connector.jar, joram-shared.jar, ow_monolog.jar, JCup.jar and jms.jar.

1. Joram configuration

First you have to set the JORAM_HOME environment variable. Then to start up the server, execute the script $JORAM_HOME/samples/bin/single_server.sh. To configure the server, execute $JORAM_HOME/samples/bin/admin.sh. In the menu Admin, choose connect. Fill the username with root and the password with root and validate with the button connect. Then in the menu JNDI, choose connect and validate with the button connect. Then you have to create connection factory, queue and topic. You will need the Destination identifier for each queue and topic, you're going to use. You need also to create a user with name "anonymous" and password "anonymous".

2. server.xml configuration

In a similar manner to the activemq config above, you will need to define your Resource in your server.xml file. Here we define a Resource called jms/ConnectionFactory.

<!-- factory: The class who's going to create the objects we need. --> <!-- cFactory.host: Name or IP address of the server's host. --> <!-- cFactory.port: Server's listening port. --> <!-- cFactory.url: url to connect to joram --> <!-- cFactory.cnxT: Duration in seconds during which connecting is attempted (connecting might take time if the server is temporarily not reachable); the 0 value is set for connecting only once and aborting if connecting failed. --> <!-- cFactory.txT: Duration in seconds during which a JMS transacted (non XA) session might be pending; above that duration the session is rolled back and closed; the 0 value means "no timer". --> <!-- cFactory.cnxPT: Period in milliseconds between two ping requests sent by the client connection to the server; if the server does not receive any ping request during more than 2 * cnxPendingTimer, the connection is considered as dead and processed as required. --> <!-- cFactory.asyncSend: Determines whether the produced messages are asynchronously sent or not (without or with acknowledgement) Default is false (with ack). --> <!-- cFactory.queueMessageReadMax: The maximum number of messages that can be read at once from a queue. Default is 1. --> <!-- reliableClass: Reliable class name, for exemple use by ssl. --> <!-- dest.name: It is the destination Identifier which you can get in the JORAM Administration Tool. I don't know why you have to use the destination Identifier and not the JNDI name. It's a question to ask to the JORAM development team. My personal opinion is that in the class ObjectFactory when they want to create a Queue, they use the name of the queue as agentid, while they should do a naming lookup to know the agentid with LookupRequest and LookupReply. --> <Resource name="jms/ConnectionFactory" auth="Container" type="org.objectweb.joram.client.jms.tcp.TcpConnectionFactory" description="JMS Connection Factory" factory="org.objectweb.joram.client.jms.admin.ObjectFactory" cFactory.host="localhost" cFactory.port="16010" cFactory.cnxT="1000" cFactory.txT="1000" cFactory.cnxPT="1000" cFactory.asyncSend="false" cFactory.queueMessageReadMax="1" reliableClass="" /> <Resource name="jms/myQueue" auth="Container" type="org.objectweb.joram.client.jms.Queue" description="JMS Queue" factory="org.objectweb.joram.client.jms.admin.ObjectFactory" dest.name="#0.0.1026" /> <Resource name="jms/myTopic" auth="Container" type="org.objectweb.joram.client.jms.Topic" description="JMS Topic" factory="org.objectweb.joram.client.jms.admin.ObjectFactory" dest.name="#0.0.1027" />

3. web.xml configuration

The tags to insert in the web.xml are the same like to insert in the ActiveMQ web.xml.

4. Test code

The code to test the Joram server is the same like to test the ActiveMQ one.

0. Introduction

Versions of OpenJms that has been reported to work:

• OpenJms 0.7.7 alpha 3

Before you proceed, don't forget to copy the JMS Driver's jar into $CATALINA_HOME/lib. In that case it is concurrent-1.3.4.jar, openjms-0.7.7-alpha-3.jar, openjms-common-0.7.7-alpha-3.jar, openjms-net-0.7.7-alpha-3.jar, commons-codec-1.3.jar, jms-1.1.jar, jndi-1.2.1.jar and spice-jndikit-20050704.053804.jar.

1. OpenJms configuration

OpenJms doesn't need any particular configuration. It's possible to get it work from a binary distribution.

2. server.xml configuration

In a similar manner to the activemq config above, you will need to define your Resource in your server.xml file. Here we define a Resource called jms/ConnectionFactory.

<!-- type: org.exolab.jms.client.JmsConnectionFactory or org.exolab.jms.client.JmsXAConnectionFactory --> <!-- factory: The class who's going to create the objects we need. --> <!-- serverClass: The class to use to make the connection --> <!-- org.exolab.jms.net.orb.provider.uri: The broker URL to set. --> <!-- org.exolab.jms.net.orb.security.principal: OpenJms username for JMS connections. --> <!-- org.exolab.jms.net.orb.security.credentials: OpenJms password for JMS connections. --> <!-- name: The JNDI name for the JMS destination on the OpenJms server and The JNDI name in the Tomcat context. Both servers use the same parameter and Tomcat don't forward the name parameter to the OpenJms client library. So it isn't possible to declare a JMS destination resource. You have to use the createDestination method. --> <!-- persistent: Is the destination persitent ? --> <Resource name="jms/ConnectionFactory" auth="Container" type="org.exolab.jms.client.JmsConnectionFactory" description="JMS Connection Factory" factory="org.exolab.jms.client.JmsConnectionFactoryBuilder" serverClass="org.exolab.jms.client.net.JmsServerStubImpl" org.exolab.jms.net.orb.provider.uri="tcp://localhost:3035/" org.exolab.jms.net.orb.security.principal="" org.exolab.jms.net.orb.security.credentials="" /> <!--Resource name="jms/myQueue" auth="Container" type="org.exolab.jms.client.JmsQueue" description="my Queue" factory="org.exolab.jms.client.JmsDestinationFactory" name="queue1" persistent="true" /--> <!--Resource name="jms/myTopic" auth="Container" type="org.exolab.jms.client.JmsTopic" description="my Topic" factory="org.exolab.jms.client.JmsDestinationFactory" name="topic1" persistent="true" /-->

3. web.xml configuration

We don't have to insert any tag in the web.xml, because we can't declare JMS destinations resource in the server.xml.

4. Test code

We can't declare this resource in the server.xml file. So we can't use it in a servlet from the tomcat context

0. Introduction

Versions of Jboss Messaging that has been reported to work:

• Jboss Messaging 1.2.0 Beta2

Before you proceed, don't forget to copy the JMS Driver's jar into $CATALINA_HOME/lib. In that case it is jboss-messaging-client.jar.

1. Jboss Messaging configuration

Jboss Messaging doesn't need any particular configuration. It's possible to get it work from a binary distribution.

Jboss Messaging implements the interface javax.naming.spi.ObjectFactory. The classes are org.jboss.jms.referenceable.ConnectionFactoryObjectFactory and org.jboss.jms.referenceable.DestinationObjectFactory. But the parameter JBM-CF for the connection factory and the parameter JBM-DEST for the destination factory have to be set with an object, which is not possible in a configuration file.