Web Services and the Service-Oriented Architecture

955 views

Published on

PowerPoint presentation on Web Services and the Service-Oriented Architecture from Library Technology Reports

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
955
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
64
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Web Services and the Service-Oriented Architecture

  1. 1. Web Services and the Service-Oriented Architecture<br />November 5, 2009<br />Ruben Balderas<br />Jill Baron<br />Jessica Ng<br />Jing Yang<br />
  2. 2. Basic Concepts <br />Service-Oriented Architecture<br />SOA is an organizing principle for an organization&apos;s technical infrastructure to support the needs of the organization&apos;s software users. <br />Web services are the dominant approach for implementing SOA.<br />
  3. 3. Web Services Are Not<br /> Web interfaces<br /> Web-based information resources<br /> Web-based “services”<br /> Software as service<br /> Application service provider<br /> Web Service Librarian<br />
  4. 4. Web Services<br />Definition<br />A Web service is a software system designed to support interoperable machine-to-machine interaction over a network. <br />It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.<br />(World Wide Web Consortium)<br />
  5. 5. Example: Amazon Web Services<br />
  6. 6. Amazon E-Commerce Service<br />
  7. 7. Communication Path for Web Services<br />
  8. 8. Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)
  9. 9. Simple Object Access Protocol (SOAP)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)
  10. 10. Simple Object Access Protocol (SOAP)
  11. 11. Web Services Description Language (WSDL)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)
  12. 12. Simple Object Access Protocol (SOAP)
  13. 13. Web Services Description Language (WSDL)
  14. 14. Universal Description, Discovery and Integration (UDDI)</li></li></ul><li>Open Source Protocol Substitutes<br />Representational State Transfer (REST)<br /> - Substitute for SOAP<br />-Response as an XML Stream<br /> Easier and faster to implement<br /> Better Performance and response time<br /><ul><li>Really Simple Syndication (RSS)</li></li></ul><li>
  15. 15.
  16. 16.
  17. 17.
  18. 18.
  19. 19. Web Services in the Library Environment<br />The VIEWS Initiative<br />Vendor Initiative for Enabling Web Services (VIEWS).<br />A consortium of vendors formed to facilitate the development of interoperable Web services related to library applications.<br />Goal: Provide a forum in which library-automation vendors could establish a set of Web services that can be used in library applications.<br />
  20. 20. Mission: <br /><ul><li>Developing best practices for designing and deploying web services
  21. 21. Produce and maintain a “Web Services Best Practices” document for general use in assessing new and ongoing Web-service applications
  22. 22. Provide and maintain “Web Services Interoperability Mechanisms</li></li></ul><li>Non-Web-Service Library Standards and Protocols<br />Z39.50<br />ISO 10160/10161 and ISO ILL<br />UN/EDIFACT and ANSI x12<br />MARC 21 Format<br />Dublin Core<br />OpenURL<br />
  23. 23. MARC 21 Format<br />
  24. 24. Marc 21 Format<br />
  25. 25. OpenURL<br />
  26. 26. Open URL<br />
  27. 27. Library Protocols based on Web Services<br />Z39.50 International: Next Generation (ZING)<br />Established to take the concepts and functionality embodied in Z39.50 forward.<br />Development of a version of Z39.50 in the framework of Web services – search-and-retrieval protocol.<br />SRU: Search/Retrieve via URL<br />SRW: Search/Retrieve Web Service<br />
  28. 28. SRU and SRW supports three operations:<br />SearchRetrieve<br />Scan<br />Explain<br />
  29. 29. The Cheshire Project<br />
  30. 30. The Cheshire Project<br />
  31. 31. The Cheshire Project<br />
  32. 32. Open Archives Initiative Protocol for Metadata Harvesting<br />Supports federated-search model<br />Harvesting metadata from multiple information repositories<br />Create centralized search services<br />Provides alternative to those based on simultaneous queries.<br />Relies on data providers and service providers. <br />Web harvesting: Provides means to harvest new and changed pages.<br />
  33. 33.
  34. 34. When we think of architecture we think of<br />
  35. 35. or<br />
  36. 36. “Service-oriented” architecture might be more like<br />
  37. 37. INTEROPERABILITY <br />or,<br />many moving parts<br />
  38. 38. Why this matters<br />
  39. 39. Services make life easier<br />
  40. 40. We want to do things here:<br />
  41. 41. Research<br />
  42. 42. Architectural Repository, aka SOA<br />
  43. 43.
  44. 44.
  45. 45.
  46. 46.
  47. 47.
  48. 48.
  49. 49.
  50. 50. SOA allows the library or archive:<br />Manage materials effectively<br />Build on resources<br />Greater collaboration with other organizations and businesses<br />Provide services within campus or municipal portal environments or other non-traditional channels<br />Enhance research experience<br />
  51. 51. SOA allows the user:<br />Ease of access<br />Multimedia resources<br />More resources = a more global understanding of a subject<br />Opportunity to consider relationships between items<br />More fun<br />
  52. 52. Questions?<br />Comments?<br />

×