Configuring the Lock Manager

Configure server and client lock managers between your servers. The lock manager is used for locked caching mode (see the Locked Caching section of the ATG Repository Guide).

Both Search Administration and Oracle ATG Web Knowledge Manager automatically point their SearchClientLockManager components to the ClientLockManager_production component; SearchClientLockManager requires no further configuration. If you are using other Oracle ATG Web Commerce applications with Search, you may need to perform this configuration manually. You must also configure the following components:

  • /atg/dynamo/service/ClientLockManager component on the production server

  • /atg/dynamo/service/ClientLockManager_production component on the asset management server

  • /atg/dynamo/service/ClientLockManager_production component on the staging server (if using one)

In each of those components, perform the following configuration:

useLockServer=true
lockServerPort=production_server_port
lockServerAddress=production_host_name_or_IP

The address and port specified for this component on the asset management and staging servers must match that of the ClientLockManager on the production instance.