Configuration & Logging¶
Configuration files¶
Backend¶
Unidata uses single configuration file, called backend.properties
(the name is predefined). Its location can be specified via JVM flags -Dunidata.conf=”<path>/unidata-conf”:
# Versions - platform and SOAP
unidata.api.version = 5.2
unidata.platform.version = 5.2
...
org.unidata.mdm.data.datasource.validationInterval=30000
org.unidata.mdm.data.datasource.type=javax.sql.DataSource
You can see actual example in the project
Frontend¶
To configure UI parameters use customer.json
file. It will be shown as a path: /usr/share/nginx/html/customer.json
when running the app in docker.
If you change the file in container, then you could lose the configuration after the next restart.
For configuration some parameters on UI you should use customer.json
file. In running app in docker it placed by this path: /usr/share/nginx/html/customer.json
If you change file in container, after next restart your configuration will be lost.
For store you changes:
If you start the app with unidata-platform-deploy repo, put the file with changes (with different name, e.g.: “my_customer.json”) in to
json_configs
folder, and then rerun the app with docker-compose with command:-f docker-compose.yml -f docker-compose-json-generate.yaml up -d
If you make UI locally, you can just change the
customer.json
file before a code or docker image building (in this case, change thecustomer.json
file in a folder “Build”).
Logs¶
Unidata uses slf4j and logback classic for logging. Thus, logback settings can be supplied via -Dlogback.configurationFile="<path>/logback.xml"
.
To give Hazelcast a hint about the logging subsystem -Dhazelcast.logging.type=slf4j
can be used.