Setting Up Siebel Search with Oracle Secure Enterprise Search

This chapter covers setting up Siebel Search with Oracle Secure Enterprise Search. All tasks in this chapter are required for Siebel Search and Oracle Secure Enterprise Search integration. This chapter includes the following topics:

About Installing Siebel Search

Siebel Search uses Oracle Secure Enterprise Search as the default search engine. This topic covers installation of Oracle Secure Enterprise Search, and installation of Siebel components related to Search.

Upgrading from Siebel Search Version 7.x

Any custom search objects which were defined in Siebel Search Version 7.x must be redefined in the Application_Suite_OSES_Field-Mappings.xml file. For more information, see Configuring Index Mappings for Oracle Secure Enterprise Search.

Installing Server Components for Siebel Search

Siebel Search requires the installation of the Siebel Enterprise Server, including the Siebel Server and the Siebel Gateway, and Oracle Secure Enterprise Search. Oracle Secure Enterprise Search and the Siebel Enterprise Server must be deployed on separate, dedicated servers.

Note: The system requirements and supported platform certifications are available from the Certifications tab on My Oracle Support. For information about Certifications, see article 1492194.1 (Article ID) on My Oracle Support.

The recommended installation and configuration sequence is as follows:

Install the Siebel Enterprise Server
Install the Oracle Secure Enterprise Search Server
Configure Siebel Search on the Oracle Secure Enterprise Search server and Siebel servers.

For information on installing server components, see Installing Oracle Secure Enterprise Search.

Oracle Secure Enterprise Search Pre-Installation Tasks

Refer to the Pre-Installation Tasks topic in the Oracle Secure Enterprise Search Installation and Upgrade Guide. This guide is provided on Oracle Technology Network.

Installing Oracle Secure Enterprise Search

This topic covers Oracle Secure Enterprise Search installation and additional installation steps required for Siebel Search. Capture the Search and Administration URLs from the Oracle Secure Enterprise Search install wizard during the Oracle Secure Enterprise Search installation process, as these will be required for post-installation verification. The Administration Password will also be required when configuring the Search Engine Settings in the Siebel Search administration view. The examples in this guide use Siebel1 as the Oracle Secure Enterprise Search Administration Password. Make sure that the file RSS_Crawler_Configuration.xml is accessible to the Oracle Secure Enterprise Search engine and that the file Application_Suite_OSES_Field-Mappings.xml is accessible to the Siebel Server.

To install Oracle Secure Enterprise Search

Complete the tasks in the Installation Tasks section of the Oracle Secure Enterprise Search Installation and Upgrade Guide. Use the installation values in the following table.

Field	Value
Search Server Name	Set the value to SES.
Administrative Password	Set the value to siebel1.
HTTP Port	The default port can be used.
Destination Path	Set the value to D:\oracle\ses\ses version\OH.
Data Storage Location	Set the value to D:\oracle\ses\ses version\oradata.

Create the Siebel Search Center Config directory under the Siebel File System on the Oracle Secure Enterprise Search Server:
- On Windows create the Config directory at D:\fs\SSC\Config\.
- On UNIX create the Config directory at /export/home/fs/SSC/Config/.
Copy the file RSS_Crawler_Configuration.xml from the Siebel Server to the SSC Config directory on the Oracle Secure Enterprise Search Server:
- On Windows copy the crawler file from siebsrvr\bin\ on the Siebel Server to D:\fs\SSC\Config/ on the Oracle Secure Enterprise Search Server.
- On UNIX copy the crawler file from siebsrvr/lib/ on the Siebel Server to /export/home/fs/SSC/Config/ on the Oracle Secure Enterprise Search Server.
Set the permissions for fs\SSC\Config\ to Full Control for Everyone.

Creating the Siebel Search Center Directory Structure on the Siebel Server

This topic covers creating the Siebel Search Center directory structure on the Siebel Server for storing the XML feed files and feed status files which are generated at runtime.

This topic includes the following tasks:

Creating the Siebel Search Center Directory on Windows

This topic covers creating the Siebel Search Center directory structure on the Siebel Server for a Windows environment. The D:\fs\SSC directory on the Siebel Server will also be used as the FTP home directory.

To create the Siebel Search Center directory structure on Windows

Create a directory for storing the XML feed files on the Siebel Server, for example, D:\fs\SSC\xmlidata.
The XML feed files are generated at runtime and temporarily stored in the fs\SSC\xmlidata folder. The feed files are automatically deleted once indexing completes.
Create a directory for storing the XML feed status files on the Siebel Server, for example, D:\fs\SSC\xmlidata\err.
The XML feed status files are generated at run time, and indicate the error or success status of the crawl operation.
Create a directory for storing the XML field mapping file on the Siebel Server, for example, D:\fs\SSC\Config.
Copy the file Application_Suite_OSES_Field-Mappings.xml from the installation directory at siebsrvr\bin\ to the config directory at D:\fs\SSC\Config\.
- Copy 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.
- Copy the file SIA_OSES_Field-Mappings.xml if you are using a Siebel industry application, such as Siebel Finance, Siebel Medical, or Siebel Pharma.
Copy the file Search_Engine_Config.xml from the installation directory to the config directory at D:\fs\SSC\Config\.

Note: Do not modify the contents of the file Search_Engine_Config.xml from the preconfigured settings.
Set the permissions for D:\fs\ to Full Control for Everyone.

Creating the Siebel Search Center Directory on UNIX

This topic covers creating the Siebel Search Center directory structure on the Siebel Server for a UNIX environment.

To create the Siebel Search Center directory structure on UNIX

Create a directory for storing the XML feed files on the Siebel Server, for example, /export/home/fs/SSC/xmlidata.
The XML feed files are generated at runtime and temporarily stored in the fs/SSC/xmlidata folder. The feed files are automatically deleted once indexing completes.
Create a directory for storing the XML feed status files on the Siebel Server, for example,
/export/home/fs/SSC/xmlidata/err.
The XML feed status files are generated at runtime, and indicate the error or success status of the crawl operation.
Create a directory for storing the XML field mapping file on the Siebel Server, for example:
/export/home/fs/SSC/Config.
Copy the file Application_Suite_OSES_Field-Mappings.xml from the installation directory at siebsrvr/lib/ to the config directory at /export/home/fs/SSC/Config/.
- Copy 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.
- Copy the file SIA_OSES_Field-Mappings.xml if you are using a Siebel industry application, such as Siebel Finance, Siebel Medical, or Siebel Pharma.
Copy the file Search_Engine_Config.xml from the installation directory to the config directory at /export/home/fs/SSC/Config/.

Note: Do not modify the contents of the file Search_Engine_Config.xml from the preconfigured settings.
Set the permissions for /export/home/fs/ to Full Control for Everyone.

Configuring EAIFileTransportFolder Access for Siebel Search

The EAIFileTransportFolders parameter must be configured to grant write access to specific folders within the Siebel file system that are required for Siebel Search. For information on configuring the EAIFileTransportFolders parameter, see Transports and Interfaces: Siebel Enterprise Application Integration.

Administering FTP Indexing

Siebel supports FTP connections with Oracle Secure Enterprise Search. This topic includes information about the following:

Note: From Siebel Innovation Pack 2016 onwards, URL credentials are disabled. As a result, HTTP indexing is not supported by Oracle Secure Enterprise Search. Only FTP indexing is supported.

Enabling FTP Indexing

Siebel Search provides an FTP option for indexing. The FTP indexing method uses a type of feed. The feed is defined as the collection of documents in the data repository for the index operation. FTP indexing uses the following feed type:

FTP indexing using directory feed. All feeds are placed in a directory, and this directory is the input to the connector. The directory feed location is configured in the file RSS_Crawler_Configuration.xml. Directory feed is useful when the data feeds are available in a single directory. The number of documents in each directory must be less than 10,000.

To enable FTP indexing for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Engine Settings view.
Configure the Send Index Feed Via HTTP settings as follows:
- Set the value to False to turn on FTP indexing.
  The default value is False.

For information on configuring search engine settings for FTP indexing, see Configuring Search Engine Settings for Oracle Secure Enterprise Search.

Configuring the FTP Server for FTP Indexing

Siebel Search uses an Oracle Secure Enterprise Search XML framework for submitting records for indexing in the form of XML feeds. The pre-indexed XML feed files are stored on an FTP server for Oracle Secure Enterprise Search access. The FTP server and Siebel Server must be colocated on the same server—all examples in this guide assume that the FTP server and Siebel Server are colocated. Accessing the feeds over FTP is a crawl time operation requiring administrative privileges. The FTP location is not accessed at search time, therefore there is no end user access to the FTP location.

This topic includes the following tasks:

Configuring the Search FTP Server on Windows

This topic covers configuring the FTP server on Windows, so that Oracle Secure Enterprise Search can access the Siebel Search XML feed files for crawling and indexing operations. The FTP home directory is set to the Siebel Search Center directory. For more information on setting up the FTP server, see your operating system documentation on Internet Information Services.

To configure the Search FTP server on Windows

From the Start menu choose Control Panel, Add or Remove Programs, and then the Add/Remove Windows Components option.
From the Windows Components list choose Application Server, Details, Internet Information Services (IIS), and then Details.
Select File Transfer Protocol (FTP) Service and click OK.
Click Next on Windows Components Wizard.
This will install the IIS and FTP services.
From the Start menu choose All Programs, Administrative Tools, and then Internet Information Services.
The Internet Information Services (IIS) console is launched.
Right-click on Default FTP Site and select Properties.
Select the FTP Site tab.
Enter Siebel Search Center FTP Site in the Description field.
Select the Home Directory tab.
Select the option Directory Located on this Computer.
Set the Home Directory Local Path to D:\fs\SSC.
The paths in the RSS Crawler file are configured relative to your FTP Home Directory.
Select the options Read, Write and Log visits.
Set Directory Listing Style to UNIX.

Configuring the Search FTP Server on UNIX

This topic covers configuring the FTP server on UNIX, so that Oracle Secure Enterprise Search can access the Siebel Search XML feed files for crawling and indexing operations.

To configure the Search FTP server on UNIX

Enable the FTP service on the Siebel Server.
Set the FTP home directory to /export/home/fs/SSC.
The paths in the RSS Crawler file are configured relative to your FTP home directory.

Configuring the RSS Crawler for FTP Indexing

Oracle Secure Enterprise Search crawls Siebel data in RSS feed format. The file RSS_Crawler_Configuration.xml is located on the Oracle Secure Enterprise Search Server and is used to configure the Oracle Secure Enterprise Search Crawler. The path to this configuration file must be specified when creating the Siebel Source in Oracle Secure format. The fileRSS_Crawler_Configuration.xml is located on the Oracle Secure Enterprise Search Server and is used to configure the Oracle Secure Enterprise Search Crawler. The path to this configuration file must be specified when creating the Siebel Source in Oracle Secure Enterprise Search. Siebel Search uses the directory feed type for indexing over FTP.

To configure the RSS Crawler for FTP indexing on Oracle Secure Enterprise Search Server

Open the file RSS_Crawler_Configuration.xml on the Oracle Secure Enterprise Search server in an XML or text editor:
- On Windows this file is located at D:\fs\SSC\Config\.
- On UNIX this file is located at /export/home/fs/SSC/Config/.

Complete the mandatory fields in the Siebel Customer configuration section - these fields are described in the following table.

Field	Description	Mandatory
feedLocation	The xmlidata\(XML-based indexable data) directory location on the FTP Server, where the XML-based feed files are stored for indexing. This value is specified relative to your FTP Home Directory, for example, if your FTP Home Directory is set to D:\fs\SSC and the xmlidata folder is at D:\fs\SSC\xmlidata, then set the feedLocation value to ftp://Siebel_Server_IP_Address/xmlidata. On Windows this value is specified in the format: ftp://Siebel_Server_IP_Address/xmlidata On UNIX this value is specified in the format: ftp://Siebel_Server_IP_Address/xmlidata Note: FTP must be included in the feedLocation value.	Yes
feedType	Type of feed file. Set the value to directoryFeed.	Yes
errorFileLocation	Location on the FTP Server where the FileName.err and FileName.suc files will be stored. This value is specified relative to your FTP Home Directory On Windows and UNIX the value is specified in the format: /xmlidata/err Note: FTP is not included in the errorFileLocation value.	No
securityType	Type of security to be enabled. Set the value to attributeBased.	Yes
sourceName	Name of the Siebel data source. Set the value to buscomp.	Yes
securityAttribute	Attribute in the feed files that provides the security information. Set the value to sblvisibilityid. Multiple access control mappings for sblvisibilityid can be passed to SES at index-time.	Yes
Grant	This attribute governs the Siebel user’s access to a set of result records. Set the value to True. The Siebel user will have access to the records with Visibility IDs set up for that user. The Visibility ID for each record is set in the XML feed that is generated by Siebel Search for Oracle Secure Enterprise Search to crawl. The set of Visibility IDs accessible to a user is retrieved by Oracle Secure Enterprise Search from Siebel CRM through the Siebel Web service, when the user logs in to Oracle Secure Enterprise Search.	No

Example of Configuring the RSS Crawler for FTP Indexing

This extract provides an example of configuring the file RSS_Crawler_Configuration.xml for FTP indexing.

<feedLocation>ftp://Siebel_Server_IP_Address/xmlidata</feedLocation> 
<feedType>directoryFeed</feedType> 
<errorFileLocation>/xmlidata/err</errorFileLocation> 
<securityType>attributeBased</securityType> 
<sourceName>buscomp</sourceName> 
<securityAttribute name="sblvisibilityid" grant="true"/>

Creating Server Repeating Jobs for Incremental Indexing

This topic covers creating server repeating jobs to enable incremental indexing. Incremental indexing enables the index to automatically update, at preconfigured intervals, with create, update and delete operations that have been executed on the data source since the last index update. It provides a more efficient method of updating the index without the overhead of a full Refresh Index operation. Incremental indexing is supported for thin clients. Refresh indexing must be used on thick clients.

When importing a batch of data, it is recommended that incremental indexing is turned off and a one time Index All operation is performed. Incremental indexing is turned off by deactivating the Update Index action set on the Runtime Events Action Set view. For more information on server component repeating jobs, see Siebel System Administration Guide.

Note: This task is required only for thin client deployments.

To create server repeating jobs for incremental indexing

Navigate to the Administration - Server Configuration screen, then the Job Templates view.
In the Jobs Templates list, click New.
Set the Name to Search Incremental Indexer.
Set the Short Name to SII.
In the Component/Job field, click the list and select the SearchDataProcessor server component.

In the Job Parameters list, add the following two parameters for the component job.

Name	Value
Business Service Name	Search Data Processor
Method Name	CreateIncrementalIndex

Configuring Field Mapping Settings

The settings enclosed in percentages in the field mapping file must be configured for integration between Siebel Search and Oracle Secure Enterprise Search. There are two mapping files and the correct one to use is 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.

To configure field mapping settings

Open the file Application_Suite_OSES_Field-Mappings.xml, located on the Siebel Server, in an XML or text editor.
- On Windows this file is located at D:\fs\SSC\Config\.
- On UNIX this file is located at /export/home/fs/SSC/Config/.

Configure all fields enclosed in the percentage symbol. The fields are described in the following table.

Field	Description
%webserver%	Set the value to the `ApplicationInterfaceHost:HTTPSPort_Number` of the Siebel Web server.
%objmgr%	This is the application object manager. Set the value to the application that is running. For example, `CallCenter/<lang> or Fins/<lang>`.
%lang%	Set the value to the language for which the Siebel application is configured. For example, the value for English is enu.
%hostName%	Set the value to the IP address of the Siebel host.

Administering Siebel Server Component Groups

This procedure enables the Enterprise Application Integration (alias EAI) and Search Processing server component groups. These two component groups must be enabled for all indexing operations. The Search Data Processor component processes Search data and builds the index. Once the Search server is set up and the indexes have been defined, the components must be synchronized. For more information on Siebel Server component groups, see Siebel System Administration Guide.

To administer Siebel Server component groups

Navigate to the Administration - Server Configuration screen, and then the Component Groups view.
Query on the Search Processing component group.
On the Component Groups applet, click the Enable button.
Query on the Enterprise Application Integration component group.
On the Component Groups applet, click the Enable button.
Restart the Siebel Server.
Navigate to Administration - Server Management screen, then the Servers and Component Groups view.
Make sure that the Search Processing and Enterprise Application Integration component groups have state Online.
Navigate to Administration - Server Configuration screen, then the Enterprises and Synchronize view.
Query on the Search Data Processor component in the list applet.
Click Synchronize.
Restart the Siebel Server.

Administering Workflow Management Components

This topic covers enabling the Workflow Management Server components. All Workflow Management components must be enabled for incremental and refresh indexing. For more information on Siebel Server component groups, see Siebel System Administration Guide.

To administer Workflow Management Components for incremental and refresh indexing

Navigate to Administration - Server Configuration screen, and then the Component Groups view.
Query on the Workflow Management component group.
On the Component Groups applet, click the Enable button.
Restart the Siebel Server.
Navigate to Administration - Server Management screen, then the Enterprises, Servers and Components view.
Query on each of the following Workflow Management components and verify that the State of each is Online:
- Workflow Action Agent
- Workflow Monitor Agent
- Workflow Process Batch Manager
- Workflow Process Manager
- Workflow Recovery Manager
- Generate Triggers
Click the Startup button for any Workflow Management component that is not online.

Enabling Search Security Web Service

This topic covers enabling the SearchSecurityService inbound Web service for integration with Oracle Secure Enterprise Search. This Web service uses SOAP header authentication.

To enable security for search inbound Web services

Navigate to Administration - Web Services screen, and then the Inbound Web Services view.
Click on the Query button on the Inbound Web Services applet.
Enter SearchSecurityService in the Name field and click Go.
On the Address field of the Service Ports applet, substitute the address variables in the following URL:
```
https://<ApplicationInterfaceHost>:<httpsPort>/siebel/app/<ApplicationName>/<language>
```
1. Substitute <ApplicationInterfaceHost> with the Siebel Application Interface hostname.
2. Substitute <httpsPort> with the port number where the application interface is configured to run.
3. Substitute <ApplicationName> with the name of the Siebel application. For example: callcenter.
4. Substitute <language> with the Siebel application language. For example: enu.
On the Service Ports applet select Menu, and then the Save Record menu item.
Click the Clear Cache button on the Inbound Web Services applet.

Activating the Search Engine for Oracle Secure Enterprise Search

A search engine is activated by selecting the Default Flag option in the Search Engine Settings view. Only one search engine can be activated at any time. Make sure that the Default Flag option is selected for just one search engine.

To activate the search engine for Oracle Secure Enterprise Search

Navigate to Administration - Search OSES screen, then the Search Engine Settings view.
In the Search Engines applet, select the Default Flag option for Oracle Secure Enterprise Search.

Configuring Search Engine Settings for Oracle Secure Enterprise Search

This topic covers configuration of the Oracle Secure Enterprise Search and Siebel Search integration fields in the Search Engine Settings view of the Siebel Search Administration UI.

To configure the search engine settings for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Engine Settings view.
Change the version number of the OSES search engine from 10.1.8 to 11.2.2.2.0.
The version number for the OSES search engine is 10.1.8 by default but if you are using Oracle Secure Enterprise Search version 11.2.2.2, then you must update the version number of the OSES search engine to 11.2.2.2.0.

In the Driver Parameters applet, complete the search engine settings described in the following table as required.

Setting	Description
Admin API Namespace	The Namespace for the OracleSearchAdminService Web service. This Oracle Secure Enterprise Search Web service invokes the Oracle Secure Enterprise Search Schedule that crawls and indexes the Siebel business component data. For Oracle Secure Enterprise Search version 11.2.2.2, set the value to: `http://search.oracle.com/Admin` For Oracle Secure Enterprise Search version 11.1.2 or earlier, set the value to: `http://search.oracle.com/AdminService/2006-09-15`
Admin API Webserver Address	The Web server address for the Oracle Secure Enterprise Search OracleSearchAdminService Web service. For Oracle Secure Enterprise Search version 11.2.2.2, set the value to: `http://SES_Server:Port/search/api/admin/AdminService` For Oracle Secure Enterprise Search version 11.1.2 or earlier, set the value to: `http://SES_Server:Port/search/ws/admin/SearchAdmin`
Advanced Batching And Indexing	This setting is used to turn the asynchronous indexing and index monitoring features on or off: Set the value to True to enable the asynchronous indexing and index monitoring features. Set the value to False to disable the asynchronous indexing and index monitoring features. The default value is True.
Batch Split Size	The number of business component records in a batch. The Object Manager query performance, search engine footprint size, and Siebel Server specification are used in determining optimum Batch Split Size. Set the value to the following: For FTP indexing, set the value to less than or equal to 4500.
Batch Submit Size	The number of records submitted at a time for indexing. The Object Manager query performance, search engine footprint size, and Siebel Server specification are used in determining optimum Batch Submit Size. Set the value to the following: For FTP indexing, set the value to less than or equal to 1500.
Dupmarked	This functionality is not supported. Set the value to false. Note: This setting is case sensitive.
Dupremoved	This is a Boolean setting to enable or disable the removal of duplicates from the result set. Set the value to true to remove duplicates from the results. Note: This setting is case sensitive.
Feed Access Password	This is the password for accessing the RSS feeds that Oracle Secure Enterprise Search will crawl. For FTP indexing, set the value to the password used to log in to the FTP server where the XML feed files are generated. Feed Access User ID is set in the Search Connector Settings view.
Filename	The path to the Application_Suite _OSES_Field-Mappings.xml file on the Siebel Server. 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. This file is located on the Siebel Server in the \fs\SSC\Config directory.
Login URL	The administration URL for Oracle Secure Enterprise Search. The URL format is: http://SES_Server:HTTP_Port/search/admin/control/ login.jsp
Namespace	The name of the Oracle Secure Enterprise Search Web service. Set the value to OracleSearchService.
OSESAutoStartSchedule	This setting is used to turn automatic Oracle Secure Enterprise Search scheduling on or off. Set the value to True to enable automatic scheduling of the index operation in Oracle Secure Enterprise Search. The schedule is automatically started once Siebel Search generates the feed files. Set the value to False to disable automatic scheduling of the index operation. This option requires manually starting the indexing schedule in Oracle Secure Enterprise Search. The default value is True.
Password	This is the Oracle Secure Enterprise Search Administration User Password. Example passwords for Oracle Secure Enterprise Search follow: For version 11.2.2.2: Welcome1. For version 11.1.2 or earlier: siebel1. For more information, see Installing Oracle Secure Enterprise Search.
Recordcount	This setting configures the inclusion of an estimate in the result for the number of records in the result set. Set the value to True.
Remote Admin Support	This setting is used to turn the remote administration feature for the Oracle Secure Enterprise Search Connector on or off: Set the value to True to enable the remote administration feature. Set the value to False to disable the remote administration feature. The default value is True.
Schedule Name	This is used for starting the Oracle Secure Enterprise Search Schedule remotely. This field takes the same value as the Business Component Connector Library Name, and is set to buscomp. This value is case sensitive.
Schedule URL	Oracle Secure Enterprise Search schedule URL for starting the crawler remotely using the Oracle Secure Enterprise Search HTTP API. Set the value to http://SES_Server:HTTP_Port/search/admin/schedules/ schedules.jsp The Oracle Secure Enterprise Search Server can be specified using either the DNS name or IP address.
Search Engine Config Filename	The path to the search engine configuration file on the Siebel server. The value is set to: \\SearchServer\fs\SSC\config\Search_Engine_Config.xml Note that \fs refers to the FTP path.
Send Index Feed Via HTTP	This setting is used to turn FTP indexing on or off: Set the value to False to turn on FTP indexing. Set the value to True to turn on HTTP indexing. The default value is False.
SES Username	This is the unique User ID which Siebel Search uses to access the application for the search operation. This value corresponds to the Entity Name which is set when creating the Oracle Secure Enterprise Search Federation Trusted Entities. The examples in this guide use sblsesuser as the Oracle Secure Enterprise Search Username/Entity Name. For more information, see Verifying Oracle Secure Enterprise Search Federated Trusted Entities and Siebel Identity Plugin Manager.
SES Password	This is the password which Siebel Search uses to access the application for the search operation. This value corresponds to the Entity Password which is set when creating the Oracle Secure Enterprise Search Federation Trusted Entities. Examples for the Oracle Secure Enterprise Search Password/Entity Password follow: For Oracle Secure Enterprise Search version 11.2.2.2: Welcome1. For Oracle Secure Enterprise Search version 11.1.2 or earlier: Welcome. For more information, see Verifying Oracle Secure Enterprise Search Federated Trusted Entities and Siebel Identity Plugin Manager.
Shared Search UNC Location	This setting is specific to FTP indexing. The value is set to the Siebel Search Center shared FTP UNC location where Siebel Search decompresses the Siebel File System files. It is the parent directory of the Xmlidata directory. The address format on Windows is: \\IP address\fs\SSC The address format on UNIX is: /export/home/qa/fs/SSC Note: Adding a slash (/) or backslash (\) after SSC will create an error.
SSC FTP Location	This setting is specific to FTP indexing. The value is set to the FTP Server shared search center location from where Oracle Secure Enterprise Search reads the Siebel File System files. The FTP Home directory is configured on the FTP server. The value must be set to: ftp://Siebel_Server_IP_Address/
Strong Password Encryption Rules Enforced	This setting is used to turn the enhanced security features on or off: Set the value to True to enable the enhanced security features. The default value is True. Set the value to False to disable the enhanced security features. The default value is True.
Username	This is the Oracle Secure Enterprise Search Administration User ID. For Oracle Secure Enterprise Search version 11.2.2.2, the default value is searchsys. For Oracle Secure Enterprise Search version 11.1.2 or earlier, the default value is eqsys.
Visibility Support	This setting is used to turn enhanced access control functionality on or off: Set the value to True to enable the enhanced access control feature. Set the value to False to disable the enhanced access control feature. The default value is True.
Web Service Endpoint Address	This is the Siebel authentication and validation Web service endpoint. Set the value to: http://<SiebelWebServer.com>:<Port>/siebel/app/<ApplicationName>/<language> This value can be copied from where it was configured in the Inbound Web Services view of the iebel administration UI, removing the username and password from the URL. For more nformation, see Enabling Search Security Web Service.
Web Service Endpoint Password	This is the Siebel administrative User Password. This value is used by Oracle Secure Enterprise Search when connecting to the Siebel server and authenticating the connection.
Web Service Endpoint Username	This is the Siebel administrative User ID. This value is used by Oracle Secure Enterprise Search when connecting to the Siebel server and authenticating the connection.
WebServer Address	URL for the Oracle Search Service. The address format is: http://SES_Server:HTTP_Port/search/query/OracleSearch
XML Indexable Data Location	This setting is specific to FTP indexing. Set the value to the Siebel Search Center shared FTP location for storing data for the RSS crawler to access and index. The path format on Windows is: \\IP address\fs\SSC\xmlidata\ The path format on UNIX is: /home/export/fs/SSC/xmlidata/

Select Save Record on the list applet.

Note: The Siebel Server must be restarted every time a change is made to Search Engine Settings configuration.

Configuring Oracle Secure Enterprise Search Engine for the Search Results View

After installing Oracle Secure Enterprise Search, activating the search engine and configuring the search engine settings for Oracle Secure Enterprise Search, you must configure the Oracle Secure Enterprise Search engine for the Search Results View as follows:

Enable or disable Oracle Secure Enterprise Search so that it appears or is hidden in the Search Results view.
Configure the position of the Oracle Secure Enterprise Search tab in the Search Results view.
Enable or disable the auto suggest feature for the Oracle Secure Enterprise Search engine.

Note: This procedure applies to both new customers setting up Oracle Secure Enterprise Search for the first time and customers upgrading to the latest release of Oracle Secure Enterprise Search.

Search results are displayed in the Search Results view. In the Search Results view, when you drill down on a record to see the detailed record information, the search results are retained. This mode of display is known as Results Retention Mode. Preview and Attach features are available in Results Retention Mode.

To configure the Oracle Search Enterprise Search engine for the Search Results view

Navigate to the Administration - Search screen, then the Search Engine Settings view.

In the Search Engines applet, add a new record for OSES (if not already present) with the values shown in the following table.

Field	Description	Value
Engine Name	Name of the search engine, which appears as the tab display name in the Search Results view.	OSES
Search Adapter	Name of the search adapter, which maps to the search engine configured.	OSES Search Adapter Service
Sequence Number	Indicates the position where the <SearchEngineName> tab will appear in the Search Results view. For example, 1 indicates the first position and so on.	3
Active	Indicates whether to show (Y) or hide (N) the <SearchEngineName> tab in the Search Results view.	Y
Auto Suggest Supported	Indicates whether to enable (Y) or disable (N) the auto suggest feature for search.	Y

Configuring the Default Search Definition

The list of Categories displayed in the Search Index Settings view is determined by the default Search Definition in the Search Definition view. Each Siebel application is mapped to a Search Definition. Before indexing business components or configuring Search Categories in the Search Index Settings view for a particular application, the corresponding Search Definition must be set up as the default Definition in the Search Definition view. For more information on Search Definition and Siebel application mappings, see Application and Search Definition Mappings.

To configure the default search definition for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Definition view.
Select the Search Definition that is to be set as the default.
Select the Default Flg option.

Clearing Attachments From the Shared Search UNC Location

Attachments are crawled by Oracle Secure Enterprise Search. In order for Oracle Secure Enterprise Search to remove attachments from the temporary Shared Search UNC Location, the Delete Linked Documents search engine setting must be set to True in the source configuration. Delete Linked Documents is set to False by default.

To clear attachments from the Shared Search UNC Location

Navigate to the Administration - Search OSES screen, then the Search Engine Settings view.
In the Search Engines applet, select the OSES search engine.
In the Driver Parameters applet, change the default value for Delete Linked Documents from False to True.

Configuring User Authentication for Search Queries

This topic describes configuring end user authentication for search queries. To require user login for secure content, configure the Login Requirement value in Oracle Secure Enterprise Search.

To configure user authentication for search queries

Log in to the Oracle Secure Enterprise Search Administration application.
Navigate to the Global Settings screen, then the Query Configuration view.
Set the Login Requirement value to one of the following options:
- Require login for secure content only. This is the default. Users can search public content without logging in, but they must log in to retrieve secure content.
- Require login for public and secure content. Users must first log in to retrieve any content.

Activating Search Run-Time Events

Activating preconfigured Search run-time events is required to enable incremental indexing and refresh indexing. This task is required for both thick and thin clients. Search runtime events monitor create, update and delete events executed on Search Objects in the data repository. The Action Sets create records in the transaction table (S_SRCH_CHG_TXN) and trigger the Search Content business service method UpdateIndex.

To activate the Search run-time events

Navigate to the Administration - Runtime Events screen, then the Action Sets view.
Query on the Update Index Action Set.
Select the Active and Enable Export options to activate the Update Index run-time events.

Siebel Search Web Services

Siebel Search provides a set of Business Service APIs, which can be implemented as Web services through the Siebel Web services framework. The following Search Web services are provided:

SearchExternalService. This Web service can be used as a Search Front End Web service, to facilitate searches on the data stored in the Siebel application, from a non-Siebel Web application.
SearchSolutionService. This Web service can be used to search for solutions based on user inputs, and retrieve a solution as a search result.
RetrieveAttachmentService. This Web service has one standard QueryPage method to retrieve attachment documents.
ProductSearchService. Business Service (Search Product Service) for searching product business components, and performing eligibility checks.

For more information on Siebel Search Web services, see Siebel CRM Web Services Reference.

Process of Setting Up the Business Component Source and Connector

The business component source and connector must be set up to integrate Siebel Search and Oracle Secure Enterprise Search.

To set up the business component source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Configuring the Siebel Business Component Connector

This topic covers configuration of the business component connector settings for integration with Oracle Secure Enterprise Search.

This task is a step in Process of Setting Up the Business Component Source and Connector.

To configure the Siebel business component connector settings for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.

Complete the business component connector fields described in the following table as required. Values are case-sensitive.

Field	Value
Name	This field is preconfigured and takes the value Bus Comp. Do not change the preconfigured value.
Library Name	This field is preconfigured and takes the value buscomp. Do not change the preconfigured value.
Engine Name	This field is preconfigured and takes the value OSES. Do not change the preconfigured value.
Configuration URL	This is the file URL of the crawler configuration file. Set the value to the location of the RSS_Crawler_Configuration.xml file on the Oracle Secure Enterprise Search server. On Windows set the value to: file://localhost/fs/SSC/config /RSS_Crawler_Configuration.xml On UNIX set the value to: file://localhost//export/home/fs/SSC/config/ RSS_Crawler_Configuration.xml
Feed Access User ID	This is the User ID for accessing the RSS feeds that Oracle Secure Enterprise Search will crawl. For FTP indexing, set the value to the User ID used to log into the FTP server where the XML feed files are generated. If the server has user accounts registered in multiple domains, then use the format Domain\UserID. Feed Access Password is set in the Search Engine Settings view.
Scratch Directory	Create a Temp/ local directory on the Oracle Secure Enterprise Search server where status files can be temporarily written.
Type	Set the value to buscomp. This value is case sensitive.
className	This field is preconfigured and takes the value oracle.search.plugin.security.auth.siebel.SiebelAuthManager. Do not change the preconfigured value.
jarFile	This field is preconfigured and takes the following value: /oracleapplications/Siebel8Crawler.jar Do not change the preconfigured value.

Activating the Siebel Identity Plugin Manager for Oracle Secure Enterprise Search

The Oracle Secure Enterprise Search Federation Trusted Entities and Siebel Identity Plugin Manager are activated remotely when the Siebel SES adapter connects to Oracle Secure Enterprise Search.

This task is a step in Process of Setting Up the Business Component Source and Connector.

To activate the Siebel Identity Plugin Manager for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Engine Settings view.
Select the CSSOSESAdapter search engine library, and click Connect.
The Connected flag in the Search Engine Settings view is set to true.

Verifying Oracle Secure Enterprise Search Federated Trusted Entities and Siebel Identity Plugin Manager

This task covers verification of the Federation Trusted Entities settings, and configuration and activation of the Identity Plugin Manager. It is recommended to execute this task if the status of the CSSOSESAdapter search engine library does not update correctly after the Connect operation, or if the error message “Error in RemoteAdmin Adapter" is displayed.

This task is a step in Process of Setting Up the Business Component Source and Connector.

To verify Federated Trusted Entities and the Siebel Plugin Manager

Log in to the Oracle Secure Enterprise Search Administration application.
Navigate to the Global Settings screen, then the Federation Trusted Entities view.

Verify the fields described in the following table.

Field	Description
Key	Siebel Search uses this value to access the application for the search operation. Verify that the value is set to `sblsesuser`. This value corresponds to the Oracle Secure Enterprise Search Username configured in the Siebel Search Engine Settings view. This value also corresponds to the Entity Name in the Key column of the Oracle Secure Enterprise Search Trusted Entities table. For more information, see Configuring Search Engine Settings for Oracle Secure Enterprise Search.
Description	Verify that the description is set to Trusted Siebel-Oracle Secure Enterprise Search user.
Authentication	Verify that the value is set to Password.
Authentication Attribute	This field is not used for Siebel Search integration and is empty.

Navigate to the Global Settings screen, then the Identity Management Setup view.
Verify that the oracle.search.plugin.security.identity.siebel.SiebelIdentityPluginMgr Identity Plugin Manager is listed as an active plug-in.

Verify the Authorization Manager plugin fields described in the following table.

Field	Description
Siebel 8 authentication web service endpoint	This is the Siebel authentication Web service endpoint. Verify that the value is set to the following: http://<webserver>/eai_<language>/ start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&WSS OAP=1 For more information, see Enabling Search Security Web Service.
Siebel 8 validation web service endpoint	This is the Siebel user validation Web service endpoint. Verify that the value is set to the following: http://<webserver>/eai_<language>/ start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&WSS OAP=1 For more information, see Enabling Search Security Web Service.
User ID	This is the Siebel administrative user ID.
Password	This is the Siebel administrative password.

Deploying the Business Component Source

This topic covers remote administration of the Oracle Secure Enterprise Search Connector. This task configures the Oracle Secure Enterprise Search business component Source and Source Group, and creates the Oracle Secure Enterprise Search business component Schedule.

This task is a step in Process of Setting Up the Business Component Source and Connector.

To deploy the business component Source for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view. The Search Connector Settings List applet is displayed.
Select Bus. Comp Connector and click Create Source.
The Deployed Flag field is automatically selected when the business component source has been deployed.

Verifying the Oracle Secure Enterprise Search Source for the Business Component Connector

This topic covers verification of the Oracle Secure Enterprise Search Source to integrate with the Siebel Search business component connector. It is recommended to execute this task if the status of the business component connector does not update correctly after the Deploy operation, or if the error message “Error in RemoteAdmin Adapter" is displayed.

This task is a step in Process of Setting Up the Business Component Source and Connector.

To verify the Oracle Secure Enterprise Search Source for the business component connector

Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Sources screen.
Select the Edit option for the buscomp Source.
The Source Configuration tab is displayed for the buscomp Source.

Verify the Source fields and values against the following table.

Field	Description
Source Name	Verify that the value is set to buscomp. This value corresponds to the buscomp connector library name in the Siebel Search Connector Settings view. Note: This value is case sensitive.
Configuration URL	This is the file URL of the configuration file. Verify that the value is set to the location of the RSS_Crawler_Configuration.xml file on the Oracle Secure Enterprise Search server. On Windows the value is set to: `file://localhost/fs/SSC/config/ RSS_Crawler_Configuration.xml` On UNIX the value is set to: `file://localhost//export/home/fs/SSC/config/RSS_Crawler_Configuration.xml`
Authentication Type	This field is not supported. The value must be empty.
User ID	This setting corresponds to, and takes the same value as, the business component connector Feed Access User ID field. For more information, see Configuring the Siebel Business Component Connector.
Password	This setting corresponds to, and takes the same value as, the business component connector Feed Access Password field. For more information, see Configuring the Siebel Business Component Connector.
Realm	This field is not supported for Siebel Search and Oracle Secure Enterprise Search integration. Verify that this field is empty.
Scratch Directory	This value points to a Temp/ local directory on the Oracle Secure Enterprise Search server where status files can be temporarily written.
Max. no. of connection attempts	This is the maximum number of connection attempts to access the data feed or upload the status feed. Verify that the value is set to 3.

Select the Authorization tab.
Verify that Crawl-time ACL Stamping is set to ACLs Controlled by the Source.

Verify the Authorization Manager fields and values against the following table

Field	Description
Plug-in Class Name	This field takes the value: oracle.search.plugin.security.auth.siebel.SiebelAuthManager
JAR File Name	This field takes the value: oracleapplications/Siebel8Crawler.jar
Siebel 8 authorization Web service endpoint	This field takes the value: http://<webserver>/eai_<language>/ start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&WSSOAP=1
User ID	This is the Siebel administrative User ID.
Password	This is the Siebel administrative User password.

Start the Oracle Secure Enterprise Search application, and verify that buscomp appears as a searchable source on the Search home page.
Navigate to the Sources screen.
Select the Edit option for the buscomp Source.
The Source Configuration tab is displayed for the buscomp Source.
Select the Authorization tab.
Verify that the SBLVISIBILITYID attribute is listed, with a value of Grant, in the Security Attributes table.
If the attribute has not been created you might have specified an incorrect path to the file RSS_Crawler_Configuration.xml.

Process of Setting Up the File System Source and Connector

The file system source and connector must be set up if you want external file systems to be indexed and searched by Oracle Secure Enterprise Search.

Note: The file system is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration. This process is only required if the Siebel File System connector will be used.

To set up the file system source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Configuring the Siebel File System Connector

The file system connector must be set up if you want external file systems to be indexed and searched by Oracle Secure Enterprise Search.

Note: The file system is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration. This process is only required if the Siebel File System Connector will be used.

This task is a step in Process of Setting Up the File System Source and Connector.

To configure the Siebel file system connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Click on the New button on the list applet.

Complete the following file system connector fields.

Field	Value
Name	filesystem
Version	1.0
Library Name	filesystem
Engine Name	OSES
StartingUrl	The starting URL is the location where the files or directories are crawled for indexing. If a URL represents a single file, then the crawler searches only that file. If a URL represents a directory, then the crawler recursively crawls all files and subdirectories in that directory. Only local host file URLs are allowed. You cannot specify file URLs on a remote computer. It is recommended to set the Starting URL to a shared folder. On Windows set the value to: file://localhost///SiebelServerIPAddress/fs/ On UNIX set the value to: file://localhost//directory_1/directory_2

Select Save Record on the Connector list.

Deploying the File System Source

This topic covers remote administration of the Oracle Secure Enterprise Search File System Connector. This task configures the Oracle Secure Enterprise Search File System Source and Source Group, and creates the Oracle Secure Enterprise Search file system Schedule.

This task is a step in Process of Setting Up the File System Source and Connector.

To deploy the file system source for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Select Filesystem Connector and click Deploy.
Verify that the deployment status of the file system Connector changes in the Search Connector Settings view.

Verifying the Oracle Secure Enterprise Search Source for the File System Connector

This topic covers verification of the Oracle Secure Enterprise Search Source to integrate with the Siebel Search file system connector. It is recommended to execute this task if the status of the file system connector does not update correctly after the Deploy operation, or if the error message “Error in RemoteAdmin Adapter" is displayed.

This task is a step in Process of Setting Up the File System Source and Connector.

To verify the Oracle Secure Enterprise Search Source for the file system connector

Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Sources screen.
Select the Edit option for the Filesystem Source.
The Source Configuration tab is displayed for the Filesystem Source.
Verify that the Starting URL is set to file://localhost///SiebelServerIPAddress/fs/.
Start the Oracle Secure Enterprise Search application, and verify that Filesystem appears as a searchable source on the Search home page.

Enabling Rich Text Format Processing for the External File System Connector

Rich Text Format file types are not processed by default by Oracle Secure Enterprise Search. This task enables indexing and searching of RTF files for the external file system connector.

This task is a step in Process of Setting Up the File System Source and Connector.

To enable Rich Text Format processing for the external File System Connector

Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Sources screen.
Select the Edit option for the file system Source.
The Customize File Source screen is displayed for the file system source.
Select the Document Types tab.
The supported document types are listed for the source type.
Select RTF Document in the Not Processed column, and click the arrow button to move it to the Processed column.
Click Apply.

Verifying Indexing for the File System Connector

The crawling and indexing operations can be invoked from the Oracle Secure Enterprise Search administration UI to make sure that the Oracle Secure Enterprise Search File System Source has been configured correctly. It is recommended to execute this task if the status of the business component connector does not update correctly after the Deploy operation, or if the error message “Error in RemoteAdmin Adapter" is displayed.

This task is a step in Process of Setting Up the File System Source and Connector.

To verify indexing for the file system connector

Navigate to the Schedules screen in the Oracle Secure Enterprise Search administration application.
Select Filesystem Schedule and click Start.
Click the Status link to view status details.
Start the Oracle Secure Enterprise Search application, and verify that Filesystem appears as a searchable source on the Search home page.

Process of Setting Up the Web Crawler Source and Connector

The crawler source and connector must be set up if you want web sources to be indexed and searched by Oracle Secure Enterprise Search.

Note: The Web Crawler is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration. This process is only required if the Siebel Web Crawler connector will be used.

To set up the Web Crawler source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Creating an Oracle Secure Enterprise Search Source for the Web Crawler Connector

This topic covers creation of an Oracle Secure Enterprise Search Web Crawler Data Source to integrate with the Siebel Search Web Crawler connector.

This task is a step in Process of Setting Up the Web Crawler Source and Connector.

To create an Oracle Secure Enterprise Search source for the Web crawler connector

Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Sources screen.
Select Web from the Source Type list.
Click Create.

Complete the Web Source fields. The fields are described in the following table.

Field	Description
Source Name	The name for the Web Source. This value corresponds to the crawler connector Library name in the Siebel Search Administration Search Connector Settings view. Set the value to crawler. This value is case sensitive.
Starting URL	The URL for the crawler to begin crawling. The starting address can be in HTTP or HTTPS format, for example, `http://www.oracle.com`.
Self Service	Enable Self Service so that Web sources that require user authentication can be crawled and indexed. Enabling Self Service means that end users can enter their credentials and authenticate themselves to crawl their data.
Start Crawling Immediately	Select this to start crawling automatically after the source is created. Clear this for crawling to begin at the next scheduled time. Note: If the Create and Customize button is clicked rather than the Create button, or if Self Service is enabled, then this option is ignored.

Click Create.

Creating a Source Group for the Web Crawler Connector

The Oracle Secure Enterprise Search File System Source must be assigned to an Oracle Secure Enterprise Search Source Group. The Oracle Secure Enterprise Search Source Group name must correspond to the Source name and the Siebel connector library name.

This task is a step in Process of Setting Up the Web Crawler Source and Connector.

To create a source group for the File System connector

Start the Oracle Secure Enterprise Search Administration application.
Navigate to the Search screen, then the Source Groups view.
Click Create.
Enter crawler as the name of the Source Group. This value is case sensitive.
Click Proceed to Step 2.
Select Web from the Select Source Type list.
Click Go.
Select crawler from the Available Sources list, and click the arrow button to add it to Assigned Sources.
Click Finish.
Start the Oracle Secure Enterprise Search application, and verify that crawler appears as a searchable source on the Search home page.

Verifying Oracle Secure Enterprise Search Indexing of the Web Crawler Source

This topic covers invoking the crawling and indexing operations from the Oracle Secure Enterprise Search administration UI, to make sure that the Oracle Secure Enterprise Search crawler source has been configured correctly.

This task is a step in Process of Setting Up the Web Crawler Source and Connector.

To verify Oracle Secure Enterprise Search indexing of the Web Crawler data source

Navigate to the Schedules view in the Oracle Secure Enterprise Search administration application.
Select the crawler Schedule and click Start.
Click the Status link to view status details.

Administering the Siebel Web Crawler Connector

The Siebel Search web crawler connector is required for integrating with the Oracle Secure Enterprise Search web crawler source. It is administered in the Search Connector Settings view.

This task is a step in Administering the Siebel Web Crawler Connector.

To configure the Siebel Search web crawler connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Click the New button on the list applet.

Complete the following fields.

Field	Value
Name	crawler
Version	1.0
Library Name	crawler
Engine Name	OSES

Select Save Record on the Connector list.

Process of Setting Up the Database Source and Connector

The database source and connector must be set up if you want JDBC sources to be indexed and searched by Oracle Secure Enterprise Search.

Note: The Database Connector is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration.

To set up the Database source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Creating a Source for the Database Connector

This topic covers creation of an Oracle Secure Enterprise Search Source to integrate with the Siebel Search Database Connector. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the Database Source and Connector.

To create a source for the Database Connector

Navigate to the Sources screen.
Select Database from the Source Type menu.
Click Create.

Complete the Database Source fields. The fields are described in the following table.

Field	Description
Source Name	The name of the Database Source. This value corresponds to the crawler connector Library name in the Siebel Search Administration Search Connector Settings view. Set the value to Database.
Database Connection String	The JDBC connection string for the database. Set the value to the following for an Oracle database: jdbc:oracle:thin@<Hostname>:<Port Number>:<SID> Set the value to the following for SQL Server: jdbc:sqlserver://<Hostname>
User ID	User ID to log in to the database.
Password	Password to log in to the database.
Query	Query to retrieve contents for crawling.
Query File	Path to the XML file specifying the attribute and attachment sub queries.
Cache File	Absolute path and filename prefix of temporary file for caching crawled data, for example: c:\temp
Path Separator	Path separator in the document path. Set the value to #.

Click Next.
Select ACLs Controlled by the Source to secure the table that is crawled.
Click Create.

Creating a Source Group for the Database Connector

The Oracle Secure Enterprise Search Database source must be assigned to an Oracle Secure Enterprise Search source group. The Oracle Secure Enterprise Search source group name must correspond to the source name and the Siebel connector library name. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the Database Source and Connector.

To create a source group for the Database Connector

Navigate to the Search screen, then the Source Groups view.
Click Create.
Enter Database as the name of the Source Group.
Click Proceed to Step 2.
Select Database from the Select Source Type menu.
Click Go.
Select Database from the Available Sources list, and click the arrow button to add it to Assigned Sources.
Click Finish.
Start the Oracle Secure Enterprise Search application, and verify that Database appears as a searchable source on the Search home page.

Verifying Oracle Secure Enterprise Search Indexing of the Database Source

This topic covers invoking the crawling and indexing operations from the Oracle Secure Enterprise Search administration UI, to make sure that the Database source has been configured correctly.

This task is a step in the Process of Setting Up the Database Source and Connector.

To verify Oracle Secure Enterprise Search indexing of the Database Crawler

Navigate to the Schedules view in the Oracle Secure Enterprise Search administration application.
Select the Database Schedule and click Start.
Click the Status link to view status details.

Configuring the Database Connector

The Siebel Search Database Connector is required for integrating with the Oracle Secure Enterprise Search Database source. It is administered in the Siebel Search Connector Settings view.

This task is a step in the Process of Setting Up the Database Source and Connector.

To configure the Database Connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Click the New button on the list applet.

Complete the following fields.

Field	Value
Name	Database
Version	1.0
Library Name	Database
Engine Name	OSES

Select Save Record on the Connector list.

Process of Setting Up the IMAP Email Source and Connector

The IMAP E-Mail source and connector must be set up if you want to index and search IMAP email sources. An email source derives its content from emails sent to a specific email address. When Oracle Secure Enterprise Search crawls an email source, it collects email from all folders set up in the email account, including Drafts, Sent Items, and Trash emails.

Note: The IMAP E-Mail Connector is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration.

To set up the IMAP E-Mail source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Creating a Source for the IMAP E-Mail Connector

This topic covers creation of an Oracle Secure Enterprise Search Source to integrate with the Siebel Search E-Mail Connector. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the IMAP Email Source and Connector.

To create a source for the IMAP E-Mail Connector

Navigate to the Sources screen.
Select E-Mail from the Source Type list.
Click Create.

Complete the email source fields. The fields are described in the following table.

Field	Description
Source Name	The name of the IMAP E-Mail Source. This value corresponds to the crawler connector Library name in the Siebel Search Administration Search Connector Settings view. Set the value to IMAP E-Mail.
IMAP Server	The address of the IMAP server.
User Name	The user name for the email account.
Password	The password for the email account.

Click Create.

Creating a Source Group for the IMAP E-Mail Connector

The Oracle Secure Enterprise Search IMAP E-Mail source must be assigned to an Oracle Secure Enterprise Search source group. The Oracle Secure Enterprise Search source group name must correspond to the source name and the Siebel connector library name. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Creating a Source for the IMAP E-Mail Connector.

To create a source group for the IMAP E-Mail Connector

Navigate to the Search screen, then the Source Groups view.
Click Create.
Enter IMAP E-Mail as the name of the Source Group.
Click Proceed to Step 2.
Select E-Mail from the Select Source Type list.
Click Go.
Select IMAP E-Mail from the Available Sources list, and click the arrow button to add it to Assigned Sources.
Click Finish.
Start the Oracle Secure Enterprise Search application, and verify that IMAP E-Mail appears as a searchable source on the Search home page.

Verifying Oracle Secure Enterprise Search Indexing of the IMAP E-Mail Source

This topic covers invoking the crawling and indexing operations from the Oracle Secure Enterprise Search administration UI, to make sure that the IMAP E-Mail source has been configured correctly.

This task is a step in the Process of Setting Up the IMAP Email Source and Connector.

To verify Oracle Secure Enterprise Search indexing of the IMAP E-Mail Crawler

Navigate to the Schedules view in the Oracle Secure Enterprise Search administration application.
Select the IMAP E-Mail Schedule and click Start.
Click the Status link to view status details.

Configuring the IMAP Email Connector

The Siebel Search IMAP Email Connector is required for integrating with the Oracle Secure Enterprise Search Email source. It is administered in the Siebel Search Connector Settings view.

This task is a step in the Process of Setting Up the IMAP Email Source and Connector.

To configure the IMAP Email Connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Click the New button on the list applet.

Complete the following fields.

Field	Value
Name	IMAP E-Mail
Version	1.0
Library Name	IMAP E-Mail
Engine Name	OSES

Select Save Record on the Connector list.

Process of Setting Up the Lotus Notes Source and Connector

The Lotus Notes source and connector must be set up if you want to index and search Lotus Notes sources. A Lotus Domino Server instance can have one or more databases that can be crawled using the Lotus Notes source. The Lotus Notes source navigates through the databases to crawl email, calendar and address book data.

Note: The Lotus Notes connector is not a required connector for Siebel Search and Oracle Secure Enterprise Search integration.

To set up the Lotus Notes source and connector for integration with Oracle Secure Enterprise Search, perform the following tasks:

Setting Up Identity Management for Lotus Notes

This topic covers setting up identity management for the Lotus Notes connector. Oracle Secure Enterprise Search provides a Lotus Notes identity plug-in so that the Lotus Domino Directory can be used to authenticate and validate the Lotus Notes users and groups for Siebel Search. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the Lotus Notes Source and Connector.

To set up identity management for Lotus Notes

Navigate to the Global Settings screen, then the Identity Management Setup view.
Select Lotus Notes in the Identity Plug-In applet.
Click Activate.

Complete the Lotus Notes Source fields. The fields are described in the following table.

Field	Description
Server Name	The Domino server fully qualified host name. The value format is `<Server-Name>:<HTTP Port Number>`. Port number is not required if the Domino server is using the default 80 port.
User Name	Name of the Lotus Domino server user to be used for crawling the Lotus Notes databases.
Password	Password for the Lotus Domino server user to be used for crawling the Lotus Notes databases.

Click Finish.

Creating a Source for the Lotus Notes Connector

This topic covers the creation of an Oracle Secure Enterprise Search source to integrate with the Siebel Search Lotus Notes connector. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the Lotus Notes Source and Connector.

To create a source for the Lotus Notes Connector

Navigate to the Sources screen.
Select Lotus Notes from the Source Type list.
Click Create.

Complete the Lotus Notes Source fields. The fields are described in the following table.

Field	Description
Source Name	The name of the Lotus Notes source. This value corresponds to the crawler connector Library name in the Siebel Search Administration Search Connector Settings view. Set the value to Lotus Notes.
Server Name	The IP address of the Domino server. The value is specified in the format `<IP address>:< HTTP port number>`.
Attribute List	The list of attribute names in the Lotus Notes database to be crawled. The attributes are specified in a comma-separated list in the format `<attribute name>, <attribute name>`.
User Name	The Lotus Notes user who has access to the Lotus Notes database used for crawling.
Password	The password for the Lotus Notes account.
Container Name	The names of the containers to be crawled. Multiple container names are specified in a comma-separated list. The container name can include folders, databases, views and folders within databases. For example, database-abc.nsf, folders-folder1, views-abc.nsf:By Author, and db-abc.nsf:folder\subfolder.
Authentication Attribute	The name of the authentication attribute that is used to validate the ACL. For Active Directory identity plug-in manager, the value is set to `USER_NAME`. For the Lotus Notes identity plug-in manager, the value is set to `NATIVE`.
Notes Title Field	This field is used to specify the text fields that are parsed to retrieve the title field, such as Subject.

Creating a Source Group for the Lotus Notes Connector

The Oracle Secure Enterprise Search Lotus Notes source must be assigned to an Oracle Secure Enterprise Search source group. The Oracle Secure Enterprise Search source group name must correspond to the source name and the Siebel connector library name. This task is executed in the Oracle Secure Enterprise Search Administration application.

This task is a step in the Process of Setting Up the Lotus Notes Source and Connector.

To create a source group for the Lotus Notes Connector

Navigate to the Search screen, then the Source Groups view.
Click Create.
Enter Lotus Notes as the name of the Source Group.
Click Proceed to Step 2.
Select Lotus Notes from the Select Source Type list.
Click Go.
Select Lotus Notes from the Available Sources list, and click the arrow button to add it to Assigned Sources.
Click Finish.
Start the Oracle Secure Enterprise Search application, and verify that Lotus Notes appears as a searchable source on the Search home page.

Verifying Oracle Secure Enterprise Search Indexing of the Lotus Notes Source

This topic covers invoking the crawling and indexing operations from the Oracle Secure Enterprise Search administration UI, to make sure that the Lotus Notes source has been configured correctly.

This task is a step in the Process of Setting Up the Lotus Notes Source and Connector.

To verify Oracle Secure Enterprise Search indexing of the Lotus Notes Source

Navigate to the Schedules view in the Oracle Secure Enterprise Search administration application.
Select the Lotus Notes Schedule, and click Start.
Click the Status link to view status details.

Configuring the Lotus Notes Connector

The Siebel Search Lotus Notes Connector is required for integrating with the Oracle Secure Enterprise Search E-Mail source. It is administered in the Siebel Search Connector Settings view.

This task is a step in the Process of Setting Up the Lotus Notes Source and Connector.

To configure the Lotus Notes Connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Click the New button on the list applet.

Complete the following fields.

Field	Value
Name	Lotus Notes
Version	1.0
Library Name	Lotus Notes
Engine Name	OSES

Select Save Record on the Connector list.

Administering Connectors for Oracle Secure Enterprise Search Integration

This topic covers administering connectors for Siebel Search and Oracle Secure Enterprise integration.

To administer connectors for Siebel Search and Oracle Secure Enterprise integration, perform the following tasks:

Updating Connector Settings

This topic covers updating Search connector settings for a connector which has already been deployed. The changes are entered in the Siebel Search Connector Settings view, and submitted to Oracle Secure Enterprise Search for remote update.

This task is a step in Administering Connectors for Oracle Secure Enterprise Search Integration.

To update connector settings for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Select the Connector for which settings have been changed, and click Update Source.

Deleting a Connector

This task deletes the Siebel connector, the corresponding Oracle Secure Enterprise Search source, source group, and schedule, and all index records for that connector. It is recommended to execute this task if a malformed connector must be deleted and recreated.

This task is a step in Administering Connectors for Oracle Secure Enterprise Search Integration.

To delete a connector for Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Connector Settings view.
The Search Connector Settings List applet is displayed.
Select the Connector and click Delete Source.

Disconnecting from Oracle Secure Enterprise Search and Deactivating the Identity Manager

This topic covers disconnecting from Oracle Secure Enterprise Search, and deactivating the identity plugin manager for Siebel.

Disconnecting from Oracle Secure Enterprise Search

Use the following procedure to disconnect from Oracle Secure Enterprise Search, using the Siebel Search Administration UI.

To disconnect from Oracle Secure Enterprise Search

Navigate to the Administration - Search OSES screen, then the Search Engine Settings view.
Select the CSSOSESAdapter search engine library, and click Disconnect.
The Connected flag in the Search Engine Settings view is set to false.

Deactivating the Siebel Identity Plugin Manager

Use the following procedure to deactivate the Siebel identity plugin manager, using the Oracle Secure Enterprise Search Administration UI.

To deactivate the Siebel Identity Plugin Manager

Log in to the Oracle Secure Enterprise Search Administration application.
Navigate to the Global Settings screen.
Select Identity Management Setup.
The Siebel Identity Plugin Manager is displayed.
Click Deactivate.

Oracle Secure Enterprise Search Changes Required for EAI to Support HTTPS

As of Siebel Innovation Pack 2017, the Enterprise Application Integration (EAI) URL has changed from HTTP to HTTPS. As a result, a certificate must be included in Oracle Secure Enterprise Search for callbacks from Oracle Secure Enterprise Search to EAI to be successful.

The following Oracle Secure Enterprise Search changes are required for EAI to support HTTPS:

Install JDK 7 for Oracle Secure Enterprise Search 11.2.2.2.0.
Modify the Searchctl.bat file and set the SetDomainEnv files to point to JDK 7.
Import the Siebel Certificate into JDK 7.
Update the Oracle Secure Enterprise Search WebLogic server to include the certificate.