2. BPEL: Building Standards- Based Business Processes with Web Services Nickolas Kavantzas Principal Member, Technical Staff Oracle Application Server 10 g, Orchestration Mike Lehmann Principal Product Manager, Oracle Application Server 10 g, Orchestration Session id: 40024

3. BPEL? “B E E P L E”? “B E E – P E L L”? “B I P P L E”?

4. Web Services Meet Business Processes Web Service 1 Web Service 2 Web Service 3 Web Service 4 Web Service 5 Web Service n

5. Example Problem Space Client PO Service Credit Service Inventory Service Purchase Order Credit Check Reserve Inventory Credit Response Inventory Response Invoice Consolidate Results

6. Business Process Challenges  Coordinate asynchronous communication between services  Correlate message exchanges between parties  Implement parallel processing of activities ...  Manipulate/transform data between partner interactions  Support for long running business transactions and activities  Provide consistent exception handling ...

7. Recent History of Business Process Standards 2000/05 XLang (Microsoft) 2001/03 BPML (Intallio et al) 2001/05 WSFL (IBM) 2001/06 BPSS (ebXML) 2002/03 BPEL4WS 1.0 (IBM, Microsoft) BPEL4WS 1.1 (OASIS) 2002/062003/01 WS-Choreography (W3C) 2003/04 WSCI (Sun et al) WSCL (HP) 2002/08

8. Orchestration vs. Choreography Orchestration  Private process  Steps of an executable workflow  Process controlled by one party Choreography  Public (abstract) process  Sequence of observable messages  Conversation made up of equals Business Process ? Business Process 1 1. CheckInv 2. Available 3. Place Order ? Business Process 2 Derivation from Chris Peltz of HP JavaOne 2003 presentation

9. Business Process Execution Language for Web Services Version 1.0 released by IBM, Microsoft and BEA in August 2002 Accompanied by WS-Coordination, WS-Transaction which remain unsubmitted to standards bodies Version 1.1 submitted to OASIS April 2003 XML language for describing business processes based on Web services Convergence of XLANG (Microsoft) and WSFL (IBM) Amazing industry “consensus” in the last 6 months IBM, Microsoft, Oracle, Sun, BEA, SAP, Siebel …

10. Value Proposition  Portable business processes – Built on top of an interoperable infrastructure of Web services  Industry wide language for business processes – Common skill set and language for developers  Choice of process engines – Standards lead to competitive offerings

11. Standards Building Blocks of BPEL HTTP,IIOP, JMS, SMTP XML,Encoding SOAP WSDL UDDI Reliable Messaging Security Coordination Transport Messaging Description Discovery Quality of Service Transactions BPEL4WS Processes

12. BPEL Depends on WSDL and WSDL Extensions Service Implementation Definition Service Interface Definition Service Port Binding Port types define Operations Message Type

13. BPEL Scenario Structure............... (activities)*

14. BPEL Activities Primitive Activities  Structured Activities 

15. Partners  Declare the Web services and roles used by the process  Tied to WSDL of the process itself and the participating Web services by service link types Credit Service Partner 2 Inventory Service Partner 3 Partner 1 (the process) Purchase Service

16. Partners in BPEL <partner name=“creditChecker” serviceLinkType=“lns:creditSLT” myRole=“creditRequestor” partnerRole=“creditService”/> Purchase Process WSDL: BPEL: Purchase Process PortType:

17. Variables  Messages sent and received from partners – Persisted for long running interactions – Defined in WSDL types and messages Customer Service Process Persist Persist/ Retrieve Customer Service Persist/ Retrieve

18. Variables in BPEL Purchase Process WSDL: BPEL:

19. How is Data Manipulation Done?  Using and, data can be copied and manipulated between variables  supports XPath queries to sub-select data

20. Simple Activities  Receive – Wait for a partner inbound message – Can be the instantiator of the business process  Reply – Synchronous response to a receive activity – Response to the inbound receive from a partner  Invoke – Issue a request synchronously *or* asynchronously  Pick – Specify an inbound set of messages – Can be the instantiator of the business process – Activity completes when one of the messages arrives

21. Simple Activities Combined with Structured Activities Invoke Reply Receive

22. Sample Activities in BPEL <receive partner=“customer” portType=“lns:purchaseOrderPT" operation=“sendPurchaseOrder” variable=“PO” createInstance="yes" /> <invoke partner=“inventoryChecker” portType=“lns:inventoryPT” operation="checkINV" inputVariable="inventoryRequest" outputVariable="inventoryResponse" /> <invoke partner="creditChecker" portType=“lns:creditPT" operation="checkCRED" inputVariable="creditRequest" outputVariable="creditResponse" />... <reply partner=“customer” portType=“lns:purchaseOrderPT” operation=“sendPurchaseOrder” variable=“invoice"/>

23. Links – Control Flow

24. Correlation Customer SendPurchase ProcessPurchaseResponse PO Correlation: POResponse Correlations: Seller AsynchPurchase AsynchPurchaseResponse initiate=yes initiate=yes pattern=out initiate=no pattern=out initiate=yes initiate=no

25. Correlations in BPEL... <receive partner=“Customer” portType= " SP:PurchaseOrderPT " operation= " AsynchPurchase " variable= " PO " >... <invoke partner=“Customer” portType= " SP:CustomerPT " operation= “ ProcessPurchaseResponse " inputVariable= " POResponse " >...

26. Scopes in BPEL  Provide a shared context for subset of activities  Can contain – fault handlers – event handlers, – compensation handler variables – correlation sets  Can serialize concurrent access to variables ?... ?... (activities)*

27. Long Running Transactions and Compensation Undo Reserve Inventory ReserveInventory CancelReserveInv InventoryService CheckCredit ChargeHoldFee CancelHoldFee CreditService Undo Charge Hold Fee

28. Compensation Handlers in BPEL <invoke partner= " Seller " portType= " SP:Purchasing " operation= " CancelPurchase " inputVariable="getResponse" outputVariable="getConfirmation"> <invoke partner="Seller" portType="SP:Purchasing" operation="SyncPurchase" inputVariable="sendPO" outputVariable="getResponse">

29. Exception Handling in BPEL  catch exception – Based on WSDL port defining fault  can perform activities upon invocation <catch faultName="lns:cannotCompleteOrder" faultVariable="POFault"> <reply partner="customer" portType="lns:purchaseOrderPT" operation="sendPurchaseOrder" variable="POFault" faultName="cannotCompleteOrder"/>

30. Just Show Me How to Do it! Partner WSDL 1 Process WSDL Partner WSDL n... BPEL Scenario 1.Compile 2.Package 3.Deploy Application Server BPEL Runtime Compiled BPEL Scenario

31. Tooling Requirements  IDE – build your Web services  WSDL authoring – model your interfaces  Schema authoring – model your messages  Process modeling – model your orchestration  Packaging and deployment  Debugging  Monitoring  Analyzing

32. D E M O N S T R A T I O N Building a BPEL Scenario

33. What Happened to Java?  JSR 207 - Process Definition Language for Java  Make business processes natural for Java programmers MessagingTransactions Pooling Naming Security Application Server ServletEJB Process Definition for Java Based on JSR 207 Session at JavaOne 2003

34. What Happened to J2EE?  JSR 208 – Java Business Integration  Make business processes a first class citizen in J2EE containers Based on JSR 208 Session at JavaOne 2003... Routing Engine Transform Engine BPEL Engine Normalized Message Bus JSR 208 Binding SPI EDIJCA Web Services JMS... Binding Framework JSR 208 Machine SPI

35. Oracle’s Strategy  Oracle Application Server Containers for J2EE – BPEL runtime  Oracle JDeveloper – BPEL design time  Oracle Application Server Integration – Web service, B2B and EAI integration

36. Remember BPEL Does Not Solve “World Hunger”  No data transformation  No data translation (EDI, binary formats …)  No human workflow  No trading partner agreements  Silent on existing business protocols (ebXML, RosettaNet …)  Silent on non Web service interactions (e.g. java to java) ...

37. But Remember: People Are Trying to Solve “World Hunger”  W3C: WS-Choreography  Spec: WS-Transaction  Spec: WS-Coordination  Spec: WS-Composite Application Framework  OASIS: WS-Reliability  Spec: ReliableMessaging  Spec: WS-Addressing  OASIS: WS-Security  …

38. Parting Thoughts  Business process portability? – Java/J2EE is portable across application servers – BPEL is portable independent of Java  Programming language in XML? – Does this hurt? – Vendors, big and small, are busy building modellers…  Is BPEL in 2003/2004 J2EE in 1998? – Much missing but compelling foundation

39. Next Steps….  Recommended sessions – 36811 - Application Integration using Web Services – 40053 - Develop, Deploy, and Manage Web Services with Oracle Application Server 10 g  Recommended demos and/or hands-on labs – DemoGrounds: See the Web Services Booth – Hands On: Developing and Deploying Enterprise Web Services with Oracle Application Server 10 g  See Your Business in Our Software – Visit the DEMOgrounds for a customized architectural review, see a customized demo with Solutions Factory, or receive a personalized proposal. Visit the DEMOgrounds for more information.  Relevant web sites to visit for more information – http://otn.oracle.com/tech/webservices

40. Reminder – please complete the OracleWorld session survey Session Id : 40024 Thank you.

41. otn.oracle.com Join Over 3,000,000 Developers! Free Software Downloads http://otn.oracle.com Free Technical Advice

42.  Develop your career with Oracle’s experts – Web services, Forms Upgrade to the Web, TopLink, Business Intelligence, Integration, J2EE, Linux  Connect with your peers  Sign up at http://otn.oracle.com/events/otnworkshop FREE

43. A Q & Q U E S T I O N S A N S W E R S