T2-ITEmIS infrastructure

The main aim of this task is to develop the ITEmIS infrastructure according to the architecture defined during theTask 1.

This infrastructure is mainly based on the SCA runtime paradigm and allows to abstract different kinds of technologies languages and protocols (Web Service, CORBA, Java JBI, C, C++, etc.) thanks to a service and
component-based approach.

Integration between large set of embedded components based on heterogeneous technologies uses the PEtALS JBI compliant framework. A peer-to-peer architecture is designed that takes into account specific
requirements coming from the embedded world and allows any kind of services to be orchestrated and managed.

- Subtask 2.1: ITEmIS SCA-based framework

The main aim of this task is to design in detail the SCA based framework that allows taking into account requirements and architecture defined duringtask 1.
Main requirement is to provide a common API for orchestration engine that address large-scale service infrastructure deployed on any devices thanks to many technologies.

Main activities involve by the next sub-tasks are:
- To study the size of the SCA runtime according to target device (PC, large or small PDA, sensor).
According to hardware characteristics some runtime functionalities may be implemented or frizzed at run or deployment or compilation time. Moreover some functionality may be implemented inside
the container on-demand. This allows managing tradeoffs between functionalities and memory requirement.
- Management of different kind of components. The SCOrWare / FraSCAti component allows us to manage Java components. The main aim is to manage also lwCCM components. Such approach
allows building an SCA composite made of heterogeneous technologies.
- Implementation of new SCA bindings: SCOrWare / FraSCAti framework takes into account Web Service, JBI and RMI protocols. This project allows us to implement CORBA / IIOP a DDS bindings.

- Subtask 2.2: Java JBI and OSGi containers

This task targets the development of Java based containers compliant with Java JBI and OSGi standards.

Java container has to take into account JSE and JME editions and is based on a lightweight version of PEtALS JBI compliant engine that allows setting up service infrastructure. This tool integrates
the FraSCAti framework as a result of the SCOrWare project.
OSGi container is based on a Java OSGI implementation. FraSCAti runtime is based on Fractal framework that allows dynamic reconfiguration in order to withdraw, modify or add control functionalities
managed at container level.

- Subtask 2.3: CCM and LwCCM containers

This task deals with the implementation of DDS (RTPS) and HTTP/SOAP connectors for lwCCM containers that allows deployment on any specific devices.

- Subtask 2.4: Communication protocols

A main communication protocol that allows peers to communicate is implemented. PEtALS provides already standard Java protocols such as JMS and SOAP/HTTP.

Others commonly used in embedded world such as CORBA/IIOP and DDS are to be provided.
One way of integrating DDS is to map it onto a JMS or JMS like interface. This subtask includes the design and development of a lightweight JMS client, which interfaces DDS on the sensor side, and
behaves as a JMS binding component on the PEtALS side. Work on this middleware component includes studying the impact of scalability. Scalability in the ITEmIS context brings two major impacts on
this part of the middleware, the large number of clients, and the high frequency of adding and removing clients.

This subtask also targets administrative issues of the JMS middleware component. In order to facilitate the deployment of the middleware itself, this component matches the SCA model defined above

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.