Syntax rules for repository.cfg file

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:

<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 # (hash) are considered as comments 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 = (equals) and then the value.

Space characters are ignored, so that these two example lines have identical effect.

 

Path to directory or file:

The / (slash) is not a special character and can be used unescaped. This allows Linux paths and also Windows path to be written in to the configuration file as is.

The \ (backslash), however, needs to be escaped as it is interpreted as escape character. So when using Windows paths in the configuration file with backslash, it must be escaped to \\ (double backslash).

Note: In container deployment, Windows path with drive letters or backslashes are not allowed.

Examples:

 

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:

Example 2:

There is one exception:

If the parameter names (left side of “=” character) are identically, the line appearing last will rule.