Siebel Search Administration Guide > Configuring Siebel Search Using Siebel Tools >

Restricting the Indexing of Records

The SearchServer database text reader (dbtr) permits partial table selection for improved performance. The text reader's table definition (which is defined in the Database Interface Definition or DID file) can include a WHERE clause to specify which rows are included in the selection. Using instructions found in the DID file, the database text reader generates SQL statements to acquire column data from databases and convert it to text for SearchServer. To constrain the scope of data that is indexed, you can define a Search Filter Field in Siebel Tools, for the Search Index that you want to constrain. The Search Filter Field object needs to have the Field Type set to Constraint and the constraint specification entered into the Column Name field of the object. These fields cannot be used in filter search specifications through a filter search specification, or exposed on the UI as filter fields.

CAUTION:  The string you specify as the constraint is not checked for syntax. It is added to the Hummingbird DID file as is. For more information, see the Hummingbird SearchServer documentation.

For example, to index only Literature items that are marked external, you add a Search Filter Field in Tools under Literature Search Index -> "FUL_LIT" Search Table as shown in Table 21.

Given the preceding filter field definition, the FUL_LIT.DID file generated by Siebel Search will have this extra line:

RESTRICT SIEBEL."S_LIT"."INT_FLG" = 'N'

The BC Field you select for a constraint filter field can be any field in the business component including joined fields. For example, to index only the Product that belongs to the Caterpillar organization, you add a Search Filter Field under Product Search Index -> "FUL_PROD" Search Table as shown in Table 22.

The DID file generated will include the appropriate join clauses as well as the restrict clause:

RESTRICT SIEBEL."S_ORG_EXT"."NAME" = 'Caterpillar'