1. Implementing Recruiting
  2. Enable Oracle Search

Enable Oracle Search

Oracle Search is the default search engine for new and existing customers of Oracle Fusion Cloud Recruiting.

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 enabling Oracle Search. Refer to the Oracle Cloud Infrastructure Documentation for key concepts on how to refresh an environment.

Scenario 1: Upgrade without refresh

In this scenario, environments are upgraded without a refresh prior to the upgrade. The TEST environment isn’t refreshed from PROD or another TEST. This is generally referred as P2T or T2T.

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 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 a refresh

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

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: Refresh only without upgrade

In this scenario, TEST environments are only refreshed from another environment. The TEST environment is refreshed from PROD or another TEST. This is generally referred as P2T or T2T.

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

US Government Cage Customers

If you’re a US Government Cage customer, once the environments are updated to 21B and later releases,you need to immediately deactivate Oracle Search to revert to SemSearch.

You first need to change the profile option IRC_ELASTIC_SEARCH_ENABLED that will disable Oracle Search as the search engine for Oracle Recruiting.

  1. In the Setup and Maintenance work area, click the Tasks icon.
  2. Click Search.
  3. Search for the task Manage Administrator Profile Values.
  4. Click the task name.
  5. On the Manage Administrator Profile Values page, search for the profile option code IRC_ELASTIC_SEARCH_ENABLED.

  6. Set the profile value to "N" to disable Oracle Search.

  7. Click Save and Close.

Related Topics