Viewpoint support for Teradata DB authentication strategies

The best minds from Teradata, our partners, and customers blog about whatever takes their fancy.
Teradata Employee

Hello all. This blog discusses the recent release of support for both Teradata TD2 and LDAP authentication mechanisms in Teradata Viewpoint. Support for Teradata TD2 and LDAP authentication mechanisms was made available in the Teradata Viewpoint patch release.

The normal goal is to release new enhancements in actual Viewpoint releases instead of patch levels for various reasons including customer visibility, supportability, etc. However we also need to balance priority of the need with timing of release and consider exceptions where necessary. This is one of those cases. As you probably already know, Teradata Database supports TD2 and LDAP authentication mechanisms where either can be selected as the system default. In the past, Viewpoint was limited to supporting only TD2 which caused some grief and frustration to those who selected LDAP as their Teradata DB system wide default.

One might wonder why this is important considering Teradata Viewpoint has its own user identities and roles that don't directly rely on Teradata Database logins. For the most part that is true, but there are operations and configurations where the Teradata DB authentication becomes relevant. These instances now allow for both methods and support of the default whichever it is set to. So let's take a closer look at this new feature.

The first area that has differences is the Admin -> Teradata Systems -> General interface. The LOGIN section now has an authentication selection for the Viewpoint logins connecting to Teradata. This is followed by a new section that determines what authentication mechanisms will be offered in user interfaces within Viewpoint. These new sections look like this:

Dependent on these settings, the user interfaces for login prompts associated with the various Teradata Database actions change. For instance, aborting or changing workloads for queries in Query Monitor or adding space in Space Usage. Here is a view of how that is going to change based on these settings.


The other place worth mentioning is in the Profile setup as this is a self service aspect of Viewpoint and therefore may be seen but the business users of Teradata Viewpoint. The profile is setup to link your Viewpoint user identity with various Teradata Database credentials. This is then used by the MyQueries portlet in determining the queries that should be displayed in that portlet. This interface will adjust as follows:


While I have your attention, a few other things we snuck into this patch release of additional value for Alerting.

  • Blocking alerts now include the username and session identifier of the blocker
  • Session alerts now offer the ability to abort the session and send an email notification
  • Alert Viewer portlet now provides the alert name with an abort session action

As always, thanks for listening!

Hi Gryback

I used to run bteq scripts while inserting in to dbcmngr.alertrequest with actioncode set to 'T' and it executes the script which is stored in path C:\Program Files\NCR\Teradata Manager 12.0\Secure

Now since Teradata Manager is no longer supported, how shall I use this feature?

Please help.

Teradata Employee
Configuration of Teradata alerts information was previously in the Viewpoint Configuration Guide but has now been moved to its own publication called "Teradata Alerts Installation and Configuration Guide" which can be found on the Teradata Information Products website. This should walk you through how to configure this within Viewpoint. We will also be posting the new Teradata Alerts documentation on Developer Exchange. Last comment is that questions unrelated to articles should really be posted to the forum.