Configuring ActiveMQ is only available for Teradata Viewpoint versions 16.20.23.02 and 16.20.23.03.
-
In the /etc/opt/teradata/viewpoint/jms.cluster.properties file, update the jms.connectionFactory.uri property to use the following options on both servers:
- SSL
- 61617
- nested.verifyHostName=false
jms.connectionFactory.uri=failover\:(ssl\://<active server>\:61617,ssl\://<standby server>\:61617)?randomize\=false&priorityBackup\=true&timeout\=5000&maxReconnectAttempts\=5&maxReconnectDelay\=10000&nested.verifyHostName\=false
- From /etc/opt/teradata/viewpoint, copy tdactivemq.crt from the active server to /etc/opt/teradata/viewpoint/active-tdactivemq.crt on the standby server.
- From /etc/opt/teradata/viewpoint, copy tdactivemq.p12 from the active server to /etc/opt/teradata/viewpoint/active-tdactivemq.p12 on the standby server.
-
Import the certificate from the active server to the broker keystore on the standby server with the following command:
/opt/teradata/openjdk/jdk8/bin/keytool -importkeystore -deststorepass password -destkeypass password -destkeystore /etc/opt/teradata/viewpoint/broker.ks -destalias activebroker -srckeystore /etc/opt/teradata/viewpoint/active-tdactivemq.p12 -srcstoretype PKCS12 -srcstorepass password -srcalias broker
-
Import the certificate from the active server to the client truststore on the standby server with the following command:
/opt/teradata/openjdk/jdk8/bin/keytool -import -noprompt -alias activebroker -keystore /etc/opt/teradata/viewpoint/certs -storepass viewpoint -file /etc/opt/teradata/viewpoint/active-tdactivemq.crt
- Restart services on both servers using the /opt/teradata/viewpoint/dcs/bin/vp-control.sh option.