scholarly journals Business Process Execution From the Alignment Between Business Processes and Web Services: A Semantic and Model-Driven Modernization Process

IEEE Access ◽  
2020 ◽  
Vol 8 ◽  
pp. 93346-93368
Author(s):  
Encarna Sosa Sanchez ◽  
Pedro J. Clemente ◽  
Jose M. Conejero ◽  
Alvaro E. Prieto
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Processes ◽  
Model Driven ◽  
Process Execution ◽  
Business Process Execution ◽  
Modernization Process

A Model-based Approach for Diagnosing Fault in Web Service Processes

2013 ◽  
pp. 92-116
Author(s):  
Yuhong Yan ◽  
Philippe Dague ◽  
Yannick Pencolé ◽  
Marie-Odile Cordier
Keyword(s):  
Web Services ◽  
Web Service ◽  
Business Process ◽  
Business Processes ◽  
Formal Model ◽  
Service Orchestration ◽  
Model Based ◽  
Architecture Framework ◽  
Web Service Orchestration ◽  
Business Process Execution

Web services based on a service-oriented architecture framework provide a suitable technical foundation for business process management and integration. A business process can be composed of a set of Web services that belong to different companies and interact with each other by sending messages. Web service orchestration languages are defined by standard organizations to describe business processes composed of Web services. A business process can fail for many reasons, such as faulty Web services or mismatching messages. It is important to find out which Web services are responsible for a failed business process because we could penalize these Web services and exclude them from the business process in the future. In this paper, we propose a model-based approach to diagnose the faults in a Web service-composed business process. We convert a Web service orchestration language, more specifically BPEL4WS, into synchronized automata, so that we have a formal description of the topology and variable dependency of the business process. After an exception is thrown, the diagnoser can calculate the business process execution trajectory based on the formal model and the observed evolution of the business process. The faulty Web services are deduced from the variable dependency on the execution trajectory. We demonstrate our diagnosis technique with an example.

The Business Process Execution Language for Web Services

2005 ◽  
pp. 317-342 ◽  
Author(s):  
Rania Khalaf ◽  
Nirmal Mukhi ◽  
Francisco Curbera ◽  
Sanjiva Weerawarana
Keyword(s):  
Web Services ◽  
Business Process ◽  
Business Process Execution Language ◽  
Process Execution ◽  
Business Process Execution

A Model-Based Approach for Diagnosing Fault in Web Service Processes

2011 ◽  
pp. 1970-1993 ◽  
Author(s):  
Yuhong Yan ◽  
Philippe Dague ◽  
Yannick Pencolé ◽  
Marie-Odile Cordier
Keyword(s):  
Web Services ◽  
Web Service ◽  
Business Process ◽  
Business Processes ◽  
Formal Model ◽  
Formal Description ◽  
Service Orchestration ◽  
Model Based ◽  
Web Service Orchestration ◽  
Business Process Execution

Web service orchestration languages are defined to describe business processes composed of Web services. A business process can fail for many reasons, such as faulty Web services or mismatching messages. It is important to find out which Web services are responsible for a failed business process because we could penalize these Web services and exclude them from the business process in the future. In this paper, we propose a model-based approach to diagnose the faults in a Web service-composed business process. We convert a Web service orchestration language, BPEL4WS, into synchronized automata, so that we have a formal description of the topology and variable dependency of the business process. After an exception is thrown, the diagnoser can calculate the business process execution trajectory based on the formal model and the observed evolution of the business process. The faulty Web services are deduced from the variable dependency on the execution trajectory.

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

2012 ◽  
pp. 550-561
Author(s):  
Carlos Pedrinaci ◽  
Dong Liu ◽  
Guillermo Álvaro ◽  
Stefan Dietze ◽  
John Domingue
Keyword(s):  
Web Services ◽  
Functional Properties ◽  
Business Process ◽  
Business Process Execution Language ◽  
The Future ◽  
Process Oriented ◽  
Process Execution ◽  
Business Process Execution ◽  
General Technical

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.

Sign in / Sign up

Export Citation Format

Share Document