Making the Business Process Execution Language (BPEL) Flexible

Author(s):  
Daniela Wolff ◽  
Nishant Singh

The Business Process Execution Language (BPEL) is a process modeling language which uses standard control constructs to define a workflow. But, today‘s enterprises need to be agile to cope with increasing change, uncertainty and unpredictability. Therefore, automating agile business processes is still a challenge as they are normally knowledge intensive and can be planned to a limited degree. The execution order depends heavily on the case, which has to be performed. So instead of modeling all possible cases and situations which might occur in a knowledge intensive process we introduced an approach which uses semantic technologies and rules. Business rules can be utilized to allow for case-specific adaptation of process steps. A component was developed which allow during run-time rules to automatically detect the state of the case and to determine the necessary process adaptations.

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

Author(s):  
Dimka Karastoyanova ◽  
Tammo van Lessen ◽  
Frank Leymann ◽  
Zhilei Ma ◽  
Joerg Nitzche ◽  
...  

Even though process orientation/BPM is a widely accepted paradigm with heavy impact on industry and research the available technology does not support the business professionals’ tasks in an appropriate manner that is in a way allowing processes modeling using concepts from the business domain. This results in a gap between the business people expertise and the IT knowledge required. The current trend in bridging this gap is to utilize technologies developed for the Semantic Web, for example ontologies, while maintaining reusability and flexibility of processes. In this chapter the authors present an overview of existing technologies, supporting the BPM lifecycle, and focus on potential benefits Semantic Web technologies can bring to BPM. The authors will show how these technologies help automate the transition between the inherently separate/detached business professionals’ level and the IT level without the burden of additional knowledge acquisition on behalf of the business professionals. As background information they briefly discuss existing process modeling notations like the Business Process Modeling Notation (BPMN) as well as the execution centric Business Process Execution Language (BPEL), and their limitations in terms of proper support for the business professional. The chapter stresses on the added value Semantic Web technologies yield when leveraged for the benefit of BPM. For this the authors give examples of existing BPM techniques that can be improved by using Semantic Web technologies, as well as novel approaches which became possible only through the availability of semantic descriptions. They show how process model configuration can be automated and thus simplified and how flexibility during process execution is increased. Additionally, they present innovative techniques like automatic process composition and auto-completion of process models where suitable process fragments are automatically discovered to make up the process model. They also present a reference architecture of a BPM system that utilizes Semantic Web technologies in an SOA environment.


Author(s):  
Matthias Kloppmann ◽  
Dieter Koenig ◽  
Simon Moser

This chapter introduces a set of languages intended to model and run business processes. The Business Process Modeling Notation 1.1 (BPMN) is a notation used to graphically depict business processes. BPMN is able to express choreographies, i.e. the cooperation of separate, autonomous business processes to jointly achieve a larger scenario. Since BPMN is only a notation, there is no specification for a meta-model that allows rendering BPMN choreographies into an executable form. This chapter describes how the Service Component Architecture (SCA) and the Web Services Business Process Execution Language (WS-BPEL) help to close that gap. BPMN, SCA and WS-BPEL can jointly be used and combined to model, deploy and execute business process choreographies. We will also integrate the related BPEL4People specification, since BPMN allows human ‘user tasks’, but WS-BPEL focuses only on automated business process. The authors argue that, based on these specifications, the dichotomy between modeling and execution can be addressed efficiently. In this chapter, we will show that a key aspect of the future of Business Process Management is to combine graphical modeling (via BPMN) with a precise specification of an executable business process (via WS-BPEL and related standards).


2011 ◽  
pp. 155-190 ◽  
Author(s):  
C. Ouyang ◽  
W. Van der Aalst ◽  
M. Dumas

The Business Process Execution Language for Web Services (BPEL) is an emerging standard for specifying the behaviour of Web services at different levels of details using business process modeling constructs. It represents a convergence between Web services and business process technology. This chapter introduces the main concepts and constructs of BPEL and illustrates them by means of a comprehensive example. In addition, the chapter reviews some perceived limitations of BPEL and discusses proposals to address these limitations. The chapter also considers the possibility of applying formal methods and Semantic Web technology to support the rigorous development of service-oriented processes using BPEL.


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.


Author(s):  
Gábor Kovács

This chapter gives an overview of modeling languages used for modeling business environment, abstract workflows, executable business processes, and business data. The languages are either abstract that primarily serve the purposes of business modeling or executable that can be run in a business process engine. The business process modeling languages BPMN (Business Process Modeling Language) and BPEL (Business Process Execution Language) are in the center of the discussion; however, the core concepts and application area of other languages are given as well. An important part of business modeling is the description of business collaboration and the format of business information exchanged. XML based data modeling languages are used for describing such contracts. Throughout the chapter the focus is on the underlying concepts of these languages rather than the syntax.


Sign in / Sign up

Export Citation Format

Share Document