Configure Ecosystem Manager on the Viewpoint Server | Teradata Vantage on AWS (DIY) - 2.2 - Configuring the Ecosystem Manager Server - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.2
Release Date
May 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2800-041K
Language
English (United States)
Although you can configure this software yourself, we recommend contacting Teradata Ecosystem Services. See https://www.teradata.com/About-Us/Contact.
Depending on how you deployed your instances, use the following table to determine whether you need to complete this procedure.
Ecosystem Manual 1-Click
No Yes Yes
  1. From the AWS Management Console, note the Private IP of the Viewpoint instance, and the Public IP and Public DNS of the Ecosystem Manager instance.
  2. From your SSH client console, log on to the Ecosystem Manager instance as ec2-user using the applicable AWS key pair.
    # ssh -i  private-key-file.pem  ec2-user@public-IP  public-DNS
  3. Switch to the root user environment.
    # sudo su -
  4. Check the status of the database to ensure it is running.
    # pdestate -a
  5. Finish configuring the Ecosystem Manager instance.
    This process can take several minutes.
    # cd /opt/teradata/emserver/bin
    # ./em-syncuser-update
    # su syncuser
    # ./config_single.sh ecosystem-name private-IP 
    viewpoint-portal-user-name viewpoint-portal-user-password
    where:
    • ecosystem-name is the name of the active ecosystem, usually referred to as the data center.
    • private-IP is the private IP address of the active Viewpoint instance.
    • viewpoint-portal-user-name and viewpoint-portal-user-password are the username and password of the Viewpoint instance portal.
    After completing this procedure, you can configure the Ecosystem Manager portlet on the Viewpoint server.