Configuring the Cluster and Starting the Monitoring Service - Teradata Data Mover

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

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
pgy1512683352051.ditamap
dita:ditavalPath
DM_16_20_08_ICUCust_AsterIncluded.ditaval
dita:id
B035-4102
lifecycle
previous
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 may 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 active and standby repositories.
  • Configures and starts the local daemon, agents, and local sync service in active mode.
  • Starts the remote sync service in standby mode.
  • Starts the monitoring service on local.monitor.host to monitor the local Data Mover components.
  1. Log on to the active 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 standby repository host is the same as the standby daemon host.
    You must be a root user to configure ActiveMQ.