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.
- 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.
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
Switch to the root user environment.
# sudo su -
Check the status of the database to ensure it is running.
# pdestate -a
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-passwordwhere:
After completing this procedure, you can configure the Ecosystem Manager portlet on the Viewpoint server.
- 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.