As of Zoomdata version 2.6.0, configuration files can be filed under three distinct categories. These categories are property, JVM, or environment configuration files. The full list of services running on a Zoomdata instance can be found under the directory /opt/zoomdata/bin/
A service configuration in this context is defined as any application or microservice that is leveraged to perform a task or group of tasks in relation to Zoomdata. This can be (but not limited to) any of the following:
- Zoomdata itself
- An enterprise data connector
- The job scheduler
- The query engine
- The screenshot service
- The upload service
- The stream writer service
This framework enables any system architect to configure Zoomdata and its underlying services to be flexible and fit their specific business use case and technical environment needs. The descriptions/examples below illustrate how one might approach adjustments to Zoomdata property files.
Property Configuration Files
- Define configuration that alter service-level behavior such as logging options, connection timeouts, ports, discovery mechanisms, etc.
- Always defined per service with default values. The default configuration file can be found in the directory: /opt/zoomdata/conf/<service-name>.properties
- To override a property in the default file, create the file in /etc/zoomdata/<service-name>.properties and override the properties desired.
- A service restart is required for properties to take effect
A user is looking to create service-level properties for the edc-postgres service, and as a result they update the file: /etc/zoomdata/edc-postgres.properties
Some of these properties could be created as: