6Configuring Siebel Search for Oracle Secure Enterprise Search
Configuring Siebel Search for Oracle Secure Enterprise Search
This chapter describes how to configure search views and execution settings for Oracle Secure Enterprise Search. It includes the following topics:
This chapter assumes that you know how to use Siebel Tools. For more information, see Using Siebel Tools.
About Siebel Tools Configuration Tasks
Siebel Tools is a declarative software development tool that allows you to configure the underlying data and data presentation of your Siebel application without making changes to the program source code. Siebel Business Applications provide a core set of search object definitions that you can use as a basis for your tailored application. There are no source code modifications, nor modifications to schema. Siebel Tools uses the Siebel Runtime Repository configuration provided by Oracle.
Configuring the Indexing Mode for Index Status Monitoring
This topic covers configuration of the indexing mode for index status monitoring. The indexing mode is configured for FTP indexing by default. For information on index status monitoring, see Monitoring Index Status.
To configure the indexing mode for index status monitoring
Log in to Siebel Tools.
Query for the Search Index Batches BC business component.
Configure the Search Specification property using the following SQL conditions:
Set Search Specification to Index Mode<>’HTTP’ for FTP indexing.
Update the repository and deliver the update.
Process of Configuring Access Control for Search Results
User access to a particular view in the search results is determined by the sblvisibilityid index field mapping, and the account profile of the logged in user, such as Position ID or Account ID.
To configure access control for search results, perform the following tasks:
Configure sblvisibility Index Field Mappings
The sblvisibilityid index fields are mapped to business component access control fields, such as Position ID or Account ID. The sblvisibilityid index fields can also be mapped to custom access control fields. Multiple sblvisibilityid index fields can be defined for each business component. The sblvisibilityid index fields are configured in Aplication_Suite_OSES_Field-Mappings.xml. For more information on configuring index field mappings, see Configuring Index Mappings for Oracle Secure Enterprise Search. For more information on access control, see the access control topic in Siebel Security Guide.
This task is a step in the Process of Configuring Access Control for Search Results.
To configure sblvisibilityid index field mappings
Open the index mapping file Application_Suite_OSES_Field-Mappings.xml.The correct mapping file to use is determined as follows:
Use the file SSC_OSES_Field-Mappings.xml if you are using a Siebel application that operates across industries, such as Siebel Call Center, Siebel Sales or Siebel Marketing.
Use the file SIA_OSES_Field-Mappings.xml if you are using a Siebel industry application, such as Siebel Finance, Siebel Medical, or Siebel Pharma.
Set the bc-name attribute of each sblvisibilityid field to a business component access control field.
Save the changes to the mapping file.
Restart the Siebel server to populate the Search Index Settings and Available Fields views of the search administration UI with any new index fields.
Example of Mapping sblvisibilityid index fields
This extract provides an example of configuring the sblvisibilityid index field.
<field bc-name="Primary Organization Id" in-name="sblvisibilityid" ui-name="" on- name="" nv-name="" one2many="" is-id="N" id-rank="" type="na" /> <field bc-name="Contact Id" in-name="sblvisibilityid" ui-name="" on-name="" nv- name="" one2many="" is-id="N" id-rank="" type="na" /> <field bc-name="Owned By Id" in-name="sblvisibilityid" ui-name="" on-name="" nv- name="" one2many="" is-id="N" id-rank="" type="na" /> <field bc-name="Owner Position Id" in-name="sblvisibilityid" ui-name="" on-name="" nv-name="" one2many="" is-id="N" id-rank="" type="na" />
Configuring the Search Visibility Objects
This task covers configuring search visibility objects for determining access control for search result views.
This task is a step in the Process of Configuring Access Control for Search Results.
To configure the search visibility objects for Oracle Secure Enterprise Search
Navigate to the Administration - Search OSES screen, then the Search Visibility Settings view.
Add the Search Visibility objects with the values shown in the following table.
Visibility Object Description Business Object
This is the business object name.
Business Component
This is the business component name.
Input Field Name
This is a field name in the business component, such as Login Name, used to retrieve the access control values assigned to that user. The access control values retrieved can include fields such as PositionId, OrganizationId, or AccountId.
Configure the search visibility object fields with the values shown in the following table.
Visibility Object Field Description Field
The field name of the business component field used to determine access control, such as PositionId, OrganizationId, or AccountId.
Multi Valued
Set to Y for a multi valued field.
Parent Field
(Optional) The parent field name. It must be set if the parent field is to be included in determining access control.
Save the record.
Configuring Drill Down View Sequence for Search Results
This topic covers configuration of the sequence of drill down views for search results. User access to a particular view is determined by the sblvisibilityid index field mapping, and the account profile of the logged in user, such as Position ID or Account ID.
This task is a step in the Process of Configuring Access Control for Search Results.
To configure drill down view sequence for Oracle Secure Enterprise Search results
Navigate to Administration - Search OSES screen, then the Search Index Settings view.
In the Search Index Settings applet, select the Search Category for which drill down views are to be configured.
In the View Name column, select the drill down view.
Multiple views can be selected.
In the Seq Num column, enter a sequence number.
Administering Searchable Fields
The Searchable fields option on the Available Fields list applet determines which Search Category fields are displayed on the Search Center UI as searchable fields.
To administer searchable fields for Oracle Secure Enterprise Search
Navigate to the Administration - Search OSES screen, then the Search Index Settings view.
In the Search Index Settings applet, select the Search Category for which searchable fields are to be configured.
The fields for the selected Search Category are displayed in the Available Fields applet.
Select Y (searchable) or N (not searchable) in the Searchable column for each field.
Enter a Display Name if it does not already exist.
The Display Name appears on the searchable field text box on the Search Center UI.
Select Save Record on the Available Fields list.
Administering Field Weighting
The Search Index Settings view enables different weights to be defined for each searchable field in the search criteria, determining the field’s ranking in the search results. For example, in the Service Request Category, a weighting of 4 could be assigned to the Description field and a weighting of 2 could be assigned to the Abstract field, to rank the Description field higher in the search results, and thereby make the results more relevant. The search is executed first against the fields that have more weighting.
The Siebel Search numeric weights are mapped to the Oracle Secure Enterprise Search weight parameters in the file Search_Engine_Config.xml. Do not modify the contents of the file Search_Engine_Config.xml from the preconfigured settings.
To administer field weighting for Oracle Secure Enterprise Search
Navigate to Administration - Search OSES screen, then the Search Index Settings view.
In the Search Index Settings applet, select the Search Category for which field weightings are to be configured.
The fields for the selected Search Category are displayed in the Available Fields applet.
Enter a Weighting for each field in the Weighting factor column. The available weightings and corresponding rankings are described in the following table.
Numeric Weighting Ranking 4
Very high
3
High
2
Medium
1
Low
0
Very low
Select Save Record.
Administering Query-Time Clustering Configuration
Siebel Search uses the Oracle Secure Enterprise Search Cluster Nodes framework to dynamically generate query-time automated keywords. This task covers verifying the Oracle Secure Enterprise Search cluster settings that are required for Siebel Search automated keywords.
It is recommended to assign the “keywords" value to the in-name attribute of a descriptive business component field, if automated keywords are required. For information on defining index attributes, see Defining Index Attributes.
For more information on cluster configuration and search attributes, see Oracle Secure Enterprise Search Administrator's Guide.
The Siebel Search automated keywords framework is mapped to the Oracle Secure Enterprise Search cluster configuration framework in the file Search_Engine_Config.xml. Do not modify the contents of the file Search_Engine_Config.xml from the preconfigured settings.
To verify Oracle Secure Enterprise Search query-time clustering configuration
Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Global Settings screen, and then the Clustering Configuration view.
Confirm that Enable Clustering is selected under Cluster Tree Configuration.
Confirm that the Topic cluster tree has been created under Cluster Trees with the following values:
Field Value Tree Name
Topic
Cluster Type
Topic
Attributes
Keywords, Title, eqsnippet, eqtopphrases
Status
Enabled
Configuring the Language LOV for Siebel Search Preferences
This topic describes how to create and configure the Language list of values for the Search Preferences applet. The examples in this topic use English, German, and Korean.
To configure the Language LOV for Siebel Search
Navigate to the Administration - Data screen, and then the List of Values view.
Create the LOV header record, using the information in the following table.
Type Display Value Language Independent Code LOV_TYPE
SEARCH_LANGUAGE
SEARCH_LANGUAGE
Select the Active option.
Select the Translate option.
Set the Replication Level to All.
Define the list of languages to display in the Language LOV, using the information in the following table.
Type Display Value Language Independent Code Language Name Order SEARCH_LANGUAGE
English
English
English-American
1
SEARCH_LANGUAGE
German
German
English-American
2
SEARCH_LANGUAGE
Korean
Korean
English-American
3
Select the Active option.
Select the Translate option.
Set the Replication Level to All.