If you are using a SQL Repository with locked mode caching, you must enable the ClientLockManager (/atg/dynamo/service/ClientLockManager) on each Oracle Commerce Platform server and enable the ServerLockManager (/atg/dynamo/service/ServerLockManager) on one or more Oracle Commerce Platform servers. You may want to dedicate an Oracle Commerce Platform server only to lock management. Note that elements of the Oracle Commerce Platform are configured in the liveconfig layer to use locked mode caching by default.
Add the ServerLockManager component to the initialServices property of the /atg/dynamo/Initial component, and make sure that the ClientLockManager points to the correct host. The ClientLockManager should be configured like this:
Property | Description |
|---|---|
| The hostname of the machine running the |
| The port configured in the |
| True |
The ClientLockManager is enabled by the liveconfig configuration layer. For more information about cache lock managers, see the Repository Guide.
