Web Modeling-based Approach to Automating Web Services Mediation, Choreography and Discovery


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Web Modeling-based Approach to Automating Web Services Mediation, Choreography and Discovery

  1. 1. Web Modeling-based Approach to Automating Web Services Mediation, Choreography and Discovery SWS Challenge Stanford University, March, 8 2006 Marco Brambilla, Stefano Ceri, Dario Cerizza, Emanuele Della Valle, Federico Facca, Piero Fraternali, Christina Tziviskou
  2. 2. Summary <ul><li>Mediator modeling roadmap </li></ul><ul><ul><li>BPM modeling (choreography) </li></ul></ul><ul><ul><li>WebML Domain modeling (ontology) </li></ul></ul><ul><ul><li>WebML Navigation modeling as high-level conceptual description of mediators </li></ul></ul><ul><ul><li>Modeling of service invocation </li></ul></ul><ul><ul><li>Automatic generation of the mediator </li></ul></ul><ul><li>Demo </li></ul><ul><ul><li>Explanation </li></ul></ul><ul><ul><li>Demonstration </li></ul></ul><ul><li>Managing of dynamics: how to </li></ul><ul><li>Future vision </li></ul>
  3. 3. Mediator modeling roadmap WebML framework
  4. 4. Mediator modeling roadmap BPM modeling <ul><li>WebML integrated Business process modeling tool </li></ul><ul><li>Support of </li></ul><ul><li>BPMN standard notation </li></ul><ul><li>Automatic generation of the mediator WebML model based on business process patterns and standard description of activities </li></ul>
  5. 5. Mediator modeling roadmap WebML domain description modeling <ul><li>Ontological information described by extended E-R meta-model </li></ul>ShipmentService where ShipmentService.shipTo not in ShipmentService . locatedIn Self TO Europe where Self.locatedIn isa Europe
  6. 6. Feature of OWL-DL in webML domain description WebML structural + (C i ≠  ; A ≠ T) + (A, C i ≠  , T) - + - - + + ( C i ≠  ) + ( C i ≠  ) +  (must identify R and R - with the same name) - - - + (domain(R 2 ), range(R 2 ) ≠ T) + (domain(R 2 ), range(R 2 ) ≠ T) + + - - + - - rhs rhs - - rhs rhs rhs rhs rhs rhs
  7. 7. Mediator modeling roadmap WebML Hyper-text Navigation models <ul><li>WebML has a conceptual language for the specification and design of distributed Web applications based on SOA paradigm </li></ul><ul><ul><li>Content modeling </li></ul></ul><ul><ul><li>Operations, execution flow and data flow modeling </li></ul></ul>
  8. 8. <ul><li>Support of distributed hypertexts based on S ervice -O riented A rchitectures and Web Services </li></ul><ul><li>Web service publishing </li></ul>Mediator modeling roadmap WebML Service Navigation models
  9. 9. Mediator modeling roadmap From Business activity to Web Service <ul><li>Each activity in the business process model of the mediator is translated in a pattern of WebML Service Navigation model. Such pattern consists of 4 standard steps: </li></ul><ul><ul><li>Discovery  invocation of GLUE discovery engine </li></ul></ul><ul><ul><li>Lowering  data transformation from domain ontology to XML representation for WS message </li></ul></ul><ul><ul><li>Invocation  web service request response </li></ul></ul><ul><ul><li>Lifting  data transformation from XML message to domain ontology </li></ul></ul><ul><li>Further refinement may be applied by the designer </li></ul>
  10. 10. Mediator modeling roadmap Activity modeling in the hypertext <ul><li>Implementation for SWS Challenge Phase I: </li></ul><ul><ul><li>Discovery not needed </li></ul></ul><ul><ul><li>Some business actions follow the actual invocation: </li></ul></ul><ul><ul><ul><li>E.g., update of the state of the choreography </li></ul></ul></ul><ul><ul><li>Link topology may encapsulate programming logics </li></ul></ul>Lowering Lifting
  11. 11. Demo of the mediator <ul><li>Two interfaces </li></ul><ul><ul><li>one for machines </li></ul></ul><ul><ul><ul><li>A composed Web Service exposed to RosettaNet client for automatic enacting of the mediator process </li></ul></ul></ul><ul><ul><li>one for humans </li></ul></ul><ul><ul><ul><li>An hyper-textual application for manual inspection and execution of the process </li></ul></ul></ul>
  12. 12. Demo RosettaNet System PO service <ul><li>Receive PO </li></ul><ul><li>Obtain CustomerId </li></ul><ul><li>Create Order </li></ul><ul><li>Send Lines </li></ul><ul><li>Close Order </li></ul>
  13. 13. Demo Moon Line Confirmation service <ul><li>Receive Line Confirmations </li></ul><ul><li>Send POC </li></ul><ul><li>Demonstration </li></ul>
  14. 14. Managing dynamics.. How to <ul><li>Changes in the domain modeling </li></ul><ul><ul><li>Visual re-design of the ontology </li></ul></ul><ul><ul><li>Semi-automatic generation of the editing interfaces for the instances of the ontology </li></ul></ul><ul><li>Changes in the business process </li></ul><ul><ul><li>Visual re-design of the business process (choreography of the mediator) </li></ul></ul><ul><ul><li>Automatic generation of the mediator model (possibly preserving unchanged activities) </li></ul></ul><ul><li>Changes in the business partners </li></ul><ul><ul><li>Discovery of partners  Glue discovery engine </li></ul></ul>
  15. 15. Managing dynamics Addressing Challenge Phase II
  16. 16. Managing dynamics GLUE as discovery engine <ul><li>GLUE </li></ul><ul><ul><li>is a WSMO compliant discovery engine </li></ul></ul><ul><ul><ul><li>it aims at developing an efficient system for the manage- ment of Semantic Web Services and their discovery. </li></ul></ul></ul><ul><ul><li>adopts a mediator centric approach </li></ul></ul><ul><ul><ul><li>Provider and requester don’t have necessarily to agree on using the same set ontologies in describing their goals and Web Services, </li></ul></ul></ul><ul><ul><ul><li>But , they only have to agree in using compatible ontologies and in coding how to bypass heterogeneity using mediators: </li></ul></ul></ul><ul><ul><ul><ul><li>ggMediators are used for goal refinement </li></ul></ul></ul></ul><ul><ul><ul><ul><li>wgMediators are used for discovery </li></ul></ul></ul></ul>c 2 a c 5 c 1 c 2 c 3 c 4 a b b b c 2 REQUESTER PROVIDERS ggMediator (goal refinement) wgMediator (discovery) Class of WS C Class of Goals A Class of Goals B
  17. 17. Why Glue? <ul><li>SWS challenge scenario presents the kind of “polarization” in the point of view of requesters and providers that justifies the use of Glue </li></ul><ul><ul><li>different polarizations on different aspects </li></ul></ul><ul><ul><li>Different understanding of exact matching </li></ul></ul><ul><ul><ul><li>Products: […] a provider completely matches a request if all the requested category of products are available and it partially matches in case a subset is available. </li></ul></ul></ul><ul><ul><ul><li>Shipment Location: A service advertises the locations where it ships to. [ If the requester wish to send goods in Bristol and the supplier ships to Europe, then an exact matching exists .] </li></ul></ul></ul><ul><ul><ul><li>Shipment Price: [suppliers] might not always indicate a concrete price . </li></ul></ul></ul><ul><ul><ul><li>Payment Method: Both the requester and supplier advertise a list of acceptable payment methods. […] We have a complete match if one payment method exist in common for requester and supplier </li></ul></ul></ul><ul><ul><li>Standard matching mechanism (i.e. DL-based ) are not sufficient. </li></ul></ul><ul><ul><li>Pairs of ggMediators and wgMediators can be used to model these complex matching criteria </li></ul></ul>
  18. 18. Conclusions and future works <ul><li>The described methodology </li></ul><ul><ul><li>BPM models the choreography </li></ul></ul><ul><ul><li>BPM case tool generates the WebML model of the mediator </li></ul></ul><ul><ul><ul><li>Both as a fully automatic mediator </li></ul></ul></ul><ul><ul><ul><li>And as an hyper-textual application for manual inspection and execution of the process </li></ul></ul></ul><ul><ul><li>WebML case tool enables the designer to refine the model </li></ul></ul><ul><ul><ul><li>Defines ontologies, lowering and lifting, goal, web services ggMediators, wgMediators, business logic, etc. </li></ul></ul></ul><ul><ul><li>WebML case tools automatically generates the code </li></ul></ul><ul><li>Vision and future work </li></ul><ul><ul><li>Convergence of WebML – WSMO </li></ul></ul><ul><ul><ul><li>Integration of GLUE </li></ul></ul></ul><ul><ul><ul><li>definition of WSMO goals at the BPM level (one goal for each activity) </li></ul></ul></ul>
  19. 19. <ul><li>Thank you very much for your attention </li></ul><ul><li>Any question? </li></ul>Emanuele Della Valle CEFRIEL [email_address] Marco Brambilla Politecnico di Milano [email_address] Federico M. Facca Politecnico di Milano [email_address]