Each application that uses live statement retrieval requires an Indexer job to prepare the input data for dynamic viewing.
An Indexer job:
· Enables Web users to view statements using live retrieval.
· Let you index data fields such as customer name, amount due, and due date for display on a page listing historical statements available for viewing (sometimes called a "hit list"). (If you use the eaDirect sub-document indexing feature, the Indexer job automatically indexes all group fields defined in the parent group of a sub-account in the DDF to enable sub-documents to appear in a history list as well.)
· Enables you to generate email notifications (which you create in a separate job).
· Enables you to extract recurring table data from the input file and load it into a database table (which you load using a separate job and additional application support to use the data).
By scheduling the Indexer job to run automatically on a regular interval coinciding with the generation of your statement data file, you enable your latest statements to be routinely available for on-demand Web presentation.
The Indexer job extracts important data about your data file, called metadata, and places it in the database. When a user clicks a link to their statement, the browser uses index data in the database, the data input file, and the dynamic view files to present the user's statement.
The Indexer job also extracts data about any fields you choose to index, such as customer name, amount due, and due date, to the database. Indexing these fields makes them available for display in a historical list of bills (also called a "hit list").
The Indexer job consists of separate tasks that run sequentially. See Creating and Configuring an Indexer Job.