16.00 - Installing the Ecosystem Manager Client Package on HP-UNIX - Teradata Ecosystem Manager

Teradata Ecosystem Manager Installation, Configuration, and Upgrade Guide for Customers

prodname
Teradata Ecosystem Manager
vrm_release
16.00
created_date
December 2016
category
Configuration
Installation
featnum
B035-3203-116K
  1. Install JRE 1.7 if not installed.
  2. Download the Client Packages to a folder on the server.
  3. Copy the following packages from the Teradata Software Server or from the Teradata Ecosystem Manager media to the /opt/ folder:
    • em-publisher-hppa64__hppa_ia64.16.00.xx.xx-1.tar.gz
    • em-agent-hppa64__hppa_ia64.16.00.xx.xx-1.tar.gz
  4. Unzip the following files: gunzip em-publisher-hppa64__hppa_ia64.16.00.xx.xx-1.tar.gz

    gunzip em-agent-hppa64__hppa_ia64.16.00.xx.xx-1.tar.gz

  5. Locate these files: em-publisher-hppa64__hppa_ia64.16.00.xx.xx-1.tar

    em-agent-hppa64__hppa_ia64.16.00.xx.xx-1.tar

  6. Extract the tar files: tar -xvf em-publisher-hppa64__hppa_ia64.16.00.xx.xx-1.tar

    tar –xvf em-agent-hppa64__hppa_ia64.16.00.xx.xx-1.tar

  7. Locate these files: em-publisher-16.00.xx.xx.bin

    em-agent-16.00.xx.xx.bin

  8. Install the binary files: chmod +x em-*.bin

    ./ em-publisher-16.00.xx.xx.bin

    ./ em-agent-16.00.xx.xx.bin

  9. Configure the Ecosystem Manager services parameters: /opt/teradata/client/em/bin/emserviceconfig.sh
    This configures the following parameters:
    • JRE HOME (1.7)
    • PRIMARY EM SERVER HOSTNAME(BROKER)
    • FAIL-OVER EM SERVER HOSTNAME(BROKER)
    • ECOSYSTEM ID
    • RESOURCE SUB-CATEGORY
    For single-system environments, use the same value for the Primary and Fail-Over Server Hostname parameters. For resource subcategories, use one of these server values:
    Value Description
    RS Replication
    BI Business Intelligence
    BAR Backup, Archive, and Restore
    LS Load
    TD Teradata
    APP Application
    ETL Extract/Transform/Load
    BUS Message Bus
    DMC Data Mover
    Unknown Self-registered
    USL Unity Source Link
    The following example shows svr1 and svr2 as Ecosystem Manager servers, eco1 is the ecosystem, and APP is the resource sub-category:

    /opt/teradata/client/em/bin/emserviceconfig.sh /usr/java7/bin/java svr1 svr2 eco1 APP

    Parameter Setting
    JRE HOME (1.7) /usr/java7/bin/java
    PRIMARY EM SERVER HOSTNAME(BROKER) svr1
    FAIL-OVER EM SERVER HOSTNAME(BROKER) svr2
    ECOSYSTEM ID eco1
    RESOURCE SUB-CATEGORY APP
  10. Disable TPT operational metadata delivery on the Ecosystem Manager Repository.
  11. Check the Ecosystem Manager services status: /opt/teradata/client/em/bin/empublisher status

    /opt/teradata/client/em/bin/ emcontrolagent status

    /opt/teradata/client/em/bin/emmonitor status

  12. Stop Ecosystem Manager services: /opt/teradata/client/em/bin/empublisher stop

    /opt/teradata/client/em/bin/ emcontrolagent stop

    /opt/teradata/client/em/bin/emmonitor stop

  13. Start Ecosystem Manager services: /opt/teradata/client/em/bin/empublisher start

    /opt/teradata/client/em/bin/ emcontrolagent start

    /opt/teradata/client/em/bin/emmonitor start