|
Most review data is stored in the database. The one exception to this is the contents of the files under review. These are stored in a directory described as the "content cache". The internal structure of the content cache is subject to change between versions of CodeCollaborator, so we do not recommend altering the contents of the content cache directly without specific instructions from SmartBear technical support. However, there are two operations on the content cache that system administrators can perform: choosing a location and archiving old content.
Choosing a Location for the Content Cache
The default location for the content cache is the collaborator-content-cache subdirectory of the install directory. In many environments, this may not be an acceptable location. Here are some things to consider when choosing a content cache location:
| • |
File permissions may not allow writing in the installation directory. |
| • |
Maintenance of network storage may be easier if backups are already in place and disk usage is monitored automatically. |
| • |
Network storage allows for warm standby CodeCollaborator servers to be available in the event of failure of the primary server. |
Configuring the Location of the Content Cache
If a determination is made that the default content cache location is unacceptable, the location can be changed in installation-directory/tomcat/conf/Catalina/localhost/ROOT.xml. Find the Parameter element with the name attribute "content-cache". The "value" attribute of this element should be the path to the content cache. Relative paths are interpreted relative to the installation directory.
If the content cache location is changed on an active server, it must be restarted before the change will take effect. If the content cache is not also copied over to the new location, users will see a message that content is missing and was probably archived by the administrator. To prevent this, it is best to shut down the server, copy the content cache to the new location, and then restart the server.
Sharing the Content Cache
Sharing the content cache between servers is not supported. The only environment where CodeCollaborator servers should be configured to use the same content cache is if one is configured as a warm backup for the primary server. A warm backup is a system that configured, but not running. It can be started in the event of primary server failure to reduce down time.
Upgrading Content Store Format
There is a new file content store format that works better with many filesystems by having a deeper directory structure, reducing the number of files in each directory. The format of the cache is determined by the cache.properties file located at the root of the content-cache directory. By default this is installation-directory/tomcat/collaborator-content-cache. This file is a Java properties file (spec). There are two configuration keys, "version" and "lazy-upgrade-from-version". The "version" key determines whether to use the new format (2), or the old format (1) for storing new data. The "lazy-upgrade-from-version" key determines whether to search for and upgrade data stored in the old format (1), or not (blank). For example, here are the values you would use to store data in the new format and automatically upgrade data in the new format when requested:
version=2
lazy-upgrade-from-version=1
To just use the new format
version=2
lazy-upgrade-from-version=
To just use the old format
version=1
lazy-upgrade-from-version=
|