If your product catalog is stored in an Oracle database, you must configure the catalog to properly handle full text searching. There are two main steps involved in this configuration:

These steps are described in more detail in the sections that follow.

Setting Up the ConText Indexes

The SQL Repository has built-in support for Oracle’s ConText full text search engine, which processes queries and returns information based on the content or themes of text stored in a text column of an Oracle database. To enable full text searching on columns, you must create ConText indexes for the columns. See your Oracle documentation for information about how to do this.

Note: By default, an Oracle database rebuilds a full-text index after each commit. This behavior can cause a full deployment to hang indefinitely. To prevent this, you should configure ConText indexing to occur at regular intervals, using the following format:

CREATE INDEX schema-index-name ON schema-table (column)

If you are using the default product catalog, index these tables:

If you have imported the Pioneer Cycling product catalog into Oracle, index these tables:

If you have imported the Motorprise product catalog into Oracle, index these tables:

In each of these tables, create a ConText index on the DESCRIPTION, LONG_DESCRIPTION, and DISPLAY_NAME columns.

Configuring the Repository Components for Full Text Searching

To enable a SQL Repository to use full text searching in an Oracle database, the simulateTextSearchQueries property of the SQL Repository component must be set to false. Make sure this property is set to false for any SQL Repository component that connects to an Oracle database.

If you are using the default product catalog, the SQL Repository component for the catalog has the Nucleus address /atg/commerce/catalog/ProductCatalog.

If you have exported the Pioneer Cycling catalog into Oracle, there are three SQL Repository components for the catalog:

loading table of contents...