Configuring the Teradata Ecosystem Manager Server
Depending on how you launched your instance, use the following table to determine whether you need to complete this procedure.
- 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.For information, see Connection Considerations.
- 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 ec2-user@public-IP or public-DNSwhere:
- The private-key-file is the private key file (.pem) of the AWS key pair specified when launching the instance.
- The public-DNS or public-IP is the DNS host name or public IP address of the Ecosystem Manager instance.
- 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-IPwhere:
After completing this procedure, you can configure the Ecosystem Manager portlet on the Viewpoint server. See Configuring 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.