If excessive lock contention causes the lock server to become a bottleneck, you can distribute the load by instantiating multiple server lock managers to handle competing lock requests. For example, the following diagram shows a site with the following setup:

In a distributed application where the same repository—for example, the ProfileAdapterRepository–runs on multiple Oracle ATG Web Commerce instances, all repository instances must use the same ServerLockManager component. In the previous diagram, two instances of repository A run on separate Oracle ATG Web Commerce instances. Thus, their client lock managers must be set up to use the same server lock manager.