Configuring Locked Caching for ATG Knowledge and ATG Self Service

When using both ATG Knowledge and ATG Self Service, you need to configure locked caching in both of your clusters so that all servers stay up-to-date with user profile and ticketing information. Normally you would share lock managers only within a single cluster, but in this case locking must occur across all clusters. Refer to the ATG Service Installation and Configuration Guide for a detailed description of configuring Lock Caching.

Upgrading the Configuration

If you already have a ServerLockManager instance running for the ATG Knowledge cluster, perform the following steps:

  1. Configure the ATG Knowledge, or agent-facing server’s ClientLockManager to use the existing ServerLockManager instance.

  2. Remove the preInitial.properties for ATG Knowledge.

  3. Perform the above steps for ATG the Self Service server, or the customer-facing server , if it has been configured similarly. Start an instance for the ServerLockManager_shared on the customer-facing cluster.

  4. Override the default ClientLockManager and ClientLockManager_production on both of the server’s localconfig to point to the correct lockManagerAddress and port. Optionally, remove any preInitial.properties files in the ZIP files and edit the ClientLockManager.properties files to setup your lock managers.

    For additional information on configuration of lock managers, refer to Locked Caching in the ATG Repository Guide.

 
loading table of contents...