Running a partial update with production data

You run the partial_update script to process incremental changes in production data and distribute the resulting index files to one or more Dgraphs. Production data may come from any number of sources including data extracts, CAS crawls, or direct calls to a database through ODBC or JDBC.

For more information on partial updates, see the MDEX Engine Partial Updates Guide.

To run a partial update with production data:

  1. Ensure that the Endeca HTTP Service is running on each server in the deployment environment and that you have already deployed and initialized an application.

  2. Replace the default Forge pipeline (Developer Studio configuration files) in <app dir>/config/pipeline with the Developer Studio configuration files for your application. For details, see Replacing the Default Forge Pipeline.

  3. Provide the partial data (incremental data changes since the last baseline update). This step varies depending on the application requirements. It can include any of the following approaches:

  4. Start a command prompt (on Windows) or a shell (on UNIX).

  5. Navigate to the control directory of deployed application.

    This is located under your application directory. For example: C:\Endeca\apps\<app dir>\control.

  6. Set the partial_data_ready flag in the EAC by running the set_partial_data_ready_flag script.

  7. Run the partial_update script.

  8. Examine the indexed data in a Guided Search front-end application.

    For example, start a Web browser and open the JSP reference application at http://localhost:8006/endeca_jspref.

Copyright © Legal Notices