Configure the Cloud Staging Copy REST Service | Teradata Data Mover - Configuring the Cloud Staging Copy REST Service - Teradata Data Mover

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
jvt1700556161677.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem
During the installation of Data Mover, the Cloud Staging Copy Service (CS2) REST component is installed and started automatically. You need to configure the cs2.properties file for your environment and restart the service.
  1. In the directory /etc/opt/teradata/datamover, locate cs2.properties.
  2. Configure the following properties:
    Property Description Default Value
    dsa.rest.endpoint The DSA REST URL used by CS2 for the DSA utility. You can override the default value by adding the same named property in the cs2.properties file. https://localhost:9090/dsa
    rootLogger.level
    The six levels of logging from trace level to application error.
    • TRACE
    • DEBUG
    • INFO
    • WARN
    • ERROR
    • FATAL
    INFO
    rootLogger.appenderRef.rolling.ref Do not edit. This is an internal setting for logging infrastructure. RollingFile
    appender.rolling.type Do not edit. This is an internal setting for logging infrastructure. 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 [%t] %-5p %c{3}(%L) - %m%n
    appender.rolling.policies.type Do not edit. This is an internal setting for logging infrastructure. Policies
    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
    appender.rolling.fileName The relative or absolute path of the log file. /var/opt/teradata/datamover/logs/dmCS2.log
    appender.rolling.filePattern

    Specifies logfiles pattern.

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

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

    Example: If maximum backups = 3, three backup logs are created:
    • dmCS2.log.1
    • dmCS2.log.2
    • dmCS2.log.3
    If the current dmCS2.log file size exceeds 10MB, the file rolls to become the new dmCS2.log.1, and:
    • The previous dmCS2.log.1 becomes the new dmCS2.log.2.
    • The previous dmCS2.log.2 becomes the new dmCS2.log.3.
    • The previous dmCS2.log.3 is deleted.
    3
    rest.connection.timeout Defines the timeout in milliseconds for a connection to be established with DSA REST.
    30000
    rest.read.timeout Defines the socket timeout in milliseconds when sending requests to DSA REST.
    120000
    swagger.ui.enabled Enable/Disable Swagger user interface
    False
  3. Restart the Cloud Staging Copy Service: /etc/init.d/dmcs2 restart