Repository-wide settings are configured for each repository separately in the repository.cfg
file.
Location of the repository.cfg file
By default,
the file resides in containerized deployments
/application/config/repository.cfg
. It is best practice to use a volume mount in the container configuration:
docker [..] -v <Folder>/repository.cfg:/application/config/repository.cfg [..]
For war deployments, find the repository.cfg here:
<web server installation>/webapps/<context>/conf
.
The location of the repository.cfg
file can be modified by editing these application-wide settings (here with the default values):
configservice.class=file
configDirectory=config
configFile=repository.cfg
Parameter names
The parameter names in the repository.cfg
file follow a hierarchical scheme. The format of parameters for services therefore follow this format:
<repository>.<service>.[etc]
For example:
ZQ.contentservice.proxy.primary.type
Syntax rules for repository.cfg file
This file is a Java property file. This explains the syntax rules all entries must comply with.
Comment:
All rows starting with #
are considered a comment and not executed.
#This is a comment
Parameter Assignment:
A value is assigned to a parameter by starting with the parameter name followed by a =
character and then the value.
Space characters are ignored, so that these two example lines have identical effect.
name=Stephen
name = Stephen
Path to directory or file:
The /
(slash) is not a special character and can be used unescaped. This allows Linux paths to be written in to the configuration file as is.
The \
(backslash), however, needs to be escaped as it interpreted as escape character. So to use Windows paths in the configuration file, \\
(two backslash characters) needs to be used for each backslash in Windows path.
Examples:
# A Linux path Directory=/var/coreoftia/config # A Windows path Directory=C:\\test\\repository # An UNC path Directory=\\\\10.9.8.7\\ARCHIVE