A-OSGi: a framework to support the construction of autonomic OSGi-based applications

Abstract

The OSGi specification is becoming widely adopted to build complex applications. It offers adequate support to build modular applications, where modules can be added and removed at runtime without stopping the entire application. This paper proposes A-OSGi, a framework that leverages on the native features of the OSGi platform to support the construction of autonomic OSGi-based applications. A-OSGi offers a number of complementary mechanisms for that purpose, such as: the ability to extract indicators for the performance of deployed bundles, mechanisms that allow to have a fine grain control of how services bind to each other and to gather this information in runtime, and support to a policy language that allows to define autonomic behaviour of the OSGi application.

fANFARE: Autonomic Framework for Service-Based Pervasive Environment

“…OSGi and service component models such as OSGi Declarative Services [4] or iPOJO [5] establish a clear distinction between bundles, components, service references, service factories and service instances. Typically a bundle contains several components that provide or use services.…”

“…Existing Java tools (e.g., JVM-Ti 2 or TPTP 3 )cannot be used as is since gathered information is too fine-grained and thus not relevant. Existing OSGi tools are not suitable for embedded in-production environment because (i) they target development environments [14] or rich platforms [4], or (ii) they require heavy modifications of the JVM or underlying operating system [21], and (iii) they generally induces a persistent strong overhead of at least 20%. Our main contributions are to propose flexible monitoring mechanisms.…”

Towards the Description and Execution of Transitions in Networked Systems

“…Ferreira et al [6] developed A-OSGi to support the construction of autonomic OSGi-based applications. Therefore, they integrate the MAPE-K approach into OSGi.…”

Memory monitoring in a multi-tenant OSGi execution environment

“…Thanks to the popularity of Java-based systems, many monitoring tools were developed for them, such as A-OSGi [3], JMX [12], JVM-TI [13], and the method described in [11]. All these solutions are designed to monitor low granularity Java elements, e.g., threads, classes, objects, methods.…”

“…Resource monitoring provides essentially two information: (1) counting, i.e., how much of the resource is consumed, and (2) accounting, i.e., which entity should be charged for using that quantity of the resource. Existing work performed in component-based and service-oriented platforms [11,3,10,8,4] enable resource accounting at component level in only two cases: (1) when a component calls a service method implemented by a component belonging to the operator platform, or (2) when the opposite happens. Still, there is a third case that occurs when a component from a given tenant calls a service method implemented by a component belonging to another tenant.…”