Glassfish V3.1 running embedded ActiveMQ for JMS (Part 3)

In the third and final part of this tutorial we will crate a MDB (Message Driven Bean) that listens to our embedded ActiveMQ from Part 1.

Pre-Requirements:

• Netbeans 6.5 +
• Glassfish Setup from Tutorial Part 1

Tutorial:

• Create a new EJB AmdMDB
  

  New EJB Project

  

  New EJB Project

  

  New EJB Project

• Create a Message Driven Bean NewMessageBean
  

  Message Driven Bean

  

  Message Driven Bean

• Create a Glassfish Descriptor glassfish-ejb-jar.xml
  

  glassfish-ejb-jar.xml

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE glassfish-ejb-jar PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 EJB 3.1//EN" "http://glassfish.org/dtds/glassfish-ejb-jar_3_1-1.dtd">
  <glassfish-ejb-jar>
   <enterprise-beans>
    <ejb>
     <ejb-name>NewMessageBean</ejb-name>
      <mdb-resource-adapter>
       <resource-adapter-mid>activemq-rar-5.5.0</resource-adapter-mid>
      </mdb-resource-adapter>
        <mdb-connection-factory>
            <jndi-name>amqpool</jndi-name>
      </mdb-connection-factory>
     </ejb>
   </enterprise-beans>
  </glassfish-ejb-jar>
  

• Create a Standard Deployment Descriptor ejb-jar.xml
  

  ejb-jar.xml

  <?xml version="1.0" encoding="UTF-8"?>
  
  <ejb-jar xmlns = "http://java.sun.com/xml/ns/javaee"
           version = "3.1"
           xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation = "http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd">
      <display-name>Ejb1</display-name>
      <enterprise-beans>
          <message-driven>
              <display-name>NewMessageBean</display-name>
              <ejb-name>NewMessageBean</ejb-name>
              <ejb-class>mdb.NewMessageBean</ejb-class>
              <messaging-type>javax.jms.MessageListener</messaging-type>
              <transaction-type>Container</transaction-type>
              <activation-config>
                  <activation-config-property>
                      <activation-config-property-name>DestinationType</activation-config-property-name>
                      <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
                  </activation-config-property>
                  <activation-config-property>
                      <activation-config-property-name>Destination</activation-config-property-name>
                      <activation-config-property-value>amqmsg</activation-config-property-value>
                  </activation-config-property>
              </activation-config>
          </message-driven>
      </enterprise-beans>
      <assembly-descriptor>
          <container-transaction>
              <method>
                  <ejb-name>NewMessageBean</ejb-name>
                  <method-name>onMessage</method-name>
                  <method-params>
                      <method-param>java.lang.String</method-param>
                  </method-params>
              </method>
              <trans-attribute>Required</trans-attribute>
          </container-transaction>
      </assembly-descriptor>
  </ejb-jar>
  

• Deploy the EJB
  

  Deployment

• Send a message from ActiveMQ Web Console
  

  Send Message

  

  Receive Message

• Send Message from external Client (from Part 2)
  

  External Client

 

Resume

In the 3 parts of the tutorial we walked through all the steps from embedding ActiveMQ into Glassfish, sending messages from both admin client and external client and receiving messages in a MDB. It is a working sample, that requires some finetuning towards more security and certainly features. I hope it helps you to get started, even all the nitty-gritty details and JMS science stuff are omitted. I believe it is much easier to get started with a working sample and begin to adopt to your own needs and read more in some of the JMS, ActiveMQ and Glassfish books and websites.
I spend more time trying to get a external client to talk to Glassfish JMS (unsuccessfully) than to get the above setup into a production system ! Thanks to AvtiveMQ team for this great messaging tool.

About these ads