Installing and configuring the Ecosystem Manager Client package on the Unity server initiates the integration between Unity and Ecosystem Manager.
-
Execute the emserviceconfig.sh script in the /opt/teradata/client/EM/bin directory.
The script takes the following parameters:
Parameter Description PRIMARY EM SERVER HOSTNAME (BROKER) Host name of the primary Ecosystem Manager server. FAIL-OVER EM SERVER HOSTNAME (BROKER) Broker name of the failover Ecosystem Manager server. If a failover Ecosystem Manager server is not available, then specify the same value as the Primary Ecosystem Manager Server Hostname.
ECOSYSTEM ID Ecosystem Manager Ecosystem ID for adding this Unity server.
EM DB USER(EMEM) PASSWORD Password of the EM Database username. The default value is em.
Unity SERVER HOSTNAME Server hostname of the Unity server that the script is being executed on.
Unity Admin User Name Name of the UnityAdmin administrator user. This is typically admin.
Unity Admin User Password Password of the UnityAdmin administrator user. The default value admin should be changed.
UNITY CLUSTER TDPID Logical TDPID used in Ecosystem Manager to represent the Unity cluster.
[Optional] Override UNITY CLUSTER TDPID(Y/N) Updates the existing UNITY CLUSTER TDPID and deletes the history of UNITY CLUSTER TDPID in both EM/Unity repository.
-
[Optional] If either of the following scenarios exist, restart the Unity services with the unity start command:
- If this service configuration is running for the first time for this Unity cluster.
- If the UNITY CLUSTER TDPID is changed to a new value and Override UNITY CLUSTER TDPID is set to Y.
For example:
./emserviceconfig.sh server1 server2 DatacenterA em tara admin admin UnityCluster - [Optional] Check the status of the Ecosystem Manager services: /opt/teradata/client/em/bin/emstatus.sh