Archivo de propiedades para la interfaz de línea de comandos - Teradata Data Mover

Teradata® Data Mover Guía del usuario

Product
Teradata Data Mover
Release Number
16.20
Published
Noviembre de 2021
ft:locale
es-ES
ft:lastEdition
2021-12-02
dita:mapPath
es-ES/wph1512683331242.ditamap
dita:ditavalPath
es-ES/mpm1591127278842.ditaval
dita:id
B035-4101
Product Category
Analytical Ecosystem

El archivo commandline.properties configura la interfaz de línea de comandos. Se instala como parte del proceso de instalación de la línea de comandos de Data Mover.

En la primera sección, se especifica el nombre de host o la dirección IP del equipo que ejecuta el agente de mensajes de Java Message Service (JMS). Si desea conectarse a un servidor ActiveMQ diferente (y, por tanto, a un daemon diferente) en tiempo de ejecución, puede cambiar estos valores predeterminados si los introduce como parámetros de los comandos de Data Mover.
# Copyright (C) 2009-2019 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: 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

# Purpose: When set to true, a connection to a 
# Secondary Java Message Service (JMS) Message Broker can be
# established in case the Primary Java Message Service (JMS) Broker fails.
# Default: false
cluster.enabled=false
#----------------------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

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