16.20 - Installing the Ecosystem Manager Client Package on z/OS USS System - Teradata Ecosystem Manager

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

prodname
Teradata Ecosystem Manager
vrm_release
16.20
created_date
December 2020
category
Configuration
Installation
featnum
B035-3203-107K
  1. Verity the system has Java 1.8.
  2. Verify the EM 16.20 z/OS client version is z/OS OS/390 13.00 01 - Version 1, Release 13 mod 00 or z/OS 2.1.
  3. Copy the em-client-mvs_mvs_i386.16.20.xx.xx.pax.Z file from the Teradata Software server or from the Ecosystem Manager media to the installation folder em-client-16.20.xx.xx.bin.
  4. Install the binary files:
    pax -rf em-client-mvs_mvs_i386.16.20.xx.xx.pax.Z
    Ecosystem Manager is installed from the directory to an installation folder. If the current folder is usr/local/, then Ecosystem Manager is installed in the usr/local/opt/teradata/client/em folder.
  5. Change the INSTALL_ROOT_DIR value in /opt/teradata/client/em/empublisher.sh so the user value corresponds to the user logged on to the system and installing the EM Client:
    INSTALL_ROOT_DIR=/usr/admin
  6. Run the following script to configure Ecosystem Manager services at the installation folder level:
    /opt/teradata/client/em/bin/emserviceconfig.sh
    The following parameters are configured:
    • JRE HOME (1.8)
    • PRIMARY EM SERVER HOSTNAME(BROKER)
    • FAIL-OVER EM SERVER HOSTNAME(BROKER)
    Example:

    emserviceconfig.sh/usr/lpp/java/J8.0_64 svr1 svr2

    The parameters are given the following values:

    Parameter Value
    JRE Home (1.8) Java Home 1.8
    Primary Ecosystem Manager server Hostname(Broker) svr1
    Fail-Over Ecosystem Manager server Hostname(Broker) svr2

    If you have a single Ecosystem Manager server environment (no Failover Ecosystem Manager server), use the same value as the primary Ecosystem Manager server for the Failover Ecosystem Manager server Hostname(Broker) parameter.

    Example:

    emserviceconfig.sh/usr/lpp/java/J8.0_64 svr1 svr1

    The parameters are given the following values:
    Parameter Value
    JRE Home (1.8) Java Home 1.8
    Single Ecosystem Manager server Hostname(Broker) svr1
    Single Ecosystem Manager server Hostname(Broker) svr1
  7. Verify the $EM_HOME/lib and $TMSM_HOME/lib is part of LIBPATH.
  8. Stop empublisher from the installation location:
    /opt/teradata/client/em/bin/empublisher stop
  9. Start the empublisher from the installation location:
    /opt/teradata/client/em/bin/empublisher start
  10. Check the empublisher status from the installation location:
    /opt/teradata/client/em/bin/empublisher status

    For z/OS platforms, if the Ecosystem Manager API (USS) is invoked from the PDSE dataset, add the snippet as shown in the example, to the client Job Control Language (JCL) to point to the correct Hierarchical File System (HFS) .

    This example shows Ecosystem Manager installed in the default path of /usr/local/opt/teradata/client/em:
    // PARM='ENVAR("_CEE_ENVFILE_S=DD:ENVFILE")'
    //ENVFILE DD PATH='/usr/local/opt/teradata/client/em/conf/
    em.env'
    Sample JCLs are located in the /opt/teradata/client/em/jcl/samples file.