BPEL

Resources


BPEL4People and WS-HumanTask to OASIS

The BPEL4People and WS-HumanTask specs are headed to OASIS, resulting in a new BPEL4People Technical Committee (TC) - expect to see an announcement and call for participation soon. The TC will focus on defining human interactions (human tasks) as part of a WS-BPEL process, enabling these definitions to be exposed as web services.

Active Endpoints Delivers BPEL4People Tool

By Darryl K. Taft, eWeek 20 July 2007. Active Endpoints, which makes SOA orchestration solutions, is rolling out ActiveBPEL for People, a product that adds workflow and human interaction capabilities to the company's ActiveBPEL Enterprise servers. Fred Holahan, founder and chairman of Active Endpoints, of Shelton, Conn., said the company based its technology on the emerging BPEL4People specifications, which bring the human element to the BPEL (Business Process Execution Language). ActiveBPEL for People, which became generally available July 19, is architecturally aligned with both the BPEL4People and WS-HumanTask specifications, which form the foundation of standards-based human interaction using BPEL, Holahan said. Active Endpoints - along with Adobe Systems, BEA Systems, IBM, Oracle and SAP - co-authored BPEL4People and WS-HumanTask, he said.

BPEL: Service composition for SOA

Get started developing business processes based on the Business Process Execution Language. In this article, an excerpt from Business Process Execution Language for Web Services, 2nd Edition, by Matjaz Juric, Poornachandra Sarang, and Benny Mathew (Packt Publishing, January 2006; ISBN 1904811817), Juric explains the importance of the Business Process Execution Language to service-oriented architecture and shows readers how to develop their own BPEL processes.

8

BPEL Cookbook: Best Practices for SOA-based integration and composite applications development

Book published by Packt Publishing in June 2006. Ten practical real-world case studies combining business process management and web services orchestration. Real-world BPEL recipes for SOA integration and Composite Application development. Combining business process management and web services orchestration. Authors: Matjaz Juric, Stany Blanvalet, Jeremy Bolie, Michael Cardella, Sean Carey, Praveen Chandran, Yves Coene, Kevin Geminiuc, Arun Poduval, Lawrence Pravin, Jerry Thomas, Doug Todd, The Hoa Nguyen, Markus Zirn, Harish Gaur

An Introduction to BPEL

By Kumar Raj Moorthy. Business Process Execution Language (BPEL) is a XML-based language used to define enterprise business processes within Web services.

The Case Against BPEL: Why the Language is Less Important Than You Think

David Chappell: Even amid all of the noise around web services, the Business Process Execution Language (BPEL) gets a lot of attention. Now owned by OASIS, the language was originally created by IBM and Microsoft, and it's supported today in many products. These products are certainly useful, and some organizations are using BPEL successfully. Yet the language gets far more attention than it deserves. Here's why.

2

SOA Best Practices: The BPEL Cookbook

Learn advanced BPEL concepts and best practices for development, deployment, and administration from the architects implementing them in real-world applications.

Automating business processes and transactions in Web services

James Snell's introduction to BPELWS, WS-Coordination, and WS-Transaction

Business Process Execution Language for Web Services version 1.1

BPEL4WS provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. BPEL4WS 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.

Business processes: Understanding BPEL4WS, Part 1

The recently released Business Process Execution Language for Web Services (BPEL4WS) specification is positioned to become the Web services standard for composition. It allows you to create complex processes by creating and wiring together different activities that can, for example, perform Web services invocations, manipulate data, throw faults, or terminate a process. These activities may be nested within structured activities that define how they may be run, such as in sequence, or in parallel, or depending on certain conditions. This series of articles aims to give readers an understanding of the different components of the language, and teach them how to create their own complete processes.