Consider a single JMS module that includes a connection factory as well as queue. Based on your system's requirements, the connection factory needs to be made available to all servers in the domain. The queue, on the other hand, can be targeted to only a single JMS server domain. What is the best way to achieve the desired JMS setup?
A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, SAF agents, or a cluster).
For example, you can group a connection factory with stand-alone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.
Currently there are no comments in this discussion, be the first to comment!