Zoomdata's architecture is enhanced to enable the deployment of Zoomdata's data connectors as standalone components running in their own process space. Each of these connectors with their own dedicated connector servers also have a corresponding property file.
Each connector now self-documents the parameters and specific information for each connector, for example
edc-postgresql.properties. For information specific to the connector you are using, navigate to
These property files can be found in the following locations:
/etc/zoomdata- for example, /etc/zoomdata/edc-elasticsearch-1.7.properties
/your_install_directory/conf- for example, /your_directory/conf/edc-oracle.properties
While each connector has different properties that are unique, you can find the common values below.
|Property Name||Default Value||Possible Value(s)||Mandatory?||Description|
|app.name||unique to each connector||alphanumeric string||yes||
Defines the name of the connector in Zoomdata environment.
|app.connection.type.name||unique to each connector||alphanumeric string||yes||Defines the name of the connection type and used for display in the Data Sources page.|
|server.port||unique to each connector||a positive integer||yes||Defines the port where the server is started; must be an available port|
|discovery.enabled||true||true, false||no||Defines whether the connector service requires Consul (a service registry app) to register in Zoomdata|
|log.file.base.name||unique to each connector||any valid file name||yes||The name of the log file for a specific connector.|
|log.zoomdata.level||INFO||TRACE, DEBUG, INFO, WARN, ERROR||no||
Sets the logging level for Zoomdata classes.
|logs.dir||$your_install_dir/logs||any valid directory path||no||Identifies the name of the directory for the log file.|
|sample.log.limit||10||a positive integer||no||Specifies the number of records to log.|
|syslog.host||localhost||any valid host||no||Identifies the syslog server host.|
|syslog.port||514||any valid port||no||Identifies the syslog server port.|
|no||Sets the syslog logging level.|
|syslog.suffix||EDC||alphanumeric string||no||Distinguishes the connector service from other types of services in the Zoomdata environment.|
|Properties for Connectors Using JDBC URL|
Sets the minimum number of idle connections in the pool. The pool attempts to ensure that
|datasource.max.idle||5||an integer||Sets the maximum number of connections that can remain idle in the pool. Excess idle connections are deleted on return to the pool.|
|datasource.max.active||100||an integer||Sets the maximum total number of idle and borrow connections that can be active at the same time. Use a negative value setting no limits.|
|datasource.max.idle.time.sec||5||an integer||The minimum amount of time a connection may sit idle in the pool before it is eligible for eviction by the idle connection evictor (if any). When this is a negative value, no connections will be evicted from the pool due to idle time alone.|
|datasource.max.wait.time.sec||20||an integer||Sets the max amount of time (in seconds) the borrowObject() method should block before throwing an exception when the pool is exhausted and getBlockWhenExhausted() is true. When less than 0, the borrowObject() method may block indefinitely.|
|datasource.eviction.time.sec||1||an integer||The number of seconds to sleep between runs of the idle connection evictor thread. When set to a negative value, no idle object evictor thread will be run.|
Sets the max time (in seconds) that a driver will wait while attempting to connect to a database after the driver is identified. A zero value means there is no limit.
Not all JDBC drivers support this property.
Was this topic helpful?