BEA does not support JTA integration with MQSeries (or any other external JMS provider) for outbound messages, unless you use a proprietary call to enlist the JMS XA session with the WebLogic transaction manager. Inbound messages integrate well (without the need for proprietary calls) with JTA as long as you use MDBs.

 

BEA also provides a bridge service to bridge their internal JMS provider with any external JMS provider (like MQSeries). Using the bridge (WLS Messaging Bridge) allows you to get full 2PhC integration between EJBs and MQSeries without proprietary code. A drawback of this approach is that you will need to monitor both BEA JMS destinations as well as MQSeries destinations.

 

When it comes to making IBM managed objects and connection factory references available through JNDI, we have found using a WLS start-up class to be a practical solution. The start-up class populates the WLS jndi implementation with MQSeries connection factory references and destination objects using the jndi api. WLS does not allow you to define the order in which the start-up class is run relative to WLS starting up the MDB listeners. The hen-and-the-egg problem J Fortunately, WLS MDB engine will retry until your start-up–class  has made the objects available through jndi.

 

/Johan

 

 

-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]On Behalf Of [EMAIL PROTECTED]
Sent: den 5 mars 2003 16:53
To: [EMAIL PROTECTED]
Subject: Re: Can I provide communication between my EJB Server and MQSeries?????????

 


I had also tried out this sometime back for integrating Weblogic server and MQ Series using JMS. There are many options. But I had to consider the option of making it app server independent. One way is using a file system context where you will specify a file where the bindings of the MQ JMS Adminstered objects will be specified. But that makes the system look for a file and the file has to be put in a common location for MQ and weblogic. Then I considered the option of an rmi registry. But that one also requires the rmi registry run in the same machine as the MQ, otherwise I was not able to bind the JMS objects of MQ to the registry.. Does anybody know a workaround for this??



 

Murali Mohan <[EMAIL PROTECTED]>
Sent by: A mailing list for Enterprise JavaBeans development <[EMAIL PROTECTED]>

03/05/03 06:53 PM
Please respond to Murali Mohan

       
        To:        [EMAIL PROTECTED]
        cc:        
        Subject:        Can I provide communication between my EJB Server and MQSeries?????????




Can I provide communication between my EJB Server and MQSeries(or any
other queing server)?????????

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".


Reply via email to