17 Administering the Java Message Service (JMS)

To Deploy and Configure GenericJMSRA

Before deploying GenericJMSRA, JMS client libraries must be made available to GlassFish Server. For some JMS providers, client libraries might also include native libraries. In such cases, these native libraries must be made available to any GlassFish Server JVMs.

1. Download the genericra.rar archive as an Add-On in the Administration Console's Update Tool.

2. Deploy GenericJMSRA the same way you would deploy a connector module.

   See "Deploying a Connector Module" in Oracle GlassFish Server Application Deployment Guide.

3. Configure the resource adapter's properties.

   See GenericJMSRA Configuration Properties.

4. Create a connector connection pool.

   See To Create a Connector Connection Pool.

5. Create a connector resource.

   See To Create a Connector Resource.

6. Create an administered object resource.

   See To Create an Administered Object.

GenericJMSRA Configuration Properties

The following table describes the properties that can be set to when configuring the resource adapter.

Connection Factory Properties

ManagedConnectionFactory properties are specified when a connector-connection-pool is created. All the properties specified while creating the resource adapter can be overridden in a ManagedConnectionFactory. Additional properties available only in ManagedConnectionFactory are given below.

Destination Properties

Properties in this section are specified when a destination (queue or topic) is created. All the resource adapter properties can be overridden in a destination. Additional properties available only in the destination are given below.

Activation Spec Properties

Properties in this section are specified in the GlassFish Server glassfish-ejb-jar.xml deployment descriptor of an MDB as activation-config-properties. All the resource adapter properties can be overridden in an Activation Spec. Additional properties available only in ActivationSpec are given below.

Deploy the WebLogic Thin T3 Client JAR in GlassFish Server

WebLogic Server provides several different clients for use by standalone applications that run outside of WebLogic Server. These client are summarized in "Overview of Stand-alone Clients" in Programming Stand-alone Clients for Oracle WebLogic Server. When connecting from GlassFish Server to WebLogic JMS resources you must use the WebLogic Thin T3 client, wlthint3client.jar.

There are a couple of methods to deploy the WebLogic Thin T3 client in GlassFish Server and make it available to GenericJMSRA:

• To make the Thin T3 client available to all applications, copy the wlthint3client.jar to the as-install/lib directory under your GlassFish Server installation. The Thin T3 client can be found in a WebLogic Server installation in a directory similar to MW_HOME/server/lib.

• It is also possible to deploy the Thin T3 client in a less global manner, so that it is specific to an individual application. For information on how to do this, see "Application-Specific Class Loading" in Oracle GlassFish Server Application Development Guide.

Configure WebLogic JMS Resources for Integration

If you need to configure the necessary WebLogic JMS resources on the WebLogic Server from which you want to access messages using GlassFish Server, then follow the instructions in the WebLogic Server documentation for configuring the necessary resources, such as destinations, and connection factories.

• JMS System Module Configuration

• Queue and Topic Destination Configuration

• Connection Factory Configuration

The example code snippets in this section refer to a WebLogic JMS connection factory named WLoutboundQueueFactory and queue destination named WLoutboundQueue. For conceptual overviews on configuring WebLogic JMS resources, refer to "Understanding JMS Resource Configuration" in Configuring and Managing JMS for Oracle WebLogic Server. For detailed instructions on configuring WebLogic JMS resources, refer to "Configure JMS system modules and add JMS resources" in the WebLogic Administration Console Online Help.

Create a Resource Adapter Configuration for GenericJMSRA to Work With WebLogic JMS

When you deploy GenericJMSRA, you also need to create a resource adapter configuration in GlassFish Server. You can do this using either the Administration Console or the asadmin command. If you use theAdministration Console then you need deploy the GenericJMSRA resource archive first. Here's an example using asadmin:

asadmin create-resource-adapter-config --host localhost --port 4848 --property
SupportsXA=false:DeliveryType=Synchronous:ProviderIntegrationMode
                          =jndi:JndiProperties=java.naming.factory.initial\
                          =weblogic.jndi.WLInitialContextFactory,java.naming.provider.url\
                          =t3\://localhost\:7001,java.naming.factory.url.pkgs\
                          =weblogic.corba.client.naming genericra

This creates a resource adapter configuration with the name genericra, and Oracle recommends not changing the default name. The resource adapter configuration is configured with the properties specified using the --properties argument; multiple properties are configured as a colon-separated list of name-value pairs that are entered as a single line. You will also need to change the host and port that WebLogic Server is running on to suit your installation.

In this example, the following properties are configured:

java.naming.factory.initial
=weblogic.jndi.WLInitialContextFactory,java.naming.provider.url
=t3://localhost:7001,java.naming.factory.url.pkgs
=weblogic.corba.client.naming

(replace "localhost:7001" with the host:port of WebLogic Server)

You must use the same values for SupportsXA, DeliveryType and ProviderIntegrationMode as the required values that are used in this table. The JndiProperties value must be set to a list of JNDI properties needed for connecting to WebLogic JNDI.

For a description of all the resource adapter properties that are relevant for WebLogic JMS, see the Configuration Reference of GenericJMSRA Properties for WebLogic JMS.

Deploy the GenericJMSRA Resource Archive

The supported version of the GenericJMSRA resource archive is available as an Add-On in the Administration Console's Update Tool.

1. Download the GenericJMSRA resource archive (genericra.rar) using the Administration Console's Update Tool.

2. Deploy the resource adapter. You can do this using either the Administration Console or the asadmin deploy command. Here's an example using the asadmin deploy command:

   $ asadmin deploy --user admin --password adminadmin
     <location of the generic resource adapter rar file>
   

   If you deploy the resource adapter using the Administration Console, then after deployment you need to create a resource adapter configuration as described in Create a Resource Adapter Configuration for GenericJMSRA to Work With WebLogic JMS.

Configuring an MDB to Receive Messages from WebLogic JMS

In this example, all configuration information is defined in two deployment descriptor files: ejb-jar.xml and the GlassFish Server glassfish-ejb-jar.xml file. To configure a MDB to receive messages from WebLogic JMS, you would configure these deployment descriptor files as follows:

1. Configure the ejb-jar.xml deployment descriptor:

   <ejb-jar>
     <enterprise-beans>
       <message-driven>
         <ejb-name>SimpleMessageEJB</ejb-name>
         <ejb-class>test.simple.queue.ejb.SimpleMessageBean</ejb-class>
         <transaction-type>Container</transaction-type>
       </message-driven>
     </enterprise-beans>
     <assembly-descriptor>
       <container-transaction>
         <method>
           <ejb-name>SimpleMessageEJB</ejb-name>
           <method-name>onMessage</method-name>
           <method-params>
             <method-param>javax.jms.Message</method-param>
           </method-params>
         </method>
         <trans-attribute>NotSupported</trans-attribute>
       </container-transaction>
     </assembly-descriptor>
   </ejb-jar>
   

   Note:

   If container-managed transactions are configured, then the transactional attribute must be set to NotSupported. For more information, see Limitations When Using GenericJMSRA with WebLogic JMS.

2. Configure the glassfish-ejb-jar.xml deployment descriptor:

   <sun-ejb-jar>
     <enterprise-beans>
       <ejb>
         <ejb-name>SimpleMessageEJB</ejb-name>
         <mdb-resource-adapter>
           <resource-adapter-mid>genericra</resource-adapter-mid>
           <activation-config>
             <activation-config-property>
               <activation-config-property-name>
                 ConnectionFactoryJndiName
               </activation-config-property-name>
               <activation-config-property-value>
                 jms/WLInboundQueueFactory
               </activation-config-property-value>
             </activation-config-property>
             <activation-config-property>
               <activation-config-property-name>
                 DestinationJndiName
               </activation-config-property-name>
               <activation-config-property-value>
                 jms/WLInboundQueue
               </activation-config-property-value>
             </activation-config-property>
           </activation-config>
         </mdb-resource-adapter>
       </ejb>
     </enterprise-beans>
   </sun-ejb-jar>
   

   where:

   The <resource-adapter-mid>genericra</resource-adapter-mid> element is used to specify the resource adapter and resource adapter configurations that was deployed in the Create a Resource Adapter Configuration for GenericJMSRA to Work With WebLogic JMS instructions. It is recommended you stick to genericra as is used here.

   The activation-config element in glassfish-ejb-jar.xml is the one which defines how and where the MDB receives messages, as follows:

   • The ConnectionFactoryJndiName property must be set to the JNDI name of the connection factory in the WebLogic JNDI store that will be used to receive messages. Therefore, replace jms/WLInboundQueueFactory in the example above with the JNDI name used in your environment.

   • The DestinationJndiName property must be set to the JNDI name of the destination (the queue or topic from which messages will be consumed) in the WebLogic JNDI store. Therefore, replace jms/WLInboundQueue in the example above with the JNDI name used in your environment.

   For a description of all the ActivationSpec properties that are relevant for WebLogic JMS, see the Configuration Reference of GenericJMSRA Properties for WebLogic JMS.

   Make sure to use the appropriate WebLogic administration tools, such as the WebLogic Administration Console or the WebLogic Scripting Tool (WLST). For more information, see "Configure Messaging" in WebLogic Server Administration Console Online Help and WebLogic Server WLST Online and Offline Command Reference.

Accessing Connections and Destinations Directly

When configuring a MDB to consume messages from WebLogic JMS your code does not need to access the WebLogic JMS connection factory and destination directly. You simply define them in the activation configuration, as shown in Configuring an MDB to Receive Messages from WebLogic JMS. However when configuring an MDB to send messages, or when configuring a EJB, Servlet, or application client to either send or receive messages, your code needs to obtain these objects using a JNDI lookup.

1. Looking up the connection factory and destination

   The following code looks up a connection factory with the JNDI name jms/QCFactory and a queue with the namejms/outboundQueue from the GlassFish Server JNDI store:

   Context initialContect  = new InitialContext();
        QueueConnectionFactory queueConnectionFactory = (QueueConnectionFactory) 
             jndiContext.lookup("java:comp/env/jms/MyQCFactory");
        Queue queue = (Queue) jndiContext.lookup("java:comp/env/jms/outboundQueue");
   

   Note that the resources used are GlassFish Server resources, not WebLogic JMS resources. For every connection factory or destination that you want to use in the WebLogic JMS JNDI store, you need to create a corresponding connection factory or destination in the GlassFish Server JNDI store and configure the GlassFish Server object to point to the corresponding WebLogic JMS object.

2. Declaring the connection factory and destination

   In accordance with standard Java EE requirements, these resources need to be declared in the deployment descriptor for the MDB, EJB or other component. For example, for a session bean, configure the ejb-jar.xml with <resource-env-ref> elements, as follows:

   <ejb-jar>
     <enterprise-beans>
       <session>
         . . .
         <resource-env-ref>
           <resource-env-ref-name>jms/QCFactory</resource-env-ref-name>
           <resource-env-ref-type>javax.jms.QueueConnectionFactory</resource-env-ref-type>
         </resource-env-ref>
         <resource-env-ref>
           <resource-env-ref-name>jms/outboundQueue</resource-env-ref-name>
           <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
         </resource-env-ref>
   

3. Create a Connector Connection Pool and Connector Resource by entering the following asadmin commands, both all in one line:

   In order to configure a JMS Connection Factory using GenericJMSRA, a Connector connection pool and resource need to be created in GlassFish Server using names that map to the corresponding connection factory in the WebLogic JNDI store.

   asadmin create-connector-connection-pool --host localhost --port 4848
      --raname genericra --connectiondefinition javax.jms.QueueConnectionFactory 
      --target server --transactionsupport LocalTransaction
      --property ConnectionFactoryJndiName=jms/WLOutboundQueueFactory
        qcpool
   
   asadmin create-connector-resource --host localhost --port 4848 
       --poolname qcpool --target server jms/QCFactory
   

   These asadmin commands together creates a connection factory in GlassFish Server and its corresponding connection pool.

   • The connection pool has the JNDI name jms/WLoutboundQueueFactory and obtains connections from a connection pool named qcpool.

   • The connection pool qcpool uses the resource adapter genericra and contains objects of type javax.jms.QueueConnectionFactory.

   • The transactionsupport argument is set to LocalTransaction, which specifies that the connection will be used in local transactions only. You can also specify NoTransaction. However, the default setting of XATransaction cannot be used. For more information, see Limitations When Using GenericJMSRA with WebLogic JMS.

   • The connection pool is configured with the properties specified using the properties argument; multiple properties are configured as a colon-separated list of name-value pairs. Only one property is configured in this example, as follows:

     ConnectionFactoryJndiName=jms/WLOutboundQueueFactory
     

     The ConnectionFactoryJndiName property must be set to the JNDI name of the corresponding connection factory in the WebLogic JMS JNDI store. Therefore, replace jms/WLOutboundQueueFactory in the example above with the JNDI name used in your environment.

   • For a description of the ManagedConnectionFactory properties that are relevant for WebLogic JMS, see the Configuration Reference of GenericJMSRA Properties for WebLogic JMS.

4. Create a destination object that refers to a corresponding WebLogic JMS destination by entering the following asadmin command, all in one line:

   asadmin create-admin-object --host localhost --port 4848 --target server 
       --restype javax.jms.Queue --property DestinationJndiName=jms/WLOutboundQueue 
       --raname genericra jms/outboundQueue
   

   This asadmin command creates a destination in GlassFish Server.

   • The destination has the JNDI name jms/outboundQueue, uses the resource adapter genericra, and is of type javax.jms.Queue.

   • The destination is configured with the properties specified using the properties argument; multiple properties are configured as a colon-separated list of name-value pairs. Only one property is configured in this example, as follows:

     DestinationJndiName=jms/WLOutboundQueue
     

     The DestinationJndiName property must be set to the JNDI name of the corresponding destination in the WebLogic JMS JNDI store. Therefore, replace jms/WLOutboundQueue in the example above with the JNDI name used in your environment.

   • For a description of the destination properties that are relevant for WebLogic JMS, see the Configuration Reference of GenericJMSRA Properties for WebLogic JMS.

Limitations When Using GenericJMSRA with WebLogic JMS

Due to the nature of the WebLogic T3 Thin Client there are a number of limitations in the way in which it can be used with GenericJMSRA.

Configuration Reference of GenericJMSRA Properties for WebLogic JMS

The tables in this section list the properties that need to be set to configure the resource adapter and any activation specs, managed connections, and other administered objects that are relevant only when using GenericJMSRA to communicate with WebLogic JMS. For a complete list of properties, see the comprehensive table in GenericJMSRA Configuration Properties

Resource Adapter Properties

These properties are used to configure the resource adapter itself when it is deployed, and can be specified using the create-resource-adapter-config command.

java.naming.factory.initial
=weblogic.jndi.WLInitialContextFactory,
java.naming.provider.url
=t3://localhost:7001,java.naming.factory.url.pkgs
=weblogic.corba.client.naming
(replace localhost:7001 with
the host:port of WebLogic Server)

Connection Factory Properties

ManagedConnectionFactory objects are created in the GlassFish Server JNDI store using the Administration Console or the asadmin connector-connection-pool command. All the properties that can be set on a resource adapter configuration can be overridden by setting them on a destination object. The properties specific to ManagedConnectionFactory objects are listed in the following table.

Destination Properties

Destination (queue or topic) objects are created in the GlassFish Server JNDI store using the Administration Console or the asadmin connector-admin-object command. All the properties that can be set on a resource adapter configuration can be overridden by setting them on a destination object. The properties specific to destination objects are listed in the following table.

ActivationSpec Properties

An ActivationSpec is a set of properties that configures a MDB. It is defined either in the MDB's GlassFish Server deployment descriptor glassfish-ejb-jar.xml using activation-config-property elements or in the MDB itself using annotation. All the resource adapter properties listed in the table above can be overridden in an ActivationSpec. Additional properties available only to a ActivationSpec are given below.

Preliminary Setup Procedures for WebSphere MQ Integration

Before you can configure WebSphere MQ to exchange messages with GlassFish Server, you must complete the following tasks:

• The following permissions must be added to the server.policy and the client.policy file to deploy GenericJMSRA and to run the client application.

  • Use a text editor to modify the server.policy file in the ${appserver-install-dir}/domains/domain1/config/directory by adding the following line to the default grant block:

    permission java.util.logging.LoggingPermission "control";
    permission java.util.PropertyPermission "*", "read,write";
    

  • If you use an application client in your application, edit the client's client.policy file in the ${appserver-install-dir}/lib/appclient/ directory by adding the following permission:

    permission javax.security.auth.PrivateCredentialPermission
    "javax.resource.spi.security.PasswordCredential * \"*\"","read";
    

• To integrate GlassFish Serverwith WebSphere MQ 6.0 or 7.0, copy the necessary JAR files to the as-install/lib directory:

  • For WebSphere MQ 6.0, copy these JAR files to the as-install/lib directory:

    /opt/mqm/java/lib/com.ibm.mq.jar
    /opt/mqm/java/lib/com.ibm.mq.jms.Nojndi.jar
    /opt/mqm/java/lib/com.ibm.mq.soap.jar
    /opt/mqm/java/lib/com.ibm.mqjms.jar
    /opt/mqm/java/lib/com.ibm.mqetclient.jar
    /opt/mqm/java/lib/commonservices.jar
    /opt/mqm/java/lib/dhbcore.jar
    /opt/mqm/java/lib/rmm.jar
    /opt/mqm/java/lib/providerutil.jar
    /opt/mqm/java/lib/CL3Export.jar
    /opt/mqm/java/lib/CL3Nonexport.jar
    

    where /opt/mqm is the location of the WebSphere MQ 6.0 installation.

  • For WebSphere MQ 7.0, copy these JAR files to the as-install/lib directory:

    /opt/mqm/java/lib/com.ibm.mq.jar,
    /opt/mqm/java/lib/com.ibm.mq.jms.Nojndi.jar,
    /opt/mqm/java/lib/com.ibm.mq.soap.jar,
    /opt/mqm/java/lib/com.ibm.mqjms.jar,
    /opt/mqm/java/lib/com.ibm.mq.jmqi.jar,
    /opt/mqm/java/lib/com.ibm.mq.commonservices.jar,
    /opt/mqm/java/lib/dhbcore.jar,
    /opt/mqm/java/lib/rmm.jar,
    /opt/mqm/java/lib/providerutil.jar,
    /opt/mqm/java/lib/CL3Export.jar,
    /opt/mqm/java/lib/CL3Nonexport.jar
    

    where /opt/mqm is the location of the WebSphere MQ 7.0 installation.

• Set the LD_LIBRARY_PATH environment variable to the java/lib directory, and then restart GlassFish Server. For example, in a UNIX—based system, with WebSphere MQ installed under /opt/mqm, you would enter:

  $ export LD_LIBRARY_PATH=/opt/mqm/java/lib
  

Configure the WebSphere MQ Administered Objects

This section provides an example of how you could configure the necessary administered objects, such as destinations and connection factories, on the WebSphere MQ instance from which you want to access messages using GlassFish Server. Therefore, you will need to change the administered object names to suit your installation.

Before You Begin

If WebSphere MQ created a user and a group named mqm during the installation, then you must specify a password for the mqm user using the $ passwd mqm command.

1. Switch to the mqm user:

   $ su mqm

2. For Linux, set the following kernel version:

   $ export LD_ASSUME_KERNEL=2.2.5

3. Create a new MQ queue manager named "QM1":

   $ crtmqm QM1

4. Start the new MQ queue manager.

   In the image above, QM1 is associated with the IBM WebSphere MQ broker.

   $ strmqm QM1

5. Start the MQ listener:

   $ runmqlsr -t tcp -m QM1 -p 1414 &

6. Modify the default JMSAdmin console configuration as follows:

   1. Edit the JMSAdmin script in the /opt/mqm/java/bin directory to change the JVM to a location of a valid JVM your system.

   2. Set the relevant environment variable required for JMSAdmin by sourcing the setjmsenv script located in the /opt/mqm/java/bin directory.

      $ cd /opt/mqm/java/bin
      $ source setjmsenv
      

      where /opt/mqm is the location of the WebSphere MQ installation.

   3. Change the JMSAdmin.config file to indicate the Initial Context Factory you will be using by setting the following name-value pairs and commenting out the rest:

      INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
          PROVIDER_URL=file:/opt/tmp
      

7. Create WebSphere MQ queues using the runmqsc console and MQJMS_PSQ.mqsc script.

   $ runmqsc QM1 < MQJMS_PSQ.mqsc

8. Create user defined physical queue for your application using runmqsc console and an appropriate physical queue name. An example of how this could be done is shown below.

   In the image above, ORANGE.LOCAL.QUEUE is associated with QM1.

   $ runmqsc QM1
                > DEFINE QLOCAL(ORANGE.LOCAL.QUEUE)
                > end
   

9. Start the WebSphere MQ Broker:

   $ strmqbrk -m QM1

10. In the WebSphere MQ JMSAdmin console, use the following commands to create the connection factories, XA connection factories, and destinations for your application, as shown in the following sample, which lists each of the various JMS administered objects.

    In the image above, QCF (for QM1) and TQueue (associated with ORANGE.LOCAL.QUEUE) are defined in the FileSystem Naming Context.

    $ ./JMSAdmin
       
       InitCtx>def qcf<JNDI name to be given to the Queue Connection Factory> 
         hostname<IBM MQ server hostname> port(1414) channel(SYSTEM.DEF.SVRCONN)
         transport(CLIENT) qmanager<name of queue manager defined>
       
         For example:
         def qcf(QCF) hostname(localhost) port(1414) channel(SYSTEM.DEF.SVRCONN) 
          transport(CLIENT) qmanager(QM1)
       
       InitCtx%def xaqcf<JNDI name to be given to the XA Queue Connection Factory> 
         hostname<IBM MQ server hostname> port(1414) channel(SYSTEM.DEF.SVRCONN)
         transport(CLIENT) qmanager<name of queue manager defined>
      
         For example:
         def xaqcf(XAQCF) hostname(localhost) port(1414) channel(SYSTEM.DEF.SVRCONN) 
         transport(CLIENT) qmanager(QM1)
       
       InitCtx%def q<JNDI Name to be given to the Queue> queue<physical queue name> 
         qmanager(name of queue manager defined )
       
         For example: def q(TQueue) queue(ORANGE.LOCAL.QUEUE) qmanager(QM1)
       
       InitCtx%def tcf<JNDI Name to be given to the Topic Connection Factory> 
         qmanager(name of queue manager defined )
       
         For example: def tcf(TCF) qmanager(QM1)
       
       InitCtx%def xatcf<JNDI Name to be given to the  XA Topic Connection Factory> 
         qmanager(name of queue manager defined )
       
         For example: def xatcf(XATCF) qmanager(QM1)
       
       InitCtx%def t<JNDI Name to be given to the Topic> topic<sample topic name>
       
         For example: def t(TTopic) topic(topic)
    

Create a Resource Adapter Configuration for GenericJMSRA to Work With WebSphere MQ

Before deploying GenericJMSRA, you need to create a resource adapter configuration in GlassFish Server. You can do this using either the Administration Console or the asadmin command. Use the following asadmin command to create a resource adapter configuration for genericra to configure it to work with WebSphere MQ.

asadmin> create-resource-adapter-config
                       --user <adminname> --password <admin password>
                       --property SupportsXA=true:ProviderIntegrationMode
                       =jndi:UserName=mqm:Password=###:RMPolicy
                       =OnePerPhysicalConnection:JndiProperties
                       =java.naming.factory.url.pkgs\\
                       =com.ibm.mq.jms.naming,java.naming.factory.initial\\
                       =com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\
                       =file\\:\\/\\/opt\\/tmp:LogLevel=finest genericra

This creates a resource adapter configuration with the name genericra, and Oracle recommends not changing the default name. The resource adapter configuration is configured with the properties specified using the --properties argument; multiple properties are configured as a colon-separated list of name-value pairs that are entered as a single line.

In this example, the following properties are configured:

JndiProperties=
java.naming.factory.url.pkgs\\
=com.ibm.mq.jms.naming,java.naming.
factory.initial\\=com.sun.jndi.fscontext.
RefFSContextFactory,java.naming.
provider.url\\
=file\\:\\/\\/opt\\/tmp:
LogLevel=finest genericra

Deploy the GenericJMSRA Archive

The GenericJMSRA archive is available as an Add-On in the Administration Console's Update Tool.

For instructions on downloading and deploying GenericJMSRA, see Deploy the GenericJMSRA Resource Archive.

Create the Connection Factories and Administered Objects in GlassFish Server

In order to configure a JMS Connection Factory using GenericJMSRA, a Connector Connection Pool and resource needs to be created in GlassFish Server, as described in this section.

Using the example WebSphere MQ configuration in Configure the WebSphere MQ Administered Objects, you will see mypool (pointing to GenericJMSRA and QCF) and jms/MyQCF (for mypool) created in GlassFish Server.

Configuring an MDB to Receive Messages from WebSphere MQ

The administered object names in the sample deployment descriptor below map to the example WebSphere MQ configuration in Configure the WebSphere MQ Administered Objects. The deployment descriptors need to take into account the resource adapter and the connection resources that have been created. A sample sun-ejb-jar.xml for a Message Driven Bean that listens to a destination called TQueue in WebSphere MQ, and publishes back reply messages to a destination resource named jms/replyQueue in GlassFish Server, as shown below.

<sun-ejb-jar>
         <enterprise-beans>
         <unique-id.1</unique-id>
         <ejb>
            <ejb-name>SimpleMessageEJB</ejb-name>
            <jndi-name>jms/SampleQueue</jndi-name>
             <!-- QCF used to publish reply messages -->
            <resource-ref>
               <res-ref-name>jms/MyQueueConnectionFactory</res-ref-name>
               <jndi-name>jms/MyQCF</jndi-name>
               <default-resource-principal>
                  <name>mqm</name>
                  <password>mqm</password>
               </default-resource-principal>
            </resource-ref>
            <!-- reply destination resource> Creating of this replyQueue destination resource is not
                 shown above, but the steps are similar to creating the  "jms/MyQueue" resource -->
            <resource-env-ref>
               <resource-env-ref-name>jms/replyQueue</resource-env-ref-name>
               <jndi-name>jms/replyQueue</jndi-name>
            </resource-env-ref>
            
            <!-- Activation related RA specific configuration for this MDB -->
            <mdb-resource-adapter>
            <!-- resource-adapter-mid points to the Generic Resource Adapter for JMS -->
            <resource-adapter-mid>genericra</resource-adapter-mid>
            <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>ConnectionFactoryJndiName</activation-config-property-name>
                  <activation-config-property-value>QCF</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>DestinationJndiName</activation-config-property-name>
                  <activation-config-property-value>TQueue</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>MaxPoolSize</activation-config-property-name>
                  <activation-config-property-value>32</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>RedeliveryAttempts</activation-config-property-name>
                  <activation-config-property-value>0</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>ReconnectAttempts</activation-config-property-name>
                  <activation-config-property-value>4</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>ReconnectInterval</activation-config-property-name>
                  <activation-config-property-value>10</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>RedeliveryInterval</activation-config-property-name>
                  <activation-config-property-value>1</activation-config-property-value>
               </activation-config-property>
               <activation-config-property>
                  <activation-config-property-name>SendBadMessagesToDMD</activation-config-property-name>
                  <activation-config-property-value>false</activation-config-property-value>
               </activation-config-property>
            </activation-config>
          </mdb-resource-adapter>
          </ejb>
          </enterprise-beans>
       </sun-ejb-jar>

The business logic encoded in Message Driven Bean could then lookup the configured QueueConnectionFactory/Destination resource to create a connection as shown below.

Context context = null;
             ConnectionFactory connectionFactory = null;
             logger>info("In PublisherBean>ejbCreate()");
             try {
                 context = new InitialContext();
                 queue = (javax>jms>Queue) context>lookup ("java:comp/env/jms/replyQueue");
                 connectionFactory = (ConnectionFactory) context>lookup("java:comp/env/jms/MyQueueConnectionFactory");
                 connection = connectionFactory>createConnection();
             } catch (Throwable t) {
                 logger>severe("PublisherBean>ejbCreate:" + "Exception: " +
                 t>toString());
             }