04.11.2014 Views

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

elektronická verzia publikácie - FIIT STU - Slovenská technická ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Semantic Web Services 169<br />

their services and consumers can find the available ones. The quality of service part of the<br />

SOA stack includes the following elements. Policy is a set of rules under which the service<br />

provider makes the service available to consumers. Security is the set of rules that might be<br />

applied to the identification, authorization, and access control of service consumers invoking<br />

services. Transaction is the set of attributes that might be applied to a group of services to<br />

deliver a consistent result. Management is the set of attributes that might be applied to<br />

managing the services provided or consumed.<br />

Functions<br />

Quality of Service<br />

Business Process<br />

Service registry<br />

Service<br />

Service Description<br />

Service Communication<br />

Protocol<br />

Policy<br />

Security<br />

Transaction<br />

Management<br />

Transport<br />

Figure 6-1. SOA stack (retrieved from [31]).<br />

The main advantages of SOA can be summarized as follows:<br />

– SOA provides loosely coupled services which can be thus very easily distributed. This<br />

contributes to its effective usage in distributed, grid computing [18].<br />

– SOA provides an effective way for software application integration.<br />

– SOA uses platform independent building elements contributing to higher flexibility<br />

of the software application.<br />

Despite of that SOA offers several advantages there are cases when it is not suitable. First,<br />

if the application is already built, its modification to SOA requires redesigning and reimplementation.<br />

This means that there will be additional costs. The access to certain functionalities<br />

has also disadvantages. If some modules are closely related and they communicate extensively,<br />

the use of web services may be an unreasonable trade off. Web services are not<br />

suitable also when the component is highly bound to a user interface. In each situation<br />

concrete circumstances and requirements need to be analyzed.<br />

6.1.2 Web Services<br />

The term web service [3, 24] is nowadays a very often used word, although not always<br />

in the same meaning. Even though there exist a lot of definitions of web services, there<br />

exist discussions which attributes must the service have [41]. For us, the most appropriate<br />

definition is the one, given by W3C:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!