Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
CosmosDataReportingComponent
COSMOS Main Page > Architecture >
This article presents the architecture and high-level design of the COSMOS Data Reporting Component.
Contents
Component Overview
The COSMOS Data Reporting Architecture Overview is maintained in CVS.
Service Interface Types
The services of the COSMOS Data Reporting Component are organized into sets of interface types, organized as adoption points for implementers of management applications. The service interface types are grouped according to the degree of abstraction they provide:
- Service Interface Types for Structured Data Access
- Service Interface Types for Visualization
- Service Interface Types for Light-weight Browser-based Components
Each of these sets of service interface types is explored further in the following sections.
Service Interface Types for Structured Data Access
This set of service interface types is organized for adoption by management application components that consume structured data, for example, tabular displays of information about modeled resources, status information, events, and performance data.
itemize service interface types for structured data access here...
Service Interface Types for Visualization
This set of service interface types is organized for adoption by management application components that consume user interface visualizations, for example, portlet-based displays of information describing modeled resources, status information, events, and performance data. This set of service interface types will also serve the Eclipse workbench.
itemize service interface types for visualization here...
Service Interface Types for Light-weight Browser-based Components
This set of service interface types is organized for adoption by management application components that consume user interface visualizations, for example, browser-based gadgets (obviously, we need to choose an AJAX-enabled quasi-standard pattern to implement!) that can be composed into mashups.
itemize service interface types for light-weight browser-based components here...