It is possible to manually re-index orders or profiles. By default, you can re-index using a date range or an ID.

The /atg/commerce/search/OrderOutputConfig contains the manualIndexRequests property that enumerates the types of queries used to manually re-index orders. The default queries perform indexing by creation date, last modified date, submitted date, or ID:

manualIndexRequests=\
  /atg/commerce/search/OrderManualIndexRequestByCreationDateRange,\
  /atg/commerce/search/OrderManualIndexRequestByLastModifiedDateRange,\
  /atg/commerce/search/OrderManualIndexRequestBySubmittedDateRange,\
  /atg/commerce/search/OrderManualIndexRequestById

The /atg/userprofiling/search/ProfileOutputConfig contains the manualIndexRequests property. By default, queries perform indexing for profiles by last modification date or by ID:

manualIndexRequests=\
  /atg/userprofiling/search/ProfilesManualIndexRequestById,\
  /atg/userprofiling/search/
     ProfileManualIndexRequestByLastModifiedDateRange

Each of the ManualIndexRequests defines an RQL query that sets the criteria for the indexing request.

To manually re-index:

To review the orders being indexed, enable the loggingDebug property in /atg/commerce/
search/OrderLiveDocumentSubmitter
. To review the profiles being indexed, enable the loggingDebug property in /atg/userprofiling/search/ProfileLiveDocumentSubmitter.

Customizing Manual Indexing

By default, manual re-indexing searches for date ranges and IDs. However, you can customize the re-indexing process. To do this, define an RQL query, or write a custom class that implements the atg.search.routing.ManualIndexReqest interface referenced by the atg.repository.search.indexing.IndexingOutputConfig class. For information on writing RQL queries, refer to the ATG Repository Guide. For information on extending and working with the IndexingOutputConfig class, refer to the ATG Search Administration Guide.


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