Overview

Direct Indexing enables information stored during a transaction flow into the search appliance (for example, Google or Apache Lucene) to be associated directly with a lookup in the main database. It does not look into the iWay Audit Manager.

To use this service, you must specify context information that is sufficient to perform an inquiry so as to recover the indexed data. An example might be storing the keys associated with updated or inserted relational information. The actual lookup can be performed later by an iWay-provided service such as the relational access component, or by a service developed specifically for your purpose.

Caution: Under this indexing option, if the database containing the data changes, the index points to either a missing record or a record that may have changed between the time of the index and time of the search.

Unlike Audit Message Indexing, which relies on the Audit Manager, Direct Indexing is not performed automatically. Instead, you install a service into a process flow that organizes the index update based on information in the flow. Later the lookup is performed by a service that can use the saved index information to reconstitute the data.

It is possible to use both Audit Message Indexing and Direct Indexing in the same application.

The following advantages are associated with using the Direct Index service:

Several disadvantages are also associated with use of the Direct Index service:

The document and context reaching the Direct Index component is indexed and the context is stored.


iWay Software