Okay, this is technical now. Be warned.
On high level onePortal™ is three things:
- onePortal™ Appliance,
- onePortal™ Framework, and
- onePortal™ Management UI.
Etymology for the term onePortal™ comes from a grand idea, there is only one web portal, from where all things are managed for a modern web application. That boils down to the Management UI, which is the "original" onePortal.
Nowadays the base platform is much more, and more often used from a mobile application or from another external application, than via the Management UI.
The onePortal™ Appliance offers onePortal™ services and is used with a web browser.
The onePortal™ Appliance contains onePortal™ Framework, application logic, database, web server, LDAP Server, and Admin Web Portal. It is an installable software product which can be purchased from Trivore® Corporation.
The onePortal™ Framework is a comprehensive web application framework ready to be used as the basis for many kinds of web applications. It has already been used for healthcare, building automation and public sector applications. From business perspective, the Framework is the most valuable element.
The onePortal™ Framework (and thus also the onePortal™ Appliance) contains multi-tenancy, per tenant branding, comprehensive object management, Two Factor Authentication (2FA), application level diagnostics, Health Insurance Portability and Accountability Act (HIPAA) compatible secure audit trail, flexible field-level database encryption, Representational State Transfer (REST) server, modern user interface, context architecture to easily add new functionality to the Framework to form a custom application, and many other features you normally have to implement separately from scratch when building a new application.
onePortal™ Appliance adds to that full-disk (and database) encryption, a real globally scalable HA clustering, load-balancing, integrated LetsEncrypt certificates, management utilities, installation and updates simply using normal Linux packet management commands like “yum update”.
Logical structure of the full onePortal™ platform with the user, and external line-of-business applications and services.
This guide covers the Appliance and for most part any customer custom application created using the Framework. Most of the time the customer custom application created using Framework comes with its own user guide, which has some fragments from this user guide.
Customers may license onePortal™ Framework to build their own custom web applications. As such, not all features and components need to be utilised. It is also possible to license onePortal™ Appliance to utilise features from it in the customer’s custom web application.
As noted above, onePortal™ is multi-tenant (the term is defined in more detail in next chapter). It means many organisations are able to use it simultaneously, safely, and independently. This is achieved by creating a multitude of independent environments called namespaces inside a onePortal™ platform. Namespace is an isolated logical space which is inaccessible to users in other namespaces (with some controllable exceptions). In onePortal™ multi-tenancy also means multi-functionality. That means each namespace and signed in user account might see somewhat different view depending on the functionality purchased by the organisation, and the roles, rights, and permissions of the signed in user account. This all might initially feel complex and even confusing. It is however normal behaviour and we try to smooth things up for You by dynamically changing the contents of what a user is shown on user interface, based on user roles.
Note: If interested, for more information on the technical details and features of the Appliance and Framework, please see document “onePortal™ Architecture and Functionality” (DocID 1001-111C). Management via API is covered in “onePortal™ API Guide” (DocID 1001-188C) documentation.