
Emerging Web Services Technology
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
Ricardo Quintero, Victoria Torres and Vicente Pelechano Abstract. The development of composite Web Services is being specified in a more declarative way than imperative programming. In this context, conceptual modeling has been the most accepted solution. Conceptual modeling of Web services has been done using behavioral models (like activity diagrams) considering mainly the dynamic view. We believe that, besides the dynamic aspects, the models should capture structural requirements between web service operations. In this way, behavioral models could be complemented with a structural model. In this paper we introduce a Web service composition modeling solution, following the MDA approach, considering both -structural and dynamic properties- enriched with semantic constraints in order to automatically generate composite Web services implemented in BPEL. Keywords. Web Services, Composition, Conceptual Modeling, Web Engineering, MDA.
1. Introduction
Current e-business processes have, as an important requirement, the integration (the composition) of diverse application functionalities. The main strategy that has been followed by the industry is the use of Web Services to export the functionality and the use of programming languages to define service composition [11].
Because the majority of them were not designed with this goal in mind, they do not have abstractions for this objective, so usually the composition definitions are cumbersome. In contrast, conceptual modeling offers abstractions and models in order to define this composition at a high level of abstraction [12,13,14]. The main focus of these approaches is on dynamic concerns (as in UML Activity diagrams) forgetting the structural concerns. Although there are some model-driven solutions that generate in a semi-automatic way Web services and WS-BPEL [15], the problem with these modeling approaches is some lack of semantics that makes it difficult to capture the composition requirements in a precise way. This drawback does make it unfeasible to build modeling tools that validate models and generate complete and fully operative implementations. We consider that structural and dynamic models are needed in order to capture these issues, especially static and dynamic binding properties between the Web services that are being composed (the main focus of this work). Moreover it could be used as a way to export the functionality of the application: by means of methodological guidelines it is possible to detect functional groups from the business layer (specified by a structural model) and export them as a set of Web services. These Web services could be consumed by other applications to enable collaboration with other third parties. In this work we introduce, as a main contribution, two models (the Service Model and the Dynamic Model for Service Composition) which allow us specifying the structural and dynamic requirements of Web services compositions by using aggregation/ association relationships with a precise semantics, defined in the context of a multidimensional framework [3]. In order to obtain the equivalent software artifacts of these models we follow a Model driven approach where the application of a set of transformation rules generates the corresponding WS-BPEL specification.
This solution extends ourWeb engineering method Object-OrientedWeb Solutions (OOWS) [1] in order to capture the collaborative requirements that are necessary to produce (in an automatic way) complete collaborative Web applications. The remainder of the paper is structured as follows: section 2 explains our proposal to conceptual modeling of Services, section 3 shows the introduced models from the point of view of their structural properties, section 4 explains the dynamic properties and the transformation of the models to a specific Web service composition technology (in this case we choose WS-BPEL [4], although it can be another -like BPML [5]), section 5 explains our code generation strategy and finally, section 6 presents conclusions and further work.
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.