OperationThis document describes how to operate the Harvest-PDAP Tool software. The following topics can be found in this document: Note: The command-line examples in this section have been broken into multiple lines for readability. The commands should be reassembled into a single line prior to execution. Tool ExecutionHarvest-PDAP Tool can be executed in various ways. This section describes how to run the tool, as well as its behaviors and caveats. Command-Line OptionsThe following table describes the command-line options available:
Execute Harvest-PDAP ToolThe Harvest-PDAP Tool operates with a policy fie to register product metadata. Details on host to create this policy file can be found in the Policy File section. This section demonstrates some of the ways that the tool can be executed:
Registering Products from a Configured Source The following command demonstrates how to register products to a non-secured registry instance from a source specified in the policy file and to direct the output to a log file: % harvest-pdap -c policy.xml -l output.log Registering Products to a Secured Registry Instance The following command demonstrates the previous scenario but registering products to a secured registry instance: % harvest-pdap -c policy.xml -u {username} -p {password} -k {keystorePassword} \ -l output.log Policy FileThe Harvest-PDAP policy file is an XML-based configuration file that the tool uses to find products and register their metadata. This section details how to setup the policy file to do PDS product registration. The following is an example of a policy file to perform registration of ESA/PSA products: <policy> <pdsRegistry url="http://localhost:8080/registry"> <packageName>Harvest-PDAP Package</packageName> <packageDescription> This is a run that includes registration of products from the PSA. </packageDescription> </pdsRegistry> <pdapServices> <!-- Currently, the only valid value for 'agency' is 'esa'. --> <pdapService agency="esa" url="http://psa.esac.esa.int:8000"/> </pdapServices> <productMetadata> <!-- All context product metadata definitions are captured in the global policy. --> </productMetadata> <resourceMetadata> <title>The Planetary Science Archive METADATA Query Service</title> <type>System.Browse</type> <slot name="resource_name"> <value>The Planetary Science Archive METADATA Query Service</value> </slot> <slot name="resource_description"> <value>The Planetary Science Archive METADATA Query Service</value> </slot> </resourceMetadata> </policy> The policy file is made up of the following complex type elements: pdsRegistry, pdapServices, productMetadata and resourceMetadata. pdsRegistry Each time the Harvest Tool runs, it creates a package in the registry to group the product registrations together. Specify this element to give a registry package a name and/or description. A required attribute of the pdsRegistry element named url, must be populated to specify the endpoint of the Registry Service. The following table describes the child elements that are allowed:
pdapServices Specify this element to indicate the PDAP service endpoint for accessing product metadata for registration with the Registry Service. The following table describes the child elements that are allowed:
productMetadata Specify this element to include additional metadata in the form of registry slots for every product. The following table describes the child elements that are allowed:
staticMetadata Specify this element to include static metadata for every product. The following table describes the child elements that are allowed:
dynamicMetadata Specify this element to include dynamic metadata for every product. The following table describes the child elements that are allowed:
resourceMetadata Specify this element to include metadata for every resource product. A corresponding resource product is registered for every data set product registered. The following table describes the child elements that are allowed:
Report FormatThis section describes the contents of the Harvest-PDAP Tool report. At this time, the tool only outputs a series of log messages. The log will report the success or failure of a discovered product attempting to be registered. A log consists of a severity level, file name, and a message. The following is an example of some of the log messages that can be expected from the Harvest Tool: PDS Harvest-PDAP Tool Log Version Version 0.1.1 Time Sun, Jun 09 2013 at 01:40:00 PM Severity Level INFO PDAP Target(s) [http://psa.esac.esa.int:8000] Registry Location http://localhost:8080/registry-psa Registry Package Name Harvest-PDAP Package Registration Package GUID urn:uuid:c554631c-a353-4b0f-9643-4796a921d523 INFO: Connecting to PDAP Service: http://psa.esac.esa.int:8000 ** AdaptiveByteStore default memory limit = 986M * 0.125 = 123M ** ** malloc 2778306 bytes ** INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Processing dataset. INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Additional metadata needed. Getting dataset catalog file. INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Retrieving VOLDESC.CAT to look up the data set catalog file name. INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Retrieving catalog file: DATASET.CAT SUCCESS: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Successfully ingested product: \ urn:nasa:pds:...AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0::1.0 INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Product guid is urn:uuid:e7bba690-c946-4a80-b911-2a3a47fdde14 SUCCESS: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Successfully ingested product: \ urn:nasa:pds:...AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0::1.0 INFO: [AIRUB-C-PHOTOCAM-2-EDR-HALLEY-1986-V1.0] \ Product guid is urn:uuid:5147a7a6-dced-4402-8dd7-0b401c56b1f3 ... Summary: 2712 dataset(s) processed 64 error(s), 7290 warning(s) 2712 of 2712 datasets registered. 2712 of 2712 resources registered. End of Log
|