Configuration & Logging

Configuration Location in Docker

The relative path to the configurations in Docker is /usr/share/tomcat/conf/unidata.

The directory contains:

  • System parameters (“System Parameters” section on UI).

  • templates. Directory of the email templates.

  • community/enterprise-pipelines.json. Pipelines.

  • logback.xml. Logging options.

Backend Configuration

Unidata uses a single configuration file called (name predefined).

You can see an actual example in the CE project

If you install Unidata manually, the location of the file can be specified through the JVM flags -Dunidata.conf="<path>/unidata-conf"

Frontend Configuration

Use the customer.json file to configure the user interface settings. It will appear as path: /usr/share/nginx/html/customer.json when you start the application in docker. If you change the file in the container, you may lose the configuration after the next restart.

To store changes:

  • If you run the application from the unidata-platform-deploy repo, place the file with the changes (with a different name, for example: “my_customer.json”) in the json_configs folder, and then restart the application using docker-compose with the command:

    -f docker-compose.yml -f docker-compose-json-generate.yaml up -d
  • If you are making the UI locally, you can simply change the customer.json file before building the docker code or image (in this case, change the customer.json file in the “Build” folder).


Unidata uses slf4j and logback classic for logging.

If you install Unidata manually, you can use -Dhazelcast.logging.type=slf4j to inform Hazelcast about the logging subsystem.