© 2006 Blueprint Technologies, Inc. All Rights Reserved ECHO – NASA’s Middleware for an Earth...

© 2006 Blueprint Technologies, Inc. All Rights Reserved

ECHO – NASA’s Middleware for an Earth Science Marketplace

Overview and Status

WGISS 22


Influences on Science

• Complex Problems– Societal Benefit

• Stakeholders Community– Scientists– Educators– Decision Makers– Public Consumers

• Pace of Innovation– Double Edged Sword

• Need to collaborate– Value of Synergy– Resource Sharing

• Funding


Cyberinfrastructure

• Providing an environment for Science– eScience

• (R)evolution of Technologies– Processing– Networking– Storage– Information Technologies

• Policy Challenges– Governance: What is made available, to whom, when– Retirement Strategies– Consumption of computational resources– Cost of resource management

Atkins Report (NSF): http://www.nsf.gov/cise/sci/reports/atkins.pdf


Architectural Drivers

• What influences the solution?– Flexibility– Evolvability– Extensibility– Net-Centric

• Functional demands– Publishing Resources– Discovery– Access

• GEOSS– Support the Reference Architecture


Service Oriented Architecture (SOA)

• Representing resources as Services– Interface specifications as “contracts”

• Fundamental Architecture Pattern– Publish– Find – Bind

• Dynamic, loose coupling

• Net-centric Architecture– Application Network

• Distribution of resources & roles

ECHO Client

Service ProviderBind

ECHO Operations

(from Use Case View)

ECHO Service Registry

PublishFind

manages


ECHO Vision

• Goals– Support a Marketplace …– Enabling …

• Approach– Interoperable Registries

• Publish• Find (Discovery)• Binding (Access)

– Not “the” solution/system• But integrated into a dynamic enterprise• Building systems, interoperating with systems

– Net-centric• Power to the partners


ECHO in Cyberinfrastructure

• Enterprise-level middleware– Enabling…– Core Services (e.g. – Registration, Security, Ordering, Query, etc.)– Leveraging Web Service Technologies (XML, WSDL, SOAP, UDDI)– Based on Interoperable Registries– “Power to the Partner”

• Fundamental Use Cases– Publish EO Resource– Discover EO Resource– Understand EO Resource– Access EO Resource

• Current Status– 70+ Million Earth Science items– extra-NASA participation


ECHO’s Metadata Registry

• Common metadata model– Based on NASA’s ECS data model (ISO 11179)– Maps to standards (ISO 19115, FGDC)– Multiple spatial models supported (Cartesian, geodetic, orbital)– Extensible through product specific attributes

• XML is the language of metadata exchange

• Data Partners use Partner Interface Tools– Represent their own data holdings– Two level access control (visibility, accessibility)

• Ingest Adaptors– Run partner-specified translation rules– Run partner-specified validation rules


Extended Services Registry

• What are “Extended Services”– “Extended” – because they are not native to ECHO– “Services” - functional capabilities offered by the community– 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


ECHO & UDDI (Universal Description, Discovery and Integration)

• Service Registry• Provides Domain View of UDDI

Registry

• Four fundamental “service objects”– Web Service Interfaces– Web Service Implementations– Web Service GUIs– Advertisements

• Using Systinet


Categorization in Service Registries

• Facilitate Discovery

• Taxonomies– DataSet– DataFormat– ServiceType– IDNKeyword (coming)

• Rules of EngagementProviders Rule

– They declare their own categorizationsFlexibility

– Service Objects can be categorized in zero or more taxonomies

– Service Objects can be categorized in one or more nodes within a taxonomy

Changeability– Providers can change categorization as they wish

Extensibility– New categorization schemes (taxonomies) may be added

without perturbing existing categorizations– New nodes can be added to taxonomies

WebServiceIF

WebServiceImp

WebServiceGUI

Advertisement

Categorization

(taxonomy)

(node)


ECHO & WSDL(Web Services Description Language)

• Describing Web Services– Interface

• Operations, Parameters & Types

– Binding Location• Machine, Port & Protocol, Quality of Service

• Following Best Practice– Using WSDL in UDDI Registry– Separation of Interface from Implementationhttp://www.uddi.org/pubs/wsdlbestpractices-V1.07-Open-20020521.pdf

• Ownership of WSDL– ECHO Stores Interface WSDL

• Assumes ownership if removed, and dependencies exist

– Implementation WSDL• Owned and offered by partner• Imports Interface WSDL


Interoperability for the Science Enterprise

• Open Interfaces (APIs)

• Adoption of Standards

• Between registries– Service Registry through Taxonomies

• Based on Data Sets and Formats

– Data Registry through Catalog Service• What Services are available for this item?

• External Interoperability– Adaptors

• Protocol interoperability with Partners for order and ingest• Data model interoperability through Ingest Adapters and data set registration• Can establish “Views” of results

– ECHO services enable external other interoperability through adaptors• Ostensibly, ECHO clients


Governance of Services

• Science Marketplace– Registered Providers only, with MOUs– Must supply discoveryURL’s for human understanding

• Policies– Owned by NASA– Implemented by Operations Team

• Two-phase publication– Register– Manual activation by Operations Team, after review

• Ownership of “Abandoned Interfaces”

• Endorsements


Current Status

• Operational Version – (about to be, October 2006) 8.0

• 8.0 Capabilities – 7.0 ++– Full Web Service (Basic Profile 1.0 compliant)– Asynchronous Queries– PSA searching– Filtered subscriptions (temporal and spatial)– Full Service Model Support (CRUD on all Entities)

• 9.0 Features– SSL Ordering– Upgraded Exception framework– Metrics– Improved Performance– Interoperability with GCMD– Event Management


Summary

• ECHO is:– Middleware for the enterprise– Supporting SOA– Marketplace of EO resources– Enabling..

• Currently Operational– Significant population of Registry– Full Operations Team

• Growing– More NASA resources– US resources beyond NASA– International Partners

• For more information– http://www.echo.eos.nasa.gov/

© 2006 Blueprint Technologies, Inc. All Rights Reserved ECHO – NASA’s Middleware for an Earth...

Documents

Transcript of © 2006 Blueprint Technologies, Inc. All Rights Reserved ECHO – NASA’s Middleware for an Earth...