Planning for Elastic search

                        Planning for Elastic search 

If you are planning for ES then go for tools patch 8.55.19 or 8.56.04 as suggested by Oracle

https://blogs.oracle.com/peopletools/planning-to-deploy-elasticsearch-with-peoplesoft-between-now-and-early-2018

We had issues when we were PT 8.55.15 

1) There is no concept of direct transfer of files, it will have to go through IB.

2) If your search definitions are having attachment then it gives lot of rejections in ES log.

Further we went to PT8.55.17 and there we were able to use Direct transfer method after discussion with Oracle development as they accepted it as a bug. There were few more things you need to change when you are facing rejections in ES log.

1)Navigate to Main menu>Peopletools>Search Framework>Administration>Search Instance

select PTSF_ELASTIC (whatever name you have given) click search option config

Here you will get an option Attachment Handler make it 10. It is with Patch 17 and afterward only.
2)Open .yml file and add http.max_content_length: 500mb at the end.

3) There are two ways to transfer the files:

a) Data with attachment will go directly while without attachment it will go through IB.

b) Direct full transfer here with or without attachment all data will go directly without using IB.

We opted for Direct full transfer that is option B.

There will be code changes done by Oracle development in Application Package PTSF_ES (Ingest service).

• DirectTransfer is already in use from PeopleSoft 8.55.17 and 8.56 GA for documents with attachments. From 8.55.19 and 8.56.04, even documents without attachments will be sent through DirectTransfer making it Full DirectTransfer.
• The default configuration for Full DirectTransfer takes care of most of the customer scenarios for indexing speed and performance. Customers may perform a few additional configurations based on their requirements, for example,  changing the number of Direct Transfer Handles, which is explained in the PeopleBooks.