ClientLockManager Component

If an SQL repository contains item descriptors that use locked caching, set the Repository component’s lockManager property to a component of type atg.service.lockmanager.ClientLockManager. The Oracle Commerce Platform provides a default ClientLockManager component:

/atg/dynamo/service/ClientLockManager

Thus, you can set an SQL Repository’s lockManager property as follows:

lockManager=/atg/dynamo/service/ClientLockManager

ClientLockManager Properties

A ClientLockManager component must be configured as follows:

Property

Setting

useLockServer

true enables this component to connect to a ServerLockManager

lockServerAddress

Host address of the ServerLockManager and, if set, the backup ServerLockManager

lockServerPort

The ports used on the ServerLockManager hosts, listed in the same order as in lockServerAddress

For example, given two ServerLockManagers on hosts tartini.acme-widgets.com and corelli.acme-widgets.com, where both use port 9010, the ClientLockManager is configured as follows:

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

Note: The liveconfig configuration layer always sets useLockServer to true.

Copyright © 1997, 2019 Oracle and/or its affiliates. All rights reserved. Legal Notices