Properties File | Command-Line Interface | Teradata Data Mover - Properties File for the Command-Line Interface - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Published
October 2021
Language
English (United States)
Last Update
2021-10-14
dita:mapPath
cai1626458602965.ditamap
dita:ditavalPath
cai1626458602965.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

The commandline.properties file configures the command-line interface. It is installed as part of the Data Mover command-line installation process.

The Data Mover REST server URL is specified in the first half of the output. If you want to connect to a different REST server (and thus a different daemon) at runtime, you can change these default values by entering them as parameters of the Data Mover commands.
# Copyright (C) 2009-2021 by Teradata Corporation.
# All Rights Reserved.
# TERADATA CORPORATION CONFIDENTIAL AND TRADE SECRET
#----------------------------------------------------------------------------------------------
# File: "commandline.properties"
#
# Purpose: This file contains all of the properties used by the DM CommandLine.
#
# Caution: Do not modify the property names/values in this file unless absolutely sure
# of the implications to the DM CommandLine.
#
# Note: Any line of text in this document that begins with a '#' character is a comment and
# has no affect on the DM CommandLine. However, comments should not be modified.
#
# All properties under LOGGING Comment are used for logging purposes
#
#----------------------------------------------------------------------------------------------
# Purpose: Data Mover Rest Interface
# Default: https://localhost:1443/datamover
# For automatic failover support:
# dm.rest.endpoint=https://activeServer:1443/datamover,https://standbyServer:1443/datamover
dm.rest.endpoint=https://localhost:1443/datamover

#----------------------LOGGING-------------------------------

# Purpose: Set Logging level to info.  User has 6 options.
# From most amount of logging to least: trace < debug < info < warn < error < fatal
rootLogger.level=info

# Purpose: Informs the logging application to use a specific appender and it's properties.  DO NOT CHANGE
appender.rolling.type=RollingFile
appender.rolling.name=RollingFile
appender.rolling.layout.type=PatternLayout
appender.rolling.layout.pattern=%d [%t] %-5p %c{3}(%L) - %m%n
appender.rolling.policies.type=Policies
appender.rolling.policies.size.type=SizeBasedTriggeringPolicy
appender.rolling.strategy.type=DefaultRolloverStrategy
logger.rolling.name=com.teradata
logger.rolling.appenderRef.rolling.ref=RollingFile

# Purpose: Allow's user the ability to change the location of the log file.
# If changing log file location, please give the absolute path of the file;
# for example, /var/log/dmCommandLine.log
# for windows os: use slash instead of back slash:
# For Example: C:/Program File/Teradata/Log/dmCommandLine.log
appender.rolling.fileName=dmCommandLine.log
appender.rolling.filePattern=dmCommandLine.log.%i

# Purpose: The max size of the logging file before being rolled over to backup files.
appender.rolling.policies.size.size=20MB
# Purpose: The number of backup logging files created, after the max number, the oldest file is erased.
appender.rolling.strategy.max=5


#------------------------------------------------------------