1. 1 1 ECHO Extended Services WGISS – 23 Hanoi, Vietnam May 15, 2007

2. 2 Agenda ECHO Status Review of Extended Services Policy and Governance ECHO’s Service Domain Model How to…

3. 3 ECHO Status and Activities Release Highlights Performance Status Current Participation Upcoming Highlights GCMD Interoperability

4. 4 What is ECHO? SOA-based middleware for the exchange of Earth Observation resources Based on Web Service Technologies Focused on Interoperability Two types of registries Data Registry Published metadata representing data holdings –Datasets (directory-level) –Granules (inventory-level) Data model is comprehensive, yet extensible Service Registry Standards-based Multiple service types Flexible Categorization ECHO’s services that support the interaction with those registries: Publication Discovery Understanding Access

5. 5 ECHO Status - Version 9 Version 9 went operational on April 25, 2007 Key Capabilities Improved Catalog Searching Performance Case Sensitive Searches Improved Order Options SSL communication Streamlined API for providers New Order Options framework Improved Reconciliation Capabilities Improved error handling Eventing for Services Web-based PUMP tool

6. 6 ECHO Status - Performance ECHO performance improvement activities focused on Queries, Presenting Results, and Ordering Overall significant performance improvement: Version 9 is 91% faster than ECHO Version 8 ECHO 8.0ECHO 9.0 1 Dataset, Spatial 1, and Temporal 2 10811 1 Dataset, Spatial 3, and Temporal 4 48041 >10 Datasets, Spatial 1, and Temporal 2 69060 Spatial 1 and Temporal 2 2760180 1 Dataset and OnlineOnly1308 Dataset(s), Spatial 1, Temporal 2, and OnlineOnly4610 1 Dataset, Spatial 1, Temporal 2, and DayNightFlag 4612 1.10 o x 10 o 2.1 month 3.25 o x 75 o 4.10 months

7. 7 ECHO Status - Current Participations Current Holdings Collections2,082 Granules56 million Browse19 million Data Partners Operational Public 10 Test 1 (PO DAAC) Proposed2 (USGS, OCDPS) Landsat incorporation in process Availability beginning by end of 2007 Client Partners Operational1 In evaluation or test9 Active development3 Planning/requirements3

8. 8 ECHO Status - ECHO 10 Target Operational Q1 2008 Ingest Updates Improved Operability Improved Reconciliation Updated data rules for data integrity Increase reliability and maintainability Security improvements Migrate existing ECS User accounts to ECHO Alpha Testbed available http://testbed.echo.nasa.gov/echo/ http://testbed.echo.nasa.gov/echo/

9. 9 ECHO Policy – Participation Data Providers ECHO works to specific Data Success Criteria, as part of the EOSDIS Evolution implementation effort 2005-2008. Support metadata and browse for all EOS data products and other identified data held by NASA DAAC and Data Centers or the USGS Long-term Archive. Transition existing EDG partners to ECHO, including interested international partners Clients ECHO has an open policy for clients; anyone can create an ECHO client ECHO is identifying science communities who could benefit from ECHO’s capabilities and resources (e.g. metadata and services) ACCESS 2006 solicitation for ECHO clients OPeNDAP community Proposed TERRA data fusion client Extended Services ECHO is also looking to find extended services that could be applied to the data represented in ECHO and would benefit the science community ESDS’ Tech Infusion WG has been adding services to ECHO LP DAAC has identified services that they would like to offer in ECHO for the land community Proposed TERRA data fusion client will add data fusion services to ECHO CEOS presentation to solicit services participation

10. 10 GCMD Interoperability GCMD and ECHO provide complementary capabilities to enable Earth science research GCMD enables users to locate a broad spectrum of Earth science datasets and services relevant to global change and Earth science research. GCMD holds over 21,000 metadata records. ECHO enables users to search and access NASA’s granule-level Earth science data and related services through tailored interfaces. ECHO has over 2,000 datasets and 56 million granules. GCMD and ECHO interoperate to provide a cohesive perspective of NASA’s Earth science data holdings

11. 11 ECHO Extended Services - Overview

12. 12 Extended Services Background What are “Extended Services” “Services” - functional capabilities offered by the community “Extended” – because they are not native to ECHO Published to the ECHO Registry Functional Summary – What does ECHO do with them? Register – Service Providers register the services Activate – ECHO operations review and activate them. Find – Users find the services using the UDDI inquiry API or Extended Services Viewer Retrieve – Users can get the services to view their details Update – Service Providers can update their services Delete – Service Providers can remove their services

13. 13 Extended Services Capabilities Full CRUD for Extended Service Entities Create Read Update Delete Allow for combined Service Interface/Implementation WSDL Single registration sequence Initial brokering of services Invocation Service

14. 14 Extended Services Capabilities (con’d) Event Management Publication of events for changes in the registry Examples: New Service Interface, Service Deleted, Service Updated, etc. Ability to subscribe to those events Notification upon event occurrence Event Summary New Dataset Updated Dataset Deleted Dataset New Service Updated Service Deleted Service Based on WS-Eventing & -Notification

15. 15 Policy and Governance Policy drives how an organization uses the tools available to them. To protect the organization’s interests ECHO is a partnership between NASA and ECHO participants NASA has the responsibility to ensure that what it publicly represents is legitimate and appropriate ECHO policy practices Registered partners may publish Form sent to ECHO Operations team NASA approval Two-phased Publication Registration & Activation

16. 16 Registration & Activation Pattern

17. 17 ECHO’S Service Domain Model Provider

18. 18 Extended Services Entity: Web Service Interface Defines a web service API Defined in a WSDL file Hosted within ECHO system Centrally managed interfaces encourages standardization and reuse within community Reusable between provider organizations Example: Common Subsetting interface Common Access service interface (OPeNDAP) WMS service

19. 19 Extended Services Entity: Web Service Implementation An executable web service hosted by an ECHO Service Provider Defined in a WSDL file Contains at least one service element May implement interfaces registered in ECHO By importing interface WSDL from ECHO hosted location Examples: An application-specific service (OPeNDAP Query adaptor) A predictive model Specific WMS server

20. 20 Extended Services Entity: Web Service GUI A user interface for a web service Provides a way for human to interact with a web service Includes name, description, and access point Associated with implementations and interfaces registered in ECHO Examples: ECHO Query Client Domain Specific User Client for subsetting

21. 21 Extended Services Entity: Advertisement A way to advertise a service that is not a real Web Service Includes name and description of service and an access point Example Service for expert advice on a specific application area Ability to drop sensors in the Chesapeake Bay

22. 22 Categorization and Classification Natural technique for understanding and remembering items and their relationship to other items Categorization Process of creating categories or types Classification Process of assigning objects within categories Example: Animal and Plant kingdoms Businesses in a phone book

23. 23 Taxonomies A way of classifying extended service entities in ECHO. Have a tree like structure. Root of the tree is the taxonomy. Leaves and nodes on the tree are taxonomy entries A taxonomy entry is a name and value pair. Values are unique in a taxonomy.

24. 24 Virtual Taxonomies This is a type of taxonomy (categorization scheme) that is populated by ECHO automatically. Example: As new data providers and their datasets are registered, they are added to the taxonomies (as appropriate) They behave and look to the user like a regular static taxonomy.

25. 25 Existing Taxonomies in ECHO nasa-ECHO:Dataset Is a virtual taxonomy Datasets are automatically added to the taxonomy when they are ingested into ECHO Used to classify services according to the primary type of input data (the data that is primarily operated upon) Contains each provider and Collections for that provider

26. 26 Existing Taxonomies in ECHO nasa-ECHO:ServiceType – This is a categorization scheme of kinds of services from a functional perspective. It is comprised of other taxonomies defined by external organizations. Currently contains: ISO 19119 (OGC) Specific OGC subgroups OPeNDAP

27. 27 Existing Taxonomies in ECHO nasa-ECHO:DataFormat – This is a categorization scheme based on the format of Earth Science data. It is similar to a mime-type classification scheme. Currently contains Complex Graphical

28. 28 Classification within ECHO Service Partners classify their service offerings Upon Publication Updates as needed Classification is not required But very useful Multiplicity Classify to zero or more Taxonomies Classify to zero or more nodes within a Taxonomy

29. 29 How To… What is available to use ECHO Extended Services APIs Documentation Tools Extended Services Scenarios Register as a Service Provider Publish a Web Service Interface Publish a Web Service Implementation Publish a Web Service GUI Publish an Advertisement Classify an offering Update an offering Delete an offering

30. 30 Using Extended Services API’s available for all capabilities Operational System http://www.echo.nasa.gov/reference/reference.shtml Extended Services Registry Tool (ESRT) GUI for all management functions (CRUD) http://www.echo.nasa.gov/services/service_tools.shtml Extended Services Viewer Navigation tool to discover services Operational System http://api.echo.nasa.gov/echo-esviewer/

31. 31 ECHO Tools – Extended Services Registry Tool (ESRT) Tool for Service Partners Registration Publishing Services Any type Classification Manage Organizational contacts Full CRUD

32. 32 ECHO Tools – Extended Services Viewer Discovery and Navigation Tool for Services Registry Each Categorization Scheme represented by a tree Details of selected node presented in the right-hand panel

33. 33 Create an ECHO User Account Logon as “guest”, with your email address as a password. Once logged on, select the “User” Task Group

34. 34 Create an ECHO User Account

35. 35 Create an ECHO User Account

36. 36 Create an ECHO User Account

37. 37 Register as a Service Provider Goal As an organization, offer your capabilities to the broader EO community Prerequisites Register as a User Login as User Once logged in to ECHO using the ESRT, Select the “Provider“ Task Group. Then select “Create Provider”

38. 38 Register as a Service Provider

39. 39 Register as a Service Provider

40. 40 Register as a Service Provider

41. 41 Register as a Service Provider Describe your offerings in the “Descriptions” panel In the “Additional Information” text area, provide the ECHO user account name that you would like associated with this provider or contact ECHO Ops @ echo@killians.gsfc.nasa.gov to have them associate your ECHO user account with the ECHO Service Provider. echo@killians.gsfc.nasa.gov

42. 42 Register as a Service Provider At this point your organization has been registered, but not activated. ECHO Operations has been notified of your registration and will review the application. Once they approve your application, you will be notified via email sent to the email address you supplied above.

43. 43 Register as a Service Provider Once you are notified that your ECHO user account is associated with an ECHO Service Provider you can begin to register your Extended Service. The next time you login, you enter your provider ID in the “On behalf of provider” field.

44. 44 Publish an Extended Service Under the “Task Groups” for Extended Services you must register your Interface, Implementation, GUI or Advertisement service. ECHO Ops will then review your registration and notify you of your status.

45. 45 Publish a Web Service Interface Goal Offer a standard interface which can be used by multiple organizations. Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider Have the Web Service Interface defined in a.wsdl file

46. 46 Publish a Web Service Implementation (using a Web Service Interface) Goal Offer a Service for access by the community Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider Have the Web Service Implementation defined in a.wsdl file Reference a published Web Service Interface

47. 47 Publish a Web Service GUI Goal Offer a GUI which provides a human interface to a published Web Service, for access by the community Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider Reference a published Web Service Interface or specific Web Service Implementation

48. 48 Publish an Advertisement Goal Offer a capability which is not a Web Service, to the EO community Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider

49. 49 Classify an Offering Goal Enable better discovery by classifying your offering in one or more taxonomies Can be done in registration, or by updating Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider A registered service offering has been (or is being) published

50. 50 Update an Offering Goal Change the information representing a published service offering Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider A registered service offering has been (or is being) published Have the GUID of the service to be updated

51. 51 Delete an Offering Goal Remove a published service offering Prerequisites Be a registered User Your organization is a Registered Service Provider Login, with your provider context set to a Registered Service Provider A registered service offering has been (or is being) published NOTE: ECHO will “take ownership” of an interface which has dependent implementations and/or GUIs.

52. 52 Contacts http://www.echo.nasa.gov/ ECHO Operations team echo@killians.gsfc.nasa.gov NASA ECHO Operations Lead Andy Mitchell Andrew.E.Mitchell@nasa.gov Me Michael Burnett michael.burnett@vangent.com

53. 53 Backup Slides

54. 54 Submit search criteria to WIST Use Portal to select metadata GCMD Search GCMD for datasets ECHO GCMD and ECHO: Users Or search WIST for granule-level metadata Display Results WIST GCMD’s ECHO Portal 1 2 3 4 5 6 Query ECHO 7 Click “Get Data” link

55. 55 GCMD and ECHO: Data Providers