Service-Oriented Processes

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):  
W. L. Yeung

Business collaboration is increasingly conducted over the Internet. Trading parties require business-level protocols for enabling their collaborative processes and a number of standardised languages, and approaches have been proposed for specifying business-level protocols. To illustrate the specification of web services based collaborative processes, three inter-related specification languages, namely, the ebXML Business Process Specification Schema (BPSS), the Web Service Business Process Execution Language (WSBPEL), and the Web Services Conversations Language (WSCL) are discussed in this chapter. A contract negotiation protocol is used as an example to illustrate the concepts involved in the specification. The chapter also discusses different strategies for deploying these specification languages.


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

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):  
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.


Author(s):  
Hossana H. Aberra

SAP Business Blueprint is a vital part of SAP implementation exercise. A well-defined business blueprint may set the foundation for successful implementation of the subsequent SAP implementation phases; provided that the necessary project success factors are in position. This chapter clarifies some of the concepts behind SAP Business Blueprint. It explains and views the ERP solution as an integral component of the design process. It outlines different aspects of SAP business blueprinting from technical infrastructure enablement, while setting the solution landscape, to the details of business process defi- nition. It points out how the SAP Solution Manager facilitates (business process) architecture-driven implementation through tight integration with ARIS Business Architect for NetWeaver. It details ways of moving toward Service Oriented Architecture (SOA) utilizing Enterprise Services, and an approach for generating Business Process Execution Language (BPEL) models using Web Services Description Language (WSDL) imported objects for analysis.


Sign in / Sign up

Export Citation Format

Share Document