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-----
|
- Can I provide communication between my EJB Server and ... Murali Mohan
- Re: Can I provide communication between my EJB Server... Vikramjit Singh
- Re: Can I provide communication between my EJB Server... Vadim Gurov
- Re: Can I provide communication between my EJB Server... VargheseP
- Re: Can I provide communication between my EJB Server... Chandra Peri
- Re: Can I provide communication between my EJB Server... Milind Kulkarni