This script outputs the google search URL required for search on edocs documentation.
This script outputs the banner required for edocs documentation.
This script outputs the google search parameters required for search on edocs documentation.
This script outputs the product breadcrumb required for edocs documentation.
>
Configuring and Managing the WebLogic Messaging Bridge
Configuring and Managing the WebLogic Messaging Bridge
Introduction and Roadmap
Document Scope and Audience
Guide to This Document
Related Documentation
Samples and Tutorials for the JMS Developer
Avitek Medical Records Application (MedRec) and Tutorials
JMS Examples in the WebLogic Server Distribution
Additional JMS Examples Available for Download
New and Changed Message Bridge Features in This Release
Deprecation of Messaging Bridge Adapter for WLS 5.1
Understanding the Messaging Bridge
What Is a Messaging Bridge?
Messaging Bridge Components
Resource Adapters
Source and Target Bridge Destinations
Messaging Bridge Instance
Configuring and Managing a Messaging Bridge
Create a Messaging Bridge Instance
Manage a Messaging Bridge Instance
Designing a Messaging Bridge
When to use a Messaging Bridge
Store and Forward Messaging
Replicating a Topic
When to Avoid using a Messaging Bridge
Selecting a Quality-of-Service (QOS) Level
Messaging Persistence
Message Ordering
Setting the Number of Connection Factories
Preserving Message Properties
Using the JMSXUserID Property with a Messaging Bridge
Using Distributed Destinations as Source and Target Destinations
Tuning a WebLogic Messaging Bridge
Interoperating with Different WebLogic Server Releases or Foreign Providers
Interoperating with Different WebLogic Server Releases
Naming Guidelines for WebLogic Servers and Domains
Configuring Interoperability for WebLogic Domains
Access Destinations In a Release 6.1 or Later Domain
Interoperating with Foreign Providers
FAQs: WebLogic Messaging Bridge
Why did the messaging bridge fail to connect to the source bridge destination?
Can the messaging bridge handle two-phase or global transactions between separate WebLogic Server domains or between different releases?
I configured the messaging bridge to use the Exactly-once quality of service for two-phase transactions. So why am I getting a "quality of service is unreachable" error?
Can a messaging bridge to automatically downgrade the quality of service if the Exactly-once service isn't available on either the source or target bridge destination?
I deployed the transactional jms-xa-adp.rar resource adapter on domain where the message bridge is running, but I still get a "failed to find bridge adapter" message?
When configuring a source or target messaging bridge destination, do I need to set the Adapter Classpath field?
Can the messaging bridge forward durable subscription messages between separate WebLogic Server 6.1 and 7.0 or later domains?
How do I enable debugging for the messaging bridge?
What do the messaging bridge monitoring states indicate on the Monitor Messaging Bridge console page?
Is there another way to monitor the messaging bridge without using the Administration Console?
Can the messaging bridge use distributed destinations as source and target destinations?
© BEA Systems
