Properties File | Command-Line Interface | Teradata Data Mover - The commandline.properties File - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
17.05
Published
October 2020
Language
English (United States)
Last Update
2020-11-18
dita:mapPath
iak1591023586907.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
B035-4102
lifecycle
previous
Product Category
Analytical Ecosystem
Property Description Default Value
dm.rest.endpoint The Data Mover REST server URL. When automatic failover support is configured, use a comma separated list to add the standby REST server URL.

Example: dm.rest.endpoint=https://activeServer:1443/datamover,https://standbyServer:1443/datamover

Make sure the host:port value used for dm.rest.endpoint is on the accept.host.list in tdmrest.properties.

https://localhost:1443/datamover
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. com.teradata.datamovement.commandline
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.  
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\dmCommandLine.log. Dynamic property.1 dmCommandLine.log
appender.rolling.filePattern

Specifies logfiles pattern.

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

dmCommandLine.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:
  • dmCommandLine.log.1
  • dmCommandLine.log.2
  • dmCommandLine.log.3

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

3