New Capabilities

The following capabilities are new for this release:

• Harvest Tool now includes support for validation of products prior to registration and can now be executed and run as a daemon process.
• Registry Service now includes a configuration endpoint allowing the configuration file generated from the data model to be processed in one action. Also added support for a registry package object to support batch operations. Also added support for MySQL as a backend database.

Modified Capabilities

The following capabilities have been modified for this release:

• Harvest Tool was modified for more robust handling of Association registrations as well as modified to keep pace with changes occurring in the PDS4 data model and the Registry Service interface.
• Registry Service was modified to move the core functionality to the Registry Core component to better satisfy JAR dependencies from other components. Also modified to include additional support for service registrations, general query improvements for registry objects and better alignment with the ebXML registry specification.
• Registry User Interface was modified to keep pace with the changes to the Registry Service interface.
• Security Service was modified to simplify the deployed solution by utilizing a single directory service to satisfy the requirements.
• Validate Tool was modified to include the latest set of generic schemas generated from the data model.

Corrected Capabilities

There were no corrected capabilities in this release.

EN Environment

This section details deployment to the EN operations environment. The following diagram details the deployment of the major components of this release and gives a very high-level view of the interfaces between the components and system resources:

If viewing this document in online form, click the image for a larger version.

The components depicted above serve as the operational deployment of this release for the Engineering Node. The main purpose of this deployment is for demonstration and testing purposes.

• Registry Service
  

  The Registry Service provides functionality for tracking, auditing, locating and maintaining artifacts within the system. For this release, the registry is populated with the PDS4 context products migrated from the PDS3 central catalog database. New for this release, the EN deployment will utilize MySQL as the backend database for the service. The web-based endpoint for this service is http://pdsops2.jpl.nasa.gov/registry-service/registry/.

• Registry User Interface
  

  The Registry User Interface provides a simple viewing capability of the contents of the associated Registry Service. It is intended to offer visual verification of successful registration of products. The web-based endpoint for this application is http://pdsops2.jpl.nasa.gov/registry-ui/.

• Report Service
  

  The Report Service provides the capability for capturing and reporting metrics. With this release and the previous release, this service is undergoing testing of configurations and features with a set of metrics from the Engineering Node and the Imaging Node at JPL. This service is not yet available to the user community. The web-based endpoint for this service is http://pdsops.jpl.nasa.gov/report-service/.

• Security Service
  

  The Security Service provides authentication and authorization functions for the system. This service is satisfied with an open source directory service. The directory service is populated with the PDS personnel list extracted from the PDS3 central catalog database. The application server hosting the Registry Service and Registry User Interface is configured to restrict access to certain URLs and to forward those requests to this service for authentication and authorization.

• Harvest Tool
  

  The Harvest Tool provides the means for registering products with the Registry Service. This tool reads a PDS4 product label, extracts specified metadata and registers the product with the registry. This tool allows the user to register a batch of products and generates a summary report.

Node Environment

This section details the deployment to a participating Node environment. The Nodes are asked to download, install and exercise the software that makes up this release. The following diagram details an example deployment of selected components:

If viewing this document in online form, click the image for a larger version.

The selected components depicted above are intended to aid the Nodes in their PDS3 to PDS4 conversion exercises. The following diagram depicts a normalized system flow, starting with schema design, continuing onto data product label generation and validation and finishing up with data product registration:

If viewing this document in online form, click the image for a larger version.

The system flow depicted above is described in more detail in the Data Provider's Handbook, albeit with a different flavor of this diagram. This diagram identifies where the system components come into play within the system flow. These components and the ones depicted in the deployment diagram, are described in more detail with respect to how the components can be utilized in the PDS3 to PDS4 conversion exercises with an eye towards testing these components for use in operations:

• Design Tool
  

  Although not depicted in the deployment diagram, the Design Tool is intended to aid users in the development of their data product label schemas. This release identifies two off-the-shelf products (Oxygen and Eclipse) that are available for this purpose. The provided documentation guides the user with respect to the download, installation and operation of each of these products.

• Validate Tool
  

  The Validate Tool comes pre-packaged with the latest version of the generic schemas generated from the data model. The tool allows the user to validate collections of products or single products against the associated generic schema. Specific schemas can be passed into the tool to enable a more detailed validation check. Although the Design Tools listed above provide a file-by-file validation capability, this tool allows the user to validate a batch of products and generates a summary report.

• Registry Service
  

  The Registry Service provides functionality for tracking, auditing, locating and maintaining artifacts within the system. Ultimately, all products (including PDS3 products) will be registered and tracked with the Registry Service. For this release, users are asked to install and configure a local instance of the service in order to exercise this procedure. Additionally if the user is participating in the PDS3 to PDS4 conversion exercises, the resulting products or collections of products can be registered with their local registry instance. For this release, it is assumed that the Node deployments will utilize Derby as the backend database for the service. If MySQL is preferred, a specific package can be provided upon request.

• Registry User Interface
  

  The Registry User Interface provides a simple viewing capability of the contents of the associated Registry Service. It is intended to offer visual verification of successful registration of products.

• Harvest Tool
  

  The Harvest Tool provides the means for registering products with the Registry Service. This tool reads a PDS4 product label, extracts specified metadata and registers the product with the registry. This tool functions as the Validate Tool does, in that it allows the user to register a batch of products and generates a summary report.