...
Environmental variables: This method is useful for containerized deployments as environmental variables can be defined in the container configuration.
In
context.xmlfile: This is useful for a war-file deployment in a web application server. This file can be found (or if not create it) in the<webappserver>/WEB-INF/<web context>/META-INFdirectory.
The parameter names are written in lowercase strings and reflect the hierarchy of application modules. For that reason, the “.” (dot character) is used to separate the levels in the hierarchy.
| Info |
|---|
Note: When using environmental variables, the parameter names will need to be converted to all-uppercase and the usage of dot is not permitted. Hence replace all the “.” (dot characters) by “_” (underscore characters). |
Repository-wide settings
Repository-wide settings are configured for each repository separately in the repository.cfg file, which resides in the configuration directory with path.
The file resides in containerized deployments /application/config/repository.cfg. It i 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 parameter names in the repository.cfg file follow a hierarchical scheme. The format of parameters for services therefore follow this format:
...