Technical data

18 Using the WebLogic Messaging Bridge
18-20 Administration Guide
Using the Messaging Bridge To Access Destinations In a
Release 6.1 or Later Domain
Use these guidelines when configuring a messaging bridge on a release 6.1 domain to
provide “Exactly-once” transactional message communication between two release
6.1 or later domains.
Note: The Exactly-once quality of service for transactions is only
supported for
implementations of WebLogic Server 6.1 or later.
n A messaging bridge running on release 6.1 cannot support durable subscribers
when the source destination is a JMS destination topic running on release 7.0.
Therefore, when configuring a messaging bridge on release 6.1, disable the
Durability Enabled attribute on the Messaging Bridge
→ Configuration →
General tab. This issue has been resolved for messaging bridges running on
release 7.0 or later.
n If a JMS file store is being used for persistent messages, the JMS file store name
must be unique across WebLogic domains, as described in “Naming Guidelines
for WebLogic Servers and Domains” on page 18-18.
n Make sure that security interoperability between the domains is correctly
configured, as described in “Enabling Security Interoperability for WebLogic
Domains” on page 18-19.
n Make sure that the transaction connection factory is enabled for both domains by
selecting the User Transactions Enabled and XAConnection Factory Enabled
check boxes on the Services
→ JMS → Connection Factories → Configuration
→ Transactions tab.
n Deploy the transaction resource adapter, jms-xa-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 bridge destinations, as described in “Configuring
JMS Bridge Destinations” on page 18-6, do the following for both the source
and target bridge destinations:
l In the Adapter JNDI Name field, identify the transaction adapter’s JNDI
name,
eis.jms.WLSConnectionFactoryJNDIXA.
l Do not enter anything in the Adapter Classpath field.