Configure Server and Client lock managers between your servers. The lock manager is used when you have multiple repositories referring to the same database and want to ensure that the repositories remain in sync. For example, the Search routing repository is used by all Search clients within a system. Therefore, all of the servers on which those Search clients run need to have a Client Lock Manager set up to look at the same Server Lock Manager.
Both Search Administration and Knowledge automatically point their SearchClientLockManager components to the ClientLockManager_production component; SearchClientLockManager requires no further configuration. If you are using other ATG applications with Search, you may need to perform this configuration manually. You must also configure the following components:
ClientLockManagercomponent on the production serverClientLockManager_productioncomponent on the Knowledge and Search Administration servers
In both of those components, perform the following configuration:
Set
useLockServer=trueSet the
lockServerAddressandlockServerPortproperties to point to thelockServerAddressandlockServerPortproperties of theClientLockManagercomponent on the production server
See also the Locked Caching section of the ATG Repository Guide.
