1 / 8

Reusable Web Services – A notation modeling dynamic service composition

Reusable Web Services – A notation modeling dynamic service composition. Peter Henderson and Jingtao Yang School of Electronics and Computer Science University of Southampton SO17 1UB, UK. Background . Objective An architecture to design web service based E-Commerce

kiele
Download Presentation

Reusable Web Services – A notation modeling dynamic service composition

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. Reusable Web Services – A notation modeling dynamic service composition Peter Henderson and Jingtao Yang School of Electronics and Computer Science University of Southampton SO17 1UB, UK

  2. Background • Objective • An architecture to design web service based E-Commerce • Asynchronous interactions • Dynamic reconfiguration • Service reuse • Web Services • An autonomous entity • WSDL interfaces • Accessible through standardized XML messaging • Web Services orchestrated to deliver business processes

  3. Web Services Orchestration • A travel agent system • Composed by distributed services • Flight shop, hotel shop, car shop • Travel agent • System requirement • Concurrent • Transaction states handling • Reuse or replace a service • Dynamic configuration

  4. Document Flow Model • DFN • OnMessage [to:a. from:u, query:q, context:c] • generate new uid • store uid -> [from:u, query:q, context:c] in CS • send [to:s1, from:a, query:q1, context:uid] • send [to:s2, from:a, query:q2, context:uid] • OnMessage [to:si, from:a, query:qi, context:uid] • send [to:a, from:si, reply:[query:qi, result:ri], context:uid] • OnMessage [to:a, from:si, reply:[query:qi, result:ri], context:uid] • store uid -> [query:qi, result:ri] in CS • if CS[uid] contains[from:u,query:q,context:c], • [query:q1, result:r1], and [query:q2, result:r2] • then • send [to:u,from:a,reply:[query:q,result:[r1,r2]],context:c]

  5. DFM - Summary • Document Flow Model (Notation) • XML oriented • Flexible data structure • Web-service flow model • Modeling concurrent transactions

  6. Future Works • More Features in DFM • Compensation • … • Model Checking • Model checkers • Tool Generation

  7. Conclusion • DFM - A design notation modeling dynamic service composition based on stateless services and stateful messages.

  8. Q/A? • Prof Peter Henderson • p.henderson@ecs.soton.ac.uk • Jingtao Yang • j.yang@ecs.soton.ac.uk

More Related