When you install Commerce Service Center using Oracle Commerce Platform Configuration and Installation Manager (CIM), the TextSearch modules are added to your environment. These modules install the components that allow you to search for orders and profiles using standard Full Text Searching (FTS) SQL queries. FTS is performed using standard search tokens within the supported databases: Oracle, MSSQL and DB2. Note that MySQL database searches are also supported, but not for production environments.

A tokens table and index for both orders and profiles is created in the database and referenced as repository items in the appropriate Search repository. By default, a listener is attached to each repository and is triggered when an update, delete, or insert operation occurs. The listener updates the modified table to indicate that during the next scheduled incremental execution, the updated order or profile indexing tokens will be regenerated and the token will be updated. As a result, the index reflects the new tokens. This can occur in real-time, be performed manually or as a bulk index.

When performing a bulk load, or baseline indexing operation, a staging table is populated with the search tokens. These tokens are then merged into the token table and indexed, allowing the indexing process to occur without disrupting agent searches.

Note: This search process is not used for ticket, product or catalog searches.