BPEL (Business Process Execution Language) for Web services is an XML-based language designed to enable task-sharing for a distributed computing or grid computing environment - even across multiple organizations - using a combination of Web services. Written by developers from BEA Systems, IBM, and Microsoft, BPEL combines and replaces IBM's WebServices Flow Language (WSFL) and Microsoft's XLANG specification. (BPEL is also sometimes identified as BPELWS or BPEL4WS.)
Using BPEL, a programmer formally describes a business process that will take place across the Web in such a way that any cooperating entity can perform one or more steps in the process the same way. In a supply chain process, for example, a BPEL program might describe a business protocol that formalizes what pieces of information a product order consists of, and what exceptions may have to be handled. The BPEL program would not, however, specify how a given Web service should process a given order internally.
 |
Getting started with BPEL |
| To explore how the BPEL is used in the enterprise, here are some additional resources: |
| BPEL Learning Guide: This SearchSOA.com learning guide introduces you to Business Process Execution Language for Web services, or BPEL4WS. In this BPEL learning guide, you'll find articles, tips, expert advice, white papers and more that will explain how BPEL fits into the world of SOA and Web services. |
| Service contracts for BPEL 2.0: The BPEL orchestration standard allows for contract-first Web services design inside an SOA. This tip identifies best practices for using BPEL and WSDL for service contracts. |
| Las Vegas bets on BPEL: BPEL-based applications are being used by the City of Las Vegas to reduce the bureaucratic paper work at its water treatment facility. |