This chapter covers the following topics:
Information about repositories and contexts is applicable only for service providers. For service requestors through Oracle iSupport, please refer to Customizations and Extensions.
Oracle Knowledge Management users can quickly integrate and use their existing knowledge documents within Oracle Service applications. The documents constitute a large pool of unstructured data and can include, for example, product manuals, training guides, and corporate presentations. Specifically, users can:
Search for documents on web sites
Oracle Secure Enterprise Search (SES) achieves this functionality.
Search for documents within local and network file systems
SES achieves this functionality.
A repository defines a collection of documents that can be searched. Contexts control access to these repositories.
Repositories defined in Oracle Knowledge Management can be of the following types:
custom
Oracle Secure Enterprise Search
Custom repositories refer to custom repositories built by a service requestor in the Oracle Applications Framework as described in the section Define Simple Search Repositories. If you have implemented Oracle Secure Enterprise Search, then you can define SES repositories. The setup instructions for SES are in the Oracle Secure Enterprise Search Web page, which is on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/oses/index.html.
In the Manage Repositories page you provide the technical properties of the repositories referenced in the Repository Mappings region of the Mapping Contexts page. The properties depend on the repository type.
Navigation
Setup > Repositories > Manage Repositories
Notes for Secure Enterprise Search (SES) Repository Properties (Repository Details Region)
END_POINT: This is the URL from which the SES search web server is hosted.
PROXY_HOST, PROXY_PORT: These fields specify a proxy server through which search requests to the SES server must be made.
DATA_GROUPS: This property is a comma delimited list of data groups that are defined in the SES setup. Data groups are groupings of data sources. When this property is set, search for this repository is restricted to documents in the list of specified data groups.
Steps to Integrate Oracle Knowledge Management with Oracle Secure Enterprise Search
Log in as Knowledge Administrator.
Navigate to Setup > Repositories.
Select Manage Repositories.
Click Add Another Row.
Select Type = Oracle Enterprise Search, Name = <whatever you want>.
Copy the SOAP endpoint for the SES web service to the ENDPOINT property.
For SES, this is always of the following form: http://<machine>:<port>/search/query/OracleSearch.
Click Apply.
Select Context to include the repository, that is, Global, an Application, or a particular responsibility.
Click Add Another Row in the Repository Mappings.
Select Repository = <the one you created earlier> and Tab Label = <whatever you want>.
You can move up and down however you want to reorder the tabs at this point.
Click apply.
Click the Knowledge tab to go back to search, and perform a search.
Your new SES tab appears.
Notes for Custom Repository Properties (Repository Details Region)
Results JRAD: This is a UI region within the OA framework for showing search results.
Search VO: This is the name of Java view object that contains the query to perform a search and returns the results (not merely a count).
Count VO: The Count VO is a view object that encapsulates a procedure to return how many search results occur for a given keyword search.
In the Mapping Contexts page you define which set of repositories will be searched and what their display order is in the Basic (Unified) Search page. You can define multiple tab configurations for different scenarios of user responsibilities and can make mappings for a Global, Application, or Responsibility context.
Navigation
Setup > Repositories
Notes
When adding contexts, keep in mind that settings at the Responsibility level override Application settings, which override Global settings for a particular user.