PrerequisiteIf you used a Manual or 1-Click launch, you must configure the Ecosystem Manager Server before completing this procedure.
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 launched your instance, use the following table to determine whether you need to complete this procedure.
| Ecosystem | AWS CloudFormation | Manual | 1-Click |
|---|---|---|---|
| Yes | Yes | Yes | Yes |
You can use the Ecosystem Manager portlet to connect to a Teradata system on AWS or another deployment location.
- From the AWS Management Console, note the Private IP and either the Public IP or Public DNS of the Ecosystem Manager instance and the Viewpoint instance.
-
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@public-DNS or public-IP
-
Switch to the root user environment.
# sudo su -
-
Change the directory and configure the Ecosystem Manager portlet.
# cd /opt/teradata/viewpoint/portlets/em-portlets/uiConfig.sh #./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 have 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).
-
From your browser, go to the Viewpoint portal logon screen.
http://public-DNS/cwhere: public-DNS is the DNS host name of the Viewpoint instance. -
Log on to the Viewpoint portal using administrator credentials.
See Teradata® Ecosystem Manager User Guide, B035-3201.