Maintaining Oracle Search for Oracle Recruiting

Oracle Search is the default search engine for new and existing customers of Oracle Fusion Cloud Recruiting. Oracle Search needs to be maintained after an upgrade or Production to Test (P2T) or Test to Test (T2T).

With Oracle Search, these features become available:

Recruiters and hiring managers can find candidate profiles using advanced search filters and boolean expressions.
Recruiters and Hiring Team members can see candidates that they're responsible for when the Candidate Security for Candidate Search is enabled.
External candidates can see similar jobs when searching for jobs.
External candidates can search for jobs using a postal code.
External candidates can explore jobs using a map view
External candidates can see the distance between their selected location and the job location.
External candidates can use the Work Location, Organization, and Job Requisition filters.
External candidates can see job requisition flexfield values exposed by recruiters.

Consider these scenarios before upgrading or refreshing Oracle Search. See the Oracle Cloud Infrastructure Documentation for key concepts on how to refresh an environment.

Note: The info applies to Production and Non Production environments.

Scenario 1: Upgrade With No P2T (Production to Test) or T2T (Test to Test)

In this scenario, environments are upgraded without a P2T or T2T. The TEST environment isn’t refreshed from PROD or another TEST.

Run these scheduled processes:

Maintain Candidates and Job Requisitions for Search. Run every 15 minutes. This incremental indexing scheduled process will index any new requisition, candidate, and geography entities that are added going forward.
Index Candidate Attachments. Run every 15 minutes.
Load and Index Job Requisitions and Load and Index Candidates. Set the Upgrade Current Index indexing mode to make sure the index is up to date for new fields being introduced.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-jobapplication.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-savedsearch.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-requisition.

Scenario 2: Upgrade After P2T (Production to Test) or T2T (Test to Test)

In this scenario, environments are upgraded after a P2T or T2T. The TEST environment is refreshed from PROD or another TEST.

Cancel these scheduled processes:

Maintain Candidates and Job Requisitions for Search
Index Candidate Attachments

Run these scheduled processes one time sequentially:

Load and Index Master Geography Hierarchy
Load and Index Job Requisitions (with Drop and Recreate Index indexing mode)
Load and Index Candidates (with Drop and Recreate Index indexing mode)
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-jobapplication.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-savedsearch.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-requisition.

Run these scheduled processes at a frequency of 15 minutes:

Maintain Candidates and Job Requisitions for Search
Index Candidate Attachments

Scenario 3: P2T (Production to Test) or T2T (Test to Test) Only Without Upgrade

In this scenario, P2T or T2T has occurred with no upgrade.

Cancel these scheduled processes:

Maintain Candidates and Job Requisitions for Search
Index Candidate Attachments

Run these scheduled processes one time sequentially:

Load and Index Master Geography Hierarchy
Load and Index Job Requisitions (with Drop and Recreate Index indexing mode)
Load and Index Candidates (with Drop and Recreate Index indexing mode)
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-jobapplication.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-savedsearch.
ESS job to create index definition and perform initial ingest to OSCS. In the Index Name to Reingest field, enter this value: fa-hcm-requisition.

Run these scheduled processes at a frequency of 15 minutes:

Maintain Candidates and Job Requisitions for Search
Index Candidate Attachments