3 Replies Latest reply: Mar 1, 2012 2:53 AM by D.N.R RSS

    Normal ATG Application -- ATG Lock Server

    D.N.R
      Hi All,

      I've created a normal ATG application with the help of eclipse. Now I'm going to create a lock server for this application.

      How can I do this through eclipse. and How my atg application points to lock server if I create?

      Please help me.


      Thanks,
      Kushal.
        • 1. Re: Normal ATG Application -- ATG Lock Server
          Gurvinder
          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

          ClientLockManager.properties
          lockServerAddress=your host name
          lockServerPort=9010
          useLockServer=true

          ClientLockManager_production.properties
          lockServerAddress=youe host name
          lockServerPort=9010
          useLockServer=true


          ServerLockManager.properties
          port=9010


          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.

          Thanks
          • 2. Re: Normal ATG Application -- ATG Lock Server
            898142
            Well depends if you are going to setup other instances to play the role of lock manager.

            Basically to turn any instance into a lock manger:

            atg/dynamo/Initial.properties to turn this instance into Lockmanager at startup.
            contents: initialServices+=/atg/dynamo/service/ServerLockManager

            atg/dynamo/service/ServerLockManager.properties
            contents: port=9010

            Then for store/production instances you just need
            atg/dynamo/service/ClientLockManager.properties
            contents:
            lockServerPort=9010
            useLockServer=true
            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.

            -Kip
            • 3. Re: Normal ATG Application -- ATG Lock Server
              D.N.R
              Thanks Gurvinder, Jklarsen.

              I've created ATG servers with CIM, able to assemble my modules with the help of atg servers.

              Thanks,
              Kushal.