composite services n.
Skip this Video
Loading SlideShow in 5 Seconds..
Composite Services PowerPoint Presentation
Download Presentation
Composite Services

Composite Services

0 Vues Download Presentation
Télécharger la présentation

Composite Services

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Composite Services Gustavo Alonso Swiss Federal Institute of Technology (ETHZ) Zürich, Switzerland

  2. Outline • Our vision and grand goals • State of the art and influence on ADAPT • Progress so far • Work on year two

  3. Our vision Automating the integration of IT infrastructures through Web service composition, business protocols, and conversation specifications Service specification Automated validation of the composition Enactment Automatic extraction of service data Automated support for composition

  4. Our grand goals • Through automation and leveraging Web services we hope to: • reduce the development cost of B2B applications • make Web service technology available to SMEs • create the basics for plug&play Web service technology • complement standardization in areas that are currently not being well covered by industry efforts • hide the complexity and changing nature of Web service technology from the end user • contribute to standardization efforts in composite services • open source platform

  5. State of the art • Many important developments in the last year: • BPEL specification • BPEL implementations (Collaxa, BPELWS4j) • Many additional specifications relevant to composition (WS-CAF, WSIF, WS-Coordination, WS-Transactions, Grid, etc.) • Many changes and not a clear direction • Competing standards without a clear winner (ebXML, xCBL) • Luckily, this situation does not negatively influence our plans within ADAPT (so far, we will keep a close watch) • our goals still beyond the scope of industry efforts • we profit from all the tools that have become available

  6. CONCEPTUAL DESIGN Use of Web service specifications is ill defined and changing The range of design options is widening and may require us to focus on a particular application type The focus is also shifting in industry (from simple services to conversations) ACTUAL ARCHITECTURE Increasing number of tools available (to enhance the work on ADAPT, or to give us a link to products) May have to postpone some design decisions until a later stage than planned Otherwise, the initial goals of the ADAPT platform for composition remain unchanged Influences on ADAPT

  7. Progress so far • Two prototype composition engines (based on previous work) capable of automatically importing information about Web services (WSDL description), embedding the operations within a workflow process, and invoking the services using SOAP • Centralized engine (Java) • Distributed engine (Java) • Bottom up composition • Graphical tool for composition • Consensus formed on model behind composition (Pi calculus) and properties of composition that we will support (transactions, choreography).

  8. Evaluation of progress so far • All the background work has been done: • thorough understanding of available technology • flexible design to keep our options open (centralized, distributed, bottom up composition, top down composition, conversation based composition, etc.) • Existing prototypes provide excellent platform for experimentation and exploring interaction of heterogeneous systems • Consensus emerging on what are the limits to what we can do in ADAPT, what we can take from others (e.g., TAPAS), and where the strength of the open source platform will be

  9. Planned work for year two • Consolidation of the prototypes • possible decision to go with only one engine (not necessary) • Closer look at top down composition (as an extension or alternative) • Tying together of graphical tool, engines and composition model in a single unified framework • careful attention to standards (BPEL) • Work on adaptive composition and automated analysis • transactions • choreography and business protocols • First version of the ADAPT platform


  11. JOpera Architecture

  12. JOpera Distributed Kernel

  13. JOpera Storage Architecture

  14. Cost of persistent storage

  15. Process instantiation time

  16. Throughput degradation

  17. Scalability (Response time)

  18. Scalability (throughput)

  19. Split/Merge Options

  20. Reliable WS Call Static Dynamic

  21. Visual XML Transformation

  22. WS Demo Process This process is included as an example of WS composition with the current JOpera release