An Outlook on the Future of Services and Non-Functional Properties Management

Author(s):  
Carlos Pedrinaci ◽  
Dong Liu ◽  
Guillermo Álvaro ◽  
Stefan Dietze ◽  
John Domingue

Over the years a large number of technologies have been devised in order to describe service interfaces, e.g., WSDL (Booth & Liu, 2007), combine services in a process-oriented way, e.g., WS-BPEL (OASIS Web Services Business Process Execution Language (WSBPEL) TC, 2007), provide support for transactions, e.g., WS-Transaction, and cover non-functional properties (NFP) of services such as security aspects and the like, see for instance WS-Security and WS-Policy to name just a few (Erl, 2007). There is in an overwhelming stack of technologies and specifications dubbed WS-*, covering most aspects researchers have faced thus far. There remain nonetheless a number of outstanding issues (Papazoglou, Traverso, Dustdar, & Leymann, 2007) some of which are of a general technical nature, and some, indeed, are specifically related to NFPs. The latter will be dealt with in more detail in the next section.

2005 ◽  
pp. 317-342 ◽  
Author(s):  
Rania Khalaf ◽  
Nirmal Mukhi ◽  
Francisco Curbera ◽  
Sanjiva Weerawarana

2018 ◽  
Vol 7 (4) ◽  
pp. 2422
Author(s):  
Senthil Velan S ◽  
Sam Jaffray M

Service Oriented Architecture (SOA) facilitates seamless application integration through standards-based predefined web services. During integration, Business Process Execution Language (BPEL) plays a vital role in composing existing Web Services thereby achieving a service based workflow model.   Due to frequently changing business requirements, it becomes very much essential for an SOA application to have the capability to dynamically bind with an alternate service rather than statically fixing the services in a given composition. However, BPEL lacks support for the run-time inclusion of a new Web Service or functionality. Aspects overcome this limitation by providing support to independently encapsulate the cross-cutting functionalities by separating them from the core business logic. Using AOP, it is possible to achieve dynamic binding in web service composition. To illustrate the embedding of AOP constructs into a BPEL process, this paper implements a case study on distributed e-HealthCare system. Further, two core design level properties namely, cohesion and coupling have been measured and the impact of introduction of AO into a composed BPEL process has also been discussed. Empirical evaluation of the design level properties shows that cohesion improves by the introduction of AOP in BPEL.


2014 ◽  
Vol 666 ◽  
pp. 301-304
Author(s):  
Yu Lin Liu ◽  
Gui Yuan Zhai ◽  
Jian Tao Zhou

BPEL is a Business Process Execution Language, BPEL process complish the cooperation of Web services through exchanging messages between services. Some privacy data should be collected and exposed in BPEL process, the leaking of privacy data will bring troubles to the user of Web service. So the paper’s aim is analyzing and verifying whether the usage or the transmission of privacy data in BPEL process violate the privacy statute. This paper establishs a BPEL CPN model using modeling method and uses extended P3P policy to describe user’s requirements, finally a prototype system is designed and developed. The result of the experiment can show whether the usage or the transmission of privacy data in BPEL violate the privacy statute and can show the default informations in detail.


Sign in / Sign up

Export Citation Format

Share Document