CIM allows you to configure dedicated lock manager servers during the installation process.

Lock servers synchronize caches among ATG servers to maintain data integrity, even if an item is modified at the same time by different servers. CIM configures the ClientLockManager.properties and the ServerLockManager.properties files to ensure all servers are using the correct ports. For additional information on ClientLockManager and ServerLockManager properties, refer to the SQL Repository Caching section in the ATG Repository Guide.

CIM locates the default client lock manager to LockManager=/atg/dynamo/
service/ClientLockManager. By default, the ClientLockManager component has its useLockServer property set to false, which disables the lock server. To use locked mode repository caching, this property must be set to true. For example:

$class=atg.service.lockmanager.ClientLockManager
lockServerAddress=tartini,corelli
lockServerPort=9010,9010
useLockServer=true

ServerLockManager on the Customer-Facing Server

The customer-facing server cluster defines a primary ServerLockManager instance. Additionally, there is a defined ClientLockManager, which points to the primary ServerLockManager.

You can configure backup ServerLockManager instances for redundancy if needed. The following diagram shows a typical customer-facing configuration with three commerce servers that have ClientLockManagers that each point to the primary ServerLockManager:

Customer-Facing Lock Management

ClientLockManagers on the Agent-Facing Server

Agent-facing servers use the customer-facing server lock manager for any shared repositories, and individually scheduled services.

The agent-facing clusters define a ClientLockManager_production, which points to the ServerLockManager used by the customer-facing server. The following diagram displays both the customer-facing server described above and the agent-facing server configuration. The agent-facing configuration displays the two Service Center instances that each contain a ClientLockManager_production that points to the ServerLockManager used by the three customer-facing commerce servers. The two Service Center instances contain their own ClientLockManagers that each point to the agent-facing ServerLockManager:

Customer and Agent-Facing Lock Management