Q: What are the differences between ELM Enterprise Manager, ELM Log Manager and ELM Performance Manager?A: ELM Enterprise Manager is a superset of ELM Log Manager and
ELM Performance Manager combined, plus some additional functionality
in the form of Monitor Items. ELM Log Manager and ELM Performance
Manager are common-code subsets of ELM Enterprise Manager; that
is, the code is the same in all three applications, with the exception
of the minimal amount of code involved in branding each product
separately (e.g., icon files, string files with the product name,
etc.). For a comparison between the three products, see the comparison
grid . Q: What is the best way to backup ELM Server configuration data?A: Every ten seconds the ELM Server polls for configuration changes. If it detects any, the ELM Server creates a backup of its current configuration data. This file has a .BAK extension (e.g., EEMSVR.BAK). You can also manually backup the ELM Server configuration from within the ELM Console. ELM also stores a small amount of data in the Windows registry. This includes both software-specific settings, and COM component registration information. It is essential that you also take regular backups of your registry. In Windows NT 4.0, you can preserve this data by backing up the Registry with NT Backup or a third-party application. In Windows 2000 and Windows XP, the registry and COM registration database are backed up as part of the System State Data. We also strongly recommend regular backups of your ELM Server database, as it contains all of the data collected from Agents. You can back up this data with NT Backup or a third-party application. Q: How is ELM licensed?A: ELM is licensed on an Agent basis. An Agent is a monitored system or device. There are four classes of Agents that are licensed: Cluster Agents - for Windows NT and Windows 2000 clusters Server Agents - for Windows NT and Windows 2000 Server family products Workstation Agents - for Windows NT/2000/XP Professional IP Agents - for Unix, Linux, Netware, Apple, mainframes and TCP/IP devices A minimum purchase of one Server Agent is required to obtain an ELM Server. The primary user interface, the ELM Console, is implemented as an MMC snap-in that can be distributed to an unlimited number of administrators/end-users in your organization. Q: Can I use my Event Log Monitor 2.x Reports in ELM 3.0?A: ELM 3.0 includes a new reporting engine that enables you to create, edit and schedule reports without the need for additional software. The reports for Event Log Monitor 2.x are in Crystal Reports format, and cannot be imported into version 3.0. You will therefore need to recreate the report. Q: What can ELM 3.0 do that Event Log Monitor cannot?A: ELM 3.0 boasts a wide variety of enhancements improvements over Event Log Monitor, many of which were the result of customer feedback. Both products provide the same core functionality of real-time monitoring, rules-based management, rich notification and action options, and archival and reporting. Version 3.0 offers significant improvements in these areas, and adds functionality. For a detailed list of the improvements and enhancements, see What's New in ELM Enterprise Manager 3.0, and What's New in ELM Log Manager 3.0. Q: What is the difference between a Service Agent and a Remote Agent?A: A Service Agent is an executable (TNTAgent.exe) and companion files. TNTAgent is installed as a service on the monitored system and communicates with an ELM Server via TCP sockets. Service Agents are Windows NT, Windows 2000 or Windows XP systems. Monitor Items assigned to a Service Agent are executed within the TNTAgent process. Only Service Agents can monitor systems in real-time, providing the highest level of monitoring. Remote Agents provide agentless monitoring because nothing is installed on the monitored system. Remote Agents are also Windows NT, Windows 2000 or Windows XP systems. Monitor Items assigned to a Remote Agent are executed within the ELM Server process. Because the ELM Server performs the monitoring of Remote Agents over the network, Remote Agents cannot be monitored in real-time.
More Information
|
FAQs
FAQ's