Configuring JMS Services - Creating Oracle Weblogic JMS application modules

 

Creating Oracle Weblogic JMS application modules

JMS Resources can be packed along with your application just like we did for JDBC resources. The procedure stays the same as for the data sources except that the JMS module needs to be named with the –jms.xml suffix; for example, module-name-jms.xml. Here’s an Eclipse view of an Enterprise project which contains a JMS application module:

oracle weblogic jms tutorial

And here’s an example module-jms.xml file which will be placed at the root of your EAR file:

<wls:queue name="JMSQueue">

   <wls:jndi-name>jms/queue1</wls:jndi-name>

</wls:queue>

The JMS resource needs, in turn, to be enlisted in weblogic-application.xml

<wls:module>

   <wls:name>module-jms</wls:name>

   <wls:type>JMS</wls:type>

   <wls:path>module-jms.xml</wls:path>

</wls:module>

Next, add a resource reference to all Java EE modules which are using the JMS resource, just like we did for the data source (See section “Deploying a data source at application level” in Chapter 3). The only notable difference is the resource type referenced, which should match the corresponding java JMS class; for example if you were to add a QueueConnection factory:

<res-type>javax.jms.QueueConnectionFactory</res-type>

On the other hand, a JMS queue can be referenced using a javax.jms.Queue res-type:

<res-type>javax.jms.Queue</res-type>

Francesco Google+