An Oracle blog about PeopleSoft Technology

Another Update on PeopleSoft's Plans for Elasticsearch

Matthew Haavisto
Product Management Director

In an earlier post, we indicated that Elasticsearch would be available in the 8.55.10 of PeopleTools.  Instead, it will not be available with this specific PeopleTools patch. We are working on completing release requirements and we will update the exact 8.55 patch number when we make Elasticsearch generally available for PeopleSoft.  As mentioned previously, Elasticsearch will be the only Search engine supported in PeopleTools 8.56.

For those using SES and Verity...

  • SES: We plan to support SES in PeopleTools 8.55 for 18 months after Elasticsearch is generally available.
  • Verity: We plan to support Verity for our 9.1 application releases through September 2018. Note that Verity will not be supported in 8.56, which means that if customers wish to use Verity, they will need to stay on 8.55. We will do our best to support customers through the support policy of the 9.1 applications.

For those attending Oracle Open World this September, we offer a session on Elasticsearch that you should find interesting and informative. In the presentation, we will describe all the benefits of Elasticsearch integration for
PeopleSoft including its ease of deployment, transition, and
operations. Here are the session logistics:

Session ID: CON7066
Session Title: Getting the Most Out of PeopleSoft: Transitioning to Elasticsearch 
Room: Moscone West—2004
Date and Time: 09/21/16, 12:15:00 PM - 01:00:00 PM


Join the discussion

Comments ( 2 )
  • Abhilash Vareekal Thursday, September 14, 2017
    I would like to attend the session : Getting the Most Out of PeopleSoft: Transitioning to Elasticsearch
  • Zoheir Puthawala Friday, September 15, 2017
    We are planning to implement Elastic Search for our HCM and CRM 9.2 applications in first quarter of 2018, and I wanted to get a better understanding of the product.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.