A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical destination to a client. A distributed destination has the following characteristics:
Applications that use distributed destinations are more highly available than applications that use simple destinations because WebLogic JMS provides load balancing and failover for member destinations of a distributed destination within a cluster. Once properly configured, your producers and consumers are able to send and receive messages through the distributed destination. WebLogic JMS then balances the messaging load across all available members of the distributed destination. When one member becomes unavailable due a server failure, traffic is then redirected toward other available destination members in the set.
Types of Distributed Destinations
WebLogic Server supports two types of distributed destinations:
Uniform Distributed Destinations
In a uniform distributed destination (UDD), each of the member destinations has a consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas.
Weighted Distributed Destinations
In a weighted distributed destination, the member destinations do not have a consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas.
To configure JMS On Web Logic Cluster, following steps need to be involved.
- Create Persistent Store (Creating a JDBC Store)
- Weblogic 10.3.5: Configure JMS Servers on Weblogic Cluster
- Weblogic 10.3.5: Configure JMS Modules on Weblogic Cluster
- Weblogic 10.3.5: Configure uniform distributed queues on Weblogic Cluster
- Weblogic 10.3.5: Create connection factories in a system module on Weblogic Cluster
