OpenDash360

The OpenDash360™ Architecture

OpenDash360™ is a framework designed to support the development and deployment of applications in the form of custom elements.

OpenDash360 Customizable Dashboard Screenshot
Custom Elements

Custom elements are part of the HTML5 Web Components specification. Custom elements provide a way to build portable and reusable components that can be deployed and consumed in any web page or web application.

Along with portability, custom elements directly support the use of the Shadow DOM. HTML elements attached to the Shadow DOM are scoped, which eliminates the risk of id, classname, or CSS conflicts with the parent document.

Within the context of OpenDash360™, individual custom elements take the form of either a MicroApplication or a Widget. The primary difference is presentation. Only one microapplication can be loaded and consumed by a user at any point, similar to how a Single-page Application (SPA) would function. Only one instance of any microapplication executes at any given time. Widgets, however, are presented globally. Several instances of the same widget or multiple instances of different widgets can be consumed simultaneously. Widgets can remain open during navigation events and are only unloaded when the user decides to close them.

Within OpenDash360™ multiple microapplications/widgets can run together seamlessly regardless of the language or framework they were created in.

Application

In OpenDash360™, an Application is the “container” for a single microapplication, its supporting widgets, and any supportive assets. Applications are described by a project manifest. At a minimum, Applications must define:

  • A microapplication with no widgets
  • At least one widget and no microapplication
  • One microapplication and one or more widgets

When an application is deployed to OpenDash360™, it is backed by an auto-generated SSO client containing developer-defined client roles. These client-roles provide a singular security context for all elements (its microapplication and widgets) of the Application. These client roles are mapped to realm-level roles as composites, which are in turn mapped to specific users. This allows application developers to only check for client roles within their application's respective client for the purpose of role-based security.

Microapplication

Within an Application, a Microapplication is the primary component. All primary functionality and features should reside in the Microapplication.

Widget

Widgets are simplistic and designed to provide a narrow, focused view of a subset of a microapplication's features. Widgets are supportive content and should provide specific insights.

OpenDash360
Developed By Ultimate Knowledge Institute

Ultimate Knowledge Institute (UKI) sets the standard for Information Technology, Information Assurance and Cyber Security training and consulting services to the Department of Defense, Federal Agencies, DOD Contracting Partners, and Fortune 500 companies.

UKI understands the critical requirements of effective training. Since 1999 the US Department of Defense and Industry has turned to our team members for the customized and focused training required to ensure the security and integrity of the networks and services supporting the Global Information Grid.

Have a question about OpenDash360™?