Teradata Notification Service Cluster Configuration | Teradata Viewpoint - Teradata Notification Service Cluster Configuration - Teradata Viewpoint

Teradata® Viewpoint Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Viewpoint
Release Number
16.50
16.20
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
nsn1520516845887.ditamap
dita:ditavalPath
nsn1520516845887.ditaval
dita:id
B035-2207
lifecycle
previous
Product Category
Analytical Ecosystem

To use BTEQ and Run Program alert actions on Windows, Teradata Notification Service must be installed on a Windows Server. Only one Teradata Notification Service for Windows can run within a Teradata Alerts cluster.

To use BTEQ and Run Program alert actions on Linux, Teradata Notification Service must be installed on a Linux Server. Only one Teradata Notification Service for Linux can run within a Teradata Alerts cluster.

Teradata Notification Service connects to the active database cache on the Viewpoint server. When the active cache database is promoted, the service automatically connects to the new active database.

Teradata Notification Service connects to the messaging service on the Viewpoint server. When a Teradata Alerts messaging service failure occurs, the Teradata Notification Service is automatically reconnected to the secondary messaging service. When the messaging service is restored, the Teradata Notification Service reconnects to the original messaging service.

The sections below describe the steps required when enabling or disabling a cluster configuration.