Installing Ecosystem Manager Client Package on a Linux Teradata Server - Teradata Ecosystem Manager

Teradata® Ecosystem Manager Installation, Configuration, and Upgrade Guide for Customers
Product
Teradata Ecosystem Manager
Release Number
16.20
Published
December 2020
Language
English (United States)
Last Update
2020-12-23
dita:mapPath
ntu1488477755124.ditamap
dita:ditavalPath
3203_ICUCustomer_em_1610.ditaval.ditaval
dita:id
B035-3203
Product Category
Analytical Ecosystem
In addition to installing the client package as described here, Ecosystem Manager provides a REST API for installation and configuration of certain types of publisher and agent client packages. For reference, go to: http://EM server host:port/swagger-ui.html#!/server-controller/updateServerUsingPUT. For example: http://wario:8090/swagger-ui.html#!/server-controller/updateServerUsingPUT. For API examples, see: Teradata® Ecosystem Manager API Reference.
  1. Download the Client Packages to a folder on the server.
  2. Start PUT.
  3. Log on to the system as a root user.
  4. In the main screen, select Install/Upgrade Software and click Next.
  5. In the Configuration screen, select Typical Configuration and click Next.
  6. In the Network Subnet Selection screen, select 127.0.0.0 (LOOPBACK) from the list, and click Next.
  7. In the Node screen, make sure the selected node name is Localhost(LINUX), and click Next.
    If a message appears, click Ignore.
  8. In the Select Spool Area for Linux Nodes screen click Next to accept the default location.
  9. In the Package Source Section screen, enter or select the following path, and then click Next.
    /var/opt/teradata/packages/EM/EM-16200000
  10. In the Group Nodes screen, click Next to accept the automatically selected node.
  11. In the Select Packages screen, add the JDK and Client packages:
    1. teradata-jdk8__sles_x8664.1.8.0_xx-tdc2.tar.gz
    2. em-publisher-linux64__linux_x86_64.16.20.xx.xx-1.tar.gz
    3. Appropriate agent package:
    Agent Package Server
    em-agent-linux64_linux86.16.20.xx.xx-1.tar.gz Data Mover (DMC)
    em-unitydirector-agent__sles_x86_64.16.20.xx.xx-1.tar.gz Unity
    em-agent-linux64_linux86.16.20.xx.xx-1.tar.gz Unity Source Link (USL)
    em-viewpoint-agent__sles_x86_64.16.20.xx.xx-1.tar.gz Viewpoint (VP)
  12. Accept the default options for all subsequent steps.
  13. In Select Teradata Startup Option, select Automatically Start Teradata after a system reboot and click Next to finish the installation.
  14. If you installed Unity, run the configuration script to set the following parameters:
    /opt/teradata/client/em/bin/emserviceconfig.sh
    • PRIMARY EM SERVER HOSTNAME(BROKER)
    • FAIL-OVER EM SERVER HOSTNAME(BROKER)
    • ECOSYSTEM ID
    • EM DB USER(EMEM) PASSWORD
    • UNITY SERVER HOSTNAME
    • Unity Admin User Name
    • Unity Admin User Password
    • UNITY CLUSTER TDPID
    • [Optional] Override UNITY CLUSTER TDPID (Y/N)
      This updates the existing Unity Cluster TDPID and deletes the history of the Unity Cluster TDPID in both the Ecosystem Manager and Unity repository.
  15. [Optional] Restart Unity if running for the first time or if you selected to override the Unity Cluster TDPID:
    ./emserviceconfig.sh bond Wario DatacenterA em tara admin admin UnityCluster
  16. Make sure Ecosystem Manager Client services are running:
    /opt/teradata/client/em/bin/emstatus.sh
  17. If the em-agent-linux package is installed on a Data Mover server, restart both Data Mover services (daemon and agent) for integration.