daemon.properties file | Teradata Data Mover - 17.11 - The daemon.properties File - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-4102-091K
Language
English (United States)
Property Description Default Value
broker.port=port The port number of the machine where the Java Message Service (JMS) message broker is listening. 61616
broker.url=url The hostname or IP address of the machine running the Java Message Service (JMS) message broker. localhost
cluster.enabled=setting for cluster When set to True, establishes a connection to a standby Java Message Service (JMS) broker in case the active JMS broker fails. False
viewpoint.url The hostname or IP address for the Viewpoint Authentication server.

Example: viewpoint.url=https://localhost

https://localhost
viewpoint.port The port number for the Viewpoint Authentication server.

Example: viewpoint.port=443

443
tvi.useLogger=setting for TVI messages The Server Management logger can be set to true or false. If set to true, fatal error messages are sent to Server Management. Dynamic property.1 True
jobExecutionCoordinator.maxConcurrentJobs=maximum number of jobs The maximum number of jobs allowed to run on the daemon at the same time. Additional jobs are placed on the queue and run when slots become available. Dynamic property. 1 20
jobExecutionCoordinator.maxQueuedJobs=maximum number of jobs allowed in queue The maximum number of jobs allowed in the job queue. Additional jobs are placed in a higher level memory queue until slots are available in the job queue. Dynamic property. 1 20
querygrid.manager.urls=url The hostname and IP address for the QueryGrid Manager servers. Supports up to two URLs, separated by commas.

Example: querygrid.manager.urls=https://host1:9443,https://host2:9443

9443
rootLogger.level The six levels of logging, TRACE | DEBUG | INFO | WARN | ERROR | FATAL. From trace level to application error. LOG_LEVEL can be updated dynamically, but not logfile.1 INFO
appender.rolling.type The six levels of logging, TRACE | DEBUG | INFO | WARN | ERROR | FATAL. From trace level to application error. LOG_LEVEL can be updated dynamically. RollingFile
appender.rolling.name Do not edit. This is an internal setting for logging infrastructure. RollingFile
appender.rolling.layout.type Do not edit. This is an internal setting for logging infrastructure. PatternLayout
appender.rolling.layout.pattern Do not edit. This is an internal setting for logging infrastructure.
  • d = date
  • t = thread
  • p = log level
  • c = class name
  • m = message
  • n = platform dependent line separator
%d [%t] %-5p %c{3}(%L) - %m%ns
appender.rolling.policies.type Do not edit. This is an internal setting for logging infrastructure. Policies
appender.rolling.policies.size.type Do not edit. This is an internal setting for logging infrastructure. SizeBasedTriggeringPolicy
appender.rolling.strategy.type Do not edit. This is an internal setting for logging infrastructure. DefaultRolloverStrategy
logger.rolling.name Do not edit. This is an internal setting for logging infrastructure. com.teradata.datamovement.daemon
logger.rolling.appenderRef.rolling.ref Do not edit. This is an internal setting for logging infrastructure. RollingFile
appender.rolling.fileName The relative or absolute path of the log file. If changing the location, specify the absolute path of the file. For Windows, specify back slash instead of forward slash, for example, C:\Program File\Teradata\Log\dmDaemon.log. Dynamic property.1 /var/opt/teradata/datamover/logs/dmDaemon.log
appender.rolling.filePattern

Specifies logfiles pattern.

Example: dmDaemon.log.%i saves the files as dmDaemon.log.1, dmDaemon.log.2, dmDaemon.log.3, and so on.

/var/opt/teradata/datamover/logs/dmDaemon.log.%i
appender.rolling.policies.size.size The maximum size of the logging file before being rolled over to backup files. Dynamic property.1 20MB
appender.rolling.strategy.max

The number of backup logging files that are created. After the maximum number of files have been created, the oldest file is deleted. Dynamic property.1

Example: If maximum backups = 3, three backup logs are created:
  • dmDaemon.log.1
  • dmDaemon.log.2
  • dmDaemon.log.3

If the current dmDaemon.log size exceeds 20MB, it rolls to become the new dmDaemon.log.1 and a new dmDaemon.log is created. The previous dmDaemon.log.2 becomes the new dmDaemon.log.3. The previous dmDaemon.log.3 is deleted.

5
dm.rest.endpoint This is a hidden property used only by DSA. The Data Mover REST URL used by the daemon for the DSA utility.

You can override the default value by adding the same named property in the daemon.properties file.

Before modifying the localhost, verify the new host is listed in the accept.host.list property in tdmrest.properties file.

http://localhost:1443/datamover
dsa.rest.endpoint This is a hidden property used only by DSA. The DSA REST URL used by the daemon for the DSA utility.

You can override the default value by adding the same named property in the daemon.properties file.

http://localhost:9090/dsa
is.dsc.colocate.dm This is a hidden property used only by DSA. Flag indicating if Data Mover is using the bundled DSC.

You can override the default value by adding the same named property in the daemon.properties file.

true

If the Viewpoint Authentication server does not have HTTPS enabled, you can set the following if you want to authenticate through HTTP instead: viewpoint.url to http://localhost and viewpoint.port to 80.

1For properties that can be set dynamically, the changes take effect one minute after the updated daemon.properties file is saved. There is no need to restart the daemon service if you are only updating dynamic properties. For example:
  • If you changed the value of rootLogger.level from the default of INFO, logfile to DEBUG, logfile, any debug messages generated would start appearing in the log file one minute after saving the updated properties file.
  • If you changed the value of jobExecutionCoordinator.maxConcurrentJobs from the default value of 20 to a new value of 25, the new value of 25 takes effect one minute after saving the updated daemon.properties file.