Command-Line Options

The following table describes the command-line options available:

usage: search-core [options]


===========================================================
Command-line Options--------------Description---------------------------------------
===========================================================
 -a,--all                         Run all components of the Search Core
                                  [default]
 -c,--config-home <directories>   Specify the product class configuration home
                                  directory.Multiple directories can be
                                  specified to accompany multiple registries.
                                  (Default: $SEARCH_CORE_HOME/conf/pds/)
 -C,--clean-dirs                  Removal of all directories from previous
                                  Search Core execution output. These
                                  directories will still be backed up in the
                                  Search Home directory. (Default: True)
 -d,--debug                       Turn on developer debugger.
 -e,--extractor                   Execute component to extract data from
                                  registry
 -H,--search-home <directory>     Specify the Search Home directory. The tool
                                  will output the index files to this directory.
                                  When using the Search Service, this should be
                                  the  $SEARCH_SERVICE_HOME/pds directory
                                  (Default: $SEARCH_SERVICE_HOME/pds directory)
 -h,--help                        Display usage.
 -i,--solr-indexer                Execute component to generate a Solr Index
 -l,--log-file <file name>        Specify a log file name. Default is standard
                                  out.
 -m,--query-max <integer>         Specify the maximum number of registry values
                                  to be returned from query.(Default: 999999999)
 -P,--solr-post                   Execute component to post the index to the
                                  Search Service.
 -p,--properties-file <files>     Specify properties file containing Search
                                  Home, Registry URL, and search core
                                  configurations home directory. Multiple files
                                  can be specified.
 -r,--primary-registry <urls>     Specify the primary Registry Service
                                  instance(s) to query. Multiple registries can
                                  be specified. These registries will be used
                                  for all queries.
 -R,--secondary-registry <urls>   Specify secondary Registry Service instance(s)
                                  to query. Multiple registries can be
                                  specified. These registries will only be used
                                  after a query fails against all primary
                                  registries.
 -s,--service-url <url>           Specify the Search Service URL
                                  endpoint.Default:
                                  http://localhost:8080/search-service
 -v,--verbose <level>             Specify the severity level and above to
                                  include in the log: (0=Debug, 1=Info,
                                  2=Warning, 3=Error). Default is Info and above
                                  (level 1).
 -V,--version                     Display application version.
			  

Execute Search Core Tool

This section demonstrates execution of the tool using the command-line options. The examples below execute the tool via the batch/shell script.

The Search Core requires, at minimum, a Search Home directory be specified via command-line. The following is the format for the command:

% search-core -H <search-home> [options]
        

Search Home refers to the home directory of the Solr Core we want to generate an index for. With the common Search Service installation, Search Home will be /usr/local/search-service/pds (SEARCH_SERVICE_HOME/pds). The following demonstrates how to run the Search Core with a SEARCH_SERVICE_HOME=/usr/local/search-service, Primary Registry URL of http://localhost:8080/registry, an output log file of run.log, and config home of /usr/local/search-core/conf/pds/pds3 :

% search-core -H /usr/local/search-service/pds -r http://localhost:8080/registry \
-c /usr/local/search-core/conf/pds/pds3 -l run.log
        

By default, the command above runs all components of the Search Core software and produces Solr XML Documents from the Registry Service data. The Solr XML Documents are files formatted for addition to the Search Service index and will appear in the SEARCH_SERVICE_HOME/pds/index directory.

The following does not specify a configuration home directory so the default is set to SEARCH_CORE_HOME/conf/pds/pds3 and output the logs to standard out:

% search-core -H /usr/local/search-service/pds -r http://localhost:8080/registry
        

The Search Core Tool also provides the capability to run each component separately, however, they must be completed in the following order:

1. The following command will run the Registry Extractor component of the Search Core to generate temporary XML metadata files for each Registry context product type specified in the configurations. By default, the output appears in the directory /usr/local/search-service/pds/registry-data/<object-type>/:

   % search-core -e -H /usr/local/search-service/pds -r http://localhost:8080/registry
               

2. The following command will run the Solr Indexer component of the Search Core to parse the XML metadata files produced by the Registry Extractor, and generate Lucene Solr Documents located in /usr/local/search-service/pds/index :

   % search-core -i -H /usr/local/search-service/pds -r http://localhost:8080/registry
               

3. The following command will run the Solr Post component of the Search Core to use HTTP Post and HTTP Get to submit the Lucene Solr Documents to the Search Service Solr Index. The default Search Service URL is http://localhost:8080/search-service/ and assumes the Solr Documents are in /usr/local/search-service/pds/index :

   % search-core -P
               

The following command demonstrates how to test the Search Core with a SEARCH_SERVICE_HOME=/usr/local/search-service and only query 5 products for indexing (useful for testing purposes):

% search-core -H /usr/local/search-service/pds -r http://localhost:8080/registry \
-m 5
        

The following command demonstrates how to specify a primary registry and configuration home via a Search Core properties file:

% search-core -H /usr/local/search-service/pds \
-p /usr/local/search-core/conf/pds/pds3/core.properties
        

An example Search Core properties file looks like this:

search.core.primary-registry = http://localhost:8080/registry
search.core.config-home = /usr/local/search-core/conf/pds/pds3
        

The following command demonstrates how to specify multiple registries:

% search-core -H /usr/local/search-service/pds -r http://localhost:8080/registry \
http://localhost:8080/registry-psa
        

The following command demonstrates how to specify multiple Search Core property files:

% search-core -p /usr/local/search-core/conf/pds/pds3/core.properties \
/usr/local/search-core/conf/psa/pds3/core.properties
        

Defaults

Default configurations are provided for the following data types (assumes Search Core is installed at /usr/local/search-core, if not, update the file paths as needed):

Layout

<?xml version="1.0" encoding="UTF-8"?>
<product>
  <specification>
    <title>DataSet</title>
    <registryObjectType>Product_Data_Set_PDS3</registryObjectType>
    </specification>
  
  
  <indexFields>
    
    <field name="identifier" type="required">
      <registryPath>lid</registryPath>
      </field>
    <field name="title" type="required">
      <registryPath>name</registryPath>
      </field>
    <field name="description" type="required">
      <registryPath>data_set_terse_description</registryPath>
      </field>
    <field name="resLocation" type="required">
      <outputString>/ds-view/pds/viewDataset.jsp?dsid={data_set_id}</outputString>
      </field>
    <field name="objectType" type="string">
      <registryPath>objectType</registryPath>
      </field>
    <field name="agency_name" type="string" default="Unknown">
      <registryPath>node_ref.agency_ref.alternate_id</registryPath>
    </field>
  </indexFields>
</product>
	

Description of schema TBD.

Using Environment Variables

• Update $SEARCH_CORE_HOME/bin/env-vars with, at minimum, the following information:
  • SEARCH_HOME - The path for the home directory of local instance of search service.
  • SEARCH_SERVICE_URL - URL of the Search Service instance.
  • SOURCE - Source machine name where initial index was generated
  • SOURCE_USER - Username to connect source machine
  • SOURCE_PATH - Optional variable. Path on source machine to directory containing solr_index.xml.*. Defaults to $SEARCH_HOME/index.
• Run the ops-index script:

  % $SEARCH_CORE_HOME/ops-index
              

Using Command-Line Arguments

The ops-index script can also be run using command-line arguments in lieu of updating env-vars:

% $SEARCH_CORE_HOME/ops-index <SEARCH_HOME> <SEARCH_SERVICE_URL> \
<SOURCE> <SOURCE_USER> [<SOURCE_PATH>]
        

For example:

% ./ops-index /usr/local/search-service/pds http://localhost:8080/search-service/pds \
pdsbeta.jpl.nasa.gov root
        

Test Search Service

Once this script completes, the data should be available through the Search Service interface. Go to http://localhost:8080/search-service/pds/search/?q=*:* to verify data is available (modify domain and port as needed). See the Search Service - Operate page for more information on how to query data.

Error running Registry Extractor

This error arises when there is an error connecting with the Registry. The following are potential mitigation strategies:

• Verify the Registry URL specified is correct and accessible.
• Verify the Registry is populated with data by going to $REGISTRY_URL/report. See Registry Documentation for more information.

501 Method Not Implemented

This error occurs when using solr-post script and the HTTP POST method to ingest data into Solr. This usually means that the Search Service URL specified is either incorrect or attempting to access a port that is not open to the HTTP POST method. The following are potential mitigation strategies:

• Verify Search Service URL is correct by navigating to the page. The Solr Welcome screen should appear.
• Try changing the URL to access the localhost or an intranet-only accessible port (i.e. 8080). Often servers do not allow the HTTP POST method through port 80 when accessing Tomcat. For instance, if the Search Service URL used is http://my-host/search-service, try http://localhost:8080/search-service or http://my-host:8080/search-service (ports will differ according to Tomcat installation).

search-core: command not found

This error occurs when the system cannot find the search-core script in the PATH. See Installation Instructions for more information on adding the search-core to the PATH.