Configure ActiveMQ and REST Settings | Teradata Data Mover - Configuring Cluster Settings - 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
In a high availability configuration, the ActiveMQ broker is enabled on the primary Data Mover server. The ActiveMQ broker on the secondary server is only activated if a failover occurs.
  1. Confirm the network of brokers has been disabled:
    /opt/teradata/client/nn.nn/datamover/failover/dmcluster configactivemq -e false
    If upgrading from a Data Mover version earlier than 16.20, you must reconfigure the ActiveMQ settings to use only a single active ActiveMQ broker.
  2. On both the primary and secondary Data Mover servers, set the following values for the daemon.properties file:
    cluster.enabled=false
    broker.url=localhost or IP address of local system
    The daemon on the primary Data Mover server only uses the local ActiveMQ broker. If failover occurs, the daemon on the secondary Data Mover sever only uses the ActiveMQ broker on the secondary server.
  3. On both the primary and secondary server, and any standalone Data Mover agent servers, set the following values for the agent.properties file:
    cluster.enabled=true 
    broker.url=active broker host or IP,standby broker host or IP
    Providing both broker URLs allows the agent to automatically connect to whichever Data Mover daemon is active.
  4. On both the primary and secondary Data Mover server, and any other server where the Data Mover command line is installed, set the following values for the commandline.properties file:
    dm.rest.endpoint=active REST server url,standby REST server url
    Providing both REST server URLs in commandline.properties allows the command line to automatically connect to whichever Data Mover server is active.

    Make sure the host:port for both the primary and secondary REST servers are added to the accept.host.list in tdmrest.properties on both the primary and secondary Data Mover servers.