Teradata Alerts Installation, Configuration, and Upgrade Guide Release B K May 2013

Transcription

1 Teradata Alerts Installation, Configuration, and Upgrade Guide Release B K May 2013

2 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, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast, Gridscale, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision Experts, "Teradata Labs" logo, "Teradata Raising Intelligence" logo, Teradata ServiceConnect, Teradata Source Experts, "Teradata The Best Decision Possible" logo, The Best Decision Possible, 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 Hadoop, 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. 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 Quest Software, 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. Red Hat is a trademark of Red Hat, Inc., registered in the U.S. and other countries. Used under license. 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 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 by Teradata Corporation. All Rights Reserved.

3 Table of Contents Preface...5 Revision History...5 Audience...5 Related Documents...5 Chapter 1: Overview...7 About Teradata Alerts...7 Overview of Teradata Alerts Installation...7 Basic Installation...7 Teradata Viewpoint Cluster Installation...8 Software Components...9 Dependencies...10 Network Ports...10 Teradata Viewpoint Server Requirements...10 Linux Server Requirements...10 Windows Server Requirements...11 Supported Teradata Database Versions...11 Chapter 2: Installing Notification Services...13 Downloading the Teradata Alerts Notification Software...13 Installing Teradata Notification Service for Windows...13 Preparing for Installation of Notification Service...13 Installing Notification Service Software on a Windows Server...14 Configuring the Teradata Viewpoint Server Location...15 Starting and Stopping the Teradata Notification Service (Windows)...15 Setting Up the BTEQ Scripts and Run Program Executables...16 Installing Teradata Notification Service for Linux...16 Preparing for Installation of Notification Service for Linux...16 Installing Software on a Linux Server...17 Installing Teradata Notification Service Interactively...17 Configuring the Teradata Viewpoint Server Location...18 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

4 Table of Contents Starting and Stopping the Teradata Notification Service (Linux)...19 Setting Up the BTEQ Scripts and Run Program Executables...19 Uninstalling the Teradata Notification Service...20 Chapter 3: Administrative Tasks...21 About Starting and Stopping the Teradata Alerts Services...21 Backing Down to a Previous Teradata Alerts Version...22 About Backing Up Alerts Database...23 Restoring Teradata Alerts Database...23 Manually Uninstalling Teradata Alerts Packages...25 Teradata Notification Service Cluster Configuration...26 Cluster Enabling...26 Cluster Disabling...26 About Replacing a Viewpoint Server...27 Chapter 4: Upgrading Software...29 About Upgrading Teradata Alerts Software...29 Creating an Incident...29 Finding the PUT Version Running on the System...30 Determining the Latest PUT Release...30 Downloading New PUT Packages...30 Installing and Upgrading PUT...32 Installing PUT...32 Upgrading PUT...32 Checking for Space on the Node...33 Creating a Target Directory...33 Software Package Downloads...33 Downloading Software Packages...33 Verifying the Previous Database Backup...35 Clustering Prerequisites...35 Identifying the Primary Cache Database Server...35 Stopping the Teradata Viewpoint Services...35 Installing Software Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

5 Preface Revision History Date Release Description May Updated to reflect the changes in Teradata Alerts Re-organized book structure. October Updated to reflect the changes in Teradata Alerts Audience This guide is intended for use by: Customers Teradata Customer Services Related Documents Access the Teradata Information Products web site to view or download additional documentation related to this product. 1. Go to 2. Under the Online Publications subcategory, click General Search. 3. Search on the title or publication ID. Title Publication ID Parallel Upgrade Tool (PUT) Reference B Teradata Viewpoint User Guide B Teradata Viewpoint Configuration and Upgrade Guide B Teradata Alerts User Guide B Teradata Alerts Installation, Configuration, and Upgrade Guide B Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

6 Preface Related Documents 6 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

7 CHAPTER 1 Overview About Teradata Alerts Teradata Alerts is a software product that integrates with other Teradata applications to perform shared alert delivery actions through these delivery mechanisms: notifications Simple Network Management Protocol (SNMP) traps SQL queries Basic Teradata Query (BTEQ) scripts provided by the customer Executable programs provided by the customer Teradata Alerts is available for: New customers looking to add Teradata Alerts to their existing Teradata Viewpoint installation. Customers who have an older version of Teradata Alerts installed at their site and want to upgrade The software that runs BTEQ scripts and Run Program executables is installed on a Windows or Linux Server. The remaining Teradata Alerts components are installed on a Teradata Viewpoint server. Teradata Alerts is used to configure shared alert actions for the following Teradata applications: Viewpoint (Teradata Systems) TASM (Workload Designer) Teradata Multi-System Manager (MSM Setup) Server Management (Server Management) Overview of Teradata Alerts Installation Basic Installation In a basic installation, Teradata Alerts components are installed on a single Teradata Viewpoint server, Windows Server, and Linux Server. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

8 Chapter 1 Overview Overview of Teradata Alerts Installation Figure 1: Basic Installation Components Teradata Viewpoint Server Windows Server Linux Server Cache DB Portlets Alert Setup Alert Viewer Notification Service Notification Service Messaging Service Alert Service Optional (Required for BTEQ and Run Program actions) Optional (Required for BTEQ and Run Program actions) SM_0031 Teradata Viewpoint Cluster Installation Teradata Alerts is clustered when Viewpoint is configured in a cluster. For instructions on how to configure services in a Viewpoint cluster, refer to Teradata Viewpoint Configuration and Upgrade Guide. In a cluster configuration, the Teradata Alerts components fail over to the warm standby cache database, if the database instance is promoted. Alert and messaging services are active on both Teradata Viewpoint servers. If one of the alert services fails, the secondary alert service automatically continues to process alerts. If one of the messaging services fails, clients are automatically connected to the secondary messaging service. 8 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

9 Chapter 1 Overview Software Components Figure 2: Teradata Alerts Cluster Installation Components Teradata Viewpoint Server Teradata Viewpoint Server Windows Server Linux Server Warm Standby Cache DB Cache DB Portlets Alert Setup Alert Viewer Portlets Alert Setup Alert Viewer Notification Service Notification Service Messaging Service Messaging Service Alert Service Alert Service Optional (Required for BTEQ and Run Program actions) Optional (Required for BTEQ and Run Program actions) SM_0032 Software Components Table 1: Software Components Component Cache DB Alert service Messaging service Teradata Notification Service for Windows Teradata Notification Service for Linux Alert Setup portlet Alert Viewer portlet Description Local repository instance used by the Teradata Viewpoint server. The database used by the Teradata Alerts is the cam database. Java daemon that processes alerts. Installed as the camalert service. Java Message Service (JMS) provider (Apache ActiveMQ) that allows message exchange between the software components. Installed as the tdactivemq service. [Optional] Service that executes BTEQ scripts and Windows executable programs provided by the customer. Installed on a Windows Server provided by the customer. Only required if running BTEQ scripts or executable programs on Windows. [Optional] Service that executes BTEQ scripts and executable Linux programs provided by the customer. Installed on a Linux Server provided by the customer. Only required if running scripts or executable programs on Linux. Portlet used to configure Teradata Alerts. Portlet used to view logged alerts. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

10 Chapter 1 Overview Dependencies Dependencies Network Ports Teradata Alerts uses the following network ports: Table 2: Network Ports Incoming 80 (HTTP) 443 (HTTPS) 5432 (Cache Database) (Messaging) Outgoing 25 SMTP (default)* 465 SMTP over SSL (default)* 162 SNMP Trap *You can change the outgoing SMTP ports by selecting Delivery Settings > in the Alert Setup portlet. Teradata Viewpoint Server Requirements Teradata Alerts must be installed on a Teradata Viewpoint server running Teradata Viewpoint. Hardware Requirements There are no additional hardware requirements beyond those specified for Teradata Viewpoint. Software Dependencies To run Teradata Alerts, the following software must be installed on the Teradata Viewpoint server: SuSE Linux Enterprise 10, Service Pack 3 or later version net-snmp Teradata JDK 6 PostgreSQL Server Teradata Viewpoint or later Linux Server Requirements Teradata Notification Service for Linux is needed to run the BTEQ scripts and executable programs on a Linux server and must be installed on a customer provided Linux server. If the BTEQ and Run Program alert actions are not needed on Linux, Teradata Notification Service for Linux is not required. Hardware Requirements There are no additional hardware requirements beyond those specified for Teradata Tools and Utilities client packages for SuSE Linux. 10 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

11 Chapter 1 Overview Supported Teradata Database Versions Software Dependencies SuSE Linux Enterprise 10, Service Pack 3 or later version or SuSE Linux Enterprise 11 Java SE Runtime Environment 6 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. Windows Server Requirements Teradata Notification Service for Windows is needed to run the BTEQ scripts and executable programs on a Windows server, and must be installed on the Windows Server. If the BTEQ and Run Program alert actions are not needed on Windows, Teradata Notification Service for Windows is not required. Hardware Requirements There are no additional hardware requirements beyond those specified for Teradata Tools and Utilities client packages for Windows. Software Requirements One of the following Microsoft Windows operating systems: Windows XP Windows Server 2003 Windows Vista Windows Server 2008 Windows Server 2008 R2 Windows 7 The following Java SE Runtime Environment: 32-bit Java SE Runtime Environment 6 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 Windows system clock must be synchronized with the clock on the Viewpoint server. Supported Teradata Database Versions Teradata Alerts has limited interaction with Teradata Database. The three components that interact with the Teradata Database are: BTEQ alert actions Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

12 Chapter 1 Overview Supported Teradata Database Versions SQL alert actions Alerts processed by the Teradata Viewpoint alert request data collector Teradata Notification Service for Windows and Teradata Notification Service for Linux can execute BTEQ scripts. The version of BTEQ that is installed on the Windows Server or Linux Server must be compatible with the version of the Teradata Database that the BTEQ scripts are executing against. Teradata Alerts running on the Viewpoint Server executes SQL alert actions using the Teradata JDBC driver. The queries entered by the administrator must be compatible with the Teradata Database where the queries will be executed. Teradata Viewpoint alert request data collector monitors the dbcmngr.alertrequest and dbcmngr.monitorrequest tables for alert requests. Teradata Alerts supports the same versions of the Teradata Database that Viewpoint monitoring supports. 12 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

13 CHAPTER 2 Installing Notification Services Downloading the Teradata Alerts Notification Software 1 Access the Teradata Software Server: at 2 Select Certified Configs. 3 On the menu on the left, select Software Patches > Teradata Applications. 4 At Sub Category, select Common Alerting Mechanism. 5 At Release, select Click Submit. 7 Select the Notification Service package for Windows or Linux as needed. 8 At please enter the following information to download, enter your user name, address, site ID, and the change control number. 9 Click Submit. 10 Click Download. 11 Extract the files from the downloaded archive. 12 Copy the files to the servers where the installation or upgrade is to be performed. Installing Teradata Notification Service for Windows To use BTEQ and Run Program alert actions on Windows, first install the Teradata Notification Service. Install the service on a Windows server and configure the software with information specific to your Teradata Viewpoint server. Preparing for Installation of Notification Service Before installing Teradata Notification Service, ensure the following: Teradata Viewpoint server is set up and running. Alert Services are running on the Viewpoint Server. You have the hostname or IP address of the Teradata Viewpoint server. You have installed a 32-bit Java Runtime Environment 6 or greater. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

14 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Windows The JAVA_HOME environment variable is defined at the System (not at the User) level. This is important because the Teradata Notification Service runs as a service. The process varies depending on the Windows operating system. You must log on as an administrator to change System-level environment variables. 1 Depending on your version of the Windows operating system, do the following: Option Windows operating systems prior to Windows 7 Windows 7 operating system Description a. From Control Panel, double-click the System icon to view and change system settings. b. Select the Advanced tab. a. From Control Panel, select System and Security. b. Select System. c. Select Advanced system settings. 2 Click Environment Variables. 3 Click New, located under System variables, to set the JAVA_HOME environment variable. Installing Notification Service Software on a Windows Server 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_i 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_i xx in the current directory. 5 Navigate to the teradatacam Windows_i 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: a b c d Accept the license agreement. [Optional] Change the destination folder. Specify the system name of the Teradata Viewpoint server. This can be the hostname defined by DNS or an IP address. Click Install. 14 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

15 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Windows e f Select Start the Teradata Notification Service now. Click Finish. The software is installed at drive:\program Files (x86)\teradata\client \14.10\Teradata Notification Service Configuring the Teradata Viewpoint Server Location 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\14.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. Starting and Stopping the Teradata Notification Service (Windows) The Teradata Notification Service is installed as a Windows Service named Teradata Notification Service. The default installation procedure configures the service to automatically start when the system reboots. You can start and stop the service using the Services Administration tool in Windows. Perform the following procedure to ensure that the Teradata Notification Service is running. 1 In a command prompt window, type: services.msc 2 Locate the Teradata Notification Service. 3 Verify that the Status column for the service displays Started. 4 In the Name column, double-click Teradata Notification Service. The Teradata Notification Service Properties dialog box appears. 5 Click OK. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

16 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Linux 6 Change the Service status, if it has not Started. a b c Ensure the Startup type is Automatic. Click Apply. Click Start. Setting Up the BTEQ Scripts and Run Program Executables 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. 1 Place the BTEQ scripts in the following folder relative to the installation location: installation folder\teradata\client\14.10\teradata Notification Service\sql 2 Place the programs you want to run in the following folder relative to the installation location: installation folder\teradata\client\14.10\teradata Notification Service\usrcmd Installing Teradata Notification Service for Linux Preparing for Installation of Notification Service for Linux Before installing Teradata Notification Service, ensure the following: Teradata Viewpoint server is set up and running. Alert Services are running on the Viewpoint Server. You have the hostname or IP address of the Teradata Viewpoint server. You have installed a 64-bit Java Runtime Environment 6 or greater. The JAVA_HOME environment variable is defined in the default profile so that once the software is installed, the service is able to locate the Java Runtime Environment. Perform the steps below the change this system setting. 1 Log in as root. 2 Edit /etc/profile.local by adding a line to define JAVA_HOME where you have installed the JRE. For example, if you have installed the Java Runtime Environment in /home/jre6 type: export JAVA_HOME=/home/jre6 16 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

17 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Linux 3 Source the updated file to pick up the JAVA_HOME definition.. /etc/profile.local Installing Software on a Linux Server 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 tdnotification1410 package onto the server. 3 After the installation, manually configure the software with the location of the Viewpoint server. Installing Teradata Notification Service Interactively Use these steps to perform an interactive installation or upgrade of Teradata Notification Service on a Linux server. This procedure is only used when PUT is not available. Note that xx represents the version of the software you are installing or upgrading. 1 Download the software from the Teradata Software Server: /TSFS/. 2 Copy the rpm file tdnotification1410 SLES10_x xx-1.rpm to the server where the installation or upgrade is to be performed. 3 Log on to your Linux server as the root user. 4 Change to the directory containing the rpm file. 5 Verify that JAVA_HOME is defined: echo $JAVA_HOME 6 Set the CAM_INTERACTIVE_INSTALL environment variable to indicate the installation is interactive: export CAM_INTERACTIVE_INSTALL=1 7 Install the rpm: rpm -Uvh tdnotification1410 SLES10_x xx-1.rpm. 8 When prompted, enter the name of the Viewpoint server. 9 When prompted, enter the name of the service user, or accept the default of camuser. The service runs with the user id of the service user account. See Service User for more information. The software is installed in the following location: /opt/teradata/client/14.10/cam/tdnotification A symbolic link is created to the installation directory: Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

18 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Linux Service User /opt/teradata/client/cam/tdnotification -> /opt/teradata/client/ 14.10/cam/tdnotification If you provided the name of the Viewpoint server, the software is now configured and ready to start: /etc/init.d/tdnotification start 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. Configuring the Teradata Viewpoint Server Location 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 18 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

19 Chapter 2 Installing Notification Services Installing Teradata Notification Service for Linux Starting and Stopping the Teradata Notification Service (Linux) The Teradata Notification Service is installed as a Linux service and is installed as the tdnotification service. The default installation procedure configures the service to automatically start when the system reboots. The Teradata Notification Service for Linux has an init script called tdnotification, located in the /etc/init.d directory. The init scripts support the following command arguments: start Starts the service. If the service is already running, a new instance is not started. stop Stops the service. restart Stops and restarts the service. status Checks if the service is running. 1 Type /etc/init.d/tdnotification followed by a space and the command argument. For example: To start the tdnotification service: /etc/init.d/tdnotification start To stop the tdnotification service: /etc/init.d/tdnotification stop To restart the tdnotification service: /etc/init.d/tdnotification restart To check if the tdnotification service is running: /etc/init.d/tdnotification status Setting Up the BTEQ Scripts and Run Program Executables 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 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 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

20 Chapter 2 Installing Notification Services Uninstalling the Teradata Notification Service During the installation, the following symbolic links are created: /opt/teradata/client/14.10/cam/tdnotification/sql -> /opt/teradata/ client/cam/sql /opt/teradata/client/14.10/cam/tdnotification/usrcmd -> /opt/ teradata/client/cam/usrcmd 1 Log in to the server as the root user. 2 Place the BTEQ scripts in: /opt/teradata/client/cam/tdnotification/sql 3 Ensure BTEQ scripts have at least 744 file permissions. 4 Place the programs you want to run in: /opt/teradata/client/cam/tdnotification/usrcmd 5 Ensure the programs have at least 755 file permissions. Uninstalling the Teradata Notification Service 1 Uninstall the Teradata Notification Service: Operating System Windows Linux Description Use Windows Control Panel to uninstall the Teradata Notification Service. Use the following command: rpm -e tdnotification1410 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. 20 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

21 CHAPTER 3 Administrative Tasks About Starting and Stopping the Teradata Alerts Services Teradata Alerts contains the following services: tdactivemq Messaging service that allows message exchanges between the Teradata Alerts components camalert Alert service that processes events and alerts Each service has an init script on the Teradata Viewpoint server located in the /etc/ init.d directory. The init scripts support the following command arguments: start Starts the service. If the service is already running, a new instance is not started. stop Stops the service. restart Stops and starts the service. status Checks if the service is running. For example, to start the alert service: /etc/init.d/camalert start To stop the alert service: /etc/init.d/camalert stop To restart the alert service: /etc/init.d/camalert restart To check if the alert service is running /etc/init.d/camalert status Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

22 Chapter 3 Administrative Tasks Backing Down to a Previous Teradata Alerts Version Backing Down to a Previous Teradata Alerts Version If an upgrade of Teradata Alerts produces an undesired or unanticipated effect, the following steps allow you to back the system down to the previously installed version. Note that xx represents the specific version of the software. This procedure is only for backing down from Teradata Alerts xx to release xx. For instructions on backing down from Teradata Alerts xx to release xx or earlier, refer to Teradata Viewpoint Configuration Guide. Caution: 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: /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 Teradata Alerts 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 tdnotification1410 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: 22 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

23 Chapter 3 Administrative Tasks About Backing Up Alerts Database installation folder\teradata\client\version\teradata Notification Service\usrcmd b c 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 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 b If tdnotification1400 is already installed, it is the current package. If it is not installed, install the prior version manually. 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 /etc/init.d/camalert start /etc/init.d/dcs start /etc/init.d/tmsmonitor start /etc/init.d/viewpoint start About Backing Up Alerts Database Teradata Viewpoint Data Collection Service (DCS) automatically creates snapshot dumps of the Teradata Alerts ("cam") database, along with the Teradata Viewpoint databases, on a daily basis. The backup process can be managed with the Backup portlet. Refer to the Teradata Viewpoint Configuration Guide for more information. Restoring Teradata Alerts Database The following procedure restores the Teradata Alerts ("cam") database from a backup made by Viewpoint 14.0 or later. This procedure restores the cam database only. For instructions on restoring Teradata Viewpoint databases along with the Teradata Alerts database, refer to Teradata Viewpoint Configuration Guide. Starting with Teradata Viewpoint 14.0, the backup is performed incrementally for alert log data to improve the overall speed of the backup process. Because log data is backed up incrementally, smaller portions of the data can be restored. You can choose to restore: Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

24 Chapter 3 Administrative Tasks Restoring Teradata Alerts Database Configuration data: restores Teradata Alerts configuration data. Alert log data is not restored. This option drops the cam database and creates it again. Caution: This option deletes all collected data in cam because it creates a new cam database. Current data: restores alert log data in cam for the current week. Data from previous weeks is not restored. Historical data: restores alert log data in cam from previous weeks. Alert log data from the current week is ignored. Everything (default): restores all data in cam. This option drops the database and creates it again. When restoring a backup in a clustered environment, perform the following restoration steps on the primary server. 1 If the Teradata Notification Service is running on a Windows or Linux servers, stop the service. 2 Stop the Teradata Alerts and Viewpoint services on all Teradata Viewpoint servers: /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 3 If the backup files are located on network storage, perform the following steps: a b Mount the remote host directory on the Teradata Viewpoint server. The remote directory should be the root directory for the backups and should contain the database directory (cam). mkdir /data/restore mount remote host:remote directory /data/restore In the /etc/opt/teradata/cam/cam.properties file, define the value of the backup.dir property to /data/restore. c Ensure the directory and file permissions within /data/restore are readable by the postgres Linux user. 4 If the backup files are located on a backup server of a third-party application, perform the following steps: a b c Make a directory on the Teradata Viewpoint server to store the files from the backup server: mkdir /data/restore Copy the files from the backup server to this directory on the Teradata Viewpoint server. This directory should contain the database directory (cam). In the /etc/opt/teradata/cam/cam.properties file, define the value of the backup.dir property to /data/restore. 24 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

25 Chapter 3 Administrative Tasks Manually Uninstalling Teradata Alerts Packages d Ensure the directory and file permissions within /data/restore are readable by the postgres Linux user. 5 Run the restore script as follows: For configuration data: /opt/teradata/cam/alert/bin/camrestore.sh conf For current data: /opt/teradata/cam/alert/bin/camrestore.sh curr Note: This option does not attempt to create the cam database and tables, therefore it should be performed after the database has been created by running the conf option. For historical data: /opt/teradata/cam/alert/bin/camrestore.sh hist Note: This option does not attempt to create the cam database and tables, therefore it should be performed after the database has been created by running the conf option. Everything (default): /opt/teradata/cam/alert/bin/camrestore.sh 6 Validate that the script completed successfully by looking for the message RESTORATION OF ALERTS ON server COMPLETED SUCCESSFULLY! If the restoration process failed, an error message is displayed instead of the success message. If the restoration process fails or is interrupted in any manner, fix the problem that caused the failure and execute these steps again. 7 If the backup files are located on network storage, edit the /etc/opt/teradata/cam/ cam.properties file to change the value of the backup.dir property back to / data/backup. 8 If the backup was generated from an earlier version of Teradata Alerts, run /opt/ teradata/cam/alert/bin/setupdb.sh to update the cam repository for Start the Teradata Alerts and Viewpoint services on all Teradata Viewpoint servers: /etc/init.d/tdactivemq start /etc/init.d/camalert start /etc/init.d/viewpoint start /etc/init.d/tmsmonitor start /etc/init.d/dcs start 10 If the Teradata Notification Service was running on a Windows or Linux server, start the service. Manually Uninstalling Teradata Alerts Packages If necessary, you can uninstall the Teradata Alerts packages manually. 1 Use the rpm e command to uninstall each package. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

26 Chapter 3 Administrative Tasks Teradata Notification Service Cluster Configuration For example, to uninstall the camportlets package, run the following command: rpm -e camportlets 2 Uninstall the packages in the following order: camportlets camalert tdactivemq Teradata Notification Service Cluster Configuration 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. 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. 26 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

27 Chapter 3 Administrative Tasks Teradata Notification Service Cluster Configuration After disabling the Viewpoint clustering, the Teradata Alerts components running on the Viewpoint servers are restarted as two standalone Viewpoint servers. The Teradata 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. About Replacing a 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. Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

28 Chapter 3 Administrative Tasks Teradata Notification Service Cluster Configuration 28 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10

29 CHAPTER 4 Upgrading Software About Upgrading Teradata Alerts Software Teradata Alerts software can be upgraded by customers. Creating an Incident You must obtain an Incident number from Teradata at Your Service prior to performing any software upgrades. 1 Log on to Teradata at Your Service. 2 On the Incidents page, click Create. 3 Make the following appropriate selections: Note: Click the green arrows to move forward or back in the selection screens. Option Site Incident Type Problem Type Synopsis Description The site where the activity will be performed. A list of the Incident Type items: Incident Type can be either a Problem or a Question. Priority is the severity of the outage. Product Area indicates which part of the system is going to be upgraded. A list of Problem Types related to the Incident Type selected. A short Synopsis of the activity being performed, and a Description with complete details. 4 Click Submit the Incident. 5 Click OK to confirm the submission of the incident. The incident is added to the list of Incidents. The Status shows Pending (a blue circle) until Customer Services approves the activity at which time the Status becomes Active (a green circle). Teradata Alerts Installation, Configuration, and Upgrade Guide, Release

30 Chapter 4 Upgrading Software Finding the PUT Version Running on the System Finding the PUT Version Running on the System 1 From your PC, open a communication window to any server in the system. 2 Issue one of the following commands for your system configuration: System Configuration Multiple nodes (MPP) with PDE installed Single node (SMP) or nodes without PDE installed Command psh rpm -qa TDput rpm -qa TDput Note: In PUT version and earlier, files and pathnames are named with or contain the phrase "NCRput." In PUT version that phrase changed to "TDput." If you are working with an earlier version your command must specify "NCRput," not "TDput." The response from each server will be similar to: all 2 nodes: TDput Normally the version is the same on all servers, but at times they may differ. 3 Record the latest PUT version number. Determining the Latest PUT Release PUT is updated periodically. You must always use the latest version of PUT. You can find the latest version on the Teradata Software Server at 1 Compare the version of PUT installed on the Master Node with the version on the Teradata Software Server. Note: If the versions are the same, no action is required. You will not need to download the PUT software, nor transfer those files to the Master Node and update the PUT software on the nodes. 2 If the version on the Teradata Software Server is later than the installed version, update the Master Node and any other nodes running PUT with the latest version. Downloading New PUT Packages This task needs to be performed only if your version of PUT needs to be updated. 1 On your Windows PC, open a web browser and go to Your Service at tays.teradata.com and log in. 2 Click Software Downloads > Certified Configs. 3 On the Certified Configuration Help screen, click Parallel Upgrade Tool (PUT) under Software Patches in the left pane. 30 Teradata Alerts Installation, Configuration, and Upgrade Guide, Release 14.10