The legacy weighted distributed topic feature is for users who prefer to manually create topic members to carry extra message load or have extra capacity. However, Oracle strongly recommends configuring uniform distributed topics to avoid possible administrative and application problems due to a weighted distributed topic not being deployed consistently across a cluster. For more information on creating a uniform distributed topic, see Create uniform distributed topics in a system module.
To create a weighted distributed topic:
Once you create a uniform distributed topic, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
If you do not specify a JNDI name for the distributed topic,
it will not be available for JNDI lookup even after it has been
targeted to a server resource. Therefore, you will only be able
to access the distributed topic using the
javax.jms.topicSession.createtopic() API or in
an application-scoped context.
The new weighted distributed topic is added to the module's Summary of Resources table.
After you finish
To configure the load balance weighting of the member topics, see Weighted distributed topics - configure member weights.