Skip to main content
Jump to: navigation, search

COSMOS Design 212189

Revision as of 22:54, 12 December 2007 by (Talk | contribs) (New page: = '''Change History''' = {|{{BMTableStyle}} !align="left"|Name: !align="left"|Date: !align="left"|Revised Sections: |- |Sheldon Lee-Loy |12/12/2007 |<ul><li>Initial version</li></ul> |}...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Change History

Name: Date: Revised Sections:
Sheldon Lee-Loy 12/12/2007
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Build and infrastructure
Code review, etc.*

'* - includes other committer work (e.g. check-in, contribution tracking)


The COSMOS I7 End-to-End scenario provides a data collection component that collects and queries logging events. This data collection component utilizes the assembly components that were created in COSMOS I3 as outlined in enhancement 180318. The data collection component for logging event should conform to the new Data Collection framework as defined in enhancement 197868 and 192493


A Data Manager is required to query logging information from a logging event repository. The Data Manager should provide the capabilities to allow clients to do the following:

  1. provide a list of datasets that is contained in the logging event repository. The datasets are ids that group a list of common base events. Typically this id is made up of the agent, host location, monitor and log file name that was collected. Note that this id is constructed from TPTP hierarchy model concepts
  2. provide a list of common base events associated with a dataset id
  3. provide a list of common base events grouped by severity

Note that the above operations provides the necessary function to render the current BIRT Log Report.


The following diagram shows the overall architecture of the Statistical Data Manager. A client will use the web service client class to communicate with the Statistical data manager class over SOAP requests. The Statistical data manager will interact with an underlying database that will contain the log event data. The data manager will provide the necessary query APIs to get a list log event data in the form of Common Base Events.

File:Statisticaldatamanger arch.gif


The following class diagram shows the set of classes required to create the Statistical data manager

Statdatamanager class.gif

The following defines the web service client interface (IStatisticalClient). This interface will provide the necessary APIs to get a list of datasets, get a list of Statisticals based on a dataset and get a list of datasets grouped by serverity

public interface IStatisticalClient {

	public Collection<String> getDatasets() throws Exception{
	public Collection<CommonBaseEvent> getAllStatistical(String dataset) throws Exception {
	public Collection<StatisticalSeverityCount> getStatisticalCountBySeverity(String dataset) throws Exception {

The implementation of the StatisticalDataManager will contain the SQL statements to query the Statistical database.

The implementation of the StatisticalClient will contain the soap request that will communicate with the StatisticalDataManager service.

Back to the top