| Oracle® Fusion Middleware Configuring and Managing the Messaging Bridge for Oracle WebLogic Server 11g Release 1 (10.3.4) Part Number E13741-03 |
|
|
View PDF |
| Oracle® Fusion Middleware Configuring and Managing the Messaging Bridge for Oracle WebLogic Server 11g Release 1 (10.3.4) Part Number E13741-03 |
|
|
View PDF |
The following sections provide interoperability guidelines for using the WebLogic Messaging Bridge to access JMS destinations on different releases of WebLogic Server or when accessing foreign providers:
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.
Configuring Interoperability for WebLogic Domains
Note:
When the messaging bridge is used to communicate between two domains running different releases of WebLogic Server, Oracle recommends that the messaging bridge be configured to run on the domain using the latest release of WebLogic Server.Unique naming rules apply to all WebLogic Server deployments if more than one domain is involved. Therefore, ensure that:
WebLogic Server instances and domain names are unique.
WebLogic JMS server names are unique name across domains.
If a JMS file store is being used for persistent messages, the JMS file store name must be unique across domains.
Configuring interoperability between domains depends on the 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:
"Configuring Domains for Inter-Domain Transactions" in Programming JTA for Oracle WebLogic Server
"Changing the Asynchronous Mode Enabled Attribute" in Performance and Tuning for Oracle WebLogic Server
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.
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.
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:"Configuring Security for a WebLogic Domain" in Securing Oracle WebLogic Server
"Changing the Asynchronous Mode Enabled Attribute" in Performance and Tuning for Oracle WebLogic Server
When configuring a messaging bridge involves interoperability with a third-party messaging provider, you must configure the following:
Before starting WebLogic Server:
Supply the provider's CLASSPATH in the WebLogic Server CLASSPATH.
Include the PATH of any native code required by the provider's client-side libraries in the WebLogic Server system PATH. (This variable may vary depending on your operating system.)
In the JMSBridgeDestination instance for the third-party messaging product being bridged, provide vendor-specific information in the following attributes:
Connection URL
Initial Context Factory
Connection Factory JNDI Name
Destination JNDI Name
Note:
The messaging bridge cannot provide the "Exactly-once" quality of service when the source and target bridge destinations are located on the same resource manager (that is, when the bridge is forwarding a global transaction that is using the XA resource of the resource manager). For example, when using MQ Series, it is not possible to use the same Queue Manager for the source and target bridge destinations.For more information on configuring the remaining attributes for a JMS Bridge Destination, see "Create JMS Bridge destinations" in Oracle WebLogic Server Administration Console Help.
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
