Session ID:

Prepared by:

Hybrid Cloud Integration -Connecting Taleo Enterprise Edition With E-Business Suite

10332

@klambert61

Kyle LambertSenior Director, SolutionsEiS Technologies, Inc. Kyle.Lambert@EiSTech.com

Abstract

Many Cloud implementations fail because the integration to other applications do not work.

This session addresses how one company approached the bi-directional integration of Taleo Enterprise Edition and E-Business Suite, connecting a Cloud application to an on premise suite.

2

Bad Joke Of The Day

What is the difference between

3

and

a Hippo?a Zippo?

Bad Joke Of The Day

and the other is a little lighter!!!!!

4

One is heavy

Agenda

• About the Presenters/Audience• About EiS Technologies, Inc.• How Has Integration Changed?• How Is Cloud Integration Different?• About The Company• About The Challenge• About The Fear• The Approaches Considered• The Integration Approach• The Transaction Flow• Changes Required To Applications• Changes Made To Taleo• The Integration Components• The Architected Solution• Keys To Success• Future Integrations Plans• Players in Cloud Integration Services• Questions & Answers

5

About The Presenters/Audience

• Presenter & Contributors:– Kyle Lambert – Senior Director, Solutions– Sumit Dahiya – Technical Director– Sreevalli Mellacheruvu – Solutions Engineer

• Audience Profile:– Running Taleo Enterprise Edition? Business Edition?– Considering Taleo EE? Taleo BE?– Running EBS?– Managers/Developers/Integrators?

6

About EiS Technologies, Inc.

7

At EiS Technologies, we create tangible value for our clients by providing powerful and cost effective solutions that enable efficiencies throughout the

organization.

From Reporting and BI, to integrations, implementations, and upgrades, we stand by our clients, both as partners,

trusted advisors, and friends.

How Has Integration Changed?

• Better tools– Data mapping– Pre-defined methodologies– Pre-built libraries to leverage & build upon

• “Best of Breed” requires more integrations• The best of “Best of Breed” is always changing• Greater separation of technical & business analyst

skills• Increased variety of services with more complexity

& faster pace of change• Internet of Things (IoT) means more integrations

using less code for small transactions over limited bandwidth

8

How Is Cloud Integration Different?

• Less control over changes to Cloud services– Generally, customizations are not allowed

• Shortened implementation cycles are expected– Less time to react to changes

• More network considerations– Internet bandwidth– Secure protocols

• More security considerations– Handling Personally Identifiable Information (PII)– Multitenant environment

9

About The Company

• Part of the Hospital & Health Care industry• Leader in the developing, marketing and managing

senior living communities• Long time EBS user• New to Taleo

10

About The Challenge

• Streamline the business process to:– Assure timely transactions– Eliminate duplicate data entry– Reduce data errors

• Taleo acquired talent become EBS employees• EBS terminated employees become Taleo disabled

users• EBS new locations become Taleo new locations• Complete integration in production in 3 weeks

11

About The Fear

According to Oracle, in a recent study of more then 1,300 business leaders:•50% of companies has abandoned the use of at least 1 departmental cloud app in the last 3 years due to integration problems, and at a frequency of 1 app dropped per year•83% have been prevented from getting the best out of their departmental cloud applications – 25% blames poor integration•54% say project deadlines have been missed in the last 6 months due to cloud integration problems•68% of cloud adopters have attempted integration, 55%have tried and failed.

May-2013, http://www.oracle.com/us/dm/full-report-cloud-may-2013-1965502.pdf

The Client:•The Integration needed to be live with Taleo in 3 weeks

12

The Approaches Considered

• Direct Point-To-Point• On-Premise Integration Hub• Cloud Integration Hub• Hybrid Approach

13

The Integration Approach

• Build the integrations for re-use• Build like micro-services• Build for publish & subscribe potential• Integrations will be 2-way

– Extract à Transfer à Load à Confirm or Error• Integrations will be viewed as multiple pieces

– Connectors – Extractions– Transformations– Loads

• Identify mandatory fields of transaction destinations• Make the mandatory work before building up

14

The Transaction Flow

15

Flagged New Hires

New Locations

Terminated Employees

Changes Required To Applications

• In EBS, created an account for all integrations

• In Taleo, a number of additional fields were added

16

Changes Made To Taleo

Created UDF called ‘New Hire’ the recruiter marks when employees are to be picked up by the integration

17

Changes Made To Taleo

• Additional custom fields were created in order to pass required information to create employee assignments in EBS

• Used position to derive the information required to create employee assignment in EB, such as, the payroll pay basis, work location, organization, GRE, etc.

18

Changes Made To Taleo

• Created below selection list called City to capture the city and county details of employee’s residence. As EBS has an address validation and require the city value to be exact match.

• Used below Taleo standard field to record the employee number after the employment is created in EBS

19

Changes Made To Taleo

• Changed role from ‘Recruiter’ to ‘No Access’ when the employee is terminated on EBS

20

Changes Made To Taleo

• This is how locations appears in Taleo

21

The Integration Component: Connectors

• Create lightweight 2-way agents– Must be able to handle inbound and outbound data

• Manage security at a session level– Pass the username and password– Keeps security separate from transactions

• Can handle multiple methods of transactions– SOAP/WSDL APIs– REST/JSON APIs– PL/SQL Calls

• Can be used for multiple transactions

22

The Integration Component: Extractions

• Create generic extraction code– Allows source data to be used at multiple destinations– Data is extracted in the source native format

• Consider using triggers or business events to fire data transfers per transactions

• Can use scheduled jobs for bulk data transfers

23

The Integration Component: Transformations

• Convert from native source to destination specific:– Data formatting

• XML• CSV• Pipe delimited

– Data conversions• Perform data mapping conversions from DVM tables

– Data structuring• Ordering data as required

24

The Integration Component: Loads

• Use load programs compatible with the destination system

• Connectors should be able to support all the possible Load programs methods

• Various methods that need to be considered:– Taleo Connect Client– FTP– Web Services– APIs

25

The Integration Component: Confirmation or Errors

• Return a success or failure– The return message should be meaningful– Success message are simple– Errors need to be considered and deliberate

• Successes need to be logged at the source– The success should be meaningful and usable– Allow the user to confirm the success without needing

access to the destination system • Errors are logged on the integration engine

– Errors need to be meaningful and actionable– Capture errors at the integration server level

26

The Integration Component: Monitoring

• Need to have mechanisms to track the integration transactions

• Collecting and reporting transaction statistics – Total numbers of transactions by type over time– Successes versus failure– Elapsed time to complete transactions

• Create alerts and notifications when transactions are in error

• Reprocessing of transactions in error

27

The Architected Solution

28Co

nnec

tor

Transformation Import Data File(CSV)

HTTPSTaleo Connect Client

Errors

Extraction

Load(PL/SQL)

Confirmation

Monitoring

Connector

UsingTaleo ConnectClient(TCC)

DVM

Keys To Success

• Assemble End-To-End integration teams• The integration development team understood ALL

technical & functional aspects of the transactions:– EBS– Taleo – Integration

• Design from the Destination to the Source• Build from the Destination to the Source• First KISS, Then Go For Home Base

29

Future Integrations Planned

EBS to Taleo EE: – Address Information– Positions– Jobs– Organizations

30

Players in Cloud Integration Services

• SplashBI Integration Platform• Oracle Integration Cloud Services• Jitterbit Harmony• MuleSoft Anypoint Platform

31

Questions & Answers

32

Other EiS Technologies Sessions

33

April 10 3:30PM- 4:30PMHybrid Cloud Integration - Connecting Taleo Enterprise Edition With E-Business SuitePRESENTER(S):Kyle Lambert

April 11 10:30AM- 11:30PMHacks to Increase Social Media Reach in Taleo Business Edition RecruitPRESENTER(S):Suresh Pallapothu

April 11 12:45PM- 1:45PMGo Mobile! Taleo Mobile Enabled WebsitesPRESENTER(S):Austin Reason

April 11 2:00PM- 3:00PMANN INC- Hiring the Best by Removing Disparate Data Obstacles PRESENTER(S):Manny FueyoMarc Ramos

April 12 9:15AM- 10:15AMManaging Multiple Projects Within E-Business Suite Upgrade PRESENTER(S):Kyle Lambert

April 14 11:00AM- 12:00PMOracle Talent Management Cloud: Federal Implementation Lessons Learned PRESENTER(S):John Faucher

VendorSession

ReplacingDiscovererReports:Quickly.Accurately.InexpensivelyPRESENTER(S): KiranPasham

Hybrid Cloud Integration -Connecting Taleo Enterprise Edition With E-Business Suite

Many Cloud implementations fail because the integration to other applications do not work.

This session addresses how one company approached the bi-directional integration of Taleo Enterprise Edition and E-Business Suite, connecting a Cloud application to an on premise suite.