1 / 148

Outline

Outline. Workflows Service registries Adaptive services Matching and adaptation Interface Behavior Context-awareness QoS agreement Adaptation/Repair actions Architectural repair Process adaptation Service matching QoS optimization and agreement. Service Requestor. SOAP. WSDL.

yauvani
Download Presentation

Outline

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. Outline • Workflows • Service registries • Adaptive services • Matching and adaptation • Interface • Behavior • Context-awareness • QoS agreement • Adaptation/Repair actions • Architectural repair • Process adaptation • Service matching • QoS optimization and agreement

  2. Service Requestor SOAP WSDL UDDI ...SOA and Web Services

  3. Towards managed WS Papazoglou, CACM Oct. 2003

  4. Workflows • Focus on differences • Scheduling • Control • Human resources

  5. Workflow Classification (C) Leymann 2001

  6. WFMS

  7. Product Implementation Model

  8. Grid and Workflows • Managing resources

  9. A Taxonomy of Workflow Management Systems for Grid Computing Jia Yu and Rajkumar Buyya1

  10. A Taxonomy of Workflow Management Systems for Grid Computing Jia Yu and Rajkumar Buyya1

  11. Service Adaptation Traverso 2006

  12. S1.op1 Flexible e-services Adaptive networks S1.op2 S2.op1 Context-awareness and personalization S2.op2 Adaptive front-ends S1.op3 Dynamic service selection and optimization Service registry S2.op3 MAIS-Platform Scenario (MAIS-P) • MAIS http://www.mais-project.it • Multichannel Adaptive Information Systems – FIRB Project 2002-2006

  13. Micro-MAIS scenario Mobile camp Operation teams Sets up and coordinates teams Collect field information Traditional information system Central site • MAIS http://www.mais-project.it • Multichannel Adaptive Information Systems – FIRB Project 2002-2006

  14. Service Adaptation Traverso 2006

  15. Adaptive services: approaches • Matching and adaptation • Interface • Behavior • Context-awareness • QoS agreement • Repair actions • Architectural repair

  16. Matching and adaptation • Goals • Dynamic services selection (and composition) • Substitution / rebinding • UDDI • Interface • Behavior • Context-awareness

  17. UDDI

  18. Repositories e registries • systems storing and managing • e-Service specifications • e-service providers • UDDI Universal Description, Discovery & Integration

  19. How UDDI Works 3. 1. SW companies, standards bodies, and programmers populate the registry with descriptions of different types of services Marketplaces, search engines, and business apps query the registry to discover services at other companies 2. 4. Businesses populate the registry with descriptions of the services they support Business uses this data to facilitate easier integration with each other over the Web Service Type Registrations BusinessRegistrations UDDI

  20. Registry Data WhitePages Who am I? • Businesses register public informationabout themselves YellowPages What do I offer? GreenPages How to dobusiness with me • Standards bodies, Programmers, Businesses register information about their Service Types(„tModels“) Service Type Registrations

  21. UDDI • OASIS standard (v. 3) • Formerly a joint proposal of (IBM, SAP, BEA, ...) • UDDI Service discovery is driven by: • Keyword-based query • Pre-defined taxonomies browsing • UNSPSC • ISO 3166 • NTIS - NAICS • UDDI supports publication of generic services, not necessarily Web services

  22. The UDDI acronym • Universal Description: UDDI does not rely on a specific approach for describe a service (WSDL is only one of them) • Universal Discovery: service retrieval can be performed in several ways • white pages: by service provider • yellow pages: by service classification • green pages: by service type • Universal Integration: services are described regardless of the underlying technologies

  23. How to extend • Interface matching • Stroulia and Yang, Woogle (WSDL) • Semantic matching • OWL-S MM, WSMO MM • Hybrid matching • Lumina (SAWSDL) • Quality driven matching • WSOI (WSOL), UDDIe (Proprietary Language) • Hybrid+Quality matching • URBE (WSDL, SAWSDL, WS-Policy) • What about behavior?

  24. Matching and adaptation • Interface • Behavior • Context-awareness • QoS

  25. Interface matching: Stroulia and Yang • Two main aspects • structural similarity based only on data type analysis (casting) • semantic similarity based on operations and parameters names • This approach also considers the documentation field • relies on IR approach (tf/idf) • Term similarity evaluation is based on Wordnet

  26. Interface matching: Woogle • Proposed by Dong et al. at VLDB 2004 • now it seems to be abandoned • Operation-based query • Based on parameter names clustering • parameters tend to express the same concept if they occur together often • Operation matching is based on the defined clusters • Tool available on linehttp://data.cs.washington.edu/webService/

  27. Semantic approaches: the roadmap Modeling query and description with logics. Unfeasible as a general purpose solution Describe services as interlinked subactivities Easy to describe and general purpose Attribute-values pair e.g., UDDI Based on ad-hoc ontology classifying documents Google Style from E. Klein, A. Bernstein, Toward High-Precision Service Retrieval, IEEE Internet Computing, Jan-Feb 2004

  28. X Semantic Matchmaking = G = WS Exact Match: G, WS, O, M ╞ x. (G(x) <=> WS(x) ) PlugIn Match: G, WS, O, M ╞ x. (G(x) => WS(x) ) Subsumption Match: G, WS, O, M ╞ x. (G(x) <= WS(x) ) Intersection Match: G, WS, O, M ╞ x. (G(x) WS(x) ) Non Match: G, WS, O, M ╞ ¬x. (G(x) WS(x) ) Keller, U.; Lara, R.; Polleres, A. (Eds): WSMO Web Service Discovery. WSML Working Draft D5.1, 12 Nov 2004.

  29. OWL-S: the upper ontology • Languages for specifying Web service ontology • Based on OWL (formerly DAML) All the images about OWL-S are from OWL-S Web site (http://www.ai.sri.com)

  30. OWL-S: Service Profile (v.1.1)

  31. OWL-S Matchmaking • Reasons on the OWL-S Ontology • Proposes three kinds of similarity: • exatch • plug-in • subsumes • The related paper introduces a new aspect: reputation!

  32. WSMO • WSMO provides ontological specifications for the core elements of Semantic Web services: • Web services, Goal, Mediator, Ontology • We are mainly focused on the Web service definition

  33. WSMO Matchmaker • Needs to consider both goals and capabilities • Kaufer & Klusch proposes a matchmaker • extracts relevant information from description (derivative) • works on that information

  34. Hybrid approaches • Considers both interfaces and semantics • Usually based on annotations • SAWSDL extends WSDL with annotations offering semantic description about operations, messages, parameters • Good balance between: • expressiveness • feasibility • What about the matchmaker?

  35. SAWSDL

  36. URBE (Uddi Registry By Example) (Plebani, Pernici, 2007) Plebani’s PhD thesis

  37. Main features • Interface matching • Semantic matching • The main goal is: retrieval for substitutability

  38. URBE • Uddi Registry By Example • is compliant with UDDI (publishing, searching, data models) • performs content based query based • user submits a WSDL expressing the requirements • URBE returns a list of Web services close to the request • Similarity function fSim is the core of URBE • structural analysis • semantic analysis

  39. Similarity Function fSim • Semantic analysis • portType names • operation names • parameter names • Structural analysis • data types • number of inputs • number of outputs • number of operations

  40. 1.0 0.3 0.2 0.8 0.5 1.0 0.7 0.2 0.7 Adopted linear problem WS Q WS P Q.1 Q.2 Q.3 P.1 P.2 P.3 opt(sim(Q, P)) = 1.0 + 0.7+ 1.0 = 2.7

  41. Names similarity automobile car money currency • Quantifies how much two names are related • We need that to compare service, operation, and parameter names • Stemming and tokenization are required before comparing names • We assume that the WSDL is automatically generated

  42. Structural analysis • Mainly related to the data types analysis • Also considers how many operations (messages, parameters) are required w.r.t. the ones offered

  43. Exploting the annotations • Recall can be improved if SAWSDL description is available • In this case name similarity is based on the annotations

  44. Service adaptation FlightService WSDL Similarity Evaluation Mapping information Alitalia WSDL Similarity Engine

  45. Mediation engine • Based on mapping tables (built semiautomatically) • Similarity of parameters and operations • Thesaurus (terms, simple semantic annotations) • Reference services • Transformation of parameters structure and names • Restructuring • String concatenation • Designer support to extract semantics derived from user interface (web page) • Structural analysis of page • Thesaurus • Research towards wrapper and mediation engines Enrico Mussi PhD Thesis, Politecnico di Milano, 2007

  46. Web Service Substitution:Mediator execution Mapping information Input message (Warehouse 1 WSDL) Input message (Warehouse 2 WSDL) Mediation Service Translation Engine Output message (Warehouse 1 WSDL) Output message (Warehouse 2 WSDL) External Data Retriever

  47. Behavior compatibility

More Related