Uniform Distributed Destinations Weighted Distributed Destinations

9-2 Programming JMS for Oracle WebLogic Server

9.3 Creating a Distributed Destination

Distributed destinations are created by the system administrator using the Administration Console. For more information, see Configuring Distributed Destination Resources in Configuring and Managing JMS for Oracle WebLogic Server.

9.4 Types of Distributed Destinations

WebLogic Server supports two types of distributed destinations: ■ Section 9.4.1, Uniform Distributed Destinations ■ Section 9.4.2, Weighted Distributed Destinations

9.4.1 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. Oracle recommends using UDDs because you no longer need to create or designate destination members, but instead rely on WebLogic Server to uniformly create the necessary members on the JMS servers to which a UDD is targeted. This feature of UDDs provides dynamic updating of a UDD when a new member is added or a member is removed. For example, if UDD is targeted to a cluster, there is a UDD member on every JMS server in the cluster. If a new JMS server is added, a new UDD member is dynamically added to the UDD. Likewise, if a JMS server is removed, the corresponding UDD member is removed from the UDD. This allows UDDs to provide higher availability by eliminating bottlenecks caused by configuration errors. For more information, see Configuring Distributed Destination Resources in Configuring and Managing JMS for Oracle WebLogic Server.

9.4.2 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. Oracle recommends converting weighted distributed destinations to UDDs because of the administrative inflexibility when creating members that are intended to carry extra message load or have extra capacity more weight. Lack of a consistent member configuration can lead to unforeseen administrative and application problems because the weighted distributed destination can not be deployed consistently across a cluster. For more information, see Configuring Distributed Destination Resources in Configuring and Managing JMS for Oracle WebLogic Server. Note: Weighted distributed destinations are deprecated in Weblogic Server 10.3.4.0. Oracle recommends using Uniform Distributed Destinations. Using Distributed Destinations 9-3