1 / 10

NASA EOS Web Services Experiences

NASA EOS Web Services Experiences. September 25, 2008 Michael Burnett Beth Weinstein. Value of Web Services. Standards-based Software-interface Separation of Interface from Implementation Location Independence Technology independence Enables (and encourages) reuse

felcia
Download Presentation

NASA EOS Web Services Experiences

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. NASA EOS Web Services Experiences September 25, 2008 Michael Burnett Beth Weinstein

  2. Value of Web Services • Standards-based • Software-interface • Separation of Interface from Implementation • Location Independence • Technology independence • Enables (and encourages) reuse • Supports a net-centric enterprise • Providers can offer capabilities more efficiently

  3. Standards & Web Services • Description • WSDL • Discovery • UDDI, ebXML • Access • SOAP, REST • Processing • OGC WxS

  4. Role of Web Services within NASA EOS • Infrastructure • Participation • Security • Eventing • Publication • Discovery • Collection and Granules • Access • Ordering • Direct • Processing • Subsetting • Transforming • Orchestration

  5. Web Services in NASA EOS

  6. OGC and Web Services • WxS implemented operationally at various levels • In process of assessing the benefit of OGC services • Some are widely accepted and providing tremendous value • WMS, WFS (issues with gridded data) • Some need maturing • WCS, SWE (SOS) • Jury is still out • CWS • Topics • Feedback on interfaces, as web services is mixed • Variation in “standards” makes it challenging to test for compliance

  7. Using Web Services • Clients using Web Services • Growing in number • Examples • WIST, SNOWI, AOTC, WECHO, AQUA, EOLI (eoPortal) • Applications using Web Services • Compositing, or value-added services • Examples • Data Mining System, leveraging BPEL, ECHO (GES DISC) • Brian Wilson’s ordering/staging tool

  8. Security • Does Security Matter? • If so, need Authentication and Authorization services • Agree on them, interoperability, User Management, Authority management, etc.

  9. Progress of Adoption • Commitment to using Web Service Standards many years ago • Providing web service Infrastructure, enabling an SOA • Move to Services • Application decomposition, de-layering is gaining strong momentum • New capabilities are being designed with a services-view point • Hesitation on offering services • Once a service is public, how does the organization prepare for its use? Causes services to be “hidden”

  10. Lessons Learned / Observations • Standards aren’t really mature in many cases • CSW point-to-point, vice interoperability • Still have the challenge of categorization • Facilitation of discovery, probably don’t want to wait for full adoption of semantic web • Service interoperability is complicated • Parameters, chaining, etc. Beyond hand-stitching • Address robustness in your plan • Account for exceptions and error management • Perl can cause some interoperability challenges (namespace management) • Still a bit of a frontier • But there are very valuable lessons learned , which can be leveraged in the next generation • Web Services are a part of the future • NASA EOS is committed to continued adoption of Web Services

More Related