In a high availability environment, ActiveMQ authentication is automatically configured when running dmcluster config during the install or upgrade process to Data Mover 17.00 or later. The designated-standby server and all additional agents in the clustered environment are automatically configured with the ActiveMQ secret and encrypted password from the designated-active Data Mover server.
However, if your environment is not configured to use a high availability cluster, perform the following steps after the install or upgrade so that any remote agents can successfully access ActiveMQ on the Primary server.
Copy /etc/opt/teradata/tdactivemq/datamover.properties from the Primary Data Mover server to the same location on the remote agent(s), as in the following example:
# scp /etc/opt/teradata/tdactivemq/datamover.properties root@your_agent_server:/etc/opt/teradata/tdactivemq
Login to each remote agent to verify the ActiveMQ permissions are similar to the following:
-rw-r----- 1 root activemq 16 Feb 10 14:49 datamover.properties
If necessary, set the permissions for datamover.properties on each remote agent:
# chmod 640 datamover.properties # chgrp activemq datamover.properties
Update the agent broker.password property in the agent.properties file with the same value defined on the Primary Data Mover server.
Update /etc/opt/teradata/datamover/agent.properties if it exists. If not, update opt/teradata/client/nn.nn/datamover/agent/agent.properties.
Restart the agent.
/etc/init.d/dmagent stop /etc/init.d/dmagent start