Cache server configuration settings and serviceability

Learn more about the cache server configuration settings and serviceability.

Client-side configuration settings

On the client side, in the ccm.properties file, you can configure these parameters:
  • ccm.cache.temp.dir

    This directory is on the client machine where static files are temporarily copied before they are copied to the cache server. If no value is specified, the default directory is the system temp directory. The static files are deleted from this directory after they are copied to the cache server.

    Note:

    When active Rational® Synergy client processes are running, do not manipulate or delete the files that are created under this directory.

  • ccm.cache.server.reconnect.delay

    If the cache server goes down after a client session is started, the client tries to connect to the cache server after a specified time delay. The time delay is in minutes, and the default value is 3 minutes.

Cache server-side configuration settings

On the cache server, in the ccm.cache.server.properties file, you can configure these parameters:
  • ccm.cache.repository.path

    This path is where the cache repository is maintained. The default location is C:/Repository.

    The location cannot be set to UAC protected folders (Program Files or Windows System folders) on User Access Control enabled Windows operating systems.

  • ccm.cache.size.limit

    The size of the cache that is permitted on the cache server. The value is treated as number of megabytes and must be a positive integer. Any other value indicates that there is no cache size limit.

  • ccm.cache.size.limit.report

    The type of message that is reported on the cache server when the repository size crosses the size limit that is set. These messages are reported in the cacheserver_host_port_cachesize_usage.log file in the CACHESERVER_HOME/log directory. The acceptable values for this property are WARNING or ERROR. The default value is WARNING. When the value is set to WARNING, the system displays a warning message and continues caching the files. If the value is set to ERROR, the system reports an error message and stops copying files to cache server repository.

  • ccm.cache.size.monitor.timer

    This value is the time interval that is required to recalculate the cache server repository size. The value is in minutes, and the default value is 180 minutes.

Other Rational Synergy server-side configuration settings

In addition to the cache server location to the URL mappings, you can set these configuration parameters on the Rational Synergy server side:
  • ccm.cache.server.disable

    To disable the cache server for all of the client locations, in the ccm.server.properties file, on the Rational Synergy main server run area, set the ccm.cache.server.disable property to TRUE.

  • ccm.cache.server.filesize.threshold

    The minimum file size determines whether the file is served from the Rational Synergy CCM server or from the cache server. If the size of the file is greater then the value of the ccm.cache.server.filesize.threshold property, then the file is cached and served from the cache server. The value is in bytes. If no value is specified, all of the files of all sizes are cached. Define the ccm.cache.server.filesize.threshold property in the ccm.svm.properties file on the Rational Synergy main server run area.

Serviceability

You can switch the logging on the client and the cache server to obtain details of the activities that occur between the client and the cache server when the cache server is enabled.

When a client is configured to use a cache server and it successfully establishes a connection with the cache server, this message is logged in the ccm_client.log file:
2013-06-17T11:39:29.687+0530 INFO   : Client location name - BANGALORE (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}
2013-06-17T11:39:29.703+0530 INFO   : Initializing cache server services... (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}
2013-06-17T11:39:30.265+0530 INFO   : ClientCache services is registered for 'indmaga in \\9.184.164.220\ccmdb\trainingdb from machine 9.124.23.79 at time 1371449367671' (Thread=1)
{cacheservice.client}
If the client is configured to use a cache server but fails to establish a connection with the cache server, this message is logged in the ccm_client.log file:
2013-06-17T11:42:28.671+0530 INFO   : Client location name - BANGALORE (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}
2013-06-17T11:42:28.687+0530 INFO   : Initializing cache server services... (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}
2013-06-17T11:42:30.015+0530 WARNING: Initialization of Client Cache failed .... (Thread=1)
{cacheservice.client}
2013-06-17T11:42:30.015+0530 WARNING: Client Caching is disabled for this client (Thread=1)
{cacheservice.client}
If the client is not configured to use any cache server, this message is logged in the ccm_client.log file:
2013-06-17T11:48:49.437+0530 INFO   : Client location name - null (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}
2013-06-17T11:48:49.437+0530 INFO   : Client location name is empty, so no cache server will be used for this session. (Thread=1)
{internal.objectapi.longcall.AccentCallbackManager}

To obtain detailed information about the file transfers that occur between the client and the cache server, enable logging on the client and cache server. On the client side, add this entry to the logging.properties file in the CCM_HOME/etc directory.

com.telelogic.cm.cacheservice.level = FINEST

If you require more details, add these lines:

com.telelogic.cm.cvm.level = FINEST

com.telelogic.cm.vm_util.level = FINEST

On the cache server side, to enable logging, change the log level from CONFIG to FINEST in the logging.properties file in the CCM_HOME/etc directory:

com.telelogic.level = FINEST


Feedback