HTML5 version for EMS instead of FlashPlayer

How to use HTML5 version of Neverfail Engine Management Service (EMS) UI instead FlashPlayer version

Summary

This Knowledge base article provides information about using the HTML5 version of the Neverfail EMS (centralized web console) instead of FlashPlayer version as FlashPlayer is end-of-life and no longer working.

More Information

The EMS web console is the main tool used for deployments/installations and normal daily control of Neverfail Continuity Engine. Most routine operations can be performed from the EMS User Interface thereby providing a lightweight, easily accessible, method of conducting Neverfail Continuity Engine operations.

HTML5 version of the EMS UI looks like in the screenshot below.



If you are already having EMS version 8.5 Update 7 then you already have the HTML5 version (with limited features) available. To access the HTML5 version you simply need to add /web-ui expression at the end of the address bar in your browser. Please note that you will need to change the ems_ip with the actual IP of the server hosting the EMS.

      Old EMS link (FlashPlayer based): https://ems_ip:9727/
      New link (HTML5 based): https://ems_ip:9727/web-ui  

On the other hand, to mitigate the Flash Player EOL, we have released the new Engine 2021 (version 9.0) which includes the fully featured HTML5 interface for EMS. You can download the new version 9.0 from here: https://support.neverfail.com/portal/en/kb/articles/neverfail-continuity-engine and to start using it for managing your existing clusters of Neverfail Continuity Engine because EMS console is backwards compatible. For this you simply need to do an in-place upgrade of your current EMS, as per page 41 of the install guide available here: https://download.neverfail.com/Product/downloads/engine/v9-0/doc/Neverfail-CE-9-0-Installation-Guide.pdf

Note: upgrading the EMS is enough to have the new HTML5 UI available, upgrading Engine on the protected servers is not a must. 

Important: If you want to also upgrade Neverfail Continuity Engine to version 9.0 on the protected servers (Primary, Secondary, Tertiary), please note that in version 9.0 Neverfail has changed the licensing model to a subscription-based model. For more details about this, please contact your Neverfail account owner.

Support

For any questions please contact us via email at support@neverfail.com 

Applies To

Neverfail Continuity Engine 8.5 and later

    • Related Articles

    • 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 ...
    • 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 ...
    • How to enable DEBUG level logging on Neverfail Continuity Engine Management Service

      Summary  This Knowledgebase article provides information about how to enable DEBUG level logging on Neverfail Continuity Engine Management Service. Procedure To enable DEBUG level logging on Neverfail Continuity Engine Management Service: On the ...
    • Using the Neverfail Continuity Engine Management Service

      Summary This Knowledgebase article provides an introduction to the Neverfail Continuity Engine Management Service. More Information Using the Engine Management Service User Interface The Engine Management Service is the primary tool used for ...
    • When to Use Neverfail Patch Management Options

      The challenges associated with patching passive nodes with Engine's true clone based architecture Neverfail Continuity Engine employs a clone-based architecture in order to create exact copies of production servers and incrementally synchronize ...