Professional Documents
Culture Documents
Teradata Viewpoint
Installation, Configuration, and Upgrade Guide
for Customers
Release 15.10
B035-2207-035K
May 2015
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Data Warehousing, Active Enterprise Intelligence, Applications-Within, Aprimo Marketing Studio, Aster, BYNET,
Claraview, DecisionCast, Gridscale, MyCommerce, QueryGrid, SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, Teradata
ServiceConnect, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered trademarks of Teradata Corporation or its
affiliates in the United States and other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
Apache, Apache Avro, Apache Hadoop, Apache Hive, Hadoop, and the yellow elephant logo are either registered trademarks or trademarks
of the Apache Software Foundation in the United States and/or other countries.
Apple, Mac, and OS X all are registered trademarks of Apple Inc.
Axeda is a registered trademark of Axeda Corporation. Axeda Agents, Axeda Applications, Axeda Policy Manager, Axeda Enterprise, Axeda
Access, Axeda Software Management, Axeda Service, Axeda ServiceLink, and Firewall-Friendly are trademarks and Maximum Results and
Maximum Support are servicemarks of Axeda Corporation.
Data Domain, EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Hortonworks, the Hortonworks logo and other Hortonworks trademarks are trademarks of Hortonworks Inc. in the United States and other
countries.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
NetVault is a trademark or registered trademark of Dell Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
Quantum and the Quantum logo are trademarks of Quantum Corporation, registered in the U.S.A. and other countries.
Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license.
SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
The information contained in this document is provided on an "as-is" basis, without warranty of any kind, either express
or implied, including the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
Some jurisdictions do not allow the exclusion of implied warranties, so the above exclusion may not apply to you. In no
event will Teradata Corporation be liable for any indirect, direct, special, incidental, or consequential damages, including
lost profits or lost savings, even if expressly advised of the possibility of such damages.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or
updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this
information at any time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please e-mail: teradata-books@lists.teradata.com
Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display,
transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis.
Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose
whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 2008 - 2015 by Teradata. All Rights Reserved.
Table of Contents
Preface.............................................................................................................................................................7
Purpose.................................................................................................................................................................. 7
Audience................................................................................................................................................................ 7
Revision History................................................................................................................................................... 7
Additional Information........................................................................................................................................7
Related Links..................................................................................................................................................7
Related Documentation................................................................................................................................8
Customer Education..................................................................................................................................... 8
Product Safety Information.................................................................................................................................8
Chapter 1:
Overview........................................................................................................................................................9
Dependencies........................................................................................................................................................ 9
Supported Web Browsers..............................................................................................................................9
Supported Teradata Viewpoint Appliances................................................................................................ 9
Supported Teradata Database Versions...................................................................................................... 9
Ports Used by Teradata Viewpoint............................................................................................................ 10
Teradata Manager Feature Equivalence...........................................................................................................10
Teradata Viewpoint Services............................................................................................................................. 10
Starting and Stopping Teradata Viewpoint Services...................................................................................... 11
Interaction between Teradata Alerts and Teradata Database.......................................................................12
Notification Server Requirements....................................................................................................................12
Linux Server Requirements........................................................................................................................12
Windows Server Requirements..................................................................................................................13
Starting and Stopping the Teradata Notification Service (Windows)..........................................................13
Starting and Stopping the Teradata Notification Service (Linux)................................................................14
Chapter 2:
Upgrading Viewpoint Software............................................................................................ 15
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 3
Table of Contents
Creating an Incident............................................................................................................................................16
Finding the PUT Version Running on the System.......................................................................................... 16
Determining the Latest PUT Release................................................................................................................16
Downloading New PUT Packages.....................................................................................................................17
Installing and Upgrading PUT...........................................................................................................................18
Installing PUT...............................................................................................................................................18
Upgrading PUT............................................................................................................................................ 18
Checking for Space on the Node....................................................................................................................... 19
Creating a Target Directory................................................................................................................................19
Software Package Downloads.............................................................................................................................20
Downloading Software Packages................................................................................................................20
Verifying the Previous Database Backup..........................................................................................................21
Upgrading a Teradata Viewpoint Server...........................................................................................................21
Creating a Teradata User for Data Collection..................................................................................................22
Upgrading a Teradata Viewpoint Cluster......................................................................................................... 23
Troubleshooting a Failed Upgrade.................................................................................................................... 23
Chapter 3:
Installing Notification Services.............................................................................................25
Chapter 4:
Advanced Configuration Tasks...............................................................................................33
4 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Table of Contents
Definitions....................................................................................................................................................34
Before You Begin LDAP Configuration................................................................................................... 35
Determining LDAP Configuration Mode................................................................................................35
Is the Username in DN?...................................................................................................................... 36
Determining the Number of Bind Patterns...................................................................................... 37
LDAP Servers...................................................................................................................................................... 37
About Auto-Provisioning and Role Mapping..........................................................................................38
Adding an LDAP Server............................................................................................................................. 38
LDAP Configuration Options....................................................................................................................39
Basic Configuration............................................................................................................................. 39
DN Pattern Bind...................................................................................................................................40
User Search............................................................................................................................................40
Key User Information.......................................................................................................................... 40
Auto-Provisioning................................................................................................................................41
Role Mapping Global Settings............................................................................................................ 41
Role Mapping Individual Settings......................................................................................................41
Changing a Teradata Viewpoint System Name...............................................................................................41
Resetting the Admin User Password................................................................................................................42
Portlets Enabled Under Special Circumstances............................................................................................. 42
Installing Teradata Data Lab............................................................................................................................. 42
Configuring Teradata Data Lab Email Notifications..............................................................................43
Configuring Teradata Viewpoint to Monitor a Managed Server..................................................................43
About Configuring Stats Manager....................................................................................................................44
Before You Begin......................................................................................................................................... 44
Configuring Stats Manager........................................................................................................................ 44
Configuring Teradata Database to Collect and Analyze Statistics...............................................................45
Collecting Statistics..................................................................................................................................... 45
Analyzing Statistics..................................................................................................................................... 45
Cleaning Up the TDStats Database...........................................................................................................45
Teradata Viewpoint Server Clustering Configurations..................................................................................46
High Availability Configuration: Two Teradata Viewpoint Servers..................................................... 46
High Usage Configuration: Three or More Teradata Viewpoint Servers............................................. 47
Advanced Configuration: Three or More Teradata Viewpoint Servers With Dedicated Cache
Database Server.................................................................................................................................... 47
Teradata Alerts Cluster Configurations................................................................................................... 48
Failure Scenarios..........................................................................................................................................49
Teradata Viewpoint Failure Scenarios............................................................................................... 49
Data Collection Server Failure.............................................................................................49
Cache Database Failure.........................................................................................................49
Active Teradata Viewpoint Server Failure.......................................................................... 50
Teradata Alerts Failure Scenarios.......................................................................................................51
Alert Service Failure (Scenario 1)........................................................................................51
Messaging Service Failure (Scenario 2).............................................................................. 51
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 5
Table of Contents
6 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Preface
Purpose
This guide provides customer information and procedures for configuring and maintaining
the Teradata Viewpoint server, as well as upgrading from and backing down to a previous
Teradata Viewpoint software version.
Audience
This guide is intended for use by:
• System administrators
• Database administrators and relational database developers
• Customers
• Teradata Customer Support
Revision History
Date Release Description
May 2015 15.10 Corrected "Creating a Teradata Viewpoint Cluster" topic
April 2015 15.10 Added Data Lab installation instructions
March 2015 15.10 Initial release
Additional Information
Related Links
URL Description
http://tays.teradata.com Use Teradata At Your Service to access Orange Books, technical
alerts, and knowledge repositories, view and join forums, and
download software packages.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 7
Preface
Product Safety Information
URL Description
www.teradata.com External site for product, service, resource, support, and other
customer information.
Related Documentation
Documents are located at www.info.teradata.com.
Title Publication ID
Parallel Upgrade Tool (PUT) Reference B035-5713
Describes how to install application software using PUT.
Teradata Viewpoint User Guide B035-2206
Describes the Teradata Viewpoint portal, portlets, and system administration
features.
Electronic Software Distribution Guide BCD0-0718-0000
Customer Education
Teradata Customer Education designs, develops and delivers education that builds adept
skills and capabilities for our data warehousing technology customers, enabling them to
maximize their Teradata investment. Teradata offers a variety of delivery formats to suit your
needs. The combination of web technology through the Teradata Education Network, along
with hands-on classroom training, provides each user level with a wide range of
opportunities to gain knowledge about our data warehousing tools.
Our flexible education options build upon and complement one another to give you a cost
effective, robust education offering. On this website, you can view and enroll in any Teradata
Customer Education training offering.
As the premier on-line learning environment for Teradata users, Teradata Education
Network (TEN) is a membership-based learning community that allows you to harness the
power of the internet and expand your knowledge of Teradata data warehousing tools at your
own pace ... anytime, anywhere.
If you do not have a membership that includes web-based training courses, you can purchase
courses at www.teradata.com/TEN/ or Teradata University.
Notice: Improper use of the Reconfiguration utility can result in data loss.
8 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
CHAPTER 1
Overview
Dependencies
Recommended Hardware
• At least 1.8 GHz Pentium M, 3 GHz Pentium 4, or equivalent CPU
• At least 1 GB of RAM
• Monitor or display supporting at least 1024x768 resolution
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 9
Chapter 1 Overview
Teradata Manager Feature Equivalence
*You can change the outgoing Teradata Alerts SMTP ports by selecting Delivery Settings >
Email in the Alert Setup portlet.
10 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 1 Overview
Starting and Stopping Teradata Viewpoint Services
Service Description
dcs Data Collection Service that monitors and collects data from Teradata
systems
postgresql Internal database used to store all Viewpoint configuration and collected
data
tdnotification Teradata Notification Service used to run BTEQ and Run Program alert
actions.
tdactivemq Messaging service that allows message exchanges between the Teradata
Alerts components
tmsmonitor Teradata Managed Server Monitor that monitors performance of the
Teradata Viewpoint server
viewpoint Teradata Viewpoint portal that provides web browser access
The Teradata Viewpoint services that can use these commands are:
• camalert
• dcs
• postgresql
• tdactivemq
• tmsmonitor
• viewpoint
The following are examples of using the commands.
Action Example
Starting the Teradata Alert service /etc/init.d/camalert start
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 11
Chapter 1 Overview
Interaction between Teradata Alerts and Teradata Database
Action Example
Checking the Teradata Managed Server monitor status /etc/init.d/tmsmonitor status
The vp-control.sh script, located in the same directory, allows you to run the start, stop,
restart and status commands. When running start, stop, or restart, the script performs the
specified action on the tdactivemq, camalert, tmsmonitor, dcs, and viewpoint services. When
running status, you receive the status of all commands for all the services including
postgresql.
/opt/teradata/viewpoint/bin/vp-control.sh command
Where command is the command you want to perform using the script.
This script supports the same command arguments as the individual init.d scripts.
12 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 1 Overview
Starting and Stopping the Teradata Notification Service (Windows)
Software Dependencies One of the following SuSE Linux Enterprise operating systems:
• SuSE Linux Enterprise 10, Service Pack 3 or later version
• SuSE Linux Enterprise 11
The following Java SE Runtime Environment:
• Java SE Runtime Environment 7 or greater
BTEQ and related dependencies:
• TTU versions are dependent on the targeted Teradata
Database and should be installed using the TTU Client Main
Install so all required dependencies are installed.
Other Requirements The Linux system clock must be synchronized with the clock on
the Viewpoint server.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 13
Chapter 1 Overview
Starting and Stopping the Teradata Notification Service (Linux)
You can start, stop, pause, resume, or restart a service using the Services Administration tool
in Windows, which can be opened from a command prompt window by typing
services.msc.
restart Stops and restarts the service. To restart the tdnotification service, type:
/etc/init.d/tdnotification restart
status Checks if the service is To check if the tdnotification service is running, type:
currently running.
/etc/init.d/tdnotification status
14 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
CHAPTER 2
When upgrading from a release earlier than 14.01.00.00, perform the following upgrades
concurrently in the same single PUT session:
• Teradata Alerts to release 14.01.
• PostgreSQL database to PostgreSQL 9.1.
1 Perform an incremental backup to reduce the upgrade time.
Determine the approximate duration of the Teradata Viewpoint upgrade:
a. Determine the duration of the last backup by subtracting the finish time from the
configured start time.
b. Multiply this value by 2.
2 Verify the previous database backup.
3 Upgrade the software based on your configuration:
• Teradata Viewpoint Server
• Teradata Viewpoint Cluster
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 15
Chapter 2 Upgrading Viewpoint Software
Creating an Incident
Creating an Incident
You must obtain an Incident number from Teradata at Your Service prior to performing any
software upgrades.
1 On your Windows PC, open a web browser and go to Teradata At Your Service at http://
tays.teradata.com and log in.
2 Under the Product banner click Incident.
3 Click the Create tab.
4 Make the following selections as appropriate:
Note: Click the green arrows to move forward or back in the selection screens.
Option Description
Site The site where the activity will be performed.
Priority The Priority of the issue.
Product Area The area of the system where the issue is located or where work will be
performed.
Problem Type A list of Problem Types.
Synopsis A short Synopsis of the activity being performed.
Description A short description of the activity being performed.
16 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 2 Upgrading Viewpoint Software
Downloading New PUT Packages
1 Check for the latest version of PUT in the Certification List section of Teradata At Your
Service at http://tays.teradata.com.
Field Selection
Platform The operating system
Current Current
5 Click Submit.
6 On the Teradata PUT screen, select PUTSRC, PUTTools, and TDput for download and
write the version number in the following space:
TDput ______________________________________
PUTSRC____________________________________
PUTTools_(Version not required; download is)______
7 Complete the download request with the following choices:
Field Selection/Entry
Download Type Windows
Download Readme Files? No
User Name The name on your account
E-Mail The e-mail address on your account
Site ID The site ID for your site
Change Control Number The Change Control Number previously
obtained
Note: The Change Control Number entered
must be valid for your site ID.
8 Click Submit.
9 Click Download.
10 Save the downloaded files and transfer them to the PUT Master Node:
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 17
Chapter 2 Upgrading Viewpoint Software
Installing and Upgrading PUT
c In the Save As dialog box, go to the target directory for the downloaded packages and
click Save.
The package files are compressed into a single Windows .zip file.
d Extract or unzip the downloaded .zip file.
Notice: The unzipped files are Linux files in the .gz or .rpm format. Never uncompress a
Linux .gz file on a Windows computer. Windows might corrupt the file.
e Use the Secure File Transfer Protocol (SFTP) utility to transfer the .gz or .rpm files to
the Master Node download directory and then uncompress the .rpm files (the .gz files
do not need to be uncompressed).
Note: Make sure you transfer the files using the binary mode, not the ASCII mode.
The .zip files are not needed on the Master Node and can be deleted from the
Windows system after the upgrade.
Installing PUT
1 To install PUT, follow the instructions in the Parallel Upgrade Tool (PUT) Reference.
Note: Make sure the version of PUT is the same on all nodes, including TMS servers.
Always use the latest version of PUT.
Upgrading PUT
This procedure copies PUT from the Master Node to all other nodes that need a new version
of PUT installed.
Notice: Do not choose any PUT operation other than the operation specified. Choosing any of the
PUT operations that are not specified in your task could result in severe damage to user data.
18 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 2 Upgrading Viewpoint Software
Checking for Space on the Node
In this example, the / drive has no available space. Contact your system administrator to
remove old files and free up space for the new packages. Teradata recommends that you
double the total the space required by the packages you are downloading.
where the ccnumber is the Teradata Change Control Number, as shown in the following
example:
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 19
Chapter 2 Upgrading Viewpoint Software
Software Package Downloads
/var/opt/teradata/VECD2RQ9B/pkgs
Option Description
Customer access: http://tays.teradata.com a. Click Software Downloads.
b. Click Certified Configs.
2 In the Certification List section of the left pane, click Current List.
3 In the Certification List area, make the appropriate selections as follows:
Field Selection/Entry
Node Type The application package to be installed.
Target OSs The operating system on the node.
Application Version The release number for the application.
Teradata Releases N/A
BusType SM3G
Would you like to compare lists? Select Yes or No
4 Click Submit.
5 Select all packages.
6 Complete the download request with the following choices:
20 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 2 Upgrading Viewpoint Software
Verifying the Previous Database Backup
Field Selection/Entry
Download Type Windows
Download Readme Files? No
User Name The name on your account
E-Mail The e-mail address on your account
Site ID The site ID for your site
Change Control Number The Change Control Number previously
obtained
Note: The Change Control Number entered
must be valid for your site ID.
7 Click Submit.
8 When the .zip package is ready to download, click the Download button.
Optionally, you can save the patch for future use by selecting the Save the Patch for
future use box.
9 In the File Download dialog, click Save, navigate to the target directory, and click Save
again.
10 Extract or unzip the file in the target directory.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 21
Chapter 2 Upgrading Viewpoint Software
Creating a Teradata User for Data Collection
These values vary based on several factors, including the size of the Teradata Database
system, the level of activity on the Teradata Database system, and the amount of data
retained in the data dictionary tables queried by Teradata Viewpoint. For Teradata
systems of 50 nodes or fewer, the suggested allocations are 2 GB of perm space and 500
GB of spool space. For Teradata Database systems larger than 50 nodes, additional perm
and spool space might be required.
22 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 2 Upgrading Viewpoint Software
Upgrading a Teradata Viewpoint Cluster
2 Type the following command, where perm space and spool space are the perm space and
spool space to allocate to the user:
create user username as perm=perm space, spool=spool space
password=user password;
3 If the console user does not exist on the target Teradata Database system, run the
following command to create the user:
create user console as perm=50000, spool=50000, account='$H-remote-
console-user', password=console, fallback;
If there are more than two Teradata Viewpoint servers in the cluster, the order in which
you stop the servers does not matter.
3 Upgrade the primary server.
4 Upgrade the remaining servers in the cluster.
5 If you upgraded from a version earlier than 14.01.00.00, use the cluster setup tool from
the primary server to re-establish the cluster by following the instructions in Creating a
Teradata Viewpoint Cluster.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 23
Chapter 2 Upgrading Viewpoint Software
Troubleshooting a Failed Upgrade
24 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
CHAPTER 3
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 25
Chapter 3 Installing Notification Services
Installing Teradata Notification Service for Windows
Option Description
Windows operating systems a. From Control Panel, double-click the System icon to view
prior to Windows 7 and change system settings.
b. Select the Advanced tab.
The following steps describe how to install or upgrade the Teradata Notification Service on a
Windows Server. Note that xx represents the version of the software you are installing or
upgrading.
1 Download the software from the Teradata Software Server, as explained in Downloading
the Teradata Alerts Notification Software.
2 Copy the zip file teradatacam__Windows_i386.15.10.00.xx.zip to the server
where the installation or upgrade will be performed.
3 Navigate to the directory and folder containing the zip file.
4 Extract the zip file.
This creates a folder called teradatacam__Windows_i386.15.10.00.xx in the
current directory.
5 Navigate to the teradatacam__Windows_i386.15.10.00.xx\DISK1 folder.
6 Click setup.exe.
7 Select the setup language, and click OK.
8 Follow the Install Shield wizard instructions and do the following:
26 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 3 Installing Notification Services
Installing Teradata Notification Service for Windows
f Click Finish.
The software is installed at drive:\Program Files (x86)\Teradata\Client
\15.10\Teradata Notification Service
The previous installation procedure requested that you enter the name of the Teradata
Viewpoint server. If you did not complete this step, manually configure the Teradata
Notification Service to include the location of the Viewpoint server where Teradata Alerts is
installed.
1 Create the following folder in the installation partition:
drive:\etc\opt\teradata\cam
2 Change the directory to the installation folder to:
drive:\Program Files (x86)\Teradata\Client\15.10\Teradata
Notification Service
3 Copy config\cam.properties.template to
drive:\etc\opt\teradata\cam\cam.properties
4 Edit cam.properties and locate the entry for cam.activemq.host:
#cam.activemq.host=localhost
5 Remove the comment sign and assign cam.activemq.host to the Viewpoint server
where you installed the Teradata Alerts packages:
cam.activemq.host=serverName
6 Save and close the file.
7 Restart the Teradata Notification Service.
The Teradata Notification Service executes the BTEQ and Run Program alert actions. The
BTEQ scripts and program executables must be located in the specified folders.
The directories where you placed the BTEQ scripts and programs are scanned periodically
by the Teradata Notification Service while the service is running. If changes are detected to
the directories, the updated directory contents are relayed to the alert service, which updates
the Teradata Alerts repository on the Viewpoint server. The alert service must be running on
the Viewpoint server in order for updates to be visible on the Viewpoint server.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 27
Chapter 3 Installing Notification Services
Installing Teradata Notification Service for Linux
1 Place the BTEQ scripts in the following folder relative to the installation location:
InstallFolder\Teradata\Client\15.10\Teradata Notification Service
\sql
2 Place the programs you want to run in the following folder relative to the installation
location:
InstallFolder\Teradata\Client\15.10\Teradata Notification Service
\usrcmd
Teradata Notification service for Linux can be installed using PUT. These instructions
assume that the reader is familiar with the PUT installation process, and that the TDPut
software is installed and available on the Linux server.
1 Download the software from the Teradata Software Server, as explained in Downloading
the Teradata Alerts Notification Software.
2 Launch TDPut on the Linux server and install the tdnotification1500 package onto
the server.
3 After the installation, manually configure the software with the location of the Viewpoint
server.
28 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 3 Installing Notification Services
Installing Teradata Notification Service for Linux
Service User
The tdnotification installation process creates a new user which, as of release 14.10, can be
custom-defined during installation. If no user is defined, the system creates a default user
called camuser, with a default home account of /home/camuser. If the new user account
cannot be created with a home account, it is created without one. The camuser account is a
non-login account. The tdnotification service runs with the user ID--either custom-defined
or camuser-- instead of running as the root user.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 29
Chapter 3 Installing Notification Services
Installing Teradata Notification Service for Linux
The previous installation procedure requested that you enter the name of the Teradata
Viewpoint server. If you did not complete this step or you performed the installation with
PUT, manually configure the Teradata Notification Service for Linux to include the location
of the Viewpoint server where Teradata Alerts is installed.
1 Create the following directory if it does not already exist:
mkdir -p /etc/opt/teradata/cam
2 Change the permissions on the directory:
chmod 755 /etc/opt/teradata
chmod 755 /etc/opt/teradata/cam
3 Change directory:
cd /opt/teradata/client/cam/tdnotification/config
4 Copy the cam.properties.template file to the configuration location:
cp cam.properties.template /etc/opt/teradata/cam/cam.properties
5 Edit cam.properties and locate the entry for cam.activemq.host:
#cam.activemq.host=localhost
6 Remove the comment sign and assign cam.activemq.host to the Viewpoint server
where you installed the Teradata Alerts packages:
cam.activemq.host=serverName
7 Save and close the file.
8 Change the file owner, replacing camuser with the custom service user as needed:
chown camuser: cam.properties
9 Change the file permissions:
chmod 744 cam.properties
10 Restart the tdnotification service:
/etc/init.d/tdnotification restart
The Teradata Notification Service for Linux executes the BTEQ and Run Program alert
actions. The BTEQ scripts and program executables must be located in specified directories.
The directories where you placed the BTEQ scripts and programs are scanned periodically by
the Teradata Notification Service while the service is running. If changes are detected to the
directories, the updated directory contents are relayed to the alert service, which updates the
Teradata Alerts repository on the Viewpoint server. The alert service must be running on the
Viewpoint server in order for updates to be visible on the Viewpoint server.
The following directories are created during the installation and preserved during upgrades.
The system administrator should ensure that these directories have the appropriate
30 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 3 Installing Notification Services
Uninstalling the Teradata Notification Service
permissions set for the service user (default is “camuser”) effective user ID for the
tdnotification service.
/opt/teradata/client/cam/sql
/opt/teradata/client/cam/usrcmd
If multiple versions of the Teradata Notification Service Package are installed in a Linux
environment, removing the primary version reverts all soft links to the next greatest
version installed. To uninstall all packages, use the command on each installed
tdnotification package.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 31
Chapter 3 Installing Notification Services
Uninstalling the Teradata Notification Service
32 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
CHAPTER 4
b Add the following line to the end of the file, where host is the host name of the time
server:
server host
3 If Teradata Viewpoint is configured in a cluster:
b Add the following line to the end of the file for each Teradata Viewpoint server in the
cluster, excluding the current host, where address is the IP address of another
Teradata Viewpoint server:
peer address
4 Start the NTP service by typing /etc/init.d/ntp start.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 33
Chapter 4 Advanced Configuration Tasks
Configuring LDAP for Teradata Viewpoint
When users are auto-provisioned, the administrator does not need to enter their account into
Teradata Viewpoint. LDAP validation works in conjunction with the Externally
Authenticated? flag on the Add User and Modify User dialog boxes in the User Manager
portlet. If the Externally Authenticated? check box is selected, the user is authenticated
through LDAP when logging in. The Externally Authenticated? check box is automatically
selected when a user is created using auto-provisioning. The first time these users log in to
Teradata Viewpoint, they are validated against the LDAP directory. If their credentials are
valid, a Teradata Viewpoint account is created for them.
Use the LDAP Servers portlet to:
• Add and delete an LDAP configuration in Teradata Viewpoint
• Enable and disable the LDAP after it has been added
• Use the auto-provisioning feature to automatically add users to Teradata Viewpoint on
first login
• Use the role mapping feature to position the new user in Teradata Viewpoint
Prerequisites
• A basic understanding of LDAP
• The URL of the LDAP server, for example, ldap://ldap.acme.com:389
• The username and password of a user or availability of that user to test the configuration
Definitions
Lightweight Directory Access Protocol (LDAP)
Technically an application-protocol, LDAP is frequently used to refer to a directory
server such as Microsoft Active Directory or OpenLDAP.
LDAP Data Interchange Format (LDIF)
A standard, plain-text data interchange format for representing LDAP directory
content and update requests.
Distinguished Name (DN)
The full "path" to a user-entry in LDAP. Every user's DN is, by definition, unique. The
DN consists of its Relative Distinguished Name (RDN) constructed from some
attributes in the entry, followed by the parent entry's DN. Think of the DN as a full
file name and the RDN as a relative filename in a folder. In the following example,
the DN is the entire string.
cn=joec,OU=NorthAmerica,OU=User
Accounts,DC=td,DC=acme,DC=com
34 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Configuring LDAP for Teradata Viewpoint
cn=joec,OU=NorthAmerica,OU=User
Accounts,DC=td,DC=acme,DC=com
Bind
Used for LDAP authentication, binding is an LDAP operation that authenticates a
username and a password.
Service Account
An LDAP service account is an account (username and password) not associated
with a user, but existing for the purposes of binding to LDAP to perform a search of
the directory. Typically, a service account is required when the DN of an
authenticating-user is unknown, and an LDAP search (based on some other attribute
of the user-entry such as sAMAccountName) must first be performed to determine
the user's DN. After the user's DN has been determined, a normal bind using the
user's DN and password is run.
Viewpoint Authenticator
Also referred to simply as the Authenticator, this component of Teradata Viewpoint
runs the authentication process against LDAP, among other actions.
1 You can use the following figure to help you determine which Teradata Viewpoint
authentication configuration mode to use:
• DN pattern bind
• User search with bind
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 35
Chapter 4 Advanced Configuration Tasks
Configuring LDAP for Teradata Viewpoint
36 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
LDAP Servers
memberOf: cn=Sales,ou=Groups,dc=acme,dc=com
memberOf: cn=DBA,ou=Groups,dc=acme,dc=com
...
3 Search the LDAP tree for a user entry where the attribute matches the username value
presented by Joe Customer.
Proceed to the Number of Pattern Binds section.
1 Are all users in Joe's company located at the same Base DN in LDAP?
That is, do all user DNs have the following pattern?
cn=<<USERNAME>>,dc=User Accounts,dc=acme,dc=com
If there are multiple DN patterns, the Teradata Viewpoint Authenticator iterates over
each of the patterns until it finds one that matches the username presented. If the
authenticator does not find a match, it fails to authenticate.
Note: if the number of patterns grows to seven or more, it might be faster to perform a
user search.
3 Select one of the following options in the LDAP Servers portlet:
• If there are fewer than seven DN patterns, select the DN Pattern Bind option.
• If there are seven or more DN patterns, select the User Search option.
LDAP Servers
The LDAP Servers portlet allows you to configure LDAP (Lightweight Directory Access
Protocol) servers to authenticate users and assign user roles in Teradata Viewpoint. The
LDAP Servers portlet displays the names of currently configured LDAP servers or is empty
if an LDAP server is not configured.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 37
Chapter 4 Advanced Configuration Tasks
LDAP Servers
In Teradata Viewpoint, users are assigned roles to organize and control their access to
portlets, metrics, and features. You can use the Roles Manager portlet to assign permissions
to the roles. During the process of adding an LDAP configuration to Teradata Viewpoint, you
can automatically assign Viewpoint roles through auto-provisioning or role mapping.
Auto-provisioning assigns the same roles to all users the first time they access Teradata
Viewpoint. You cannot use auto-provisioning to add or remove roles on subsequent logins.
Role mapping assigns roles to each user based on the user's LDAP group membership or
LDAP attributes. Use role mapping to do the following:
• Assign roles for a new user
• Add roles that were assigned to the user since the last user login
• Remove roles that were removed since the last user login
Only roles already defined using the Roles Manager portlet can be mapped. The Teradata
Viewpoint Administrator can change a role at any time using the Roles Manager portlet.
a [Optional] To search using a specific account, enter a valid service account DN and
password.
If these fields are empty, the Viewpoint portal connects to the LDAP server
anonymously.
38 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
LDAP Servers
11 [Optional] Under Settings Test you can test whether your settings are correct.
b Click Test.
Basic Configuration
Attribute Description
Server Nickname Short name by which this LDAP configuration is referred to in the
LDAP Servers portlet. This name must be 8 characters or less.
Enable server When checked, enables this LDAP configuration as part of the Teradata
Viewpoint authentication process.
Cleared, disables this LDAP configuration as part of the Teradata
Viewpoint authentication process.
URL One or more URLs for this LDAP configuration. The URL must include
the appropriate protocol (ldap:// or ldaps://) as well as the port, for
example, ldap://ldap.acme.com:389. Enter more than one URL
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 39
Chapter 4 Advanced Configuration Tasks
LDAP Servers
Attribute Description
only if all of the URLs point to a similarly configured LDAP server. This
might be the case if you have replicated LDAP servers or a failover
LDAP server that should be used if the primary one is unreachable.
DN Pattern Bind
Attribute Description
Pattern DN patterns used to perform the LDAP user bind attempt. The patterns
are invoked in the order specified, so it is recommended that you put the
patterns that match the most users before those that match fewer users.
For example:
cn={0},OU=User Accounts,DC=acme,DC=com
User Search
Attribute Description
Service Account DN DN of the LDAP service account. The DN must not be surrounded by
parentheses.
Service Account Password of the LDAP service account.
Password
Search Pattern LDAP attribute to match against the username when searching for a user
entry.
If the cn attribute is the username, set to (cn={0}).
If the sAMAccountName attribute is the username, set to
(sAMAccountName={0}).
Search Base Entry that is the base of the subtree containing users. If not specified, the
search base is the top-level context. For example:
OU=User Accounts,DC=acme,DC=com
Search Extent When the Recursive scan check box is selected, searches the entire
subtree rooted at the search base entry. Unselected, requests a single-
level search including only the top level.
40 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Changing a Teradata Viewpoint System Name
Auto-Provisioning
Attribute Description
Turn on auto- Select to turn on auto-provisioning
provisioning
Automatically assign When auto-provisioning is enabled, the newly provisioned user is
these roles automatically added to these roles. This attribute is often set to User.
Related Topics
About Auto-Provisioning and Role Mapping, on page 38
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 41
Chapter 4 Advanced Configuration Tasks
Resetting the Admin User Password
/opt/teradata/viewpoint/bin/vp-control.sh stop
2 Run the dcsadmin command on the primary server:
/opt/teradata/viewpoint/dcs/bin/dcsadmin.sh
3 Type renamesystem on the primary server and press Enter.
4 Enter the number of the system to rename on the primary server and press Enter.
5 Enter the new name on the primary server and press Enter.
• If the name is correct, type Y and press Enter to confirm.
The new system name is applied.
• If the name is incorrect, type N to cancel and then re-enter the name.
6 To exit the dcsadmin shell, type quit on the primary server and press Enter.
7 Restart the Teradata Viewpoint services for all nodes in the Viewpoint cluster:
/opt/teradata/viewpoint/bin/vp-control.sh start
42 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Configuring Teradata Viewpoint to Monitor a Managed Server
In order to send email notifications, Teradata Data Lab requires that version 14.01 or higher
of Teradata Alerts be installed and running on the Teradata Viewpoint server. Additionally,
the Alert Setup portlet must be used to configure the SMTP delivery settings for e-mail.
Teradata Data Lab email notifications for a Teradata Viewpoint user are sent to the email
address set for the user in the Profile portlet or the User Manager portlet.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 43
Chapter 4 Advanced Configuration Tasks
About Configuring Stats Manager
1 Run the TDStats DIP script so that the TDStats database is created and populated.
If the operation is successful, appears. If the operation fails, appears. If you receive
an error, verify that the login credentials are valid and the host can be reached.
8 [Optional] Click Grant to provide Viewpoint data collectors with access to Teradata
Database system resources.
9 Click Apply.
If the operation is successful, appears. If the operation fails, appears. If you receive
an error, verify that the settings are correct and try again.
44 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Configuring Teradata Database to Collect and Analyze Statistics
Collecting Statistics
When a Stats Manager collect job runs, statistics are collected by TDStats.RunCollect
XSP. If the TDStats database does not have permission to collect statistics as an object in the
scope of a collect job, the statistics are not collected and an error is reported. Follow this step
to prevent these errors.
1 To grant TDStats permission to collect statistics on any databases you associate with a
collect job enter the following:
GRANT STATISTICS ON DATABASE TO TDStats;
Analyzing Statistics
Some analyze job options require that Teradata Database query logging (DBQL) features be
enabled. For the analyze job options that you plan to use, you must enable the associated
database feature prior to running the job.
1 Depending on which method you choose to evaluate statistics, select one of these
procedures:
Method Procedure
Evaluate stat usage and Enable query logging with the XMLPLAN, STATSUSAGE, and
staleness and find missing USECOUNT options for the objects being analyzed.
stats to collect
Note: The query logging features should be enabled for at least
and one week prior to running the analyze job.
Use DBQL
Evaluate stats to determine Enable query logging with the USECOUNT option for the objects
if they should be collected being analyzed.
or deactivated
Note: The query logging feature should be enabled, prior to
running the analyze job, for a period of time that is equal to the
period specified in the Recommend stats for deactivation when
inactive for option.
The TDStats database contains a history of all collect and analyze job reports, so you may
need to increase the PERM space available to the TDStats database so that it can hold all of
the information required to run Stats Manager jobs. For information on how to do this, see
the Viewpoint online help.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 45
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
The most basic Teradata Viewpoint cluster provides high availability by including two
Teradata Viewpoint servers, one active and one standby.
Both Teradata Viewpoint instances point at the same a cache database on the active server.
The standby cache database is kept up-to-date with the last minute of data. The DCS service
runs on the active server, with a standby DCS service available on the standby server. Both
servers share a distributed cache to ensure that the state between the Teradata Viewpoint
portals remains consistent.
46 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
A High Usage configuration extends the High Availability configuration by adding Teradata
Viewpoint servers to the cluster. This allows Teradata Viewpoint to scale to thousands of
concurrent users.
The additional Teradata Viewpoint servers run only the Teradata Viewpoint portal and not
the DCS or cache database. Instead, they point to the cluster-wide cache database to access
users, permissions, preferences, and collected data.
The two additional Teradata Viewpoint servers are optional and are not required for high
availability. Even though these additional servers run only the Teradata Viewpoint portal,
they are staged the same as any Teradata Viewpoint server and have the DCS and cache
database installed, but not enabled.
The Advanced configuration provides enhanced cache database performance. This is useful
when a system needs to support high usage.
In this configuration, the Teradata Viewpoint portal does not run on the same machine as
the active cache database. This provides the cache database with additional system resources.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 47
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
48 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
Failure Scenarios
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 49
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
50 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 51
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
52 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 53
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
Clustering Considerations
LAN or WAN
Although using a LAN is recommended, Teradata Viewpoint clusters can be set up over a
WAN. All the data collected by the active Teradata Viewpoint server is sent asynchronously
to the standby Teradata Viewpoint server. Depending on the number and activity of the
Teradata systems being monitored, the amount of data transferred has the potential of
approaching 1 GB an hour. Consider setting up a Teradata Viewpoint cluster spanning a
WAN only if there is adequate bandwidth available.
Load Balancing
To make all Teradata Viewpoint portals in a cluster appear as a single host and to protect
users from a single host failure, you can set up a third-party load balancer to split traffic
between the running Teradata Viewpoint portals.
Configuration of a third-party load balancer is outside the scope of this guide.
54 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
An email is sent for the active DCS that is failing and another one for the active DCS
that is recovering. The standby DCS must be up and running for the alerts to be sent.
Notice: Any data on the server hosting the standby cache database is lost.
See:
Clustering Considerations, on page 54
Note: 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.
Related Topics
Adding Teradata Viewpoint Servers to a Cluster, on page 56
Configuring NTP Time Synchronization, on page 33
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 55
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
You can add additional servers to a cluster to support more end users.
1 Run the following command on the server that is currently hosting the active cache
database:
/opt/teradata/viewpoint/bin/clustersetup.sh
2 Select option 2 to add a server to the cluster.
The cluster setup tool performs the following actions:
• Asks a few simple questions about what hosts to add to the cluster
• 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
The server is added when the script completes, and you are prompted to configure the
new server for clustering.
You can configure the standby cache database to be promoted automatically to become the
active cache database when the active cache database becomes unavailable. A TMS server co-
located with the Teradata Viewpoint server hosting the active cache database prevents
automatic promotions occurring as the result of temporary network outages. If the active and
standby Viewpoint servers are separated by a WAN, a third TMS server that is co-located
with the active Teradata Viewpoint server is required.
1 Download the vpclustermonitor package.
2 Install the package on a co-located TMS server:
rpm -ivh vpclustermonitor-15.10.xx.xx.rpm
3 Run the vpclustermonitor setup script:
/opt/teradata/viewpoint/vpclustermonitor/bin/vpclustermonitor-
setup.sh
4 Answer the questions about which server is hosting the active cache database and which
server is hosting the standby cache database.
5 When the setup script completes, you can tail the vpclustermonitor log file to ensure that
it begins monitoring the active cache database:
/opt/teradata/viewpoint/vpclustermonitor/logs/
vpclustermonitor.log
6 [Optional] Configure email alerts to provide notification when an automatic promotion
occurs.
Related Topics
Setting Up Notifications of Failures and Promotions, on page 54
56 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Teradata Viewpoint Server Clustering Configurations
1 Run the following command on the server that is currently hosting the active cache
database:
/opt/teradata/viewpoint/bin/clustersetup.sh
2 Select option 1 to disable a cluster.
The cluster is disabled and each Viewpoint server points to its own local cache database
and performs its own data collection.
If the active cache database fails, you can promote the standby cache database to become the
active cache database. The Teradata Viewpoint software in the cluster will automatically
begin using the newly promoted cache database. No restarts are required.
After the promotion, there is no longer a standby cache database in the cluster. You must
recreate the standby cache database.
1 Log in to the Teradata Viewpoint server hosting the standby cache database.
2 Type the following command to promote the standby cache database:
/opt//teradata/viewpoint/bin/promote.sh
When an active cache database has failed and the standby cache database has been promoted
to active, you will need to create another cache database to act as the standby. The new cache
database can be created on the Viewpoint server that failed or on another server.
1 Log in to the Teradata Viewpoint server hosting the active cache database.
2 Run the cluster setup script and select the Configure standby server option to
create a cache database on a standby server:
/opt/teradata/viewpoint/bin/clustersetup.sh
The clustersetup script ends with a statement that the status of the operation can be
viewed in the Viewpoint Portal notification area. Do not perform further activities until
you have seen the message that the operation has completed successfully.
3 [Optional] If you want to make the new cache database the active one:
a Log in to the Teradata Viewpoint server hosting the newly created cache database.
b Type the following command to promote the newly created cache database to active:
/opt/teradata/viewpoint/bin/promote.sh
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 57
Chapter 4 Advanced Configuration Tasks
Teradata Notification Service Cluster Configuration
All Viewpoint services in the cluster will be restarted automatically, resulting in a short
outage of the Teradata Viewpoint portal.
Cluster Enabling
The Teradata Notification Service may be running when a Viewpoint cluster is configured.
The service should initially be configured as the notification service for the server that is to
become the primary Viewpoint server.
After configuring the Viewpoint cluster, the Teradata Alerts components running on the
Viewpoint server are restarted in the new clustered configuration. The Teradata Notification
Service automatically detects the configuration change within five minutes and reconfigures
the service to operate in a clustered configuration.
Cluster Disabling
The Teradata Notification Service is aware of the two Viewpoint servers that are part of the
cluster configuration. The initial state of the primary and secondary Viewpoint servers is
maintained by the service.
After disabling the Viewpoint clustering, the Teradata Alerts components running on the
Viewpoint servers are restarted as two standalone Viewpoint servers. The Teradata
58 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Backup for Teradata Viewpoint Databases
Notification Service automatically detects the configuration change within five minutes and
reconfigures the service as the Teradata Notification Service for the initial primary
Viewpoint server. If this is not the desired Teradata Alerts configuration, the service should
be manually configured with the location of the Viewpoint server.
The Teradata Notification Service is aware of the two Viewpoint servers that are part of the
cluster configuration. The initial state of the primary and secondary Viewpoint servers is
maintained by the service. If one of the Viewpoint servers is being replaced, it is
recommended that the Teradata Notification Service be manually reconfigured to connect to
the server that will remain in the cluster.
After the Viewpoint cluster is reconfigured, the Teradata Notification Service reconfigures
itself.
Backup
The Backup portlet allows you to enable and disable automatic Teradata Viewpoint system
backups and to select the daily backup time as well. You can select whether to store the
backup files on the local system or at a network location and set the number of days the
backups are stored. The Teradata Alerts (cam) database is backed up at the same time.
The Backup portlet displays the backup process icon with either a successful completion or
an error for the last attempt and lists the last successful backup date and time.
The Backup dialog box displays if an error occurs during the backup process. To
investigate the error, you can view the backup log file: /opt/teradata/viewpoint/dcs/
logs/backup.log.
You can configure automatic backups, set a data retention length, and enable or disable the
backup process at any time.
From the Backup view, a status displays. If the last backup was successful, the date and time
display, as well as the size of the data that was backed up, using a 1024 byte kilobyte as the
base.
1 From the Teradata Viewpoint portal page, click .
2 Open the Backup portlet.
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 59
Chapter 4 Advanced Configuration Tasks
Backup for Teradata Viewpoint Databases
Option Description
Local Backs up Teradata Viewpoint databases to the local server.
Network Backs up Teradata Viewpoint databases to a networked file server to prevent data loss
in the event of a catastrophic failure.
a. Enter a Host to specify the host system name.
The host is the IP address or DNS name of the networked file server.
b. Enter a Path to specify the absolute path name where the backups are stored on
the host system.
For example, if you are running the command on Linux, it would look something
like this: mount <host>:<path>/path/to/local/mount/point
c. [Optional] Click Test to verify that the login settings are correct.
If the operation is successful, appears. If the operation fails, appears. Verify
the settings are correct and try again.
Note: You can click to view the result of the test.
7 Click Apply.
The changes are saved and backup files are deleted when they are older than the
configured number of days.
You can schedule third-party applications to back up the Teradata Viewpoint backup files.
See the vendor-specific documentation for instructions on how to install the client and
configure and run backup jobs. Teradata Viewpoint supports the following third-party
applications for backup:
• Symantec NetBackup
• IBM Tivoli Storage Manager
• Quest NetVault
1 The third-party application's client software must be installed on the server where the
Teradata Viewpoint backup files reside:
a From the Teradata Viewpoint portal page, click and click Backup on the page to
check the configured backup location.
b Install the backup application's client software in the following location, depending on
which location is selected in Backup:
60 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Uninstalling a Teradata Data Lab Package Manually
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 61
Chapter 4 Advanced Configuration Tasks
Migrating Teradata Viewpoint to a New Server
1 If the Teradata Notification Service is running on a Windows server, stop this service.
2 If the backup files are located on network storage or on a third-party application backup
server, do the following:
a Copy the backup files to /data/backup on the Viewpoint server being restored.
b Ensure that the directory and file permissions within /data/restore are readable
by the postgres Linux user.
3 Run the /opt/teradata/viewpoint/bin/restore.sh script.
4 Validate that the script completed successfully by looking for the message: Restore or
migration performed successfully. If historical data is also
being restored or migrated, progress of this operation can be
viewed in the portal's notification bar.
If the restoration process failed, an error message is displayed instead of the success
message.
5 If the restoration process fails or is interrupted in any manner, fix the problem that
caused the failure and execute these steps again.
6 If you want the Teradata Notification Service to run on a Windows server, start this
service.
62 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Backing Down to a Previous Teradata Viewpoint Version
3 If the migration process fails or is interrupted in any manner, fix the problem that caused
the failure and execute these steps again.
Notice: If backing down to an earlier version of Teradata Alerts, ensure that any applications that
require the version being removed are also backed down.
1 If the Teradata Notification Service is running on a Windows Server, stop the service.
2 If the Teradata Notification Service is running on a Linux Server, stop the tdnotification
service:
/etc/init.d/tdnotification stop
3 Stop all of the Teradata Alerts services on all Teradata Viewpoint servers. Also stop the
Teradata Viewpoint services:
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 63
Chapter 4 Advanced Configuration Tasks
Backing Down to a Previous Teradata Alerts Version
• /etc/init.d/dcs stop
• /etc/init.d/tmsmonitor stop
• /etc/init.d/viewpoint stop
• /etc/init.d/camalert stop
• /etc/init.d/tdactivemq stop
4 Restore the last successful backup of the previous version of the Teradata Alerts database.
See Restoring a Teradata Viewpoint Database.
The duration of this process varies and is based on the size of the database. If you have a
clustered environment, perform the restore against the primary database server.
5 If the Teradata Notification Service is running on a Windows Server, uninstall the
Teradata Notification Service.
6 If the Teradata Notification Service for Linux is running on a Linux Server, uninstall the
tdnotification1500 package.
7 Uninstall the Teradata Alerts RPMs on all Teradata Viewpoint servers.
See Manually Uninstalling Teradata Alerts Packages.
8 Reinstall the previous version of Teradata Alerts RPMs on all Teradata Viewpoint servers.
9 If the Teradata Notification Service was installed on a Windows Server, install and
configure the previous version of the Teradata Notification Service for Windows.
a Move the programs from the usrcmd folder of the current version to the usrcmd
folder of the previous version.
The current usrcmd folder is located at:
installation folder\Teradata\Client\version\Teradata
Notification Service\usrcmd
b Move the BTEQ scripts from the sql folder of the current version to the sql folder of
the previous version.
The sql folder is located at:
installation folder\Teradata\Client\version\Teradata
Notification Service\sql
c Start the previous version of the Teradata Notification Service on the Windows Server.
10 If the Teradata Notification Service for Linux was installed on a Linux Server, install the
previous version of the Teradata Notification Service for Linux.
a If tdnotification1410 or tdnotification1400 is already installed, it is now the current
package. If it is not installed, install the prior version manually.
b Start the previous version of the Teradata Notification Service on the Linux Server:
/etc/init.d/tdnotification start
11 Start the previous version of the Teradata Alerts services on all Teradata Viewpoint
servers. Also start the Teradata Viewpoint services:
• /etc/init.d/tdactivemq start
64 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10
Chapter 4 Advanced Configuration Tasks
Manually Uninstalling Teradata Alerts Packages
• /etc/init.d/camalert start
• /etc/init.d/dcs start
• /etc/init.d/tmsmonitor start
• /etc/init.d/viewpoint start
Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10 65
Chapter 4 Advanced Configuration Tasks
Manually Uninstalling Teradata Alerts Packages
66 Teradata Viewpoint Installation, Configuration, and Upgrade Guide for Customers, Release 15.10