An Oracle blog about PeopleSoft Technology

  • September 13, 2017

Planning to Deploy Elasticsearch with PeopleSoft between now and Early 2018?

Matthew Haavisto
Product Management Director
If you are planning to deploy Elasticsearch by the end of this year or early next year, we suggest going to PeopleTools 8.55.19.  This PeopleTools patch is planned for availability in mid-October, and it contains many fixes and improvements.  Similarly, if you are moving to PeopleTools 8.56, we recommend going to the 8.56.04 patch, which contains the same fixes, and is planned for the same availability.  As PeopleSoft customers have deployed Elasticsearch over the past several months, we have modified some of the ways we handle certain functions architecturally and have fixed several issues that customers reported.  These patch levels contain all the fixes and changes that we have made to date.  If you are already live on Elasticsearch or are in the process of going live and can’t wait until 8.55.19, contact Oracle Support for assistance if you experience any issues.

Join the discussion

Comments ( 8 )
  • Frank Dolezal Friday, September 15, 2017
    Where can I find a list of the Elastic enhancements for 8.55.19? Are they available as a hotfix for 8.55.18?
  • Rajendra Francis Tuesday, September 26, 2017
    8.56.04 patch is not available yet , when will it be released
  • Matthew Tuesday, September 26, 2017
    Frank: Enhancements will be not be in .18, however, you can contact support if you are unable to move to 19. They may be able to make a POC available to you.

    Rajendra: We can't give exact dates, but it's planned for October. You'll see more soon. 8.56.04 will be released the same time as 8.55.19.
  • Vijeyakumar Chinnaraj Anthony Thursday, November 9, 2017
    At Baptist Health, we are going live with 9.2 Upgrade early next year, and we are currently on PeopleTools version 8.55.14.

    Do we still need to upgrade tools to 8.55.19?
  • Douglas Tuesday, November 21, 2017
    This recommendation is at odds with our experience. We are having to go live with 8.56.03 due to several critical problems with released 8.56.04 - one of them is specifically related to Elasticsearch. We have three critical incidents logged with support currently. My initial suspicion was that our problems were due to environment or configuration problems; however, after rebuilding the environment and applying each update in succession, we have confidence that Image 4 actually breaks Elasticsearch for us (among several other issues).
  • Matthew Tuesday, November 28, 2017
    Vijeyakumar: You don't necessarily have to move to .19/.04. We recommend it generally because there are performance improvements, particularly for customers that whose searches cover large volumes and attachments. Not everyone requires that, and we still have customers on .11 that are working fine. You may test with .14, but if you encounter performance or indexing issues, try the upgrade.
  • Matthew Tuesday, November 28, 2017
    People have asked what is different with 8.55.19/8.56.04. There are several, and you can view the complete update on MOS/Elasticsearch page. Probably the biggest change is a feature we call Direct Transfer. This eliminates Integration Broker in the communication chain with ES. Without DT...
    - Not able to handle large volume or size
    - Error handling was manual (re-send)
    - Resulted in more errors

    With DT...
    - Multiple threads for sending multiple docs simultaneously
    - Reduced errors and automated error handling (retry)

    DT was first introduced in 8.55.17, but that only handled docs with attachments. In 8.55.19 all docs use DT.
  • Matthew Wednesday, December 6, 2017
    Douglas: I understand from support that the issue you describe has been fixed for your customer. The issue happens when a customer does a manual upgrade of PeopleTools and does not use the DPK, but instead uses the manual VCD approach. We advocate using DPKs in any case, but this is another reason to do so. We are working on a solution for the manual/VCD approach, but customers should use DPKs for Tools/Elasticsearch.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.