PeopleSoft Search Framework: Crawl & Deploy Indexes (Part 4)

by Apurva T. on March 24, 2014

in PeopleSoft Administration

Now that you’ve installed Oracle SES, configured it for PeopleSoft application, configured the PeopleSoft application to make use of SES – it is time to deploy the indexes and start making use of the search functionalities.

This is part 4 of the series on PeopleSoft Search Framework and for your reference, the other parts of this topic are mentioned below:

Part 1- PeopleSoft Search Framework: How to Install Oracle SES

Part 2- How to Configure PeopleSoft 9.2 with Oracle SES

Part 3- Configure PeopleSoft to use SES

Prior to continuing with the part 4, the following items need to be installed, configured, and functional.

  • Oracle SES
  • PeopleSoft Database
  • Application Server
  • PeopleSoft Integration Broker
  • Process Scheduler Server
  • Successful diagnostic tests

PeopleSoft Search Framework: Crawl & Deploy Indexes

Based on the application or functionality you’re using, you will be deploying indexes and crawling them. To begin with, we can atleast deploy the PTPORTALREGISTRY index to enable global search in the application. Go to PeopleTools -> Search Framework -> Administration -> Deploy/Delete Object.

Deploy PTPORTALREGISTRY

Now check the PTPORTALREGISTRY deploy option and click the Deploy button. You will see the status change to Deployed-Not Crawled

PeopleSoft SES Configuration Part 3

Now we need to setup crawling. Go to PeopleTools -> Search Framework -> Administration -> Schedule Search Index and add a new value, say PTPORTALREGISTRY and do a full index when doing it for the first time.

PeopleSoft SES Build Search Index

 

It will run an application engine process named PTSF_GENFEED and once it goes to success, you can come back to Deploy/Delete objects and note the change in status of the index to Crawled.

Also Read:  PeopleSoft Application Server Configuration

You can now start using Search functionalities. Also, deploy any more indexes you need to.

Hopefully you found the series helpful. Any questions – let us know in the comment box.

{ 18 comments… read them below or add one }

Wil September 8, 2014 at 10:48 pm

Thank you for this… it helped me in my issue

Reply

Narasimha March 20, 2015 at 6:50 am

when i tried to Deploy
Deploy Status is showing “Deployed” But problem is Crawl Status is saying “Not Crawled”.

Can you please help on this Issue.
Thank You

Reply

Apurva March 20, 2015 at 10:20 am

You need to run the index:
PeopleTools -> Search Framework -> Administration -> Schedule Search Index

Reply

James Albert August 31, 2015 at 10:06 pm

Hi 🙂

I cant crawl my search index, (PeopleTools -> Search Framework -> Administration -> Schedule Search Index)
these are the errors that i get. can you help me solve this 🙂

*On the .log file
EQG-30236: Crawler plug-in fatal error
EQP-60328: FeedFetcher already exited due to failure
EQG-30237: Crawler plug-in warning:
EQP-80317: HTTP connect attempt failed after 3 attempts.

*On the message log
SES crawler status : Failed , restart AE after resolving the error (262,153) PTSF_GENFEED.SES_STAT.GBL.default.1900-01-01.Step01.OnExecute PCPC:6680 Statement:76

Reply

apurva August 31, 2015 at 11:40 pm

There is a hint in the error – EQP-80317: HTTP connect attempt failed after 3 attempts.
Is your Integration Broker working fine? Are you able to successfully test all SES connections and able to deploy indexes?

Reply

James Albert September 1, 2015 at 9:00 pm

Hi

our IB is working fine. i checked it a couple of times already. done every possible resolution found on Oracle Support but none works.

i am able to deploy all search indexes but i am always getting that error when i am crawling it. I always crawl PTPORTALREGISTRY first but it always fails. I tried crawling the other search index and it also fails with the same error.

i ran round trip test and it completed successfully.

Reply

apurva September 1, 2015 at 10:46 pm

Okay, got it..
I believe, I might have seen this error earlier.
Try this – undeploy the index, deploy, update and then crawl again.

Reply

James Albert September 2, 2015 at 12:09 am

i already tried that a couple of time. even deleteng on DEPLOY_OBJ . but it still doesnt work.
by the way our ptools version is 8.53.09

User5800 August 15, 2017 at 1:15 pm

Hi Apurva,

I’m also struggling with the same error. (EQP-80317: HTTP connect attempt failed after 3 attempts.). Would you please help me resolve this error.

Thanks

Reply

Apurva T. August 21, 2017 at 10:03 am

Did you verify that your IB is working okay?

Reply

elraff January 28, 2016 at 10:26 am

Hi Apurva,
Do you know how can I make this process PTSF_GENFEED not to be kicked anymore on certain environments?
We got SES in prod environment but not in the rest. However, the process is kicked everyday, ending in No Success.

rgds

Reply

Carrie March 24, 2016 at 10:00 am

Great article!!! Thx, from a totally novice user!

Reply

Srini April 25, 2017 at 5:52 am

I am also facing the same issue. James, are you done with this issues and what was the solution you applied for this ?

Regards,
Srini

Reply

apurva September 2, 2015 at 9:48 am

but did you try to update the index?

Reply

James Albert September 3, 2015 at 1:05 am

Hi

yes I tried updating the index it says No update Required.

Do you know what are the possible causes of this?

thank you for always replying 🙂

Reply

User1234 August 7, 2017 at 4:32 pm

Hi apurva,

The PTSF_GENFEED app engine is failing intermittently with the following error:

SES crawler status : Failed , restart AE after resolving the error (262,153) PTSF_GENFEED.SES_STAT.G BL.default.1900-01-01.Step01.OnExecute PCPC:6800 Statement:75

I would greatly appreciate your help. Thanks in advance.

Reply

Sai March 21, 2017 at 10:05 am

Hi James,,

We are facing the same issue, Could you please let me know how you resolved the issue?

Thanks in advance.

Reply

Apurva T. August 21, 2017 at 10:20 am

There can be several reasons for this. Which all things you’ve verified till now?

Reply

Cancel reply

Leave a Comment

Previous post:

Next post: