A deployed application includes test data that you can process
with baseline update scripts, baseline test data, and a baseline Forge
pipeline. Because this task describes test data, not production data, you use
the
load_baseline_test_data
script to simulate the data
extraction process (or to set the data readiness signal, in the case of an
application that uses a non-extract data source).
The
load_baseline_test_data
script loads the test data
stored in
<app dir>/test_data/baseline
and runs the
set_baseline_data_ready_flag
script which sets a
flag in the EAC indicating that data has been extracted and is ready for
baseline update processing.
Note
This script is not required in applications that use CAS to produce MDEX-compatible output.
When you are done familiarizing yourself with the data processing steps and the test data, see Running a baseline update with production data . Processing production data requires the following changes to an application' s configuration:
Replace the step to run
load_baseline_test_data
with a data extraction process that delivers production data into the<app dir>/test_data/baseline
directory. Delete thedata.txt
file from<app dir>/test_data/baseline
. This step is not necessary if your application does not use data extracts: for example, if your application retrieves data directly from a database via ODBC or JDBC or from a CAS crawl.Set the
baseline_data_ready
flag in the EAC. You set thebaseline_data_ready
flag by making a Web service call to the EAC or by running theset_baseline_data_ready_flag
script.
To run a baseline update with test data:
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.
Navigate to the
control
directory of deployed application.This is located under your application directory. For example:
C:\Endeca\apps\<app dir>\control
.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
.You should see 10 records.