New Capabilities

The following capabilities are new for this release:

• Search Service is new for this release and includes the PDS search protocol request handler and generation of the search index from a populated Registry Service.
• Registry User Interface includes new support for browsing associations, packages, services, events, schemes, and classification nodes.

Modified Capabilities

The following capabilities have been modified for this release:

• Registry Service was modified to include schema creation scripts for the target database and now requires a database population step during configuration.
• Harvest Tool was modified to represent LIDVID-based references as slots instead of associations as well as modified to keep pace with changes occurring in the PDS4 data model and the Registry Service interface.
• Validate Tool was modified to include the latest set of generic schemas generated from the data model.

Corrected Capabilities

The following capabilities were corrected in this release:

• Registry User Interface was modified to correct scrolling issues and window behavior.
• Harvest Tool was modified to correct an issue where the directory path was not determined correctly for document products.

Java Runtime Environment

The custom software contained in this release was developed using Java and will run on any platform with a supported Java Runtime Environment (JRE). The software was specifically developed under Java version 1.6 and has only been tested with this version. The following commands test the local Java installation in a UNIX-based environment:

% which java
/usr/bin/java

% java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode)
        

The first command above checks whether the java executable is in the environment's path and the second command reports the version. If Java is not installed or the version is not at least 1.6, Java will need to be downloaded and installed in the current environment. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, the Java software can be downloaded from the Oracle Java Download page. The software package of choice is the Java Standard Edition (SE) 6, either the JDK or the JRE package. The JDK package is not necessary to run the software but could be useful if development and compilation of Java software will also occur in the current environment.

Java Application Server

The other main system requirement pertains to providing a Java application server for hosting certain components (Registry Service and Registry User Interface). The suggested application server for this release is Apache Tomcat with a minimal version of 6.0.20 through version 7.0.X. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, the Apache Tomcat software can be downloaded from the Apache Tomcat page. Choose the version to download (6.0 or 7.0) from the menu on the left. Details on downloading, installing and configuring an Apache Tomcat server can be found in the Tomcat Deployment document.

Engineering Node Environment

This section details deployment to the Engineering Node 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 following diagram depicts the EN system flow, starting with central catalog migration, data product registration and finishing up with search index generation:

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.

• 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.

• Search Service
  

  The Search Service provides functionality for accepting queries from data consumers for registered products and includes functionality for retrieving search results. This component acts as the interface to the Registry Service for the data consumer.

• 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.

• 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.

  An issue was discovered post-delivery where the application is requiring the keystore password to be provided to the application even when accessing an unsecured instance of the Registry Service. The workaround for this issue is to remove the reference to the pds.security.keystore system property from the launch script (e.g., Harvest, Harvest.bat).

Discipline Node Environment

This section details the deployment to a participating Discipline 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.

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
  

  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.

• Generate Tool
  

  The Generate Tool is intended to aid users in the generation of their data product labels. This tool was developed by the Imaging Node at JPL and provides a command-line interface for generating PDS4 Labels from either a PDS3 Label or a PDS-specific DOM object.

• 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.

• 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 allows the user to register a batch of products and generates a summary report.

  An issue was discovered post-delivery where the application is requiring the keystore password to be provided to the application even when accessing an unsecured instance of the Registry Service. The workaround for this issue is to remove the reference to the pds.security.keystore system property from the launch script (e.g., Harvest, Harvest.bat).

An installation exercise was not specified for this release but each Node is welcome to download, install and exercise the above components in their environment. The Installation document for the desired component(s) is a good place to get started.