1 / 28

IRIS Web Services Initiative

IRIS Web Services Initiative. building new capabilities. Outline. Introduction to web services Web services at IRIS DMC Introduction to service oriented architecture Future directions. Outline. Introduction to web services Web services at IRIS DMC

keanu
Télécharger la présentation

IRIS Web Services Initiative

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. IRIS Web Services Initiative building new capabilities

  2. Outline • Introduction to web services • Web services at IRIS DMC • Introduction to service oriented architecture • Future directions

  3. Outline • Introduction to web services • Web services at IRIS DMC • Introduction to service oriented architecture • Future directions

  4. What are web services? A Web service is a software system designed to support interoperable machine-to- machine interaction over a network. [www.w3c.org] • Many protocols fit this definition • CORBA • SOAP • REST • Usually specifies XML-formatted messages to be passed over HTTP

  5. Characteristics of a web service • Distributed • Stateless • Synchronous • XML messages passed over port 80

  6. SOAP web service overview • Client discovers a service (often skipped) • Client interprets what the service can provide through the WSDL • Client makes a request in the format specified by the WSDL • Service responds to that request

  7. REST and SOAP REST Representational State Transfer No interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  8. REST and SOAP REST Representational State Transfer No formal interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  9. REST and SOAP REST Representational State Transfer No interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  10. REST and SOAP REST Representational State Transfer No interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  11. REST and SOAP REST Representational State Transfer No interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  12. REST and SOAP REST Representational State Transfer No interface definition Query is in the form of a URL Response is XML Suitable for small numbers of input criteria, simple responses No support for binary attachments SOAP Simple Object Access Protocol Interface defined through WSDL Query is XML, contains SOAP specific headers Response is XML , contains SOAP specific headers Capable of expressing complex queries and responses Support for binary attachments

  13. Example REST Message Request is a simple URL http://www.new-iris-service.edu/channels/IU/TUC/00 Client recieves XML snippet <?xml version=“1.0”?> <p:channels xmlns:p=“http://www.new-iris-service” xmlns:xlink=“http://www.w3.org/1999/xlink”> <network>IU</network> <station>TUC</station> <location>00</location> <channels> <channel>BHE</channel> <channel>BHN</channel> <channel>BHZ</channel> <channel>LHE</channel> <channel>LHN</channel> <channel>LHZ</channel> </channels> </p:channels>

  14. Example SOAP Message SOAP Query <SOAP:Envelope xmlns:SOAP=“http://schemas.xmlsoap.org/soap/envelope> <SOAP:Body xmlns:netDC=“http://www.iris.edu/networkDC”> <netDC:GetChannelInfo> <network>IU</network> <station>TUC</station> <location>00</location> </netDC:GetChannelInfo> </SOAP:Body> </SOAP:Envelope> SOAP Response <SOAP:Envelope xmlns:SOAP=“http://schemas.xmlsoap.org/soap/envelope> <SOAP:Body xmlns:netDC=“http://www.iris.edu/networkDC”> <netDC:GetChannelInfoResponse> <network>IU</network> <station>TUC</station> <location>00</location> <channels> <channel>BHE</channel> <channel>BHN</channel> <channel>BHZ</channel> <channel>LHE</channel> <channel>LHN</channel> <channel>LHZ</channel> </channels> </netDC:GetChannelInfoResponse> </SOAP:Body> </SOAP:Envelope>

  15. Why web services at the DMC? • Allow programmatic access to IRIS DMC resources • Different software tools can make use of same components • Outside users can incorporate these resources into their own software • Services can be accessed from a wide variety of languages, including MATLAB • Web services are becoming ubiquitous • Many organizations offer web service interfaces to various resources • NSF is encouraging the scientific community to adopt web services

  16. Outline • Introduction to web services • Web services at IRIS DMC • Introduction to service oriented architecture • Future directions

  17. Existing/upcoming IRIS services

  18. DHI through web services

  19. SeismoProcess • Developed to support SOSA • Update and expand processing capabilities without re-installing application • Prototype for more general seismogram processing service

  20. SPADE

  21. Outline • Introduction to web services • Web services at IRIS DMC • Introduction to service oriented architecture • Future directions

  22. SOA Basic Definition • A perspective of software architecture that defines the use of services to support the requirements of software users. • Nodes on a network make resources available to other participants in the network as independent services that the participants access in a standardized way. • Most definitions of SOA identify the use of Web services (i.e., using SOAP or REST). However, one can implement SOA using any service-based technology. • The software components become very reusable because the interface is standards-compliant and is independent from the underlying implementation of the service logic. [From Wikipedia]

  23. Characteristics of Service Oriented Architectures • Services have contracts • Provides information about itself • Establishes agreement between provider and requestor • Services are loosely coupled • They play together, but play apart as well • Changes to one service implementation shouldn’t break another • Services are composable • Multiple services can be linked together • Implies contracts are compatible (data access seismogram = analysis seismogram)

  24. Composing services

  25. Outline • Introduction to web services • Web services at IRIS DMC • Introduction to service oriented architecture • Future directions

  26. Composing IRIS services

  27. Why SOA at IRIS? • Make better use of resources Tools can be linked together Continuous upgrades • Provide other capabilities such as analysis and visualization tools Capabilities are coupled to data access Allow basic processing before data download • Link to other data providers Hopefully will become part of broader geosciences service architecture

  28. Need community involvement! • Looking for potential beta users • People interested in developing clients

More Related