ACM Home Page
Please provide us with feedback. Feedback
Dependable distributed OSGi environment
Full text PdfPdf (511 KB)
Source Middleware Conference archive
Proceedings of the 3rd workshop on Middleware for service oriented computing table of contents
Leuven, Belgium
Pages 1-6  
Year of Publication: 2008
ISBN:978-1-60558-368-6
Authors
Miguel Matos  Universidade do Minho
António Sousa  Universidade do Minho
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 13,   Downloads (12 Months): 144,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1462802.1462803
What is a DOI?

ABSTRACT

As the vision of Service Oriented Computing matures the need for well defined architectures and protocols is essential. The SOC paradigm has several requirements to work properly: service composition and cooperation in a loosely coupled fashion, ability to adapt autonomously to environmental and business changes, proper integration between services, modularity and service dynamics. The OSGi[13] platform embodies key aspects of the SOC paradigm by defining a modular and dynamic architecture. However there is still room for improvement, namely on the creation of architectures and mechanisms to improve the dependability of the platform by strengthening key properties such as availability, reliability, integrity, safety and maintainability.

In this paper we propose a OSGi based middleware layer that offers the strong modular and dynamic properties required in a SOC environment, while addressing dependability concerns. The starting point to achieve this is by instrumenting a OSGi implementation with means to monitor and manage it accordingly to business and environmental requirements. By relying on group communication facilities and some properties from the OSGi specification we are able to migrate OSGi environments among nodes, thus minimizing service outage in the presence of faults and addressing, at the same time, Service Level Agreement properties by migrating (or shutting down) services that are consuming more resources than agreed/expected.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
Amazon. Amazon web services. http://aws.amazon.com/, 1996--2008.
 
3
N. Carvalho, J. Pereira, and L. Rodrigues. Towards a generic group communication service. In On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE, pages 1485--1502. Springer Berlin / Heidelberg, 2006.
 
4
G. Czajkowski. Resource consumption management api. Technical report, Java Community Process (JSR'284), 2007.
 
5
M. Grogan. Scripting for the java platform. Technical report, Java Community Process (JSR'223), 2006.
6
 
7
Y. Royon, S. Frénot, and F. L. Mouel. Virtualization of service gateways in multi-provider environments. In Component-Based Software Engineering, pages 385--392. SpringerLink, 2006.
 
8
9
 
10
The Apache Software Foundation. Apache felix. http://felix.apache.org/.
 
11
The Eclipse Foundation. Equinox. http://www.eclipse.org/equinox/.
 
12
The Knopflerfish Project. Knopflerfish. http://www.knopflerfish.org/.
 
13
The OSGi Alliance. Osgi service platform. http://osgi.org/osgi technology/download_specs.asp, Aug. 2005. Release 4.
 
14
 
15
I. Yamasaki. Monitoring and managing resource usage on osgi frameworks. In OSGi World Congress, 2005.

Collaborative Colleagues:
Miguel Matos: colleagues
António Sousa: colleagues