1 / 12

BPEL and XPDL

BPEL and XPDL. Park, Nam Joon ISILab. Introduction. Feedback based framework for semi-automatic composition of Web services – needs short name! uses information of previous processes defined to help the composition of Web services

harvey
Download Presentation

BPEL and XPDL

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. BPEL and XPDL Park, Nam Joon ISILab

  2. Introduction • Feedback based framework for semi-automatic composition of Web services – needs short name! • uses information of previous processes defined to help the composition of Web services • extract data access pattern and connection pattern between Web services

  3. BPEL and XPDL • BPEL(Business Process Execution Language) • execution language • has variables and operations • makes it easy to use several Web services at the same time • doesn’t support the graphics of diagram • XPDL(XML Processing Description Language) • a process design format • represents the drawing of the process definition • has X&Y coordination and node size

  4. BPEL and XPDL • Goal • BPEL • provide the definitions of • Web services orchestration • underlying sequences of interactions • the flow of data from point to point • XPDL • store and exchange the process diagram • provides the way to exchange the diagram between process modeling tools

  5. BPEL and XPDL • Goal • In design level, XPDL is used for exchange the diagram between tools • In execution environment, engine uses its own format

  6. BPEL and XPDL • Paradigm • BPEL(Business Process Execution Language) • block structured programming language • declaration and definition is possible only at top-level • it is impossible to define the flow out-of-block • XPDL(XML Processing Description Language) • graph structured language • activity-node, transition-edge • flow is defined as transitions between activities • conditions related transitions define which activities will be executed at next time • Translation from BPEL to XPDL is more difficult • For the translation, we need some constraints for well-structured graph • X&Y coordination, node size, arrow

  7. BPEL and XPDL • Market trend • BPEL is though as the best BPM standard • suggested IBM, MS, BEA • The specification will be extend, so BPEL will be supported by more vendors

  8. BPEL and XPDL • Oracle BPEL Manager

  9. XPDL and BPEL • WebVine

  10. BPEL and XPDL • Implementation our framework • BPEL • difficult to extract data access pattern int a = 0; functionA(a); a = 455; functionB(a); • XPDL • difficult to deal with Web services

  11. How about WebVine? • Implementation • Java, Eclipse • XPDL • Issues • Web services support • Processes implemented in XPDL • Extracting information

  12. Conclusion • We have look over BPEL and XPDL for choosing appropriate language for implementing our framework • BPEL has advantages in dealing Web services and market power, but it is difficult to implement our framework • We have very nice platform, WebVine, so I’ll implement our framework based on WebVine • If we can extends WebVine to support BPEL, it would be more powerful tool

More Related