|
Siebel Search Administration Guide > Siebel Search Configuration Using Siebel Tools > The Search Index >
The Search Index Object
The Search Index object is a logical name for a group of search engine specific entities. For example, the Search Index for Hummingbird will be a Hummingbird index table. Thus, the search index, Solution will map to an index table called FUL_SOLN. Rules and Assumptions
- It is a good practice to only index master data (also called referential data), and not transactional data as transactional data change very often and your index may not reflect the current data.
- Search engines are most powerful when used to search for text and keywords in voluminous documents and attachments in the database. The perfect candidates for Search are Literature, Solution, Product, FAQ, and Resolution documents. Siebel 7 includes preconfigured search indices, such as Product Literature, SmartScripts, Service Requests, and so on.
- Search supports Access Control and Organization visibility rules. The buscomp that you plan to index should support one of these rules. It is also acceptable to index buscomp that have no visibility rules enforced. In such cases, all buscomp records will be visible to all users. For further information on Access Control, see Visibility Control.
Properties
Table 8 lists the properties for the Search Index object.
Table 8. Search Index Object Properties
|
|
|
|
Name |
Required |
Logical name for the search index. |
|
Index Buscomp |
Optional |
Buscomp that the index maps to. This field can be null if it is based on an external directory. |
|
DB Table |
Optional |
Flag indicates if the object maps to a database table or not. If the search index is based on an external file system, this field should not be checked. The default case is checked. |
|
|
