WebEOC Nexus and Juvare Saas Communication Overview

This following information describes the communication between the WebEOC Nexus instance and Juvare SaaS, as well as possible changes that can happen to WebEOC Nexus functionality when the WebEOC Nexus cloud services in Juvare SaaS are updated.

The common parts in a WebEOC Nexus system are:

  • The WebEOC Nexus instance that is installed on client systems, or hosted in the Juvare infrastructure.

  • The Juvare SaaS that includes:

    • The configuration service that provides configuration information to the WebEOC Nexus instance.

    • The Juvare SaaS that provides WebEOC Nexus cloud services as plug-ins and features to the WebEOC Nexus instance (for example, Ad Hoc Alerts, Contacts, and the WebEOC Nexus Inbox).

    • The alert service that provides board and scheduled notification services to the WebEOC Nexus instance.

      Juvare Exchange (JX), WebEOC NexusFusion, and other services are not detailed in this content.

Communication Between the WebEOC Nexus Instance and Juvare SaaS

Communications for end users, including enabled Juvare SaaS plug-ins and features, go through the WebEOC Nexus instance. Devices that connect to the WebEOC Nexus instance have access to these plug-ins and features.

To communicate, the WebEOC Nexus instance needs access to the following Juvare SaaS components:

  • The configuration service

  • The Juvare SaaS features, if enabled (for example, Ad Hoc Alerts, Inbox, and so on)

  • The alert services that are used (for example, SMS, Voice, WhatsApp, and so on)

    Upon request, Juvare will help determine the hostname/IP address since this information may depend on the client and region. No firewall exceptions are needed to allow connections from the WebEOC Nexus SaaS/configuration service to the WebEOC Nexus instance. All communication is through standard HTTPS.

    You can configure email relay within WebEOC Nexus. This configuration is not detailed in this document because it is client-specific (for example, determining the firewall configuration).

Configuration Service

WebEOC Nexus periodically synchronizes the configuration with the configuration service using HTTPS. The default synchronization time is once per hour. The host with which the synchronization happens is defined in WebEOC Nexus Admin: System: Configuration: Services.

The URL, Client Name, and Key are provided byJuvare.

The settings that the configuration service controls include:

  • The Juvare Login Services

  • The sending of notifications (for example, SMS, Voice, and so on)

  • JX

  • The Juvare SaaS plug-ins and features (for example, Ad Hoc Alerts, WebEOC Nexus Inbox, and so on)

  • Others

The data flow is one-way. Information is retrieved from the configuration service. No information is transmitted from the WebEOC Nexus instance to the configuration service.

Possible changes to any of these values appear in the audit log; however, changes are not expected in common operations.

WebEOC Nexus Juvare SaaS Services

If the Juvare SaaS service (aka cloud services in WebEOC Nexus) are enabled, a synchronization process runs every minute, by default. Information about users, positions, and groups in the WebEOC Nexus instance is synchronized to the WebEOC Nexus cloud services that provide, for example, notification sending functionalities.

If the communication channel is blocked, some services may not work or may contain outdated information. For example, WebEOC Nexus Inbox notifications from boards are not delivered if there is no connection to the WebEOC Nexus cloud services. Any features or plug-ins provided by the Juvare SaaS services are not available (for example, Ad Hoc Alerts).

Updates to WebEOC Nexus Features in Juvare SaaS Services

Since WebEOC Nexus cloud services are provided by the Juvare SaaS, updates to its features and functionalities are separate from the WebEOC Nexus instance. Even if the WebEOC Nexus instance is not updated to a newer version, some of the WebEOC Nexus cloud services features or functions may update automatically. This means that parts of the user interface that are provided by the WebEOC Nexus cloud services may change. For example, boards defined by the client will not change their appearance or functionality unless the WebEOC Nexus instance is upgraded, but the WebEOC Nexus Inbox feature and the Ad Hoc Alerts plug-in may receive new features without any interaction from the client.

Determining a suitable update policy occurs between Juvare and the client.