System Aliases | Teradata Data Mover - System Aliases - 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

Host aliases, or tdpids, for source and target systems are defined either in DNS (preferred) or in hosts file of all Data Mover-DSA components such as the servers and source and target TPA nodes.

If a system has been previously configured with DSA using a tdpid and you want to refer to that system through a different server alias in the job definition, you can add the server alias to the DNS or hosts file. There is no need to reconfigure the DSA system, provided that the previously configured tdpid remains working.

When configuring DSA components, be sure to refer to the server aliases instead of the IPs for the hosts involved. For example, use the server alias in dsc.properties and clienthandler.properties, as well as the ActiveMQ brokers, BAR NC master nodes, and when configuring DSA system tdpid.