This is only for ELM Enterprise Manager.
ELM has the functionality to forward events to another ELM Server using a Forward Event Notification Method.
The Start Diagnostics button launches the ELM Diagnostics Tool (TNTDiag.exe).
The ELM Diagnostic Tool (TNTDiag) is a troubleshooting tool used to trace some or all activity of an ELM Server, an ELM Console, and/or a Service Agent. The diagnostic output produced by this tool is intended for TNT Software's Product Support Group. This tool adds overhead to the system and should be used only under the direction of TNT Software support personnel.
TNTDiag installs itself as a service when performing its operations. It can be used by administrators only.
TNTDiag can also be started from a command prompt. This enables starting a diagnostic trace from a Windows scheduled task. Syntax is:
/Quiet - Starts a TNTDiag trace using the options in TNDiagConfig.xml
/Save - Saves a currently running TNTDiag trace started using the Quiet command line /Stop - Stops and saves a currently running TNTDiag trace started using the Quiet command line
/? or H[elp] - Display this text and exit
Logging
Set the level of logging activity to one of three pre-defined settings. In general the three levels control logging by event type as indicated below.
Low - Log errors only.
Medium - Log errors and warnings.
High - Log errors, warnings and informational events.
Only events that are written to the Application log respect logging level and logging cannot be completely turned off.
Database
This tab displays current database configuration information. You may click the Database Settings
3.1.1.4 Home and Standby
Premise
ELM provides additional Fault Tolerance by providing the option to employ a Standby ELM Server which will accept data (Events, Performance Data) from Agents should the primary (now referred to as the Home) ELM Server become unavailable for an extended period of time.
The Standby server may be another active ELM Server on the network servicing its own group of Agents, or may be simply another server on the network with an idle instance of ELM running. In the active-active ELM Server scenario, each ELM Server may be configured as the Standby server for the other. However, each Agent can have only 1 Home ELM Server, and 1 Standby ELM
Server. This is illustrated below: ELM Server A is the Home Server for Workstations 1 and 2, plus it is the Standby Server for Workstations 3 and 4. ELM Server B is the Home Server for
Workstations 3 and 4, and the Standby Server for Workstations 1 and 2.
Active-Active ELM Servers
Only ELM Service Agents can be configured to Switchover and Switchback to the ELM Standby Server. Virtual Agents and IP Virtual Agents cannot be configured for use with this feature. The ELM Standby Server must have sufficient unallocated licenses available to accommodate the Agents it receives during Switchover from the ELM Home Server. Note that these licenses are allocated on a first-come, first-served basis. Any Agents that attempt to Switchover without an unallocated license will fail to Switchover and will remain in
ELM installation directory on the Home ELM Server: 1. StandbyELMServerName
2. StandbyELMServerIPAddresses 3. StandbyELMServerPort
4. StandbyELMServerIndex - This can be found on the Standby ELM Server, in the following registry key:
HKLM\SOFTWARE\TNT Software\ELM Enterprise Manager\6.7\Settings::Console Item Index
5. StandbyELMServerLicenseKey - This can be found on the Activation tab of the Standby ELM Server.
6. StandbyELMServerAgentCategoryName - All agents switching over to the standby server will be assigned to this category. This appSettings key is optional on the Standby Server, and the home server ignores this key. The category will be created by the standby ELM server when Agents switchover. If not present, Agents in Standby mode will appear only in the All Agents container in the Standby ELM Server Console.
7. HomeELMServerAgentCategoryName - This Category will be created by the ELM Home Server when it is restarted, and all agents assigned to this Category will have Home and Standby properties.
8. HomeELMServerCacheDurationInMinutes - See Switchover for more details. 9. HomeELMServerRetryIntervalInMinutes - See Switchback for more details.
The following sample appSettings.xml entries can be found near the bottom of the file. In a
default ELM install, the keys are commented-out. The Home Server keys in the example below are commented-in to facilitate copy/paste.
<!-- ELM Home/Standby server keys
The below keys must all be set in the Home Server's appSettings file to enable the Home/Standby feature. Search for 'Standby' in the Help file for more information.
-->
<add key="StandbyELMServerName" value="NetBIOS Name of Standby Server" /> <add key="StandbyELMServerIPAddresses" value="000.000.000.000" />
<add key="StandbyELMServerPort" value="1251" />
<add key="StandbyELMServerIndex" value="{00000000-0000-0000-0000-000000000000}" /> <add key="StandbyELMServerLicenseKey" value="{00000000-0000-0000-0000-000000000000}" /> <add key="HomeELMServerAgentCategoryName" value="This Category will be created, and agents put in it will have the Home/Standby behavior" />
<add key="HomeELMServerCacheDurationInMinutes" value="1" /> <add key="HomeELMServerRetryIntervalInMinutes" value="1" />
<!-- optional for the standby server appSettings file -->
<!-- add key="StandbyELMServerAgentCategoryName" value="If this category exists, agents switching to the standby on this server will exist in this category" / -->
All Agents desired to Switchover to the Standby server must be placed in the Category defined in the "HomeELMServerAgentCategoryName" appSettings.xml key. After restarting the Home ELM Server, this Category will be created and visible in the ELM Console.
Tip
After editing appSettings.xml, open it using Internet Explorer to verify there are no xml formatting errors.
Both ELM Server services must be restarted to activate changes to appSettings.xml.
Note
If testing switchover functionality, be sure to generate at least 1 test event to create a cache file, and at least 1 test event after the "Cache Duration" timer has elapsed. The cache file starts the timer, and the 2nd event triggers switchover.