How to configure Oracle webcenter content search index?

GOOD DAY,,,

Content Server interfaces with a variety of indexing tools such as commercial search engines and databases. The indexing tool to use is chosen before installation based on the purpose and environment in which the Content Server instance performs.

Each indexing tool provides full-text indexing and metadata-only indexing. Full-text indexing means that every word in a file is indexed, not only its metadata. Full-text indexing takes longer than metadata indexing; however, it can return a more comprehensive result set. Metadata-only indexing means that every word in the stored content information is indexed. Metadata-only indexing is faster than full-text indexing. By default the Content Server instance is configured to use metadata-only indexing.

If your system is set up to provide indexing and searching capabilities with databases, your system integrator would have added one of the following lines in the IntradocDir/config/config.cfg file:

1. Metadata Searching Only:
SearchIndexerEngineName=DATABASE.METADATA
DATABASE.METADATA is supported in all databases supported by Oracle Fusion Middleware 11g Release 1 (11.1.1).

2. Full-text Searching:
SearchIndexerEngineName=ORACLETEXTSEARCH
ORACLETEXTSEARCH is supported in Oracle Database version 11.1.0.7 and newer.

3. Full-text Searching:
SearchIndexerEngineName=DATABASE.FULLTEXT
DATABASE.FULLTEXT is supported in SQL Server, and in Oracle Database (all supported versions).

----------------------------------------------------------------------------------------
How to setup on of the following search index?
- Metadata Search with All Databases
  To set up and use metadata-only searching and indexing in all databases:
  1. Ensure that Content Server is installed and configured to work with the 
      database.
  2. Add the following entry to the DomainHomeName/ucm/cs/config/config.cfg 
      file and save the file:
      SearchIndexerEngineName=DATABASE.METADATA
  3. Restart the Content Server instance.
  4. Rebuild the search index using the Repository Manager.

To access the Repository Manager, choose Administration, then Admin Applets, then Repository Manager.

Click Start in the Collection Rebuild Cycle part of the Indexer tab. The search index is entirely rebuilt, and the old index collection is replaced with a new index collection when the rebuild is successfully completed.

- Full-Text Search with SQL Server
  To set up and use full-text database searching and indexing in SQL Server and 
  in Oracle Database (all supported versions):
  1. Ensure that Content Server is installed and configured to work with the 
      database.
  2. Add the following entry to the DomainHomeName/ucm/cs/config/config.cfg         file and save the file:
      SearchIndexerEngineName=DATABASE.FULLTEXT
  3. Restart the Content Server instance.
  4. Rebuild the search index using the Repository Manager.

  To access the Repository Manager, choose Administration, then Admin 
  Applets, then Repository Manager.

  Click Start in the Collection Rebuild Cycle part of the Indexer tab. The search 
  index is entirely rebuilt, and the old index collection is replaced with a new 
  index collection when the rebuild is successfully completed.

- Full-Text Search with OracleTextSearch
  To set up and use full-text searching and indexing with OracleTextSearch, 
  which is supported in Oracle Database version 11.1.0.7 and newer:
  1. Ensure that Content Server is installed and configured to work with the   
      database.
  2. Add the following entry to the DomainHomeName/ucm/cs/config/config.cfg         file and save the file:
      SearchIndexerEngineName=DATABASE.ORACLETEXTSEARCH
  3. Restart the Content Server instance.
  4. Rebuild the search index using the Repository Manager.

  To access the Repository Manager, choose Administration, then Admin 
  Applets, then Repository Manager.

  Click Start in the Collection Rebuild Cycle part of the Indexer tab. The search 
  index is entirely rebuilt, and the old index collection is replaced with a new 
  index collection when the rebuild is successfully completed.

----------------------------------------------------------------------------------------

Optimizing Full Text Search
When using full text search in WebCenter Content, with either of the following two settings, the database uses Oracle Text Index to manage the data for searching.

SearchIndexerEngineName=OracleTextSearch
SearchIndexerEngineName=DATABASE.FULLTEXT

When using Oracle Text Index, the index on the database must be maintained in order to keep the disk from becoming fragmented. To avoid fragmentation, an optimize_index procedure should be run weekly. This procedure should be scheduled by the database administrator for WebCenter Content.

Determine the Active Index

To determine what is the active index on your WebCenter Content system, log in to the WebCenter Content system and select Administration, then Configuration for instance. On the Configuration page, for Oracle Text Search you will see something like the following information:

Search Engine::ORACLETEXTSEARCH
Index Engine Name:ORACLETEXTSEARCH
Active Index:ots2

For full text database, you will see something like the following information:

Search Engine::DATABASE.FULLTEXT
Index Engine Name:DATABASE.FULLTEXT
Active index:IdcColl1

The Active Index values tell you the table and index active in the database.

Enjoy,
Mohammad K. Faidi
 "Think Positive"