OpenSearch Support Based on PeopleSoft Application Version

All customers should review the information on the PeopleSoft Search and Insights Home Page, Troubleshooting and Known Issues to determine which updates and fixes are required for your application. The information is applicable whether you are doing a new installation of OpenSearch or moving from Elasticsearch.

For more information on which update images have the required fixes for your application, see PeopleSoft Search and Insights Home Page (Doc ID 2205540.2) on My Oracle Support.

This table lists the OpenSearch key functionality from the perspective of its use and implementation within a PeopleSoft application system.

Item

OpenSearch Functionality

High availability

The recommended approach to high availability is by deploying an OpenSearch cluster with at least three nodes on machines that are not on the same physical server and by following the configuration guidelines.

Fail-over mechanism

OpenSearch is distributed by nature, that is, it knows how to manage multiple nodes. A cluster can contain one or more nodes and one of the nodes act as a master node. OpenSearch automatically distributes the indexed data to the nodes based on its constructs of primary shards and replica shards, so indexed data is available even when a node fails.

Phonetic

OpenSearch supports phonetic search using a plug-in that is installed when you install OpenSearch in a PeopleSoft implementation.

Note: For custom search pages, PeopleSoft Applications can use PeopleSoft APIs for phonetic queries in OpenSearch.

Wild card search

OpenSearch supports using a wild card as a leading character in a search text. For example, *racle.

Stop Word

Stop Words are words that are commonly used (such as articles, prepositions) and do not contain important significance to be used in a search text.

If a word is in the OpenSearch’s stop word list, it would be ignored.

Attachment processing

PeopleSoft Search Framework downloads any attachment specified in a search definition, and directly pushes the attachment to the search engine using the libcurl library bypassing Integration Gateway. OpenSearch uses the ingest- attachment plug-in to extract the attachment contents and indexes the attachment data. This avoids multiple log-in attempts during crawling.

Stemming

Stemming is the process of reducing inflected word to its root or stem. For example, talking, talked, talks will reduce to the root — talk.

OpenSearch supports limited stemming support, for example, talk/talked/talks. Synonyms are supported by using a file to store the required synonyms as per your business needs.

OpenSearch supports stemming search for the following languages:

  • Arabic

  • Czech

  • Danish

  • Dutch

  • English

  • Finnish

  • French

  • German

  • Greek

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Portuguese

  • Romanian

  • Russian

  • Simplified Chinese

  • Spanish

  • Swedish

  • Thai

  • Turkish

  • Traditional Chinese

Relevancy Scoring

Relevancy scoring is performed by OpenSearch, which uses an internal scoring algorithm.

Custom Scoring

In OpenSearch, custom scoring is supported through Search Framework APIs.

Synonyms

OpenSearch uses a file (synonyms_grammar.txt) to store synonyms or any abbreviations that you want to include. If synonyms provided are not adequate for your installation, you can modify this file. The file is located at config\analysis\synonym_grammar.txt.

You can enter synonyms in two ways:

"i-pod, i pod => ipod"

OR

"universe, cosmos"