The project aims to develop and sustain the necessary tooling that will assist Cloud application lifecycle management operations, using open standards and languages, where appropriate. As aforementioned, these operations are classified into three distinct categories: (1) application description, (2) application deployment and (3) application monitoring. CAMF will follow the Eclipse OSGi plug-in based software architecture for each of the aforementioned operations and will inherit the same look-and-feel that Eclipse users are accustomed to.

MDM@WEB includes multiple components for handling measured data. These components are structured to allow for high re-usability of core components like the communication with the ODS server or the import and export of data. In addition to these core components the project includes a web-based front-end.

The list of components includes:

Trace Compass is a Java tool for viewing and analyzing any type of logs or traces. Its goal is to provide views, graphs, metrics, etc. to help extract useful information from traces, in a way that is more user-friendly and informative than huge text dumps.


Many development tools that are deployed on the desktop create two challenges for large organizations: configuration and compliance. When a developer or system administrator needs to install a tool individually on each machine, or each tool needs a reconfiguration for each branch / project / issue, there is a lot of manual step-by-step configuration tasks that a developer or admin must perform (repeatedly) to achieve a proper configuration.

score is a generic engine that is able to execute workflows. A workflow has a logical structure that resembles a flow-chart.

Workflows contains both logical operations and actions. A workflow must be compiled using one of the available orchestration languages before use.

A compiled workflow is known as content and can take several forms such as jar files or a binary object stored in a database.


The fundamental architecture of the project consists of:

Moquette is a Java implementation of an MQTT 3.1 broker. Its code base is small. At its core, Moquette is an events processor; this lets the code base be simple, avoiding thread sharing issues.

The Moquette broker is lightweight and easy to understand so it could be embedded in other projects. By default it lives standalone, but could be integrated into an OSGi container to create more significant integrations, for example running inside an embedded OSGi broker like Concierge.

The Oomph project provides tools based on extensible frameworks, packaged as fine-grained features that allow consumers to pick and choose. The basic building blocks include the following:

This project provides features to allow scientific software to be inter-operable. Algorithms exist today which could be shared between existing Eclipse-based applications however in practice they describe data and do plotting using specific APIs which are not inter-operable or interchangeable. This project defines a structure to make this a thing of the past. It defines an inter-operable layer upon which to build RCP applications such that your user interface, data or plotting can be reused by others.

EASE allows the execution of script code (using scripting languages such as JS, Python, ...) within the context of the Eclipse Platform/RCP. As they are running in the same JRE as Eclipse itself, these scripts have direct access to any class of your application and may interact with your workbench.

The Eclipse Integrated Computational Environment (ICE) will address the usability needs of the scientific and engineering community for the Big Four modeling and simulation activities. The focus of the ICE will be to develop an easily extended and reusable set of tools that can be used by developers to create rich user interfaces for their modeling and simulation products. Custom widgets and data structures with well-defined interfaces and high-coverage unit tests will be provided for plugin developers.