Re: Using Websphere MQ & Weblogic 7.0 MDBs....

Question

          Sridhar,
          It interest me to to know how you got on with this.
          Thanks,
          Ranjit
          "Sridhar Krishnaswamy" <[email protected]> wrote:
          >
          >We would like to keep Websphere MQ and Weblogic on separate machines
          >and still
          >take advantage of XA. My understanding (from reading the BEA Whitepaper
          >on configuring
          >foreign JMS Providers) is that it is not possible to configure the Weblogic
          >MDBs
          >in 'Container Managed Transaction Mode', because of the limitations of
          >MQSeries
          >(until version 5.2) supporting XA only in bindings mode, which means
          >that the
          >QM Manager where the MDBs connect to have to be on the same machine.
          >
          >
          >It looks like Websphere MQ 5.3 CSD03 does not have this limitation, i.e.
          >it provides
          >an 'Extended Transactional Client' that eliminates the need for the Queue
          >Manager
          >to be on the same machine as WLS. I am struggling to configure the setup,
          >because
          >there is not much information available and the only manual I got from
          >IBM talks
          >only about configure their own AppServer, Websphere.
          >
          >Does anyone have experience with configuring MDBs getting messages from
          >a MQ Queue
          >Manager on a different machine as a Container Managed Transaction? If
          >so, any
          >pointers would help.
          >
          >Thanks,
          >Sridhar
          

Answer 1

          Hi,
          We use WebLogic 7.0 and MQSeries running on separate servers. I created the .bindings
          file with the JMSAdmin tool and create a jndi dir to store the file in the WebLogic
          domain. I also configured the classpath in the startup script for Weblogic.
          To get the MDB's to work, you define the path of the .binding file in the weblogic.xml
          file. See below classpath and xml. I never tried to look at the file through
          the jndi tree. I did not implement code to do this such as the startup class.
          It hasn't been necessary, everything works great. I'm still looking into using
          the ETC....IBM says your can't but this thread says you can. Hope this helps.
          Jennifer
          classpath info:
          $DOMAIN_HOME/lib/fscontext.jar:$DOMAIN_HOME/lib/providerutil.jar:$
          DOMAIN_HOME/lib/com.ibm.mqjms.jar:$DOMAIN_HOME/lib/com.ibm.mq.jar
          weblogic-ejb-jar.xml
          <ejb-name>SynchronousMessageControllerMDB</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>3</max-beans-in-free-pool>
          <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>RPCS.REQUEST.TO.RPCS</destination-jndi-name>
          <initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
          <provider-url>file:/opt/weblogic/apps1/rpcs/rpcsDomain/jndi</provider-url>
          <connection-factory-jndi-name>RPCSQCF</connection-factory-jndi-name>
          <jms-polling-interval-seconds>60</jms-polling-interval-seconds>
          </message-driven-descriptor>
          "Jean-François Malaise" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have the same problem but with a little difference: I don't use a start-up
          >classe
          >but configur a foreign JMS Server (I use Weblogic 8.1) and I point our
          >provider
          >url to the directory where .bindings are (That file was created by the
          >JSMAdmin
          >tool of Websphere MQ).
          >I added the CLASS_PATH of MQ jars in the StartManagedServer.sh script.
          >The problem is: when I would like to see the JNDI tree, I have the foolowing
          >message
          >instead the tree: "Access denied". I have verified the file access (we
          >used Solaris
          >8.0) for the file .binding and they are corrects.
          >
          >Is someone had already have the problem and can help me?
          >
          >"K.V.Subrahamnyam" <[email protected]> wrote:
          >>
          >>
          >>
          >>Hi Guys,
          >>
          >>Hi Guys,
          >>Attached my startup class.i can connect to MQ through that.but how i
          >>can connect
          >>through MDB.
          >>Please help me in setting up my MDB to connect to MQ series.I've followed
          >>the
          >>same way as in jmsproviders pdf document.I've one weblogic startup class.in
          >>the
          >>startup class can i give any jndi name?where it stores jndi information?how
          >>it
          >>invokes MDB?what is the provider url and connection factory jndi anme
          >>we've to
          >>give in the weblogic-ejb-jar.xml.
          >>
          >>Please provide me the exact information.I heard that if we can copy
          >.bindings
          >>file from MQ Server to WebLogic server (as both are on different machines)
          >>and
          >>point our provider url to the directory where .bindings file copied.is
          >>it the
          >>correct way.i cannot get MQ server access.how i can do it?
          >>
          >>Tom Barnes <[email protected]> wrote:
          >>>You could try contacting BEA customer support,
          >>>a support person recently got the MQ extended client working
          >>>for another customer. (Her name is Jane Sampson.)
          >>>The main thing seemed to be that you
          >>>need to make sure that all required MQ jars are in
          >>>the server class path:
          >>>
          >>>Required on WLS where MQ objects are bound into JNDI:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>
          >>>Required only if MQ objects are bound into JNDI on a different server:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>
          >>>For the jmsadmin.bat classpath, all that seems to be necessary is:
          >>>
          >>>%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>
          >>>If that doesn't work try, dumping them all in:
          >>>
          >>>set MQ_JAVA_INSTALL_PATH=C:\PROGRA~1\IBM\WEBSPH~1\Java
          >>>set MQ_JAVA_LIB=%MQ_JAVA_INSTALL_PATH%\lib
          >>>set MQJMS_CLASSPATH=%MQ_JAVA_LIB%\com.ibm.mq.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqbind.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqjms.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\com.ibm.mqetclient.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\fscontext.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\connector.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jms.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jndi.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\jta.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\ldap.jar
          >>>set MQJMS_CLASSPATH=%MQJMS_CLASSPATH%;%MQ_JAVA_LIB%\providerutil.jar
          >>>
          >>>
          >>>In addition, I doubt the startup class you
          >>>are using is required anymore - instead, leverage
          >>>the new "foreign vendor" integration features
          >>>built into 8.1 (configured via console).
          >>>
          >>>http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
          >>>
          >>>Tom
          >>>
          >>>Leong Dong wrote:
          >>>
          >>>> "Sridhar Krishnaswamy" <[email protected]> wrote:
          >>>...
          >>>>
          >>>> Sridhar,
          >>>>
          >>>> I am currently trying to configure the MQ 5.3 extended transactional
          >>>client to
          >>>> work with MDB's on WLS 8.1, and is getting the following error:
          >>>> [EJB:010196]'javax.jms.JMSException: MQJMS1068: failed to obtain
          >XAResource'
          >>>Linked
          >>>> exception = 'javax.transaction.xa.XAException: client connection
          >not
          >>>XA enabled'
          >>>>
          >>>> I am using a Startup Class to set up the JNDI objects, as described
          >>>in the "Using
          >>>> Foreign JMS Providers with WebLogic Server" document. This worked
          >>>fine with MQ
          >>>> 5.2 in "bindings" mode, but not with MQ 5.3 in extended client mode.
          >>>>
          >>>> Any suggestions you can offer is greatly appreciated.
          >>>>
          >>>> Thank you in advance,
          >>>> Leong
          >>>
          >>
          >