1. WS-BPEL 2.0 TC Briefing Charlton Barreto Adobe Senior Computer Scientist/Architect charltonb@adobe.com

2. WS-BPEL 2.0 MyProcess invoke receive invoke Handlers fault handler event handler fault handler compensation handler termination handler event handler Partner Links Partner Link Type Port Type 1 Port Type 2 partner link partner link Variables 42 WSDL Message XML Schema Type XML Schema Element Properties Correlation Sets Property 1 Property 2 Structured Activities if-else while scope pick sequence flow repeatUntil forEach Basic Activities receive reply invoke throw exit wait empty compensatevalidate assign rethrow extensionActivity compensateScope

3. WS-BPEL 2.0 n BPEL is the Web Services Orchestration standard from OASIS l bee’pel, beepel’, beep’əl, bip’əl, ta’mātō, tō’måtō n An XML-based grammar for describing the logic to orchestrate the interaction between Web services in a business process BPEL Historical Timeline Dec 2000 Microsoft publishes XLANG March 2001 IBM publishes WSFL July 2002 IBM, Microsoft and BEA converge WSFL & XLANG into BPEL4WS 1.0 March 2003 BPEL4WS is submitted to OASIS May 2003 OASIS publishes BPEL4WS 1.1 April 2007 WS-BPEL 2.0 released BPEL Historical Timeline Dec 2000 Microsoft publishes XLANG March 2001 IBM publishes WSFL July 2002 IBM, Microsoft and BEA converge WSFL & XLANG into BPEL4WS 1.0 March 2003 BPEL4WS is submitted to OASIS May 2003 OASIS publishes BPEL4WS 1.1 April 2007 WS-BPEL 2.0 released

4. Motivation n Integration continues to be a key problem facing businesses l Intra-enterprise integration (Enterprise Application Integration) l Integrating with partners (Business-to-Business Integration) l Syndication n Web services  move towards service-oriented computing l Applications are viewed as “services” l Loosely coupled, dynamic interactions l Heterogeneous platforms l No single party has complete control n Service composition l How do you compose services in this domain?

5. Why the Need For BPEL? n WSDL defined Web services have a stateless interaction model l Messages are exchanged using n Synchronous invocation n Uncorrelated asynchronous invocations n Most “real-world” business processes require a more robust interaction model l Messages exchanged in a two-way, peer-to-peer conversation lasting minutes, hours, days, etc. n BPEL provides the ability to express stateful, long-running interactions

6. Why BPEL? n WS-* stack did not address conversation description n Combines graph-oriented and block-oriented programming n Supports the addressability of processes through data they use n Implicit creation and termination n Parallelism l Flows l Event Handlers l Parallel ForEach n Abstract BPEL for observable behaviour and process templating

7. Why not BPEL? n BPEL is NOT for service creation l Java Standard Edition l Java Enterprise Edition l.NET l Adobe LiveCycle ES n BPEL is NOT a UI l BPDM l BPMN l Adobe LiveCycle Designer n BPEL is NOT designed for choreography l CDL

8. What’s New since BPEL 1.1 n Data Access l XSD complex-type variable l Simplified XPath expressions l Simplified message access on WSDL l Elaborated operation behavior in l keepSrcElement option in l New l Standardized XSLT 1.0 function for use within XPath expressions l XML data validation model l New activity l “inline” variable initialization at the point of variable declaration

9. What’s New since BPEL 1.1 n Scope Model l Elaboration of Compensation & Fault Models l Scope Isolation and Control Links interaction in l New activity l l exitOnStandardFault n Message Operations l Join-style Correlation Set l Scope-local PartnerLink declaration l initializePartnerRole l messageExchange construct

10. What’s New since BPEL 1.1 n Other New Activities l n Syntactic [extreme] makeover l -> - - l -> n Other additions l Improved event handling l alarm feature l directive l

11. WS-BPEL Schedule n Status l OASIS standard - April 2007 l Approximately 20 current TC members n Down from several hundred l Five organizations have certified use of WS-BPEL in product n ActiveEndpoints, IBM, Intalio, SEEBURGER, Sun l Adobe a member of the TC since 2003 n Active participation n Spec editor

12. WS-BPEL Schedule n Next steps l OASIS Symposium - April 15-20, 2007 San Diego, California, USA n Business Process Sessions - April 16 n Lightning Rounds – April 16 n Mini-Talk – April 17 n WS-BPEL Workshop - April 18 n Start using WS-BPEL today