Table of Contents
- Title and Copyright Information
- Preface
- 1 Understanding the Messaging Bridge
-
2
Designing a Messaging Bridge
- When to use a Messaging Bridge
- 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
- 3 Interoperating with Different WebLogic Server Releases or Foreign Providers
-
4
FAQs: WebLogic Messaging Bridge
- Why did the messaging bridge fail to connect to the source bridge destination?
- Why are some of my messages not being forwarded?
- Can the messaging bridge handle two-phase or global transactions between separate WebLogic Server domains or between different releases?
- 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?
- How do I enable debugging for the messaging bridge?
- Can the messaging bridge use distributed destinations as source and target destinations?
- Is there another way to monitor the messaging bridge?
- Can I use the Message Bridge in a Mixed or Dynamic Cluster?
- What are the recommendations for the bridge Distribution Policy and Migration Policy settings?