Continuing from Part 2 where I wrote about the configuration of SES and PeopleSoft integration we move on to the Administration of the PeopleSoft Search Framework.
Next we will use the Deploy/Delete Object page to deploy our first search definition to SES. Search definitions are created and maintained in PeopleSoft. Once the definition is deployed, we run the Application Engine PTSF_GENFEED via the Schedule Search Index page. This AE will create a special SES feed in PeopleSoft and schedule the SES crawler to crawl the feed. The following is quoted from the SES PeopleBook for 8.53
The Schedule Search Index page initiates the PTSF_GENFEED Application Engine program.
The Pre Processing Application Engine program defined for the search definition runs.
PTSF_GENFEED Application Engine program runs the query (PeopleSoft Query or Connected Query) associated with the search definition.
The output of the query becomes a data source for the Feeds Framework.
The Feeds Framework converts the query output to an Oracle RSS Schema format and writes the SES Feed to the Integration Broker queue, and the Deletion query defined for the Search Definition runs.
The Search Framework then creates an SES Schedule for the SES source associated with the search definition and sets the schedule disposition to “CRAWL immediately.”
The Post Processing Application Engine program defined for the search definition runs.
The SES Crawler, using the URL of the Integration Broker queue where the SES Feed is located, initiates the crawling of the SES Feed.
Let’s work through the exercise of setting up the Portal Registry aka Menu search index. This index is delivered in the 9.2 applications.
1. Navigate to PeopleTools –> Search Framework –> Administration –> Deploy/Delete Object
Scroll to the bottom of the the list of Search Definitions and select PTPORTALREGISTRY (# 29 in my case) and click deploy. Once successfully deployed the Deploy Status column will say Deployed.
Next we build the index data (the feed) and tell SES to crawl the data. In order to do this we run the Schedule Search Index job as previously mentioned.
2. Navigate to PeopleTools –> Search Framework –> Administration –> Schedule Search Index
Create a run control, naming it after your Search Definition and the Index type. Once created the run control options cannot be changed from what I’ve seen. You might name the run control something like PTPORTALREG_FULL. Select PTPORTALREGISTRY as the search definition and select Full index for the Indexing type. If you use the lookup it will only return deployed search definitions. There are two Indexing Type options, Full and Incremental. Full will be used for initial processing and possibly if you wanted to update the full index, otherwise it is recommended to run the incremental option. Oracle says:
It is recommended to create one run control for incremental indexing, scheduled to run very frequently, and create another run control for full index rebuilding set to run less frequently. For example, incremental indexing might run daily, where a full index rebuild may be set to run every six months.
I left Language Option on Base Language as I only have one language available. Click Run, and check process monitor to verify it completed successfully.
Once the job is complete lets check SES. Login to SES and go to the Sources tab of the Home tab. You should see your search source, then click the schedules tab, you should see that the index build was schedule for a one time run.
Once you’ve validated your search is working repeat the Schedule Search Index process creating a new Run Control for the incremental index. This time set this one up as a recurring job based on the frequency that you would like to have it updated.
In the 9.2 applications certain functions won’t work until you’ve deployed the Search Definition and built the Index. In HCM 9.2 let’s try to browse job openings in recruiting. Without the search properly deployed we get the following error in the Demo environment.
Lets follow the above steps to to Deploy and Build the Index.
Select HC_HRS_JOB_OPENING from the Search Definition list on the Deploy/Delete Object page.
Click deploy to send the definition to SES. Then let’s use the Schedule Search Index page to create the index and schedule the crawl of the feed.
Once the job is complete we can return to Recruiting –> Browse Job Openings and see if it worked.
Next up, some troubleshooting tips.