OSGi

From Wikipedia, the free encyclopedia

Jump to: navigation, search
OSGi Service Platform
Developed by OSGi Alliance
Latest release 4.1 / May 2007
Operating system Java
Type standards organization
License OSGi Specification License
Website http://www.osgi.org

The OSGi Alliance (formerly known as the Open Services Gateway initiative, now an obsolete name) is an open standards organization founded in March 1999. The Alliance and its members have specified a Java-based service platform that can be remotely managed. The core part of the specifications is a framework that defines an application life cycle management model, a service registry, an Execution environment and Modules. Based on this framework, a large number of OSGi Layers, APIs, and Services have been defined.

Contents

[edit] OSGi Framework Scope

Classification: OSGi & System-Layering

The Framework implements a complete and dynamic component model, something that is missing in standalone Java/VM environments. Applications or components (coming in the form of bundles for deployment) can be remotely installed, started, stopped, updated and uninstalled without requiring a reboot; management of Java packages/classes is specified in great detail. Life cycle management is done via APIs which allow for remote downloading of management policies. The service registry allows bundles to detect the addition of new services, or the removal of services, and adapt accordingly.

The original focus was on service gateways but the applicability turned out to be much wider. The OSGi specifications are now used in applications ranging from mobile phones to the open source Eclipse IDE. Other application areas include automobiles, industrial automation, building automation, PDAs, grid computing, entertainment (e.g. iPronto), fleet management and application servers.

[edit] Specification Process

The OSGi specification is developed by the members in an open process and made available to the public free of charge under the OSGi Specification License [1]. The OSGi Alliance has a compliance program that is open to members only. As of September 2008, the list of certified OSGi implementations contains five entries.

[edit] Architecture

OSGi Service Gateway Architecture

Frameworks that implement the OSGi standard provide an environment for the modularization of applications into smaller bundles. Each bundle is a tightly-coupled, dynamically loadable collection of classes, jars, and configuration files that explicitly declare their external dependencies (if any).

The framework is conceptually divided into the following areas:

  • Bundles - Bundles are normal jar components with extra manifest headers.
  • Services - The services layer connects bundles in a dynamic way by offering a publish-find-bind model for plain old Java objects(POJO).
  • Services Registry - The API for management services (ServiceRegistration, ServiceTracker and ServiceReference).
  • Life-Cycle - The API for life cycle management (install, start, stop, update, and uninstall bundles).
  • Modules - The layer that defines encapsulation and declaration of dependencies (how a bundle can import and export code).
  • Security - The layer that handles the security aspects by limiting bundle functionality to pre-defined capabilities.
  • Execution Environment - Defines what methods and classes are available in a specific platform. There is no fixed list of execution environments, since it is subject to change as the Java Community Process creates new versions and editions of Java. However, the following set is currently supported by most OSGi implementations:

[edit] Bundles

This section requires expansion.

[edit] Life-Cycle

This section requires expansion.

[edit] Services

This section requires expansion.

[edit] Standard Services

The OSGi Alliance has specified many services. Services are specified by a Java interface. Bundles can implement this interface and register the service with the Service Registry. Clients of the service can find it in the registry, or react to it when it appears or disappears.

The table below shows a description of OSGi System Services:

System Services Description
Logging The logging of information, warnings, debug information or errors is handled through the Log Service. It receives log entries and then dispatches these entries to other bundles that subscribed to this information.
Configuration Admin This service allows an operator to set and get the configuration information of deployed bundles
Device Access Facilitates the coordination of automatic detection and attachment of existing devices. This is used for Plug and Play scenarios.
User Admin This service uses a database with user information (private and public) for authentication and authorization purposes.
IO Connector The IO Connector Service implements the CDC/CLDC javax.microedition.io package as a service. This service allows bundles to provide new and alternative protocol schemes.
Preferences Offers an alternative, more OSGi-friendly mechanism to using Java’s default java.util.Properties for storing preference
Component Runtime The dynamic nature of services -- they can come and go at any time -- makes writing software harder. The Component Runtime specification can simplify handling these dynamic aspects by providing an XML based declaration of the dependencies.
Deployment Admin Standardizes access to some of the responsibilities of the management agent.
Event Admin Provides an interbundle communication mechanism based on a publish-and-subscribe model.
Application Admin Simplifies the management of an environment with many different types of applications that are simultaneously available.

The table below shows a description of OSGi Protocol Services:

Protocol Services Description
HTTP Service Allows formation to be sent and received from OSGi using HTTP, the Web’s protocol.
UPnP Device Service Specifies how OSGi bundles can be developed to interoperate with Universal Plug and Play (UPnP) devices.
DMT Admin Defines an API for managing a device using concepts from the Open Mobile Alliance (OMA) device management specifications.

[edit] Organization

The OSGi Alliance was founded by Ericsson, IBM, Oracle, Sun Microsystems and others in March 1999 (before incorporating as a nonprofit corporation it was called the Connected Alliance).

Among its members are (as of May 2007) more than 35 companies from quite different business areas, for example IONA Technologies, Ericsson, Deutsche Telekom, IBM, Makewave (formerly Gatespace Telematics), Motorola, Nokia, NTT, Oracle, ProSyst, Red Hat, Samsung Electronics, Siemens, SpringSource, and Telefonica.

The Alliance has a Board of Directors which provides the organization's overall governance. OSGi Officers have various roles and responsibilities in supporting the Alliance. Technical work is conducted within Expert Groups (EGs) chartered by the Board of Directors, and non-technical work is conducted in various Working Groups and Committees. The technical work conducted within Expert Groups include developing specifications, reference implementations, and compliance tests. These Expert Groups, working together, have produced four major releases of the OSGi specifications (as of 2007).

There are dedicated Expert Groups for the Enterprise, Mobile, Vehicle and the Core Platform areas. The Enterprise Expert Group (EEG) is the newest EG and is addressing Enterprise / Server-side applications. In November 2007 the Residential Expert Group (REG) started to work on specifications to remotely manage residential/home-gateways.

[edit] Community

In October 2003, Nokia, Motorola, IBM, ProSyst and other OSGi members formed a Mobile Expert Group (MEG) that will specify a MIDP-based service platform for the next generation of smart mobile phones, addressing some of the needs that CLDC cannot manage - other than CDC. MEG became part of OSGi as with R4.

Also in 2003 Eclipse selected OSGi as the underlying runtime for the plug-in architecture used for the Eclipse Rich Client Platform and the IDE platform. Eclipse itself includes sophisticated tooling for developing OSGi bundles and there are a number of other Eclipse plug-ins aimed at supporting OSGi behaviour (e.g. both ProSyst and Knopflerfish have Eclipse plug-ins available specifically for OSGi developers).

There is a vibrant free software community revolving around the OSGi. Some widely-used open source implementations are Equinox OSGi, Apache Felix, Knopflerfish OSGi project as well as the mBedded Server Equinox Edition. Regarding tooling, build system support and testing, the OPS4J Pax projects provide a lot of useful components and expertise.

[edit] Specification Versions

  • OSGi Release 1 (R1): May 2000
  • OSGi Release 2 (R2): October 2001
  • OSGi Release 3 (R3): March 2003
  • OSGi Release 4 (R4): October 2005 / September 2006
    • Core Specification (R4 Core): October 2005
    • Mobile Specification (R4 Mobile / JSR-232): September 2006
  • OSGi Release 4.1 (R4.1): May 2007 (AKA JSR-291)

[edit] New in OSGi Release 4

The new features of OSGi R4 in brief are as follows:

  • New modularization capabilities providing enhanced encapsulation of networked services that can share a single VM.
  • Modularized class sharing and hiding of implementation details.
  • Methods for handling multiple versions of the same classes so old and new applications can execute within the same VM.
  • Localization of OSGi bundle manifests enabling service deployment anywhere.
  • Enhancements in security and policies: The new Conditional Permission Admin service provides an elegant and simple way to manage networked services securely. It also supports dynamic policies that can depend on external (custom) conditions. Combined with R4 support for digital signatures, this provides a central security solution to large deployments of products using the OSGi Service Platform.
  • A Declarative Services specification that addresses memory footprint issues that can prevent small embedded devices from using a service oriented architecture to support multiple applications. Additionally, it significantly simplifies the service-oriented programming model by declaratively handling the dynamics of services.
  • Compatibility with Release 3, requiring no changes for existing OSGi bundles, applications, or services.

[edit] OSGi Tutorial

[edit] Guidance and Information Exchange

[edit] Related RFCs and Java Specifications

  • RFC-2608 (Service Location Protocol)
  • Sun JINI (Java Intelligent Network Infrastructure)
  • Sun JCP JSR-8 (Open Services Gateway Specification)
  • Sun JCP JSR-232 (Mobile Operational Management)
  • Sun JCP JSR-246 (Device Management API)
  • Sun JCP JSR-249 (Mobile Service Architecture for CDC)
  • Sun JCP JSR-277 (Java Module System)
  • Sun JCP JSR-291 (Dynamic Component Support for Java SE - AKA OSGi 4.1)
  • Sun JCP JSR-294 (Improved Modularity Support in the Java Programming Language)

[edit] Related Technology Standards

[edit] Projects Using OSGi

[edit] References

  1. ^ OSGi Specification License

[edit] Electronic Books

[edit] Books

[edit] Webinar

[edit] See also

[edit] External links

Retrieved from "http://en.wikipedia.org/wiki/OSGi"
Personal tools