1 / 15

Web Service Composition workflow patterns in BPEL4WS

Web Service Composition workflow patterns in BPEL4WS. http://tmitwww.tm.tue.nl/research/patterns/download/wfs-pat-2002.pdf http://tmitwww.tm.tue.nl/research/patterns/download/bpel_er.pdf http://www.big.tuwien.ac.at/research/publications/2003/0603.pdf. Eyal Oren DERI 2004/06/02. Overview.

sage
Download Presentation

Web Service Composition workflow patterns in BPEL4WS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Service Compositionworkflow patterns in BPEL4WS http://tmitwww.tm.tue.nl/research/patterns/download/wfs-pat-2002.pdfhttp://tmitwww.tm.tue.nl/research/patterns/download/bpel_er.pdfhttp://www.big.tuwien.ac.at/research/publications/2003/0603.pdf Eyal Oren DERI 2004/06/02

  2. Overview • Goal • Workflow Patterns • Supported by BPEL4WS • YAWL: Yet Another Workflow Language • Relevance to WSMO

  3. Goal • To analyse web service composition languages, specifically BPEL4WS • Focus on control flow • Learn from workflow management research • “industry ignores established formal process modeling techniques: ignore the industry”

  4. Bernauer et. al. – Comparison Framework • comparing interorganizational workflow • different than intra-organizational workflow: • interoperability • autonomy (of participating organizations) • trust, privacy and security • requirements: • re-usable workflow types (private/public, roles) • profile specifications (organization, role, technology) • implementation details (executable specification)

  5. Workflow patterns • workflow: • process (control flow) • information (data) • organization (resource) • operation (implementation) • integration • gathered control-flow patterns(www.workflowpatterns.com) • it’s not expressivity, almost all Turing completeit’s about suitability, direct support • how good (necessary) are the patterns?

  6. Patterns • often-used patterns but often no direct support: providing solutions in ‘simpler’ language • can also be used to analyse language usability (you would like direct support) not 8,9 not 10 not 18 not 14,15

  7. Basic Patterns

  8. Advanced Patterns A1 = audit_applicationA2 = process_applicationC = close_case paper accepted if both reviews positive, author notifiedif first=negative, notify author immediately paper accepted if all 2 out of 3 positive, author notifiedif 2=negative, notify author immediately

  9. Structural Patterns

  10. State-based Patterns

  11. BPEL Summary • BPEL supports a lot of patterns(compared to languages considered) • positive: • expressive • negative: • should be simplified (WSFL, XLANG overlap) • should be formalized

  12. YAWL • Petri nets for workflow modeling: • formal semantics, yet graphical • state-based (not just event-based) • analysis techniques • Problems: • (keeping track of) multiple instances • advanced synchronization patterns (either AND or XOR, depending on context) • cancellation pattern (vacuum cleaner) • you can model everything, it just becomes unreadable and unmaintainable

  13. YAWL • Petri-net based language • Directly supports all patterns • Formal semantics • Control flow, data flow, operational perspective • Supports web services • Prototype software • Future: • transactions, communication patterns • analysis techniques/tools

  14. YAWL Examples multi-merge milestone

  15. Relevance to WSMO • Orchestration is (or needs) a way to describe composite processes • Orchestration shouldn’t re-invent the wheel • Orchestration should (partly) support patterns • Orchestration should use either • BPEL • YAWL

More Related