Hide Notes 

Slide 1: WS-BPEL 2.0 TC Briefing Charlton Barreto Adobe Senior Computer Scientist/Architect charltonb@adobe.com
Slide 2: WSDL Message receive exit reply throw invoke rethrow assign Basic Activities empty compensateScope WS-BPEL 2.0 42 XML Schema Type XML Schema Element wait Variables partner link partner link Partner Links Port Type 1 Partner Link Type validate compensate MyProcess receive extensionActivity Port Type 2 invoke receive invoke flow pick invoke event handler event handler fault handler fault handler sequence forEach while Structured Activities scope Handlers if-else compensation handler termination handler repeatUntil Properties Correlation Sets Property 1 Property 2
Slide 3: WS-BPEL 2.0  BPEL is the Web Services Orchestration standard from OASIS  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 bee’•pel, bee•pel’, beep’•əl, bip’•əl, ta’mātō, tō’måtō  An XML-based grammar for describing the logic to orchestrate the interaction between Web services in a business process
Slide 4: Motivation  Integration continues to be a key problem facing businesses    Intra-enterprise integration (Enterprise Application Integration) Integrating with partners (Business-to-Business Integration) Syndication Applications are viewed as “services” Loosely coupled, dynamic interactions Heterogeneous platforms No single party has complete control How do you compose services in this domain?  Web services  move towards service-oriented computing      Service composition 
Slide 5: Why the Need For BPEL?  WSDL defined Web services have a stateless interaction model  Messages are exchanged using   Synchronous invocation Uncorrelated asynchronous invocations  Most “real-world” business processes require a more robust interaction model  Messages exchanged in a two-way, peer-to-peer conversation lasting minutes, hours, days, etc.  BPEL provides the ability to express stateful, long-running interactions
Slide 6: Why BPEL?      WS-* stack did not address conversation description Combines graph-oriented and block-oriented programming Supports the addressability of processes through data they use Implicit creation and termination Parallelism    Flows Event Handlers Parallel ForEach  Abstract BPEL for observable behaviour and process templating
Slide 7: Why not BPEL?  BPEL is NOT for service creation     Java Standard Edition Java Enterprise Edition .NET Adobe LiveCycle ES BPDM BPMN Adobe LiveCycle Designer CDL  BPEL is NOT a UI     BPEL is NOT designed for choreography 
Slide 8: What’s New since BPEL 1.1  Data Access           XSD complex-type variable Simplified XPath expressions Simplified message access on WSDL Elaborated <copy> operation behavior in <assign> keepSrcElement option in <copy> New <extensionAssignOperation> Standardized XSLT 1.0 function for use within XPath expressions XML data validation model New <validate> activity “inline” variable initialization at the point of variable declaration
Slide 9: What’s New since BPEL 1.1  Scope Model      Elaboration of Compensation & Fault Models Scope Isolation and Control Links interaction in <flow> New <rethrow> activity <terminationHandler> exitOnStandardFault Join-style Correlation Set Scope-local PartnerLink declaration initializePartnerRole messageExchange construct  Message Operations    
Slide 10: What’s New since BPEL 1.1  Other New Activities    <forEach> <repeatUntil> <extensionActivity> <switch> -> <if>-<elseif>-<else> <terminate> -> <exit> Improved event handling <repeatEvery> alarm feature <extension> directive <import>  Syntactic [extreme] makeover    Other additions    
Slide 11: WS-BPEL Schedule  Status   OASIS standard - April 2007 Approximately 20 current TC members  Down from several hundred  Five organizations have certified use of WS-BPEL in product  ActiveEndpoints, IBM, Intalio, SEEBURGER, Sun Active participation Spec editor  Adobe a member of the TC since 2003  
Slide 12: WS-BPEL Schedule  Next steps  OASIS Symposium - April 15-20, 2007 San Diego, California, USA     Business Process Sessions - April 16 Lightning Rounds – April 16 Mini-Talk – April 17 WS-BPEL Workshop - April 18  Start using WS-BPEL today