Configure the Cluster and Start Monitor | Teradata Data Mover - Configuring the Cluster and Starting the Monitoring 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
The monitoring service uses SSH connections to the servers it monitors and JDBC to monitor the Data Mover repositories. The command can take a few minutes to complete and does the following:
  • Sets up the SSH logons for the monitoring services so that the services can log on without a password to the monitored servers.
  • Sets up and stores the usernames and passwords for the primary and secondary repositories.
  • Sets up ActiveMQ authentication for the primary and secondary ActiveMQ, daemon, agents, and REST servers.
  • Configures and activates the synchronization service from the primary to the secondary repository.
  • Configures and starts the primary daemon, agents, REST, bundled DSA, and primary sync monitor service in active mode.
  • Starts the monitoring service on local.monitor.host to monitor the local Data Mover components.
  1. Log on to the primary daemon server and edit the /etc/opt/teradata/datamover/failover.properties file for your system.
    For details about the Failover.properties file, see Failover.properties File
  2. Run the following command as root:
    ./dmcluster config
    In a default installation, the active repository host is the same as the active daemon host and the secondary repository host is the same as the secondary daemon host.