The order and profile search configuration is comprised of the following components:
The
/atg/textsearch/indexing/IndexingOutputConfig
class, which specifies output options that define properties used during the indexing process. This component works with the following components:The
/atg/commerce/textsearch/OrderOutputConfig
component that configures the text search SQL and associated indices for ordersThe
/atg/userprofiling/textsearch/ProfileOutputConfig
component that configures the SQL and text search indices for profiles
Indexing Sessions – The sessions identify the database indexing configurations.
The
/atg/textsearch/repository/SearchRepository
that defines the search token and modification tables.
Full Text Search Components
The following primary classes and interfaces are used for order and profile searches.
Location and Name | Description |
---|---|
| This component sets the |
| Identifies the database that is installed, the column of the search table that contains search tokens, and other database specific configurations. It also is used to identify the
|
| Configures indexing functions that construct operations maps. Operation maps are built using resource keys that link messages and SQL statements together. |
| Provides the interface for all types of indexing:
|
| The necessary methods to build the SQL needed to perform bulk, incremental and live updates on a specific database type. Each database type has a properties file that describes the configuration and indexing operations for that specific database:
|
| Specified output options defining properties for indexing along with SQL to generate the necessary search tokens. |
Order Search Components
The following components are used when performing order searches. These components reside in the DCS.TextSearch
module.
Location and Name | Description |
---|---|
| Used to provide any additional information for each database vendor type. For example, if your database type requires specific numbering formats, etc. |
| Identifies the database SQL to perform order indexing. |
| Allows an administrator to re-index orders by creation date range. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Allows an administrator to re-index orders by ID. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Allows an administrator to re-index orders by the last modified date range. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Allows an administrator to re-index orders by the submitted date range. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Sets the |
| The The component class |
Profile Search Components
The following components are used when performing profile searches. These components reside in the DPS.TextSearch
module.
Location and Name | Description |
---|---|
| Identifies the repository item to listen to for changes, the RQL details that indicate an index can be performed and properties that, when modified, trigger an index. |
| Used to provide any additional information for each database. |
| Database SQL for profile searches. |
| Allows an administrator to re-index profiles by ID. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Allows an administrator to re-index profiles by the last modified date range. For information on performing manual indexing, refer to the Performing a Manual Re-Index section. |
| Sets the
|
| The The component class |