WSBPEL 2'0 TC Briefing

1
WS-BPEL 2.0TC Briefing

• Charlton Barreto
• Adobe Senior Computer Scientist/Architect
• charltonb_at_adobe.com

2
WS-BPEL 2.0
3
WS-BPEL 2.0

• BPEL is the Web Services Orchestration standard
  from OASIS
• beepel, beepel, beep?l, bip?l, tamato,
  tomåto
• 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
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
• Web services ? move towards service-oriented
  computing
• Applications are viewed as services
• Loosely coupled, dynamic interactions
• Heterogeneous platforms
• No single party has complete control
• Service composition
• How do you compose services in this domain?

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

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

7
Why not BPEL?

• BPEL is NOT for service creation
• Java Standard Edition
• Java Enterprise Edition
• .NET
• Adobe LiveCycle ES
• BPEL is NOT a UI
• BPDM
• BPMN
• Adobe LiveCycle Designer
• BPEL is NOT designed for choreography
• CDL

8
Whats New since BPEL 1.1

• Data Access
• XSD complex-type variable
• Simplified XPath expressions
• Simplified message access on WSDL
• Elaborated ltcopygt operation behavior in ltassigngt
• keepSrcElement option in ltcopygt
• New ltextensionAssignOperationgt
• Standardized XSLT 1.0 function for use within
  XPath expressions
• XML data validation model
• New ltvalidategt activity
• inline variable initialization at the point of
  variable declaration

9
Whats New since BPEL 1.1

• Scope Model
• Elaboration of Compensation Fault Models
• Scope Isolation and Control Links interaction in
  ltflowgt
• New ltrethrowgt activity
• ltterminationHandlergt
• exitOnStandardFault
• Message Operations
• Join-style Correlation Set
• Scope-local PartnerLink declaration
• initializePartnerRole
• messageExchange construct

10
Whats New since BPEL 1.1

• Other New Activities
• ltforEachgt
• ltrepeatUntilgt
• ltextensionActivitygt
• Syntactic extreme makeover
• ltswitchgt -gt ltifgt-ltelseifgt-ltelsegt
• ltterminategt -gt ltexitgt
• Other additions
• Improved event handling
• ltrepeatEverygt alarm feature
• ltextensiongt directive
• ltimportgt

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
• Adobe a member of the TC since 2003
• Active participation
• Spec editor

12
WS-BPEL Schedule

• Next steps
• OASIS Symposium - April 15-20, 2007San 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