Creating a Teradata Viewpoint Cluster - Teradata Viewpoint

Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Viewpoint
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
iwr1478709689896.ditamap
dita:ditavalPath
2207_ICUCustomer_vp_1610.ditaval.ditaval
dita:id
B035-2207
lifecycle
previous
Product Category
Analytical Ecosystem
Ensure that all of the following conditions are met:
  • You have at least two Teradata Viewpoint servers.
  • All servers have the same patch version of Teradata Viewpoint installed.
  • All servers have the same time and timezone, with an accuracy within a few minutes.

Determine which server is going to host the active cache database and which is going to host the standby cache database. The server that is going to host the active cache database can already have existing users, roles, permissions, settings, and collected data from monitored Teradata systems that is shared by all Teradata Viewpoint servers in the cluster.

Any data on the server hosting the standby cache database is lost.
The cluster setup script used here clusters both Teradata Viewpoint and Teradata Alerts servers.
  1. Run the cluster setup script on the server that will host the active cache database: /opt/teradata/viewpoint/bin/clustersetup.sh
  2. Select option 1. The cluster setup tool performs the following actions:
    • Asks a few simple questions about what hosts to add to the cluster and a list of email addresses that receive alerts
    • Verifies that the software versions and times on the new servers match
    • Stops all the Teradata Viewpoint services in the cluster
    • Configures Teradata Viewpoint and Teradata Alerts with information about the new servers
    • Restarts all Teradata Viewpoint services in the cluster
  3. Follow the instructions on the screen. After the cluster setup script completes, the Notification Banner within the Teradata Viewpoint portal appears, and the setup of the standby cache database is handled automatically in the background. The server is added to the cluster, and all Teradata Viewpoint services are restarted.