Parameter names in repository.cfg file
The parameter names in the repository.cfg file follow a hierarchical scheme. The format of parameters for services therefore follow this format:
...
| Code Block |
|---|
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 # (hash) are considered as comments and not executed.
| Code Block |
|---|
#This is a comment |
Parameter Assignment:
A value is assigned to a parameter by starting with the parameter name followed by a = (equals) and then the value.
...
| Code Block |
|---|
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.
...
| Code Block |
|---|
# A Linux path Directory=/var/coreoftia/config # A Windows path Directory=C:\\test\\repository # A UNC path Directory=\\\\10.9.8.7\\ARCHIVE |
Impact position of parameter in repository.cfg file
The position of a parameter in the repository.cfg file has NO IMPACT.
The two example configurations below result in identical configuration: The property retention.type for repository SF is "none".
Example 1:
| Code Block |
|---|
SF.template = config_all_REPO
SF.retention.type=none
config_all_REPO.retention.type=adretention |
Example 2:
| Code Block |
|---|
SF.template = config_all_REPO
config_all_REPO.retention.type=adretention
SF.retention.type=none |
There is one exception:
If the parameter names (left side of “=” character) are identically, the line appearing last will rule.