Difference between revisions of "Onepoint"
(→Architecture) |
(→Backends) |
||
Line 13: | Line 13: | ||
= Backends = | = Backends = | ||
+ | |||
+ | Backends are a Onepoint-specific concept. They are components of the computational environment designed to carry out a task or a group of related tasks for a [[Discipline]]. | ||
+ | |||
== Primary Backends == | == Primary Backends == | ||
+ | |||
+ | [[Primary Backends]] are backends that can be instanced, parameterized and extended to integrate environment's own components, such as vaults, user directories, ticketing systems, authentication systems and authorizations systems. | ||
+ | |||
=== Authentication Backends === | === Authentication Backends === | ||
=== Authorization Backends === | === Authorization Backends === | ||
Line 28: | Line 34: | ||
=== Flow Backend === | === Flow Backend === | ||
=== Backend Backends === | === Backend Backends === | ||
+ | |||
= The UI = | = The UI = | ||
== Main Modules == | == Main Modules == |
Revision as of 08:31, 17 October 2018
Contents
Introduction
Onepoint enables Systems Integration for the IT environment. Through its disciplines concepts, it allows the integration of IT assets, modules, systems and units into a single and widelly connected among all parts, creating the possibility to creating actions, tasks and flows involving all those parts.
Architecture
Onepoint components:
Backends
Backends are a Onepoint-specific concept. They are components of the computational environment designed to carry out a task or a group of related tasks for a Discipline.
Primary Backends
Primary Backends are backends that can be instanced, parameterized and extended to integrate environment's own components, such as vaults, user directories, ticketing systems, authentication systems and authorizations systems.