Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Configure connection factory load balancing parameters

After you configure a connection factory, you can define load balancing parameters so that when multiple clients use this connection factory, they can choose how to distribute their work to targeted server instances.

Note: The Server Affinity Enabled attribute does not affect queue browsers. Therefore, a queue browser created on a distributed queue can be pinned to a remote distributed queue member even when server affinity is enabled.

To configure load balancing parameters on a connection factory:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, navigate to the connection factory resource that you want to configure:
   - Navigate to JMS Resources in System Modules
   - Navigate to JMS resources in an application module
3. Click the Configuration > Load Balance tab.
4. On the Load Balance page:
   1. In Server Affinity Enabled, specify whether non-anonymous producers sending to a distributed destination are load balanced on a per-send basis. When server affinity is turned off, then a server instance will load balance consumers or producers across member destinations in a distributed destination and disregard any other physical destinations also running on the same server instance.
   2. In Load Balancing Enabled, specify whether a server instance that is load balancing consumers or producers across multiple member destinations in a distributed destination will first attempt to load balance across any other physical destinations that are also running on the same instance. You can turn off load balancing if you have applications that use distributed destinations to distribute or balance their producers and consumers across multiple physical destinations, but do not want WebLogic Server to make a load balancing decision each time a message is produced.

   For more information about these fields, see Configuration Options.

5. Save your changes:
   - Save Changes to JMS Resources in System Modules
   - Save changes to JMS resources in an application module
6. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
   Not all changes take effect immediately—some require a restart (see Use the Change Center).