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

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
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 hostname or IP address of the machine running the Java Message Service (JMS) Message Broker is specified in the first section. If you want to connect to a different ActiveMQ 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-2016 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  Data Mover  CommandLine.
#
# Caution: Do not modify the property names/values in this file unless absolutely sure 
# of the implications to the  Data Mover  CommandLine.
#
# Note: Any line of text in this document that begins with a '#' character is a comment and 
# has no affect on the  Data Mover  CommandLine. However, comments should not be modified.
#
# All properties starting with log4j are used for logging purposes
#
#----------------------------------------------------------

# Purpose: The hostname or IP address of the machine running the 
# Java Message Service (JMS) Message Broker.
# Default: localhost
# Other examples include:
# broker.url=10.0.1.199
# broker.url=hostname
# broker.url=[fe80::114:23ff:fe1d:32fb]
broker.url=localhost

# Purpose: The port number on the machine in which the
# Java Message Service (JMS) Message Broker is listening.
# Default: 61616
broker.port=61616

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

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

# Purpose: Allows users to change the location of the log file.
# If changing log file location, give the absolute path of the file;
# for example, /var/log/dmAgent.log
# for windows os: use slash instead of back slash: 
# For Example: C:/Program File/Teradata/Log/dmCommandLine.log 
log4j.appender.logfile.file=dmCommandLine.log

# Purpose: Informs the logging application to use a specific appender.  DO NOT CHANGE 
log4j.appender.logfile=org.apache.log4j.RollingFileAppender
# Purpose: The max size of the logging file before being rolled over to backup files.
log4j.appender.logfile.maxFileSize=20MB
# Purpose: The number of backup logging files created, after the max number, the oldest file is erased.
log4j.appender.logfile.maxBackupIndex=5

# Purpose:  The Pattern of the layout of log file.  d is the date, t is the
# thread, p is the log level, c is the class name and m & n are the messages
# You can create your own layout. For detailed information, go to: 
# http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html
log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
log4j.appender.logfile.layout.ConversionPattern=%d [%t] %-5p %c{3}(%L) - %m%n

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