JBones OSGI Deployment Engine

News


August 31, 2004 NewFirst version of JBones is released.
Overview

JBones: Java Based OSGi Native dEployment System

JBones is an automatic and customizable deployment engine, targeted to ease service deployment tasks on OSGi enabled devices. The engine has entirely been written in Java and it runs on an OSGi framework. Nonetheless, the field of operation of the engine extends its functionalities also to the operating system level. JBones carries out the recursive identification and resolution of dependencies between services in OSGi enabled platforms, including the resolution of native dependencies.

For more information on JBones's features read the features overview documentation.

JBones has been developed by the Departamento de Ingeniería Telemática (DIT) of the Universidad Politécnica de Madrid (UPM), Spain, in collaboration with Telvent.

JBones is distributed under the GNU Lesser General Public License, LGPL, for detailed information visit LGPL.

OSGi

The Open Services Gateway initiative (OSGi) is an independent consortium launched, in 1998, by more than fifty companies in the area of embedded systems, with the aim to develop a series of open specifications for a Java based service platform, able to act as a gateway between Internet and the local area networks that can be found at home, at a car, and other types of constrained environments.

The third release of this specification defines a service platform (an instantiation of a Java virtual machine, an OSGi framework and a set of running services) that includes a minimal component model and a small framework for managing components, including a packaging and delivery format.


What is JBones for?

JBones was initially conceived to give an answer to deployment needs in a scenario of service provisioning to home environments.


Deployment Scenario

In this image we can find the essential elements that take part into the service provisioning scenario. On the left of the diagram: the service providers, the service aggregators and the gateway operator represent the actors that would be on the “server side”. On the left of the diagram: the service gateway (GW), the home networks and the home/outdoor devices, that would be on the “client side”.

The gateway operator is in charge of the management of the service gateways, both as an IP gateway and as an OSGi service platform.

Services provided to the service gateways will have components installed on the OSGi service platform, but for many of them some components will have to be deployed in other locations (for example service applications developed under the client-server model), controlled either by the service provider or by the gateway operator.

With JBones installed on top of the OSGi service platform (and consequently in each Service GW) deployment tasks are eased and automated.  It is a win to win scenario, the user wins in usability (service deployment tasks are transparent for him) and service providers automate service deployment, saving time and money at the same time.

Examples

Here you can find some JBones utilization examples (more to be added in brief).

  • Simple: a crash course on how to write and use JBones deployment descriptors.
  • PIDS Physical Intruder Detection System.

Please, contact us if you have any interesting examples that could be included here.


Roadmap

To be provided.


Contact

Please send any comment, suggestion or problem report related to JBones using the mailing lists at Os4os.


JBones Team

JBones has been initially developed in the context of the participation of the Departamento de Ingeniería Telemática (DIT) and of the Universidad Politécnica de Madrid (UPM) and Telvent. 

JBones programs and documentation have been created by Jose Luis Ruiz and Juan C. Dueñas. Besides, several people has contributed to the project with good ideas, examples or helping to test and debug the tool: Fernando Usero, Francisco Gimeno, Miguel A. Oltra and Jesús Bermejo from Telvent; and Cristina Díaz from Telefónica I+D.


Links

Useful references:


Last update: .    Accesses since February 10th, 2004:   counter  

Valid HTML 4.01!