This content has been marked as final. Show 3 replies
You have to just create ClientLockManager and ServerLockManager.
Create it either from eclipse or directly in the directory /atg/dynamo/service/
Place the following properties in this dir
lockServerAddress=your host name
lockServerAddress=youe host name
The above configuration will be good if you are using production server only.
For any other server instance, you ll have to do same ways.
But it will be good if you create these properties by running CIM.
Well depends if you are going to setup other instances to play the role of lock manager.1 person found this helpful
Basically to turn any instance into a lock manger:
atg/dynamo/Initial.properties to turn this instance into Lockmanager at startup.
Then for store/production instances you just need
lockServerAddress=localhost (or server hostname where the lock manager is located)
ClientLockManager_production.properties is only needed for publishing application or other applications that communicate with other clusters. The production, or staging is usually to provide publishing each cluster's lock manager information for file and repository asset deployment purposes.
Usually if you only have 1 instances running you point to itself for lock management. If you have cluster - you should have separate instance to play the role of lock management. Each cluster group needs its own lock manager. stores/production cluster, staging instance or cluster, publishing instance or cluster.
Thanks Gurvinder, Jklarsen.
I've created ATG servers with CIM, able to assemble my modules with the help of atg servers.