1 / 5

Don’t go with the flow Web services composition standards exposed By, W.M.P. van der Aalst

Don’t go with the flow Web services composition standards exposed By, W.M.P. van der Aalst (Dept. of Technology, Eindhoven University of Technology). Requirement of web services composition languages:.

buzz
Download Presentation

Don’t go with the flow Web services composition standards exposed By, W.M.P. van der Aalst

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. Don’t go with the flow Web services composition standards exposed By, W.M.P. van der Aalst (Dept. of Technology, Eindhoven University of Technology) • Requirement of web services composition languages: • Not sufficient to merely support simple interaction using standard messages and protocols. • Business interactions require long running interactions that are driven by an explicit process model. • This raises the need for web services composition languages such as BPEL4WS, WSFL, XLANG etc.

  2. Problem of Many • Many companies have been coming out with their own standards. • Having standards is good but many of them die even before becoming mature. • They have no clear defined semantics. • BPES tries to mix features of XLANG from Microsoft and WSFL from IBM but this is done at the price of increasing complexity. • The only solution: Critical evaluation of these so-called standards for web services composition.

  3. Overview of Standards • XLANG: • A block structured language with basic control flow structures such as sequence, switch, while etc. • Completely based on the current middleware solution of Microsoft so cannot exactly be called a standard. • WSFL: • Not limited to block structures, allows for directed graphs. Control flow part of WSFL is almost identical to IBM’s MQ Series Workflows. • Very different from other languages, imprecise and complex for use with web services. • Other Standards: • Other vendors: Sun, BEA, SAP, Intalio introduced WSCI. • Business Process Management Initiative developed BPML • OASIS and UN/CEFACT support ebXML.

  4. Comparing supported workflow patterns • BPEL4WS is combination of XLANG and WSFL when it comes to comparing patterns. • WSFL and MQ Series Workflow have identical process specification. • XPDL is less expressive than BPEL4WS. • WSFL, XPDL, Staffware, MQ Series and eProcess are graph based. • While, only XLANG and FLOWer are block structured.

  5. Conclusion • Not possible to originate standard by companies pushing their own products. • The software industry has been ignoring available well established process modelling techniques. • Too many standards which are mainly driven by concrete products and commercial interests. • Solution: Ignore standardization proposals that are not using well-established process modelling techniques.

More Related