Endeca ITL development process

The Endeca ITL uses an instance configuration to process, tag, and locate data.

Creating an instance configuration is an iterative process. Endeca recommends that you first create a very simple instance configuration to test your data. After the simple configuration is working as you expect, you can make additional modifications, view your results, and make changes as necessary. Also, it is often useful to work on a subset of your data, for quicker turnaround of data processing, while you are developing your instance configuration.

At a high level, Endeca ITL development looks like this:

  1. Use Developer Studio to create an instance configuration. This defines how your data should be indexed and displayed. It includes Content Acquisition System components, such as a JDBC Adapter.
  2. Use an Endeca Deployment Template application to do the following:
    1. Run Forge, referencing the instance configuration, to process your source data into tagged Endeca records.
    2. Run Dgidx on the Forge output to create MDEX Engine indices from the tagged Endeca records.
    3. Run Dgraph to start a MDEX Engine and point it at the indices created by Dgidx.
  3. View the results and repeat these steps to make changes as necessary.