Configuring the Ecosystem Manager Portlet on the Viewpoint Server - Teradata Software for AWS

Teradata Vantageā„¢ on AWS (DIY) Quick Deployment Guide

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
uxv1521735824743.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2801
Product Category
Cloud
Although you can configure this software yourself, we recommend contacting Teradata instead. See https://www.teradata.com/Consulting/Velocity.

You can use the Ecosystem Manager portlet to connect to a Teradata system on AWS or an on-premises Teradata system.

  1. From the AWS Web Console, note the Private IP and either the Public IP or Public DNS of the Ecosystem Manager instance and the Viewpoint instance.
  2. From your SSH client console, log on to the Viewpoint instance as ec2-user using the applicable AWS key pair.
    # ssh -i  private-key-file.pem  ec2-user@viewpoint-public-DNS-or-IP
  3. Switch to the root user environment.
    # sudo su -
  4. Change the directory and configure the Ecosystem Manager portlet.
    # cd /opt/teradata/viewpoint/portlets/em-portlets/uiConfig.sh active-em-server standby-em-server em-password
    where:
    • active-em-server is the DNS host name of the active Ecosystem Manager server.
    • standby-em-server is the DNS host name of the standby Ecosystem Manager server. If you did not set up a standby Ecosystem Manager server, use the DNS host name of the active Ecosystem Manager server.
    • em-password in the Ecosystem Manager user password (the default password is em).
  5. From your browser, display the Viewpoint portal logon screen. http://viewpoint-public-DNS/c
  6. Log on to the Viewpoint portal using administrator credentials.