IB setup for Search Framework
- You need to have setup your Integration Gateway
and load the connectors
- You should define your Gateway Default App Server
and PeopleSoft Nodes in the Gateway Setup properties.
- On the Advanced Properties Page for the Gateway
Setup you should define a secureFileKeystorePasswd
- You Local Node should be active and when if you
ping it, it should come back with Success
- PUBSUB processes should be running on your application
server domain
- Verify that your Service Configuration is correct.
- Navigate to PeopleTools -> Integration
Broker -> Configuration -> Service Configuration
- Click Setup Target Locations
- Confirm the Web Services Target
Location references the correct URL for your system.
7. Configure Content RI and Portal URI text
specified on the portal tab for the default Local Node you
are working with.
This is required,
and you may get an error building your search index without it.
You should also
verify that the Service Operations needed for SES integration exist in your
system. ADMINSERVICE and ORACLESEARCHSERVICE should both
exist as Services.
Setting up PeopleSoft for Integration with SES
First thing you need to do, is to
assign the Search Framework roles (Search Administrator, Search Developer, Search
Server) to the user that is assigned to the default locale node.
Verify
that required permission lists (PTPT3100, PTPT3200, and PTPT3300) are present
on role PeopleSoft User.
Now navigate to Main menu –>
PeopleTools –> Search FrameWork –> Administration –> Search Instance
and create a Search Instance.
- Enter the SES server and port
- Enter the SES admin password you supplied during
installation of SES (eqsys/welcome1)
- Enter the Federation Trusted Entity and the password
you created earlier in SES (PS/PS)
- Enter the call back URL (endpoint of Integration
Broker) and the userid and password of the default locale node
Verifying
PeopleSoft and SES Connectivity
Now navigate to Main menu –> PeopleTools –> Search FrameWork
–> Utilities –> Diagnostics
Click Step
1: Ping Test. This should also work if your previous tests
worked. Once the Ping Test comes back it should make Step 2: Deploy an active link. You
should be able to continue through to Step 4: Search and
everything should work.
Create & Deploy Search Indexes
Now you
have successfully completed the installation and configuration of the
integration between SES and PeopleSoft.
You now have to ‘create search
collections in PeopleSoft ‘and ‘feed
these collections to SES’.
PeopleSoft Search Framework uses PSQuery and Connected Query as search
collections.
Some search collections have
already been supplied with the Feature Pack (Eg: HCM 9.1 FP2). If not you will
have to create a Query and create a Search Index with the Query as input and
then choose which Query fields should be indexed as keywords.
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.
Navigate to Main menu –> PeopleTools –> Search FrameWork –> Administration
–> Deploy/Delete Object. Scroll
to the bottom of the list of Search Definitions and select
PTPORTALREGISTRY 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.
Navigate to PeopleTools –> Search Framework –> Administration –>
Schedule Search Index. Create a run control for each search index you want
to publish to SES. 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. I left Language Option on Base Language as I only have one language
available. Click Run.
You can then schedule this and
check process monitor to verify it completed successfully. This is to keep SES and PeopleSoft in sync. Once
the job is completed, login to SES and go to the Sources tab of the Home
tab. You should see your search source, and then click the schedules tab;
you should see that the index build was schedule for a one time run.
In the 9.2 applications certain
functions won’t work until you’ve deployed the Search Definition and built the
Index. It will throw an error like below screenshot.
Enable Global Search & Keyword Component Search
Now you have seeded SES with PeopleSoft data. You now need to
enable the search feature in PeopleSoft. This can be done on two places.
To enable Global Search navigate to Main menu –> PeopleTools –> Portal –> General Settings and
check Display global search in header. This will enable the embedded
search in the portal banner. Make sure users have search indexes
assigned through permission lists; otherwise they will not be able to run
searches.
This is a new tab in the Permission
lists page in People Tools 8.52.
To enable Keyword search on
Component Search pages, open the search index by navigating to PeopleTools –> Search FrameWork –>
Designer –> Search Definition and on the last tab select the components
where you want to add the Keyword search. This will change your search page
with a new tab enabling Keyword Search.
I have replicated this post @ http://www.citagus.com/citagus/blog/oracle-ses-installation-configuration/