Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CosmosDataReportingComponent"

(COSMOS Data Visualization and SML)
(Compiling the Data Visualization UI)
 
(39 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
This article presents the architecture and high-level design of the COSMOS Data Visualization Component.
 
This article presents the architecture and high-level design of the COSMOS Data Visualization Component.
  
= COSMOS Design Document =
+
= COSMOS 0.4 Data Visualization 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 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.
  
Line 15: Line 15:
 
*Document file: COSMOS-DataVisualizationDesign.html
 
*Document file: COSMOS-DataVisualizationDesign.html
  
 +
You can directly download and view the document [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cosmos/doc/org.eclipse.cosmos.doc.architecture/data-visualization/COSMOS-DataVisualizationDesign.html?root=Technology_Project&view=co here], but the image links will be broken.
  
 +
= Compiling the COSMOS 0.4 Data Visualization UI =
 +
Follow the following steps to build the data visualization ui components.
  
= COSMOS Data Visualization and other Open Standards =
+
# Download wtp 2.0 RC1 all in one driver (http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0RC1-200705250432/wtp-S-2.0RC1-200705250432.zip).
 
+
# Import the following project set file [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cosmos/data-reporting/org.eclipse.cosmos.dr.build/projectSet/org.eclipse.cosmos.dr.projectSet.psf?root=Technology_Project&view=co here], .  This will check out the code from cvs into your workspaceWhen prompted for a user id and password enter 'anonymous' for the id with a blank password.
''needs more work -- cthomas 27-feb-2007''
+
# Make sure the org.eclipse.cosmos.dr.drs.service.handler compiles.    You might have to edit the JRE System Library in the Java Build Path to point to the correct jdk[[Image:Jdkcompile.gif]]
 
+
# Repeat the above step for org.eclipse.cosmos.dr.gvs.views and org.eclipse.cosmos.dr.ps.common.
* 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 =
+
 
+
<br style="clear:both"/>
+
 
+
== Service Interface Types ==
+
The services of the COSMOS Data Visualization 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 Visualization
+
* Service Interface Types for Graphical Visualization
+
* Service Interface Types for Browser-based Visualization
+
 
+
The following diagram illustrates the high level interaction between the data visualization components.  
+
 
+
[[Image:Cosmos-data-visualization-components.png|COSMOS Data Visualization Components]]
+
 
+
Each of these sets of service interface types is explored further in the following sections.
+
 
+
== 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 repositorySimilarly ODAs will be created to utilize the data collection componentry to acces the data collection repositoryWith 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 systemSpecifically, 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.
+
 
+
  
 
[[ COSMOS#Architecture | back to home]]
 
[[ COSMOS#Architecture | back to home]]

Latest revision as of 21:13, 16 August 2007

COSMOS Main Page > Architecture >

This article presents the architecture and high-level design of the COSMOS Data Visualization Component.

COSMOS 0.4 Data Visualization 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

You can directly download and view the document here, but the image links will be broken.

Compiling the COSMOS 0.4 Data Visualization UI

Follow the following steps to build the data visualization ui components.

  1. Download wtp 2.0 RC1 all in one driver (http://download.eclipse.org/webtools/downloads/drops/R2.0/S-2.0RC1-200705250432/wtp-S-2.0RC1-200705250432.zip).
  2. Import the following project set file here, . This will check out the code from cvs into your workspace. When prompted for a user id and password enter 'anonymous' for the id with a blank password.
  3. Make sure the org.eclipse.cosmos.dr.drs.service.handler compiles. You might have to edit the JRE System Library in the Java Build Path to point to the correct jdk. File:Jdkcompile.gif
  4. Repeat the above step for org.eclipse.cosmos.dr.gvs.views and org.eclipse.cosmos.dr.ps.common.

back to home

Back to the top