Technical data

Using the Messaging Bridge to Interoperate with Different WebLogic Server Versions
Administration Guide 18-21
n On the Messaging Bridge → Configuration → General tab, select a Quality Of
Service of Exactly-once, as described in “Configuring a Messaging Bridge
Instance” on page 18-12.
Using the Messaging Bridging To Access Destinations In
a Release 6.0 Domain
When configuring a messaging bridge involves interoperability between WebLogic
Server 6.1 and a release 6.0 domain, you must configure the following settings on the
release 6.1 domain that the bridge is running on:
Note: The Exactly-once QOS for transactions is not supported for WebLogic Server
6.0. For more information on the bridge QOS options, see “Messaging Bridge
Attributes on the General Tab” on page 18-12.
n Deploy the non-transaction resource adapter, jms-notran-adp.rar on the 6.1 bridge
domain, as described in “Deploying the Bridge’s Resource Adapters” on page 18-5.
n When configuring the JMS source and target destinations, as described in
“Configuring JMS Bridge Destinations” on page 18-6, do the following:
In the Adapter JNDI Name field:
l For the source and target destinations, specify the non-transaction adapter’s
JNDI name as
eis.jms.WLSConnectionFactoryJNDINoTX.
In the Adapter Classpath field:
l For the 6.1 destination, leave the field blank.
l For the 6.0 destination, indicate the location of the classes for the WebLogic Server
6.0 release
.
For example, if you have WebLogic Server 6.0 GA installed in a directory
named
WL60_HOME, then set the Adapter Classpath as follows for the 6.0
JMS bridge destination:
WL60_HOME\lib\weblogic60.jar
n On the Messaging Bridge → Configuration → General tab, select a Quality Of
Service of Atmost-once
or Duplicate-okay, as described in “Configuring a
Messaging Bridge Instance” on page 18-12.