agents.properties file | Teradata Data Mover - 17.05 - The agent.properties File - Teradata Data Mover

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

prodname
Teradata Data Mover
vrm_release
17.05
created_date
October 2020
category
Administration
Configuration
Installation
featnum
B035-4102-090K
Property Description Default Value
agent.id=id Unique identifier for this agent. Agent1
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
broker.port=port number 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
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. Polices
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.agent
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\dmAgent.log. Dynamic property.1 /var/opt/teradata/datamover/logs/dmAgent.log
appender.rolling.filePattern

Specifies logfiles pattern.

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

/var/opt/teradata/datamover/logs/dmAgent.log.%i
appender.rolling.policies.size.size The maximum size of the logging file before being rolled over to backup files. Dynamic property.1 10MB
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:
  • dmAgent.log.1
  • dmAgent.log.2
  • dmAgent.log.3

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

3
agent.maxConcurrentTasks=maximum number of tasks The maximum number of tasks allowed to run on this agent at the same time.

Note that tasks are distributed to agents using a round robin method. Task size is not currently considered, so load may not be balanced if one agent is randomly assigned larger tasks than another.

5
tvi.useLogger=setting for TVI messages The TVI logger can be set to true or false. If set to true, fatal error messages are sent to TVI. Dynamic property. 1 True
1 For 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 agent.maxConcurrentTasks from the default value of 5 to a new value of 6, the new value of 6 would take effect one minute after saving the updated agent.properties file.