A startup class to enable MQ Queues to trigger MDBs in WLS 6.1(sp4)

Question

          Hi,
          I am hoping for references to documentation or opinions on the following method
          allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          with MQs connection factory.
          I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          in a startup class will not allow MDBs to be linked to an MQ queue because startup
          classes are run after MDB deployment during startup. However I found some unused
          in-house code which appeared to do just that and it works.
          Here is the code in abbreviated form:
          public String startup(String str, Hashtable args) throws Exception
               bindMQFactory();
               bindMQQueues();
               return "";
          private void bindMQFactory() throws Exception
               // Create MQ Factory and configure it
               MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
               factory.setChannel(channel );
               factory.setHostName(host);
               factory.setPort(Integer.parseInt(port));
               factory.setQueueManager(qmanager);
               factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
               // bind connection factory into WLS JNDI for later use by clients
               _wlsContext.bind( connectionFactoryJndi, factory );
               // Force mq connection factory to be the one used for mdb's
               _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          private void bindMQQueue() throws Exception
               // create queue and configure it
               MQQueue queue = new MQQueue();
               queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
               queue.setBaseQueueName( mqQueueName );
               // bind queue in WLS JNDI
               _wlsContext.bind( wlsJndi, queue );
          Thanks in advance for any comments or opinions on the above.
          regards
          Martin
          

Answer 1

Start with the white-paper:
          "Using Foreign JMS Providers with WebLogic Server"
          Note that to get transactional behavior you
          will need to use the WebLogic Messaging Bridge feature.
          Note that integrating MQ is easier in 8.1 - consider
          using WL 8.1 if you can.
          One more comment in-line.
          Martin wrote:
          > Hi,
          >
          > I am hoping for references to documentation or opinions on the following method
          > allowing the use of MQ queues to drive MDBs in WLS. The technique involves rebinding
          > the connection factory in jndi at "weblogic.jms.MessageDrivenBeanConnectionFactory"
          > with MQs connection factory.
          Not recommended. Highly not recommended. Do not use the same name
          as the internal factory. Create your own name for a CF, and change the
          weblogic ejb jar to reference your name. The above white-paper
          states how to do this.
          >
          > I read in various newsgroup posts that replacing WLS' ConnectionFactory with MQ's
          > in a startup class will not allow MDBs to be linked to an MQ queue because startup
          > classes are run after MDB deployment during startup. However I found some unused
          > in-house code which appeared to do just that and it works.
          >
          > Here is the code in abbreviated form:
          > public String startup(String str, Hashtable args) throws Exception
          > {
          >      bindMQFactory();
          >      bindMQQueues();
          >
          >      return "";
          > }
          >
          > private void bindMQFactory() throws Exception
          > {
          >
          >      // Create MQ Factory and configure it
          >      MQQueueConnectionFactory factory = new MQQueueConnectionFactory();
          >      factory.setChannel(channel );
          >      factory.setHostName(host);
          >      factory.setPort(Integer.parseInt(port));
          >      factory.setQueueManager(qmanager);
          >      factory.setTransportType( JMSC.MQJMS_TP_CLIENT_MQ_TCPIP );
          >
          >      // bind connection factory into WLS JNDI for later use by clients
          >      _wlsContext.bind( connectionFactoryJndi, factory );
          >
          >      // Force mq connection factory to be the one used for mdb's
          >      _wlsContext.rebind("weblogic.jms.MessageDrivenBeanConnectionFactory", factory);
          > }
          >
          > private void bindMQQueue() throws Exception
          > {
          >      // create queue and configure it
          >      MQQueue queue = new MQQueue();
          >      queue.setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ );
          >      queue.setBaseQueueName( mqQueueName );
          >
          >      // bind queue in WLS JNDI
          >      _wlsContext.bind( wlsJndi, queue );
          > }
          >
          > Thanks in advance for any comments or opinions on the above.
          >
          > regards
          >
          > Martin