Just when I thought I was up to speed on the newest search functionality in PeopleSoft, Oracle Secure Enterprise Search (SES), I learned that it was being replaced by Elasticsearch. What is Elasticsearch and how does it impact my organization?
Elasticsearch is a new search engine that was introduced in Tools 8.55.11 and the implementation is similar to that of SES. If it’s similar, then why the change? Well, it provides a few added benefits over SES, which includes:
- Easier to install and maintain
- Better crawl and search performance
- Better resource utilization on the search engine host
- Valuable with Fluid User Experience
- Ability to search from any context and at any point in the process
Is there a need to move to Elasticsearch? To put it bluntly, YES there is a need. SES and Verity search functions will be deprecated as of PeopleTools 8.56. The SES; however, will continue to be supported through April 30, 2018.
So now that you see that there is an end in sight for the SES search capability, what steps need to be taken to move to Elasticsearch? Overall, the steps would include the following:
- Adding an Elasticsearch instance
- Taking Elasticsearch updates and fixes from the latest PeopleSoft application image
- Deploying search definitions and categories on the Elasticsearch server
- Building the search index with full crawling
- Scheduling incremental crawling updates
- Performing user acceptance tests
- Going live on Elasticsearch
What does the transition look like? There are actually two options to transition. The first option is to move to production after Elasticsearch is fully built which involves production downtime. This would be a good option if you want to avoid the resource contentions for indexing while the production environment is on SES. You would also be able to setup a separate test environment to perform acceptance testing. This would allow you to take down the production environment while building the index.
The second option is a live cutover, without the need to take the production environment down. You would decommission SES in the production environment and install an Elasticsearch instance, build the indexes and test on your production environment. This approach will extend your downtime. In both instances, you will need to take into account the time it will take for a full crawl of your search definitions when deciding which approach to take.
The prerequisites for moving to Elasticsearch include the following:
- PeopleSoft 9.2 application
- Latest PeopleSoft Update Image for your application
- PeopleTools 8.55.11 or higher patch level
- Meet resource requirements
- One or more hosts provisioned to run Elasticsearch
- Updates installed in PeopleSoft environment
- Download and deploy the DPK.
Additional documentation can be found on My Oracle Support , PeopleTools 8.55.11 or Higher Elasticsearch Home Page (Doc 2205540.2):
- PeopleSoft Deployment Packages for Elasticsearch Installation (PeopleSoft PeopleTools 8.55)
- Moving from SES to Elastic Search
- PeopleTools 8.55: Search Technology
If you have any questions please feel free to email us at Larry.Zagata@MIPROConsulting.com.Posted by