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 folder described as the content storage or content cache.
The default location for the content storage is: <Collaborator Server>/tomcat/collaborator-content-cache
|The internal structure of the content storage is subject to change between versions of Collaborator, so we do not recommend altering the contents of the content storage directly without specific instructions from SmartBear technical support.|
In some environments, the default content storage location could not be an acceptable solution. In this case you can change it.
Below are some things to consider when choosing a content storage location:
File permissions may not allow writing in the installation folder.
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 Collaborator servers to be available in the event of failure of the primary server.
To change content storage location:
Parameterelement with the
valueattribute of this element. Relative paths in this attribute are interpreted relative to the server installation folder.
Over time, content storage will grow to be quite large, and will periodically need to be purged. The Archive section of the administrator interface allows you to check the current status of the content cache and to archive (or delete) files that have not been in use for a long time.
Starting from version 6, Collaborator has a new file content storage format that works better with many file systems by having a deeper folder structure, reducing the number of files in each folder. By default all new installations of Collaborator server use the new file content storage format.
To upgrade the content storage format of existing installations of legacy (CodeCollaborator 5 and earlier) servers:
Edit it as follows:
The cache.properties file is a Java properties file having two configuration keys,
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).