How to use the Engine Management Service

How to use the Engine Management Service

Summary

This Knowledgebase article provides information about using the Engine Management Service.

More Information

The Engine Management Service is used to control Neverfail software and provides access to the status of Neverfail Continuity Engine and the configuration of the software.

Procedure

Running the Engine Management Service (EMS) User Interface (UI)

The EMS UI is launched by opening a browser, entering the EMS server's name or IP address, and port 9727 (for example, http://localhost:9727).

The Engine Management Service presents information gathered from all servers in the group (Primary, Secondary, and if installed, Tertiary) including:
  • Server information from Neverfail Continuity Engine, such as logged events, connection status, file system and registry status, and channel throughput
  • System settings, which may be altered by an administrator

Information displayed by the Engine Management Service user interface

The EMS UI displays exactly the same information regardless of where you log into the EMS UI from. It polls roughly every 10 seconds for server information. The system settings are loaded from the server only when Engine Management Service is first opened.

Multiple Engine Management Service User Interfaces

With Neverfail Continuity Engine running as a web service, you access EMS using your local browser. Because it runs as a web service, you can access EMS from any location that allows network access to the server running EMS. Additionally, EMS allows multiple instances of the User Interface to run without interfering with one another.

  • System output from Neverfail Continuity Engine, such as logged events, connection status, file system and registry status, and channel throughput, is updated on all panels simultaneously.

Closing the Engine Management Service User Interface

It is recommended that the Engine Management Service be closed at all times when not in use.

Using Engine Management Service via Terminal Services

The Engine Management Service UI is designed to run on a remote client PC, and it is recommended that you run the EMS UI in this configuration. This will allow remote access to the server pair, regardless of which server is active, without using Windows Terminal Services or Remote Desktop.

Applies To

Neverfail Continuity Engine

Related Information

None

 

KBID-2929

    • Related Articles

    • Engine Management Service API

      Summary This knowledgebase article provides information about Engine Management Service (EMS) API: frequently used API endpoints (applicable to all supported CE versions) procedure for enabling, capturing and viewing Swagger API documentation (valid ...

    • How to enable HTTP Strict-Transport-Security (HSTS) in Continuity Engine Management Service

      Summary This Knowledgebase article provides information about how to enable HTTP Strict-Transport-Security (HSTS) in Continuity Engine Management Service The HTTP HSTS is a mechanism that allows websites to declare that they can be only accessed via ...

    • Continuity Engine Product Architecture

      Learning objectives At the completion of this session, you should be able to: Identify major components of the Neverfail Continuity Engine product architecture. Describe major component configuration. Identify advantages of the Neverfail Continuity ...

    • How to Install Neverfail Engine Management Service (EMS - web centralized console)

      Summary This Knowledgebase article provides the procedure to install the Neverfail Engine Management Service. Using this procedure will ensure that you achieve a successful installation.   Note: You CAN'T install the EMS web console on a server which ...

    • Check Continuity Engine Server Status

      This article describes how to check server status by reviewing several indicators, including the system tray icon, the Server Details page and Applications page in EMS, and Windows services. Check Server Status Learning objectives At the end of the ...