Reference Architecture - Taleo Recruiting Cloud Data Replication into ADW : Using ODI Marketplace

June 30, 2020 | 19 minute read
Matthieu Lombard
Consulting Solution Architect
Text Size 100%:

Co-authors:

Profile photo for Balaji Krishnan

Balaji Krishnan, Product Management Architect, Analytics Apps

Profile photo for Ravi Guddanti

 

Ravi Guddanti, Principal Member of Technical Staff, Analytics Customer Excellence

 Background

This blog is the third in a series covering topics on how to utilize Oracle ETL / Data Integration tools to extract data from various data sources. Future blog topics will cover extracting from: Oracle SaaS Applications, Oracle on-premise applications (e.g. EBS), and other Oracle applications such as Taleo, Responsys, Eloqua and third party data sources like Salesforce or Workday.

The first blog detailed how to replicate Oracle Fusion SaaS data into ADW using ODI Marketplace and BICC.

The second blog detailed how to replicate Salesforce data into ADW using ODI Marketplace.

This blog walks though how to configure Oracle Data Integrator (ODI) on Oracle Cloud Marketplace to replicate data from Taleo Recruiting Cloud into an Autonomous Data Warehouse (ADW) database.

 

Suggested Prerequisite Reading Material:

* Using Oracle Cloud Marketplace

Overall prerequisites:

* Follow the steps in the first blog for instructions on:

Policies Assignment (Step 1)

SSH key-pair Generation (Step 4-b and 4-c)

ODI Marketplace Provisioning (Step 2)

ADW Configuration (Step 5-h, 5-i, 5-j and 6-d)

User/Policy/Key Requirements:

* It is strongly recommend to configure OCI and ODI with a local (non-Federated) user.

* The local OCI user must be granted these policies: "read buckets in compartment" and "manage objects in compartment".

Autonomous Database Requirements:

* The Autonomous Database needs access to Object Storage to retrieve the View Object extracts.

 Using Taleo Client Connect on Windows and Preparing the Extract

For details on how to set up Taleo Client Connect on Windows, please refer to Gerhard's blog here. The blog will go over the following steps

a) Connecting to the Taleo Cloud Service

This step will generate the default configuration board file under [TCC ROOT FOLDER]\system\default.configuration_brd.xml. This file contains the details about the Taleo instance to extract data from, such as the host name, the port, the type of authentication (if basic, username and encrypted password). It will be required by the Taleo Connect Client on Linux.

b) Exporting the Data

  • Defining the export: this step will generate a <export name>_sq.xml file. It will store all the details around the entities and attributes to be extracted and will be required by the Taleo Connect Client on Linux too.
  • Configuring the export: this step will generate a <export name>_cfg.xml file. It will store all the operational details of the export process, such as the export definition file location, the directory to store the response file, the format of the response file (CSV,..), the naming convention of the reponse file. This is the third fiel required by the Taleo Connect Client on Linux.
  • Validating the export with execution

c) Saving the configuration files required by the Linux Client

Make sure to take a copy of the three files above as they will help streamlining the Taleo Connect Client configuration on Linux.

 

 Installing and configuring Taleo Client Connect on the ODI Marketplace VM (Linux)

a) Downloading the binaries from edelivery

From the ODI Markeplace instance, open firefox and open the edelivery url.

Click on Sign In and enter your Oracle credentials