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.
High level architecture
COSMOS Main Page > Architecture >
Architecture Overview
The COSMOS architecture is described in the project creation review pdf.
During the F2F in Toronto we spent a significant amount of time drilling down into this architecture with a focus on what could be created to show in a prototype at [Eclipse Con].
March 2007 Deliverables
It is not the goal of the COSMOS project to invent new data collection technology. Instead, the project intends to leverage existing work that is available, and where possible, provide value add, especially in the area of standards. For March 07, this is the infrastructure from the Eclipse TPTP project.
Data Collection
The data collection work is in the process of being updated. Please check out CVS: [| Data Collection Doc]
The picture above is the next level down from the architecture document presented in the project creation review. It focuses on how COSMOS will acquire data from a Windows host via perfmon. Similar "block-i-tectures" have been put together for JMX and WSDM.
The System Under Test (SUT) is a Windows Machine with Tomcat 5.5 deployed. Inside of Tomcat there is a single application running that serves up some web content. In order to collect the statistical data, the existing TPTP agent controller has been deployed.
- The COSMOS TPTP Agent Controller Contribution is a wrapper of the existing TPTP Agent Controller client API. It will expose this API through WSDM.
- The COSMOS TPTP Agent Contribution is provides a mechanism to expose the custom command framework via WSDM. There will be one COSMOS TPTP Agent Contribution for each kind of collection technology. In the example above, this will represent the commands that can be sent to perfmon.
Data Reporting
