list_configuration - 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

Purpose

The list_configuration command outputs one file with configuration and performance settings for the daemon. Configuration settings for the event table are also included.

Parameters

dir
[Optional] Output directory for the daemon configuration settings. A directory will be created if one does not exist.
/home/datamover/config
The generated XML file is written by default to the current directory.
filename
[Optional] Name with which to save the configuration file. Existing file name will be overwritten.
configuration.xml
The generated XML file has by default the name configuration.xml.
security_username
[Optional] User ID of the super user or authorized Viewpoint user. The user ID of the super user is dmcl_admin and cannot be changed.
Required if security management is enabled on the Data Mover daemon.
security_password
[Optional] Password for the super user or authorized Viewpoint user.
53cUr17y
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password_encrypted is also specified.
security_password_encrypted
[Optional] Encrypted password for the super user.
052c7aabd14c7770141ac3c0137ab98ae0d3f0f7cddf588981206b010c0c1b2f
Required if security management is enabled on the Data Mover daemon. Not a valid parameter if -security_password is also specified.
broker.url
[Optional] You may enter a broker URL to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
dm-server1
broker.port
[Optional] You may enter a broker port to overwrite the default value specified in the commandline.properties file in order to connect to a different ActiveMQ server (and therefore a different daemon) at runtime.
61616

Usage Notes

Edit the file information, then save the file to the daemon with the save_configuration command.

Configurable options include settings for:
  • Data dictionary views
  • Forcing the direction of copying between source and target Teradata Database systems
  • Online archiving
  • Preventing a Teradata Database system from being used as a target
  • Overwriting existing objects
  • Messages that are generated for the event table
  • Performance tuning
  • Using multiple target users for Teradata ARC jobs
  • Interaction with Teradata Ecosystem Manager
  • Management of security for the command-line interface and the Data Mover portlet
  • Client encryption

XML File Example

For the list_configuration command, type datamove list_configuration -f parameters.xml.

In the following example, the parameters file writes the Data Mover daemon configuration to /home/datamover/config/configuration.xml.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<dmListConfiguration
	xmlns="http://schemas.teradata.com/dataMover/v2009"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://schemas.teradata.com/unity/datamover.xsd">
	<dir>/home/datamover/config</dir>
	<filename>configuration.xml</filename>
</dmListConfiguration>