Web Services Business Process Execution Language Version 2.0
Public Review Draft 02, 20 November, 2006
Diane Jordan, IBM
John Evdemon, Microsoft
Alexandre Alves, BEA
Assaf Arkin, Intalio
Sid Askary, Individual
Ben Bloch, Systinet
Francisco Curbera, IBM
Mark Ford, Active Endpoints, Inc.
Yaron Goland, BEA
Alejandro Guízar, JBoss, Inc.
Neelakantan Kartha, Sterling Commerce
Canyang Kevin Liu, SAP
Rania Khalaf, IBM
Dieter König, IBM
Mike Marin, IBM, formerly FileNet Corporation
Vinkesh Mehta, Deloitte
Satish Thatte, Microsoft
Danny van der Rijn, TIBCO Software
Prasad Yendluri, webMethods
Alex Yiu, Oracle
This document defines a language for specifying business process behavior based on Web Services. This language is called Web Services Business Process Execution Language (abbreviated to WS-BPEL in the rest of this document). Processes in WS-BPEL export and import functionality by using Web Service interfaces exclusively.
Business processes can be described in two ways. Executable business processes model actual behavior of a participant in a business interaction. Abstract business processes are partially specified processes that are not intended to be executed. An Abstract Process may hide some of the required concrete operational details. Abstract Processes serve a descriptive role, with more than one possible use case, including observable behavior and process template. WS-BPEL is meant to be used to model the behavior of both Executable and Abstract Processes.
WS-BPEL provides a language for the specification of Executable and Abstract business processes. By doing so, it extends the Web Services interaction model and enables it to support business transactions. WS-BPEL defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces.
This document was last revised or approved by the WS-BPEL TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at www.oasis-open.org/committees/wsbpel.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( www.oasis-open.org/committees/wsbpel/ipr.php.)
The non-normative errata page for this specification is located at www.oasis-open.org/committees/wsbpel.
Special thanks to Peter Furniss for his contributions to the WS-BPEL TC in managing the automated issues list.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
Copyright © OASIS Open 2003, 2006. All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
Web Services Business Process Execution Language Version 2.0 1
Public Review Draft 02, 20 November, 2006 1
Table of Contents 4
1. Introduction 5
2. Notational Conventions 8
3. Relationship with Other Specifications 10
4. Static Analysis of a Business Process 12
5. Defining a Business Process 13
6. Partner Link Types, Partner Links, and Endpoint References 36
7. Variable Properties 40
8. Data Handling 45
9. Correlation 74
10. Basic Activities 84
11. Structured Activities 98
12. Scopes 115
13. WS-BPEL Abstract Processes 147
14. Extension Declarations 164
15. Examples 166
16. Security Considerations 191
Appendix A. Standard Faults 192
Appendix B. Static Analysis requirement summary (Non-Normative) 194
Appendix C. Attributes and Defaults 207
Appendix D. Examples of Replacement Logic 209
Appendix E. XML Schemas 217
Appendix F. Revision History 259
Appendix G. References 275
Appendix H. Committee Members (Non-Normative) 277