Jump to: navigation, search

Difference between revisions of "CosmosDataReportingComponent"

(Project Scope)
Line 1: Line 1:
 
[[COSMOS|COSMOS Main Page]] > [[ COSMOS#Architecture | Architecture]] >
 
[[COSMOS|COSMOS Main Page]] > [[ COSMOS#Architecture | Architecture]] >
  
== Project Scope ==
+
This article presents the architecture and high-level design of the COSMOS Data Reporting Component.
* Integrate with the BIRT report viewer
+
** BIRT provides a BIRT report viewer that presents the report in a view with a RCP application.  The following link provides the technical details to accomplish this integration: [[RCP_Example|BIRT Report Viewer]].
+
* Implement a set of data reports
+
** Create a BIRT report template that will list available data models to report on.
+
** Create a BIRT report template for the [[CurrentOperationStatusReport|Current Operation Status Report]]
+
** Create a BIRT report template for the [[ResourceTrendReport|Resource Trend Report]]
+
  
 +
= Component Overview =
 +
The [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cosmos/doc/org.eclipse.cosmos.doc.architecture/dataReportingServices.html?root=Technology_Project&view=co 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.
 +
 +
''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...''
  
 
[[ COSMOS#Architecture | back to home]]
 
[[ COSMOS#Architecture | back to home]]

Revision as of 14:43, 26 February 2007

COSMOS Main Page > Architecture >

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

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.

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...

back to home