taleo connect client - oracle · taleo connect client 1-1 introduction taleo connect platform taleo...

Taleo Connect Client

Version 2.2.1

January 2007

Taleo Connect Client i

Confidential Information

Confidential Information

It shall be agreed by the recipient of the document (hereafter referred to as “the other party”) that confidential information disclosed by Taleo through its documents shall be retained in confidence by the other party, and its respective employees, affiliates and/or subsidiaries, pursuant to the following terms and conditions:

For the purpose herein, the term “Confidential Information” shall mean the following:

1. Any information, know-how, data, process, technique, design, drawing, program, formula or test data, work in process, business plan, sales, suppliers, customer, employee, investor or business information contained in a document, whether in written, graphic, or electronic form; or

2. Any document, diagram, or drawing which is either conspicuously marked as “Confidential”, known or reasonably known by the other party to be confidential, or is of a proprietary nature, and is learned or disclosed in the course of discussions, demonstrations, or other collaboration undertaken between the parties.

© 2007 Taleo Corporation. Do not reproduce without the written permission of Taleo Corporation.

Table of Contents Introduction

Taleo Connect Client ii

Tab le o f Conten ts

IntroductionTaleo Connect Platform...................................................................1-1

Taleo Integration Offering ................................................................... 1-1Product Overview ...........................................................................1-2

Development Environment .................................................................. 1-2Integration Engine .............................................................................. 1-2Feature Packs .................................................................................... 1-3Documentation Strategy ..................................................................... 1-3

Business CasesWelcome Wagon ............................................................................2-1

Business Need ................................................................................... 2-1Taleo Connect Solution ....................................................................... 2-1

ERP System Update ........................................................................2-2Business Need ................................................................................... 2-2Taleo Connect Solution ....................................................................... 2-2

Global Recruiting ............................................................................2-3Business Need ................................................................................... 2-3Taleo Connect Solution ....................................................................... 2-3

Development EnvironmentEclipse RCP Framework ..................................................................3-1

Underlying Concepts .......................................................................... 3-1Design Perspective .........................................................................3-2

Configuration Editor ........................................................................... 3-2Export Editor ...................................................................................... 3-2Import Editor ...................................................................................... 3-2

Runtime Perspective .......................................................................3-3Console Perspective .......................................................................3-4

Message List Viewer .......................................................................... 3-4

Integration EngineWorkflow Concept ..........................................................................4-1

Table of Contents Processing

Taleo Connect Client iii

Workflow Type ...............................................................................4-2Communication Types ........................................................................ 4-2Message Types .................................................................................. 4-2

Configuration .................................................................................4-4Runtime.........................................................................................4-5

Execution .......................................................................................... 4-5Monitoring ......................................................................................... 4-5Logging ............................................................................................. 4-6Error Handling ................................................................................... 4-6Temporary Files ................................................................................. 4-8

Monitoring .....................................................................................4-9Configuration ..................................................................................... 4-9Monitoring Information ..................................................................... 4-11Default Monitoring ........................................................................... 4-13

Alerting........................................................................................4-14Configuration ................................................................................... 4-14

HTTP Proxy ..................................................................................4-17

ProcessingPre-processing Steps......................................................................5-1

Convert Encoding ............................................................................... 5-1Validate Encoding .............................................................................. 5-1Prepare Export ................................................................................... 5-1Prepare Import ................................................................................... 5-1Wrap SOAP ....................................................................................... 5-1Generate ID ....................................................................................... 5-1Custom Steps .................................................................................... 5-2

Processing Steps............................................................................5-3Endpoint Information .......................................................................... 5-3Authentication Information .................................................................. 5-3Quality Information ............................................................................. 5-3

Post-processing Steps ....................................................................5-4Strip SOAP ........................................................................................ 5-4Convert Encoding ............................................................................... 5-4Transform Import Results ................................................................... 5-4Transform Export Results .................................................................... 5-4Transform Using XSL .......................................................................... 5-4Transform Using Java (deprecated) ..................................................... 5-5Custom Steps .................................................................................... 5-5

Business Case ImplementationsWelcome Wagon ............................................................................6-1

Table of Contents Appendices

Taleo Connect Client iv

Business Requirements ...................................................................... 6-1Taleo Connect Solution ....................................................................... 6-1

ERP System Update ........................................................................6-5Business Requirements ...................................................................... 6-5Taleo Connect Solution ....................................................................... 6-5

Global Recruiting ............................................................................6-9Business Requirements ...................................................................... 6-9Taleo Connect Solution ....................................................................... 6-9

AppendicesTaleo Connect Client Installation ......................................................A-1

Account Creation ............................................................................... A-1Environment Files .............................................................................. A-1Connection Authorization .................................................................... A-1Pre-installation .................................................................................. A-2Installation ......................................................................................... A-2Feature Pack Delivery ......................................................................... A-2Using the Client ................................................................................. A-2

Migration .......................................................................................A-3Version 2.1 ........................................................................................ A-3Version 2.0 ........................................................................................ A-4Version 1.0 ........................................................................................ A-5

Volume Limits ................................................................................A-7Taleo Connect Client Self-Service Tools ............................................... A-7

How to Execute Taleo Connect Client from a Java Application ...........A-8Execution Environment ....................................................................... A-8Execution Entry Point .......................................................................... A-9

Taleo Business Edition ..................................................................A-10Account Creation ............................................................................. A-10Environment File .............................................................................. A-10

I n t r o d u c t i o n

Taleo Connect Client 1-1

Introduction Taleo Connect Platform

Taleo Connect Platform

Taleo Integration Offering

Al l Ta leo p roduc ts have an i n tegra t ion o f fe r ing t ha t a l l ows sys tem- to-sys tem in te rac t i on w i th the cus tomer . Th is o f fe r i ng con ta ins a d ic t i ona ry and a se t o f se rv i ces .

The d ic t iona ry con ta ins the descr ip t ion o f the bus iness en t i t i es t ha t a re exposed fo r da ta ex t rac t i on . I t a l so de f ines the f i e lds and re la t ions o f each en t i t y w i th the i r d i f f e ren t charac te r i s t i cs (mu l t i l i ngua l o r no t , da ta t ypes , e tc . ) .

The serv i ces g roup the ava i l ab le opera t i ons by bus iness func t ion . Each opera t i on can be invoked w i th a se t o f paramete rs to execute i ns t ruc t ions fo r the Ta leo p roduc ts .

For examp le the Ta leo Pro fess iona l p roduc t con ta ins the Candidate en t i t y i n i t s d i c t i onary w i th f i e lds such as EmailAddress and HomePhone. I t a l so o f fe rs a Requisition se rv ice w i th opera t ions such as create, update and cancel.

Taleo Connect ServerThe Ta leo Connect Se rve r i s the server -s ide po r t i on o f the Ta leo Connec t P la t fo rm embedded w i th in the Ta leo p roduc ts . I t enab les the p roduc ts to expose the i r in teg ra t i on o f fe r i ng th rough a secure ga teway us ing sys tem- to-sys tem t ype messages . The Ta leo Connect Se rve r expor t f ea tu re a l l ows access to the Ta leo p roduc t ' s d ic t i onary and i t s impor t f ea tu re accep ts ins t ruc t ions to i nvoke serv i ce opera t ions . The Ta leo Connec t Server on l y accepts messages in the p rop r ie ta r y T-XML fo rmat wrapped in a s tandard SOAP enve lope w i th Ta leo ex tens ions (named T-SOAP) .

Taleo Connect ClientThe Ta leo Connect C l i en t i s the c l i en t-s ide por t i on o f the Ta leo Connec t P la t fo rm tha t res ides in a cus tomer 's env i ronment . I t i s the co rne rs tone o f the Ta leo se l f - serv i ce in teg ra t i on approach , enab l ing cus tomers to bu i l d and execute the i r own in teg ra t i on p rocesses . The techn ica l aspec ts o f the in tegra t i on o f fe r ing a re abs t rac ted by des ign ing the in teg ra t ion processes us ing a p ro fess iona l use r i n te r face and execu t ing them w i th p repackaged sc r ip ts ( ava i lab le fo r bo th Windows and UN IX /L INUX p la t fo rms) .

Taleo Web ServicesFor some cus tomer imp lementa t i ons , the in te rac t i on w i th the Ta leo p roduc t m igh t be th rough a por ta l -l i ke a rch i tec tu re . I n th i s case , the Ta leo p roduc ts expose some o f the in teg ra t i on o f fe r ing se rv i ce opera-t ions th rough indus t r y s tandard web se rv ices .

P lease consu l t you r account execut i ve o r the re levan t documenta t i on on th is sub jec t .


Introduction Product Overview

Product Overview

The Ta leo Connec t C l i en t comb ines :

• A use r - f r i end ly and p ro fess iona l deve lopment env i ronment to des ign and con f igure s imp le to comp lex in teg ra t ion scenar ios .

• A power fu l and f l ex ib le work f low- l i ke in tegrat ion eng ine t ha t can communica te w i th the Ta leo env i ronment us ing mu l t ip le f i l e fo rmats .

Development Environment

The Ta leo Connect C l ien t ' s des ign and conf igu ra t ion env i ronment i s bu i l t w i th the power fu l and ex ten-s ib l e R ich C l i en t P la t fo rm (RCP) f rom the Ec l ipse foundat ion . RCP i s the s tandard fo r Java c l i en t use r i n te r face deve lopment o f fe r ing a p ro fess iona l g rade exper ience to the end use r .

The Ta leo Connect C l i en t o f fe rs the user th ree pe rspec t i ves :

1 . Design: Bu i l d impor t and expor t spec i f i ca t ions and c rea te comp lex in teg ra t i on p rocesses us ing a work f l ow- l i ke eng ine .

2 . Runtime: Execu te the in tegra t i on p rocess w i th the c l i ck o f a bu t ton , see the p rog ress o f the p rocess , and ana ly ze the resu l t s .

3 . Console: Mon i to r the in teg ra t i on p rocesses runn ing w i th in the Ta leo p roduc ts .

A l l t he use r tasks a re e i the r w i za rd d r i ven o r based on na tu ra l c l i en t app l i ca t i on behav io r such as drop-down menus and d rag-and-drop func t iona l i t y .

The Ta leo Connect C l ien t sh ips w i th a number o f f ea tu re packs tha t con ta in the fu l l bus iness mode l o f the va r i ous Ta leo produc ts and s tandard con ten t fo r easy imp lementa t i on o f impor t and expor t p rocesses .

Integration Engine

The Ta leo Connec t C l i en t communica tes w i th Ta leo produc ts us ing the propr ie ta ry Ta leo message fo rmat tha t i s based on indus t r y s tandards such as XML, SOAP, and WS-Address ing . I t a l so suppor ts cus tom message fo rmats th rough c l i en t -s ide o r server-s ide t rans fo rmat ions s ince cus tomer sys tems usua l l y on l y suppor t the i r own fo rmats .

The Ta leo Connect C l ien t sh ie lds the comp lex i t y o f the asynchronous i n tegra t ion p rocess f rom the cus tomer and prov ides a synchronous- l i ke behav io r tha t can in tegra te i n to o the r bus iness p rocesses .


Introduction Product Overview

Feature Packs

The in teg ra t ion o f fe r ing o f a Ta leo P roduc t can be accessed w i th in the Ta leo Connec t C l ien t us ing a f ea tu re pack . Fea tu re packs a re ava i l ab le fo r a l l Ta leo P roduc ts , a l though they m igh t be d i s t r i bu ted separa te l y ( see de ta i l s in sec t ion be low) .

A fea tu re pack i s l i nked to a spec i f i c ve rs ion o f a Ta leo produc t s ince the o f fe r ing o f ten expands w i th each So lu t i on Pack p rov ided . For examp le , the d ic t i onary fo r the Ta leo Pro fess iona l 7 .0 .2 and Ta leo P ro fess iona l 7 .0 .3 fea tu re packs a re the same, bu t seve ra l new opera t i ons were added w i th So lu t i on Pack 3 , i nc reas ing the se rv i ce o f fe r ing .

When c rea t ing e i ther impor t o r expor t spec i f i ca t i ons , i t i s mandato ry to se lec t a fea ture pack . In the same way , con f igura t i on f i l es a l so depend on fea ture packs and w i l l on l y execute spec i f i ca t i ons bu i l t on the same p roduc t vers ion .

Documentation Strategy

There a re th ree documents ava i l ab le fo r the Ta leo Connect C l i en t . Each addresses a pa r t i cu la r need and aud ience .

User guideTh is document o f fe rs a h igh- leve l ove rv iew o f the Ta leo Connect C l ien t and an in -dep th look a t the func t i ona l concep ts i nvo l ved in c rea t ing and execu t ing in teg ra t i on p rocesses . I t i s addressed to anyone in te res ted in work ing w i th the Ta leo Connec t C l i en t and shou ld be cons ide red mandato ry read ing be fo re ins ta l l i ng o r us ing the p roduc t .

Online helpThe on l ine he lp inc luded w i th the Ta leo Connect C l ien t de ta i l s a l l aspec ts o f the app l i ca t i on . Each perspec t i ve , ed i to r , v i ew , and p re fe rence i s documented . A l l o f the regu la r f ea tures o f on l i ne he lp a re o f fe red : t ab le o f con ten ts , search ing , and bookmarks . As we l l , mos t o f the p roduc t f ea tu res suppor t con tex tua l he lp by us ing the spec ia l He lp v iew.

Training presentationTh is document o f fe rs a hands-on and sequen t ia l approach to desc r ib ing the Ta leo Connect C l i en t . The ove rv iew cove rs the fea tu res mos t l i ke l y needed in s tandard in tegra t i on p rocesses .

B u s i n e s s C a s e s


Business Cases Welcome Wagon

Welcome Wagon

Th is i s the f i r s t o f th ree ac tua l bus iness cases tha t we w i l l p resent to he lp cus tomers qu ick l y and e f f i c ien t l y address the i r i n teg ra t i on needs . To l earn how the ac tua l imp lementa t i on o f the in teg ra t i on p rocesses wou ld occur fo r th i s spec i f i c bus iness case , go to the Bus iness Case Imp lementa t i ons chap ter , We lcome Wagon sec t i on .

Business Need

Amer ican Compute rs , I nc . i s a m id-s i ze company l oca ted in De t ro i t , M I tha t p r ides i t se l f i n i t s pe rsona l t ouch w i th regards to human resources . As w i tness to th i s commi tment , each and every new employee rece i ves a we lcome baske t p rov ided by a l oca l re ta i l e r , G i f t s On Reques t . The company h i res a few dozen peop le eve ry week and needs to send the i r address in fo rmat ion to G i f t s On Reques t i n a M ic roso f t Exce l f i l e . So Amer ican Compute rs , Inc . must f ind a way to ex t rac t the name, address , and phone numbers o f the emp loyees h i red in the l as t week and prov ide th i s i n fo rmat ion to G i f ts On Reques t .

Taleo Connect Solution

S ince Amer ican Compute rs , I nc . uses the Ta leo P ro fess iona l p roduc t to hand le the rec ru i t i ng pa r t o f i t s human resource management , a l l o f the requ i red i n fo rmat ion i s access ib le th rough the Ta leo Connect Server embedded in th i s p roduc t . The Ta leo Connect C l i en t can access the employee l i s t by send ing a T-SOAP1 message con ta in ing a Ta leo SQ-XML2 ex t rac t i on exp ress ion de f in ing the proper c r i t e r i a . The name, address , and , phone numbers o f the new emp loyees can then be saved to CSV f i l e f o rmat tha t can be opened d i rec t l y in M ic roso f t Exce l . The IT Depar tment o f Amer ican Compute rs , Inc . can con f igu re the Ta leo Connec t C l i en t to execute th i s p rocess w i th the in fo rmat ion p rov ided by Ta leo cus tomer suppor t .

1 . T a l e o u s e s a p r o p r i e t a r y e x t e n s i o n o f t h e i n d u s t r y s t a n d a r d S O A P m e s s a g e f o r m a t c a l l e d T - S O A P . T h i s f o r m a t i s t r u l y a n e x t e n s i o n a s a l l T - S O A P m e s s a g e s a r e a l s o S O A P m e s s a g e s . T h e e x t e n s i o n c o v e r s c e r t a i n h e a d e r e l e m e n t s r e q u i r e d t o c o m m u n i c a t e w i t h t h e T a l e o e n v i r o n m e n t a n d t h e s p e c i f i c a t i o n o f t h e b o d y a s T a l e o i n t e g r a t i o n i n s t r u c t i o n s .

2 . T h e T a l e o C o n n e c t P l a t f o r m u s e s a p o w e r f u l a n d f l e x i b l e p r o p r i e t a r y q u e r y l a n g u a g e c a l l e d S Q - X M L t o e x t r a c t d a t a f r o m t h e v a r i o u s T a l e o p r o d u c t s . M o r e i n f o r m a t i o n a b o u t t h i s l a n g u a g e i s a v a i l a b l e o n t h e T a l e o w e b s i t e i n t h e i n t e g r a t i o n s e c t i o n .


Business Cases ERP System Update

ERP System Update

Th is i s the second o f th ree ac tua l bus iness cases tha t we w i l l p resen t t o he lp cus tomers qu ick l y and e f f i c ien t l y address the i r i n teg ra t i on needs . To l earn how the ac tua l imp lementa t i on o f the in teg ra t i on p rocesses wou ld occur fo r th i s spec i f i c bus iness case , go to the Bus iness Case Imp lementa t i ons chap ter , ERP Sys tem Upda te sec t ion

Business Need

Cass i v i Too ls i s a b lue-co l l a r i ndus t r y f rom the hear t l and tha t spec ia l i zes in l a rge manu fac tu r ing equ ip-ment . They have been runn ing a commerc ia l ERP sys tem fo r the i r supp ly cha in management fo r severa l yea rs and a l so use the same sys tem as a human resource sys tem o f reco rd . They recen t l y subscr ibed to the Ta leo P ro fess iona l p roduc t to op t im i ze the i r rec ru i tment p rocess and to s ta r t mov ing to In te rne t -based techno logy . Because o f cos t and l egacy i ssues , the ERP sys tem rema ined the sys tem o f record fo r a l l new ly h i red emp loyees . The ERP sys tem does no t suppor t web se rv ices and requ i res a p rop r ie ta r y tex t f i l e f o rmat to impor t emp loyee da ta . Wi th the cu r ren t I T res t r i c t i ons a t Cass i v i Too l s , the on l y way to submi t a tex t f i l e t o upda te the ERP sys tem is th rough an FTP s i te access ib le on l y w i th in the in te rna l co rpora te ne twork .


As in the preced ing example , the Ta leo Connec t C l i en t can eas i l y access the requ i red in fo rmat ion us ing an appropr ia te T-SOAP reques t message con ta in ing an SQ-XML ex t rac t i on express ion . The Ta leo Connec t Server on l y suppor t s s tandard XML and CSV fo rmats , bu t th i s i s no t a p rob lem because the Cass i v i Too l s I T Depar tment can use the p rov ided XSL t rans fo rmat ion fea ture in the Ta leo Connec t C l i en t to conve r t the employee in fo rmat ion in to the p rop r ie ta ry l egacy fo rmat o f the ERP sys tem. F ina l l y , the IT Depar tment can cus tomize the de fau l t behav io r o f the Ta leo Connect C l i en t to t rans fe r the re t r i e ved in fo rmat ion to the ERP sys tem's FTP s i te .


Business Cases Global Recruiting

Global Recruiting

Th is i s the th i rd o f th ree ac tua l bus iness cases tha t we w i l l p resent t o he lp cus tomers qu ick l y and e f f i c ien t l y address the i r i n teg ra t i on needs . To l earn how the ac tua l imp lementa t i on o f the in teg ra t i on p rocesses wou ld occur fo r th i s spec i f i c bus iness case , go to the Bus iness Case Imp lementa t i ons chap ter , G loba l Recru i t ing sec t ion

Business Need

RC Marke t ing i s a smal l bu t g loba l adve r t i s ing company tha t f requent l y h i res con t r ibu to rs f rom a l l ove r the wor ld . They make ex tens i ve use o f Ta leo P ro fess iona l ’ s mu l t i l i ngua l caree r s i t es to a t t rac t the bes t peop le in the i r own language . There fo re , the requ is i t i ons ( j ob o f fe rs ) must be t rans la ted in to seve ra l l anguages . To do th is e f f i c i en t l y , RC Marke t ing ou tsources th i s work . The ou tsourcers re tu rn the t rans la-t i ons to RC Marke t ing in an Exce l sp readshee t . RC Marke t ing wou ld l i ke an au tomated way to upda te the i r ex i s t ing requ is i t i ons in a l l r equ i red languages w i thou t hav ing to copy and pas te the tex ts manua l l y in to the Ta leo P ro fess iona l S ta f f i ng WebTop .


The Ta leo Connect C l ien t fu l l y suppor t s up load ing in fo rmat ion in to Ta leo p roduc ts f rom Exce l sp read-sheets saved as CSV ( cha rac te r o r comma separa ted va lues ) f i l es . I n add i t i on , the fea tu re pack fo r the Ta leo P ro fess iona l 7 .0 inc ludes s tandard spec i f i ca t i ons fo r requ is i t i on impor ts tha t can eas i l y be adap ted to th i s pa r t i cu la r case .

D e v e l o p m e n tE n v i r o n m e n t


Development Environment Eclipse RCP Framework

Eclipse RCP Framework

The Ta leo Connect C l i en t i n teg ra t i on deve lopment env i ronment i s based on the Ec l i pse founda t ion 's R ich C l i en t P la t fo rm pro jec t (h t tp : / /www.ec l i pse .o rg ) . I t i s impor tan t t o unders tand the under l y ing concep ts o f th i s f ramework be fo re go ing th rough the fea tu res in the Ta leo Connec t C l i en t .

Underlying Concepts

A perspec t i ve i s a l og ica l g roup ing o f e lements tha t o rgan i zes the work fo r the use r i n a c lear and unc lu t -te red fash ion ( inc lud ing v iews , too lba rs , and menu i t ems ) .

An ed i to r i s a user i n te r face tha t a l l ows a user to c rea te and upda te a par t i cu la r par t o f the in teg ra t i on p rocess . Mu l t i p l e ed i to r t ypes and ins tances may be opened in a s ing le pe rspec t i ve .

A v iew i s a read-on l y aux i l i a r y e lement tha t o f fe rs in fo rmat ion about the ac t i ve ed i to r . As such , v i ews reac t to se lec t i ons w i th in the ac t i ve ed i to r and to changes to d i f f e ren t ed i to r i ns tances .

A pre fe rence i s a se t t i ng tha t a f fec ts the use r expe r ience w i th in the app l i ca t i on . A l l p re fe rences have a de fau l t va lue se t by Ta leo tha t can be changed by the use r and prese rved be tween work sess ions .

http://www.eclipse.org


Development Environment Design Perspective

Design Perspective

The des ign perspec t i ve i s where the in tegra t i on p rocess work f l ow i s bu i l t and where you de te rmine how to ex t rac t i n fo rmat ion f rom o r up load in fo rmat ion to the Ta leo env i ronment . A spec i f i c ed i to r i s o f fe red fo r each o f these ac t i v i t i es .

Configuration Editor

The con f igu ra t i on ed i to r enab les the user to c rea te the ac tua l i n teg ra t i on process tha t sends the reques t f i l e t o the Ta leo p roduc t and re t r i eves the response f i l e . Th i s work f l ow may inc lude one o r more p re- o r pos t -process ing s teps , wh ich reduce dependency on p ropr i e ta r y Ta leo fo rmats .

Export Editor

The Expor t Ed i to r uses a bus iness mode l f rom a par t i cu la r Ta leo produc t t o c rea te a spec i f i ca t ion fo r i n fo r -mat i on to be ex t rac ted . Each expor t i s based on a roo t en t i t y f rom wh ich a l l f i e lds and re la t i ons a re de f ined. Expor t s suppor t any number o f f i l t e r i ng c r i t e r ia and so r t ing keys , and suppor t mu l t i l i ngua l and cus tom f i e lds .

Import Editor

The Impor t Ed i to r c rea tes a spec i f i ca t i on to up load CSV (charac te r o r comma separa ted va lues ) f i l es i n to a Ta leo produc t . Each co lumn in the CSV f i l e i s assoc ia ted w i th a f i e ld i n the pa r t i cu la r Ta leo p roduc t bus iness mode l . As w i th the Expor t Ed i to r , each ins tance i s l i nked to a spec i f i c roo t en t i t y i n the mode l . Impor t spec i f i ca t i ons a l so o f fe r suppor t o f mu l t i l i ngua l and cus tom f i e lds .


Development Environment Runtime Perspective

Runtime Perspective

The run t ime pe rspec t i ve i s most l y used du r ing the deve lopment o f a new in teg ra t i on process . W i th a s ing le c l i ck , you can execute an i n tegra t ion work f low, as de f i ned in a con f i gu ra t i on f i l e , to p rocess a par t i cu la r reques t message in to a response f i l e . The p rog ress o f the work f l ow can be fo l l owed f rom a s t y l ed HTML mon i to r ing v iew . Reques t and response f i l es can be accessed v ia ex te rna l t ex t o r f i l e ed i t i ng app l i ca t i ons . In a p roduc t ion env i ronment , th i s t ype o f p rocess wou ld be t r i gge red by a sys tem event o r a t imed task . As such, the execu t i on wou ld no t occur th rough the use r i n te r face .


Development Environment Console Perspective

Console Perspective

The conso le perspec t i ve i s an op t i ona l pa r t i n the in teg ra t i on p rocess and o f fe rs a rea l - t ime v iew o f a l l i n teg ra t i on p rocesses be ing hand led by a Ta leo p roduc t ( t ha t has a Ta leo Connec t Serve r embedded ) . Th is perspec t i ve d i s t i ngu i shes be tween the message and the document conta ined in the message . The fo rmer be ing the communica t i on wrapper fo r the la t te r tha t ac tua l l y con ta ins the bus iness ins t ruc t ions as ind i v idua l records .

Message List Viewer

The conso le perspec t i ve uses a s ing le ed i to r , the message l i s t v i ewer , tha t l i s t s a l l t he messages in a Ta leo p roduc t match ing a pa r t i cu la r c r i te r ia . Th is perspec t i ve o f fe rs mu l t i p le v iews tha t ana l yze each message f rom d i f f e ren t ang les .

I n t e g r a t i o n E n g i n e


Integration Engine Workflow Concept

Workflow Concept

The Ta leo Connect C l ien t i s bu i l t as a h igh ly spec ia l i zed work f l ow eng ine based on the s tandard reques t - response message exchange pa t te rn .

Each in tegra t ion p rocess i s de f ined by a workf low conf igurat ion t ha t spec i f i es a sequence o f steps tha t each con t r i bu te to the exchange o f i n fo rmat ion be tween the cus tomer and the Ta leo env i ronment . The work f l ow con f igura t i on a l so de f ines the behav io r o f the Ta leo Connect C l i en t i n regards to mon i to r ing and a le r t i ng .

Each ins tance o f an in tegra t i on process i s represen ted by a workf low execut ion .

Dur ing a pa r t i cu la r work f l ow execu t ion , a pipe l ine i s t rans fe r red be tween each s tep con ta in ing in fo rma-t i on on the cur ren t s ta te o f the reques t and response messages . I n add i t i on to the cur ren t p ipe l i ne , each s tep has access to the work f l ow con f igu ra t i on when execu t ing i t s par t i n the ove ra l l i n tegra t i on p rocess .

Each work f low execut i on p roduces a workf low resu l t t ha t can be mon i to red du r ing and a t the comp le t i on o f the overa l l i n tegra t i on p rocess .


Integration Engine Workflow Type

Workflow Type

The Ta leo Connect C l i en t suppor ts seve ra l t ypes o f i n tegra t ion p rocesses . Each work f low t ype i s de f ined by the commun ica t ion s t ra tegy and the message t ype (o r f o rmat ) . Ta leo recommends us ing the Product communica t i on t ype and the T-SOAP message t ype .

Communication Types

The commun ica t ion t ype de f i nes where the in teg ra t i on ins t ruc t ions a re sen t w i th in the Ta leo env i ronment .

ProductThe reques t message i s sen t d i rec t l y to the ta rge t Ta leo p roduct . A f te r the message i s p rocessed , the response message can be re t r i eved f rom the Ta leo produc t i t se l f .

MiddlewareThe reques t message i s sen t to the gener ic ga teway o f our m idd leware p la t fo rm. The message i s then ana l y zed , ver i f i ed , t rans fo rmed ( i f needed) , and rou ted to the p roper Ta leo p roduc t . The response message i s a l so re t r i eved f rom the midd leware env i ronment , poss ib l y a f te r o the r t rans fo rmat ions .

Mixed (deprecated)The reques t message i s sen t to the m idd leware and rou ted to the Ta leo p roduc t . The response message i s then re t r i eved d i rec t l y f r om the ta rge t Ta leo produc t .

Th i s op t ion i s no t recommended because the two f i r s t commun ica t i on t ypes a lmost a lways o f fe r be t te r in teg ra t i on cond i t i ons .

Message Types

The message t ype de f i nes how the in teg ra t i on i ns t ruc t ions a re sen t to the Ta leo env i ronment . Th i s p laces NO l im i ta t i ons on the fo rmat o f the o r ig ina l reques t message o r the f i na l response message . I t s imp ly descr ibes the messag ing fo rmat used be tween the Ta leo Connect C l i en t and the Ta leo env i ronment .

T-SOAPStandard Ta leo messages a re exchanged be tween the Ta leo Connect C l i en t and the Ta leo env i ronment . Any t rans fo rmat ions f rom or to cus tomer spec i f i c f o rmats and/o r encod ing occur w i th in the Ta leo Connect C l i en t work f l ow.

RS-XMLTh is i s the func t iona l equ i va len t to the T-SOAP case , except i t uses the legacy Ta leo message fo rmat . Th i s t ype i s ava i lab le mos t l y f o r backwards compat ib i l i t y reasons . Un less recommended by Ta leo techn ica l s ta f f , new in teg ra t i on pro jec ts shou ld use the T-SOAP message t ype .


Integration Engine Workflow Type

Other FormatsThe messages exchanged w i th the Ta leo env i ronment cou ld be in any fo rmat o r encod ing . The t rans fo r-mat i ons requ i red—for p rocess ing the messages by Ta leo produc ts—must occur i n the Ta leo env i ronment i t se l f , as such , th i s op t i on i s on l y ava i l ab le fo r the Midd leware commun ica t ion t ype .


Integration Engine Configuration

Configuration

Work f lows can be c rea ted o r ed i ted us ing the Con f igura t ion Ed i to r w i th in the Ta leo Connect C l ien t . Each work f low requ i res a con f igura t ion to be execu ted ; however , depend ing on the comp lex i t y l eve l and the spec ia l i za t ion o f the p rocess ing , the same conf igu ra t i on can be used fo r seve ra l i n tegra t ion p rocesses .

The conf igu ra t ions a re saved to f i l es w i th *_cfg.xml ex tens ions fo r use a t execu t i on t ime. The exac t spec i f i ca t i ons o f the con f igura t i on XML s t ruc ture a re de f ined in the TaleoConnectClient.xsd schema.


Integration Engine Runtime

Runtime

Execution

I n a P roduc t i on env i ronment , a Ta leo Connect C l i en t work f low i s t yp ica l l y executed us ing a command l ine sc r ip t . The re a re th ree poss ib le uses ( they a re same fo r a l l opera t ing sys tems ; shown here fo r Windows) :

Examp les

The f i r s t examp le i s the t yp ica l use o f the Ta leo Connect C l i en t where bo th the reques t and response message f i l es a re spec i f i ed exp l i c i t l y . The work f low con f igu ra t i on usua l l y con ta ins on ly commun ica t ion in fo rmat ion tha t app l i es to a va r i e t y o f d i f fe ren t messages .

The second examp le i s t yp ica l o f a schedu led in tegra t i on process where the reques t message var i es and the response message f i l e i s genera ted based on the t imes tamp ( i .e . NewCandidates_2005-11-11.xml) .

The l as t examp le i s t yp ica l o f a spec ia l i zed work f l ow w i th ex tens i ve p re and/or pos t -p rocess ing tha t on l y app l i es to a s ing le i n teg ra t i on process . I n th i s s i tua t i on , the reques t and response f i l es a re o f ten known and can thus be spec i f i ed in the con f igu ra t i on i t se l f .

I t i s a l so poss ib l e to execu te a Ta leo Connec t C l i en t work f l ow f rom w i th in another Java app l i ca t i on . To do so , the hos t app l i ca t ion mus t match the env i ronment cons t ra in t s de f ined in the TaleoConnectClient.bat sc r ip t and invoke the com.taleo.integration.client.Client.execute() method .

Monitoring

The Ta leo Connec t C l i en t genera tes a work f l ow s ta tus a t the in i t i a l i za t i on o f a work f l ow execu t i on , a f te r each s tep and aga in a t the comp le t i on o f the work f l ow. Th i s s ta tus can be mon i to red in seve ra l ways , inc lud ing the raw XML ser i a l i za t i on o r p re-con f igu red tex t and HTML ve rs ions o f the resu l t . I t i s a l so poss ib le to p rov ide an XSL t rans fo rmat ion to c rea te a cus tomized v iew on the work f low s ta tus ( f o r v iew ing in a por t l e t fo r examp le ) .

The HTML mon i to r ing page cu r ren t l y o f fe rs the mos t comp le te and user - f r i end l y v i ew o f the work f l ow execu t i on and var ious in fo rmat ion on the p ipe l ine . E r ro rs can a l so be examined f rom th i s v i ew .

The s t ruc ture o f the work f l ow resu l t i s de f i ned in the TaleoConnectClient.xsd schema. I t bas i ca l l y cons i s t s o f the overa l l s ta tus o f the work f l ow, the er ro r de ta i l s ( i f app l i cab le ) , a copy o f the work f low con f igu ra t i on , and the resu l ts o f each o f the ind i v idua l s teps .

TaleoConnectClient.bat

[Configuration]: Absolute or relative location of the file containing the workflow configuration.

[RequestMessage]: Absolute or relative location of the file containing the request message (optional if the information is provided in the configuration).

[ResponseMessage]: Absolute or relative location of the file to contain the request message (optional if the information is provided in the configuration).



Logging

The Ta leo Connec t C l i en t l ogs a l l pe r t inen t work f low even ts th rough the Apache Jakar ta Commons-Logg ing p ro jec t . The de fau l t con f igu ra t ion i s t o co l l ec t th i s l og in fo rmat ion us ing the Apache Logg ing Log4J p ro jec t , wh ich i s conf igu rab le us ing the log4j.properties f i l e i n the log f o lde r .

In the cu r ren t ve rs ion o f the Ta leo Connect C l i en t , the mon i to r ing fea tu re was des igned to rep lace a lmost a l l uses o f the logg ing fea ture . I t i s recommended to a lways enab le and consu l t the mon i to r ing f i l es be fo re scann ing the log f i l es .

The two ma in reasons fo r us ing logg ing in the cur ren t ve rs ion a re :

• In tegrat ion process progress ion f rom the Ta leo product : Cur ren t l y , the mon i to r ing f i l es do no t show the p rog ress in fo rmat ion ( record o r ins t ruc t ion coun t ) f rom the Ta leo p roduc t p rocess ing the reques t message . By de fau l t , the l ogg ing w i l l show th i s i n fo rmat ion a t each invoca t i on o f the Po l l s tep (ava i l ab le fo r P roduc t commun ica t i on t ype on l y ) .

• Advanced debugging o f the HTTP communicat ion : By enab l ing the logg ing o f the HTTP communica t i on s t ream, i t i s poss ib le to see every s ing le by te o f i n fo rmat ion t rans fe r red to and f rom the Ta leo env i ronment . Th i s i s use fu l a t imp lementa t i on t ime o r fo r ce r ta in techn ica l i nves t iga t ions

Error Handling

The cu r ren t ve rs ion o f the Ta leo Connect C l ien t has s ign i f i can t l y improved er ro r hand l i ng . Examin ing e r ro rs w i th the mon i to r ing fea tu re shou ld enab le cus tomers to d iagnose and co r rec t most o f the po ten t i a l p rob lems w i th work f low execut ions .

Each e r ro r genera ted by the Ta leo Connec t C l i en t i s iden t i f i ed by a un ique and s tab le code tha t can be used in au tomated p rocesses . Each code cor responds to a spec i f i c human-readab le desc r ip t i on . I n severa l e r ro r scenar ios , a reason i s ava i l ab le tha t descr ibes the pa r t i cu la r con tex t o f the prob lem.

Work f l ow er ro rs may a l so have any number o f de ta i l s o f d i f fe ren t t ypes . When the p rob lem occurs dur ing a s tep , bo th the s tep 's un ique iden t i f i e r and human-readab le name are inc luded as de ta i l s . I f t he e r ro r was caused by a Java l anguage excep t i on , the s tack t race i s p rov ided as a de ta i l . I n add i t i on , seve ra l p rob lems o f fe r a t roub leshoo t ing t i p as an e r ro r de ta i l . F ina l l y , gener i c messages a re o f ten added as de ta i l s t o c la r i f y the contex t o f the p rob lem. The numer ica l e r ro r code used in p rev ious ve rs ions o f the c l i en t i s i nc luded as a de ta i l when poss ib le .



Workflow Execution Error Displayed on the HTML Monitoring Page

Workflow Execution Error, Workflow Error Details Section



Temporary Files

The Ta leo Connec t C l i en t uses a ser i es o f t emporary f i l es du r ing the work f l ow execu t i on . These f i l es a l l ow the in teg ra t i on p rocess to suppor t l a rge t rans fo rmat ions by s t reaming the conten t o f one vers ion o f the message to ano the r . By de fau l t , the f i l es a re c rea ted in the s tandard tempora ry fo lde r p rov ided by the opera t ing sys tem and a re de le ted when the work f l ow execut i on i s comple ted ( success fu l l y o r no t ) .

A t imp lementa t i on t ime o r fo r ce r ta in techn ica l i nves t iga t i ons , i t may be use fu l t o keep these temporary f i l es . Th i s bas i ca l l y p rov ides a snap shot o f the reques t and response message be fo re and a f te r eve ry work f l ow s tep . The XML vers ion o f the work f l ow resu l t con ta ins the spec i f i c l oca t i on o f each temporary f i l e used in the execu t i on .


Integration Engine Monitoring

Monitoring

The Ta leo Connect C l i en t enab les end use rs to t rack the p rog ress and inspec t the f i na l s ta tus o f work f l ow execu t i ons us ing the mon i to r ing fea ture . The fea ture i s based on the work f l ow resu l t i n fo rmat ion tha t i s upda ted a t each s tep o f the work f l ow execu t ion . Th is in fo rmat ion can be saved to d i sk i n i t s o r ig ina l XML fo rmat , i n a tex t o r HTML fo rmat ted ve rs ion , o r i n a cus tom fo rmat us ing an XSL t rans fo rmat i on .

Configuration

Folder and File Name PatternThe ma in conf igu ra t ion requ i red to enab le the mon i to r ing fea tu re i s se lec t ing the comp le te l oca t i on o f the mon i to r ing f i l es . The f i r s t s tep i s to se lec t the fo lde r where the mon i to r ing f i l es fo r the work f l ow con f ig u ra t i on w i l l be c rea ted . The fo lder can be any l oca t ion access ib le by the p rocess runn ing the Ta leo Connect C l ien t . The second s tep i s t o se lec t the pa t te rn fo r the mon i to r ing f i l e names. I t i s poss ib le to re -use the work f low execu t i on iden t i f i e r o r spec i f y a cus tom pa t te rn fo r the f i l e name. Here a re a few t yp ica l scenar ios :

• The work f l ow iden t i f i e r i s de f i ned as Ex t rac tNewHi res- [NOW] and the p rocess i s execu ted eve ry hour . As such, to keep proper reco rds , the mon i to r ing f i l e can d i rec t l y re-use th i s iden t i f i e r .

Example o f HTML moni tor ing f i le name: ExtractNewHires-20051015-1432.html

• The work f l ow iden t i f i e r i s de f i ned as Ex t rac tNewHi res- [NOW] bu t the p rocess i s execu ted every n igh t . He re the mon i to r ing needs a re to examine du r ing the day i f the n igh t l y execut ion wen t smooth l y . I n o rder to s imp l i f y th i s task , the mon i to r ing f i l e can spec i f y a f i xed f i l e name l i ke Ex t rac tNewHi res . I n th i s way , the IT s ta f f can de f i ne a b rowser bookmark tha t rema ins the same fo r a l l execu t i ons .

Example o f HTML moni tor ing f i le name: ExtractNewHires.html

• The work f l ow iden t i f i e r i s de f ined as [UU ID ] , and the work f l ow con f igu ra t i on app l i es to a va r ie t y o f reques t messages . Th i s i s a good cho ice to ensure un iqueness bu t a bad one to recogn i ze a p rocess . Here the mon i to r ing needs focus on f i nd ing the cor rec t f i l e fo r each p rocess . A good cho ice fo r the mon i to r ing f i l e pa t te rn i s then ( [F ILE ] - [NOW] ) . I n th i s way , a s imp le g lance a t the mon i to r ing fo lder w i l l de te rmine wha t reques t message was sen t and when .

Example o f HTML moni tor ing f i le name: LoadRequisitions-2005.05.12T23h12m.html

Us ing a va r i ab le work f l ow ident i f i e r and a f i xed mon i to r ing f i l e name pat te rn i s the recommended con f ig u ra t i on when des ign ing and imp lement ing a work f low. S ince the in tegra t ion p rocess i s l aunched mu l t ip le t imes and no record keep ing i s requ i red , th i s a l l ows the imp lemente r to s imp ly re f resh the mon i to r ing in fo rmat ion in a b rowser w i thou t l ook ing fo r the co r rec t f i l e .



HTML FormatThe HTML fo rmat i s the recommended cho ice fo r the mon i to r ing fea ture . Th i s fo rmat i s the eas ies t t o use and o f fe rs a l l o f the usua l l y requ i red in fo rmat ion . I t a l l ows the qu ick de tec t i on o f e r ro rs and a l so g raph ica l l y shows the p rog ress o f the work f low execu t i on .

In o rder fo r an HTML mon i to r ing f i l e to d isp lay co r rec t l y i t mus t be c rea ted in a fo lde r w i th the p roper web resources ( i . e . con ta in ing the web f o lde r d i s t r i bu ted in the monitoring f o lde r ) .

A l though the HTML mon i to r i ng page w i l l d i sp lay in most b rowsers , the con ten t i s op t im ized fo r v iew ing w i th in M ic roso f t 's I n te rne t Exp lo re r , ve rs ion 6 .0 o r be t te r .

The HTML fo rmat SHOULD NOT be used as pa r t o f an au tomated process as Ta leo does no t guaran tee the s tab i l i t y o f the p roduced fo rmat . I f work f l ow resu l t i n fo rmat ion i s requ i red to make dec is ions i n an au tomated p rocess , then a cus tom mon i to r ing f i l e shou ld be used .

Text FormatThe tex t fo rmat o f fe rs an abbrev ia ted v iew on the work f l ow resu l t i n fo rmat ion and shou ld on l y be used in env i ronments where a HTML page i s no t appropr ia te :

• L INUX or UN IX based env i ronments access ib le on l y th rough command l i ne access .

• Env i ronments tha t p reven t the access to the HTML page o r web resources .

The tex t f o rmat SHOULD NOT be used as par t o f an au tomated process as Ta leo does no t guaran tee the s tab i l i t y o f the p roduced fo rmat . I f work f l ow resu l t i n fo rmat ion i s requ i red to make dec is ions i n an au tomated p rocess , then a cus tom mon i to r ing f i l e shou ld be used .

Custom FormatTh is fo rmat o f fe rs the end use r the ab i l i t y t o cus tomize the v iew on the mon i to r ing in fo rmat ion . Th i s can be use fu l in seve ra l ways , in pa r t i cu la r :

• The mon i to r ing in fo rmat ion i s t o be d isp layed in a po r t l e t , bu t us ing the company s ty l ing (no t the Ta leo b rand ing p rov ided in the de fau l t HTML fo rmat ) .

• An au tomated p rocess examines the work f l ow resu l t and thus a s tab le ( and p resumab ly s imp le r ) f o rmat mus t be c rea ted .

XML FormatThe XML fo rmat i s a d i rec t ser i a l i za t i on o f a l l t he in fo rmat ion con ta in ing in the work f l ow resu l t , as such i t i s the most comple te fo rmat . However , the in fo rmat ion i s no t p rov ided in a use r - f r i end l y manner . Th i s fo rmat w i l l no rma l l y on ly be used a t des ign t ime when bu i ld ing a cus tom mon i to r ing t rans fo rmat i on . However , i t may be used d i rec t l y i n au tomated processes i f t he app l i ca t i on read ing the in fo rmat ion suppor t s XML s t ruc tures . The XML fo rmat i s a l so the on l y one conta in ing the temporary f i l e l oca t i ons used by each o f the s tep execut ions .



Monitoring Information

HTML Monitoring View of a Completed Workflow

Basic InformationThe bas ic mon i to r ing in fo rmat ion can be seen in the l e f t hand co lumn o f the HTML mon i to r ing fo rmat and cons i s t s o f the overa l l s ta te o f the work f l ow execu t i on and the ind i v idua l s tep s ta tuses .

• I f the work f l ow execu t ion i s comp le ted , then a l l s teps w i l l a l so be comp le ted .

• I f the work f l ow execut i on i s i n p rogress , then a subse t o f a l l s teps w i l l be comple ted .

• I f the work f l ow execu t ion i s i n e r ro r , then a pa r t i cu la r s tep may a l so be in e r ro r . However , ce r ta in e r ro r scenar ios occur a t the in i t i a l i za t i on o r f i na l i za t i on o f the work f l ow execu t i on , hence e i the r no s teps o r a l l s teps w i l l have been comple ted .

Basic Monitoring Information



Workflow InformationThe work f low in fo rmat ion i s p rov ided in the f i r s t sec t ion o f the HTML mon i to r ing fo rmat and cons i s t s o f the work f l ow iden t i f i e r fo r th i s execu t i on , the t ype o f the work f l ow , the s ta r t , end and du ra t i on o f the execu t i on (when app l i cab le ) . I n add i t i on , the o r ig ina l l oca t i on o f the reques t message f i l e and the ta rge t l oca t i on o f the response message f i l e a re a l so shown. The p resence o f the response message ta rge t l oca t ion DOES NOT imp ly tha t the f i l e was ac tua l l y c rea ted . Th i s i s on l y the case i f the work f l ow execut i on comp le ted w i l l success .

Workflow Information in the HTML Monitoring View

Step Related InformationThe HTML mon i to r ing f i l e o f fe rs a comple te sec t i on o f s tep re la ted in fo rmat ion . A graph ica l ove rv iew o f the s tep p rog ress g roups a l l p re- and pos t -process ing s teps in a s ing le aggrega ted i con . The de ta i l ed tabu la r v i ew then shows the s ta r t , end, and dura t i on (when app l i cab le ) as we l l as the reques t and response message in fo rmat ion when appropr ia te .

Step Related Information in the HTML Monitoring View

Error Handling Information

Workflow Execution Error, Workflow Error Details Section



Default Monitoring

There i s a spec ia l case o f work f l ow mon i to r ing tha t hand les the case where an e r ro r occurs be fo re the in i t i a l i za t i on o f the work f l ow execu t ion . In such cases , the mon i to r ing con f igura t i on de ta i l ed above i s no t known and as such , a de fau l t behav io r has to be de f ined . In the cu r ren t re lease , th i s behav io r i s t o c rea te a tex t and HTML mon i to r ing f i l e named WorkflowProblem.html i n the monitoring sub fo lde r o f the cur ren t fo lde r .

The typ i ca l s i tua t i ons where the de fau l t mon i to r ing i s used a re :

• The work f low conf igu ra t ion f i l e l oca t ion i s i nva l id and the conf igu ra t ion i s no t f ound .

• The work f low conf igu ra t ion f i l e i s i nva l id . Th is canno t happen when us ing the Con f igu ra t i on Ed i to r U I app l i ca t i on , bu t may occur i f the XML con f igura t ion f i l e i s ed i ted manua l l y .

• The reques t and/or response f i l e were requ i red by the con f igu ra t i on bu t no t spec i f i ed in the command l ine a rguments .

These s i tua t i ons a lmos t on l y occur du r ing imp lementa t ion t ime, so th i s i s no t a concern fo r p roduc t ion env i ronments . However , when des ign ing and c rea t ing a new process , i t i s use fu l t o check fo r the p resence o f the de fau l t mon i to r ing f i l e i f no resu l t s seem to be genera ted .


Integration Engine Alerting

Alerting

The Ta leo Connect C l i en t Mon i to r ing fea tu re i s ve ry he lp fu l to ge t de ta i l ed in fo rmat ion about the work f low execu t i on o f an in tegra t i on p rocess dur ing i t s execut i on . However , when p rocesses a re schedu led to run a t t imes where i t i s no t p rac t i ca l f o r a use r to mon i to r the execu t i on , an e-mai l r epor t can he lp the user s tay i n fo rmed on the s ta tus o f the in teg ra t i on p rocesses . The Ta leo Connect C l i en t enab les end use rs to ge t such no t i f i ca t i ons v ia the A le r t ing fea ture by send ing no t i f i ca t i ons upon each work f l ow comp le t i on o r on l y upon fa i l u res . The end user can choose to rece i ve e-mai l s as tex t o r in a cus tom fo rmat us ing an XSL t rans fo rmat ion .

Configuration

General informationF i rs t , the in fo rmat ion tha t needs to be conf igu red fo r the Ta leo Connect C l i en t to be ab le to send e-mai l no t i f i ca t i ons i s the address o f the ma i l se rve r be ing used . The ma i l hos t mus t be spec i f i ed on the A le r t ing page , Genera l sec t ion .

General Section of the Alerting Page

Enabling notificationsThe Ta leo Connect C l i en t can send no t i f i ca t i ons when the work f l ow execut i on comp le tes ( rega rd less o f i t s s ta tus ) , when i t encoun ters an e r ro r , o r bo th . For examp le , i f t he end use r i s on l y i n te res ted in ge t t i ng e-mai l no t i f i ca t i ons when an e r ro r occurs , on l y tha t not i f i ca t i on can be ac t i va ted . Each no t i f i ca t ion mus t then be separa te l y con f igu red ( see nex t sec t i on ) .

Enabling Notifications on the Alerting Page

E-mail message informationFor each enab led no t i f i ca t i on , the use r can conf igu re the in fo rmat ion needed to c rea te the e-mai l message tha t w i l l be sen t when the event occurs .



Recipients

E-mai l no t i f i ca t i ons can be sen t to one o r more rec i p ien ts . Rec ip ien ts can be added to the "To" o r "CC" e-mai l f i e ld . I f more than one rec ip ien t must be spec i f i ed in a g i ven f i e ld , separa te the rec ip ien ts w i th a comma.

Rec ip ien ts can be added e i the r w i th the i r e-ma i l address o r w i th the i r name and address . Here a re samp le va l i d rec ip ien t con f igu ra t i ons :

• j smi th@domain .com

• John A . Smi th < jsmi th@domain .com>

• John A . Smi th < jsmi th@domain .com>, i t@doma in .com

Configuring E-mail Notification Recipients

Subject

The sub jec t o f each e-ma i l no t i f i ca t i on can be se t t o p rov ide de ta i l s on the pa r t i cu la r work f l ow execut i on . The sub jec t f i e ld i s a pa t te rn tha t can inc lude p laceho lders fo r i n fo rmat ion tha t changes each execu t i on . Th i s can make i t eas ie r f o r the rec ip ien t ( s ) o f the no t i f i ca t i on to unders tand the con tex t o f the no t i f i ca t i on . Here a re a few examp les :

• The sub jec t i s de f ined as Comple ted expor t ( [NOW] ) . I f the rec ip i en t i s no t expec t ing to rece ive no t i f i ca t i ons abou t mu l t i p l e i n tegra t ion p rocesses , s imp ly inc lud ing the cu r ren t da te / t ime in the sub jec t i s su f f i c ien t .

Actua l sub ject sample : Comp le ted expor t (04-20-2006 08 :32 :00 AM)

• The sub jec t i s de f ined as [ F ILE ] comp le ted . I f t he rec ip ien t may rece i ve no t i f i ca t i ons abou t mu l t ip le i n tegra t ion p rocesses , the da te / t ime a lone w i l l no t be su f f i c ien t t o d is t ingu i sh no t i f i -ca t ions qu ick l y in an e-ma i l reader . Inc lud ing the name o f the reques t f i l e can he lp in tha t case .

Actua l sub ject sample : NewH i reEx t rac t i on comp le ted

• The sub jec t i s de f ined as I n teg ra t ion comp le ted . S ince a s ing le i n tegra t i on p rocess i s i n use , the rec ip ien t s imp ly wan ts to be no t i f i ed when i t comp le tes and does no t need any add i t i ona l de ta i l s .

Actua l sub ject sample : I n tegra t ion comp le ted

Text e-mail body

The body o f the tex t e -ma i l no t i f i ca t i on conta ins a tex tua l rep resenta t i on o f the work f l ow execut i on , s im i la r to the fo rmat used in tex t mon i to r ing f i l es . Us ing th i s fo rmat g i ves the end use r a comple te execu-t i on repor t tha t i s guaran teed to work w i th mos t e-mai l readers .



Custom e-mail body

Us ing a cus tom body a l l ows the end use r t o cus tomize the con ten t o f e -ma i l no t i f i ca t i ons sen t by Ta leo Connect C l ien t . Th is can be use fu l i n severa l ways :

• When the e-ma i l no t i f i ca t i ons a re sen t to rec ip ien ts who have l i t t l e know ledge o f the techn ica l de ta i l s o f the in tegra t i on p rocess , a c l eaner fo rmat t i ng a l l ows them to qu ick l y g rasp the re levan t in fo rmat i on .

• When the e-ma i l no t i f i ca t i ons a re sent t o an au tomated sys tem tha t may pe r fo rm o the r ac t i ons based on the work f l ow resu l t . Thus , a s tab le and con t ro l l ed fo rmat i s requ i red .

To bu i ld the cus tom e-ma i l body , an XSL s t y le sheet must be spec i f i ed , wh ich i s app l ied to the XML fo rmat o f the work f l ow execu t i on resu l t ( see Mon i to r ing sec t i on ) . The resu l t o f the XSL t rans fo rmat ion i s i nc luded in the body o f the e-mai l no t i f i ca t i on . The con ten t - t ype o f the e-ma i l mus t be spec i f i ed and can be e i the r HTML ( tex t /h tm l ) o r tex t ( t ex t / tex t ) .

Configuring the Body in a Custom E-mail Notification


Integration Engine HTTP Proxy

HTTP Proxy

I n ce r ta in co rpo ra te ne tworks , IT po l i c i es en fo rce the use o f a p roxy to funne l a l l ex te rna l HTTP reques ts . Th i s i s an impor tan t par t o f the ove ra l l ne twork secur i t y .

The Ta leo Connec t C l i en t fu l l y suppor t s the use o f an HTTP p roxy bo th in the run t ime execut i on sc r ip t and th rough the des ign env i ronment . The con f igura t i on o f the HTTP p roxy fo l l ows the Java s tandard documented a t h t tp : / / j ava .sun .com/ j2se/1 .4 .2 /docs /gu ide /ne t /p roper t i es .h tm l ( these a re the same spec i -f i ca t i ons as fo r the new 1 .5 ve rs ion ) .

Accord ing to these spec i f i ca t ions , the con f igu ra t i on o f the HTTP p roxy i s done a t the JRE leve l ; t ha t i s the run t ime env i ronment i n wh ich the in tegra t i on p rocess i s i nvoked . The connec t i v i t y i n fo rmat ion i s passed as sys tem proper t i es i n e i the r the run t ime execu t ion sc r ip t o r the des ign env i ronment in i t i a l i za t i on f i l e .

Hence, assuming the co rpora te HTTP p roxy i s ava i l ab le a t proxy.acme.net on po r t 3128, the TaleoConnectClient.bat sc r ip t shou ld be changed to add

%JAVA_HOME%\bin\java.exe

-Dhttp.proxyHost=proxy.acme.net -Dhttp.proxyPort=3128 -Djava.endorsed.dirs=%IC_HOME%\lib\endorsed ...

Cer ta in corpo ra te HTTP p roxy imp lementa t i ons requ i re an exp l i c i t au then t i ca t ion . Th i s in fo rmat ion can be p rov ided w i th two ex t ra sys tem proper t i es as in the fo l l ow ing example :

%JAVA_HOME%\bin\java.exe

-Dhttp.proxyHost=proxy.acme.net -Dhttp.proxyPort=3128

-Dhttp.proxyUser=acmeuser -Dhttp.proxyPassword=secret

-Djava.endorsed.dirs=%IC_HOME%\lib\endorsed ...

P lease no te tha t we a l so fu l l y suppor t the http.nonProxyHosts p roper t y as de f ined in the Java spec i f i -ca t ions .

I f t he use o f an HTTP proxy i s requ i red a l so in the des ign env i ronment , then the fo l l ow ing l i nes shou ld be added to the TaleoConnectClient.ini f i l e :

-vmargs

-Djava.endorsed.dirs=lib/endorsed

-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

-Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl

-Dhttp.proxyHost=proxy.acme.net

-Dhttp.proxyPort=3128

I n p rev ious vers ions , the conf igu ra t ion o f the HTTP p roxy was done in the c l i en t con f igura t ion f i l e i t se l f . Th i s i s no longer suppor ted in favo r o f the s tandard way desc r ibed above ( see the M ig ra t ion sec t ion fo r more de ta i l s ) .

Cer ta in imp lementa t i ons suppor t the https.proxyHost p roper t y a l though i t i s no t pa r t o f the Java s tandard . The Ta leo Connec t C l ien t on l y suppor ts http.proxyHost, wh ich i s used fo r a l l HTTP reques ts (HTTP o r HTTPS pro toco l ) .

http://java.sun.com/j2se/1.4.2/docs/guide/net/properties.html

P r o c e s s i n g


Processing Pre-processing Steps

Pre-processing Steps

The ma in ob jec t i ve o f the p re-process ing s teps i s t o i n i t i a te the in tegra t i on p rocess by ga the r ing a l l t he requ i red in fo rmat ion and cons t ruc t a va l i d reques t message in the Ta leo fo rmat .

Convert Encoding

Th is s tep conve r t s the encod ing o f the f i l e con ta in ing the reques t message . The conf igu ra t ion spec i f i es the expec ted encod ing and the ta rge t encod ing . Th is s tep may be requ i red because the Ta leo Connec t P la t fo rm on l y suppor t s UTF-8 encod ing .

Se lec t Genera te BOM (by te o rder mark ) t o ass ign a s igna ture charac te r code to the encod ing .

Validate Encoding

Th is s tep scans the f i l e conta in ing the reques t message to en fo rce the va l i d i t y o f the spec i f i ed encod ing in the con f igura t i on . Th i s i s a conven ience s tep tha t i so la tes th i s va l i da t i on fo r an eas ie r d iagnos is . Even i f t h i s s tep i s no t i nc luded in the work f l ow , the Send s tep w i l l va l i da te the reques t message to en fo rce the mandato ry UTF-8 encod ing fo r the Ta leo Connec t P la t fo rm; as such, i t i s a lways op t i ona l .

Prepare Export

Th is s tep t rans fo rms a spec i f i ca t ion c rea ted in the Expor t Ed i tor i n to a s tandard T-XML document . Th is i s a requ i red s tep when the reques t f i l e i s in the SQ-XML fo rmat genera ted by the Expor t Ed i to r .

Prepare Import

Th is s tep conver t s a CSV source f i l e i n to a T-XML impor t document . The l oad spec i f i ca t i on c rea ted in the Impor t Ed i tor i s used to execu te the convers ion . The p rocess i s re la t i ve l y s t ra igh t fo rward , c rea t ing a s t ruc tu red v iew o f the impor ted in fo rmat ion based on the Ta leo produc t bus iness mode l and ass ign ing va lues based on the ind i v idua l co lumn spec i f i ca t ions . Th i s i s a requ i red s tep when the reques t f i l e i s in CSV fo rmat and the Produc t commun ica t i on t ype i s se lec ted .

Wrap SOAP

Th is s tep wraps a T-XML document i n a T-SOAP message fo r t ransmiss ion to a Ta leo p roduc t . Th i s i s a requ i red s tep a f te r bo th the Prepare Expor t and Prepare Impor t s teps .

Generate ID

Th is s tep genera tes a un ique ident i f i e r and inser t s i t i n to the reques t message p rov ided in the p ipe l i ne . The presence o f such an ident i f i e r i n the reques t message i s mandato ry i n the T-SOAP fo rmat and i s a p re- requ i s i te fo r a l l i n tegra t ion p rocesses . Th is s tep i s use fu l i f the cus tomer sys tem does no t c rea te such a va lue in the o r ig ina l reques t message f i l e o r f o r da ta ex t rac t i on scenar i os where the reques t f i l e i s re -used fo r each execut i on .

NOTE: The Wrap SOAP s tep cove rs th i s when us ing impor t o r expo r t spec i f i ca t ions .


Processing Pre-processing Steps

Custom Steps

The ma in ob jec t i ve o f cus tom s teps i s t o p rov ide func t i ona l i t y tha t i s no t ava i l ab le i n the se t o f p re- o r pos t -process s teps in the cu r ren t ve rs ion o f Ta leo Connec t C l i en t .

The imp lemente r can access the cu r ren t p ipe l i ne as we l l as the en t i re work f l ow con f igura t i on when execu t ing a cus tom s tep . I n add i t i on , the conf igu ra t i on o f the cus tom s teps a l l ows any ex t ra i n fo rmat ion to be passed to the cus tom s tep Java code , in name/va lue pa i r s .


Processing Processing Steps

Processing Steps

The ma in ob jec t i ve o f the process ing (o r communica t i on ) s teps i s t o send a reques t message to the Ta leo env i ronment and re t r i eve a co r respond ing response message.

The fo l l ow ing th ree mandato ry p rocess ing s teps a re a t the co re o f any Ta leo Connec t C l i en t work f l ow are Send , Pol l , and Ret ieve . These s teps share th ree common con f igura t i on ca tegor ies tha t have on l y s l i gh t va r ia t ions be tween them: Endpo in t I n fo rmat ion , Au then t i ca t i on In fo rmat ion , and Qua l i t y I n fo rmat ion . The Wiza rd w i l l co r rec t l y popu la te mos t o f the in fo rmat ion .

Endpoint Information

The endpo in t i n fo rmat ion con f igu res where the Ta leo Connec t C l i en t i s t o send o r re t r i eve the messages . Bas ica l l y , th i s in fo rmat ion rep resents the d i spa tcher URL fo r the web se rv ices exposed by e i the r the Ta leo m idd leware o r the Ta leo p roduc t .

Authentication Information

The au then t i ca t i on in fo rmat ion conf igu res how the Ta leo Connect C l i en t au then t i ca tes i t se l f to i nvoke the Ta leo env i ronment web se rv ices . Cur ren t l y , on l y the HTTP Bas ic Au thent ica t i on scheme is suppor ted .

Quality Information

The qua l i t y in fo rmat ion de te rm ines the robus tness o f the in teg ra t ion p rocess d r i ven by the Ta leo Connec t C l i en t . A l though c ruc ia l f o r the po l l i ng s tep , cer ta in va lues app ly to a l l p rocess ing s teps . Bas ica l l y the qua l i t y i n fo rmat ion de te rmines how many t imes the s tep 's web se rv i ce i s i nvoked be fo re the process i s cons ide red in e r ro r . The po l l i ng s tep o f fe rs a few ex t ra conf igu ra t i ons g i ven i t s spec ia l c i r cumstances o f a lmost a lways hav ing to i nvoke the s ta tus web se rv i ce seve ra l t imes .


Processing Post-processing Steps

Post-processing Steps

The ma in ob jec t i ve o f the pos t-process ing s teps i s t o conve r t o r t rans fo rm the in fo rmat ion in the Ta leo fo rmat response message to a p roper fo rmat fo r the cus tomer sys tem and comp le te the in tegra t i on p rocess .

Strip SOAP

Th is s tep removes the enve lope used in the message t ransmiss ion , wh ich fo l l ows the SOAP web se rv i ce s tandard . The SOAP enve lope con ta ins commun ica t ion re la ted in fo rmat ion tha t i s ra re l y use fu l in the cus tomer 's bus iness in tegra t i on process .

In th i s s tep , i f the se lec ted ou tpu t f o rmat (mode ) fo r a T-SOAP t ype expor t reques t i s CSV, i t i s poss ib l e to d i rec t l y s to re the resu l t s i n a CSV f i l e . The drawback i s tha t the process w i l l on l y succeed i f CSV da ta i s re tu rned. There a re two spec i f i c cases where Ta leo Connect C l i en t w i l l p rov ide an e r ro r :

1 . The fo rmat o f the reques t query i s i nco r rec t .

2 . An app l i ca t i on e r ro r occur red on the se rve r du r ing the execut i on o f the query .

In bo th cases , s ince the SOAP enve lope was d iscarded dur ing the p rocess , the ac tua l e r ro r message i s l os t . As these e r ro rs a re mos t l y de tec ted a t imp lementa t i on t ime, i t i s su f f i c ien t t o remove the s tep and re-execu te the f i l e to assess the p rob lem.

Convert Encoding

Th is s tep conve r t s the encod ing o f the f i l e con ta in ing the response message . The con f igu ra t i on spec i f i es the expec ted encod ing and the ta rge t encod ing . Th is s tep may be requ i red because the Ta leo Connec t P la t fo rm on l y suppor t s UTF-8 encod ing .

Transform Import Results

Th is s tep conver ts the impor t opera t ion resu l t s to a s tandard CSV fo rmat . When us ing an impor t spec i f i -ca t i on in the P repare Impor t p re-p rocess ing s tep to i nvoke impor t opera t i ons w i th a CSV reques t f i l e , th i s a l l ows an eas ie r co r re la t i on be tween the opera t i ons and the i r resu l t s .

Transform Export Results

Th is s tep conve r t s the resu l t s o f an expor t t o a s tandard CSV fo rmat . Th i s s tep on ly app l i es to the Ta leo Bus iness Ed i t i on p roduc t . The Ta leo En te rpr i se Ed i t i on p roduc ts have a na t i ve CSV expor t fo rmat .

Transform Using XSL

Th is s tep conve r t s the response message in fo rmat ion us ing a s tandard XSL t rans fo rmat ion . Because the Ta leo Connect C l i en t i s des igned to suppor t l a rge f i l es ( f o r examp le , h igh vo lumes o f ex t rac ted da ta ) the XSL t rans fo rmat ion i s no t app l i ed d i rec t l y t o the response message . S ince XSL techno logy does no t suppor t l a rge t rans fo rmat ions (because a l l i n fo rmat ion mus t be l oaded in memory p r i o r t o the ac tua l t rans-fo rmat ion ) , th i s s tep executes the t rans fo rmat ion on a reco rd by record bas i s . The p rov ided XSL w i l l app l y on l y to a par t i cu la r XML record s t ruc tu re , no t the en t i re response message .


Processing Post-processing Steps

Transform Using Java (deprecated)

I n ve rs ion 2 .0 , the T rans fo rm Us ing Java s tep was o f fe red . Th is s tep i s no longer suppor ted in vers ion 2 .1 ; i t has been rep laced by us ing an XSLT based t rans fo rmat ion w i th the power fu l Saxon 8B eng ine tha t suppor t s the l a tes t XSLT 2 .0 spec i f i ca t i on . I f eve r XSLT 2 .0 does no t o f fe r the requ i red fea tu res fo r the t rans fo rmat i on , then a no rma l cus tom s tep can be wr i t ten to address the need , based on the en t i re response document .

Custom Steps

The ma in ob jec t i ve o f cus tom s teps i s to p rov ide func t iona l i t i es tha t a re no t ava i lab le in the se t o f p re- o r pos t -p rocess s teps in the cu r ren t ve rs ion o f Ta leo Connec t C l i en t .

The imp lemente r can access the cu r ren t p ipe l i ne as we l l as the en t i re work f l ow con f igura t i on when execu t ing a cus tom s tep . I n add i t i on , the conf igu ra t i on o f the cus tom s teps a l l ows any ex t ra i n fo rmat ion to be passed to the cus tom s tep Java code , in name/va lue pa i r s .

B u s i n e s s C a s eI m p l e m e n t a t i o n s


Welcome Wagon Business Case Implementations

Welcome Wagon

We w i l l now rev i s i t t he Welcome Wagon bus iness case to see how an ac tua l imp lementa t i on o f the i n tegra t ion p rocesses wou ld occur w i th the Ta leo Connec t C l ien t .

Business Requirements

We f i r s t need to l ook a t the de ta i l ed requ i rements o f th i s bus iness case . A f te r fu r the r i nves t iga t i on w i th the IT s ta f f a t Amer i can Compute rs , Inc . , we now have the fo l l ow ing po in ts to address :

1 . The ex t rac t i on o f the new emp loyees shou ld be done eve ry week day a t 04 :00 a .m.

2 . The ex t rac ted da ta shou ld be sent v i a e-ma i l t o G i f t s On Reques t on the morn ing o f the same day .

3 . G i f t s On Reques t expec ts a f i l e i n the fo l l ow ing fo rmat : Full Name, Complete Address, Phone NumberJohn A . Smi th , "123 Ma in S t ree t , De t ro i t , M I , 22540" ,123-456-7890

4. G i f t s On Reques t i s expec t ing the f i l e to be in the ISO-8859-1 encod ing .


The comple te se t o f f i l es requ i red to run th is bus iness case can be found in your Ta leo Connect C l i en t d i rec to ry under docs\examples\WelcomeWagon.

Overall processThe Ta leo Connec t C l ien t does no t hand le schedu l ing so requ i rement #1 w i l l be hand led by a t imed scr ip t managed by the IT Depar tment a t Amer ican Compute rs , I nc . Th i s sc r ip t w i l l i nvoke the Ta leo Connec t C l i en t w i th the p roper con f igura t ion .

The cur ren t ve rs ion o f the Ta leo Connect C l i en t does no t hand le "push" l i ke pos t -process ing s teps ; th i s i s p l anned fo r upcoming ve rs ions . In the mean t ime , to hand le requ i rement #2 , th i s imp lementa t ion w i l l use a manua l p rocess to send the f i l e to G i f t s On Reques t . A member o f the HR s ta f f w i l l check eve ry morn ing fo r the f i l e c rea ted on a ne twork shared d r i ve . I f the f i l e i s p resen t , then he o r she w i l l send i t d i rec t l y to G i f ts On Reques t as an e-ma i l a t tachment us ing Mic roso f t Ou t look .

Export requestThe Ta leo Connect C l i en t can be used to c rea te the expor t reques t needed to ex t rac t the requ i red in fo rmat ion f rom the Ta leo p roduc t . I n th i s case , the Ta leo Connect C l i en t comes w i th an expor t temp la te tha t can be used as- i s to ex t rac t the in fo rmat ion . You can a l te r the f i e lds i f needed by mov ing them or by d ragg ing them f rom the en t i t y v i ew. Ta leo imp lementa t i on consu l tan ts can a l so p rov ide the requ i red exper t i se to cus tomize the expor t fu r the r when needed.

S ince the des i red f ina l CSV fo rmat i s na t i ve l y suppor ted by the Ta leo Connec t p la t fo rm, th i s f o rmat w i l l be used d i rec t l y f o r the ex t rac ted da ta . Us ing the Expor t Wi za rd , the new h i re temp la te can be found under the P rese lec t i onApp l i ca t i on en t i t y ( i t i s no t a Cand ida te temp la te because we a re a l so in te res ted in the requ is i t i on in fo rmat ion , hence we need to expo r t the app l i ca t i on i t se l f ) . A f te r the Wiza rd c rea tes the expor t spec i f i ca t ion you mus t save i t t o a f i l e w i th an _sq.xml ex tens ion .



New Export Wizard for the Welcome Wagon Business Case

ConfigurationThe Ta leo Connect C l ien t can be used to c rea te the con f igu ra t i on f i l e tha t de f ines the in tegra t ion p rocess and communica tes w i th the Ta leo p roduc t . In th i s case , the Con f igura t i on Wiza rd can comp le te l y bu i ld the requ i red con f igu ra t i on by se lec t ing a l l o f the de fau l t op t ions and the new ly de f i ned expor t spec i f i ca t i on on the l as t page . A proper env i ronment i s a l so requ i red to comple te the Wizard .

New Configuration Wizard for the Welcome Wagon Business Case



Pre-processingBoth the P repare Impor t and Wrap SOAP s teps a re inc luded in the work f l ow by the Wiza rd . These a re mandato ry p re-p rocess ing s teps when us ing an Expor t spec i f i ca t i on .

ProcessingThe env i ronment f i l e p rov ided to the Wizard i s used to fu l l y con f igure the p rocess s teps , i nc lud ing the connec t i v i t y i n fo rmat ion . You may wan t to ad jus t the qua l i t y se t t i ngs o f the Po l l s tep a f te r execut ing the p rocess a few t imes .

Post-processingThe response message p rov ides the ex t rac ted da ta in the requ i red CSV fo rmat , s ince th i s i s na t i ve l y suppor ted by the Ta leo Connec t P la t fo rm. However , i t i s wrapped in the manda tory SOAP enve lope ( requ i red fo r web se rv i ce commun ica t ion ) . Hence , the f i r s t pos t-p rocess ing s tep o f the work f l ow s t r ips the SOAP enve lope . Th is meets requ i rement #3 as the SQ-XML ex t rac t i on express ion a l ready fo rmats the in fo rmat ion in the cor rec t sequence . The Ta leo Connect Se rve r uses a M ic roso f t Exce l compat ib le escap ing s t ra tegy , so the requ i rement i s comp le te l y met .

Because the Ta leo Connect P la t fo rm on l y suppor ts UTF-8 encod ing , the CSV f i l e genera ted by the p rev ious pos t -p rocess ing s tep does no t meet requ i rement #4 . Ano ther pos t-p rocess ing s tep must be added to change the f i l e encod ing to the cus tomer spec i f i ed va lue o f ISO-8859-1.

Final configurationYou can f i nd the f ina l con f igu ra t ion requ i red fo r th i s bus iness case in the documenta t i on bund le p rov ided w i th the Ta leo Connect C l ien t d is t r ibu t i on .

Workflow Configuration for the Welcome Wagon Business Case



HTML Monitoring Page for the Welcome Wagon Business Case


ERP System Update Business Case Implementations

ERP System Update

We wi l l now rev i s i t the ERP Sys tem Upda te bus iness case to see how an ac tua l imp lementa t i on o f the in teg ra t i on processes wou ld occur w i th the Ta leo Connec t C l i en t .


We f i r s t need to l ook a t the de ta i l ed requ i rements o f th i s bus iness case . A f te r fu r the r inves t iga t i on w i th the IT s ta f f a t Cass i v i Too l s , we now have the fo l l ow ing po in ts to address :

1 . The ex t rac t i on o f the new employees shou ld be done every week day a t 10:00 PM.

2 . The ex t rac ted da ta shou ld be immedia te l y pos ted to the ERP sys tem v ia FTP .

3 . The ERP sys tem is expec t ing the fo l l ow ing fo rmat :INSERT EMPLOYEE:First Name|Middle Initial|Last NameE-MAIL:e-mail addressSTREET ADDRESS:street address;CITY:city;STATE:state code;ZIPCODE:zipcode====INSERT EMPLOYEE :John|A|SmithE-MAIL : [email protected] ADDRESS:123 Main Street;CITY:Detroit;STATE:MI;ZIPCODE:22540====Note : Th i s i s , o f course , a s imp l i f i ca t i on o f the ac tua l i n fo rmat ion requ i red fo r a t rue ERP sys-tem.

4 . The ERP sys tem w i l l accep t the f i l e i n UTF-8 encod ing .


The comple te se t o f f i l es requ i red to run th is bus iness case can be found in you r Ta leo Connect C l ien t d i rec to ry under docs\examples\ERPSystem.

Overall processSame comments as in the Welcome Wagon scenar io ; however , the IT s ta f f a t Cass i v i Too l s w i l l t hemse l ves imp lement a s imp le FTP f i l e t rans fe r as a Ta leo Connect C l i en t cus tom s tep ins tead o f us ing a manua l p rocess . Th i s w i l l be desc r ibed fu r ther in the pos t -process ing sec t ion .

Export requestAs in the We lcome Wagon scenar i o , the Ta leo Connect C l ien t can be used to c rea te the expor t reques t needed to ex t rac t the requ i red in fo rmat ion f rom the Ta leo produc t . The New Expor t W iza rd can be used to c rea te an expor t reques t and the Expor t Ed i to r can then be used to add the requ i red p ro jec t i ons . For the f i l t e r ing , the Ta leo Connect C l i en t p rov ides a Da i ly New H i re f i l te r t emp la te tha t can be s imp ly added to the expor t reques t as- i s . Add i t i ona l l y , s i nce the des i red f i na l f o rmat i s cus tom to the ERP sys tem and thus no t na t i ve l y suppor ted by the Ta leo Connect P la t fo rm, the ex t rac ted da ta i s p rov ided in XML fo rmat to enab le an XSL t rans fo rmat ion .



New Export Wizard for the ERP System Update Business Case

ConfigurationThe Ta leo Connect C l ien t can be used to c rea te the con f igu ra t i on f i l e tha t de f ines the in tegra t ion p rocess and communica tes w i th the Ta leo p roduc t . In th i s case , the Con f igura t i on Wiza rd can comp le te l y bu i ld the requ i red con f igu ra t i on by se lec t ing a l l o f the de fau l t op t ions and the new ly de f i ned expor t spec i f i ca t i on on the l as t page . A proper env i ronment i s a l so requ i red to comple te the Wizard .

New Configuration Wizard for the ERP System Update Business Case



Pre-processingBoth the P repare Impor t and Wrap SOAP s teps a re inc luded in the work f l ow by the Wiza rd . These a re mandato ry p re-p rocess ing s teps when us ing an Expor t spec i f i ca t i on .

ProcessingThe env i ronment f i l e p rov ided to the Wizard i s used to fu l l y con f igure the p rocess s teps , i nc lud ing the connec t i v i t y i n fo rmat ion . You may wan t to ad jus t the qua l i t y se t t i ngs o f the Po l l s tep a f te r execut ing the p rocess a few t imes .

Post-processingThe fo rmat expec ted by the ERP sys tem i s cus tom and thus a pos t-p rocess ing t rans fo rmat i on s tep w i l l be requ i red . S ince the ERP fo rmat i s we l l -s t ruc tu red and the in fo rmat ion i s no t ve ry comp lex , a s tandard XSL t rans fo rmat ion i s the mos t appropr ia te cho ice . The XML fo rmat re tu rned by the Ta leo Connec t Se rve r can be de te rmined based on the SQ-XML ex t rac t i on in o rder to wr i t e the XSL t rans fo rmat ion . As no ted in the s tep descr ip t i on , i n o rder to hand le l a rge amounts o f da ta , the XSLT must on l y app l y to a pa r t i cu la r reco rd . The s tep execu t i on w i l l hand le the cyc l i ng th rough the en t i re se t o f ex t rac ted records . The XSL t rans fo rmat i on s tep w i l l a l so s t r ip the SOAP enve lope as pa r t o f i t s execu t i on .

Requ i rement #4 i s met na t i ve l y by the Ta leo Connect P la t fo rm as a l l ex t rac ted da ta i s pers is ted by de fau l t in UTF-8 encod ing .

To fu l l y au tomate the in teg ra t i on process , requ i rement #2 w i l l a l so be hand led by the Ta leo Connec t C l i en t , us ing a cus tom s tep coded by the IT s ta f f a t Cass i v i Too l s . Th is s tep w i l l p ick up the conve r ted f i l e i n i t s cu r ren t l oca t i on and send i t to the ERP sys tem's FTP s i t e . I n o rder to p romote the re-use o f th i s cus tom s tep , i t s con f igu ra t ion w i l l spec i f y the connec t i v i t y in fo rmat ion o f the FTP s i te . In th i s way , i f eve r th i s in fo rmat i on changes , on l y the con f igura t ion w i l l need to be mod i f i ed us ing the Con f igu ra t i on Ed i to r U I ( the cus tom s tep code wou ld no t need to be recomp i l ed ) .


Workflow Configuration for the ERP System Update Business Case



HTML Monitoring Page for the ERP System Update Business Case


Global Recruiting Business Case Implementations

Global Recruiting

We w i l l now rev i s i t the G loba l Rec ru i t ing bus iness case to see how an ac tua l imp lementa t i on o f the in teg ra t i on processes wou ld occur w i th the Ta leo Connec t C l i en t .


The t rans la t i on team prov ides the mate r i a l i n th ree l anguages : Eng l i sh (en ) , F rench ( f r ) , and Span ish (es ) . The va lues in pa ren theses a re the l oca le codes used to i den t i f y the l anguages in the Ta leo produc ts ( they co r respond to the f l ag i cons used when en ter ing mul t i l i ngua l in fo rmat ion th rough the S ta f f ing WebTop ) . The t rans la ted tex t a r r i ves in a M ic roso f t Exce l f i l e ( t rans la t ions . x l s ) tha t i s saved as a comma separa ted f i l e ( t r ans la t i ons .csv ) ; th i s i s a s tandard M ic roso f t Exce l f ea tu re .

NOTE: To make the imp lementa t ion tex t l i gh te r , on l y the requ is i t i on t i t l e i s hand led . Add ing the o the r re levan t f i e lds i s s t ra igh t fo rward .


The comple te se t o f f i l es requ i red to run th is bus iness case can be found in you r Ta leo Connect C l ien t d i rec to ry under docs\examples\GlobalRecruiting.

Overall processBased on the s t ruc ture o f the source mate r i a l , an impor t spec i f i ca t i on i s made to l i nk the va r i ous in fo rmat ion e lements to the Ta leo bus iness mode l . An in tegra t i on p rocess i s then des igned us ing a work f l ow tha t hand les such impor ts . The resu l ts o f the impor t a re re tu rned in a Ta leo s tandard T-SOAP response f i l e .

Import requestS ince the impor t spec i f i ca t i on i s spec i f i c t o the cur ren t scenar io , we w i l l use the Impor t W iza rd to c rea te a b lank spec i f i ca t i on fo r the requ is i t i on en t i t y .



You now have the fo l l ow ing s i tua t ion in the Des ign perspec t i ve :

The de fau l t i n fo rmat ion on the Genera l page i s f i ne fo r th i s example as the source f i l e va lues a re separa ted w i th comma charac te rs and a header l i ne i s p resent .



Swi tch ing to the Co lumn page, we need fou r en t r i es , one fo r each o f the co lumns in the source f i l e . The requ is i t i on number seen in the Ta leo Pro fess iona l S ta f f i ng WebTop i s l abe led Contes tNumber in the bus iness mode l ; we can d rag tha t f i e ld to the co lumn l i s t t o c rea te our f i r s t mapp ing .



The requ is i t i on number (we added a header fo r conven ience ) w i l l se rve to f i nd the requ is i t i on , so i t must be marked as a key co lumn in the Search sec t i on . Th i s co lumn i s no t mu l t i l i ngua l , so there i s no op t i on to se lec t i n the Loca le sec t i on .

Nex t , we need th ree co lumns fo r the T i t l e f i e ld , wh ich i s i n the re la ted Job In fo rmat i on en t i t y . Aga in we use a header to p rov ide a more readab le a l i as fo r the co lumn. The t i t l es a re be ing updated , so we do no t sea rch fo r them. However , each co lumn needs to be in a spec i f i c l oca le , so we use tha t op t i on in the Loca le sec t i on .



ConfigurationThe Ta leo Connect C l ien t can be used to c rea te the con f igu ra t i on f i l e tha t de f ines the in tegra t ion p rocess and communica tes w i th the Ta leo p roduc t . In th i s case , the Con f igura t i on Wiza rd can comp le te l y bu i ld the requ i red con f igu ra t i on by se lec t ing a l l o f the de fau l t op t ions and the new ly de f i ned impor t spec i f i ca t i on on the l as t page . A proper env i ronment i s a l so requ i red to comple te the Wizard .

Pre-processingBoth the P repare Impor t and Wrap SOAP s teps have been inc luded in the work f l ow by the Wizard . These a re mandato ry p re-p rocess ing s teps when us ing an Impor t spec i f i ca t ion .



ProcessingThe env i ronment f i l e p rov ided to the Wiza rd was used to fu l l y con f igure the process s teps , i nc lud ing the connec t i v i t y i n fo rmat ion . You may wan t to ad jus t the qua l i t y se t t i ngs o f the Po l l s tep a f te r execut ing the p rocess a few t imes .

Post-processingThere a re no pos t -process ing s teps requ i red as the response message s imp ly con ta ins the s ta tus o f the reques ted updates .


Workflow Configuration for the Global Recruiting Business Case

HTML Monitoring Page for the Global Recruiting Business Case

A p p e n d i c e s

Taleo Connect Client A-1

Appendices Taleo Connect Client Installation

Taleo Connect Client Installation

Th is Append i x covers the s teps tha t a re requ i red to success fu l l y i ns ta l l t he Ta leo Connec t C l i en t app l i ca-t i on . These s teps shou ld be fo l l owed in the sequence p resented a l though some o f them may be done in para l l e l . I n fo rmat ion on the XML reques t f i l e i s a l so p rov ided.

Account Creation

Ta leo Suppor t can p rov ide cus tomers w i th a fu l l y con f igu red account on the i r Ta leo p roduc t to execute in teg ra t i on p rocesses . Th i s accoun t i s de l i ve red in the fo rm o f an env i ronment f i l e ( see be low) a long w i th a use r /password comb ina t i on fo r a use r w i th the Sys tem In teg ra t i on o r Sys tem In tegra to r ro le .

NOTE: Th i s i s a very power fu l account as i t a l l ows access to impor t and expor t da ta d i rec t l y f rom Ta leo p roduc ts . The accoun t in fo rmat ion shou ld be kept secure a t a l l t imes and no t be used fo r any o the r use then to d r i ve the in teg ra t ion p rocesses .

I f us ing the Midd leware commun ica t i on s t ra tegy , the accoun t i n fo rmat ion i s a l so p rov ided as an env i ron-ment f i l e w i th a use r tha t has access to the Ta leo m idd leware .

Environment Files

A Ta leo Connec t C l i en t env i ronment f i l e conta ins the connec t i v i t y de ta i l s o f your Ta leo p roduc t i n an easy to read and ed i t f o rmat . I f you do no t have such a f i l e , you can eas i l y c rea te one g i ven the proper access to the Ta leo Pro fess iona l Admin i s t ra to r WebTop . You w i l l need the URL to access your Ta leo P ro fess iona l web s i t e and a use r w i th the Sys tem In teg ra t i on ro le . You can c rea te such a use r when l ogg ing in as a Sys tem Admin is t ra to r .

NOTE: Th i s i s a power use r ro le as i t a l l ows access to impor t and expor t da ta d i rec t l y f rom the Ta leo p roduc ts . The accoun t in fo rmat ion shou ld be kept secure a t a l l t imes and no t be used fo r any o the r use than to d r i ve the in teg ra t ion p rocesses .

Suppose th i s i n fo rmat ion i s http://acme.taleo.net and the use r l og in name i s i n tegra to r . The env i ron-ment f i l e shou ld then be a tex t f i l e named acme_env.properties and conta in the fo l l ow ing l ine :

product=https://integrator:[email protected]

When us ing such an env i ronment f i l e , you w i l l be prompted fo r the password when requ i red . I n the con f ig -u ra t ion f i l es , the password i s no t i n c l ea r tex t . The enc ryp t i on used i s d i f f i cu l t , bu t no t imposs ib le to b reak . As such , the con f i gu ra t i on f i l es shou ld a l so be kep t in a secure loca t ion .

Connection Authorization

Th is sec t ion on l y app l i es to in tegra t i on p rocesses us ing the m idd leware commun ica t ion s t ra tegy .

For secur i t y reasons , connec t i ons to the Ta leo in teg ra t i on server f rom Ta leo Connect C l ien t can on ly be made f rom t rus ted IP addresses . Cus tomers mus t the re fo re p rov ide the i n tegra t ion suppor t spec ia l i s t w i th the pe r t i nen t IP address , o r IP address range i f the compute r o r se rve r uses a dynamic IP . I f cus tomers use a f i r ewa l l , t hey have to p rov ide the in tegra t i on suppor t spec ia l i s t w i th the ou tgo ing IP address o r IP address range ra the r than the IP address o f the compute r o r se rve r .


Appendices Taleo Connect Client Installation

Pre-installation

The Ta leo Connec t C l ien t requ i res Java Run t ime Env i ronment ( JRE ) vers ion 1 .4 .2 exac t l y . Un fo r tunate l y , the C l ien t cu r ren t l y does no t suppor t the mos t recen t 1 .5 vers ion (a l so known as Java 5 .0 ) . The Windows ins ta l l e r sh ips w i th an approp r ia te ve rs ion o f the JRE , so the re shou ld be no ex t ra s teps . When ins ta l l i ng the UN IX /L INUX run t ime b ina ry f i l es , a p re- ins ta l l ed JRE i s requ i red . Customers us ing a UNIX computer or server shou ld make sure to ins ta l l the appropr iate vers ion of the Java Runt ime Env i ronment for the i r vers ion o f UNIX.

Installation

The Ta leo Connec t C l i en t sh ips as two d i f fe ren t f i l es . The f i r s t i s a s tandard Windows ins ta l l e r . S imp ly doub le c l i ck the Ta leoConnec tC l ien t .exe f i l e and fo l l ow the on-sc reen ins t ruc t i ons ( the re a re no comp lex cho ices , on l y the t yp ica l pages o f any p roduc t i ns ta l l e r ) . You are p rompted fo r a password to p roceed w i th the ins ta l l a t i on , wh ich i s p rov ided by Ta leo Cus tomer Suppor t .

The second de l i ve rab le i s a bund le o f the b ina ry f i l es requ i red to execu te in teg ra t i on processes in a UN IX /L INUX env i ronment . S imp ly unpack the Ta leoConnectC l i en t . ta r .gz f i l e t o a new fo lder on the UN IX /L INUX sys tem.

Feature Pack Delivery

The Ta leo Connect C l i en t i s de l i ve red w i th the fea ture packs fo r our f l agsh ip P ro fess iona l p roduc t o f the Ta leo En te rpr i se Ed i t i on . I f you a re us ing the c l i en t w i th ano ther o f our p roduc ts , you w i l l need to i ns ta l l t he re levan t f ea tu re pack by s imp ly copy ing the *.fp f i l e to the featurepacks f o lde r o f the ins ta l l a t i on d i rec to ry . Fo r a s tandard Windows ins ta l l a t i on , the pa th wou ld be :

C:\Program Files\Taleo Connect Client\featurepacks

Using the Client

Each t ime you use the C l ien t , you a re p rompted to connec t t o you r Ta leo p roduc t . In the fo l l ow ing d ia log , you can se lec t you r env i ronment f i l e and then op t i ona l l y en te r your au thent i ca t i on in fo rmat ion ( i f no t p resen t i n the env i ronment f i l e i t se l f ) :

I f you r connec t i v i t y i n fo rmat ion i s i nco r rec t o r your Ta leo p roduc t i s no t ava i l ab le , then you canno t access the Des ign env i ronment . There i s no such prompt when us ing the run t ime execut i on sc r ip t .


Appendices Migration

Migration

Version 2.1

InstallationThere a re no changes in the ins ta l l a t i on p rocedure s ince ve rs ion 2 .1 . We s imp ly recommend tha t you un ins ta l l t he ve rs ion 2 .1 app l i ca t ion be fo re ins ta l l i ng the cur ren t ve rs ion .

DeploymentThe conf igu ra t ion , expo r t and impor t f i l e f o rmats have been enhanced s ince vers ion 2 .1 . Bo th the user in te r face and the execut i on sc r i p t w i l l au tomat ica l l y upgrade these f i l es w i th no manua l in te rven t ion . I t i s recommended , however , t o exp l i c i t l y upgrade your ex i s t ing conf igu ra t i on f i l es and impor t /expor t spec i -f i ca t i ons by s imp ly open ing them in the deve lopment env i ronment and sav ing them aga in . Be su re to look a t any d iagnos t i c messages tha t may ind ica te a poss ib le p rob lem w i th you r f i l es .

The execut i on sc r ip t has been changed to i nc lude an upgrade o f ce r ta in l i b ra r i es , bu t i t s s igna ture remains the same. As such, any processes ca l l i ng the execu t i on sc r ip t s w i l l con t inue to func t i on as be fo re .

ChangesPing dialog

The p ing d ia l og now requ i res the p roduc t se lec t ion p r io r t o se lec t ing the env i ronment f i l e . A lso , the las t used p roduc t and env i ronment f i l e a re kept in a l oca l cache and de fau l ted to du r ing the cu r ren t sess ion and a lso when s ta r t i ng a new sess ion .

Environment file

The Ta leo Connect C l i en t env i ronment f i l e f o rmat has changed to be t te r suppor t a range o f Ta leo produc ts . The pa th e lement o f the URL i s no l onger requ i red in the env i ronment f i l e and w i l l s imp l y be ignored i f us ing ex i s t i ng env i ronment f i l es . See the Env i ronment F i l e sec t i on above fo r more de ta i l s .

Feature pack

A l l con f igu ra t i on f i l es , impor t and expor t spec i f i ca t i ons mus t now be assoc ia ted to a p roduc t fea ture pack . Moreove r , when us ing an impor t o r expor t spec i f i ca t i on in a conf igu ra t i on , the produc t ( codes ) mus t match . For ex i s t ing f i l es , th i s i s hand led dur ing the au tomat ic upgrade p rocedure by ass ign ing a p roduc t code based on the ex is t ing mode l ve rs ion fo r impor t and expor t spec i f i ca t ions and the p rov ided Ta leo Connec t Serve r ve rs ion fo r the conf igu ra t i on f i l es .

Import specifications

The impor t spec i f i ca t i ons no l onger spec i f y an en t i t y t o impor t , bu t ra ther a serv i ce and opera t i on to execu te . These no t i ons were a l ready pa r t i a l l y p resen t i n the 2 .1 ve rs ion in the de fau l t ope ra t i on concep t tha t was l im i ted to the c rea te , upda te and merge op t i ons . Fo r ex is t ing f i l es , th i s i s hand led du r ing the au tomat i c upgrade p rocedure by us ing the en t i t y name as se rv i ce name and the de fau l t ope ra t i on as opera t i on . Th i s i s poss ib l e s ince a l l impor tab le en t i t i es i n the Ta leo P ro fess iona l p roduc t have cor re-spond ing impor t serv ices .

Wi th th i s adap ta t i on to the Ta leo In tegra t i on o f fe r ing , the impor t spec i f i ca t i on and ed i to r now suppor t the no t ion o f pa ramete rs . Howeve r , th i s has no impac t on ex i s t i ng f i l es as a l l p rev ious opera t i ons ( c rea te ,



upda te and merge ) had and s t i l l have a s ing le pa rameter ( tha t i s the en t i t y t o impor t ) and a l l co lumn de f in i -t i ons de fau l t t o the f i r s t pa ramete r . Hence , the re i s no th ing to ad jus t rega rd ing th is change in behav io r .

Diagnostics

Diagnos t i cs have been improved fo r bo th the impor t and expor t spec i f i ca t i ons . You can see these when us ing the respec t i ve ed i to rs and se lec t i ng the d iagnos t i c v i ew a t the bo t tom o f the w indow.

Taleo Business Edition

The Ta leo Connect C l ien t now suppor t s the Ta leo Bus iness Ed i t i on p roduc ts . See the Ta leo Bus iness Ed i t i on sec t ion be low fo r more de ta i l s .

Version 2.0

InstallationThe core o f Ta leo Connec t C l ien t has rema ined the same s ince the 2 .0 ve rs ion . However , the use r i n te r -face has been en t i re l y revamped. I n add i t i on , the C l i en t now comes w i th a p roper Windows ins ta l l e r tha t c rea tes the requ i red fo lder s t ruc tu re . We recommend tha t you ins ta l l t he new C l ien t in a d i f f e ren t l oca t ion than the 2 .0 ve rs ion . You can keep your con f igu ra t i on f i l es i n the i r cu r ren t l oca t i on o r move them.

DeploymentThe con f igura t ion f i l es have been upgraded s ince the 2 .0 ve rs ion . A few manda tory e lements have been added and some fea tu res depreca ted ( see L im i ta t i ons sec t i on ) . Bo th the use r i n te r face and the execu t i on sc r ip t w i l l au tomat i ca l l y upgrade the con f igura t ion w i th no manua l in te rven t ion . I t i s recommended to exp l i c i t l y m ig ra te your o ld con f igura t ion f i l es by s imp ly open ing them in the Conf igu ra t ion Ed i to r and sav ing them aga in .

A l l o f the reques t f i l es used w i th vers ion 2 .0 w i l l a l so func t i on w i th vers ion 2 .1 and ve rs i on 2 .2 .

The execut i on sc r ip t has the same name and accep ts a l l o f the same pa ramete rs .

LimitationsTa leo Connec t C l i en t , ve rs ion 2 .0 on ly suppor ted the Mixed commun ica t ion t ype , wh ich i s now depre-ca ted . I f your Ta leo env i ronment i s a l ready conf igu red in th i s fash ion , then your in teg ra t i on p rocesses w i l l con t inue to work th rough ve rs ion 2 .2 . You w i l l see d iagnos t i c i n fo rmat ion ind i ca t ing tha t the communica-t i on t ype i s depreca ted .

Ta leo Connec t C l i en t , ve rs ion 2 .0 a l l owed the exp l i c i t con f igura t ion o f an HTTP proxy th rough the con f ig -u ra t ion f i l e . Th is i s no longer ava i lab le o r suppor ted in ve rs ion 2 .1 o r ve rs ion 2 .2 . We have ha rmon i zed the behav io r o f the C l i en t w i th the Java s tandards ( see HTTP Proxy sec t i on ) . The procedure to m igra te th i s fea tu re g i ven the fo l l ow ing 2 .0 con f igura t ion :



i s to add the fo l l ow ing s ta r tup pa rameters in the c l i en t execu t ion sc r i p t (TaleoConnectClient.bat) :


The mos t impor tan t l im i ta t i on , the use o f the Ex t rac t bu i lder f i l es , i s documented be low.

Extract builder

The Ex t rac t (o r ex t rac t i on ) Bu i l de r i s no l onger suppor ted in vers ion 2 .1 o r ve rs ion 2 .2 . I t has been rep laced w i th the Expor t Ed i to r fea tu re w i th in the cen t ra l i zed Des ign env i ronment . The fo rmat o f the ex t rac t f i l es i s no t compat ib le w i th the Expor t Ed i to r . However , the genera ted reques t f i l es can s t i l l be sen t us ing Ta leo Connect C l ien t ( jus t as any o ther reques t f i l e ) .

Version 1.0

InstallationTa leo Connec t C l i en t has been comp le te l y rewr i t t en s ince vers ion 1 .0 . As such, i t i s recommended to ins ta l l ve rs i on 2 .2 i n a d i f fe ren t l oca t ion .

DeploymentThe in teg ra t ion p rocess con f igura t ion in the 1 .0 ve rs ion were conta ined in P roper t i es f i l es (*.proper-ties) . Excep t fo r the l im i ta t i ons s ta ted be low, these f i l es a re fu l l y suppor ted in the cu r ren t ve rs ion . However , we s t rong ly recommend mig ra t ing these conf igu ra t ions to the 2 .2 l eve l to enab le the mon i to r ing fea tu re and , i f necessary , access the new p rocess ing s teps . Th i s i s a s t ra igh t fo rward p rocess : s imp l y open the P roper t i es f i l e (F i l e /Open/Legacy Con f igura t i on ) ; ad jus t the con f igu ra t i on ; and save to a *_cfg.xml f i l e . The o the r a l t e rna t i ve i s to d i rec t l y i nvoke the execut i on sc r ip t w i th the l egacy con f igu ra t i on f i l es . Th i s w i l l work seamless l y w i th the except i ons o f the po in ts no ted in the l im i ta t i ons .

A l l o f the reques t f i l es used w i th vers ion 1 .0 a lso func t i on w i th vers ion 2 .2 .

The execut ion sc r ip t has been renamed f rom riscient.bat t o TaleoConnectCient.bat. However , i t accep ts the same th ree paramete rs .

LimitationsTa leo Connec t C l i en t , ve rs ion 1 .0 on ly suppor ted the Mixed commun ica t ion t ype , wh ich i s now depre-ca ted . I f your Ta leo env i ronment i s a l ready conf igu red in th i s fash ion , then your in teg ra t i on p rocesses w i l l con t inue to work th rough ve rs ion 2 .2 . You w i l l s imp ly see d iagnos t ic i n fo rmat ion ind ica t ing tha t the communica t i on t ype i s depreca ted .



Ta leo Connec t C l i en t , ve rs ion 1 .0 a l l owed the exp l i c i t con f igura t ion o f an HTTP proxy th rough the con f ig -u ra t ion f i l e . Th is i s no longer ava i lab le o r suppor ted in ve rs ion 2 .1 o r ve rs ion 2 .2 . We have ha rmon i zed the behav io r o f the C l i en t w i th the Java s tandards ( see HTTP Proxy sec t i on ) . You may l eave the proxy.* proper t i es i n the f i l e bu t they w i l l be igno red . The p rocedure to m ig ra te th i s f ea tu re f rom the fo l l ow ing legacy conf igu ra t ion f i l e :

...

proxy.host=proxy.acme.net

proxy.port=3128

i s to add the fo l l ow ing s ta r tup pa rameters in the c l i en t execu t ion sc r i p t :



Appendices Volume Limits

Volume Limits

Taleo Connect Client Self-Service Tools

The use o f the Ta leo Connect C l i en t Se l f -Se rv i ce Too l and o f the Ta leo Managed In tegra t i ons on the Connect In teg ra t ion p la t fo rm are sub jec t to the fo l l ow ing vo lume l im i ts :

• Max imum of 100 000 records and 3 hours o f execu t i on pe r ex t rac t i on t ransac t i on .

• Max imum o f 5 000 records and 3 hours o f execu t i on pe r impor t t ransac t ion .

• Max imum of 250 000 ex t rac ted reco rds pe r day .

• Max imum of 750 000 records per day fo r cus tomers w i th p remium da ta ex t rac t op t i on .

• Max imum of 25 000 impor ted records per day .

• Max imum of 2 concur ren t i n tegra t ion reques ts per cus tomer per p roduc t .


Appendices How to Execute Taleo Connect Client from a Java Application

How to Execute Taleo Connect Client from aJava Application

I t i s poss ib le to run Ta leo Connec t C l i en t f rom ano the r Java p rog ram. To do so , you must insu re tha t the ca l l i ng p rog ram's JVM is runn ing w i th the p roper env i ronmenta l va r i ab les and then ca l l the execute() me thod o f the c lass .

Execution Environment

I n o rde r fo r the Ta leo Connec t C l i en t to execu te co r rec t l y , the p roper execut i on env i ronment must be ava i l -ab le . The fo l l ow ing execu t i on sc r ip t i s the m in ima l requ i red conf igu ra t ion fo r a t yp i ca l W indows ins ta l l a -t i on :

SET IC_HOME="C:\Program Files\Taleo Connect Client";

SET CLASSPATH=

"%IC_HOME%\lib\taleo-integrationclient.jar";"%IC_HOME%\log";

java.exe

-Dcom.taleo.integration.client.install.dir="%IC_HOME%"

-Djava.endorsed.dirs="%IC_HOME%\lib\endorsed"

-Djavax.xml.parsers.SAXParserFactory=

org.apache.xerces.jaxp.SAXParserFactoryImpl

-Djavax.xml.transform.TransformerFactory=

net.sf.saxon.TransformerFactoryImpl

-Dorg.apache.commons.logging.Log=

org.apache.commons.logging.impl.Log4JLogger

-classpath %CLASSPATH%

com.acme.integration.ACMEIntegrationProcess

The IC_HOME var iab le de f ines the ins ta l l a t i on d i rec to ry o f the Ta leo Connect C l i en t . Th i s i n fo rmat ion i s requ i red because seve ra l l i b ra r i es and resources a re de l i ve red w i th the ins ta l l a t i on bund le .

The c lasspa th o f the app l i ca t i on i s f a i r l y s imp le because the taleo-integrationclient.jar con ta ins the fu l l c lasspa th embedded in i t s man i fes t . Th is works f ine w i th most JRE imp lementa t ions . I f any c lass-pa th prob lems occurs , you may a lso exp l i c i t l y de f ine the c lasspath by inc lud ing a l l Java l ib ra r ies (*.jar) i n the lib and lib/endorsed f o lders . O f course , the c lasspa th mus t a l so con ta in the requ i red re fe rences to the hos t Java app l i ca t ion .

In the Java invoca t ion command i t se l f , we f i r s t se t the Ta leo Connec t C l i en t i ns ta l l a t i on d i rec to ry exp l i c -i t l y . Th i s i s requ i red ma in l y to l oca te the fea ture pack f i l es . The nex t two ins t ruc t i ons ensure tha t the p roper ve rs i on o f the Xe rces XML pa rse r i s used . Then , because most o f the XSLT f i l es used in the Ta leo Connect C l i en t a re i n vers ion 2 .0 o f th i s spec i f i ca t ion , we ensure tha t the XSL t rans fo rmer suppor ts i t ( i n th i s case by choos ing the Saxon 8 Bas ic eng ine ) . The f ina l sys tem proper t y d i rec ts the Apache Jakar ta


Appendices How to Execute Taleo Connect Client from a Java Application

Commons Logg ing p ro jec t to use the Apache Log4J sys tem. Th i s i s the reason why the log f o lde r i s pa r t o f the c l asspa th , as the log4j.properties con f igura t ion f i l e i s l oca ted the re . The i nvoked c lass com.acme.integration.ACMEIntegrationProcess i s used he re on l y as an examp le and shou ld be rep laced by the ac tua l en t ry po in t o f your Java app l i ca t ion hos t ing the Ta leo Connect C l i en t .

Execution Entry Point

The co r rec t en t r y po in t t o execu te the Ta leo Connec t C l i en t i s : com.taleo.integration.client.Client.execute(). The JavaDoc p rov ided fo r th i s method in the docs/api fo lde r o f the p roduc t desc r ibes the behav io r and paramete r va lues .


Appendices Taleo Business Edition

Taleo Business Edition

Users o f the Ta leo Bus iness Ed i t i on (TBE ) p roduc t shou ld f i r s t read th rough the genera l Use r Gu ide and then consu l t the i t ems be low tha t con ta in spec ia l charac te r i s t i cs re l a t ing to tha t p roduc t .

Account Creation

To access the Ta leo Bus iness Ed i t i on in tegra t i on o f fe r ing us ing the Ta leo Connect C l i en t , an admin is t ra to r use r accoun t must be used. On ly TBE cus tomers w i th the p remium se rv ice l eve l can access the in tegra t ion o f fe r ing .

Environment File

Ta leo Bus iness Ed i t i on cus tomers do no t have the i r own doma in name as i s the case w i th the Ta leo En te r -p r i se Ed i t i on ( i . e . h t tp : / /acme. ta leo .ne t ) . I ns tead, TBE users use a common web s i te and l ogon w i th a company code. As such , the env i ronment f i l e fo r a TBE cus tomer shou ld be a tex t f i l e named acme_env.properties and con ta in the fo l l ow ing l i nes :

username=integrator

companycode=ACME

http://acme.taleo.net

http://acme.taleo.net

taleo connect client - oracle · taleo connect client 1-1 introduction taleo connect platform taleo...

Documents