Web Services and the Service-Oriented Architecture<br />November 5, 2009<br />Jessica Ng<br />Jing Yang<br />Jill Baron<br...
Basic Concepts <br />Service-Oriented Architecture<br />SOA is an organizing principle for an organization&apos;s technica...
Web Services Are Not<br />		Web interfaces<br />		Web-based information resources<br />		Web-based “services”<br />		Softw...
Web Services<br />Definition<br />A Web service is a software system designed to support interoperable machine-to-machine ...
Communication Path for Web Services<br />
Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)</li></li></ul><li>Web-Service Component...
 Simple Object Access Protocol (SOAP)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible Marku...
 Simple Object Access Protocol (SOAP)
 Web Services Description Language (WSDL)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible M...
 Simple Object Access Protocol (SOAP)
 Web Services Description Language (WSDL)
 Universal Description, Discovery and Integration (UDDI)</li></li></ul><li>Open Source Protocol Substitutes<br />Represent...
Second-Generation Specifications<br />WS-Security<br />
Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />
Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />
Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />...
Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />...
Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />...
Web Services in the Library Environment<br />The VIEWS Initiative<br /><ul><li>Vendor Initiative for Enabling Web Services...
A consortium of vendors formed to facilitate the development of interoperable Web services related to library applications.
Goal: Provide a forum in which library-automation vendors could establish a set of Web services that can be used in librar...
Specific implementation of Web services.</li></li></ul><li>Controversy<br />Originally not a National Information Standard...
Mission: <br /><ul><li>Developing best practices for designing and deploying web services
Produce and maintain  a “Web Services Best Practices” document for general use in assessing new and ongoing Web-service ap...
Provide and maintain “Web Services Interoperability Mechanisms</li></li></ul><li>Non-Web-Service Library Standards and Pro...
ISO 10160/10161 and ISO ILL<br /><ul><li>Provides set of standard protocols for the interoperable exchange of ILL transact...
Open Systems Interconnect style of communication based on ASN.1 and BER
Maintained by the Library and Archives Canada</li></ul>UN/EDIFACT and ANSI x12<br /><ul><li>Electronic Data Interchange (E...
International standard employed across many industries
Used between libraries and suppliers </li></ul>Electronic ordering<br />Making claims for items expected and received<br /...
MARC 21 Format<br />Most widely accepted adapted library standard<br />Formats store bibliographic records in a compact fo...
Dublin Core<br />Metadata format expressed in XML.<br />Provides simplified approach for describing information objects.<b...
Library Protocols based on Web Services<br />Z39.50 International: Next Generation (ZING)<br />Established to take the con...
SRU and SRW supports three operations:<br />SearchRetrieve<br />Scan<br />Explain<br />Implementation of SRU and SRW<br />...
Open Archives Initiative Protocol for Metadata Harvesting<br />Supports federated-search model<br />Harvesting metadata fr...
Standardized Usage Statistics Harvesting Initiative (SUSHI)<br />Deals with issue of transferring statistics that assess a...
When we think of architecture we think of<br />
or<br />
“Service-oriented” architecture might be more like<br />
INTEROPERABILITY <br />or,<br />many moving parts<br />
Why this matters<br />
Services make life easier<br />
We want to do things here:<br />
Research<br />
Architectural Repository, aka SOA<br />
Upcoming SlideShare
Loading in …5
×

Ltr Presentaion 2

427 views
361 views

Published on

Web Services and Service-Oriented Architecture

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

  • Be the first to like this

No Downloads
Views
Total views
427
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Ltr Presentaion 2

  1. 1. Web Services and the Service-Oriented Architecture<br />November 5, 2009<br />Jessica Ng<br />Jing Yang<br />Jill Baron<br />Ruben Balderas<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. Communication Path for Web Services<br />
  6. 6. 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)
  7. 7. Simple Object Access Protocol (SOAP)</li></li></ul><li>Web-Service Components and Protocols<br /><ul><li>eXtensible Markup Language (XML)
  8. 8. Simple Object Access Protocol (SOAP)
  9. 9. Web Services Description Language (WSDL)</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)
  12. 12. 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>
  13. 13. Second-Generation Specifications<br />WS-Security<br />
  14. 14. Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />
  15. 15. Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />
  16. 16. Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />WS-Reliable Messaging<br />
  17. 17. Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />WS-Reliable Messaging<br />WS-Attachments<br />
  18. 18. Second-Generation Specifications<br />WS-Security<br />WS-AtomicTransaction/WS-BusinessActivity<br />WS-Coordination<br />WS-Reliable Messaging<br />WS-Attachments<br />Business Process Execution Language for Web Services (BPEL4WS)<br />
  19. 19.
  20. 20.
  21. 21.
  22. 22. Web Services in the Library Environment<br />The VIEWS Initiative<br /><ul><li>Vendor Initiative for Enabling Web Services (VIEWS).
  23. 23. A consortium of vendors formed to facilitate the development of interoperable Web services related to library applications.
  24. 24. Goal: Provide a forum in which library-automation vendors could establish a set of Web services that can be used in library applications.
  25. 25. Specific implementation of Web services.</li></li></ul><li>Controversy<br />Originally not a National Information Standards Organization (NISO) sponsored group.<br />Not all vendors chose to participate<br />Much of the work intertwined with NISO’s initiatives.<br />Replaced by NISO Web Services and Practices Working Group in August 2005.<br />
  26. 26. Mission: <br /><ul><li>Developing best practices for designing and deploying web services
  27. 27. Produce and maintain a “Web Services Best Practices” document for general use in assessing new and ongoing Web-service applications
  28. 28. Provide and maintain “Web Services Interoperability Mechanisms</li></li></ul><li>Non-Web-Service Library Standards and Protocols<br />Z39.50<br />Search-and-retrieval protocol<br />Performs search operations and returns results in MARC cimmunications format.<br />Based on Abstract Syntax Notation (ASN.1) and Basic Encoding Rules (BER),<br />Maintained by the Library of Congress.<br />
  29. 29. ISO 10160/10161 and ISO ILL<br /><ul><li>Provides set of standard protocols for the interoperable exchange of ILL transactions.
  30. 30. Open Systems Interconnect style of communication based on ASN.1 and BER
  31. 31. Maintained by the Library and Archives Canada</li></ul>UN/EDIFACT and ANSI x12<br /><ul><li>Electronic Data Interchange (EDI) standards intended for the exchange of messages related to business transactions
  32. 32. International standard employed across many industries
  33. 33. Used between libraries and suppliers </li></ul>Electronic ordering<br />Making claims for items expected and received<br />Transfer of invoices<br />
  34. 34. MARC 21 Format<br />Most widely accepted adapted library standard<br />Formats store bibliographic records in a compact format. <br />MARCXML – Provides XML Structure for MARC 21 data.<br />Metadata Object Description Standard (MODS)<br />XML schema for MARC 21 bibliographic records<br />Metadata Authority Description Schema (MADS)<br />XML schema for selected tags of the MARC 21 authority format.<br />Encoded Archival Description (EAD)<br />Standard for creating finding aids of archival collections in XML.<br />
  35. 35. Dublin Core<br />Metadata format expressed in XML.<br />Provides simplified approach for describing information objects.<br />Widely used as a metadata format describing electronic resources or other application in which MARC format is not needed.<br />OpenURL<br />Provides a mechanism for linking to resources independently of their physical locations.<br />
  36. 36. 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 />
  37. 37. SRU and SRW supports three operations:<br />SearchRetrieve<br />Scan<br />Explain<br />Implementation of SRU and SRW<br />OCLC Research<br />Index Data<br />The Cheshire Project<br />
  38. 38. 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 />
  39. 39. Standardized Usage Statistics Harvesting Initiative (SUSHI)<br />Deals with issue of transferring statistics that assess an institution’s use of an electronic resource that the library subscribes to.<br />Project COUNTER<br />Initiative to develop set of standard practices regarding how publishes will produce use statistics related to library subscriptions.<br />
  40. 40.
  41. 41. When we think of architecture we think of<br />
  42. 42. or<br />
  43. 43. “Service-oriented” architecture might be more like<br />
  44. 44. INTEROPERABILITY <br />or,<br />many moving parts<br />
  45. 45. Why this matters<br />
  46. 46. Services make life easier<br />
  47. 47. We want to do things here:<br />
  48. 48. Research<br />
  49. 49. Architectural Repository, aka SOA<br />
  50. 50.
  51. 51.
  52. 52.
  53. 53.
  54. 54.
  55. 55.
  56. 56. 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 />
  57. 57. 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 />

×