Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CosmosDataReportingComponent"
(→COSMOS Data Visualization and SML) |
(→Service Interface Types) |
||
| Line 29: | Line 29: | ||
<br style="clear:both"/> | <br style="clear:both"/> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Service Interface Types for Structured Data Visualization == | == Service Interface Types for Structured Data Visualization == | ||
Revision as of 17:28, 5 April 2007
COSMOS Main Page > Architecture >
This article presents the architecture and high-level design of the COSMOS Data Visualization Component.
Contents
COSMOS Design Document
The design document has been moved to CVS undergoing iterative updates. Currently CVS was deemed as the best medium to update this document. After careful review this document will be finalized and ready to be published at which time the wiki page will contain the design document.
The CVS information to get the design document is as follows:
- Host: dev.eclipse.org
- Repository path: /cvsroot/technology
- Connection Type: pserver
- User: anonymous
- Module path: org.eclipse.cosmos/doc/org.eclipse.cosmos.doc.architecture/data-visualization
- Document file: COSMOS-DataVisualizationDesign.html
COSMOS Data Visualization and other Open Standards
needs more work -- cthomas 27-feb-2007
- structured data access interface types: WSDL for web services
- portlet interface types: JSR-168
- web browser interface types: n/a
COSMOS Data Visualization Component Design
Service Interface Types for Structured Data Visualization
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.
Open Data Access(ODA) Library
ODA components will be constructed to utilize resource model componentry to access the resource model repository. Similarly ODAs will be created to utilize the data collection componentry to acces the data collection repository. With ODAs in place BIRT report templates can be created to provide customized views of the data.
Service Interface Types for Graphical 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.
Report Manager UI
The report manager UI will provided the necessary tools to allow users to deploy and configure reports on to the reporting system. Specifically, the tool can be used to configure data binding information such as database hostname, username, password, etc. It may be necessary for this tool to consume sml documents that contain data binding information.
This tool will also provide a management system based on data collection types. For example, this tool will manage separate list of reports that are associated with performance data, events and status information. (Side Note: a widget can be created to expose this management list to a user interface)
Report Viewer UI
The report viewer renders report templates within a web browser. This viewer will utilize the BIRT report engine to render reports.
Resource Model UI
This user interface will provide views to navigate and describe the resource models. On certain resources, reporting capabilities can be initiated to view collected data.
Service Interface Types for Presentation Visualization
This set of service interface types is organized for adoption by management application components that consume user interface visualizations that can be composed into mashups.
Widget Libary
A rich set of browser-based widgets(obviously, we need to choose an AJAX-enabled quasi-standard pattern to implement!) will be utilized to construct mashups.
Report Component Library
A set of report components will be utilized to constuct reports. This library will contain preconfigured datasources and preconfigured report items such as charts so that basic reports can be constructed without the need to know any binding logic to the data source.