Test your setup
To test your deployment we will ingest a few datasets in your new registry.
This operation is done in 2 steps:
- convert pds records into registry records, with command harvest
- push the registry record to the server, with command registry-manager
harvest
To run this command we need a configuration file to reference the data source.
Edit the example file provided in harvest-3.3.2/conf/examples/registry.xml
Update the following section with the path of the test dataset in the package, you may use your own dataset, that is even better:
<!-- Specify the top level directory / bundle for Harvest to crawl for products to register --> <directories> <path>{absolute path to the package}/test/dph_example_archive/</path> <fileFilter> <include>*.xml</include> </fileFilter> </directories>
See details on the harvest configuration on operate harvest
We now need an output directory where the registry records will be created, for example, on unix, ~/tmp
At last, run the harvest command
harvest -c <path to the package>/harvest-3.3.2/conf/examples/minimal.xml -o ~/tmp
registry-manager
To push the newly created registry record to the server, simply run (~/tmp is the path where the input records created in the previous step are):
registry-manager load-data -file ~/tmp
query the registry
Open in your browser: http://localhost:9200/registry/_search?q=*
reset your registry
To reset your registry and other common operations, see documentation on registry manager
Next steps
Your registry application works. You can now operate your registry with your own datasets