Deployment of Services-Oriented Applications Integrating Physical and IT Systems

Abstract

Abstract

A Meta-Model Approach for the Deployment of Services-oriented Applications

“…In addition, the implementation was largely decentralized, i.e. each EE maintained a model of each deployed application via local introspections and via the received deployment plans [6]. It turned out that this architecture suffered from several limitations:…”

“…The purpose of this paper is to focus on the last two issues (more information about the first issues can be found in [6]). The work presented here has been carried out and evaluated in the PISE 1 project.…”

“…Surprisingly enough, there is still no consensus on the activities being part of the deployment process and this situation often leads to misunderstandings [6]. In the SOC context, we started from Carnagiza's proposal [3] and defined the following deployment activities that need to be addressed (here, the term software entity means both service and services applications):…”

“…Our objective was to define a meta-model precise enough to allow the effective deployment of services applications. This paper only gives an overview of this meta-model and focuses on the information needed to enable a clean cohabitation of services applications, that may share services implementation, and to solve the services implementations sharing and the instances management (for more information on the previous meta-model see [6]). This approach has been inspired by previous work made in the ADL field [9].…”

Integrating UPnP in a development environment for service-oriented applications

“…This selection phase takes into account multiple constraints expressed in the abstract composition (security and logging requirements for instance) and the current status of the physical targets. The deployment manager has also to generate the glue code necessary to run the concrete composition [10].…”