Web Services and Service-Oriented Architecture

1. Web Services and the Service-Oriented Architecture November 5, 2009 Jessica Ng Jing Yang Jill Baron Ruben Balderas

2. Basic Concepts Service-Oriented Architecture SOA is an organizing principle for an organization's technical infrastructure to support the needs of the organization's software users. Web services are the dominant approach for implementing SOA.

3. Web Services Are Not Web interfaces Web-based information resources Web-based “services” Software as service Application service provider Web Service Librarian

4. Web Services Definition A Web service is a software system designed to support interoperable machine-to-machine interaction over a network. 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. (World Wide Web Consortium)

5. Communication Path for Web Services

8. Simple Object Access Protocol (SOAP)

10. Simple Object Access Protocol (SOAP)

11. Web Services Description Language (WSDL)

13. Second-Generation Specifications WS-Security

14. Second-Generation Specifications WS-Security WS-AtomicTransaction/WS-BusinessActivity

15. Second-Generation Specifications WS-Security WS-AtomicTransaction/WS-BusinessActivity WS-Coordination

16. Second-Generation Specifications WS-Security WS-AtomicTransaction/WS-BusinessActivity WS-Coordination WS-Reliable Messaging

17. Second-Generation Specifications WS-Security WS-AtomicTransaction/WS-BusinessActivity WS-Coordination WS-Reliable Messaging WS-Attachments

18. Second-Generation Specifications WS-Security WS-AtomicTransaction/WS-BusinessActivity WS-Coordination WS-Reliable Messaging WS-Attachments Business Process Execution Language for Web Services (BPEL4WS)

23. A consortium of vendors formed to facilitate the development of interoperable Web services related to library applications.

24. Goal: Provide a forum in which library-automation vendors could establish a set of Web services that can be used in library applications.

27. Produce and maintain a “Web Services Best Practices” document for general use in assessing new and ongoing Web-service applications

30. Open Systems Interconnect style of communication based on ASN.1 and BER

32. International standard employed across many industries

33. Used between libraries and suppliers Electronic ordering Making claims for items expected and received Transfer of invoices

34. MARC 21 Format Most widely accepted adapted library standard Formats store bibliographic records in a compact format. MARCXML – Provides XML Structure for MARC 21 data. Metadata Object Description Standard (MODS) XML schema for MARC 21 bibliographic records Metadata Authority Description Schema (MADS) XML schema for selected tags of the MARC 21 authority format. Encoded Archival Description (EAD) Standard for creating finding aids of archival collections in XML.

35. Dublin Core Metadata format expressed in XML. Provides simplified approach for describing information objects. Widely used as a metadata format describing electronic resources or other application in which MARC format is not needed. OpenURL Provides a mechanism for linking to resources independently of their physical locations.

36. Library Protocols based on Web Services Z39.50 International: Next Generation (ZING) Established to take the concepts and functionality embodied in Z39.50 forward. Development of a version of Z39.50 in the framework of Web services – search-and-retrieval protocol. SRU: Search/Retrieve via URL SRW: Search/Retrieve Web Service

37. SRU and SRW supports three operations: SearchRetrieve Scan Explain Implementation of SRU and SRW OCLC Research Index Data The Cheshire Project

38. Open Archives Initiative Protocol for Metadata Harvesting Supports federated-search model Harvesting metadata from multiple information repositories Create centralized search services Provides alternative to those based on simultaneous queries. Relies on data providers and service providers. Web harvesting: Provides means to harvest new and changed pages.

39. Standardized Usage Statistics Harvesting Initiative (SUSHI) Deals with issue of transferring statistics that assess an institution’s use of an electronic resource that the library subscribes to. Project COUNTER Initiative to develop set of standard practices regarding how publishes will produce use statistics related to library subscriptions.

41. When we think of architecture we think of

42. or

43. “Service-oriented” architecture might be more like

44. INTEROPERABILITY or, many moving parts

45. Why this matters

46. Services make life easier

47. We want to do things here:

48. Research

49. Architectural Repository, aka SOA

56. SOA allows the library or archive: Manage materials effectively Build on resources Greater collaboration with other organizations and businesses Provide services within campus or municipal portal environments or other non-traditional channels Enhance research experience

57. SOA allows the user: Ease of access Multimedia resources More resources = a more global understanding of a subject Opportunity to consider relationships between items More fun