...
Repository-wide settings are configured for each repository separately in the repository.cfg file.
...
There are a few global configuration parameters in this file while most configuration is for each repository separately. For these, the parameter names always starts with the repository name.
For more details on parameters names see Syntax rules for 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:
| Code Block |
|---|
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=fileconfigDirectory=configconfigFile=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:
| Code Block |
|---|
<repository>.<service>.[etc] |
For example:
| 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 # are considered a comment 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 = character and then the value.
Space characters are ignored, so that these two example lines have identical effect.
| Code Block |
|---|
name=Stephen |
| Code Block |
|---|
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:
| Code Block |
|---|
# A Linux path
Directory=/var/coreoftia/config
# A Windows path
Directory=C:\\test\\repository |
.
Parameters for repositories relate to a service. These parameters are documented here Services (tC) .
Global parameters in the repository.cfg file
Repository list
The parameter repositoryfactory.repositorylist contains a list of all repository names.
Example:
| Code Block |
|---|
repositoryfactory.repositorylist = repo001,repo002,repo003,repo004,repo005 |
Note: When activating Multi-Tenant-Support, the repository names include the tenant name they are linked to. See Multitenancy .
Repository Description
With the description parameter you can give the repository a description that is visible in the status webapp.
| Code Block |
|---|
<repo>.description=Invoices |
see tia® Status User-Interface
Configuration templates
The parameter repositoryfactory.templatelist can be used to provide a list of template configurations for repositories.
Example:
| Code Block |
|---|
repositoryfactory.templatelist = FI_REPOS, MM_REPOS |
Then using the template name, parameters can be configured for it:
Example:
| Code Block |
|---|
#===== S3-minio content service configuration (filesystem|azureblobstore|s3blobstore|kgsstore)
FI_REPOS.contentservice.s3blobstore.connectionuser=<user>
FI_REPOS.contentservice.s3blobstore.connectionpass=<password>
FI_REPOS.contentservice.s3blobstore.maxconnections=
FI_REPOS.contentservice.s3blobstore.endpoint=127.0.0.1:9000
FI_REPOS.contentservice.s3blobstore.protocol=http
FI_REPOS.contentservice.s3blobstore.bucketname=shared.bucket
FI_REPOS.contentservice.s3blobstore.contrepinpath = true
FI_REPOS.configdata.filesystem.root=C:\\tia\\config |
By the repository parameter <repository name>.template, these template can be configured for a specific repository.
Example:
| Code Block |
|---|
FI.template = FI_REPOS
AB.template = FI_REPOS |
Parameters from template can be overwritten by specifying the parameter for the repository explicitly.
Example:
The S3 bucket should be set for each repository separately, so both do not write into the same bucket.
| Code Block |
|---|
FI.contentservice.s3blobstore.bucketname=fi.bucket
AB.contentservice.s3blobstore.bucketname=ab.bucket |