Siebel Search Administration Guide > Configuring Index Mappings for Oracle Secure Enterprise Search >

Configuring the Business Service User Property in ContentService When Indexing Business Component Pairs

For the Solution and Solution Admin business component pair, Solution is typically used for indexing and not Solution Admin where the runtime events are generated. If using the Solution business component for indexing, then you must create a name-value pair for Solution and Solution Admin in Siebel Tools in the Business Service User Prop under the Content Service business service as shown in the following procedure. These instructions apply to other business component pairs similar to Solution and Solution Admin (for example: Sales Tool and Admin Sales Tool business component pair).

To configure the Business Service User Prop in ContentService for indexing business component pairs

1. Log into Siebel Tools.
2. Go to the Fast Search Project, choose Tools and then Lock Project to lock the Fast Search Project.
3. Go to the Content Service business service.
4. Create a new Business Service User Prop with the following values:

   Field	Value
   Name	Solution Admin
   Value	Solution

5. In the Siebel application, go to the Administration - Runtime Events screen, then the Event Aliases view and verify that the run-time event alias fields for the Solution Admin buscomps are as shown in the following table. 

   Name	Object Type	Object Name	Event
   Solution - New	BusComp	Solution Admin	NewRecord
   Solution - Write	BusComp	Solution Admin	WriteRecord
   Solution - PreDelete	BusComp	Solution Admin	PreDeleteRecord

6. Go to the Administration - Runtime Events, then the Events view and verify that the event fields for the Solution Admin buscomps are as shown in the following table.

   Sequence	Name	Object Type	Object Name	Event	Action Set Name
   0	Solution - New	BusComp	Solution Admin	NewRecord	Update Index
   1	Solution - Write	BusComp	Solution Admin	WriteRecord	Update Index
   2	Solution - PreDelete	BusComp	Solution Admin	PreDeleteRecord	Update Index

   Note the following:

   • You can modify records only in the Admin business component but you can set the drilldown search results to a view that corresponds to a non-Admin business component.
   • Adding the new Business Service User Prop in the ContentService business service makes sure that:
     • The Solution business component will be indexed.
     • If records are modified in the Solution Admin business component, then the index will refresh and increment the changes.
     • The drilldown search results will be correct.
   • The ContentService business service contains an UpdateIndex method which is accessed by run time events when records are inserted, updated, or deleted from various business components. The UpdateIndex method inserts rows into the S_SRCH_CHG_TXN table, which contains a row for each change such as the Row Id val, Business Component Name, and the operation code (W-insert, W-update, or D-delete). If an insert, update, or delete operation is carried out on the Solution Admin business component, then the row inserted into the S_SRCH_CHG_TXN table is as follows: 'BUSCOMP_NAME'=Solution.
   • If indexing the Solution Admin (and not the Solution) business component, then it is not necessary to add the new Business Service User Prop mentioned in Step 4. Set the view name for that index category to the Solution Admin business component view. For example:

     - For the Solution Admin business component: Solution Administration View

     - For the Solution business component: All Solution List View

     If indexing the Solution Admin business component and if using the Solution business component as the view, then the search results will be incorrect.

     NOTE:  When new run-time events are added, you must synchronize the enterprise components and then restart the Siebel Server and Siebel Gateway services.