Ecosystem Manager runs on a Teradata managed server, which communicates with the Ecosystem Manager client software installed on each monitored server. Ecosystem Manager automatically recognizes and self-registers new resources to monitor in your ecosystem. It creates metadata and metrics, and sets up dependencies and default thresholds. When Ecosystem Manager client software is on a server, it becomes a monitored server. The client software includes monitoring agents. Use the Ecosystem Configuration portlet to edit and refine your monitoring preferences.
Ecosystem Manager uses agents to collect information from non-Teradata systems, and the Viewpoint Data Collection Service (DCS) to collect information from Teradata, Aster, and Hadoop systems. The information is passed on as messages. The message bus, located on the Ecosystem Manager server receives the message. The Ecosystem Manager software then stores the messages in an embedded repository and processes them to provide monitoring and alerting functions.
Ecosystem Manager can be run in either a single or dual system environment. When Ecosystem Manager is installed on two sites for high availability purposes, agents send messages to one of the message buses. Both Ecosystem Manager servers receive information from both message buses. In the case of one Ecosystem Manager server failing, agents automatically redirect messages to the surviving Ecosystem Manager server.