Facilitating semantic adaptation of web services at runtime using a meta-data layer

T. Baker, D. Lamb, A. Taleb-Bendiab, D. Al-Jumeily

Research output: Chapter in Book/Conference proceeding with ISSN or ISBNConference contribution with ISSN or ISBNpeer-review

Abstract

The migration of legacy system designs to full Service-Oriented applications raises several interesting issues, particularly surrounding co-ordination and management of the emerging system structure. Existing and emerging SOA and Web standards and technologies such as WSDL, BPEL and WS-BPEL are promoted as facilitating the design of fully-adaptive and scalable enterprise applications. However, runtime / semantic adaptation and management of software is still in its early stages. Adhering strictly to software engineering concerns such as high cohesion and low coupling results in a software architecture that promotes component (i.e. Service) reuse and lends itself to scalability. Equally, late runtime-binding, re-binding and failover systems demonstrate the flexibility in these system architectures, yet their lack of adaptability is apparent when higher-level runtime alterations would be beneficial. Current work towards this goal, such as OWL-S, still require human input at each change in order to facilitate true semantic adaptation at runtime, rendering it impractical for all but the most trivial of adaptations. This paper discusses current architectures' shortcomings along with a proposal for a new approach within existing SOA methodologies. This approach supports source-code semantic flexibility via an intermediary Meta Data Layer (MDL), providing a layer of separation between the source code and the service.
Original languageEnglish
Title of host publicationProceedings - 3rd International Conference on Developments in eSystems Engineering, DeSE 2010
DOIs
Publication statusPublished - 2010

Fingerprint

Dive into the research topics of 'Facilitating semantic adaptation of web services at runtime using a meta-data layer'. Together they form a unique fingerprint.

Cite this