Installing the Ecosystem Manager Client Package on Solaris - 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
  1. Verify that JRE 1.8 is installed on the Linux client.
  2. Download the Client Packages to a folder on the server.
  3. Copy the following files from the Teradata Software Server or from the Unity Ecosystem Manager media:
    em-publisher-solarisXXXX__solaris_XXXX.16.20.xx.xx.tar.gz
    em-agent-solarisXXXX__solaris_XXXX.16.20.xx.xx.tar.gz
    XXXX indicates the architecture, such as Sparc or Opteron. xx indicates the version.
  4. Extract the following tar files:
    tar -xvf em-publisher-solarisXXXX__solaris_XXXX.16.20.xx.xx.tar.gz

    tar –xvf em-agent-solarisXXXX__solaris_XXXX.16.20.xx.xx.tar.gz

  5. Install the publisher package:
    pkgadd em-publisher
    The package is installed in /opt/teradata/client/em.
  6. Install the agent package:
    pkgadd em-agent
    The package is installed in /opt/teradata/client/em.
  7. Run the script to configure the Ecosystem Manager services parameters:
    /opt/teradata/client/em/bin/emserviceconfig.sh
    Parameters are as follows:
    • JRE HOME (1.8)
    • 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/java/jre1.8.0_18 svr1 svr2 eco1 APP

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

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

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

  10. Stop the Ecosystem Manager services on the Linux client server:
    /opt/teradata/client/em/bin/empublisher stop

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

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

  11. Start the Ecosystem Manager services on the Linux client server:
    /opt/teradata/client/em/bin/empublisher start

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

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