Siebel Search Administration Guide > Administering Siebel Search Index Settings >

About Indexing Search Objects

The indexing process is comprised of a number of tasks on the Siebel side and on the Oracle Secure Enterprise Search side. When indexing initiates, the Status Code changes to a null value in the Siebel Search Index Settings view, and a set of SearchDataProcessor jobs are created. The SearchDataProcessor jobs create temporary XML feed files under the XML Indexable Data Location. For each batch of rows to be indexed, a separate job is created. The index operation starts the relevant Oracle Secure Enterprise Search Schedule. Oracle Secure Enterprise Search uses a crawler to collect data from the XML feed files for each data source, and to generate the index. This index is used for searching data sources.

The SearchDataProcessor status can be monitored in the Jobs view of the Administration - Server Management screen. When complete, each SearchDataProcessor job updates the status code for the search index to Indexed, and the Status Details reflect the number of indexed rows. The index operation is complete on the Siebel side when all of the SearchDataProcessor jobs have a status of success or error. The status details for the search index reflect the number of rows successfully transferred to feed files. If the number of indexed rows is lower than the number of records in the business component, it is recommended that the SearchDataProcessor logs are checked for errors on the jobs that have not executed successfully.

The Oracle Secure Enterprise Search schedule status can be monitored in the Crawler Schedules table of the Schedules tab on the Oracle Secure Enterprise Search administration UI. For more information on indexing status, select the log file icon in the Crawler Schedules table.

Siebel Search provides the following indexing operations:

• Full Indexing. The full indexing operation can be executed on all search objects defined in the XML mapping file, or on a specific business component or connector. This operation is available for thin and thick clients.
• Refresh Indexing. Refreshes the index with any create, update or delete operations which have been executed on the data source since the last index operation. This operation is available for thin and thick clients.
• Incremental Indexing. Updates the index, at preconfigured intervals, with any create, update or delete operations which have been executed on the data source since the last index operation. This operation is available for thin clients.

This topic contains the following sub-topics:

• Indexing Search Objects
• Refreshing the Index
• Enabling Incremental Indexing