ARC Portal Component Description - Guilin (R7) Release
Page Status: Copied from R6 - Mar, 22, 2020
Component Status: Pending PTL Updates and ArchCom Review
1. High Level Component Definition and Architectural Relationships
Portal is a GUI platform that provides the ability to integrate different ONAP platform GUIs into a centralized portal.
It provides:
The capability to allow other ONAP components to run within their own infrastructure while providing common management services and capabilities in a centralized way
Provides common capabilities such as application on-boarding and management, centralized access management and hosting application widgets, Context-Aware UIControls, Visualization & Reporting Engine
Provides SDK capabilities to access portal capabilities
Portal is used by:
VID, Policy, AAI, SDC, MSB and CLI
In addition to regular user, there are admin roles available for Portal to perform some administrative activities of Portal itself and the administration of on-boarded apps.
From the ONAP Portal, administrators:
access the same functionality accessible to users
manage users and application admins
onboard applications and widgets (developed using the Portal as a platform)
edit the functional menu
2. API definitions
Portal provides the following interfaces: (to be done, add the links)
Interface Name | Interface Definition | Interface Capabilities | Version | Status | Consumed Models |
---|---|---|---|---|---|
PortalE-1 | Portal Admin Interface. | GUI to the portal administrator to:
| |||
PortalE-2 | Application Admin Interface | GUI to the application administrator to
| |||
PortalE-3 | External App Interface | Platform API for application to:
| |||
PortalE-4 | Role Approval Interface | Platform API for application to:
| |||
PortalE-5 | Session Communication Interface | Platform API for application to:
| |||
PortalE-6 | Shared Context Interface | Platform API for application:
| |||
PortalE-7 | Ticket Event Interface | Platform API for the application to:
| |||
PortalE-8 | Web Analytics Interface | Platform API for the application to:
| |||
PortalE-9 | External Request Interface | Platform API to:
| |||
PortalE-10 | External Access Role Interface | Platform API application to:
|
Portal however provides multi-language support.
The multi-language support provides:
Login user langage settings
Update user language settings
Language options to user
Ability to add/remove and query supported languages.
3. Component Description:
Add link to read.the.docs
4. known system limitations
Runtime:
For https Apps on-boarded to portal, a certificate has to be downloaded in the browser when first trying to access the landing page of the App.
For on-boarded Apps using http (since Portal is using https) the browser asks the user to click to Proceed to the unsafe URL.
Language capability limitations:
Language support for different screens
Portal applications that do not use the portal SDK will not get multi-language support.
5. Used Models
none
6. System Deployment Architecture
FFS.
7 References
Portal Architectural Description: https://onap.readthedocs.io/en/latest/submodules/portal.git/docs/platform/architecture.html
Portal APIs Specification: https://docs.onap.org/en/beijing/submodules/portal.git/docs/platform/offeredapis.html