Description of the illustration integrate-taleo-ebs-sync.png

This image describes the flow of information between Oracle E-Business Suite and two cloud services. It consists of three boxes: one for Oracle Integration Cloud, one for Oracle Java Cloud Service, and one for Oracle E-Business Suite.

The central box illustrates the integrations in Oracle Integration Cloud that orchestrate the flow of information in to and out of the other components. In the first step in this flow, a scheduled integration in Oracle Integration Cloud sends a request (represented by a solid line) to the SOAP wrapper, deployed to an Oracle Java Cloud Service instance (represented by the second box at the top of the image). Next, the SOAP wrapper submits a Taleo Connect Client export job (also represented by a solid line). The Taleo Connect Client is also deployed to the Oracle Java Cloud Service host. Next, the Taleo Connect Client asynchronously exports new candidate records from Oracle Taleo Enterprise Cloud Service, saving the records to a .csv file to a staging location on the Oracle Java Cloud Service host. This asynchronous export is represented by a dotted line from the Taleo Connect Client to the staging folder.

Next, a solid line illustrates where the integration uses the FTP adapter to copy the exported file from the staging folder on the Oracle Java Cloud Service to a temporary folder on the Oracle Integration Cloud host. Next, another integration flow, using the Oracle E-Business Suite adapter, reads information for each candidate and imports this data into the Oracle E-Business Suite database using PL/SQL services exposed as REST APIs. This event is represented by a solid line connecting the EBS adapter node in the Oracle Integration Cloud box to the Oracle E-Business Suite box. An employee number, generated for each imported candidate, is returned with the response from Oracle E-Business Suite.

After Oracle Integration Cloud correlates employee numbers to candidate numbers for each imported record, it writes this information to a file. Using the FTP adapter, this file is transferred from the Oracle Integration Cloud host to the Oracle Java Cloud Service. This event is represented by a solid line connecting the FTP—Put File node in the integration to the staging folder node for Oracle Java Cloud Service. Finally, the integration triggers a Taleo Connect Client import job using the SOAP wrapper. This is represented by a solid line from the Invoke Import integration node to the SOAP wrapper node for Oracle Java Cloud Service. At this point, candidate records that were exported are updated with the employee number generated by Oracle E-Business Suite when they were imported.