Difference between revisions of "Onepoint"
(→Backends) |
(→Backends) |
||
Line 14: | Line 14: | ||
= 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]]. | + | 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]]. They allow requests and operations on the target systems through Onepoint REST calls. They also allow the integration of asynchronous tasks directly on the target systems, through Onepoint Scripts calls. |
== Primary Backends == | == Primary Backends == |
Revision as of 08:34, 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. They allow requests and operations on the target systems through Onepoint REST calls. They also allow the integration of asynchronous tasks directly on the target systems, through Onepoint Scripts calls.
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.