The order and profile search configuration is comprised of the following components:

Full Text Search Components

The following primary classes and interfaces are used for order and profile searches.

Location and Name

Description

/atg/textsearch/client/
  SearchClientService

This component sets the LiveIndexingSupported
and LiveSearchingSupported properties. It also delegates all the calls to the defined database client and indexing session.

/atg/textsearch/client/
  CSCDB2Client.properties
,
  CSCMSSQLClient.properties
,
  CSCMySQLClient.properties
,
  CSCOracleClient.properties

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 databaseToTextLanguage property, which identifies the databases used:

oracle=ORACLE_CONTEXT
db2=DB2_TEXT_EXT
msSQL=MSSQL_TSQL
MySQL=MYSQL_TEXT_SQL

/atg/textsearch/indexing/
  session/DatabaseIndexing
  Session

Configures indexing functions that construct operations maps. Operation maps are built using resource keys that link messages and SQL statements together.

/atg/textsearch/indexing/
  session/IndexingSession

Provides the interface for all types of indexing:

baseline – Wipes all data and reloads it.
manual – Allows definition of specified re-indexing criteria.
increment – Performs scheduled live updates of items.

/atg/textsearch/indexing/
DB2IndexingSessionImpl
,
MSSQLIndexingSessionImpl
,
MySQLIndexingSessionImpl
,
OracleIndexingSessionImpl

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:

DB2IndexingSession
MSSQLIndexingSession
MySQLIndexingSession
OracleIndexingSession

/atg/textsearch/indexing/
  IndexingOutputConfig

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

OrderIndexingAdditional
  Information

Used to provide any additional information for each database vendor type. For example, if your database type requires specific numbering formats, etc.

OrderIndexingSQL

Identifies the database SQL to perform order indexing.

OrderManualIndexRequestByCreation
  DateRange

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.

OrderManualIndexRequestById

Allows an administrator to re-index orders by ID. For information on performing manual indexing, refer to the Performing a Manual Re-Index section.

OrderManualIndexRequestByLas
  tModifiedDateRange

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.

OrderManualIndexRequestBySubmitted
  DateRange

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.

OrderModifiedListenerConfig

Sets the repositoryItemName to listen to for changes, and the modifiableProperties that trigger a re-index. By default, changes to the lastModifiedDate property trigger a re-index.

OrderOutputConfig

The OrderOutputConfig configures data and components needed for performing indexing of order items.

The component class IndexingOutputConfig creates the AdminServlet, which drives the UI in the Dynamo Server Admin. The UI is used to perform indexing operations, as described earlier in this table.

Profile Search Components

The following components are used when performing profile searches. These components reside in the DPS.TextSearch module.

Location and Name

Description

ProfileContactInfoModifiedListener
  Config

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.

ProfileIndexingAdditionalInformation

Used to provide any additional information for each database.

ProfileIndexingSQL

Database SQL for profile searches.

ProfileManualIndexinRequestByID

Allows an administrator to re-index profiles by ID. For information on performing manual indexing, refer to the Performing a Manual Re-Index section.

ProfileManualIndexRequestByLast
  ModifiedDateRange

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.

ProfileModifiedLIstenerConfig

Sets the repositoryItemName to listen to for changes, and the modifiableProperties that trigger a re-index. By default, changes to the following properties trigger a re-index:

login
firstName
lastName
email
shippingAddress
billingAddress
secondaryAddresses
creditCards

ProfileOutputConfig

The ProfileOutputConfig configures data and components needed for performing indexing of profile items.

The component class IndexingOutputConfig creates the AdminServlet, which drives the UI in the Dynamo Server Admin. The UI is used to perform indexing operations, as described earlier in this table.


Copyright © 1997, 2014 Oracle and/or its affiliates. All rights reserved. Legal Notices