The OpenECOMP Portal is a platform that provides the ability to integrate different OpenECOMP applications into a centralized Portal Core. The intention is to allow decentralized applications to run within their own infrastructure while providing common management services and connectivity with the OpenECOMP Portal core. The Portal core provides capabilities including application onboarding & management, centralized access management, and hosted application widgets. Using the provided SDK, application developers can leverage the built-in capabilities (Services / API / UI controls) along with bundled tools and technologies. Anchor Architecture Architecture
...
From the Portal, users access applications and Key Performance Indicators. Administrators onboard and manage applications and hosted application widgets, and manage user access.The Portal is also a platform that integrates different OpenECOMP applications into a centralized core. The Portal platform provides common management services and connectivity, while the applications run separately. See below.
Here are two views of the Portal landing screen, one for administrators, and one for users:
...
The forthcoming User Guide <<DocRef: User Guide>> will provide a comprehensive description user-focused view of the features capabilities of the the Portal.
| Anchor | ||||
|---|---|---|---|---|
|
...
Applications and widgets developed using the Portal SDK are onboarded via the tools available to an OpenECOMP Administrator. The Administrator creates or assigns roles for the application, and makes the application visible to users via menus or links.
Portal Platform Main Components
Portal Core Integration: APIs in the SDK provide simplified integration between the OpenECOMP Portal Core and the OpenECOMP Application. By default, any application built on the SDK will have implicit integration with the Portal Core.
Centralized Access Control: The Portal core acts as a gatekeeper for all OpenECOMP applications. The administrators will decide who gets access to which applications with a distributed access management scheme.
Common UI Controls: These are used to ensure a common look and feel and a consistent user experience.
Context-Aware UI Controls: Since the OpenECOMP Portal Core serves both as the point of entry and as the provider of context-aware menus and UI controls, it can ensure that when a user jumps from one application to another, the application menu items remain consistent and comply with the user’s access level. (This property of access control is called "Single Sign-On (SSO)".)
Visualization & Reporting Engine: This component is used to develop analytical reports and visualizations on AVP / RCloud / RSpeed / RAPTOR.
Collaborative Services: Collaboration services include video, text chatting, and screen sharing.
Web Component & Widget Development Framework: This framework is used to build widgets and visual components that will be hosted on the OpenECOMP Portal Core. It has access to services exposed by OpenECOMP applications running in separate environments.
Management for Internal/External Users: The administrators will import, or integrate with, internal and external users.
Dashboards: The Portal provides customizable dashboards tailored for each user, based on their access level. Dashboards are comprised of widgets that provide summary content hosted by applications.
Application Administration: Portal Core administrators can on-board and manage applications.
Services Registration/Discovery: Applications can publish or discover services & APIs.