The ELM Enterprise Manager licensing model can be customizable for each environment. The product infrastructure includes:
The central processing engine for ELM Enterprise Manager is the ELM Server. From it, the Agents are updated, the alerts are launched, and the data is received and inserted into the databases. With this architecture, the majority of the resources required to provide real-time monitoring, alerting and reporting are efficiently localized in ELM Server.
The ELM Server also enforces the licensing policies. The number of Agents transmitting data to the ELM Server and the Licenses assigned to these Agents are strictly controlled.
The ELM Console is the primary user interface for the ELM Sever. It provides easy access to all configurations and database settings. In addition, the ELM Console presents the event data as filtered Views and as previews of scheduled reports.
For ease of use, the ELM Console is a Microsoft Management Console snap-in. The familiar tree structure and “right click” methodologies flatten the learning curve and accelerates the time to value.
The primary role of the Agent is to collect data and securely transfer it to the ELM Server. On Windows systems, a Service Agent is installed locally. For Syslog and SNMP supported devices, Virtual Agents are installed as a component of the ELM Server.
The Service Agents provide several important advantages. These Agents can pre-filter the data to reduce bandwidth and storage costs. For resiliency, they can cache the data and prevent loss during outages. And to support security policies, the Agents encrypt the event data before transmitting it to the ELM Sever.
The Licenses are the commercial component of the ELM Enterprise Manager. They are sets of Collectors, Monitors and Receivers functionally grouped to support specific objectives. When a License is assigned to an Agent, it controls which data sets they can collect. With this granularity, multiple License Types can be used within a single ELM deployment.
For resiliency and reporting responsiveness, ELM supports three databases. The required Primary database receives data in real-time directly from the ELM Server. When it is unavailable, the data is inserted into a Failover database. Once the Primary database has returns to full operation, the Failover data is merged in the Primary database. To prevent this Primary database from growing out of control, Archive databases can be scheduled to retain some or all the aging data.
All three of these databases use Microsoft SQL Server. The efficient star schema reduces storage requirements and partitioning assists in managing large volumes of data. To keep the databases running at peak performance, maintenance jobs are run at scheduled intervals.