How To Propagate Search Parameters Changes Into OSES? (Doc ID 1555925.1)

Last updated on DECEMBER 19, 2014

Applies to:

Siebel CRM - Version 8.1.1.7 SIA [21238] and later
Information in this document applies to any platform.

Goal

Several Siebel Search paramenters are propagated into Oracle Secure Enterprise Search (OSES or SES) when integrating both applications. For example:

SearchSecurityService Search Inbound web service
Password SES Admin Password (Eqsys password)
SES Username Trusted entity user
SES Password Trusted entity user password
Web Service Endpoint Address Search web service
Web Service Endpoint Username Search web service user
Web Service Endpoint Password Search web service user password
Configuration URL URL of crawler configuration file
Feed Access User ID User that accesses the feeds
Feed Access Password Password of user that accesses the feeds
Scratch Directory OSES temporary directory

After data is indexed and if any value related to search web service (parameters in Italic) is changed, the Siebel - OSES integration fails.
If the Siebel 8 Indentity Management Setup is deactivated and the buscomp is recreated, ALL indexed data is lost. It's necessary to index the search categories from scratch.

Other paramenters can be changed/propagated without having to recreate the buscomp.

How to propagate Siebel Search changes into OSES without loosing all indexed data?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms