ECHO Services Discussion
WGISS 18
September 6-10, 2004
Beijing, Peoples Republic of China
Robin Pfister
NASA/GSFC
ECHO OverviewNative Services
• Metadata Clearinghouse (Registry)– ECHO makes the data holdings of the Earth Science Enterprise available to clients as if they had
a copy of all the metadata in their system
• Order Broker– ECHO provides a single interface for clients to place orders through and deals with the complexity
of ordering from its partner systems on behalf of the client
• User Account Management– While not a primary feature of the system, ECHO provides flexible user account management for
both registered users and providers in support of its registry and brokering roles
• Service Registry– ECHO provides a mechanism for clients to find out what Earth Science services are available
dynamically. ECHO provides the mechanism for services to express their relationship to Earth Science data
• Service Broker– ECHO will allow a client to order data from a data provider and then have a series of services
applied to it by relying on ECHO to do the coordination
• Open Source: http://opensource.arc.nasa.gov/
The Big Picture• Enabling Technology
– Middleware, not GUIs
• Marketplace– Providers offer their wares– Consumers find what they like and access it
• Interoperable Registries – Data
• Metadata Catalog/Clearinghouse• Inventory Level
– Services• Service Registry• Web Services Technology• Service User Interfaces (UIs)
– Interoperable Through Registry Taxonomies
ECHO in the EnterpriseClients
DataAcquisition
DataProcessing
Archive
Delivery/Fulfillment
…ECHO DataRegistry
ECHO ServiceRegistry
Enterprise Middleware
…
Definition and Usage
• Service - A capability offered by a provider.
• By participating in ECHO, the service’s interface is declared using standard semantics and technology (WSDL, SOAP) in a way that potential users can find, understand and access.
• Types of Services - Advertised, Brokered, Chained
Service MiddlewareUses a Service Oriented Architecture
(SOA)ECHO Client
Service ProviderBind
ECHO Operations
(from Use Case View)
ECHO Service Registry
PublishFind
manages
<<UDDI>>
<<SOAP>>
<<WSDL>><<UDDI Query>>
Service Capability Status
• Advertised services - operational
• Service Brokering - initial studies in progress; prototyping to begin soon.
• Service Chaining - will follow brokering.
Service BrokeringService Provider
Service Registry Metadata Catalog
ServerClient
Discover DataRequest Service
Invoke Service
Publish Service
Data Provider
Mainframes
Publish metadata
Access Data
Move Data (Control)
Send Results
Ultimate Goal is Service Chaining: A Distributed Virtual Computer
Service Provider
Service Registry Metadata Catalog
ServerClient
Request Service Chain
Data Provider
Mainframes
Access Data
Move Data (Control)
Service Provider
Server
Service Provider
Server
Move Data
Move Data
Move Data
Potential Topics for Follow-up Services Presentation in February
• Brokering Issues and Solutions
• Service Chaining Model
• Classification of Services in the Enterprise– Incl. What do we do when it evolves (issues
related to change)
• Federating these registries
Other Items of Interest…
ECHO Data Partner StatusStatus Organization Collections Browse Images Granules (data items)
Operational Alaska SAR Facility 14 (all restricted) 0 1,759,106 (all restricted)
Operational Goddard ECS DAAC (GDAAC)
357 981,867 16,965,099
Operational Land Processes EOS Core System (ECS) DAAC (LPDAAC)
85
(14 restricted)
2,132,233
(7,316 restricted)
10,867,820
(16,938 restricted)
Operational Atmospheric Sciences Data Center (ASDC)
91
(all restricted)
709,064
(all restricted)
1,705,492
(all restricted)
Operational Oak Ridge National Laboratory (ORNL) Distributed Active Archive Center (DAAC)
653 0 105,124
Operational Socioeconomic Data and Applications Center (SEDAC)
50
Collections are orderable items
0 0
Operational Stennis Space Center Data Purchase Project
22
(all restricted)
0 2,932
(all restricted)
Test National Snow and Ice Data Center (NSIDC) DAAC
35
(all restricted)
0 62,066
(all restricted)
Totals (public/restricted): 27,921,105 /3,546,534
3,106,784 / 716,308
1,131 / 176
OGC-ECHO Adaptor
• The OGC-ECHO Adaptor (OEA) will provide a mechanism to present ECHO holdings in an OGC-compliant fashion.
• It will service Z39.50 GEO profile catalog requests
• The Earth Science Gateway Portal (Geospatial One-Stop) is the client that is driving this development.
• The OEA will comply with version 1 of the OGC Catalog Services Specification (http://www.opengis.org/docs/02-087r3.pdf).
System Interoperability
• As we move to ECHO, the EOS Data Gateway is also being modified to interoperate via ECHO.
• For distributed searching we were hoping to move into current technology by replacing the V0 interoperability mechanism with an OGC standards based mechanism.
• We’d like feedback from those who are currently interoperable if moving to OGC interoperability standards is okay.
• Please send e-mail with responses, and also concerns and discussions. [email protected]
Thank you