Skip Headers
Oracle® Fusion Middleware Configuring and Managing the Messaging Bridge for Oracle WebLogic Server
12c Release 1 (12.1.1)

Part Number E24375-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Interoperating with Different WebLogic Server Releases or Foreign Providers

This chapter provides interoperability guidelines for using the WebLogic Messaging Bridge to access JMS destinations on different releases of WebLogic Server or when accessing foreign providers.

This chapter includes the following sections:

Interoperating with Different WebLogic Server Releases

The following interoperability guidelines apply when using the messaging bridge to access JMS destinations on different releases of WebLogic Server and in other WebLogic Server domains.

Supported Configurations and Compatibility

For the most current information on supported configurations and compatibility between current version of WebLogic Server and previous releases, see "Supported Configurations" and "WebLogic Server Compatibility" in What's New in Oracle WebLogic Server.

Naming Guidelines for WebLogic Servers and Domains

Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. For more information, see "Integration and Multi-Domain Best Practices" in Configuring and Managing JMS for Oracle WebLogic Server.

Configuring Interoperability for WebLogic Domains

Configuring interoperability between domains depends on the QOS:

Configuring Interoperability for Exactly-once QOS

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:

  • 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 check box. See "Configure connection factory transaction parameters" in Oracle WebLogic Server Administration Console Help.

  • Deploy the transaction resource adapter, jms-xa-adp.rar, on the domain where the messaging bridge is running, as described in "Deploy resource adaptors" in Oracle WebLogic Server Administration Console Help.

  • When configuring the JMS bridge destinations, as described in "Create JMS bridge destinations" in Oracle WebLogic Server Administration Console 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, as described in "Configure messaging bridge instances" in Oracle WebLogic Server Administration Console Help.

Configuring At-least-once or At-most-once QOS

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.

Note:

Keep all the domains used by your process symmetric with respect to Cross Domain Security configuration—all domains use Cross Domain Security (or are on the appropriate exception lists) or none of the domains have Cross Domain Security configured. For more information, see:

Interoperating with Foreign Providers

When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following: