Use the following guidelines to configure interoperability to handle transactional messages (using the Exactly-once QOS) between two WebLogic domains

• You must correctly configure either Cross Domain Security or Security Interop Mode for all participating domains.

  Keep all the domains used by your process symmetric with respect to Cross Domain Security configuration and Security Interop Mode. Because both settings are set at the domain level, it is possible for a domain to be in a mixed mode, meaning the domain has both Cross Domain Security and Security Interop Mode set. For more information, see:

  • Configuring Secure Inter-Domain and Intra-Domain Transaction Communication in Developing JTA Applications for Oracle WebLogic Server

  • Changing the Asynchronous Mode Enabled Attribute in Tuning Performance of Oracle WebLogic Server

• When interoperating between two WebLogic domains, see Naming Guidelines for WebLogic Servers and Domains.

• Ensure that the XA connection factory is enabled for the domains by selecting the XAConnection Factory Enabled.

  See Configure Resources for JMS System Modules in the Oracle WebLogic Remote Console Online Help.

• Deploy the transaction resource adapter, jms-xa-adp.rar, on the domain where the messaging bridge is running.

  Note:

  Messaging bridge configuration has been simplified since WebLogic Server 12.2.1. You need not explicitly configure and deploy bridge adapters. Instead, a messaging bridge now uses the automatically deployed internal adapters when the bridge is configured with a default adapter JNDI name (eis.jms.WLSConnectionFactoryJNDINoTX or eis.jms.WLSConnectionFactoryJNDIXA). These internal adapters also have a much larger connection capacity.

  Legacy adapters explicitly configured with the default adapter JNDI names still deploy, but are ignored by messaging bridges. The legacy adapter deployments can be removed in the configuration after upgrading to WebLogic Server 12.2.1.

• When configuring the JMS bridge destinations, as described in Create a JMS Bridge Destination in the Oracle WebLogic Remote Console Online Help, do the following for both the source and target destinations:

  • In the Adapter JNDI Name field, identify the transaction adapter's JNDI name, eis.jms.WLSConnectionFactoryJNDIXA.

  • Do not enter anything in the Adapter Classpath field.

• Select a Quality Of Service of Exactly-once.

  See Create a Messaging Bridge Instance in the Oracle WebLogic Remote Console Online Help.

There are no special security configuration requirements for the bridge to interoperate between two WebLogic domains. However, if you want to provide more secure communication between domains, you can configure Cross Domain Security.