About Changing Attributes of Distributed AppLogic Objects
When you change the attributes, such as enabled or disabled or sticky load balancing, for an AppLogic object that is distributed across multiple servers, those changes replicate themselves to the servers across which that object is distributed. For information about disabling AppLogic objects or enabling sticky load balancing, see "Disabling an AppLogic Object" or "Enabling Session (Sticky) Load Balancing."
If you change an object from distributed to local on one server, each server that the object was distributed across no longer attempts to balance loads with the server for which the distribution was set to local.
For example, AppLogic object X is distributed across servers A, B, and C. At some point, you decide that you are going to run object X locally on server A, but continue to allow it to run distributed across servers B and C. When you make this change on server A, servers B and C are automatically updated so that requests for object X are no longer passed to server A from servers B and C. Instead, requests for object X made to servers B or C are passed only between those servers. All requests for object X made to server A are processed by server A.
For information about changing load balancing distributions, see "Changing the Distribution Level for an AppLogic Object."
|
Previous
