1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL...
-
Upload
nelson-morris -
Category
Documents
-
view
214 -
download
0
Transcript of 1 Registry Services Overview J. Steven Hughes (Deputy Chair) Principal Computer Scientist NASA/JPL...
1
Registry ServicesOverview
J. Steven Hughes (Deputy Chair)
Principal Computer Scientist
NASA/JPL
April 21, 2023
2
Outline
DSMS Needs
Service Registry
Schema Registry
Data Element Registry
3
DSMS NeedsOverview
DSMS is looking for an enterprise hosted Registry Service.
DSMS Requirements Documents DSMS WebGDS Registry Service - Software Requirements
Document (SRD), October 21, 2004, M. DeMore.
Use Cases for the DSMS WebGDS Registry, October 14, 2004, M. DeMore.
4
DSMS NeedsRegistry Service Components
Data Element/Data Type Registry: Provides common data dictionary information that contains element definitions and data type definitions
XML Schema Registry: Provides a versioned repository for XML schemas that describe messages, file formats, and data components.
XML Stylesheet Registry: Provides a versioned repository for XML stylesheets that perform common data translations.
Namespace/Domain Registry: Provides a controlled, hierarchical namespace/domain registry.
Service Registry: Provides a dynamic Registry for Web Services.
Model Registry: Provides a repository for information models, data relationships, and other ontological information.
5
DSMS NeedsHigh-Level View
6
DSMS Needs CIO/Standards Efforts
Service Registry Evaluating COTS and Open Source products.
Schema Registry A component of the Metadata Service.
Currently deployed in the DSMS development environment.
Data Element Registry A component of the Metadata Service.
Currently deployed in the DSMS development environment.
7
Service RegistryWhat is UDDI?
The Universal Description, Discovery, and Integration (UDDI) protocol is a key member of the group of interrelated standards that comprise the Web services stack. It defines a standard method for publishing and discovering the network-based software components of a service-oriented architecture (SOA).
A Service is a software component that exports an API and provides a service for other software components on the network. The API must be such that it can be externally described to a degree sufficient for locating and using the service. In DSMS WebGDS, this generally will apply to Web services that can be described using WSDL or tModels, but the idea can be applied to other types of interfaces as well.
8
Service RegistryWeb Services Stack
9
Service RegistryStandard
UDDI specifies protocols for: Publishing and searching
services registry
Controlling access to registry
Distributing and delegating to other registries
Managed by OASIS standards body
VERSION YEAR GOALS
1.0 2000Public
registry foundation
2.0 2003
Web services alignment
and extensible
taxonomies
3.0 2004
Flexible and secure registry
interaction models
10
Service RegistryProducts
Oracle Application Server Offered as an optional component.
Minimal web-based GUI.
Currently deployed at http://uddi.jpl.nasa.gov/.
DSMS personnel have not had a chance to try it out.
Apache jUDDI Plays nice with Tomcat and PostgreSQL.
Encountered problems when accessed from Java’s Web Services Developer Pack (JWSDP) example applications.
11
Schema RegistryOverview
This registry provides a central repository for developers and organizations to publicly submit, publish and exchange XML-based schemas.
A component of the Metadata Service. An effort currently funded by the CIO.
Interfaces Application Program Interface (API)
Support distributed access using CORBA/RMI
Support Java and HTTP application interfaces
Command-Line
Web-Based GUI
Planned Features for Future Releases Support for Authentication and Authorization
12
Schema RegistryCurrent Deployment
Deployed with Metadata Service release 2.0.0 http://metadata.jpl.nasa.gov/ on February 9
http://bayamo.jpl.nasa.gov:8080/ on March 5 (DSMS Deployment)
Features Add, remove and modify schemas and their supporting
metadata in the registry.
Metadata capture based on the Dublin Core Element Set.
Allow for versioning and promotion of schemas.
Capability to locate and access registered schemas.
Provide for URL access to registered schemas.
Provide for a web directory hierarchy for organizing schemas.
13
Data Element RegistryOverview
This registry provides the capability to register and manage a data element and associate it with a data dictionary.
A component of the Metadata Service. An effort currently funded by the CIO.
Interfaces Application Program Interface (API)
Support distributed access using CORBA/RMI
Support Java and HTTP application interfaces
Command-Line
Web-Based GUI
Planned Features for Future Releases Support for value domain
Support for element relationships
Support for Authentication and Authorization
14
Data Element RegistryCurrent Deployment
Deployed with Metadata Service release 2.0.0 http://metadata.jpl.nasa.gov/ on February 9
http://bayamo.jpl.nasa.gov:8080/ on March 5 (DSMS Deployment)
Features Based on the ISO/IEC 11179 “Information technology --
Specification and standardization of data elements”.
Add, remove and modify data elements and their supporting attributes in the registry.
Allow for versioning of data elements.
Associated data elements to a data dictionary.
Extract data elements from an imported data dictionary via the Dictionary Registry component.
Capability to locate and access registered data elements.
15
Backup
16
Schema RegistryNew Features for 2.0.0
New Metadata Elements Version, URI, Status
Version Control User specified via the Version element.
Web Directory Hierarchy Organize schema file locations based on the content of the Identifier and Version
elements.
Promotion Promote a specific version of a schema.
Schema Validation Validate well formed XML and log errors.
XML Instance Validation Validate an XML file against an internally referenced DTD or XSD.
Schema Removal and Metadata Modification
17
RequirementsOverview
Priorities Priority 1 – Requirements that are critical for basic
operations, confirmation of the WebGDS architecture, or infrastructure development.
Priority 2 - Requirements that further develop core WebGDS capabilities, increase robustness of the operating environment, and promote open interfaces to existing key software systems.
Priority 3 - Requirements that streamline operations, support more distributed operations, or extend capabilities for collaborative science planning and software development.
Priority 4 – Requirements that support advanced information modeling and collaboration, or better support a component-based software architecture.
18
RequirementsInterface
Priority 2 The UDDI interface shall provide local (from the same
computing host) access to the Registry.
The UDDI interface shall provide remote (from a different computing host) access to the Registry.
The software shall support an API compliant with the UDDI Version 2.04 Technical Specification.
Priority 4 The software shall support an API compliant with the UDDI
Version 3.0.1 Technical Specification.
19
RequirementsFunctional
Priority 1 For Service Entities, the software shall include the service interface
information as part of the metadata.
The software shall register Service interface information from an external WSDL specification.
The software shall include a URL reference to the external interface definition as part of the metadata for the Service Entity, if such an interface definition is supplied at time of registration. Note: It could be difficult to provide some of the above if we rely totally on
UDDI.
The software shall perform hot registration of Services, in which a “live” service registers its presence on the network at runtime. (Programmatic Only.)
The software shall perform hot de-registration of Services, in which a live service de-registers its presence on the network at runtime. (Programmatic Only.)
20
RequirementsFunctional (cont.)
Priority 2: The software shall support Services as Versioned Entities.
The software shall register Service interface information from a tModel.
The software shall support registration of Services through the UDDI API.
The software shall support de-registration of Services through the UDDI API.
The software shall support service lookup through the UDDI API.
The software shall support retrieval and modification of Service metadata through the UDDI API. Note: Is it necessary to require a Web Service API to the registry for
functions that are provided through UDDI?