Talend Open Studio Components

4.X

Reference Guide

Intentionally Blank

ii

Talend Open Studio Components

Creative Commons License

Version 4.0_b
Adapted for Talend Open Studio v4.0.x. Supersedes previous Reference Guide releases.

Copyright
This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please check: http://creativecommons.org/licenses/by-nc-sa/2.0/

Creative Commons License

Talend Open Studio Components

iii

iv

Talend Open Studio Components

Creative Commons License

Talend Open Studio Components Reference Guide ......................... i

Preface ....................................................................... xxi Purpose ................................................................. xxi Audience ............................................................... xxi Typographical conventions .................................. xxi History of changes ...................................................xxii Feedback and Support ............................................xxii

Business Intelligence components .............. 1
tDB2SCD ...................................................................... 2 tDB2SCD properties ................................................ 2 Related scenarios ..................................................... 3 tDB2SCDELT .............................................................. 4 tDB2SCDELT Properties ........................................ 4 Related Scenario ...................................................... 6 tGreenplumSCD .......................................................... 7 tGreenplumSCD Properties ..................................... 7 Related scenario ...................................................... 8 tInformixSCD .............................................................. 9 tInformixSCD properties ......................................... 9 Related scenario .................................................... 10 tIngresSCD ................................................................ 11 tIngresSCD Properties ........................................... 11 Related scenario .................................................... 12 tMondrianInput ........................................................ 13 tMondrianInput Properties .................................... 13 Scenario: Cross-join tables .................................... 14 tMSSqlSCD ................................................................ 17 tMSSqlSCD Properties .......................................... 17 Related scenario .................................................... 18 tMysqlSCD ................................................................. 19 tMysqlSCD Properties ........................................... 19 SCD management methodologies ...................... 20 SCD keys ....................................................... 22 Combining SCD types ................................... 22 Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) ........................... 23 tMysqlSCDELT ......................................................... 31 tMysqlSCDELT Properties ................................... 31 Related Scenario .................................................... 33 tOracleSCD ................................................................ 34 tOracleSCD Properties .......................................... 34 Related scenario .................................................... 35 tOracleSCDELT ........................................................ 36 tOracleSCDELT Properties ................................... 36 Creative Commons License

Related Scenario ....................................................38 tParAccelSCD ............................................................39 tParAccelSCD Properties .......................................39 Related scenario .....................................................40 tPostgresPlusSCD ......................................................41 tPostgresPlusSCD Properties .................................41 Related scenario .....................................................42 tPostgresPlusSCDELT ..............................................43 tPostgresPlusSCDELT Properties ..........................43 Related Scenario ....................................................45 tPostgresqlSCD ..........................................................46 tPostgresqlSCD Properties .....................................46 Related scenario .....................................................47 tPostgresqlSCDELT ..................................................48 tPostgresqlSCDELT Properties .............................48 Related Scenario ....................................................50 tSPSSInput .................................................................51 tSPSSInput properties ............................................51 Scenario: Displaying the content of an SPSS .sav file 51 tSPSSOutput ..............................................................54 tSPSSOutput properties .........................................54 Scenario: Writing data in an .sav file .....................54 tSPSSProperties .........................................................57 tSPSSProperties properties ....................................57 Related scenarios ...................................................57 tSPSSStructure ..........................................................58 tSPSSStructure properties ......................................58 Related scenarios ...................................................58 tSybaseSCD ................................................................59 tSybaseSCD properties ..........................................59 Related scenarios ...................................................60 tSybaseSCDELT ........................................................61 tSybaseSCDELT Properties ...................................61 Related Scenario ....................................................63

Business components .................................65
tAlfrescoOutput .........................................................66 tAlfresco Properties ...............................................66 Installation procedure .........................................67 Prerequisites ...................................................68 Installing the Talend Alfresco module ...........68 Useful information for advanced use .............69 Dematerialization, tAlfrescoOutput, and Enterprise Content Management ...................................................70 Scenario: Creating documents on an Alfresco server 71 tCentricCRMInput ....................................................77 tCentricCRMInput Properties ................................77 Related Scenario ....................................................77 tCentricCRMOutput .................................................78 tCentricCRMOutput Properties .............................78 v

Talend Open Studio Components

Related Scenario .................................................... 78 tHL7Input .................................................................. 79 tHL7Input Properties ............................................. 79 Scenario: Retrieving information about patients and events from a HL7 file. ............................................... 80 tMicrosoftCRMInput ................................................ 83 tMicrosoftCRMInput Properties ............................ 83 Scenario: Writing data in a Microsoft CRM database and putting conditions on columns to extract specified rows ............................................................................. 84 tMicrosoftCRMOutput ............................................. 91 tMicrosoftCRMOutput Properties ......................... 91 Related Scenario .................................................... 92 tMSAXInput .............................................................. 93 tMSAXInput properties ......................................... 93 Related scenarios ................................................... 93 tMSAXOutput ........................................................... 94 tMSAXOutput properties ...................................... 94 Scenario 1: Inserting data in a defined table in a MicrosoftAX server ......................................................... 95 Scenario 2: Deleting data from a defined table in a MicrosoftAX server .................................................... 98 tOpenbravoERPInput ............................................ 101 tOpenbravoERPInput properties ........................ 101 Related Scenario ................................................. 102 tOpenbravoERPOutput .......................................... 103 tOpenbravoERPOutput properties ...................... 103 Related scenario ................................................. 103 tSalesforceBulkExec ................................................ 104 tSalesforceBulkExec Properties .......................... 104 Related Scenario: ................................................ 105 tSalesforceConnection ............................................ 106 tSalesforceConnection properties ........................ 106 Related scenario .................................................. 106 tSalesforceGetDeleted ............................................. 107 tSalesforceGetDeleted properties ........................ 107 Scenario: Recovering deleted data from the Salesforce server ................................................................ 108 tSalesforceGetServerTimestamp ........................... 111 tSalesforceGetServerTimestamp properties ........ 111 Related scenarios ................................................. 112 tSalesforceGetUpdated ........................................... 113 tSalesforceGetUpdated properties ....................... 113 Related scenarios ................................................. 114 tSalesforceInput ...................................................... 115 tSalesforceInput Properties .................................. 115 Related scenario .................................................. 116 tSalesforceOutput .................................................... 117 tSalesforceOutput Properties ............................... 117 Scenario: Deleting data from the Account object 118 tSalesforceOutputBulk ........................................... 121 tSalesforceOutputBulk Properties ....................... 121 Scenario: Inserting transformed bulk data into your vi

Salesforce.com ...........................................................121 tSalesforceOutputBulkExec ....................................126 tSalesforceOutputBulkExec Properties ................126 Scenario: Inserting bulk data into your Salesforce.com ...................................................................127 tSAPCommit ............................................................131 tSAPCommit Properties .......................................131 Related scenario ...................................................131 tSAPConnection .......................................................132 tSAPConnection properties ..................................132 Related scenarios .................................................132 tSAPInput .................................................................133 tSAPInput Properties ...........................................133 Scenario 1: Retrieving metadata from the SAP system 134 Scenario 2: Reading data in the different schemas of the RFC_READ_TABLE function ............................140 tSAPOutput ..............................................................146 tSAPOutput Properties .........................................146 Related scenario ...................................................147 tSAPRollback ...........................................................148 tSAPRollback properties ......................................148 Related scenarios .................................................148 tSugarCRMInput .....................................................149 tSugarCRMInput Properties .................................149 Scenario: Extracting account data from SugarCRM .. 149 tSugarCRMOutput ..................................................151 tSugarCRMOutput Properties ..............................151 Related Scenario ..................................................151 tVtigerCRMInput ....................................................152 tVtigerCRMInput Properties ................................152 Related Scenario ..................................................152 tVtigerCRMOutput .................................................153 tVtigerCRMOutput Properties .............................153 Related Scenario ..................................................153

Custom Code components ......................155
tGroovy .....................................................................156 tGroovy Properties ...............................................156 Related Scenarios .................................................156 tGroovyFile ...............................................................157 tGroovyFile Properties .........................................157 Scenario: Calling a file which contains Groovy code 157 tJava ..........................................................................159 tJava Properties ....................................................159 Scenario: Printing out a variable content .............159 tJavaFlex ...................................................................162 tJavaFlex properties .............................................162 Scenario1: Generating data flow ..........................163 Scenario2: Processing rows of data with tJavaFlex ... Creative Commons License

Talend Open Studio Components

165 tJavaRow .................................................................. 168 Propriétés du tJavaRow ....................................... 168 Related scenario .................................................. 168 tLibraryLoad ........................................................... 169 tLibraryLoad Properties ...................................... 169 Scenario: Checking the format of an e-mail addressl 169 tPerl .......................................................................... 172 tPerl properties .................................................... 172 Scenario: Displaying a number of processed lines .... 172

Data Quality components ....................... 175
tAddCRCRow .......................................................... 176 tAddCRCRow properties .................................... 176 Scenario: Adding a surrogate key to a file .......... 176 tExtractRegexFields ............................................... 179 tFuzzyMatch ............................................................ 180 tFuzzyMatch properties ....................................... 180 Scenario 1: Levenshtein distance of 0 in first names 181 Scenario 2: Levenshtein distance of 1 or 2 in first names ....................................................................... 183 Scenario 3: Metaphonic distance in first name ... 184 tIntervalMatch ........................................................ 185 tIntervalMatch properties .................................... 185 Scenario: Identifying Ip country (Perl and Java) . 186 tParseAddress .......................................................... 190 tParseAddress properties ..................................... 190 Related scenario .................................................. 191 tParseName .............................................................. 192 tParseName Properties ........................................ 192 Related scenario .................................................. 193 tReplaceList ............................................................. 194 tReplaceList Properties ........................................ 194 Scenario: Replacement from a reference file ...... 195 tSchemaComplianceCheck ..................................... 198 tSchemaComplianceCheck Properties ................ 198 Scenario: Validating dates against schema (java) 199 tUniqRow ................................................................. 203 tUniqRow Properties ........................................... 203 Scenario: Unduplicating entries .......................... 203

Databases components ............................ 205
tAccessInput ............................................................ 206 tAccessInput properties ....................................... 206 Related scenarios ................................................. 207 tAccessOutput .......................................................... 208 tAccessOutput properties .................................... 208 Related scenarios ................................................. 210 Creative Commons License

tAccessRow ...............................................................211 tAccessRow properties .........................................211 Related scenarios .................................................212 tAS400Close .............................................................213 tAS400Close properties .......................................213 Related scenario ...................................................213 tAS400Commit .........................................................214 tAS400Commit Properties ...................................214 Related scenario ...................................................214 tAS400Connection ...................................................215 tAS400Connection Properties ..............................215 Related scenario ...................................................216 tAS400Input .............................................................217 tAS400Input properties ........................................217 Related scenarios .................................................218 tAS400LastInsertId .................................................219 tAS400LastInsertId properties .............................219 Related scenario ...................................................219 tAS400Output ..........................................................220 tAS400Output properties .....................................220 Related scenarios .................................................222 tAS400Rollback .......................................................223 tAS400Rollback properties ..................................223 Related scenarios .................................................223 tAS400Row ...............................................................224 tAS400Row properties .........................................224 Related scenarios .................................................226 tCreateTable .............................................................227 tCreateTable Properties ........................................227 Scenario: Creating new table in a Mysql Database ... 229 tDB2BulkExec ..........................................................232 tDB2BulkExec properties ....................................232 Related scenarios .................................................234 tDB2Close .................................................................235 tDB2Close properties ...........................................235 Related scenario ...................................................235 tDB2Commit ............................................................236 tDB2Commit Properties .......................................236 Related scenario ...................................................236 tDB2Connection .......................................................237 tDB2Connection properties .................................237 Related scenarios ................................................238 tDB2Input .................................................................239 tDB2Input properties ...........................................239 Related scenarios .................................................240 tDB2Output ..............................................................241 tDB2Output properties .........................................241 Related scenarios .................................................243 tDB2Rollback ...........................................................244 tDB2Rollback properties .....................................244 Related scenarios .................................................244 tDB2Row ...................................................................245 vii

Talend Open Studio Components

tDB2Row properties ............................................ 245 Related scenarios ................................................. 247 tDB2SCD .................................................................. 248 tDB2SCDELT .......................................................... 249 tDB2SP ..................................................................... 250 tDB2SP properties ............................................... 250 Related scenarios ................................................. 251 tDBInput ................................................................. 252 tDBInput properties ............................................. 252 Scenario 1: Displaying selected data from DB table . 253 Scenario 2: Using StoreSQLQuery variable ....... 254 tDBOutput ............................................................... 256 tDBOutput properties .......................................... 256 Scenario: Displaying DB output ......................... 258 tDBSQLRow ............................................................ 261 tDBSQLRow properties ...................................... 261 Scenario: Resetting a DB auto-increment ........... 262 tEXAInput ............................................................... 264 tEXAInput properties .......................................... 264 Related scenarios ................................................. 265 tEXAOutput ............................................................ 266 tEXAOutput properties ........................................ 266 Related scenario .................................................. 268 tEXARow ................................................................. 269 tEXARow properties ........................................... 269 Related scenarios ................................................. 270 tEXistConnection .................................................... 271 tEXistConnection properties ............................... 271 Related scenarios ................................................ 271 tEXistDelete ............................................................. 272 tEXistDelete properties ....................................... 272 Related scenario ................................................. 273 tEXistGet .................................................................. 274 tEXistGet properties ............................................ 274 Related scenario ................................................. 275 tEXistList ................................................................. 276 tEXistList properties ............................................ 276 Related scenarios ................................................ 277 tEXistPut .................................................................. 278 tEXistPut properties ............................................ 278 Related scenario ................................................. 279 tEXistXQuery .......................................................... 280 tEXistXQuery properties ..................................... 280 Related scenario ................................................. 281 tEXistXUpdate ........................................................ 282 tEXistXUpdate properties ................................... 282 Related scenario ................................................. 283 tFirebirdClose .......................................................... 284 tFirebirdClose properties ..................................... 284 Related scenario .................................................. 284 tFirebirdCommit ..................................................... 285 tFirebirdCommit Properties ................................. 285 viii

Related scenario ...................................................285 tFirebirdConnection ................................................286 tFirebirdConnection properties ............................286 Related scenarios ................................................286 tFirebirdInput ..........................................................288 tFirebirdInput properties ......................................288 Related scenarios .................................................289 tFirebirdOutput .......................................................290 tFirebirdOutput properties ...................................290 Related scenarios .................................................292 tFirebirdRow ............................................................293 tFirebirdRow properties .......................................293 Related scenarios .................................................295 tGreenplumBulkExec ..............................................296 tGreenplumBulkExec Properties .........................296 Related scenarios .................................................298 tGreenplumClose .....................................................299 tGreenplumClose properties ................................299 Related scenario ...................................................299 tGreenplumCommit ................................................300 tGreenplumCommit Properties ............................300 Related scenario ...................................................300 tGreenplumConnection ...........................................301 tGreenplumConnection properties .......................301 Related scenarios ................................................302 tGreenplumInput .....................................................303 tGreenplumInput properties .................................303 Related scenarios .................................................304 tGreenplumOutput ..................................................305 tGreenplumOutput Properties ..............................305 Related scenarios .................................................307 tGreenplumOutputBulk ..........................................308 tGreenplumOutputBulk properties .......................308 Related scenarios .................................................309 tGreenplumOutputBulkExec .................................310 tGreenplumOutputBulkExec properties ...............310 Related scenarios .................................................311 tGreenplumRollback ...............................................312 tGreenplumRollback properties ...........................312 Related scenarios .................................................312 tGreenplumRow .......................................................313 tGreenplumRow Properties ..................................313 Related scenarios .................................................315 tGreenplumSCD ......................................................316 tHiveClose .................................................................317 tHiveClose properties ...........................................317 Related scenario ...................................................317 tHiveConnection ......................................................318 tHiveConnection properties .................................318 Related scenario ...................................................318 tHiveRow ..................................................................319 tHiveRow properties ............................................319 Related scenarios .................................................320 Creative Commons License

Talend Open Studio Components

tHSQLDbInput ........................................................ 321 tHSQLDbInput properties ................................... 321 Related scenarios ................................................. 322 tHSQLDbOutput ..................................................... 323 tHSQLDbOutput properties ................................ 323 Related scenarios ................................................. 325 tHSQLDbRow ......................................................... 326 tHSQLDbRow properties .................................... 326 Related scenarios ................................................. 327 tInformixBulkExec .................................................. 328 tInformixBulkExec Properties ............................. 328 Scénario associé .................................................. 330 tInformixClose ......................................................... 331 tInformixClose properties .................................... 331 Related scenario .................................................. 331 tInformixCommit .................................................... 332 tInformixCommit properties ................................ 332 Related Scenario .................................................. 332 tInformixConnection .............................................. 333 tInformixConnection properties .......................... 333 Related scenario .................................................. 334 tInformixInput ........................................................ 335 tInformixInput properties .................................... 335 Related scenarios ................................................. 336 tInformixOutput ...................................................... 337 tInformixOutput properties .................................. 337 Related scenarios ................................................. 339 tInformixOutputBulk ............................................. 340 tInformixOutputBulk properties .......................... 340 Related scenario .................................................. 341 tInformixOutputBulkExec ..................................... 342 tInformixOutputBulkExec properties .................. 342 Related scenario .................................................. 344 tInformixRollback ................................................... 345 tInformixRollback properties .............................. 345 Related Scenario .................................................. 345 tInformixRow .......................................................... 346 tInformixRow properties ..................................... 346 Related scenarios ................................................. 348 tInformixSCD .......................................................... 349 tInformixSP ............................................................. 350 tInformixSP properties ........................................ 350 Related scenario .................................................. 351 tIngresClose ............................................................. 353 tIngresClose properties ........................................ 353 Related scenario .................................................. 353 tIngresCommit ........................................................ 354 tIngresCommit Properties .................................... 354 Related scenario .................................................. 354 tIngresConnection ................................................... 355 tIngresConnection Properties .............................. 355 Related scenarios ................................................. 355 tIngresInput ............................................................. 356 Creative Commons License

tIngresInput properties .........................................356 Related scenarios .................................................357 tIngresOutput ...........................................................358 tIngresOutput properties ......................................358 Related scenarios .................................................360 tIngresRollback ........................................................361 tIngresRollback properties ...................................361 Related scenarios .................................................361 tIngresRow ...............................................................362 tIngresRow properties ..........................................362 Related scenarios .................................................363 tIngresSCD ...............................................................364 tInterbaseClose ........................................................365 tInterbaseClose properties ....................................365 Related scenario ...................................................365 tInterbaseCommit ....................................................366 tInterbaseCommit Properties ...............................366 Related scenario ...................................................366 tInterbaseConnection ..............................................367 tInterbaseConnection properties ..........................367 Related scenarios ................................................367 tInterbaseInput ........................................................369 tInterbaseInput properties ....................................369 Related scenarios .................................................370 tInterbaseOutput .....................................................371 tInterbaseOutput properties ..................................371 Related scenarios .................................................373 tInterbaseRollback ..................................................374 tInterbaseRollback properties ..............................374 Related scenarios .................................................374 tInterbaseRow ..........................................................375 tInterbaseRow properties .....................................375 Related scenarios .................................................377 tJavaDBInput ...........................................................378 tJavaDBInput properties ......................................378 Related scenarios .................................................379 tJavaDBOutput ........................................................380 tJavaDBOutput properties ....................................380 Related scenarios .................................................382 tJavaDBRow .............................................................383 tJavaDBRow properties .......................................383 Related scenarios .................................................384 tJDBCColumnList ...................................................385 tJDBCColumnList Properties ..............................385 Related scenario ...................................................385 tJDBCClose ..............................................................386 tJDBCClose properties .........................................386 Related scenario ...................................................386 tJDBCCommit .........................................................387 tJDBCCommit Properties ....................................387 Related scenario ...................................................387 tJDBCConnection ....................................................388 tJDBCConnection Properties ...............................388 ix

Talend Open Studio Components

Related scenario .................................................. 389 tJDBCInput ............................................................. 390 tJDBCInput properties ......................................... 390 Related scenarios ................................................. 391 tJDBCOutput .......................................................... 392 tJDBCOutput properties ...................................... 392 Related scenarios ................................................. 394 tJDBCRollback ........................................................ 395 tJDBCRollback properties ................................... 395 Related scenario .................................................. 395 tJDBCRow ............................................................... 396 tJDBCRow properties .......................................... 396 Related scenarios ................................................. 397 tJDBCSP .................................................................. 399 tJDBCSP Properties ............................................ 399 Related scenario .................................................. 400 tJDBCTableList ...................................................... 401 tJDBCTableList Properties .................................. 401 Related scenario .................................................. 401 tLDAPAttributesInput ........................................... 402 tLDAPAttributesInput Properties ........................ 402 Related scenario .................................................. 404 tLDAPInput ............................................................. 405 tLDAPInput Properties ........................................ 405 Scenario: Displaying LDAP directory’s filtered content ............................................................................. 406 tLDAPOutput .......................................................... 409 tLDAPOutput Properties ..................................... 409 Scenario: Editing data in a LDAP directory ........ 410 tLDAPRenameEntry .............................................. 413 tLDAPRenameEntry properties .......................... 413 Related scenarios ................................................. 414 tMaxDBInput .......................................................... 415 tMaxDBInput properties ...................................... 415 Related scenario .................................................. 416 tMaxDBOutput ........................................................ 417 tMaxDBOutput properties ................................... 417 Related scenario .................................................. 419 tMaxDBRow ............................................................ 420 tMaxDBRow properties ...................................... 420 Related scenario .................................................. 421 tMSSqlBulkExec ..................................................... 422 tMSSqlBulkExec properties ................................ 422 Related scenarios ................................................. 424 425 tMSSqlColumnList ................................................. 426 tMSSqlColumnList Properties ............................ 426 Related scenario .................................................. 426 tMSSqlClose ............................................................ 427 tMSSqlClose properties ....................................... 427 Related scenario .................................................. 427 tMSSqlCommit ........................................................ 428 tMSSqlCommit properties ................................... 428 x

Related scenarios .................................................428 tMSSqlConnection ...................................................429 tMSSqlConnection properties ..............................429 Related scenarios .................................................430 tMSSqlInput .............................................................431 tMSSqlInput properties ........................................431 Related scenarios .................................................432 tMSSqlLastInsertId .................................................433 tMSSqlLastInsertId properties .............................433 Related scenario ...................................................433 MSSqlOutput ...........................................................434 tMSSqlOutput properties .....................................434 Related scenarios .................................................437 tMSSqlOutputBulk ..................................................438 tMSSqlOutputBulk properties .............................438 Related scenarios .................................................439 tMSSqlOutputBulkExec .........................................440 tMSSqlOutputBulkExec properties .....................440 Related scenarios .................................................442 tMSSqlRollback .......................................................443 tMSSqlRollback properties ..................................443 Related scenario ...................................................443 tMSSqlRow ...............................................................444 tMSSqlRow properties .........................................444 Related scenarios .................................................446 tMSSqlSCD ..............................................................447 tMSSqlSP ..................................................................448 tMSSqlSP Properties ............................................448 Related scenario ...................................................449 tMSSqlTableList ......................................................450 tMSSqlTableList Properties .................................450 Related scenario ...................................................450 tMysqlBulkExec .......................................................451 tMysqlBulkExec properties .................................451 Related scenarios .................................................453 tMysqlClose ..............................................................454 tMysqlClose properties ........................................454 Related scenario ...................................................454 tMysqlColumnList ...................................................455 tMysqlColumnList Properties ..............................455 Scenario: Iterating on a DB table and listing its column names .................................................................455 tMysqlCommit .........................................................459 tMysqlCommit Properties ....................................459 Related scenario ...................................................459 tMysqlConnection ....................................................460 tMysqlConnection Properties ...............................460 Scenario: Inserting data in mother/daughter tables .... 460 tMysqlInput ..............................................................465 tMysqlInput properties .........................................465 Related scenarios .................................................466 tMysqlLastInsertId ..................................................467 Creative Commons License

Talend Open Studio Components

tMysqlLastInsertId properties ............................. 467 Scenario: Get the ID for the last inserted record . 467 tMysqlOutput .......................................................... 472 tMysqlOutput properties ...................................... 472 Scenario 1: Adding a new column and altering data in a DB table .................................................................. 476 Scenario 2: Updating data in a database table ..... 480 Scenario 3: Retrieve data in error with a Reject link 483 tMysqlOutputBulk .................................................. 489 tMysqlOutputBulk properties .............................. 489 Scenario: Inserting transformed data in MySQL database ............................................................................ 490 tMysqlOutputBulkExec .......................................... 494 tMysqlOutputBulkExec properties ...................... 494 Scenario: Inserting data in MySQL database ...... 495 tMysqlRollback ....................................................... 498 tMysqlRollback properties .................................. 498 Scenario: Rollback from inserting data in mother/daughter tables ...................................................... 498 tMysqlRow ............................................................... 500 tMysqlRow properties ......................................... 500 Scenario 1: Removing and regenerating a MySQL table index .................................................................... 502 Scénario 2: Using PreparedStatement objects to query data ............................................................................ 503 tMysqlSCD ............................................................... 509 tMysqlSCDELT ....................................................... 510 tMysqlSP .................................................................. 511 tMysqlSP Properties ............................................ 511 Scenario: Finding a State Label using a stored procedure ............................................................................ 512 tMysqlTableList ...................................................... 515 tMysqlTableList Properties ................................. 515 Scenario: Iterating on DB tables and deleting their content using a user-defined SQL template .............. 515 Related scenario .................................................. 519 tNetezzaBulkExec .................................................... 520 tNetezzaBulkExec properties .............................. 520 Related scenarios ................................................. 521 tNetezzaClose ........................................................... 522 tNetezzaClose properties ..................................... 522 Related scenario .................................................. 522 tNetezzaCommit ...................................................... 523 tNetezzaCommit Properties ................................. 523 Related scenario .................................................. 523 tNetezzaConnection ................................................ 524 tNetezzaConnection Properties ........................... 524 Related scenarios ................................................. 524 tNetezzaInput .......................................................... 525 tNetezzaInput properties ...................................... 525 Related scenarios ................................................. 526 tNetezzaOutput ........................................................ 527 Creative Commons License

tNetezzaOutput properties ...................................527 Related scenarios .................................................530 tNetezzaRollback .....................................................531 tNetezzaRollback properties ................................531 Related scenarios .................................................531 tNetezzaRow .............................................................532 tNetezzaRow properties .......................................532 Related scenarios .................................................534 tOracleBulkExec ......................................................535 tOracleBulkExec properties .................................535 Scenario: Truncating and inserting file data into Oracle DB ........................................................................538 tOracleClose .............................................................541 tOracleClose properties ........................................541 Related scenario ...................................................541 tOracleCommit ........................................................542 tOracleCommit Properties ...................................542 Related scenario ...................................................542 tOracleConnection ...................................................543 tOracleConnection Properties ..............................543 Related scenario ...................................................544 tOracleInput .............................................................545 tOracleInput properties ........................................545 Related scenarios .................................................546 tOracleOutput ..........................................................547 tOracleOutput properties ......................................547 Related scenarios .................................................550 tOracleOutputBulk ..................................................551 tOracleOutputBulk properties ..............................551 Related scenarios .................................................552 tOracleOutputBulkExec .........................................553 tOracleOutputBulkExec properties ......................553 Related scenarios .................................................555 tOracleRollback .......................................................556 tOracleRollback properties ..................................556 Related scenario ...................................................556 tOracleRow ...............................................................557 tOracleRow properties .........................................557 Related scenarios .................................................559 tOracleSCD ..............................................................560 tOracleSCDELT ......................................................561 tOracleSP ..................................................................562 tOracleSP Properties ............................................562 Scenario: Checking number format using a stored procedure ...................................................................564 tOracleTableList ......................................................569 tOracleTableList properties .................................569 Related scenarios .................................................569 tParAccelBulkExec ..................................................570 tParAccelBulkExec Properties .............................570 Related scenarios .................................................572 tParAccelClose .........................................................573 tParAccelClose properties ....................................573 xi

Talend Open Studio Components

Related scenario .................................................. 573 tParAccelCommit .................................................... 574 tParAccelCommit Properties ............................... 574 Related scenario .................................................. 574 tParAccelConnection .............................................. 575 tParAccelConnection Properties .......................... 575 Related scenario .................................................. 576 tParAccelInput ........................................................ 577 tParAccelInput properties .................................... 577 Related scenarios ................................................. 578 tParAccelOutput ..................................................... 579 tParAccelOutput Properties ................................. 579 Related scenarios ................................................. 581 tParAccelOutputBulk ............................................. 582 tParAccelOutputBulk properties ......................... 582 Related scenarios ................................................. 583 tParAccelOutputBulkExec ..................................... 584 tParAccelOutputBulkExec Properties ................. 584 Related scenarios ................................................. 585 tParAccelRollback .................................................. 586 tParAccelRollback properties .............................. 586 Related scenario .................................................. 586 tParAccelRow .......................................................... 587 tParAccelRow Properties .................................... 587 Related scenarios ................................................. 589 tParAccelSCD .......................................................... 590 tParseRecordSet ...................................................... 591 tParseRecordSet properties .................................. 591 Related Scenario .................................................. 591 tPostgresPlusBulkExec ........................................... 592 tPostgresPlusBulkExec properties ....................... 592 Related scenarios ................................................. 593 tPostgresPlusClose .................................................. 594 tPostgresPlusClose properties ............................. 594 Related scenario .................................................. 594 tPostgresPlusCommit .............................................. 595 tPostgresPlusCommit Properties ......................... 595 Related scenario .................................................. 595 tPostgresPlusConnection ........................................ 596 tPostgresPlusConnection Properties .................... 596 Related scenario .................................................. 597 tPostgresPlusInput .................................................. 598 tPostgresPlusInput properties .............................. 598 Related scenarios ................................................. 599 tPostgresPlusOutput ............................................... 600 tPostgresPlusOutput properties ........................... 600 Related scenarios ................................................. 603 tPostgresPlusOutputBulk ....................................... 604 tPostgresPlusOutputBulk properties .................... 604 Related scenarios ................................................. 605 tPostgresPlusOutputBulkExec ............................... 606 tPostgresPlusOutputBulkExec properties ............ 606 Related scenarios ................................................. 607 xii

tPostgresPlusRollback .............................................608 tPostgresPlusRollback properties .........................608 Related scenarios .................................................608 tPostgresPlusRow ....................................................609 tPostgresPlusRow properties ...............................609 Related scenarios .................................................611 tPostgresPlusSCD ....................................................612 tPostgresPlusSCDELT ............................................613 tPostgresqlBulkExec ................................................614 tPostgresqlBulkExec properties ...........................614 Related scenarios .................................................615 tPostgresqlCommit ..................................................616 tPostgresqlCommit Properties .............................616 Related scenario ...................................................616 tPostgresqlClose .......................................................617 tPostgresqlClose properties ..................................617 Related scenario ...................................................617 tPostgresqlConnection .............................................618 tPostgresqlConnection Properties ........................618 Related scenario ...................................................618 tPostgresqlInput .......................................................620 tPostgresqlInput properties ..................................620 Related scenarios .................................................621 tPostgresqlOutput ....................................................622 tPostgresqlOutput properties ................................622 Related scenarios .................................................624 tPostgresqlOutputBulk ...........................................625 tPostgresqlOutputBulk properties ........................625 Related scenarios .................................................626 tPostgresqlOutputBulkExec ...................................627 tPostgresqlOutputBulkExec properties ................627 Related scenarios .................................................627 tPostgresqlRollback .................................................628 tPostgresqlRollback properties ............................628 Related scenario ...................................................628 tPostgresqlRow ........................................................629 tPostgresqlRow properties ...................................629 Related scenarios .................................................631 tPostgresqlSCD ........................................................632 tPostgresqlSCDELT ................................................633 tSASInput .................................................................634 tSASInput properties ............................................634 Related scenarios .................................................635 tSASOutput ..............................................................636 tSASOutput properties .........................................636 Related scenarios .................................................638 tSQLiteClose ............................................................639 tSQLiteClose properties .......................................639 Related scenario ...................................................639 tSQLiteCommit ........................................................640 tSQLiteCommit Properties ...................................640 Related scenario ...................................................640 tSQLiteConnection ..................................................641 Creative Commons License

Talend Open Studio Components

SQLiteConnection properties .............................. 641 Related scenarios ................................................ 641 tSQLiteInput ............................................................ 642 tSQLiteInput Properties ....................................... 642 Scenario: Filtering SQlite data ............................ 643 tSQLiteOutput ......................................................... 646 tSQLiteOutput Properties .................................... 646 Related Scenario .................................................. 648 tSQLiteRollback ...................................................... 649 tSQLiteRollback properties ................................. 649 Related scenarios ................................................. 649 tSQLiteRow ............................................................. 650 tSQLiteRow Properties ........................................ 650 Scenario: Updating SQLite rows ......................... 651 tSybaseBulkExec ..................................................... 654 tSybaseBulkExec Properties ................................ 654 Related scenarios ................................................. 656 tSybaseClose ............................................................ 657 tSybaseClose properties ...................................... 657 Related scenario .................................................. 657 tSybaseCommit ........................................................ 658 tSybaseCommit Properties .................................. 658 Related scenario .................................................. 658 tSybaseConnection .................................................. 659 tSybaseConnection Properties ............................. 659 Related scenarios ................................................. 659 tSybaseInput ............................................................ 660 tSybaseInput Properties ....................................... 660 Related scenarios ................................................. 661 tSybaseIQBulkExec ................................................ 662 tSybaseIQBulkExec Properties ........................... 662 Related scenarios ................................................. 663 tSybaseIQOutputBulkExec .................................... 664 tSybaseIQOutputBulkExec properties ................ 664 Related scenarios ................................................. 665 tSybaseOutput ......................................................... 667 tSybaseOutput Properties .................................... 667 Related scenarios ................................................. 669 tSybaseOutputBulk ................................................. 671 tSybaseOutputBulk properties ............................. 671 Related scenarios ................................................. 672 tSybaseOutputBulkExec ......................................... 673 tSybaseOutputBulkExec properties ..................... 673 Related scenarios ................................................. 675 tSybaseRollback ...................................................... 676 tSybaseRollback properties ................................. 676 Related scenarios ................................................. 676 tSybaseRow .............................................................. 677 tSybaseRow Properties ........................................ 677 Related scenarios ................................................. 679 tSybaseSCD .............................................................. 680 tSybaseSCDELT ...................................................... 681 tSybaseSP ................................................................. 682 Creative Commons License

tSybaseSP properties ............................................682 Related scenarios .................................................683 tTeradataClose .........................................................684 tTeradataClose properties ....................................684 Related scenario ...................................................684 tTeradataCommit ....................................................685 tTeradataCommit Properties ...............................685 Related scenario ..................................................685 tTeradataConnection ...............................................686 tTeradataConnection Properties ..........................686 Related scenario ..................................................687 tTeradataFastExport ...............................................688 tTeradataFastExport Properties ............................688 Related scenario ...................................................689 tTeradataFastLoad ..................................................690 tTeradataFastLoad Properties ..............................690 Related scenario ...................................................691 tTeradataFastLoadUtility .......................................692 tTeradataFastLoadUtility Properties ....................692 Related scenario ...................................................693 tTeradataInput .........................................................694 tTeradataInput Properties .....................................694 Related scenarios .................................................695 tTeradataMultiLoad ................................................696 tTeradataMultiLoad Properties ............................696 Related scenario ...................................................697 tTeradataOutput ......................................................698 tTeradataOutput Properties ..................................698 Related scenarios .................................................701 tTeradataRollback ...................................................702 tTeradataRollback Properties ..............................702 Related scenario ..................................................702 tTeradataRow ..........................................................703 tTeradataRow Properties ......................................703 Related scenarios .................................................705 tTeradataTPump .....................................................706 tTeradataTPump Properties .................................706 Related scenario ...................................................707 tVerticaBulkExec .....................................................708 tVerticaBulkExec Properties ................................708 Related scenarios ................................................709 tVerticaClose ............................................................711 tVerticaClose properties .......................................711 Related scenario ...................................................711 tVerticaCommit .......................................................712 tVerticaCommit Properties .................................712 Related scenario ..................................................712 tVerticaConnection ..................................................713 tVerticaConnection Properties ............................713 Related scenario ..................................................714 tVerticaInput ............................................................715 tVerticaInput Properties ......................................715 Related scenarios ................................................716 xiii

Talend Open Studio Components

tVerticaOutput ........................................................ 717 tVerticaOutput Properties ................................... 717 Related scenarios ................................................. 719 tVerticaOutputBulk ................................................ 721 tVerticaOutputBulk Properties ........................... 721 Related scenarios ................................................ 722 tVerticaOutputBulkExec ........................................ 723 tVerticaOutputBulkExec Properties ................... 723 Related scenarios ................................................ 724 tVerticaRollback ..................................................... 725 tVerticaRollback Properties ............................... 725 Related scenario ................................................. 725 tVerticaRow ............................................................. 726 tVerticaRow Properties ...................................... 726 Related scenario ................................................. 728

ELT components ..................................... 729
tELTAggregate ........................................................ 730 tELTAggregate properties ................................... 730 Scenario: Filtering and aggregating table columns directly on the DBMS .................................................. 731 tELTCommit ........................................................... 737 tELTCommit properties ...................................... 737 Related scenario .................................................. 738 tELTFilterColumns ................................................ 739 tELTFilterColumns Properties ............................ 739 Related Scenario .................................................. 740 tELTFilterRows ...................................................... 741 tELTFilterRows Properties .................................. 741 Related Scenario .................................................. 742 tELTJDBCInput ..................................................... 743 tELTJDBCInput properties ................................. 743 Related scenarios ................................................. 743 tELTJDBCMap ....................................................... 744 tELTJDBCMap properties .................................. 744 Related scenario: ................................................. 745 tELTJDBCOutput .................................................. 746 tELTJDBCOutput properties ............................... 746 Related scenarios ................................................. 747 tELTMSSqlInput .................................................... 748 tELTMSSqlInput properties ................................ 748 Related scenarios ................................................. 748 tELTMSSqlMap ...................................................... 749 tELTMSSqlMap properties ................................. 749 Related scenario: ................................................. 750 tELTMSSqlOutput ................................................. 751 tELTMSSqlOutput properties ............................. 751 Related scenarios ................................................. 752 tELTMysqlInput ..................................................... 753 tELTMysqlInput properties ................................. 753 Related scenarios ................................................. 753 tELTMysqlMap ....................................................... 754 xiv

tELTMysqlMap properties ...................................754 Connecting ELT components ...........................754 Mapping and joining tables ..............................755 Adding where clauses .......................................755 Generating the SQL statement ..........................755 Scenario1: Aggregating table columns and filtering . 756 Scenario 2: ELT using Alias table .......................759 tELTMysqlOutput ...................................................763 tELTMysqlOutput properties ...............................763 Related scenarios .................................................764 tELTOracleInput .....................................................765 tELTOracleInput properties .................................765 Related scenarios .................................................765 tELTOracleMap ......................................................766 tELTOracleMap properties ..................................766 Connecting ELT components ...........................767 Mapping and joining tables ..............................767 Adding where clauses .......................................768 Generating the SQL statement ..........................768 Scenario: Updating Oracle DB entries .................768 tELTOracleOutput ..................................................771 tELTOracleOutput properties ..............................771 Scenario: Using the Oracle MERGE function to update and add data simultaneously ..............................773 tELTPostgresqlInput ...............................................779 tELTPostgresqlInput properties ...........................779 Related scenarios .................................................779 tELTPostgresqlMap ................................................780 tELTPostgresqlMap properties ............................780 Related scenario: ..................................................781 tELTPostgresqlOutput ............................................782 tELTPostgresqlOutput properties ........................782 Related scenarios .................................................783 tELTRollback ...........................................................784 tELTRollback properties .....................................784 Related scenarios .................................................785 tELTSybaseInput .....................................................786 tELTSybaseInput properties ................................786 Related scenarios .................................................786 tELTSybaseMap ......................................................787 tELTSybaseMap properties .................................787 Related scenarios .................................................788 tELTSybaseOutput ..................................................789 tELTSybaseOutput properties ..............................789 Related scenarios .................................................790 tELTTeradataInput .................................................791 tELTTeradataInput properties ..............................791 Related scenarios .................................................791 tELTTeradataMap ..................................................792 tELTTeradataMap properties ...............................792 Connecting ELT components ...........................792 Mapping and joining tables ..............................793 Creative Commons License

Talend Open Studio Components

Adding WHERE clauses .................................. 793 Generating the SQL statement ......................... 793 Related scenarios ................................................. 793 tELTTeradataOutput ............................................. 794 tELTTeradataOutput properties .......................... 794 Related scenarios ................................................. 795

File components ....................................... 797
tAdvancedFileOutputXML .................................... 798 tApacheLogInput .................................................... 799 tApacheLogInput properties ................................ 799 Scenario: Reading an Apache access-log file ...... 800 tCreateTemporaryFile ........................................... 802 tCreateTemporaryFile properties ........................ 802 Scenario: Creating a temporary file and writing data in it ............................................................................ 802 tFileArchive ............................................................. 807 tFileArchive properties ........................................ 807 Scenario: Zip files using a tFileArchive .............. 807 tFileCompare ........................................................... 809 tFileCompare properties ...................................... 809 Scenario: Comparing unzipped files ................... 809 tFileCopy .................................................................. 812 tFileCopy Properties ............................................ 812 Scenario: Restoring files from bin ....................... 812 tFileDelete ................................................................ 814 tFileDelete Properties .......................................... 814 Scenario: Deleting files ....................................... 814 tFileExist .................................................................. 816 tFileExist Properties ............................................ 816 Scenario: Checking for the presence of a file and creating it if it does not exist .......................................... 816 tFileInputARFF ....................................................... 820 tFileInputARFF properties .................................. 820 Scenario : Display the content of a ARFF file .... 821 tFileInputDelimited ............................................... 824 tFileInputDelimited properties ............................ 824 Scenario: Delimited file content display ............. 825 Scénario 2 : Reading data from a remote file in streaming mode ......................................................... 827 tFileInputEBCDIC .................................................. 830 tFileInputEBCDIC properties .............................. 830 Scenario: Extracting data from an EBCDIC file and populating a database ................................................ 830 tFileInputExcel ....................................................... 836 tFileInputExcel properties .................................. 836 Related scenarios ................................................. 838 tFileInputFullRow .................................................. 839 tFileInputFull Row properties ............................. 839 Scenario: Reading full rows in a delimited file ... 839 tFileInputJSON ...................................................... 842 tFileInputJSON properties .................................. 842 Creative Commons License

Scenario: Extracting data from the fields of a JSON format file ..................................................................843 tFileInputLDIF .......................................................846 tFileInputLDIF Properties ....................................846 Related scenario ...................................................847 tFileInputMail ..........................................................848 tFileInputMail properties .....................................848 Scenario: Extracting key fields from an email .....849 tFileInputMSDelimited ..........................................851 tFileInputMSDelimited properties .......................851 The Multi Schema Editor .................................851 Scenario: Reading a multi structure delimited file .... 852 tFileInputMSPositional ..........................................858 tFileInputMSPositional properties .......................858 Related scenario ...................................................859 tFileInputMSXML ...................................................860 tFileInputMSXML Properties ..............................860 Scenario: Reading a multi structure XML file .....861 tFileInputPositional ................................................864 tFileInputPositional properties .............................864 Scenario: From Positional to XML file ...............865 tFileInputProperties ................................................869 tFileInputProperties properties .............................869 Scenario: Reading and matching the keys and the values of different .properties files and outputting the results in a glossary ...............................................................869 tFileInputRegex .......................................................873 tFileInputRegex properties ...................................873 Scenario: Regex to Positional file ........................874 tFileInputXML .........................................................877 tFileList ....................................................................878 tFileList properties ...............................................878 Scenario: Iterating on a file directory ..................878 tFileOutputARFF ....................................................882 tFileOutputARFF properties ................................882 Related scenarios .................................................883 tFileOutputDelimited ..............................................884 tFileOutputDelimited properties ..........................884 Scenario: Writing data in a delimited file ............885 tFileOutputEBCDIC ...............................................890 tFileOutputEBCDIC properties ...........................890 Scenario: Creating an EBCDIC file using two delimited files .....................................................................890 tFileOutputExcel ......................................................893 tFileOutputExcel Properties .................................893 Related scenario ...................................................894 tFileOutputLDIF .....................................................895 tFileOutputLDIF Properties .................................895 Scenario: Writing DB data into an LDIF-type file .... 896 tFileOutputMSDelimited .......................................898 tFileOutputMSDelimited properties ...................898 xv

Talend Open Studio Components

Related scenarios ................................................. 899 tFileOutputMSPositional ....................................... 900 tFileOutputMSPositional properties .................... 900 Related scenario .................................................. 900 tFileOutputMSXML ............................................... 901 tFileOutputMSXML Properties ........................... 901 Defining the MultiSchema XML tree .............. 901 Importing the XML tree .............................. 902 Creating manually the XML tree ................. 904 Mapping XML data from multiple schema sources 904 Defining the node status ................................... 905 Loop element ............................................... 905 Group element ............................................. 905 Related scenario .................................................. 906 tFileOutputPositional .............................................. 907 tFileOutputPositional Properties ......................... 907 Related scenario ................................................. 908 tFileOutputProperties ............................................. 909 tFileOutputProperties properties ......................... 909 Related scenarios ................................................. 909 tFileOutputXML ..................................................... 910 tFileProperties ......................................................... 911 tFileProperties Properties .................................... 911 Scenario: Displaying the properties of a processed file 911 tFileRowCount ........................................................ 913 tFileRowCount properties ................................... 913 Related scenario .................................................. 913 tFileTouch ................................................................ 914 tFileTouch properties .......................................... 914 Related scenario ................................................. 914 tFileUnarchive ......................................................... 915 tFileUnarchive Properties .................................... 915 Related scenario .................................................. 915 tPivotToColumnsDelimited .................................... 916 tPivotToColumnsDelimited Properties ............... 916 Scenario: Using a pivot column to aggregate data .... 916

Internet components ............................... 919
tFileFetch ................................................................. 920 tFileFetch properties ............................................ 920 Related scenario 1: Fetching data through HTTP 921 Related scenario 2: Reading the data from a remote file in streaming mode ............................................... 922 tFileInputJSON ....................................................... 923 tFTPConnection ...................................................... 924 tFTPConnection properties .................................. 924 Related scenarios ................................................. 924 tFTPDelete ............................................................... 925 tFTPDelete properties .......................................... 925 xvi

Related scenario ...................................................925 tFTPFileExist ..........................................................926 tFTPFileExist properties .....................................926 Related scenario ...................................................927 tFTPFileList ............................................................928 tFTPFileList properties .......................................928 Scenario: Iterating on a remote directory ............929 tFTPFileProperties ..................................................933 tFTPFileProperties Properties ..............................933 Related scenario ...................................................934 tFTPGet ....................................................................935 tFTPGet properties ...............................................935 Related scenario ...................................................935 tFTPPut ....................................................................936 tFTPPut properties ...............................................936 Scenario: Putting files on a remote FTP server ...937 tFTPRename ............................................................939 tFTPRename Properties .......................................939 Related scenario ...................................................940 tFTPTruncate ..........................................................941 tFTPTruncate properties .....................................941 Related scenario ...................................................942 tJMSInput ................................................................943 tJMSInput properties ............................................943 Related scenario ..................................................944 tJMSOutput .............................................................945 tJMSOutput properties .........................................945 Related scenario ..................................................945 tMomInput ...............................................................946 tMomInput Properties ..........................................946 Scenario: asynchronous communication via a MOM server .........................................................................947 tMomMessageIdList ................................................950 tMomMessageIdList Properties ...........................950 Related scenario ...................................................950 tMomOutput ............................................................951 tMomOutput Properties .......................................951 Related scenario ...................................................951 tPOP ..........................................................................952 tPOP properties ....................................................952 Scenario: Retrieving a selection of email messages from an email server .................................................953 tRSSInput .................................................................956 tRSSInput Properties ............................................956 Scenario: Fetching frequently updated blog entries. .. 956 tRSSOutput ..............................................................959 tRSSOutput Properties .........................................959 Scenario 1: Creating an RSS flow and storing files on an FTP server .............................................................960 Scenario 2: Creating an RSS flow that contains metadata .............................................................................963 tSCPConnection .......................................................966 Creative Commons License

Talend Open Studio Components

tSCPConnection properties ................................. 966 Related scenarios ................................................. 966 tSCPDelete ............................................................... 967 tSCPDelete properties ......................................... 967 Related scenario .................................................. 967 tSCPFileExists ......................................................... 968 tSCPFileExists properties .................................... 968 Related scenario .................................................. 968 tSCPFileList ............................................................. 969 tSCPFileList properties ....................................... 969 Related scenario .................................................. 969 tSCPGet .................................................................... 970 tSCPGet properties .............................................. 970 Scenario: Getting files from a remote SCP server .... 970 tSCPPut .................................................................... 972 tSCPPut properties .............................................. 972 Related scenario .................................................. 972 tSCPRename ............................................................ 973 tSCPRename properties ....................................... 973 Related scenario .................................................. 973 tSCPTruncate .......................................................... 974 tSCPRename properties ....................................... 974 Related scenario .................................................. 974 tSendMail ................................................................. 975 tSendMail Properties ........................................... 975 Scenario: Email on error ...................................... 976 tSocketInput ............................................................ 978 tSocketInput properties ........................................ 978 Scenario: Passing on data to the listening port (Java) 980 tSocketOutput .......................................................... 983 tSocketOutput properties ..................................... 983 Related Scenario .................................................. 984 tWebServiceInput ................................................... 985 tWebServiceInput Properties ............................... 985 Scenario 1: Extracting images through a Web service 987 Scenario 2: Reading the data published on a Web service using the tWebServiceInput advanced features (Java only) .......................................................................... 988 tXMLRPCInput ...................................................... 993 tXMLRPCInput Properties .................................. 993 Scenario: Guessing the State name from an XMLRPC 993

tAssertCatcher Properties ...................................1004 Related scenarios ...............................................1005 tChronometerStart ................................................1006 tChronometerStart Properties .............................1006 Related scenario .................................................1006 tChronometerStop .................................................1007 tChronometerStop Properties .............................1007 Scenario: Measuring the processing time of a subjob and part of a subjob .................................................1007 tDie ..........................................................................1012 tDie properties ....................................................1012 Related scenarios ...............................................1012 tFlowMeter .............................................................1013 tFlowMeter Properties .......................................1013 Related scenario .................................................1013 tFlowMeterCatcher ...............................................1014 tFlowMeterCatcher Properties ...........................1014 Scenario: Catching flow metrics from a Job ......1015 tLogCatcher ...........................................................1019 tLogCatcher properties ......................................1019 Scenario1: warning & log on entries .................1019 Scenario 2: Log & kill a Job ..............................1021 tLogRow ................................................................1023 tLogRow properties ...........................................1023 Scenario: Delimited file content display ............1023 tStatCatcher ...........................................................1024 tStatCatcher Properties .......................................1024 Scenario: Displaying job stats log ......................1024 tWarn ......................................................................1027 tWarn Properties ................................................1027 Related scenarios ...............................................1027

Misc group components ........................1029
tAddLocationFromIP ...........................................1030 tAddLocationFromIP Properties ........................1030 Scenario: Identifying a real-world geographic location of an IP .............................................................1031 tBufferInput ...........................................................1033 tBufferInput properties .......................................1033 Scenario: Retrieving bufferized data (Java) .......1033 tBufferOutput ........................................................1036 tBufferOutput properties ....................................1036 Scenario1: Buffering data (Java) .......................1036 Scenario 2: Buffering output data on the webapp server .............................................................................1039 Scenario 3: Calling a Job with context variables from a browser .................................................................1042 Scenario 4: Calling a Job exported as Webservice in another Job ...............................................................1044 tContextDump ........................................................1047 tContextDump properties ...................................1047 Related Scenario ..............................................1047 xvii

Logs & Errors components .................... 997
tAssert ...................................................................... 998 tAssert Properties ................................................ 998 Scenario: Setting up the assertive condition for a Job execution ................................................................... 998 tAssertCatcher ....................................................... 1004 Creative Commons License

Talend Open Studio Components

tContextLoad ......................................................... 1048 tContextLoad properties .................................... 1048 Scenario: Dynamic context use in MySQL DB insert 1049 tFixedFlowInput .................................................... 1052 tFixedFlowInput properties ............................... 1052 Related scenarios ............................................... 1052 tMsgBox ................................................................ 1054 tMsgBox properties ........................................... 1054 Scenario: ‘Hello world!’ type test ..................... 1054 tRowGenerator ..................................................... 1056 tRowGenerator properties ................................. 1056 Defining the schema ....................................... 1056 Defining the function ..................................... 1057 Scenario: Generating random java data ............. 1058

Related scenario ................................................1087 tWaitForSqlData ...................................................1088 tWaitForSqlData properties ...............................1088 Scenario: Waiting for insertion of rows in a table .... 1089

Processing components .........................1093
tAggregateRow ......................................................1094 tAggregateRow properties .................................1094 Scenario: Aggregating values and sorting data ..1095 tAggregateSortedRow ...........................................1099 tAggregateSortedRow properties .......................1099 Related scenario .................................................1100 tConvertType .........................................................1101 tConvertType properties ....................................1101 Scenario: Converting java types ........................1101 tDenormalize ..........................................................1106 tDenormalize Properties .....................................1106 Scenario 1: Denormalizing on one column in Perl .... 1106 Scenario 2: Denormalizing on multiple columns ....... 1108 tDenormalizeSortedRow .......................................1111 tDenormalizeSortedRow properties ...................1111 Scenario: Regrouping sorted rows .....................1111 tEmptyToNull ........................................................1115 tEmptyToNull properties ...................................1115 Scenario: Replacing empty fields by NULL fields (fields of unknown value) .......................................1115 tExternalSortRow ..................................................1119 tExternalSortRow properties ..............................1119 Related scenario .................................................1120 tExtractDelimitedFields ........................................1121 tExtractDelimitedFields properties ....................1121 Scenario: Extracting fields from a comma-delimited file ............................................................................1122 tExtractPositionalFields ........................................1126 tExtractPositionalFields properties ....................1126 Related scenario .................................................1127 tExtractRegexFields ..............................................1128 tExtractRegexFields properties ..........................1128 Scenario: Extracting name, domain and TLD from e-mail addresses .......................................................1129 tExtractXMLFields ..............................................1132 tFilterColumns .......................................................1133 tFilterColumns Properties ..................................1133 Related Scenario ................................................1133 tFilterRow ...............................................................1134 tFilterRow Properties .........................................1134 Scenario: Filtering and searching a list of names ...... 1135 tMap .......................................................................1137 Creative Commons License

Orchestration components ................... 1061
tFileList ................................................................. 1062 tFlowToIterate ....................................................... 1063 tFlowToIterate Properties .................................. 1063 Scenario: Transforming data flow to a list ........ 1063 tInfiniteLoop .......................................................... 1067 tInfiniteLoop Properties ................................... 1067 Related scenario ................................................ 1067 tIterateToFlow ....................................................... 1068 tIterateToFlow Properties .................................. 1068 Scenario: Transforming a list of files as data flow .... 1068 tLoop ...................................................................... 1071 tLoop Properties ................................................ 1071 Scenario: Job execution in a loop ...................... 1071 tPostjob .................................................................. 1074 tPostjob Properties ............................................. 1074 Related scenario ................................................ 1074 tPrejob .................................................................... 1075 tPrejob Properties .............................................. 1075 Related scenario ................................................ 1075 tReplicate ............................................................... 1076 tReplicate Properties .......................................... 1076 Related scenario ................................................ 1076 tRunJob ................................................................. 1077 tSleep ...................................................................... 1078 tSleep Properties ................................................ 1078 Related scenarios ............................................... 1078 tUnite ...................................................................... 1079 tUnite Properties ................................................ 1079 Scenario: Iterate on files and merge the content 1079 tWaitForFile .......................................................... 1083 tWaitForFile properties ..................................... 1083 Scenario: Waiting for a file to be removed ...... 1084 tWaitForSocket ..................................................... 1087 tWaitForSocket properties ................................. 1087 xviii

Talend Open Studio Components

tMap properties .................................................. 1137 Scenario 1: Mapping with filter and simple explicit join ......................................................................... 1137 Scenario 2: Mapping with Inner join rejection .. 1142 Scenario 3: Cascading join mapping ................. 1146 Scenario 4: Advanced mapping with filters, explicit joins and Inner join rejection .................................. 1147 Scenario 5: Advanced mapping with filters and a check of all rows ................................................... 1151 Scenario 6: Advanced mapping with lookup reload at each row (java) ........................................................ 1154 Scenario 7: Mapping with join output tables ..... 1160 tNormalize .............................................................. 1163 tNormalize Properties ........................................ 1163 Scenario: Normalizing data (in Perl) ................. 1163 tPivotToRows ........................................................ 1166 tPivotToRows properties ................................... 1166 Scenario: Concatenating a list of columns in a table by using the other table columns as pivot .............. 1167 tReplace .................................................................. 1170 tReplace Properties ............................................ 1170 Scenario: multiple replacements and column filtering 1171 tSampleRow ........................................................... 1175 tSampleRow properties ..................................... 1175 Scenario: Filtering rows and groups of rows ..... 1175 tSortRow ................................................................ 1178 tSortRow properties ........................................... 1178 Scenario: Sorting entries ................................... 1179

1199 tMDMInput ............................................................1203 tMDMInput properties .......................................1203 Scenario: Reading master data in an MDM hub 1204 tMDMOutput .........................................................1208 tMDMOutput properties ....................................1208 Scenario: Writing master data in an MDM hub .1210 tMDMReceive ........................................................1216 tMDMReceive properties ...................................1216 Related scenario .................................................1217

XML components ..................................1219
tAdvancedFileOutputXML ...................................1220 tAdvancedFileOutputXML properties ...............1220 Defining the XML tree ...................................1221 Importing the XML tree .............................1222 Creating the XML tree manually ...............1223 Mapping XML data ........................................1223 Defining the node status .................................1224 Loop element .............................................1224 Group element ............................................1225 Scenario: Creating an XML file using a loop ....1226 tDTDValidator .......................................................1231 tDTDValidator Properties ..................................1231 Scenario: Validating xml files ...........................1231 tExtractXMLField .................................................1234 tExtractXMLField properties .............................1234 Scenario 1: Extracting XML data from a field in a database table ..............................................................1235 Scenario 2: Extracting correct and erroneous data from an XML field in a delimited file .....................1237 tFileInputXML .......................................................1241 tFileInputXML Properties ..................................1241 Scenario 1: Reading and extracting data from an XML structure .........................................................1243 Scenario 2: Extracting erroneous XML data via a reject flow ...................................................................1244 tFileOutputXML ....................................................1248 tFileOutputXML properties ...............................1248 Scenario: From Positional to XML file .............1249 tWriteXMLField ....................................................1250 tWriteXMLField properties ...............................1250 Scenario: Extracting the structure of an XML file and inserting it into the fields of a database table ..........1251 tXSDValidator .......................................................1256 tDTDValidator Properties ..................................1256 Related scenario .................................................1256 tXSLT .....................................................................1257 tXSLT Properties ...............................................1257 Scenario: Transforming XML to html using an XSL stylesheet .................................................................1257

System components ............................... 1181
tRunJob .................................................................. 1182 tRunJob Properties ............................................ 1182 Scenario: Executing a child Job ........................ 1183 tSetEnv ................................................................... 1188 tSetEnv Properties ............................................. 1188 Scenario: Modifying the Date variable during the execution of a Job ...................................................... 1188 tSSH ........................................................................ 1192 tSSH Properties ................................................. 1192 Scenario: Remote system information display via SSH ........................................................................ 1192 tSystem ................................................................... 1194 tSystem Properties ............................................. 1194 Scenario: Echo ‘Hello World!’ .......................... 1195

Talend MDM components .................... 1197
tMDMDelete .......................................................... 1198 tMDMDelete properties .................................... 1198 Scenario: Deleting master data from an MDM hub ..

Creative Commons License

Talend Open Studio Components

xix

xx

Talend Open Studio Components

Creative Commons License

Preface
Purpose
This Reference Guide explains in detail the major components you can find in each of the different groups in the Palette of Talend Open Studio. Information presented in this document applies to Talend Open Studio releases beginning with 4.0.x.

Audience
This guide is for users and administrators of Talend Open Studio.
The layout of GUI screens provided in this document may vary slightly from your actual GUI.

Typographical conventions
This guide uses the following typographical conventions: • text in bold: window and dialog box buttons and fields, keyboard keys, menus, and menu options, • text in [bold]: window, wizard, and dialog box titles, • text in courier: system parameters typed in by the user, • text in italics: file, schema, column, row, and variable names referred to in all use cases, and also names of the fields in the Basic and Advanced setting views referred to in the property table for each component, • In the properties section for every component, the component is available in Java and/or in Perl. or icon indicates whether the

• The icon indicates an item that provides additional information about an important point. It is also used to add comments related to a table or a figure, • The icon indicates a message that gives information about the execution requirements or recommendation type. It is also used to refer to situations or information the end-user need to be aware of or pay special attention to.

Creative Commons License

Talend Open Studio Components

xxi

History of changes
The below table lists the changes made in the 4.x release of the Talend Open Studio Reference Guide.
Version v3.2_a Date 20/10/2009 History of Change Updates in Talend Open Studio Reference Guide include: -New components in the File, Internet, Processing, Database, Business intelligence and Data quality chapters. -Modifications in the settings and scenarios of many components to match the modifications in the GUI. -Modifications in tSAPInput + new scenario. -Modifications in tRunJob and its scenario. - Reorganized book chapter related to various editions of Talend Open Studio. Updates in Talend Open Studio Reference Guide include: -New components in the File, Database, Business and Data quality chapters. -Modifications in the settings and scenarios of many components to match the modifications in the GUI. -Modifications in tMap + a new scenario. - Deleted the Multischema chapter from the book and place all the multischema components in the File chapter. Updates in Talend Open Studio Reference Guide include: -New components in the File, Database, Business, Internet and MDM chapters. -EXist components have been added to the Databases chapter. -Modifications in the settings and scenarios of many components to match the modifications in the GUI.

v4.0_a

06/04/2010

v4.0_b

27/05/2010

Feedback and Support
Your feedback is valuable. Do not hesitate to give your input, make suggestions or requests regarding this documentation or product and find support from the Talend team, on Talend’s Forum website at: http://talendforge.org/forum

xxii

Talend Open Studio Components

Creative Commons License

Creative Commons License

Talend Open Studio Components

xxiii

xxiv

Talend Open Studio Components

Creative Commons License

Business Intelligence components
This chapter details the main components which belong to the Business Intelligence family in the Talend Open Studio Palette. The BI family groups connectors that cover needs such as reading or writing multidimensional or OLAP databases, outputting Jasper reports, tracking DB changes in slow changing dimension tables and so on.

Property type Either Built-in or Repository. Built-in: No property data stored centrally. in Databases components on page 205. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. so if you need to use an existing connection from the other level. see your studio User Guide. When a Job contains the parent Job and the child Job. The following fields are pre-filled in using fetched data. Note that only one table can be written at a time. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. Name of the DB schema. Component list presents only the connection components in the same Job level. For more information on how to share a DB connection across Job levels. Otherwise. make sure that the available connection components are sharing the intended connection. tDB2SCD addresses Slowly Changing Dimension needs. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Host Port Database Table Schema Username and Password Table Database server IP address. Name of the table to be written. Listening port number of DB server. For more information about Dynamic settings. reading regularly a source of data and logging the changes into a dedicated SCD table Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined.Business Intelligence components tDB2SCD tDB2SCD tDB2SCD properties Component family Databases/DB2 Function Purpose Basic settings tDB2SCD reflects and tracks changes in a dedicated DB2 SCD table. Repository: Select the Repository file where properties are stored. DB user authentication data. 2 Talend Open Studio Components Creative Commons License . Name of the database.

Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component is used as Output component.Business Intelligence components tDB2SCD Schema and Edit Schema A schema is a row description. Repository: The schema already exists and is stored in the Repository. For more information. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Built-in: The schema is created and stored locally for this component only. i. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select this check box to maximize system performance. Creative Commons License Talend Open Studio Components 3 ..e. hence can be reused. The schema is either built-in or remotely stored in the Repository. see SCD management methodologies on page 20. it defines the number of fields to be processed and passed on to the next component. Related scenarios For related topics. It requires an Input component and Row main link as input. Debug mode Select this check box to display each step during processing entries in a database. Related topic: Setting a built-in schema of Talend Open Studio User Guide.

Host Port Database Username and Password Source table Table The IP address of the database server. in Databases components on page 205. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. For more information about Dynamic settings. In this case. and logs the changes into a dedicated DB2 SCD table. Note that only one table can be written at a time Basic settings 4 Talend Open Studio Components Creative Commons License . so if you need to use an existing connection from the other level. Name of the input DB2 SCD table. Property type Either Built-in or Repository. make sure the connection name is unique and distinctive all over through the two Job levels. Name of the database User authentication data for a dedicated database. Name of the table to be written. When a Job contains the parent Job and the child Job. Built-in: No property data stored centrally. Listening port number of database server. Component list presents only the connection components in the same Job level.Business Intelligence components tDB2SCDELT tDB2SCDELT tDB2SCDELT Properties Component family Databases/DB2 Function Purpose tDB2SCDELT reflects and tracks changes in a dedicated DB2 SCD table. Repository: Select the repository file where Properties are stored. Use an existing connection Select this check box and click the relevant tDB2Connection component on the Component List to reuse the connection details you already defined. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. tDB2SCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). For more information on how to share a DB connection across Job levels. Otherwise. see your studio user guide. make sure that the available connection components are sharing the intended connection. Enter properties manually. The fields that come after are pre-filled in using the fetched data.

You have the possibility to rollback the operation. Select the method to be used for the surrogate key generation.. to ensure the unicity of incoming data. Start date: Adds a column to your SCD schema to hold the start date value. SCD Type 1 should be used for typos corrections for example. Creative Commons License Talend Open Studio Components 5 . Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. Built-in: The schema is created and stored locally for this component only.Business Intelligence components tDB2SCDELT Action on table Select to perform one of the following operations on the table defined: None: No action carried out on the table. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. SCD Type 2 should be used to trace updates for example. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. A schema is a row description. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. You don not have the possibility to rollback the operation. Repository: The schema already exists and is stored in the Repository. the End Date column shows a null value. i. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. End Date: Adds a column to your SCD schema to hold the end date value for the record. Related topic: Setting a built-in schema of Talend Open Studio User Guide. When the record is currently active. Create table if not exists: A table gets created if it does not exist. Drop and create table: The table is removed and created again Create table: A new table gets created. hence can be reused. it defines the number of fields to be processed and passed on to the next component.e. Select one or more columns to be used as keys. Select the columns of the schema that will be checked for changes. You can select one of the input schema columns as Start Date in the SCD table. Log versions: Adds a column to your SCD schema to hold the version number of the record. Select the columns of the schema that will be checked for changes. Clear table: The table content is deleted. Truncate table: The table content is deleted. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. This column helps to easily spot the active record.

see tDB2SCD on page 2 Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Select this check box to display each step during processing entries in a database. Enable debug mode tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component is used as an output component.Business Intelligence components tDB2SCDELT Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. It requires an input component and Row main link as input. 6 Talend Open Studio Components Creative Commons License . Related Scenario For related topics. This field is compulsory for DB data handling.

Name of the table to be written. Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. tGreenplumSCD addresses Slowly Changing Dimension needs. so if you need to use an existing connection from the other level. Name of the database. Name of the DB schema. Otherwise. Component list presents only the connection components in the same Job level. Note that only one table can be written at a time. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job. In this case. For more information about Dynamic settings. The following fields are pre-filled in using fetched data. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Repository: Select the Repository file where properties are stored. For more information on how to share a DB connection across Job levels. make sure that the available connection components are sharing the intended connection. reading regularly a source of data and logging the changes into a dedicated SCD table Property type Either Built-in or Repository.Business Intelligence components tGreenplumSCD tGreenplumSCD tGreenplumSCD Properties Component family Databases/Greenplum Function Purpose Basic settings tGreenplumSCD reflects and tracks changes in a dedicated Greenplum SCD table. Creative Commons License Talend Open Studio Components 7 . make sure the connection name is unique and distinctive all over through the two Job levels. DB user authentication data. Database server IP address. see your studio user guide. Listening port number of DB server. in Databases components on page 205. Built-in: No property data stored centrally. Connection type Host Port Database Schema Username and Password Table Select the relevant driver on the list.

Select this check box to maximize system performance. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Usage This component is used as Output component.e. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. The schema is either built-in or remotely stored in the Repository.Business Intelligence components tGreenplumSCD Schema and Edit Schema A schema is a row description. Built-in: The schema is created and stored locally for this component only. see SCD management methodologies on page 20. Related topic: Setting a Repository schema of Talend Open Studio User Guide. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Repository: The schema already exists and is stored in the Repository. It requires an Input component and Row main link as input. 8 Talend Open Studio Components Creative Commons License . For more information. see tMysqlSCD Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Debug mode Select this check box to display each step during processing entries in a database. Related scenario For related scenarios. i. hence can be reused.. it defines the number of fields to be processed and passed on to the next component.

so if you need to use an existing connection from the other level. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information on how to share a DB connection across Job levels.Business Intelligence components tInformixSCD tInformixSCD tInformixSCD properties Component family Databases/Business Intelligence/Informix tInformixSCD tracks and shows changes which have been made to Informix SCD dedicated tables. tInformixSCD addresses Slowly Changing Dimension transformation needs. Built-in: No property data stored centrally. see your studio user guide. Name of the database. DB server listening port. The following fields are pre-filled in using fetched data Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. Property type Built-in or Repository. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. When a Job contains the parent Job and the child Job. Function Purpose Basic settings Creative Commons License Talend Open Studio Components 9 . Otherwise. Name of the schema. Name of the Informix instance to be used. For more information about Dynamic settings. In this case. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Host Port Database Schema Username et Password Instance Database server IP address. by regularly reading a data source and listing the modifications in an SCD dedicated table. make sure that the available connection components are sharing the intended connection. User authentication information. in Databases components on page 205. This information can generally be found in the SQL hosts file. Repository: Select the Repository file where properties are stored.

Built-in: The schema is created and stored locally for this component only. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. it requires an input component and a connection of the Row > Main type. Related topic: Setting a built-in schema of Talend Open Studio User Guide.Business Intelligence components tInformixSCD Table Schema and Edit Schema Name of the table to be created A schema is a row description. the tMysqlSCD Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23 10 Talend Open Studio Components Creative Commons License . see SCD management methodologies on page 20. Debug mode Select this check box to display each step of the process by which data is written in the database. i. see. The schema is either built-in or remotely stored in the Repository. hence can be reused. Usage This component is an output component.e. Related scenario For a scenarion in which tInformixSCD might be used. Select this check box to improve system performance.. it defines the number of fields to be processed and passed on to the next component. Use memory saving Mode Use Transaction Advanced settings tStatCatcher Statistics Select this check box to collect the log data at a component level. Consequently. Select this check box when the database is configured in NO_LOG mode. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. For more information.

Repository: The schema already exists and is stored in the Repository. it defines the number of fields to be processed and passed on to the next component. tIngresSCD addresses Slowly Changing Dimension needs.. Built-in: No property data stored centrally. Name of the table to be written. Name of the database. i. The schema is either built-in or remotely stored in the Repository. Server Port Database Username and Password Table Schema and Edit Schema Database server IP address. see SCD management methodologies on page 20. DB user authentication data. Debug mode Select this check box to display each step during processing entries in a database.Business Intelligence components tIngresSCD tIngresSCD tIngresSCD Properties Component family Databases/Ingress Function Purpose Basic settings tIngresSCD reflects and tracks changes in a dedicated Ingres SCD table. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Built-in: The schema is created and stored locally for this component only. Creative Commons License Talend Open Studio Components 11 . Usage This component is used as Output component. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Related topic: Setting a Repository schema of Talend Open Studio User Guide. reading regularly a source of data and logging the changes into a dedicated SCD table Property type Either Built-in or Repository. For more information. The fields to follow are pre-filled in using fetched data. It requires an Input component and Row main link as input. Select this check box to maximize system performance. Repository: Select the Repository file where properties are stored. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. A schema is a row description. hence can be reused. Listening port number of DB server. Note that only one table can be written at a time.

Business Intelligence components tIngresSCD Related scenario For related scenarios. 12 Talend Open Studio Components Creative Commons License . see tMysqlSCD Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23.

Built-in: The schema is created and stored locally for this component only. This component covers MDX queries for multi-dimensional datasets.Business Intelligence components tMondrianInput tMondrianInput tMondrianInput Properties Component family Business Intelligence/OLAP Cube tMondrianInput reads data from relational databases and produces multidimensional data sets based on an MDX query. Repository: The schema already exists and is stored in the Repository. Select the encoding from the list or select Custom and define it manually. DB type Property type Select the relevant type of relational database Either Built-in or Repository. Built-in: No property data stored centrally.. it defines the number of fields to be processed and passed on to the next component. DB user authentication data.e. The following fields are pre-filled in using fetched data. Datasource Username and Password Schema and Edit Schema Name and path of the file containing the data. Catalog MDX Query Path to the catalog (structure of the data warehouse). Repository: Select the Repository file where Properties are stored. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Creative Commons License Talend Open Studio Components 13 . hence can be reused. A schema is a row description. i. Then it passes on the multidimensional dataset obtained to the next component via a Main row link. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Type in the MDX query paying particularly attention to properly sequence the fields in order to match the schema definition and the data warehouse structure. This field is compulsory for DB data handling. The schema is either built-in or remotely stored in the Repository. tMondrianInput executes a multi-dimensional expression (MDX) query corresponding to the dataset structure and schema definition. Function Purpose Basic settings Encoding Advanced settings Usage tStatCatcher Statistics Select this check box to collect log data at the component level.

• Select the relevant Schema in the Repository if you store it centrally. In this example the properties are built-in. The data are retrieved using a multidimensional expression (MDX query). Port. if you store your DB connection details centrally. User Name and Password. Database name. • Select the relevant Repository entry as Property type. select the relational database you are using with Mondrian. • Link the Mondrian connector to the output component using a Row Main connection. • Select the tMondrianInput component and select the Component view. 14 Talend Open Studio Components Creative Commons License . • In DB type field. or at least have a structure description (catalog) as a reference for the dataset to be retrieved in the various dimensions. Obviously you need to have to know the structure of your data.Business Intelligence components tMondrianInput Scenario: Cross-join tables This Job extracts multi-dimensional datasets from relational database tables stored in a MySql base. the schema is to be set (built-in). • Fill out the details of connection to your DB: Host. • Drop tMondrianInput and tLogRow from the Palette to the design workspace. In this example.

[All Media].[Radio]. [Promotion Media]. This catalog describes the structure of the warehouse.[Drink].[1997])" Creative Commons License Talend Open Studio Components 15 .[All Products]. unit_sales.[Store Cost]. [Product].[All Media].Business Intelligence components tMondrianInput • The relational database we want to query contains five columns: media. • Then type in the MDX query such as: "select {[Measures].[All Media].[Street Handout] }. • The query aims at retrieving the unit_sales.[Sunday Paper]. [Measures]. [Measures]. [Promotion Media]. drink.[All Media]. store_cost and store_sales.[TV]. store_cost and store_sales figures for various media / drink using an MDX query such as in the example below: • Back on the Basic settings tab of the tMondrianInput component.[Store Sales]} on columns. CrossJoin( { [Promotion Media].[Unit Sales]. [Promotion Media]. set the Catalog path to the data warehouse.children) on rows from Sales where ([Time].

16 Talend Open Studio Components Creative Commons License . Street handout) as shown previously in a table form. • Then press F6 to run the Job. Sunday Paper.Business Intelligence components tMondrianInput • Eventually. • Select the tLogRow component and select the Print header check box to display the column names on the console. Dairy. select the Encoding type on the list. Alcoholic beverages) crossed with each media (TV. The console shows the result of the unit_sales. store_cost and store_sales for each type of Drink (Beverages.

DB user authentication data. For more information about Dynamic settings. Component list presents only the connection components in the same Job level. Name of the DB schema. so if you need to use an existing connection from the other level. Listening port number of DB server. Server Port Schema Database Username and Password Table Database server IP address. The following fields are pre-filled in using fetched data. see your studio user guide. For more information on how to share a DB connection across Job levels.Business Intelligence components tMSSqlSCD tMSSqlSCD tMSSqlSCD Properties Component family Databases/MSSQL Server tMSSqlSCD reflects and tracks changes in a dedicated MSSQL SCD table. in Databases components on page 205. Name of the database. When a Job contains the parent Job and the child Job. In this case. make sure that the available connection components are sharing the intended connection. Name of the table to be written. Function Purpose Basic settings Creative Commons License Talend Open Studio Components 17 . you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Built-in: No property data stored centrally. tMSqlSCD addresses Slowly Changing Dimension needs. Property type Either Built-in or Repository. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Note that only one table can be written at a time. make sure the connection name is unique and distinctive all over through the two Job levels. Repository: Select the Repository file where Properties are stored. Otherwise. reading regularly a source of data and logging the changes into a dedicated SCD table Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined.

i. Repository: The schema already exists and is stored in the Repository.e. This component is used as Output component. 18 Talend Open Studio Components Creative Commons License .. For more information.Business Intelligence components tMSSqlSCD Schema and Edit Schema A schema is a row description. Related scenario For related topics. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Select this check box to maximize system performance. see SCD management methodologies on page 20. it defines the number of fields to be processed and passed on to the next component. Debug mode Usage Select this check box to display each step during processing entries in a database. It requires an Input component and Row main link as input. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Built-in: The schema is created and stored locally for this component only. hence can be reused. This option is not available if you have selected the Use an existing connection check box in the Basic settings. The schema is either built-in or remotely stored in the Repository.. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Use memory saving Mode Advanced settings Additional JDBC parameters tStatCatcher Statistics Select this check box to collect log data at the component level. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Specify additional connection properties for the DB connection you are creating.

Name of the database. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Repository: Select the Repository file where properties are stored. The following fields are pre-filled in using fetched data. tMysqlSCD addresses Slowly Changing Dimension needs. see your studio user guide. Component list presents only the connection components in the same Job level.Business Intelligence components tMysqlSCD tMysqlSCD tMysqlSCD Properties Component family Databases/MySQL Function Purpose Basic settings tMysqlSCD reflects and tracks changes in a dedicated MySQL SCD table. reading regularly a source of data and logging the changes into a dedicated SCD table Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. so if you need to use an existing connection from the other level. For more information about Dynamic settings. Property type Either Built-in or Repository. Name of the table to be written. Listening port number of DB server. make sure that the available connection components are sharing the intended connection. make sure the connection name is unique and distinctive all over through the two Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise. Creative Commons License Talend Open Studio Components 19 . When a Job contains the parent Job and the child Job. in Databases components on page 205. Built-in: No property data stored centrally. For more information on how to share a DB connection across Job levels. In this case. Note that only one table can be written at a time. Host Port Database Username and Password Table Database server IP address. DB user authentication data.

e. The schema is either built-in or remotely stored in the Repository. The SCD editor offers the simplest method of building the data flow for the SCD outputs. see SCD management methodologies on page 20. you can perform one of the following operations: None: No operation is carried out. 20 Talend Open Studio Components Creative Commons License . SCD management methodologies Slowly Changing Dimensions (SCD)s are dimensions that have data that slowly changes.Business Intelligence components tMysqlSCD Action on table On the table defined. and set column change attributes through combining SCD types.. Related topic: Setting a built-in schema of Talend Open Studio User Guide. you can map columns. Create a table: The table does not exist and gets created. The below figure illustrates an example of the SCD editor. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Built-in: The schema is created and stored locally for this component only. it defines the number of fields to be processed and passed on to the next component. For more information. In the SCD editor. It requires an Input component and Row main link as input. Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings. select surrogate key columns. Debug mode Usage Select this check box to display each step during processing entries in a database. i. Use memory saving Mode Advanced settings Additional JDBC parameters tStatCatcher Statistics Select this check box to collect log data at the component level. Select this check box to maximize system performance. Repository: The schema already exists and is stored in the Repository. A schema is a row description. Schema and Edit Schema SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. hence can be reused. Create a table if not exists: The table is created if it does not exist. This component is used as Output component.

Business Intelligence components tMysqlSCD Creative Commons License Talend Open Studio Components 21 .

You can apply any of the SCD types to any column in a source table by a simple drag-and-drop operation. Use this type if tracking changes is not necessary. 22 Talend Open Studio Components Creative Commons License .Business Intelligence components tMysqlSCD SCD keys You must choose one or more source keys columns from the incoming data to ensure its unicity. • Type 1: no history is kept in the database. You must set one surrogate key column in the dimension table and map it to an input column in the source table. • Input field: key is provided in an input field. but it can be an alternate key as long as it uniquely identifies a record and its value does not change. The value of the surrogate key links a record in the source to a record in the dimension table. Source keys: Drag one or more columns from the Unused panel to the Source keys panel to be used as the key (s) that ensure the unicity of the incoming data. Creation: Select any of the below methods to be used for the key generation: • Auto increment: auto-incremental key. Some dimension data may be overwritten and other may stay unchanged over time. • Type 0: is not used frequently. • Routine: you can access the basic functions through Ctrl+ Space bar combination. Combining SCD types The Slowly Changing Dimensions support four types of changes: Type 0 through Type 3. for example the spelling of a name. A surrogate key can be generated based on a method selected on the Creation list. The surrogate key is typically the primary key in the source. this is most appropriate when correcting certain typos. Surrogate keys: Set the column where the generated surrogate key will be stored. This is most appropriate when no effort has been made to deal with the changing dimension issues. New data overwrites old data. The editor uses this mapping to locate the record in the dimension table and to determine whether a record is new or changing. • Table max +1: the maximum value from the SCD table is incremented to create a surrogate key.

lastname. This is most appropriate to track only the previous value of a changing column. The source delimited file contains various personal details including firstname. This type tracks changes using separate columns. and status. This type of change is equivalent to an SCD Type 1. • Type 3: only the information about a previous value of a dimension is written into the database. -version: adds a column to your SCD schema to hold the version number of the record. this column helps to easily spot the active record. -end: adds a column to your SCD schema to hold the end date value for a record. The SCD schema in this type should include SCD-specific extra columns that hold standard log information such as: -start: adds a column to your SCD schema to hold the start date. Creative Commons License Talend Open Studio Components 23 . SCD Type 2 principle lies in the fact that a new record is added to the SCD table when changes are detected on the columns defined. We want to track only the previous city and previous address of a person. company. This is most appropriate to track updates. the end date is NULL or you can select Fixed Year Value and fill in a fictive year to avoid having a null value in the end date field. We want to insert a new record in the dimensional table with a separate key each time a person changes his/her company. Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) This five-component Java scenario describes a Job that tracks changes in four of the columns in a source delimited file and writes changes and the history of changes in an SCD table. An id column helps ensuring the unicity of the data. for example. This type of change is equivalent to an SCD Type 2. city.address. This type of change is equivalent to an SCD Type 3. When the record is currently active. We want any change in the marital status to overwrite the existing old status record.Business Intelligence components tMysqlSCD • Type2: the whole history is stored in the database. only one additional line tracks these changes in the SCD table. You can select one of the input schema columns as a start date in the SCD table. This type tracks historical data by inserting a new record in the dimensional table with a separate key each time a change is made. Note that although several changes may be made to the same record on various columns defined as SCD Type 2. age. -active: adds a column to your SCD schema to hold the true or false status value.

Business Intelligence components tMysqlSCD To realize this kind of scenario. setting up the SCD editor. For more information about Metadata. 24 Talend Open Studio Components Creative Commons License . tFileInputDelimited. This is the main flow of your Job. • Connect tFileInputDelimited. drop the needed metadata item to the design workspace and the database connection detail will automatically display in the relevant fields. double-click tFileInputDelimited to display its Basic settings view. see Defining Metadata items of Talend Open Studio User Guide. The tMysqlConnection component should be used to avoid setting several times the same DB connection when multiple DB components are used. and finally creating the relevant SCD table in the database. tLogRow. • In the design workspace. If you have already stored the connection details locally in the Repository. Step 1: Defining the main flow of the job: • Drop the following components from the Palette onto the design workspace: tMysqlConnection. it is better to divide it into three main steps: defining the main flow of the Job. In this scenario. tMysqlSCD. and tMysqlSCD using the Row Main link. tMysqlCommit. tLogRow. double-click tMysqlConnection to display its Basic settings view and set the database connection details manually. • In the design workspace. we want to connect to the SCD table where all changes in the source delimited file will be tracked down. • Connect tMysqlConnection to tFileInputDelimited and tMysqlSCD to tMysqlCommit using the OnComponntOk trigger.

city.. Row separator. and Field separators are mandatory. set Header to 1.] button next to the File Name field to select the path to the source delimited file. • If needed. the source schema is made of eight columns: firstname. and Limit. • Set the basic settings for tLogRow in order for the content of the source file with varying attributes to display in cells of a table on the console before being processed through the SCD component. The File Name. Footer and limit for the number of processed rows are not set.address.Business Intelligence components tMysqlSCD • Click the three-dot [. Footer. In this scenario. dataset. set Header. double-click tMysqlSCD to define its basic settings. In this scenario. Creative Commons License Talend Open Studio Components 25 . • Click Edit schema to describe the data structure of the source delimited file. age.. lastname. • In the design workspace. that contains the personal details. status and id. • Define the row and field separators used in the source file. company.

• In the design workspace.. click the three-dot [. • If needed. Step 2: Setting up the SCD editor: • In tMysqlSCD basic settings. click Edit schema to view the output data structure of tMysqlSCD. double-click tMysqlCommit to define its basic settings.Business Intelligence components tMysqlSCD • In the Basic settings view.. enter the table name to be used to track changes. select the Use an existing connection check box to reuse the connection details defined on the tMysqlConnection properties. • Select the relevant connection on the Component list if more than one connection exists. • In the Table field. • Click Sync columns to auto propagate all the columns of the delimited file. 26 Talend Open Studio Components Creative Commons License .] button next to the SCD Editor to open the SCD editor and build the data flow for the SCD outputs.

For more information about SCD types. see SCD management methodologies on page 20. • From the Creation list. • Drop the address and city columns to the Type 3 panel to track only the information about the previous value of the address and city. True for the current active record and False for the modified record. -select the active check box to spot the column that will hold the True or False status. Creative Commons License Talend Open Studio Components 27 . In this scenario. select the method to be used for the surrogate key generation.Business Intelligence components tMysqlSCD All columns of the source delimited file. • From the Unused list. we select Fixed Year Value for the end column and fill in a fictive year to avoid having a null value in the end date field. display in the Unused panel of the SCD editor. Then the end date gets filled in and a new record is added with no end date. All other panels in the SCD editor display empty. -select the version check box to hold the version number of the record. Each time a person changes his/her company. coming from the previous component. drop the firstname and lastname columns to the Type 0 panel. The new value will overwrite the old value. In the Versioning area: -Define the start and end columns of your SCD table that will hold the start and end date values. enter a name for the surrogate key in the Name field. • Drop the status column to the Type 1 panel. Auto-increment in this scenario. drop the id column to the Source keys panel to use it as the key to ensure the unicity of the incoming data. • Drop the company column to the Type 2 panel. changes in these two columns do not interest us. • From the Unused list. The end date is null for current records until a change is detected. • In the Surrogate keys panel. a new record will be inserted in the dimensional table with a separate key. SK1 in this scenario.

28 Talend Open Studio Components Creative Commons License . • Click Edit schema to view the input and output data flow. The SCD output schema should include the SCD-specific columns that hold standard log information and that were defined in the SCD editor.Business Intelligence components tMysqlSCD • Click Ok to validate your configuration and close the SCD editor.

age status. Adam gets married and moves to Belmont at 2505 Alisson ct. The console shows the content of the input delimited file. . company. the SCD table has the following schema: firstname. and scd_date. previuos city. Update the delimited file with the above information and press F6 to run your Job. Creative Commons License Talend Open Studio Components 29 . scd_end. scd version. SK1.He works at Scoop. previous_address. scd_active. The SCD table must include the delimited file schema along with the SCD output schema.address.Business Intelligence components tMysqlSCD Step 3: Creating the SCD table: You must create in the database the SCD table you defined in the tMysqlSCD basic settings to be the table that will track changes. She works at Greenwood. lastname. save your Job and press F6 to execute it. city. Janet gets divorced and moves to Adelanto at 355 Golf Rd. To write changes and the history of changes in the defined SCD table. id. In this scenario.

Business Intelligence components tMysqlSCD The console shows the changes in the personal information and the SCD table shows the history of changes made to the input file along with the status and version number. 30 Talend Open Studio Components Creative Commons License .

tMysqlSCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). The fields that come after are pre-filled in using the fetched data. and logs the changes into a dedicated MySQL SCD table. make sure that the available connection components are sharing the intended connection. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. Name of the table to be written. Component list presents only the connection components in the same Job level. Note that only one table can be written at a time Talend Open Studio Components 31 Basic settings Creative Commons License . in Databases components on page 205.Business Intelligence components tMysqlSCDELT tMysqlSCDELT tMysqlSCDELT Properties Component family Databases/MySQL Function Purpose tMysqlSCDELT reflects and tracks changes in a dedicated MySQL SCD table. Name of the database User authentication data for a dedicated database. Name of the input MySQL SCD table. For more information about Dynamic settings. make sure the connection name is unique and distinctive all over through the two Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. see your studio user guide. For more information on how to share a DB connection across Job levels. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. When a Job contains the parent Job and the child Job. Built-in: No property data stored centrally. Host Port Database Username and Password Source table Table The IP address of the database server. Use an existing connection Select this check box and click the relevant tMySqlConnection component on the Component list to reuse the connection details you already defined. Otherwise. In this case. Listening port number of database server. Enter properties manually. so if you need to use an existing connection from the other level.

to ensure the unicity of incoming data. You don not have the possibility to rollback the operation. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. the End Date column shows a null value. SCD Type 2 should be used to trace updates for example. Truncate a table: The table content is deleted. A schema is a row description. Select the columns of the schema that will be checked for changes. hence can be reused. i. Usage This component is used as an output component. Related topic: Setting a Repository schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Repository: The schema already exists and is stored in the Repository. Built-in: The schema is created and stored locally for this component only. 32 Talend Open Studio Components Creative Commons License . Start date: Adds a column to your SCD schema to hold the strat date value. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. Select the method to be used for the surrogate key generation. Create a table if not exists: A table gets created if it does not exist. Drop and create the table: The table is removed and created again Create a table: A new table gets created.Business Intelligence components tMysqlSCDELT Action on table Select to perform one of the following operations on the table defined: None: No action carried out on the table. SCD Type 1 should be used for typos corrections for example. Clear a table: The table content is deleted. End Date: Adds a column to your SCD schema to hold the end date value for the record. Select the columns of the schema that will be checked for changes. The schema is either built-in or remotely stored in the Repository. Select one or more columns to be used as keys. Log versions: Adds a column to your SCD schema to hold the version number of the record. This column helps to easily spot the active record. Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. You can select one of the input schema columns as Start Date in the SCD table. It requires an input component and Row main link as input. When the record is currently active. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. You have the possibility to rollback the operation.e.. Related topic: Setting a built-in schema of Talend Open Studio User Guide.

see tMysqlSCD on page 19 Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23.Business Intelligence components tMysqlSCDELT Related Scenario For related topics. Creative Commons License Talend Open Studio Components 33 .

34 Talend Open Studio Components Creative Commons License . Name of the database. see your studio user guide. make sure that the available connection components are sharing the intended connection.Business Intelligence components tOracleSCD tOracleSCD tOracleSCD Properties Component family Databases/Oracle Function Purpose Basic settings tOracleSCD reflects and tracks changes in a dedicated Oracle SCD table. Database server IP address. Component list presents only the connection components in the same Job level. When a Job contains the parent Job and the child Job. Note that only one table can be written at a time. Repository: Select the Repository file where properties are stored. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case. DB user authentication data. so if you need to use an existing connection from the other level. Otherwise. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. The following fields are pre-filled in using fetched data. make sure the connection name is unique and distinctive all over through the two Job levels. in Databases components on page 205. Select the Oracle version you are using. Listening port number of DB server. reading regularly a source of data and logging the changes into a dedicated SCD table Property type Either Built-in or Repository. Name of the table to be written. Built-in: No property data stored centrally. Name of the DB schema. Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. Connection type DB Version Host Port Database Schema Username and Password Table Select the relevant driver on the list. For more information on how to share a DB connection across Job levels. For more information about Dynamic settings. tOracleSCD addresses Slowly Changing Dimension needs.

Repository: The schema already exists and is stored in the Repository. Select this check box to maximize system performance. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component.e. It requires an Input component and Row main link as input. Usage This component is used as Output component. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. i. Related scenario For related scenarios. Creative Commons License Talend Open Studio Components 35 .. see tMysqlSCD Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23.Business Intelligence components tOracleSCD Schema and Edit Schema A schema is a row description. Built-in: The schema is created and stored locally for this component only. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. hence can be reused. For more information. see SCD management methodologies on page 20. Debug mode Select this check box to display each step during processing entries in a database. The schema is either built-in or remotely stored in the Repository.

and logs the changes into a dedicated DB2 SCD table. In this case. Component list presents only the connection components in the same Job level. so if you need to use an existing connection from the other level. Use an existing connection Select this check box and click the relevant tOracleConnection component on the Component List to reuse the connection details you already defined. For more information about Dynamic settings. Repository: Select the repository file where Properties are stored. make sure that the available connection components are sharing the intended connection. Host Port Database Username and Password Source table Table The IP address of the database server. Built-in: No property data stored centrally. The fields that come after are pre-filled in using the fetched data. see your studio user guide. Name of the table to be written.Business Intelligence components tOracleSCDELT tOracleSCDELT tOracleSCDELT Properties Component family Databases/Oracle Function Purpose tOracleSCDELT reflects and tracks changes in a dedicated Oracle SCD table. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Name of the input DB2 SCD table. Otherwise. Listening port number of database server. tOracleSCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). Name of the database User authentication data for a dedicated database. make sure the connection name is unique and distinctive all over through the two Job levels. Property type Either Built-in or Repository. When a Job contains the parent Job and the child Job. Enter properties manually. For more information on how to share a DB connection across Job levels. in Databases components on page 205. Note that only one table can be written at a time Basic settings 36 Talend Open Studio Components Creative Commons License .

SCD Type 1 should be used for typos corrections for example. Log versions: Adds a column to your SCD schema to hold the version number of the record. the End Date column shows a null value. Built-in: The schema is created and stored locally for this component only. to ensure the unicity of incoming data.. SCD Type 2 should be used to trace updates for example. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. Truncate table: The table content is deleted. Creative Commons License Talend Open Studio Components 37 . Select the columns of the schema that will be checked for changes. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. Repository: The schema already exists and is stored in the Repository. You can select one of the input schema columns as Start Date in the SCD table. Create table if not exists: A table gets created if it does not exist. Select the columns of the schema that will be checked for changes. hence can be reused. i. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. When the record is currently active. Clear table: The table content is deleted. You don not have the possibility to rollback the operation. Select the method to be used for the surrogate key generation. Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. Start date: Adds a column to your SCD schema to hold the start date value. Related topic: Setting a Repository schema of Talend Open Studio User Guide.e. This column helps to easily spot the active record. it defines the number of fields to be processed and passed on to the next component. Select one or more columns to be used as keys. Related topic: Setting a built-in schema of Talend Open Studio User Guide. You have the possibility to rollback the operation. The schema is either built-in or remotely stored in the Repository. Drop and create table: The table is removed and created again Create table: A new table gets created. A schema is a row description.Business Intelligence components tOracleSCDELT Action on table Select to perform one of the following operations on the table defined: None: No action carried out on the table. End Date: Adds a column to your SCD schema to hold the end date value for the record.

Usage This component is used as an output component. Enable debug mode tStatCatcher Statistics Select this check box to collect log data at the component level. Related Scenario For related topics. 38 Talend Open Studio Components Creative Commons License . It requires an input component and Row main link as input. Select this check box to display each step during processing entries in a database. This field is compulsory for DB data handling. see tOracleSCD on page 34 Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23.Business Intelligence components tOracleSCDELT Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually.

reading regularly a source of data and logging the changes into a dedicated SCD table Property type Either Built-in or Repository. make sure that the available connection components are sharing the intended connection. Repository: Select the Repository file where properties are stored. see your studio user guide. Name of the DB schema. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. Creative Commons License Talend Open Studio Components 39 . Component list presents only the connection components in the same Job level. Built-in: No property data stored centrally. Name of the table to be written. Name of the database. DB user authentication data. so if you need to use an existing connection from the other level. Database server IP address. Listening port number of DB server. tParAccelSCD addresses Slowly Changing Dimension needs. For more information about Dynamic settings. The following fields are pre-filled in using fetched data. For more information on how to share a DB connection across Job levels. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. When a Job contains the parent Job and the child Job. Connection type Host Port Database Schema Username and Password Table Select the relevant driver on the list. in Databases components on page 205. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Note that only one table can be written at a time. Otherwise.Business Intelligence components tParAccelSCD tParAccelSCD tParAccelSCD Properties Component family Databases/ParAccel Function Purpose Basic settings tParAccelSCD reflects and tracks changes in a dedicated ParAccel SCD table.

Business Intelligence components tParAccelSCD Schema and Edit Schema A schema is a row description. Repository: The schema already exists and is stored in the Repository. 40 Talend Open Studio Components Creative Commons License . it defines the number of fields to be processed and passed on to the next component. For more information. i. Related topic: Setting a built-in schema of Talend Open Studio User Guide. see SCD management methodologies on page 20.e. Related scenario For related scenarios. The schema is either built-in or remotely stored in the Repository. see tMysqlSCD Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Debug mode Select this check box to display each step during processing entries in a database. hence can be reused. Usage This component is used as Output component. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Select this check box to maximize system performance.. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Built-in: The schema is created and stored locally for this component only. Related topic: Setting a Repository schema of Talend Open Studio User Guide. It requires an Input component and Row main link as input.

Server Port Database Schema Username and Password Table Database server IP address. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information on how to share a DB connection across Job levels. make sure that the available connection components are sharing the intended connection. Repository: Select the Repository file where Properties are stored. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. Property type Either Built-in or Repository. Name of the table to be written.Business Intelligence components tPostgresPlusSCD tPostgresPlusSCD tPostgresPlusSCD Properties Component family Databases/PostgresPl us Server tPostgresPlusSCD reflects and tracks changes in a dedicated MSSQL SCD table. reading regularly a source of data and logging the changes into a dedicated SCD table Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. Note that only one table can be written at a time. see your studio user guide. Otherwise. tPostgresPlusSCD addresses Slowly Changing Dimension needs. In this case. in Databases components on page 205. Listening port number of DB server. The following fields are pre-filled in using fetched data. Built-in: No property data stored centrally. When a Job contains the parent Job and the child Job. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Name of the database. Function Purpose Basic settings Creative Commons License Talend Open Studio Components 41 . so if you need to use an existing connection from the other level. Name of the DB schema. DB user authentication data. For more information about Dynamic settings.

e. it defines the number of fields to be processed and passed on to the next component. hence can be reused. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. see SCD management methodologies on page 20. Related scenario For related topics. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Built-in: The schema is created and stored locally for this component only. It requires an Input component and Row main link as input. The schema is either built-in or remotely stored in the Repository.. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository.Business Intelligence components tPostgresPlusSCD Schema and Edit Schema A schema is a row description. i. 42 Talend Open Studio Components Creative Commons License . Select this check box to maximize system performance. For more information. Debug mode Select this check box to display each step during processing entries in a database. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component is used as Output component.

so if you need to use an existing connection from the other level. Exact name of the schema User authentication data for a dedicated database. Use an existing connection Select this check box and click the relevant tPostgresPlusConnection component on the Component List to reuse the connection details you already defined. make sure the connection name is unique and distinctive all over through the two Job levels. see your studio user guide. and logs the changes into a dedicated PostgresPlus SCD table. Component list presents only the connection components in the same Job level. Property type Either Built-in or Repository. Repository: Select the repository file where Properties are stored. In this case. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Basic settings Creative Commons License Talend Open Studio Components 43 . Enter properties manually. When a Job contains the parent Job and the child Job.Business Intelligence components tPostgresPlusSCDELT tPostgresPlusSCDELT tPostgresPlusSCDELT Properties Component family Databases/Postgresql Function Purpose tPostgresPlusSCDELT reflects and tracks changes in a dedicated Oracle SCD table. Name of the input DB2 SCD table. Built-in: No property data stored centrally. For more information about Dynamic settings. in Databases components on page 205. The fields that come after are pre-filled in using the fetched data. Otherwise. make sure that the available connection components are sharing the intended connection. tPostgresPlusSCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). Name of the database. Listening port number of database server. Host Port Database Schema Username and Password Source table The IP address of the database server. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information on how to share a DB connection across Job levels.

This column helps to easily spot the active record. Start date: Adds a column to your SCD schema to hold the start date value. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository.Business Intelligence components tPostgresPlusSCDELT Table Action on table Name of the table to be written. Select the columns of the schema that will be checked for changes. Note that only one table can be written at a time Select to perform one of the following operations on the table defined: None: No action carried out on the table. 44 Talend Open Studio Components Creative Commons License . i. The schema is either built-in or remotely stored in the Repository.e. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select the method to be used for the surrogate key generation. the End Date column shows a null value. hence can be reused. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. Clear table: The table content is deleted. it defines the number of fields to be processed and passed on to the next component. Built-in: The schema is created and stored locally for this component only. to ensure the unicity of incoming data. Select the columns of the schema that will be checked for changes. Drop and create table: The table is removed and created again Create table: A new table gets created. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. When the record is currently active. Create table if not exists: A table gets created if it does not exist. Select one or more columns to be used as keys. Truncate table: The table content is deleted. End Date: Adds a column to your SCD schema to hold the end date value for the record. SCD Type 2 should be used to trace updates for example. You have the possibility to rollback the operation. You don not have the possibility to rollback the operation. Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. A schema is a row description. SCD Type 1 should be used for typos corrections for example. You can select one of the input schema columns as Start Date in the SCD table.. Log versions: Adds a column to your SCD schema to hold the version number of the record.

Creative Commons License Talend Open Studio Components 45 . Enable debug mode tStatCatcher Statistics Select this check box to collect log data at the component level.Business Intelligence components tPostgresPlusSCDELT Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. This field is compulsory for DB data handling. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Related Scenario For related topics. It requires an input component and Row main link as input. Usage This component is used as an output component. Select this check box to display each step during processing entries in a database.

Built-in: No property data stored centrally. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Name of the database. make sure the connection name is unique and distinctive all over through the two Job levels. DB user authentication data. When a Job contains the parent Job and the child Job. Listening port number of DB server. Name of the table to be written. Property type Either Built-in or Repository. reading regularly a source of data and logging the changes into a dedicated SCD table Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Otherwise. tPostgresqlSCD addresses Slowly Changing Dimension needs. Repository: Select the Repository file where Properties are stored. so if you need to use an existing connection from the other level. make sure that the available connection components are sharing the intended connection. Name of the DB schema. Host Port Database Schema Username and Password Table Database server IP address. see your studio user guide.Business Intelligence components tPostgresqlSCD tPostgresqlSCD tPostgresqlSCD Properties Component family Databases/Postgresql Server tPostgresqlSCD reflects and tracks changes in a dedicated Postrgesql SCD table. For more information about Dynamic settings. Note that only one table can be written at a time. Function Purpose Basic settings 46 Talend Open Studio Components Creative Commons License . For more information on how to share a DB connection across Job levels. in Databases components on page 205. In this case. The following fields are pre-filled in using fetched data. Component list presents only the connection components in the same Job level.

it defines the number of fields to be processed and passed on to the next component. For more information. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level.. It requires an Input component and Row main link as input. The schema is either built-in or remotely stored in the Repository. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Related scenario For related topics. Usage This component is used as Output component. Debug mode Select this check box to display each step during processing entries in a database. i. Built-in: The schema is created and stored locally for this component only. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. see SCD management methodologies on page 20. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. Creative Commons License Talend Open Studio Components 47 . Select this check box to maximize system performance. hence can be reused.Business Intelligence components tPostgresqlSCD Schema and Edit Schema A schema is a row description.

Note that only one table can be written at a time Basic settings 48 Talend Open Studio Components Creative Commons License . you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Repository: Select the repository file where Properties are stored. Built-in: No property data stored centrally. so if you need to use an existing connection from the other level.Business Intelligence components tPostgresqlSCDELT tPostgresqlSCDELT tPostgresqlSCDELT Properties Component family Databases/Postgresql Function Purpose tPostgresqlSCDELT reflects and tracks changes in a dedicated Postgresql SCD table. For more information on how to share a DB connection across Job levels. and logs the changes into a dedicated DB2 SCD table. Listening port number of database server. see your studio user guide. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. The fields that come after are pre-filled in using the fetched data. in Databases components on page 205. make sure that the available connection components are sharing the intended connection. Name of the table to be written. Use an existing connection Select this check box and click the relevant tPostgresqlConnection component on the Component List to reuse the connection details you already defined. Property type Either Built-in or Repository. For more information about Dynamic settings. Otherwise. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Name of the database User authentication data for a dedicated database. When a Job contains the parent Job and the child Job. Name of the input DB2 SCD table. Enter properties manually. tPostgresqlSCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). Host Port Database Username and Password Source table Table The IP address of the database server.

When the record is currently active. Creative Commons License Talend Open Studio Components 49 . SCD Type 2 should be used to trace updates for example. Create table if not exists: A table gets created if it does not exist. The schema is either built-in or remotely stored in the Repository. Log versions: Adds a column to your SCD schema to hold the version number of the record.. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select the columns of the schema that will be checked for changes.e. Clear table: The table content is deleted. Start date: Adds a column to your SCD schema to hold the start date value. Select the columns of the schema that will be checked for changes. You don not have the possibility to rollback the operation. Drop and create table: The table is removed and created again Create table: A new table gets created. A schema is a row description. it defines the number of fields to be processed and passed on to the next component. SCD Type 1 should be used for typos corrections for example. Built-in: The schema is created and stored locally for this component only. Select one or more columns to be used as keys. This column helps to easily spot the active record. End Date: Adds a column to your SCD schema to hold the end date value for the record. You have the possibility to rollback the operation. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. Truncate table: The table content is deleted. i. Repository: The schema already exists and is stored in the Repository. the End Date column shows a null value. You can select one of the input schema columns as Start Date in the SCD table. Select the method to be used for the surrogate key generation. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. to ensure the unicity of incoming data.Business Intelligence components tPostgresqlSCDELT Action on table Select to perform one of the following operations on the table defined: None: No action carried out on the table. Related topic: Setting a built-in schema of Talend Open Studio User Guide. hence can be reused.

Select this check box to display each step during processing entries in a database.Business Intelligence components tPostgresqlSCDELT Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. This field is compulsory for DB data handling. see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Usage This component is used as an output component. Enable debug mode tStatCatcher Statistics Select this check box to collect log data at the component level. Related Scenario For related topics. 50 Talend Open Studio Components Creative Commons License . It requires an input component and Row main link as input.

sav file and displaying the output on the log console. This component is used as a start component. Creative Commons License Talend Open Studio Components 51 .sav data to write it for example in another file. which aims at reading each row of a . If you select this check box. It requires an output flow. You can click Edit schema to view the retrieved metadata. you need to retrieve the metadata again. Filename Translate labels Advanced settings Usage tStatCatcher Statistics Select this check box to collect log data at the component level.<DR>:\program\SPSS.sav file. tSPSSInput properties Component family Business Intelligence Function Purpose Basic settings tSPSSInput reads data from an SPSS . • Right-click on tPSSInput and connect it to tLogRow using a Main Row link. Name or path of the SPSS . you must copy the SPSS IO “spssio32.sav file The following scenario creates a two-component Job. Scenario: Displaying the content of an SPSS . The schema metadata in this component is retrieved directly from the input SPSS . tSPSSInput addresses SPSS . add the path to the SPSS directory as the following: SET PATH=%PATH%. Select this check box to translate the labels of the stored values.sav file to be read. Sync schema Schema and Edit Schema Click this button to synchronize with the columns of the input SPSS .Business Intelligence components tSPSSInput tSPSSInput Before being able to benefit from all functional objectives of the SPSS components. or -If you have not installed SPSS. make sure to do the following: -If you have already installed SPSS.dll” lib from the SPSS installation CD and paste it in Talend root directory.sav file and thus is read-only.sav file. • Drop a tSPSSInput component and a tLogRow component from the Palette onto the design workspace.

• Save the Job and press F6 to execute it. A message opens up prompting you to accept retrieving the schema from the defined SPSS file. • Click OK to close the dialog box. • Click the three-dot button next to Sync schema.sav file you want to read. • Click Yes to close the message and proceed to the next step. The SPSS file is read row by row and the extracted fields are displayed on the log console. • If required. • Click the three-dot button next to the Filename field and browse to the SPSS .Business Intelligence components tSPSSInput • Click tSPSSInput to display its Basic settings view and define the component properties. click the three-dot button next to Edit schema to view the pre-defined data structure of the source SPSS file. 52 Talend Open Studio Components Creative Commons License .

Creative Commons License Talend Open Studio Components 53 . complete the following: • In the Basic settings view. select the Translate label check box. • Click Yes to close the message and proceed to the next step.Business Intelligence components tSPSSInput To carry out translation on the stored values. A second message opens up prompting you to accept propagating the changes. The SPSS file is read row by row and the extracted fields are displayed on the log console after translating the stored values. • Click Sync Schema a second time to retrieve the schema after translation. A message opens up prompting you to accept retrieving the schema from the defined SPSS file. • Click Yes to close the message and proceed to the next step. • Save the Job and press F6 to execute it.

It creates SPSS files on the fly and overwrites existing ones. The schema is either built-in or remotely stored in the Repository.sav file This Java scenario describes a very simple Job that writes data entries in an . tSPSSOutput properties Component family Business Intelligence Function Purpose Basic settings tSPSSOutput writes data entries in an .dll” lib from the SPSS installation CD and paste it in Talend root directory. Built-in: The schema is created and stored locally for this component only.sav file. add the path to the SPSS directory as the following: SET PATH=%PATH%.sav file.sav file.Business Intelligence components tSPSSOutput tSPSSOutput Before being able to benefit from all functional objectives of the SPSS components. i. hence can be reused. tSPSSOutput writes or appends data to an SPSS . Sync schema Schema and Edit Schema Click this button to synchronize with the columns of the SPSS . Filename Write Type Name or path of the SPSS . This component can not be used as start component.e. • Right-click on tRowGenerator and connect it to tSPSSOutput using a Main Row link. Append: writes the new data at the end of the existing data. It requires an input flow Scenario: Writing data in an . Related topic: Setting a Repository schema of Talend Open Studio User Guide.<DR>:\program\SPSS. Repository: The schema already exists and is stored in the Repository. you must copy the SPSS IO “spssio32. Select an operation from the list: Write: simply writes the new data. • Drop a tRowGenerator component and a tSPSSOutput component from the Palette onto the design workspace. A schema is a row description. or -If you have not installed SPSS. Advanced settings Usage tStatCatcher Statistics Select this check box to collect log data at the component level. 54 Talend Open Studio Components Creative Commons License .. Related topic: Setting a built-in schema of Talend Open Studio User Guide. make sure to do the following: -If you have already installed SPSS.sav file to be written. it defines the number of fields to be processed and passed on to the next component.sav file.

Here you can define your schema. • Define the schema and set the parameters to the columns. double click tRowGenerator to display its Basic Settings view and open its editor. • Click tSPSSOutput to display its Basic settings view and define the component properties. • Click OK to validate your schema and close the editor.Business Intelligence components tSPSSOutput • In the design workspace. Creative Commons License Talend Open Studio Components 55 . • Click the plus button to add the columns you want to write in the . • Click the three-dot button next to the Filename field and browse to the SPSS . Make sure to define the length of your columns.sav file in which you want to write data. Otherwise. an error message will display when building your Job.sav file.

• From the Write Type list.Business Intelligence components tSPSSOutput • Click the three-dot button next to Sync columns to synchronize columns with the previous component. In this example. • If required. select Write or Append to simply write the input data in the . 56 Talend Open Studio Components Creative Commons License . click Edit schema to view/edit the defined schema.sav file consists of the two columns: id and country.sav file or add it to the end of the . • Save the Job and press F6 to execute it. The data generated by the tRowGenerator component is written in the defined . the schema to be inserted in the .sav file.sav file.

see: • Scenario: Displaying the content of an SPSS . Built-in: The schema is created and stored locally for this component only.sav file on page 51.sav file to be processed. Repository: The schema already exists and is stored in the Repository. add the path to the SPSS directory as the following: SET PATH=%PATH%. do the following: -If you have already installed SPSS. hence can be reused.sav file.. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Use this component as a start component. Related scenarios For related topics. or -If you have not installed SPSS.e. Filename Name or path of the . • Scenario: Writing data in an . A schema is a row description.<DR>:\program\SPSS.sav file on page 54. Advanced settings Usage tStatCatcher Statistics Select this check box to collect log data at the component level. It needs an output flow. you must copy the SPSS IO “spssio32. tSPSSProperties allows you to obtain information about the main properties of a defined SPSS . tSPSSProperties properties Component family Business Intelligence Function Purpose Basic settings tSPSSProperties describes the properties of a defined SPSS .dll” lib from the SPSS installation CD and paste it in the Talend root directory. You can click Edit schema to view the predefined metadata. Schema and Edit Schema The schema metadata in this component is predefined and thus read-only.Business Intelligence components tSPSSProperties tSPSSProperties In order to benefit from all of the functional objectives of the SPSS components. i. Related topic: Setting a Repository schema of Talend Open Studio User Guide.sav file. Creative Commons License Talend Open Studio Components 57 .

58 Talend Open Studio Components Creative Commons License . The schema is either built-in or remotely stored in the Repository.sav files to further analyze or check the findings. i. Filename Name or path of the . Related topic: Setting a built-in schema of Talend Open Studio User Guide. tSPSSStructure properties Component family Business Intelligence Function Purpose tSPSSStructure retrieves information about the variables inside . make sure to do the following: -If you have already installed SPSS. Basic settings Usage Use this component as a start component.sav file on page 51. see: • Scenario: Displaying the content of an SPSS .<DR>:\program\SPSS.sav files. Repository: The schema already exists and is stored in the Repository.dll” lib from the SPSS installation CD and paste it in Talend root directory. Schema and Edit Schema The schema metadata in this component is predefined and thus read-only. You can use this component in combination with tFileList to gather information about existing *.Business Intelligence components tSPSSStructure tSPSSStructure Before being able to benefit from all functional objectives of the SPSS components. It is based on the internal SPSS convention. tSPSSStructure addresses variables inside . A schema is a row description. you must copy the SPSS IO “spssio32. It needs an output flow.sav file to be processed. or -If you have not installed SPSS. hence can be reused.e. Related topic: Setting a Repository schema of Talend Open Studio User Guide.sav files. Built-in: The schema is created and stored locally for this component only. Related scenarios For related topics.. add the path to the SPSS directory as the following: SET PATH=%PATH%. You can click Edit schema to view the predefined metadata. it defines the number of fields to be processed and passed on to the next component.sav file on page 54. • Scenario: Writing data in an .

In this case. Name of the database. Built-in: No property data stored centrally. Use an existing connection Select this check box and click the relevant DB connection component on the Component list to reuse the connection details you already defined. see your studio user guide. Component list presents only the connection components in the same Job level.e. Repository: Select the Repository file where Properties are stored. Name of the table to be written. reading regularly a source of data and logging the changes into a dedicated SCD table Property type Either Built-in or Repository. The following fields are pre-filled in using fetched data. Note that only one table can be written at a time. make sure that the available connection components are sharing the intended connection. in Databases components on page 205. tSybaseSCD addresses Slowly Changing Dimension needs. i.. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about Dynamic settings. Listening port number of DB server. A schema is a row description. so if you need to use an existing connection from the other level. The schema is either built-in or remotely stored in the Repository. Creative Commons License Talend Open Studio Components 59 . make sure the connection name is unique and distinctive all over through the two Job levels. DB user authentication data. For more information on how to share a DB connection across Job levels.Business Intelligence components tSybaseSCD tSybaseSCD tSybaseSCD properties Component family Databases/Sybase Function Purpose Basic settings tSybaseSCD reflects and tracks changes in a dedicated Sybase SCD table. Otherwise. it defines the number of fields to be processed and passed on to the next component. Host Port Database Username and Password Table Schema and Edit Schema Database server IP address. When a Job contains the parent Job and the child Job.

Select this check box to maximize system performance. Related topic: Setting a Repository schema of Talend Open Studio User Guide. 60 Talend Open Studio Components Creative Commons License . see Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. SCD Editor The SCD editor helps to build and configure the data flow for slowly changing dimension outputs. Related scenarios For related topics. Repository: The schema already exists and is stored in the Repository. Use memory saving Mode Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Related topic: Setting a built-in schema of Talend Open Studio User Guide. see SCD management methodologies on page 20. It requires an Input component and Row main link as input. hence can be reused. Usage This component is used as Output component. For more information. Debug mode Select this check box to display each step during processing entries in a database.Business Intelligence components tSybaseSCD Built-in: The schema is created and stored locally for this component only.

Built-in: No property data stored centrally. Enter properties manually. see your studio user guide. Host Port Database Username and Password Source table Table The IP address of the database server. Note that only one table can be written at a time Talend Open Studio Components 61 Basic settings Creative Commons License . Component list presents only the connection components in the same Job level. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. tSybaselSCDELT addresses Slowly Changing Dimension needs through SQL queries (server-side processing mode). Name of the input Sybase SCD table. Listening port number of database server. so if you need to use an existing connection from the other level. Otherwise. Repository: Select the repository file where Properties are stored. In this case. For more information on how to share a DB connection across Job levels. and logs the changes into a dedicated Sybase SCD table. Name of the database User authentication data for a dedicated database. Use an existing connection Select this check box and click the relevant tSybaseConnection component on the Component List to reuse the connection details you already defined. Name of the table to be written. The fields that come after are pre-filled in using the fetched data. When a Job contains the parent Job and the child Job. make sure the connection name is unique and distinctive all over through the two Job levels.Business Intelligence components tSybaseSCDELT tSybaseSCDELT tSybaseSCDELT Properties Component family Databases/Sybase Function Purpose tSybaseSCDELT reflects and tracks changes in a dedicated Sybase SCD table. in Databases components on page 205. make sure that the available connection components are sharing the intended connection. For more information about Dynamic settings. Property type Either Built-in or Repository.

Select one or more columns to be used as keys. Use SCD Type 2 fields Use type 2 if changes need to be tracked down. You don not have the possibility to rollback the operation. The schema is either built-in or remotely stored in the Repository. Select the columns of the schema that will be checked for changes. Create table if not exists: A table gets created if it does not exist. It requires an input component and Row main link as input. Log Active Status: Adds a column to your SCD schema to hold the true or false status value. Start date: Adds a column to your SCD schema to hold the start date value. to ensure the unicity of incoming data.. This column helps to easily spot the active record. Usage This component is used as an output component. 62 Talend Open Studio Components Creative Commons License . Log versions: Adds a column to your SCD schema to hold the version number of the record. it defines the number of fields to be processed and passed on to the next component. You can select one of the input schema columns as Start Date in the SCD table. Select the method to be used for the surrogate key generation. Schema and Edit Schema Surrogate Key Creation Source Keys Select the surrogate key column from the list. Use SCD Type 1 fields Use type 1 if tracking changes is not necessary. Built-in: The schema is created and stored locally for this component only.Business Intelligence components tSybaseSCDELT Action on table Select to perform one of the following operations on the table defined: None: No action carried out on the table. or you can select Fixed Year value and fill it in with a fictive year to avoid having a null value in the End Date field. i. Clear table: The table content is deleted. Related topic: Setting a Repository schema of Talend Open Studio User Guide. hence can be reused. A schema is a row description. the End Date column shows a null value. Truncate table: The table content is deleted. SCD Type 1 should be used for typos corrections for example. Repository: The schema already exists and is stored in the Repository. You have the possibility to rollback the operation.e. End Date: Adds a column to your SCD schema to hold the end date value for the record. Select the columns of the schema that will be checked for changes. Drop and create table: The table is removed and created again Create table: A new table gets created. When the record is currently active. SCD Type 2 should be used to trace updates for example. Related topic: Setting a built-in schema of Talend Open Studio User Guide.

Business Intelligence components tSybaseSCDELT Related Scenario For related topics. see tMysqlSCD on page 19 Scenario: Tracking changes using Slowly Changing Dimensions (type 0 through type 3) on page 23. Creative Commons License Talend Open Studio Components 63 .

Business Intelligence components tSybaseSCDELT 64 Talend Open Studio Components Creative Commons License .

such as reading and writing CRM. or ERP types of database and reading from or writing to an SAP system. The Business component family groups connectors that covers specific Business needs. .Business components This chapter details the major components that you can find in Business group of the Palette of Talend Open Studio.

This editor enables you to: . or Select the Map. Select in the list the mode you want to use for the created document. Click the three-dot button to display the tAlfrescoOutput editor. Type in the user authentication data to the Alfresco server. Type in the base path where to put the document. Document Mode Container Mode Define Document Type Property Mapping 66 Talend Open Studio Components Creative Commons License . Allows to create and manage documents in an Alfresco server. Note that an error message will display if you try to create a document that already exists Create or update: creates a document if it does not exist or updates the document if it exists. Select in the list the mode you want to use for the destination folder in Alfresco. Note that an error message will display if you try to update a document that does not exist Create or update: creates a destination folder if it does not exist or updates the destination folder if it exists. Note: When you type in the base name. Note that in the Property Mapping area. Create only: creates a document if it does not exist. Update only: updates a destination folder if the folder exists.. select the target location column. you can modify any of the input schemas.Business components tAlfrescoOutput tAlfrescoOutput tAlfresco Properties Component family Business Function Purpose Basic settings Creates dematerialized documents in an Alfresco server where they are indexed under meaningful models.select the file where you defined the metadata according to which you want to save the document in Alfresco -define the type f the document -select any of the aspects in the available aspects list of the model file and click the plus button to add it in the list to the left. Displays the parameters you set in the tAlfrescoOutput editor and according to which the document will be created in the Alfresco server. make sure to use the double backslash (\\) escape character. URL Login and Password Base Type in the URL to connect to the Alfresco Web application. check box and then in the Column list..

-Click the Add button and select a model where you have already defined aspects that contain associations. The below sub sections detail the prerequisite and the installation procedure. Allows to create new documents in Alfresco with associated links towards other documents already existing in Alfresco. it defines the number of fields that will be processed and passed on to the next component. An input component is required. Creative Commons License Talend Open Studio Components 67 . Note that if you make changes. To be able to use the tAlfrescoOutput component. Click Edit Schema to make changes to the schema. When selected. Click the Plus button to add new lines to the Permissions list. Select the Inherit Permissions check box to synchronize access rights between containers and documents. i. the schema automatically becomes built-in. Usage Limitation/Prerequisites Usually used as an output component. -Click the drop-down arrow at the top of the editor and select the corresponding document type.e. to facilitate the navigation process for example. To create associations: -Open the tAlfresco editor.. allows to manually configure access rights to containers and documents. -Click OK to close the editor and display the created association in the Association Target Mapping list. then you can assign roles to user or group columns. This field is compulsory. you need first to install the Alfresco server with few relevant resources. Result Log File Name Browse to the file where you want to save any logs related to the job execution.Business components tAlfrescoOutput Schema and Edit schema A schema is a row description. Select the encoding type from the list or select Custom and define it manually. The schema is either built-in or remote in the Repository. few relevant resources need to be installed: check the Installation procedure sub section for more information. Installation procedure To be able to use tAlfrescoOutput in Talend Open Studio. Advanced settings Configure Target Location Container Allows to configure the (by default) type of containers (folders) Select this check box to display new fields where you can modify the container type to use your own created types based on the father/child model. Configure Permissions Encoding Type Association Target Mapping tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.

launch the alfresco server using the script alf_start.jar and move them to C:\alfredsco\tomcat\webapps\alfresco\WEB-INF\lib • Add the authentification filter of the commands to the web.2.0.jar.5. and talendalfresco-alfresco_1.jar.1.50_16 • Install JDK 1.zip and in the talendalfresco_20081014\alfresco folder.xml file located in the path C:\alfredsco\tomcat\webapps\alfresco\WEB-INF son WEB-INF/ following the model of the example provided in talendalfresco_20081014/alfresco folder of the zipped file talendalfresco_20081014. Installing the Talend Alfresco module Note that the talendalfresco_20081014.jar.0+ • Update the environment variable JAVA_HOME (JAVA_HOME= C:\alfresco) • From the installation folder (C:\alfresco).0. wstx-lgpl-3. talendalfresco-client_1.7. for example: C:\Program Files\Java\jdk1.zip The below figures show the portion of lines (in blue) to add in the file web. 68 Talend Open Studio Components Creative Commons License .Business components tAlfrescoOutput Prerequisites Start with the below operations: • Download the file alfresco-community-tomcat-2.0.1. To install the talendalfresco module: • From talendalfresco_20081014. look for the following jars: stax-api-1.zip is provided with the tAlfrescoOutput component in Talend Open Studio.xml alfresco.zip • Unzip the file in an installation folder.0.bat Make sure that the Alfresco server is launched correctly before start using the tAlfrescoOutput component.

Date • Columns without either mapping or default values. are written as empty strings. which you can create.util. or one or more associations by document if it is mapped to a list value (object). and by "file://" for Windows on a network (which accepts as well "file: \ \") or for Linux. among which are file. • Do not double the backslash in the target base path (automatic escape). for example of the type Date. Multiple properties or associations: • It is possible to create only one association by document if it is mapped to a string value. by using new java.xml (description of the model). unless you type in the path in the basic settings of the tAlfrescoOutput component. Solution: delete all columns without mapping or default values.Business components tAlfrescoOutput Useful information for advanced use Installing new types for Alfresco: From the package_jeu_test. Note that any modification of the type Alfresco will put them back. • You can empty an association by mapping it to an empty list. precede them by "file:" for Windows used locally. for example.zip and in the package_jeu_test/fichiers_conf_alfresco2.ArrayList()in the tMap component. • For URLs referring to files on the file system. Creative Commons License Talend Open Studio Components 69 .xml (web interface of the model). or doing concatenation in the tMap editor for example. web-client-config-custom. Content: • Do not mix up between the file path which content you want to create in Alfresco and its target location in Alfresco. • Provide a URL! It can target various protocols.1 folder. look for the following files: xml H76ModelCustom.xml (registration of the new model) and paste them in the following folder: C:/alfredsco/tomcat/shared/classes/alfresco/extension Dates: • The dates must be of the Talend date type java.util. HTTP and so on. and custom-model-context.

it is impossible to delete an association. -group by: input name. machine-based. tAlfrescoOutput. creating interfaces to capture electronic documents from other applications. • Properties of the reference type are created in the Basic Settings view. the leading open source enterprise content management system. 70 Talend Open Studio Components Creative Commons License . The tAlfrescoOutput component allows you to stock and manage your electronic documents and the related metadata on the Alfresco server. Handwritten Character Recognition (HCR) and Optical Mark Recognition (OMR) are two examples of such technologies. Dematerialization. output name. Scanning paper documents. • An error in the association or the property of the reference type does not prevent the creation of the node that holds the reference. done by man. Furthermore. The range of documents that can be managed with an Enterprise Content Management system include just about everything from basic documents to stock certificates. function list(object). and thus helps to move away from the use of physical documentation to the use of electronic Enterprise Content Management (ECM) systems. containing a name line for example (included in the input rows). scanned documents and digital faxes are not readable texts. Considering the varied nature of the content to be dematerialized.Business components tAlfrescoOutput • However. or an automatic document handling. Now how can this document content along with the related metadata be aggregated and indexed in an Enterprise Content Management system so that it can be retrieved and managed in meaningful ways? Talend provides the answer through the tAlfrescoOutput component. enterprises have to use varied technologies to do it. • Associations are created in the Advanced Settings view. and so on are examples of the technologies available. • Building List(object)with tAggregate: -define the table of the relation n-n in a file. and Enterprise Content Management Dematerialization is the process that convert documents held in physical form into electronic form. converting document images into machine-readable/editable text documents. -operation: output categoryList. for example. input category. Equally important as the content that is captured in various formats from numerous sources in the dematerialization process is the supporting metadata that allows efficient identification of the content via specific queries. ATTENTION list (object) and non simple list! References (documents and folders): • References are created by mapping one or more existing reference nodes (xpath or namepath) using String type or List(object). and a category line (that can be defined with its mapping in a third file). The below figure illustrates Talend’s role between the dematerialization process and the Enterprise Content Management system (Alfresco). To convert them into machine-readable characters. Enterprises dematerialize their content via a manual document handling. different character recognition technologies are used.

see Setting up a File Delimited schema in Talend Open Studio User Guide. double-click tFileInputDelimited to display its basic settings. • Connect the two components together using a Row Main link. the java-based Enterprise Control Management system.Business components tAlfrescoOutput Scenario: Creating documents on an Alfresco server This Java scenario describes a two-component Job which aims at creating two document files with the related metadata in an Alfresco server. Creative Commons License Talend Open Studio Components 71 . Note that if you have already stored your input schemas locally in the Repository. • Drop the tFileInputDelimited and tAlfrescoOutput components from the Palette onto the design workspace. you can simply drop the relevant file item from the Metadata folder onto the design workspace and the delimited file settings will automatically display in the relevant fields in the component Basic settings view. • Set the File Name path and all related properties. For more information about metadata. • In the design workspace.

double-click tAlfrescoOutput to display its basic settings. the delimited file provides the metadata and path of two documents we want to create in the Alfresco server. destination_folder name.Business components tAlfrescoOutput In this scenario. and author. And therefore the input schema of the delimited file will be as the following: • In the design workspace. source_path. 72 Talend Open Studio Components Creative Commons License . The input schema for the documents consists of four columns: file_name.

select the mode you want to use for the created documents.. select the target location column. • In the TargetLocation area. destination_folder_name in this scenario. • In the Container Mode list. select the mode you want to use for the destination folder in Alfresco. • Click the Define Document Type three-dot button to open the tAlfrescoOutput editor. When you type in the base name. check box and then in the Column list. or Select the Map. • In the Document Mode list.. Creative Commons License Talend Open Studio Components 73 .Business components tAlfrescoOutput • In the Alfresco Server area. either type in the base name where to put the document in the server. make sure to use the double backslash (\\) escape character. enter the Alfresco server URL and user authentication information in the corresponding fields.

You can browse for this model folder locally or on the network. All the defined aspects used to select the metadata to write in the Alfresco server display in the Property Mapping list in the Basic Settings view of tAlfrescoOutput. select in the Available Aspects list the aspect(s) to be included in the metadata to write in the Alfresco server. two basic for the Content type (content and name) and an additional one (author). Content in this scenario. • Click the drop-down arrow at the top of the editor to select from the list the type to give to the created document in Alfresco. 74 Talend Open Studio Components Creative Commons License . three aspects in this scenario. After defining the aspects to use for the document to be created in Alfresco. • If needed. In this scenario we want the author name to be part of the metadata registered in Alfresco. All available aspects in the selected model file display in the Available Aspects list. • Click Sync columns to auto propagate all the columns of the delimited file. • If needed. this model folder is not needed any more. click Edit schema to view the output data structure of tAlfrescoOutput.Business components tAlfrescoOutput • Click the Add button to browse and select the xml file that holds the metadata according to which you want to save the documents in Alfresco.

Business components tAlfrescoOutput • Click the three-dot button next to the Result Log File Name field and browse to the file where you want to save any logs after job execution. Creative Commons License Talend Open Studio Components 75 . The two documents are created in Alfresco using the metadata provided in the input schemas. and press F6 to execute it. • Save your Job.

Business components tAlfrescoOutput 76 Talend Open Studio Components Creative Commons License .

Type in the query to select the data to be extracted. Query condition Usage Limitation Usually used as a Start component. In this component the schema is related to the Module selected. Select the relevant module in the list Type in the IP address of the DB server. Schema and Edit Schema A schema is a row description. Note that if you make changes. Creative Commons License Talend Open Studio Components 77 . CentricCRM URL Module Server Type in the webservice URL to connect to the CentricCRM DB.e. n/a Related Scenario No scenario is available for this component yet. i. the schema automatically becomes built-in. Allows to extract data from a Centric CRM DB based on a query. Click Edit Schema to make changes to the schema. An output component is required. Function Purpose Basic settings UserID and Password Type in the Webservice user authentication data.. The schema is either built-in or remote in the Repository.Business components tCentricCRMInput tCentricCRMInput tCentricCRMInput Properties Component family Business/CentricCR M Connects to a module of a Centric CRM database via the relevant webservice. it defines the number of fields that will be processed and passed on to the next component.

it defines the number of fields that will be processed and passed on to the next component. Update or Delete the data in the CentricCRM module. An Input component is required. The schema is either built-in or remote in the Repository. Note that if you make changes. 78 Talend Open Studio Components Creative Commons License . Select the relevant module in the list IP address of the DB server Function Purpose Basic settings UserID and Password Type in the Webservice user authentication data. Usage Limitation Used as an output component. the schema automatically becomes built-in. A schema is a row description.e. CentricCRM URL Module Server Type in the webservice URL to connect to the CentricCRM DB. i.. Click Edit Schema to make changes to the schema. Click Sync columns to retrieve the schema from the previous component connected in the Job. n/a Related Scenario No scenario is available for this component yet.Business components tCentricCRMOutput tCentricCRMOutput tCentricCRMOutput Properties Component family Business/CentricCR M Writes data in a module of a CentricCRM database via the relevant webservice. Action Schema and Edit Schema Insert. Allows to write data into a CentricCRM DB.

Select this check box if you do not want to validate HL7 messages. The column name is the segment name. The fields that come after are pre-filled in using the fetched data. Column Mapping:. The mapping in this array is retrieved from the mapping you have done in the editor. via a Row link. Repository: Select the Repository file where properties are stored. Basic settings Not Validate HL7 Message Advanced settings Advanced separator (for numbers) Encoding Type tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.Business components tHL7Input tHL7Input tHL7Input Properties Component family Business Function Purpose tHL7Input reads an HL7 structured file and extracts data row by row. see Setting up a File XML schema of Talend Open Studio User Guide. For more information about setting up and storing file connection parameters. Property type Either Built-in or Repository: Built-in: No property data stored centrally. Segment Lists Connection: The columns are automatically retrieved from the input file. This field is compulsory. Either: Thousands separator or Decimal separator Select the encoding type from the list or select Custom and define it manually. n/a Creative Commons License Talend Open Studio Components 79 . Click this icon to open a connection wizard and store the Excel file connection parameters you set in the component Basic settings view. Multi Schemas Editor The [Multi Schema Editor] helps to build and configure the data flow in a multi-structure delimited file to associate one schema per output. Usage Limitation Usually used as a Start component. An output component is required. Select this check box to modify the separators to be used for the numbers. Opens an HL7 structured file and reads it row by row to split them up into fields then sends fields as defined in the Schema to the next component.

• Double-click the tHL7Input in order to open its editor.Business components tHL7Input Scenario: Retrieving information about patients and events from a HL7 file. 80 Talend Open Studio Components Creative Commons License . drag and drop a tHL7Input. • From the Palette. and three tLogRow components onto the design workspace. This scenario describes a four-component Job which aims at retrieving information about patients and events from a HL7 file.

PID-5(1)-1-1[ST]. • Drag and drop the following segments from the Message View to the Schema View: PID-1(1)-1-1[SI]. select MSH. select PID. type in your segment Start character and your segment End character.Business components tHL7Input • In the File path field. in the Segment(As Schema) list. select EVN.]. browse your directory and select your HL7 file. • Link the tHL7Input to the three tLogRow. PID-5(1)-5-1[ST]. in the Segment(As Schema) list. • In the Schema View area. • In the File Setting area. • Drag and drop the EVN-1(1)-1-1[ID] and EVN-2(1)-1-1[ST] segments from the Message View to the Schema View. in the Segment(As Schema) list. click [Browse. PID-5(1)-4-1[ST]. PID-5(1)-7-1[ID]. • Click Ok to close the editor. • Save your Job and press F6 to execute it.. • In the Schema View area. • In the Schema View area. PID-5(1)-3-1[ST]. PID-5(1)-2-1[ST]. Creative Commons License Talend Open Studio Components 81 . using respectively MSH. EVN and PID links. • Drag and drop the MSH-3(1)[HD] and MSH-7(1)[TS] segments from the Message View to the Schema View..

which return different types of information. The first one give the message header label and its date.Business components tHL7Input The console displays the three tLogRow tables. The second table shows the information about the patient. 82 Talend Open Studio Components Creative Commons License . The third one displays the event ID and its date.

Click Edit Schema to make changes to the schema. Listening port number of Microsoft CRM database server. i. Username and Password Domain Host Port Time out (seconds) Entity Schema and Edit Schema Logical operators used to combine conditions Creative Commons License Talend Open Studio Components 83 . Enter the name of the user or organization. Number of seconds for the port to listen before closing.Business components tMicrosoftCRMInput tMicrosoftCRMInput tMicrosoftCRMInput Properties Component family Business Function Purpose Basic settings Connects to an entity of Microsoft CRM database via the relevant webservice. it defines the number of fields that will be processed and passed on to the next component. set by an administrator. Property type Either Built-in or Repository: Built-in: No property data stored centrally. Allows to extract data from a MicrosoftCRM DB based on conditions set on specific columns. In this component the schema is related to the selected entity. that needs to access the MicrosoftCRM database. Microsoft Webservice URL Organizename Type in the webservice URL to connect to the MicrosoftCRM DB. Type in the Webservice user authentication data. Type in the IP address of Microsoft CRM database server. The schema is either built-in or remote in the Repository. Select the relevant entity in the list. A schema is a row description.. Type in the domain name of the server on which MicrosoftCRM is hosted. the schema automatically becomes built-in. In the case you want to combine the conditions you set on columns.e. The fields that come after are pre-filled in using the fetched data. if you make changes. select the combine mode you want to use. Repository: Select the Repository file where properties are stored.

and tMicrosoftCRMOutput. • Drop the following components from the Palette to the design workspace: tFileInputdelimited. Value: Type in the column value. make sure to name the columns in accordance with the naming rule set by Microsoft. Operator: Click in the cell and select the operator to bind the input column with the value. • Connect tFileInputDelimited to tMicrosoftCRMInput using OnSubjobOk connection. The conditions are performed one after the other for each row. An output component is required. Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Input column: Click in the cell and select the column of the input schema the condition is to be set on. • Connect tFileInputDelimited to tMicrosoftCRMOutput using a Row Main connection. that is “name_columnname” all in lower case. It then extracts specified rows to an output file using the conditions set on certain input columns. • Connect tMicrosoftCRMIntput to tFileOutputDelimited using a Row Main connection. between quotes if need be. Usually used as a Start component. tMicrosoftCRMInput. tFileOutputDelimited. If you want to write in a CustomEntity in Microsoft CRM database.Business components tMicrosoftCRMInput Conditions Click the plus button to add as many conditions as needed. n/a Usage Limitation Scenario: Writing data in a Microsoft CRM database and putting conditions on columns to extract specified rows This scenario describes a four-component Job which aims at writing the data included in a delimited input file in a custom entity in a MicrosoftCRM database. 84 Talend Open Studio Components Creative Commons License .

footer and limit number of processed rows in the corresponding fields. The input file in this example contains the following columns: new_id. the header. footer and limits are not set. select Built-In and fill the fields that follow manually. Otherwise. • If needed. define the header. • Click Edit schema to open a dialog box where you can define the input schema you want to write in Microsoft CRM database. define the Row Separator allowing to identify the end of a row. new_city.Business components tMicrosoftCRMInput • Double-click tFileInputDelimited to display its Basic settings view and define its properties • Set the Property Type to Repository if you have stored the input file properties centrally in the Metadata node in the Repository tree view. new_status. In this example. Then define the Field Separator used to delimit fields in a row. • Click the three-dot button next to the File Name/Input Stream field and browse to the delimited file that holds the input data. new_firstname. property is set to Built-In. In this example. • In the Basic settings view. Creative Commons License Talend Open Studio Components 85 . new_email. new_initial and new_zipcode.

• Enter the Microsoft Web Service URL as well as the user name and password in the corresponding fields. enter the name that is given the right to access the Microsoft CRM database. • Double-click tMicrosoftCRMOutput to display the component Basic settings view and define its properties. • In the Domain field. and then enter the host IP address and the listening port number in the corresponding fields. • In the OrganizeName field. enter the domain name of the server on which Microsoft CRM is hosted.Business components tMicrosoftCRMInput • Click OK to close the dialog box. 86 Talend Open Studio Components Creative Commons License .

select one among those offered. • In the Time out field. In this example. If needed. we want to insert data in a custom entity in Microsoft CRM. • The Schema is then automatically set according to the entity selected.Business components tMicrosoftCRMInput • In the Action list. In this example. • Double-click tMicrosoftCRMInput to display the component Basic settings view and define its properties. • Click Sync columns to retrieve the schema from the preceding component. • In the Entity list. Creative Commons License Talend Open Studio Components 87 . select the operation you want to carry on. click Edit schema to display a dialog box where you can modify this schema and remove the columns that you do not need in the output. CustomEntity is selected. If CustomEntity is selected. a Custom Entity Name field displays where you need to enter a name for the custom entity. set the amount of time (in seconds) after which the Job will time out.

property is set to Built-In. In this example.Business components tMicrosoftCRMInput • Set the Property Type to Repository if you have stored the input file properties centrally in the Metadata node in the Repository tree view. In this example. • In the Time out field. select Built-In and fill the fields that follow manually. • Enter the Microsoft Web Service URL as well as the user name and password in the corresponding fields. CustomEntity is selected. 88 Talend Open Studio Components Creative Commons License . set the amount of time (in seconds) after which the Job will time out. • In the Entity list. enter the domain name of the server on which Microsoft CRM is hosted. • In the OrganizeName field. enter the name that is given the right to access the Microsoft CRM database. select the one among those offered you want to connect to. and then enter the host IP address and the listening port number in the corresponding fields. Otherwise. • In the Domain field.

select And or Or as the logical operator you want to use to combine the conditions you set on the input columns. Click Yes in the popup message. • In the Condition area. in this example Equal is selected for new_city and Greater Than for new_id. Creative Commons License Talend Open Studio Components 89 . You can use a fixed or a context value in this filed. • Click in each line in the Operator list and select the operator to bind the input column with its value. New York for new_city and 2 for new_id in this example. • Click in each line in the Value list and set the column value. • Click OK to close the dialog box. We want to extract all customer rows whose city is equal to “New York” and whose id is greater than 2. In this example. In this example. In this example.Business components tMicrosoftCRMInput • The Schema is then automatically set according to the entity selected. You will be prompted to propagate changes. new-city and new_id. we want to set two conditions on two different input columns and we use And as the logical operator. • Double-click tFileOutputdelimited to display the component Basic settings view and define its properties. you should set the schema manually since you want to access a custom entity. Copy the seven-column schema from tMicrosoftCRMOutput and paste it in the schema dialog box in tMicrosoftCRMInput. But you can modify it according to your needs. we want to set conditions on two columns. • In the Basic settings view. click the plus button to add as many lines as needed and then click in each line in the Input column list and select the column you want to set condition on.

• Select the Append check box if you want to add the new rows at the end of the records.Business components tMicrosoftCRMInput • Set Property Type to Built-In and then click the three-dot button next to the File Name field and browse to the output file. • Save the Job and press F6 to execute it. • Select the Include Header check box if the output file includes a header. 90 Talend Open Studio Components Creative Commons License . Only customers who live in New York city and those whose “id” is greater than 2 are listed in the output file you stored locally. • Click Sync columns to retrieve the schema from the preceding component. • Set row and field separators in the corresponding fields.

An Input component is required. A schema is a row description. Type in the IP address of Microsoft CRM database server. Click Sync columns to retrieve the schema from the previous component connected in the Job. n/a Usage Limitation Creative Commons License Talend Open Studio Components 91 . and delete. Listening port number of Microsoft CRM database server. Select the relevant entity in the list. Enter the name of the organization that needs to access the MicrosoftCRM database Type in the Webservice user authentication data. Number of seconds for the port to listen before closing. Select in the list the action you want to do on the CRM data. update. Allows to write data into a MicrosoftCRM DB.Business components tMicrosoftCRMOutput tMicrosoftCRMOutput tMicrosoftCRMOutput Properties Component family Business Function Purpose Basic settings Writes in an entity of a Microsoft CRM database via the relevant webservice. Microsoft Webservice URL Organizename Username and Password Domain Host Port Action Type in the webservice URL to connect to the Microsoft CRM DB. Note that if you make changes. Type in the domain name of the server that installs MicrosoftCRM. Available actions are: insert. Click Edit Schema to make changes to the schema. i. the schema automatically becomes built-in. Time out (seconds) Entity Schema and Edit Schema Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Used as an output component..e. The schema is either built-in or remote in the Repository. it defines the number of fields that will be processed and passed on to the next component.

Business components tMicrosoftCRMOutput Related Scenario For a related use case. see Scenario: Writing data in a Microsoft CRM database and putting conditions on columns to extract specified rows on page 84. 92 Talend Open Studio Components Creative Commons License .

e. This component allows to extract data from a MicrosoftAX server based on a query. i. This component is usually used as a start component. Type in the domain name on which the MicrosoftAX server is hosted. Host Domain User and Password Schema and Edit Schema Type in the IP address of the MicrosoftAX server. Property type Either Built-in or Repository. The schema is either built-in or remote in the Repository. if you make changes. Repository: Select the Repository file where properties are stored. An output component is required. Built-in: No property data stored centrally..Business components tMSAXInput tMSAXInput tMSAXInput properties Component family Business/ Microsoft AX tMSAXInput connects to a MicrosoftAX server. A schema is a row description. The fields that come after are pre-filled in using the fetched data. Click Edit Schema to make changes to the schema. it defines the number of fields that will be processed and passed on to the next component. n/a Usage Limitation Related scenarios No scenario is available for this component yet. Type in user authentication data. Function Purpose Basic settings Table Name Query Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Name of the table to read. Enter your SQL query paying particular attention to properly sequence the fields in order to match the schema definition. Creative Commons License Talend Open Studio Components 93 . the schema automatically becomes built-in.

you can retrieve the rows on error via a Row > Rejects link. i. Insert or update: add data or update existing one. Built-in: No property data stored centrally. Name of the table you want to connect to and write/modify data in. Update: update data. Update or insert: update existing data or create it if it does not exist. it defines the number of fields that will be processed and passed on to the next component.e. Type in the domain name on which the MicrosoftAX server is hosted. Repository: Select the Repository file where properties are stored. This component allows to write data in a MicrosoftAX server. Clear the check box to skip the row on error and complete the process for error-free rows. Delete: delete data. the schema automatically becomes built-in. Type in user authentication data. If needed. The schema is either built-in or remote in the Repository. You can do any of the following operations on the data in a MicrosoftAX server: Insert: insert data. if you make changes. Function Purpose Basic settings Schema and Edit Schema Die on error 94 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository. Click Edit Schema to make changes to the schema. A schema is a row description.. The fields that come after are pre-filled in using the fetched data. This check box is selected by default.Business components tMSAXOutput tMSAXOutput tMSAXOutput properties Component family Business/ Microsoft AX tMSAXOutput connects to a MicrosoftAX server. Host Domain Username and Password Table Name Action on data Type in the IP address of the MicrosoftAX server.

for example row1. Data type: type of data. An Input component is required. Name: name of the schema column to be altered or inserted as a new column. This column is not available when you use Insert as action on data. This component is used as an output component. Position: select in the list Before. this option provides you with other possibilities on WHERE statements through using different operators from the Operator column.Business components tMSAXOutput Additional Columns This option allows you to use Local expressions to perform actions on columns. Or. Creative Commons License Talend Open Studio Components 95 . you can alter values in columns of the defined table. make sure that you install and launch the MicrosoftAX server correctly.[row name]. Local expression: Type in the Local statement to be executed in order to alter or insert the relevant column data. When you update or delete data in a column. For example. n/a Usage Limitation Scenario 1: Inserting data in a defined table in a MicrosoftAX server Before being able to use this component. Reference column: type in a column of reference that the component can use to place/replace the new/ altered column. This Java scenario describes a two-component Job that uses tMSAXOutput to insert four columns in a defined table in a MicrosoftAX server after it alters values in one of the inserted columns. Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. After or Replace following the action you want to perform on the reference column. Operator: select in the list the operator you want to use with the WHERE statement. press Ctrl + Space and select any of the context variables available in the list.

Business components tMSAXOutput • Drop tFixedFlowInput and tMSAXOutput from the Palette to the design workspace. three in this example: name. • Click the plus button and add the input schema columns. 96 Talend Open Studio Components Creative Commons License . The three schema columns display automatically in the Values list. city and street. • Connect the two components together using a Row Main link. • Click in the Value column and enter a value for each of the input columns. • Double click tFixedFlowInput to display its Basic settings view and define the component properties. • Click OK to close the dialog box and accept propagating the changes when prompted by the system. • Double-click tMSAXOutput to open its Basic settings view and define the component properties. • Set Schema type to Built-in and click the three-dot button next to Edit schema to display a dialog box where you can define the input schema.

Creative Commons License Talend Open Studio Components 97 . • In the Additional columns list. • Enter your username and password for the server in the corresponding fields. • Click Sync columns to retrieve the schema from the preceding component. • Save your Job and press F6 to execute it. Insert in this example. ADDRESS in this example. In this example. city and street and write the data included in the three input columns in the microsoftAX server without any changes. we want to add a new column we call “address” after the street column. • In the Table Name field. • If needed. In this example. a position and a reference column in the corresponding columns for the line you added. Thus the address column in this example will contain the string: New York-Midtown Manhattan.city)+"-"+row2. click the plus button to add one line where you can define parameters for the new column to add to the row you want to write in the ADDRESS table. This expression will write the city name initially capped followed by the street name to form the address of Bryant park.street. we want to retrieve the three input columns: name. • In the Action on data list. • In the Host field.Business components tMSAXOutput • Set Property type to Built-in. enter the name of the table you want to write data in. a data type.UPCASE(row2. select the action you want to carry on. • In the Domain field. • Set a name. • Click in the Local expression column and press Ctrl + space on your keyboard to open the context variable list and select: StringHandling. type in the IP address of the MicrosoftAX server. click the three-dot button next to Edit Schema to verify the retrieved schema. type in the domain name on which the MicrosoftAX server is hosted.

address in this example. We want to delete from the MicrosoftAX server all addresses that are not identical with this one. This Java scenario describes a two-component Job that uses tMSAXOutput to delete from a defined table in a MicrosoftAX server all rows that do not match the data included in a key column. make sure that you install and launch the MicrosoftAX server correctly. • Drop tFixedFlowInput and tMSAXOutput from the Palette to the design workspace. • Set Schema type to Built-in and click the three-dot button next to Edit schema to display a dialog box where you can define the input schema. the input schema we use is an address column that holds the following data: New York-Midtown Manhattan. name. 98 Talend Open Studio Components Creative Commons License . • Double click tFixedFlowInput to display its Basic settings view and define the component properties. • Connect the two components together using a Row Main link.Business components tMSAXOutput tMSAXOutput inserts in the ADDRESS table in the MicrosoftAX server a row that holds the three input columns. Scenario 2: Deleting data from a defined table in a MicrosoftAX server Before being able to use this component. • Click in the Value column and enter a value for the input column. • Click the plus button and add the input schema columns. • Click OK to close the dialog box. In this example. city and street in addition to the new address column that combines the city name and the street name. The schema column displays automatically in the Values list.

type in the domain name on which the MicrosoftAX server is hosted. • In the Domain field. • Click the three-dot button next to Edit Schema to open a dialog box where you can verify the retrieved schema. • Set Property type to Built-in. type in the IP address of the MicrosoftAX server. In this example. enter the name of the table you want to delete data from.Business components tMSAXOutput • Double-click tMSAXOutput to open its Basic settings view and define the component properties. Creative Commons License Talend Open Studio Components 99 . • In the Action on data list. ADDRESS in this example. select the action you want to carry on. • In the Table Name field. • In the Host field. • Enter your username and password for the server in the corresponding fields. Delete in this example. • Click Sync columns to retrieve the schema from the preceding component. we want to retrieve the input column: address.

• In the Additional columns list. select the Key check box next to the column name you want to define as a key column. • Click OK to validate your changes and close the dialog box. all settings in the Additional columns will not be taken into account when executing your Job. you must always define the Reference column as a key column in order for tMSAXOutput to delete rows based on this key column. tMSAXOutput deletes from the ADDRESS table in the MicrosoftAX server all rows where the address string is not equal to the address in the key column. a position and a reference column in the corresponding columns for the line you added. • Set a name. • Save your Job and press F6 to execute it. 100 Talend Open Studio Components Creative Commons License . a data type. When you select Delete as an action on data. we want to delete from the ADDRESS table in the MicrosoftAX server all rows in which the address column is not equal to the address in the key address column and that reads as the following: New York-Midtown Manhattan. click the plus button to add one line and define the parameters the component will use as basis for the delete operation. a local expression.Business components tMSAXOutput • In the output schema. In this example. you must always set Position to Replace. When you select Delete as an action on data. Otherwise. an operator.

A schema is a row description. the schema corresponds to a selected entity.e. This component allows you to extract data from OpenBravoERP database according to the conditions defined in specific columns. An output component is required. Select the appropriate entity from the drop-down list. User authentication information. Click Edit Schema to make changes to the schema. Openbravo REST WebService URL Username et Password Entity Schema and Edit Schema Enter the URL of the Web service that allows you to connect to the OpenbravoERP database. Select this check box to modify the separators to be used for the numbers. If you make any changes. Either: Thousands separator or Decimal separator WHERE Clause Order by First result Max result Advanced settings Advanced separator (for numbers) tStatCatcher Statistics Select this check box to collect the log data at a component level. n/a Creative Commons License Talend Open Studio Components 101 . For this component.Business components tOpenbravoERPInput tOpenbravoERPInput tOpenbravoERPInput properties Component Family Business Function Purpose Basic settings tOpenbravoERPInput connects to an OpenbravoERP database entity via the appropriate webservice. Utilisation Limitation This component is generally used as an input component. Select this check bow to define how to order the results (the elements in the drop-down list depend on the entity selected) Sort: Choose whether to organise the results in either Ascending or Descending order. The schema is either built-in or remote in the Repository. it defines the number of fields that will be processed and passed on to the next component. i. Enter your WHERE clause. the schema will automatically become built-in. Enter the row number you want to retrieve first.. Enter the maximum number of results you want to retrieve..

Business components tOpenbravoERPInput Related Scenario For a scenario in which tOpenbravoERPInput might be used. see Scenario: Writing data in a Microsoft CRM database and putting conditions on columns to extract specified rows on page 84 102 Talend Open Studio Components Creative Commons License .

see Scenario: Writing data in a Microsoft CRM database and putting conditions on columns to extract specified rows on page 84 Creative Commons License Talend Open Studio Components 103 . Openbravo REST Webservice URL Username et Password Action on data Enter the URL of the Web service that allows you to connect to the OpenbravoERP database. i.. it defines the number of fields that will be processed and passed on to the next component. Click on Sync columns to retrieve the schema from the previous component. From the list. This component writes data in an OpenbravoERP database. Click Edit Schema to make changes to the schema. Select the appropriate entity from the drop-down list. The schema is either built-in or remote in the Repository.Business components tOpenbravoERPOutput tOpenbravoERPOutput tOpenbravoERPOutput properties Component Family Business Function Purpose Basic settings tOpenbravoERPOutput writes an object in an OpenbravoERP database via the appropriate Web service.. A schema is a row description. User authentication information. select the one of the following actions: Update/Create or Remove Select this check box if desired and then select the file by browsing your directory. Use existing data file Entity Schema and Edit Schema Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect the log data at a component level. n/a Related scenario For a scenario in which tOpenbravoERPOutput may be used. It requires an input component.e.. This component is used as an output component. it automatically built-in. Note that if you modify the schema.

Directory where are stored the bulk data you need to process. so if you need to use an existing connection from the other level. you display the Custom Module Name field where you can enter the name of the module you want to connect to. Module 104 Talend Open Studio Components Creative Commons License . Component list presents only the connection components in the same Job level.com. if you select the Use Custom module option. In this case.Business components tSalesforceBulkExec tSalesforceBulkExec tSalesforceBulkExec Properties tSalesforceOutputBulk and tSalesforceBulkExec components are used together to output the needed file and then execute intended actions on the file for your Salesforce. Once you select it. tSalesforceBulkExec gains performance while carrying out the intended data operations into your Salesforce. the Component list field appears allowing you to choose the tSalesforceConnection component to be used. Component family Business Function Purpose Basic settings tSalesforceBulkExec executes the intended actions on the prepared bulk data. make sure that the connection name is unique and distinctive. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB. For more information on tSalesforceConnection. see section tSalesforceConnection on page 106. For more information about Dynamic settings. detailed in a separate section. You can do any of the following operations on the data of the Salesforce object: Insert: insert data. Update: update data. As a dedicated component. Upsert: update and insert data.com. Username and Password Bulk file path Action Type in the Webservice user authentication data. you can use Dynamic settings to share the intended connection. see your studio user guide. When a Job contains the parent Job and the child Job. These two steps compose the tSalesforceOutputBulkExec component. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Select the relevant module in the list.

the schema automatically becomes built-in. The bulk data to be processed should be . Click Edit Schema to make changes to the schema. Advanced settings Rows to commit Bytes to commit Use Socks Proxy tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.csv format. Specify the number of bytes per data batch to be processed. Specify the number of lines per data batch to be processed. see Scenario: Inserting transformed bulk data into your Salesforce. it defines the number of fields that will be processed and passed on to the next component. Related Scenario: For a related scenario.e. Usage Limitation Used as an output component.. Click Sync columns to retrieve the schema from the previous component connected in the Job. The schema is either built-in or remote in the Repository.com on page 121. Creative Commons License Talend Open Studio Components 105 . Note that if you make changes. An Input component is required. Select this check box if you want to use a proxy server. i.Business components tSalesforceBulkExec Schema and Edit Schema A schema is a row description.

Select this check box if you want to use a proxy. Username et Password Timeout (milliseconds) For salesforce bulk component Enter your Web service authentication details. Type in the intended number of query timeout in Salesforce..com. Salesforce Webservice Enter the Webservice URL required to connect to the URL Salesforce database. Select this check box if you want to activate SOAP compression. tSalesforceBulkExec on page 104 and tSalesforceOutputBulkExec on page 126. see tSalesforceOutputBulk on page 121. see tMysqlConnection on page 460.Business components tSalesforceConnection tSalesforceConnection tSalesforceConnection properties Component family Business Function Putpose Basic settings tSalesforceConnection opens a connection to a Salesforce system in order to carry out a transaction. This component is normally used with Salesforce components. The compression of SOAP messages results in increased performance levels. Use Soap Compression Use Socks Proxy Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect the log data at a component level. n/a Related scenario For further information regarding the usage of tSalesforceConnection. For more information on these bulk data processing components. The component enables connection to a Salesforce. Select this check box if you use bulk data processing components from the salesforce family. 106 Talend Open Studio Components Creative Commons License .

The schema is either built-in or remote in the Repository. Click Edit Schema to make changes to the schema. For more information on tSalesforceConnection. Click Sync columns to retrieve the schema from the previous component connected in the Job. it defines the number of fields that will be processed and passed on to the next component. In this case. see your studio user guide. Component list presents only the connection components in the same Job level.com. For more information about Dynamic settings. i. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. Select the relevant module in the list. so if you need to use an existing connection from the other level. This component can collect the deleted data from a Salesforce object during a specific period of time. Once you select it. you display the Custom Module Name field where you can enter the name of the module you want to connect to. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB.. the Component list field appear allowing you to choose the tSalesforceConnection component to be used.e. When a Job contains the parent Job and the child Job. if you select the Use Custom module option. Schema and Edit Schema Creative Commons License Talend Open Studio Components 107 . see section tSalesforceConnection on page 106. make sure that the connection name is unique and distinctive. Username and Password Timeout (milliseconds) Module Type in the Webservice user authentication data. Note that if you make changes. A schema is a row description. you can use Dynamic settings to share the intended connection. the schema automatically becomes built-in.Business components tSalesforceGetDeleted tSalesforceGetDeleted tSalesforceGetDeleted properties Component family Business Function Purpose Basic settings tSalesforceGetDeleted recovers deleted data from a Salesforce object over a given period of time. Type in the intended number of query timeout in Salesforce.

Usage Limitation You can use this component as an output component. The compression of SOAP messages optimizes system performance. Select this check box to activate the SOAP compression. tSalesforceGetDeleted requires an input component. • Drop tSalesforceGetDeleted and tLogRow from the Palette onto the design workspace. Use the following date format:“yyy-MM-dd HH:mm:ss”. End Date Advanced settings Use Soap Compression tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. You can do the search only on the past 30 days.Business components tSalesforceGetDeleted Start Date Type in between double quotes the date at which you want to start the search. Use the following date format: “yyy-MM-dd HH:mm:ss”. Type in between double quotes the date at which you want to end the search. • Connect the two components together using a Row > Main link. • Double-click tSalesforceGetDeleted to display its Basic settings view and define the component properties. n/a Scenario: Recovering deleted data from the Salesforce server This scenario describes a two-component Job that collects the deleted data over the past 5 days from the Salesforce server. 108 Talend Open Studio Components Creative Commons License .

• From the Module list. select Vertical to display the results in a tabular form on the console. You can collect deleted data over the past 30 days. • From the Schema list. • In the Start Date and End Date fields. Account in this example. • In the Username and Password fields. In this example. • Click Sync columns to retrieve the schema from the preceding component. • In the Mode area. select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component.Business components tSalesforceGetDeleted • In the Salesforce WebService URL filed. use the by-default URL of the Salesforce Web service or enter the URL you want to access. select the object you want to access. enter respectively the start and end dates for collecting the deleted data using the following date format: “yyyy-MM-dd HH:mm:ss”. If you have not defined your schema locally in the metadata. enter your login and password for the Web service. • Double-click tLogRow to display its Basic settings view and define the component properties. • Save your Job and press F6 to execute it. we want to recover deleted data over the past 5 days. Creative Commons License Talend Open Studio Components 109 . select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually.

Business components tSalesforceGetDeleted Deleted data collected by the tSalesforceGetDeleted component is displayed in a tabular form on the console. 110 Talend Open Studio Components Creative Commons License .

The compression of the SOAP messages optimizes system performance. A schema is a row description.Business components tSalesforceGetServerTimestamp tSalesforceGetServerTimestamp tSalesforceGetServerTimestamp properties Component family Business Function Purpose Basic settings tSalesforceGetServerTimestamp retrieves the current date of the Salesforce server. Select this check box to activate the SOAP compression. Click Sync columns to retrieve the schema from the previous component connected in the Job. make sure that the connection name is unique and distinctive. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB. the schema automatically becomes built-in. see section tSalesforceConnection on page 106. For more information about Dynamic settings. Advanced settings Use Socks Proxy Use Soap Compression Creative Commons License Talend Open Studio Components 111 . In this case. the Component list field appear allowing you to choose the tSalesforceConnection component to be used. Select this check box if you want to use a proxy server. When a Job contains the parent Job and the child Job.. For more information on tSalesforceConnection. Once you select it. Type in the intended number of query timeout in Salesforce. i. Username and Password Timeout (milliseconds) Schema and Edit Schema Type in the Webservice user authentication data.com. Click Edit Schema to make changes to the schema. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. you can use Dynamic settings to share the intended connection. Note that if you make changes. so if you need to use an existing connection from the other level. This component retrieves the current date of the Salesforce server presented in a timestamp format. see your studio user guide.e. Component list presents only the connection components in the same Job level. it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository.

n/a Related scenarios No scenario is available for this component yet. Usage Limitation You can use this component as an output component. tSalesforceGetServerTimestamp requires an input component.Business components tSalesforceGetServerTimestamp tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. 112 Talend Open Studio Components Creative Commons License .

Note that if you make changes.com. A schema is a row description. Once you select it. the schema automatically becomes built-in. see section tSalesforceConnection on page 106. In this case. i. you can use Dynamic settings to share the intended connection. it defines the number of fields that will be processed and passed on to the next component.. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. Schema and Edit Schema Creative Commons License Talend Open Studio Components 113 .e. so if you need to use an existing connection from the other level. see your studio user guide. This component can collect all updated data from a given Salesforce object during a specific period of time. Select the relevant module in the list. make sure that the connection name is unique and distinctive. When a Job contains the parent Job and the child Job. Username and Password Timeout (milliseconds) Module Type in the Webservice user authentication data. you display the Custom Module Name field where you can enter the name of the module you want to connect to. The schema is either built-in or remote in the Repository. if you select the Use Custom module option. Click Sync columns to retrieve the schema from the previous component connected in the Job. For more information on tSalesforceConnection. the Component list field appear allowing you to choose the tSalesforceConnection component to be used. Type in the intended number of query timeout in Salesforce. Click Edit Schema to make changes to the schema. For more information about Dynamic settings. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB. Component list presents only the connection components in the same Job level.Business components tSalesforceGetUpdated tSalesforceGetUpdated tSalesforceGetUpdated properties Component family Business Function Purpose Basic settings tSalesforceGetUpdated recovers updated data from a Salesforce object over a given period of time.

The compression of SOAP messages optimizes system performance. tSalesforceGetUpdate requires an input component. 114 Talend Open Studio Components Creative Commons License . Type in between double quotes the date at which you want to end the search. You can do the search only on the past 30 days. End Date Advanced settings Use Soap Compression tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Use the following date format: “yyy-MM-dd HH:mm:ss”. Select this check box to activate the SOAP compression. Use the following date format:“yyy-MM-dd HH:mm:ss”.Business components tSalesforceGetUpdated Start Date Type in between double quotes the date at which you want to start the search. n/a Related scenarios No scenario is available for this component yet. Usage Limitation You can use this component as an output component.

you display the Custom Module Name field where you can enter the name of the module you want to connect to. Username and Password Timeout (milliseconds) Module Type in the Webservice user authentication data. The fields that come after are pre-filled in using the fetched data. Allows to extract data from a Salesforce DB based on a query. make sure that the connection name is unique and distinctive. see your studio user guide. the Component list field appear allowing you to choose the tSalesforceConnection component to be used. Creative Commons License Talend Open Studio Components 115 .Business components tSalesforceInput tSalesforceInput tSalesforceInput Properties Component family Business Function Purpose Basic settings tSalesforceInput connects to an object of a Salesforce database via the relevant webservice. you can use Dynamic settings to share the intended connection. Repository: Select the repository file where properties are stored. so if you need to use an existing connection from the other level. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB. When a Job contains the parent Job and the child Job. see Setting up a File XML schema of Talend Open Studio User Guide. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. For more information about setting up and storing file connection parameters. Click this icon to open a connection wizard and store the Excel file connection parameters you set in the component Basic settings view. Component list presents only the connection components in the same Job level. Once you select it.com. if you select the Use Custom module option. Type in the intended number of query timeout in Salesforce. Select the relevant module in the list. In this case. For more information on tSalesforceConnection. For more information about Dynamic settings. Property type Either Built-in or Repository. see section tSalesforceConnection on page 106. Built-in: No property data stored centrally.

the schema automatically becomes built-in. Example: account_name= ‘Talend’ Select this check box to display the Query field where you can manually enter the desired query. Click Edit Schema to make changes to the schema.. see Scenario: Deleting data from the Account object on page 118. in particular for the batch operations. therefore see scenario of tSugarCRMInput on page 149 for more information. i. Characters. In this component the schema is related to the Module selected. The schema is either built-in or remote in the Repository. The operation is similar to the connection to SugarCRM. Type in the query to select the data to be extracted. Characters. Number of registrations in each processed batch. An output component is required. n/a Related scenario For a related scenario. Query condition Maunal input of SOQL query Advanced settings Batch Size Use Socks Proxy Normalize delimited (for child relationship) Column name delimiter (for child relationship) Use Soap Compression tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.Business components tSalesforceInput Schema and Edit Schema A schema is a row description. The compression of SOAP messages optimizes system performance. it defines the number of fields that will be processed and passed on to the next component. 116 Talend Open Studio Components Creative Commons License . Note that if you make changes. Select this check box to activate the SOAP compression. Select this check box if you want to use a proxy server. Usage Limitation Usually used as a Start component. strings or regular expressions used to separate the name of the parent object from the name of the child object when you use a query on the hierarchical relations among the different Salesforce objects.e. strings or regular expressions used to normaliz the data that is collected by queries set on different hierarchical Salsforce objects.

Delete: delete data. For more information about Dynamic settings. Select the relevant module in the list. Allows to write data into a Salesforce DB. Once you select it. In this case. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB. Use an existing connection Select this check box to use an established connection from tSalesforceConnection.com. You can do any of the following operations on the data of the Salesforce object: Insert: insert data. make sure that the connection name is unique and distinctive. Module Creative Commons License Talend Open Studio Components 117 . see section tSalesforceConnection on page 106. Type in the intended number of query timeout in Salesforce. if you select the Use Custom module option. Update: update data. For more information on tSalesforceConnection. you can use Dynamic settings to share the intended connection. you display the Custom Module Name field where you can enter the name of the module you want to connect to. the Component list field appear allowing you to choose the tSalesforceConnection component to be used. so if you need to use an existing connection from the other level. Upsert: update and insert data.Business components tSalesforceOutput tSalesforceOutput tSalesforceOutput Properties Component family Business Function Purpose Basic settings tSalesforceoutput writes in an object of a Salesforce database via the relevant webservice. see your studio user guide. When a Job contains the parent Job and the child Job. Username and Password Timeout (milliseconds) Action Type in the Webservice user authentication data. Component list presents only the connection components in the same Job level.

Clear the check box to skip the row on error and complete the process for error-free rows. Usage Limitation Used as an output component. Click Sync columns to retrieve the schema from the previous component connected in the Job. If needed. Select this check box to activate the SOAP compression. 118 Talend Open Studio Components Creative Commons License . Click Edit Schema to make changes to the schema. you can retrieve the rows on error via a Row > Reject link. click the three-dot button next to this field and browse to the specified file to set its access path and its name. n/a Scenario: Deleting data from the Account object This scenario describes a two-component Job that removes an entry from the Account object. it defines the number of fields that will be processed and passed on to the next component. Select this check box if you want to use a proxy server. the schema automatically becomes built-in.e. not in the Extended Output option.Business components tSalesforceOutput Schema and Edit Schema A schema is a row description. This check box is selected by default. This check box is selected by default. The ID column is added to the processed data schema in Salesforce. The compression of SOAP messages optimizes system performance. Advanced settings Extended Output Die on error Error logging file Use Socks Proxy Use Soap Compression Retrieve inserted ID tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. This option is available only when you have chosen insert action yet not in batch mode. If you want to create a file that holds all error logs. i.. The schema is either built-in or remote in the Repository. You can specify the number of lines per batch in the Rows to commit field. Select this check box to allow Salesforce.com. It allows to transfer output data in batches.e.com to return the salesforce ID produced for a new row that is to be inserted. An Input component is required. Note that if you make changes. i.

select Repository if you have already stored the connection to the salesforce server in the Metadata node of the Repository tree view.Business components tSalesforceOutput •Drop tSalesforceInput and tSalesforceOutput from the Palette onto the design workspace. • Type in your intended query timeout in the Timeout (milliseconds) field. If you have not defined the server connection locally in the Repository. enter your login and password for the Web service. • In the Salesforce WebService URL field. see Managing Metadata. • From the Property Type list. •Connect the two components together using a Row > Main link. Account in this example. •In the Username and Password fields. use the by-default URL of the Salesforce Web service or enter the URL you want to access or select the Use an existing connection check box to use an established connection. Creative Commons License Talend Open Studio Components 119 . The property fields that follow are automatically filled in. select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually. For more information about metadata. select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component. •From the Schema list. In this example. •From the Module list. fill in the details manually after selecting Built-in from the Property Type list. •Double-click tSalesforceInput to display its Basic settings view and define the component properties. If you have not defined your schema locally in the metadata. select the object you want to access. use the default number.

•For a more advanced query. we use the query: “name=’sForce’”. select the operation you want to carry out. In this example. • From the Action list. In this example we select Delete to delete the sForce account selected in the previous component. •Double-click tSalesforceOutput to display its Basic settings view and define the component properties. To do this. • Type in your intended query timeout in the Timeout (milliseconds) field.Business components tSalesforceOutput •In the Query Condition field. use the by-default URL of the Salesforce Web service or enter the URL you want to access. In this example. Check the content of the Account object and verify that the sForce account(s) is/are deleted from the server. select the object you want to access. •In the Salesforce WebService URL field. enter your login and password for the Web service. •In the Username and Password fields. 120 Talend Open Studio Components Creative Commons License . select the Manual input of SOQL query and enter the query manually. we want to retrieve the clients whose names are sForce. Account in this example. •From the Module list. •Click Sync columns to retrieve the schema of the preceding component. enter the query you want to apply. •save your Job and press F6 to execute it. use the default number.

Note that if you make changes.com. Or the existing data will be overwritten. load them in Salesforce. the schema automatically becomes built-in. n/a Usage Limitation Scenario: Inserting transformed bulk data into your Salesforce. Creative Commons License Talend Open Studio Components 121 . Used together they gain performance while feeding or modifying information in Salesforce. This component is intended for the use along with tSalesforceBulkExec component.. i.com. Click Edit Schema to make changes to the schema.com and then displays the Job execution results in the console.e. Prepares the file to be processed by tSalesforceBulkExec for executions in Salesforce.Business components tSalesforceOutputBulk tSalesforceOutputBulk tSalesforceOutputBulk Properties tSalesforceOutputBulk and tSalesforceBulkExec components are used together to output the needed file and then execute intended actions on the file for your Salesforce. The schema is either built-in or remote in the Repository. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Component family Business Function Purpose Basic settings tSalesforceOutputBulk generates files in suitable format for bulk processing. File Name Append Type in the directory where you store the generated file. A schema is a row description.com.csv data suitable for bulk processing. Click Sync columns to retrieve the schema from the previous component connected in the Job.com This scenario describes a six-component Job that transforms . it defines the number of fields that will be processed and passed on to the next component. These two steps compose the tSalesforceOutputBulkExec component. detailed in a separate section. Select the check box to write new data at the end of the existing data. Schema and Edit Schema Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.

Then to create and execute this Job. containing some customer information. this file is sforcebulk. tMap. • Double-click tFileInputDelimited to display its Basic settings view and define the component properties. operate as follows: • Drop tFileInputDelimited. you need to prepare the input file which offers the data to be processed by the Job. and Row > out1 from tMap to tSalesforceOutputBulk.txt. 122 Talend Open Studio Components Creative Commons License . • Use Trigger > OnSubjobOk link to connect tFileInputDelimited and tSalesforceBulkExec. • Use Row > Main link to connect tFileInputDelimited to tMap. Before starting this scenario.Business components tSalesforceOutputBulk This Job is composed of two steps: preparing data by transformation and processing the transformed data. • Use Row > Main and Row > Reject to connect tSalesforceBulkExec respectively to the two tLogRow components. In this use case. tSalesforceOutputBulk. tSalesforceBulkExec and tLogRow from the Palette onto the workspace of your studio.

select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component. • Drop all columns from the input table to the output table. select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually. In this scenario.. ParentId. If you have not defined the server connection locally in the Repository. • According to your input file to be used by the Job.Business components tSalesforceOutputBulk • From the Property Type list. For more information about metadata. • Next to the File name/Stream field. select Repository if you have already stored the connection to the salesforce server in the Metadata node of the Repository tree view. Creative Commons License Talend Open Studio Components 123 . the schema is made of four columns: Name. see Managing Metadata. If you have not defined your schema locally in the metadata. Phone and Fax. sforcebulk. set the other fields like Row Separator..txt. • Double-click the tMap component to open its editor and set the transformation. The property fields that follow are automatically filled in. • From the Schema list. fill in the details manually after selecting Built-in from the Property Type list. click the button to browse to the input file you prepared for the scenario. for example. Field Separator.

select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component. 124 Talend Open Studio Components Creative Commons License . • In the File Name field. If you have not defined your schema locally in the metadata. type in or browse to the directory where you want to store the generated . • From the Action list. • Use the by-default URL of the Salesforce Web service or enter the URL you want to access. • From the Schema list.toUpperCase() behind the Name column. • Double-click tSalesforceOutputBulk to display its Basic settings view and define the component properties. • In the Bulk file path field. • Click Sync columns to import the schema from its preceding component.csv data for bulk processing. Account in this example. select the action you want to carry out on the prepared bulk data. • From the Module list. browse to the directory where is stored the generated . insert. select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually. In this use case. edit it conforming to the schema defined previously. In this example. select the object you want to access. enter your login and password for the Web service.csv file by tSalesforceOutputBulk. • Click OK to validate the transformation.Business components tSalesforceOutputBulk • Add . • Double-click tSalesforceBulkExect to display its Basic settings view and define the component properties. • In the Username and Password fields.

com. In the tLogRow_1 table. • Click Sync columns to retrieve the schema from the preceding component. • Save your Job and press F6 to execute it. On the console of the Run view. • Select Table mode to display the execution result. In the tLogRow_2 table. All the customer names are written in upper case. Creative Commons License Talend Open Studio Components 125 . you can check the execution result. you can read the data inserted into your Salesforce. you can read the rejected data due to the incompatibility with the Account objects you have accessed.Business components tSalesforceOutputBulk • Double-click tLogRow_1 to display its Basic settings view and define the component properties. • Do the same with tLogRow_2.

Component family Business Function Purpose Basic settings tSalesforceOutputBulkExec executes the intended actions on the . You can do any of the following operations on the data of the Salesforce object: Insert: insert data. if you select the Use Custom module option. Update: update data.csv bulk data for Salesforce. These two steps compose the tSalesforceOutputBulkExec component.com. so if you need to use an existing connection from the other level. Select the relevant module in the list. For more information about Dynamic settings. In this case. For more information on tSalesforceConnection. you can use Dynamic settings to share the intended connection. see section tSalesforceConnection on page 106. Module 126 Talend Open Studio Components Creative Commons License .Business components tSalesforceOutputBulkExec tSalesforceOutputBulkExec tSalesforceOutputBulkExec Properties tSalesforceOutputBulk and tSalesforceBulkExec components are used together to output the needed file and then execute intended actions on the file for your Salesforce. make sure that the connection name is unique and distinctive. When a Job contains the parent Job and the child Job.com. Directory where are stored the bulk data you need to process. you display the Custom Module Name field where you can enter the name of the module you want to connect to. Once you select it. Upsert: update and insert data. detailed in a separate section. tSalesforceOutputBulkExec gains performance while carrying out the intended data operations into your Salesforce. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. As a dedicated component. Username and Password Bulk file path Action Type in the Webservice user authentication data. Use an existing connection Select this check box to use an established connection from tSalesforceConnection. Salesforce Webservice Type in the webservice URL to connect to the URL Salesforce DB.com. Component list presents only the connection components in the same Job level. the Component list field appear allowing you to choose the tSalesforceConnection component to be used. see your studio user guide.

you need to prepare the input file which offers the data to be processed by the Job.csv format.com. the schema automatically becomes built-in. you should fill in the proxy parameters in the Proxy host. Before starting this scenario. In this use case.com. Proxy port. Specify the number of bytes per data batch to be processed.e. Then to create and execute this Job. Click Edit Schema to make changes to the schema. it defines the number of fields that will be processed and passed on to the next component.com should be . i. The schema is either built-in or remote in the Repository.txt. Proxy username and Proxy password fields which appear beneath. Usage Limitation This component is mainly used when no particular transformation is required on the data to be loaded into Salesforce. Scenario: Inserting bulk data into your Salesforce. this file is sforcebulk. Note that if you make changes. Click Sync columns to retrieve the schema from the previous component connected in the Job. containing some customer information. In this case.Business components tSalesforceOutputBulkExec Schema and Edit Schema A schema is a row description. executs your intended actions on the data.com This scenario describes a four-component Job that submits bulk data into Salesforce. operate as follows: Creative Commons License Talend Open Studio Components 127 . and ends up with displaying the Job execution results for your reference. Advanced settings Rows to commit Bytes to commit Use Socks Proxy tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Specify the number of lines per data batch to be profcessed.. Select this check box if you want to use a proxy server. The bulk data to be processed in Salesforce.

. ParentId. select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component. If you have not defined the server connection locally in the Repository. • According to your input file to be used by the Job. 128 Talend Open Studio Components Creative Commons License . • Use Row > Main link to connect tFileInputDelimited to tSalesforceOutputBulkExec. the schema is made of four columns: Name. • Next to the File name/Stream field. • From the Property Type list. In this scenario. click the button to browse to the input file you prepared for the scenario. for example. fill in the details manually after selecting Built-in from the Property Type list. see Managing Metadata. set the other fields like Row Separator.. select Repository if you have already stored the connection to the salesforce server in the Metadata node of the Repository tree view. • From the Schema list. For more information about metadata. Field Separator. • Double-click tFileInputDelimited to display its Basic settings view and define the component properties. If you have not defined your schema locally in the metadata. and tLogRow from the Palette onto the workspace of your studio. Phone and Fax. sforcebulk. select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually. • Double-click tSalesforceOutputBulkExec to display its Basic settings view and define the component properties. The property fields that follow are automatically filled in.txt. tSalesforceOutputBulkExec. • Use Row > Main and Row > Reject to connect tSalesforceOutputBulkExec respectively to the two tLogRow components.Business components tSalesforceOutputBulkExec • Drop tFileInputDelimited.

The bulk file here to be processed must be in . • From the Schema list. • Click Sync columns to retrieve the schema from the preceding component. • Double-click tLogRow_1 to display its Basic settings view and define the component properties. browse to the directory where you store the bulk . If you have not defined your schema locally in the metadata. enter your login and password for the Web service. • In the Bulk file path field. Account in this example.csv data to be processed. Creative Commons License Talend Open Studio Components 129 . • From the Action list. select Repository and then click the three-dot button to open a dialog box where you can select the repository schema you want to use for this component.Business components tSalesforceOutputBulkExec • In Salesforce WebService URL field. edit it conforming to the schema defined previously. select Built-in from the Schema list and then click the three-dot button next to the Edit schema field to open the dialog box where you can set the schema manually.csv format. insert. select the object you want to access. • Select Table mode to display the execution result. In this example. • In the Username and Password fields. select the action you want to carry out on the prepared bulk data. use the by-default URL of the Salesforce Web service or enter the URL you want to access. In this use case. • From the Module list.

you can read the data inserted into your Salesforce. In the tLogRow_2 table. If you want to transform the input data before submitting them.com on page 121.Business components tSalesforceOutputBulkExec • Do the same with tLogRow_2. For further information on the use of the two components. 130 Talend Open Studio Components Creative Commons License . you can check the execution result.com. In the tLogRow_1 table. On the console of the Run view. see Scenario: Inserting transformed bulk data into your Salesforce. • Save your Job and press F6 to execute it. you can read the rejected data due to the incompatibility with the Account objects you have accessed. you need to use tSalesforceOutputBulk and tSalesforceBulkExec in cooperation to realize the whole job.

This component is to be used along with SAP components. If you want to use a Row > Main connection to link tSAPCommit to your Job. do not select the Release connection check box or your connection will be closed before the end of your first row commit. n/a Related scenario This component is closely related to tSAPConnection and tSAPRollback. especially with tSAPConnection and tSAPRollback components. Basic settings Release Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.Business components tSAPCommit tSAPCommit tSAPCommit Properties This component is closely related to tSAPConnection and tSAPRollback. Using a unique connection. This check box is selected by default. For tSAPCommit related scenario. Clear this check box to continue to use the selected connection once the component has performed its task. your data will be commited row by row. It usually doesn’t make much sense to use these components separately in a transaction. It allows you to close the database connection once the commit is done. this component commits a global transaction in one go instead of doing that on every row or every batch and thus provides gain in performance. see Scenario: Inserting data in mother/daughter tables on page 460. Component list Select the tSAPConnection component in the list if more than one connection are planned for the current Job. It usually doesn’t make much sense to use one of these without using a tSAPConnection component to open a connection for the current transaction. Component family Business/SAP Function Purpose Validates the data processed through the Job into the connected server. In this case. Creative Commons License Talend Open Studio Components 131 .

Usage Limitation This component is to be used along with other SAP components. Userid : enter user login. Language: specify the language. System number: enter the system number. Connection configuration Client type: enter your usual SAP connection.Business components tSAPConnection tSAPConnection tSAPConnection properties Component family Business Function Purpose Basic settings tSAPConnection opens a connection to the SAP system for the current transaction. . Built-in: No property data is stored centrally. Host name: enter the IP address of the SAP system. n/a Related scenarios For a related scenarios. The fields that follow are pre-filled in using fetched data. Password: enter password. see Scenario 1: Retrieving metadata from the SAP system on page 134 and Scenario 2: Reading data in the different schemas of the RFC_READ_TABLE function on page 140. Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. 132 Talend Open Studio Components Creative Commons License . Repository: Select the Repository file where Properties are stored. Property type Either Built-in or Repository. tSAPConnection allows to commit a whole job data in one go to the SAP system as one transaction.

Function name Creative Commons License Talend Open Studio Components 133 . For more information about Dynamic settings. In this case. so if you need to use an existing connection from the other level. Use an existing connection Select this check box and click the relevant connection component on the Component list to reuse the connection details you already defined. make sure that the connection name is unique and distinctive. Language: Specify a language. you can use Dynamic settings to share the intended connection. Property type Either Built-in or Repository: Built-in: No property data stored centrally. When a Job contains the parent Job and the child Job. The fields that come after are pre-filled in using the fetched data. Password: Enter the password. Enter the name of the function you want to use to retrieve data. Host name Enter the SAP system IP address.Business components tSAPInput tSAPInput tSAPInput Properties Component family Business Function Purpose Basic settings tSAPInput connects to the SAP system using the system IP address. see your studio user guide. System number Enter the system number. see Setting up a File XML schema of Talend Open Studio User Guide. Click this icon to open a connection wizard and store the Excel file connection parameters you set in the component Basic settings view. Connection configuration Client type: Enter your SAP usual connection code Userid: Enter the user connection Id. Component list presents only the connection components in the same Job level. Repository: Select the Repository file where Properties are stored. tSAPInput allows to extract data from an SAP system at any level through calling RFC or BAPI functions. For more information about setting up and storing file connection parameters.

This java scenario uses the SAP wizard to first create a connection to the SAP system.Business components tSAPInput Initialize input Set input parameters. 134 Talend Open Studio Components Creative Commons License . Usually used as a Start component. This SAP wizard is available only for Talend Integration Suite users. This scenario uses the SAP wizard that leads a user through dialog steps to create SAP connection and call RFC and BAPI functions. Table Name (Structure Name): Enter between inverted commas the table name. It finally displays in Talend Open Studio the company details stored in the SAP system. The below figure shows the company detail parameters stored in the SAP system and that we want to read in Talend Open Studio using the tSAPInput component. Table Name (Structure Name): Enter between inverted commas the table name. Type (for iterate): Select the type of the output entity you want to have. levels. and then call a BAPI function to retrieve the details of a company from the SAP system. Type: Select the type of the input entity to retrieve. you need to set the basic settings for the tSAPInput component manually. Configure the parameters of the output schema to select the data to be extracted: Schema: Enter the output schema name. Mapping: Enter between inverted commas the name of the field you want to retrieve data from. Outputs Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Parameter Value: Enter between inverted commas the value that corresponds to the parameter you set in the Parameter Name column. RFC or BAPI. An output component is required. n/a Usage Limitation Scenario 1: Retrieving metadata from the SAP system Talend SAP components (tSAPInput and tSAPOutput) as well as the SAP wizard are based on a library validated and provided by SAP (JCO) that allows the user to call functions and retrieve data from the SAP system at Table. If you are a user of Talend Open Studio or Talend On Demand. Parameter Name: Enter between in.verted commas the name of the field that corresponds to the table set in the Table Name column.

Business components tSAPInput • Create a connection to the SAP system using the SAP connection wizard. • Call the BAPI function BAPI_COMPANY_GETDETAIL using the SAP wizard to access the BAPI HTML document stored in the SAP system and see the company details. • Select BAPI_COMPANY_GETDETAIL to display the schema that describe the company details. The three-tab view to the right of the wizard displays the metadata of the BAPI_COMPANY_GETDETAIL function and allows you to set the necessary parameters. type in BAPI* and click the Search button to display all available BAPI functions. in this scenario the SAP connection is called sap and is saved in the Metadata node. The Document view displays the SAP html document about the BAPI_COMPANY_GETDETAIL function. Creative Commons License Talend Open Studio Components 135 . • In the Name filter field.

In this scenario. 136 Talend Open Studio Components Creative Commons License . • In the Parameter view. click the Output tab to list the output parameters returned by BAPI_COMPANY_GETDETAIL. there is only one input parameter required by BAPI_COMPANY_GETDETAIL and it is called COMPANYID. In this scenario. Each of these two “structure” parameters consists of numerous “single” parameters. click the Input tab to list the input parameter(s).Business components tSAPInput The Parameter view provides information about the input and output parameters required by the BAPI_COMPANY_GETDETAIL function to return values. • In the Parameter view. there are two output parameters: COMPANY_DETAIL and RETURN.

select output. • Click Launch at the bottom of the view to display the value of each “single” parameter returned by the BAPI_COMPANY_GETDETAIL function. The two schemas display under the BAPI_COMPANY_GETDETAIL function in the Repository tree view. In this scenario. do the following: • Right-click BAPI_COMPANY_GETDETAIL in the Repository tree view and select Retrieve schema in the contextual menu.table.Business components tSAPInput The Test it view allows you to add or delete input parameters according to the called function. select the schemas you want to retrieve. • Click Next to display the two selected schemas and then Finish to close the dialog box. Creative Commons License Talend Open Studio Components 137 . • In the open dialog box. • Click Finish to close the wizard and create the connection. we want to retrieve the metadata of the COMPANY_DETAIL “structure” parameter that consists of 14 “single” parameters. To retrieve the different schemas of the BAPI_COMPANY_GETDETAIL function. COMPANY_DETAIL and RETURN in this scenario. enter “000001” to send back company data corresponding to the value 000001. • In the Value column of the COMPANYID line in the first table. • In the Output type list at the bottom of the wizard. The sap connection and the new schema BAI_COMPANY_GETDETAIL display under the SAP Connections node in the Repository tree view.

right-click tSAPInput and select Row > row_COMPANY_DETAIL_1 and then click tLogRow. • In the Repository tree-view. • Connect tSAPConnection and tSAPInput using a Trigger > OnSubJobOk link • To connect tSAPInput and tLogRow. If not. sap in this example. • Double-click tSAPConnection to display the Basic settings view and define the component properties. • Select tSAPInput from the component list and click OK. • Drop tFilterColumns and tLogRow from the Palette to the design workspace. 138 Talend Open Studio Components Creative Commons License . the Repository mode is selected in the Property Type list and the fields that follow are pre-filled. drop the SAP connection you already created to the design workspace to open a dialog box where you can select tSAPConnection from the component list and finally click OK to close the dialog box. you need to select Built-in as “property type” and fill in the connection details manually. The tSAPConnection component holding the SAP connection. expand Metadata and sap in succession and drop RFC_READ_TABLE to the design workspace to open a component list.Business components tSAPInput To retrieve the company metadata that corresponds to the 000001 value and display it in Talend Open Studio. do the following: • In the Repository tree view. If you store connection details in the Metadata node in the Repository tree view. displays on the design workspace.

we can see all different schemas of the BAPI_COMPANY_GETDETAIL function. we can see the input parameter needed by the BAPI_COMPANY_GETDETAIL function. in particular. In the Initialize input area. sap in this scenario. • Save your Job and press F6 to execute it. For more information about this component. double click tSAPInput to display its Basic settings view and define the component properties. • Select the Use an existing connection check box and then in the Component List. double-click tLogRow to display the Basic settings view and define the component properties. • In the design workspace. In the Outputs area. select the relevant tSAPConnection component.Business components tSAPInput • In the design workspace. see tLogRow on page 1023. The basic setting parameters for the tSAPInput component display automatically since the schema is stored in the Metadata node and the component is initialized by the SAP wizard. Creative Commons License Talend Open Studio Components 139 . COMPANY_DETAIL that we want to output.

• Call the RFC_READ_TABLE RFC function using the SAP wizard to access the table in the SAP system and see its structure. Scenario 2: Reading data in the different schemas of the RFC_READ_TABLE function Talend SAP components (tSAPInput and tSAPOutput) as well as the SAP wizard are based on a library validated and provided by SAP (JCO) that allows the user to call functions and retrieve data from the SAP system at Table. This SAP wizard is available only for Talend Integration Suite users. • In the Name filter field. and then call an RFC function to directly read from the SAP system a table called SFLIGHT. type in RFC* and click the Search button to display all available RFC functions. If you are a user of Talend Open Studio or Talend On Demand. you need to set the basic settings for the tSAPInput component manually. • Create a connection to the SAP system using the SAP connection wizard. This scenario uses the SAP wizard that leads a user through dialog steps to create a SAP connection and call RFC and BAPI functions. This java scenario uses the SAP wizard to first create a connection to the SAP system. levels. in this scenario the SAP connection is called sap. RFC or BAPI. It finally displays in Talend Open Studio the structure of the SFLIGHT table stored in the SAP system.Business components tSAPInput tSAPInput retrieved from the SAP system the metadata of the COMPANY_DETAIL “structure” parameter and tLogRow displayed the information on the console. 140 Talend Open Studio Components Creative Commons License .

The three-tab view to the right of the wizard displays the metadata of the RFC_READ_TABLE function and allows you to set the necessary parameters. Creative Commons License Talend Open Studio Components 141 . The Parameter view provides information about the parameters required by the RFC_READ_TABLE function to return parameter values. • In the Parameter view. click the Table tab to show a description of the structure of the different tables of the RFC_READ_TABLE function.Business components tSAPInput • Select RFC_READ_TABLE to display the schema that describe the table structure. The Document view displays the SAP html document about the RFC_READ_TABLE function.

Business components tSAPInput The Test it view allows you to add or delete input parameters according to the called function. enter SFLIGHT as the table to query. select output. we want to retrieve the structure of the SFLIGHT table and not any data. the delimiter is “. • In the Output type list at the bottom of the view.” and the table to read is SFLIGHT. • In the Value column of the QUERY_TABLE line. • In the Value column of the DELIMITER line. • In the Constructure|Table list. select DATA. In this example.table. In this example. • Click Launch at the bottom of the view to display the parameter values returned by the RFC_READ_TABLE function. enter “.” as field separator. 142 Talend Open Studio Components Creative Commons License .

The three schemas display under the RFC_READ_TABLE function in the Repository tree view. drop the RFC_READ_TABLE function of the sap connection to the design workspace to open a dialog box where you can select tSAPInput from the component list and then click OK to close the dialog box. To connect components together: • Right-click tSAPInput and select Row > row_DATA_1 and click the first tLogRow component. • Drop two tLogRow components from the Palette to the design workspace. we want to retrieve the FIELDS and DATA schemas and put them in two different output flows. do the following: • In the Repository tree view. DATA. Creative Commons License Talend Open Studio Components 143 .Business components tSAPInput • Click Finish to close the wizard and create the connection. To retrieve the different schemas of the RFC_READ_TABLE function. The sap connection and the RFC_READ_TABLE function display under the SAPConnections node in the Repository tree view. To do that. The tSAPInput component displays on the design workspace. right-click RFC_READ_TABLE and select Retrieve schema in the contextual menu. proceed as the following: • In the Repository tree view. • Right-click tSAPInput and select Row > row_FIELDS_1 and click the second tLogRow components. • Click Finish to validate your operation and close the dialog box. we want to retrieve the data and column names of the SFLIGHT table and display them in Talend Open Studio. • Click Next to open a new view on the dialog box and display these different schemas. In this example. A dialog box displays. FIELDS and OPTIONS in this example. In this example. • Select in the list the schemas you want to retrieve.

144 Talend Open Studio Components Creative Commons License . we can see the different schemas of the SFLIGHT table. double-click tSAPInput to open the Basic settings view and display the component properties. The basic setting parameters for the tSAPInput component display automatically since the schema is stored in the Metadata node and the component is initialized by the SAP wizard. we can see the input parameters necessary for the RFC_READ_TABLE function.Business components tSAPInput • In the design workspace. the field delimiter “. In the Outputs area.” and the table name “SFLIGHT”. In the Initialize input area.

see tLogRow on page 1023. For more information on the properties of tLogRow. Creative Commons License Talend Open Studio Components 145 . • Save your Job and press F6 to execute it. The tLogRow components display the information in a tabular form in the Console.Business components tSAPInput • In the design workspace. double click each of the two tLogRow components to display the Basic settings view and define the component properties. The tSAPInput component retrieves from the SAP system the column names of the SFLIGHT table as well as the corresponding data.

see Setting up a File XML schema of Talend Open Studio User Guide. The fields that come after are pre-filled in using the fetched data. Schema and Edit Schema Function name 146 Talend Open Studio Components Creative Commons License . Use an existing connection Select this check box and click the relevant connection component on the Component list to reuse the connection details you already defined. the schema automatically becomes built-in. In this case.Business components tSAPOutput tSAPOutput tSAPOutput Properties Component family Business Function Purpose Basic settings Writes to an SAP system. i. make sure that the connection name is unique and distinctive. it defines the number of fields that will be processed and passed on to the next component. Language: Specify a language. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository: Built-in: No property data stored centrally. Click Edit Schema to make changes to the schema. you can use Dynamic settings to share the intended connection.. Enter the name of the function you want to use to write data. Note that if you make changes. so if you need to use an existing connection from the other level. For more information about Dynamic settings. When a Job contains the parent Job and the child Job. see your studio user guide. Connection configuration Client type: Enter your SAP usual connection code Userid: Enter the user connection Id. The schema is either built-in or remote in the Repository. Host name Enter the SAP system IP address. For more information about setting up and storing file connection parameters. A schema is a row description. Allows to write data into an SAP system. Password: Enter the password. System number Enter the system number. Component list presents only the connection components in the same Job level.e. Click this icon to open a connection wizard and store the Excel file connection parameters you set in the component Basic settings view.

An input component is required.Business components tSAPOutput Mapping Usage Limitation Set the parameters to select the data to write to the SAP system. Creative Commons License Talend Open Studio Components 147 . n/a Related scenario For a related scenarios. see Scenario 1: Retrieving metadata from the SAP system on page 134 and Scenario 2: Reading data in the different schemas of the RFC_READ_TABLE function on page 140. Usually used as an output component.

Component family Business/SAP Function Purpose Basic settings tSAPRollback cancels the transaction commit in the connected SAP. Clear this check box to continue to use the selected connection once the component has performed its task. It usually does not make much sense to use these components separately in a transaction. n/a Related scenarios For tSAPRollback related scenario. 148 Talend Open Studio Components Creative Commons License . Component list Select the tSAPConnection component in the list if more than one connection are planned for the current Job.Business components tSAPRollback tSAPRollback tSAPRollback properties This component is closely related to tSAPCommit and tSAPConnection. tSAPRollback avoids to commit only a fragment of a transaction. This component is intended to be used along with SAP components. see Scenario: Rollback from inserting data in mother/daughter tables on page 498 of the tMysqlRollback. Release Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tSAPConnection and tSAPCommit.

Note that if you make changes.Business components tSugarCRMInput tSugarCRMInput tSugarCRMInput Properties Component family Business Function Purpose Basic settings Connects to a Sugar CRM database module via the relevant webservice. An output component is required. the schema automatically becomes built-in. Creative Commons License Talend Open Studio Components 149 . Allows you to extract data from a SugarCRM DB based on a query. The Custom module package name and Custom module name fields which appear are automatically filled in with the relevant names. SugarCRM Webservice URL Module Type in the webservice URL to connect to the SugarCRM DB. The schema is either built-in or remote in the Repository. • Connect the input component to the output component using a main row link. Select the relevant module from the list To use customized tables. A schema is a row description. Click Edit Schema to make changes to the schema. In this component the schema is related to the Module selected. select Use custom module from the list. Example: account_name= ‘Talend’ Username and Password Schema and Edit Schema Query condition Usage Limitation Usually used as a Start component. it defines the number of fields that will be processed and passed on to the next component. i..e. • Drop a tSugarCRMInput and a tFileOutputExcel component onto the workspace. Type in the query to select the data to be extracted. Type in the Webservice user authentication data. n/a Scenario: Extracting account data from SugarCRM This scenario describes a two-component Job which extracts account information from a SugarCRM database and writes it to an Excel output file.

• Save the Job and press F6 to run it.Business components tSugarCRMInput • On the tSugarCRMInput Component view. In this example. In this example: “billing_address_city=’Sunnyvale’” • Then select the tFileOutputExcel component. • In the Query Condition field. • The Schema is then automatically set according to the module selected. The filtered data is output in the defined spreadsheet of the specified Excel type file. 150 Talend Open Studio Components Creative Commons License . type in the query you want to extract from the CRM. • Set the destination file name as well as the Sheet name and select the Include header check box. Accounts is selected. But you can change it and remove the columns that you don’t require in the output. fill in the connection information in the SugarCRM Web Service URL as well as the Username and Password fields • Then select the Module from the list of modules offered.

Note that if you make changes. Insert or Update the data in the SugarCRM module. The Custom module package name and Custom module name fields which appear are automatically filled in with the relevant names.Business components tSugarCRMOutput tSugarCRMOutput tSugarCRMOutput Properties Component family Business Function Purpose Basic settings Writes in a Sugar CRM database module via the relevant webservice. it defines the number of fields that will be processed and passed on to the next component. Click Edit Schema to make changes to the schema. Type in the Webservice user authentication data. An Input component is required. select Use custom module from the list. Allows you to write data into a SugarCRM DB.. A schema is a row description. The schema is either built-in or remote in the Repository.e. Select the relevant module from the list To use customized tables. i. Username and Password Action Schema and Edit Schema Usage Limitation Used as an output component. Click Sync columns to retrieve the schema from the previous component connected in the Job. the schema automatically becomes built-in. Creative Commons License Talend Open Studio Components 151 . n/a Related Scenario No scenario is available for this component yet. SugarCRM Webservice URL Module Type in the webservice URL to connect to the SugarCRM DB.

Usually used as a Start component. Server Address Port Username and Password Version Module Method Type in the IP address of the VtigerCRM server Type in the Port number to access the server Type in the user authentication data. n/a Usage Limitation Related Scenario No scenario is available for this component yet. i.e. An output component is required. the schema automatically becomes built-in. it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository. Note that if you make changes. Type in the version of VtigerCRM you are using. In this component the schema is related to the Module selected.Business components tVtigerCRMInput tVtigerCRMInput tVtigerCRMInput Properties Component family Business/VtigerCRM Function Purpose Basic settings Connects to a module of a VtigerCRM database. The method specifies the action you can carry out on the VtigerCRM module selected. A schema is a row description. Allows to extract data from a VtigerCRM DB. Select the relevant module in the list Select the relevant method on the list. 152 Talend Open Studio Components Creative Commons License . Schema and Edit Schema Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.. Click Edit Schema to make changes to the schema.

it defines the number of fields that will be processed and passed on to the next component. Server Address Port Username and Password Version Module Method Type in the IP address of the VtigerCRM server Type in the Port number to access the server Type in the user authentication data. The method specifies the action you can carry out on the VtigerCRM module selected. the schema automatically becomes built-in. Note that if you make changes. In this component the schema is related to the Module selected. An Input component is required. A schema is a row description. Allows to write data from a VtigerCRM DB. Type in the version of VtigerCRM you are using. The schema is either built-in or remote in the Repository. Click Edit Schema to make changes to the schema. Schema and Edit Schema Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. n/a Usage Limitation Related Scenario No scenario is available for this component yet.. i. Creative Commons License Talend Open Studio Components 153 . Used as an output component.e. Select the relevant module in the list Select the relevant method on the list.Business components tVtigerCRMOutput tVtigerCRMOutput tVtigerCRMOutput Properties Component family Business/VtigerCRM Function Purpose Basic settings Writes data into a module of a VtigerCRM database.

Business components tVtigerCRMOutput 154 Talend Open Studio Components Creative Commons License .

The Custom Code components enable you to create codes for specific needs. quickly and efficiently. .Custom Code components This chapter details the major components which belong to the Custom Code family in the Talend Open Studio Palette.

Custom Code components tGroovy tGroovy tGroovy Properties Component Family Custom Code Function Purpose Basic settings tGroovy allows you to enter customized code which you can integrate in the Talend programme. Groovy Script Variables Enter the Groovy code youo want to run. Related Scenarios • For a scenario using the Groovy code. Select this check box to collect the log data at component level. Advanced settings Usage Limitation tStatCatcher Statistics This component can be used alone or as a subjob along with one other component. • For a functional example. This table has two columns. see Scenario: Calling a file which contains Groovy code on page 157. The code is run only once.. Name: Name of the variable called in the code. tGroovy broadens the functionality if the Talend Job. using the Groovy language which is a simplified Java syntax. Knowledge of the Groovy language is required. Value: Value associated with the variable. see Scenario: Printing out a variable content on page 159 156 Talend Open Studio Components Creative Commons License .

Creative Commons License Talend Open Studio Components 157 . Select this check box to collect the log data at component level. Groovy File Variables Name and path of the file containing the Groovy code. The Job calls a file containing Groovy code in order to display the file information in the Console. Value: Value associated with this variable. Advanced settings Usage Limitation tStatCatcher Statistics This component can be used alone or as a sub-job along with another component. tGroovyFile broadens the functionaility of Talend Jobs using the Groovy language which is a simplified Java syntax. • In the Groovy File field. Scenario: Calling a file which contains Groovy code This scenario uses tGroovyFile.Custom Code components tGroovyFile tGroovyFile tGroovyFile Properties Component Family Custom Code Function Purpose Basic settings tGroovyFile allows you to call an existing Groovy script. enter the path to the file containing the Groovy code. This table contains two columns. • In the Variables table. add a line by clicking the [+] button. Name: Name of the variable called in the code. Below. on its own. is an example of the information displayed: • Open the Custom_Code folder in the Palette and drop a tGroovyFile component onto the workspace. Knowledge of the Groovy language is required. or browse to the file in youor directory. • Double-click the component to display the Component view.

enter “age”. as in the screenshot. • The Console displays the information contained in the input file. then in the Value column. • Press F6 to save and run the Job.Custom Code components tGroovyFile • In the Name column. to which the variable result is added. 158 Talend Open Studio Components Creative Commons License . enter 50.

• Select and drop the following components from the Palette onto the design workspace: tFileInputDelimited. Code Type in the Java code you want to execute according to the task you need to perform. tFileOutputExcel. You should know Java language. For further information about Java functions syntax specific to Talend. see Talend Open Studio online Help (Help Contents > Developer Guide > API Reference). The content from a delimited txt file will be passed on through the connection to an xls-type of file without further transformation. check http://java. You can execute this code only once. Creative Commons License Talend Open Studio Components 159 . Scenario: Printing out a variable content The following scenario is a simple demo of the extended application of the tJava component.Custom Code components tJava tJava tJava Properties Component family Custom Code Function Purpose Basic settings tJava enables you to enter personalized code in order to integrate it in Talend program. tJava. The Job aims at printing out the number of lines being processed using a Java command and the global variable provided in Talend Open Studio. For a complete Java reference.com/javaee/6/docs/api/ Usage Limitation This component is generally used as a one-component subjob. • Connect the tFileInputDelimited to the tFileOutputExcel using a Row Main connection.sun. tJava makes it possible to extend the functionalities of a Talend Job through using Java commands.

so that the tFileOutputExcel component gets automatically set with the input schema.Custom Code components tJava • Then connect the tFileInputDelimited component to the tJava component using a Then Run link. therefore you need to set manually the two-column schema • Click the Edit Schema button. • Set the Basic settings of the tFileInputDelimited component. • Set the output file to receive the input content without changes. 160 Talend Open Studio Components Creative Commons License . In this example. the Sheet name is Email and the Include Header box is selected. click OK to accept the propagation. • The schema has not been stored in the repository for this use case. The input file used in this example is a simple text file made of two columns: Names and their respective Emails. Therefore no need to set the schema again. If the file does not exist already. • When prompted. • Then select the tJava component to set the Java command to execute. This link sets a sequence ordering tJava to be executed at the end of the main process. it will get created.

press Ctrl + Space bar on your keyboard and select the relevant global parameter. Creative Commons License Talend Open Studio Components 161 . To access the global variable list. we use the NB_Line variable. System. type in the following command: String var = "Nb of line processed: ".out. var = var + globalMap.get("tFileInputDelimited_1_NB_LINE").println(var). • Save your Job and press F6 to execute it. In this use case. The content gets passed on to the Excel file defined and the Number of lines processed are displayed on the Run console.Custom Code components tJava • In the Code area.

Enter the Java code that helps to import. Note that if you make changes. Related topic: Setting a Repository schema of Talend Open Studio User Guide. hence can be reused.. it defines the number of fields to be processed and passed on to the next component. you can enter the three java-code parts (start. external libraries used in the Main code box of the Basic settings view. You can as well use it as a one-component subjob. main and end) that constitute a kind of component dedicated to do a desired operation. With tJavaFlex. Schema and Edit Schema A schema is a row description. When you select this check box. Repository: The schema already exists and is stored in the Repository.Custom Code components tJavaFlex tJavaFlex tJavaFlex properties Component family Custom Code Function tJavaFlex enables you to enter personalized code in order to integrate it in Talend program. tJava makes it possible to extend the functionalities of a Talend Job through using Java commands. Enter the Java code that will be called during the closing phase. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Objective Basic settings Start code Main code End code Advanced settings Import tStatCatcher Statistics Usage You can use this component as a start. Enter the Java code that will be called during the initialization phase. i.e. you can not later do any transformation on the retrieved data by setting Java commands in the Main code field. Enter the Java code to be applied for each line in the data flow. intermediate or output component. Select this check box to gather the job processing metadata at a job level as well as at each component level. Data Auto Propagate Select this check box to automatically propagate the data to the component that follows. 162 Talend Open Studio Components Creative Commons License . Click Edit Schema to make changes to the schema. Related topic: Setting a built-in schema of Talend Open Studio User Guide. the schema automatically becomes built-in. if necessary.

• From the Schema Type list. select Built-in and then click the three-dot button next to Edit schema to open the corresponding dialog box where you can define the data structure to pass to the component that follows. Scenario1: Generating data flow This scenario describes a two-components Job that generates a three-line data flow describing different personal titles (Miss. • Connect the components together using a Row Main link.Custom Code components tJavaFlex Limitation You should know the Java language. • Drop tJavaFlex and tLogRow from the Palette onto the design workspace. Mrs. and Mr) and displaying them on the console. • Double-click tJavaFlex to display its Basic settings view and define its properties. Creative Commons License Talend Open Studio Components 163 .

• In the Start code field.key = i.i<valueArray. • Save your Job and press F6 to execute it. you have to modify the code of this field accordingly.value = valueArray[i].Custom Code components tJavaFlex • Click the plus button to add two columns: key and value and then set their types to Integer and String respectively. for (int i=0. row1. • In the Basic settings view of tJavaFlex.println("## START\n#"). we do not want to do any transformation on the retrieved data.length. "Mrs". select the Data Auto Propagate check box to automatically propagate data to the component that follows. In this example. • If needed. we want to display each key with its value: row1.” row1” corresponds to the name of the link that comes out of tJavaFlex. "Mr"}. If you rename this link.out. enter the code that will be executed in the closing phase. 164 Talend Open Studio Components Creative Commons License . the brace (curly bracket) closes the loop and the code indicates the end of the execution of tJavaFlex by displaying the END message: } System.out. enter the code to be executed in the initialization phase. double-click tLogRow and in its Basic settings view. click the button next to Edit schema to make sure that the schema has been correctly propagated. • In the End code field. enter the code you want to apply on each of the data rows. In the Main code. In this example.println("#\n## END"). In this example. • Click Ok to validate your changes and close the dialog box. In this example.i++) { • In the Main code field. the code indicates the initialization of tJavaFlex by displaying the START message and sets up the loop and the variables to be used afterwards in the Java code: System. String [] valueArray = {"Miss".

txt. • Double-click tRowGenerator to display its Basic settings view and the [RowGenerator Editor] dialog box where you can define the component properties. date and flag.Custom Code components tJavaFlex The three personal titles are displayed on the console along with their corresponding keys. • Click the plus button to add four columns: number. • Define the schema and set the parameters to the four columns according to the above capture. • Connect the components together using a Row Main link. Creative Commons License Talend Open Studio Components 165 . • Drop tRowGenerator and tJavaFlex from the Palette onto the design workspace. Scenario2: Processing rows of data with tJavaFlex This scenario describes a two-component Job that generates random data and then collects that data and does some transformation on it line by line using Java code through the tJavaFlex component.

the code indicates the initialization of the tJavaFlex component by displaying the START message and defining the variable to be used afterwards in the Java code: System.print (" | txt:" + row1. we create a condition to show if the status is true or false and we increment the number of the line: System. enter 10 different parameters for each of the defined columns.out. • In the Start code field.Custom Code components tJavaFlex • In the Functions column.flag) System.out..date).print(" row" + i + ":"). • Click Sync columns to retrieve the schema from the preceding component. we want to show the number of each line starting from 0 and then the number and the random text transformed to upper case and finally the random date set in the editor of tRowGenerator. enter the code to be executed in the initialization phase.. System.print(" | date:" + row1.) for each of the defined columns. System. In this example. In this example.txt. i++.print("# number:" + row1. int i = 0.toUpperCase()). if(row1. • Click OK to validate your changes and close the editor.out. • Double-click tJavaFlex to display its Basic settings view and define the components properties. System. • In the Main code field.println("## START\n#"). • In the Parameters column. These 10 parameters corresponds to the data that will be randomly generated when executing tRowGenerator.out. 166 Talend Open Studio Components Creative Commons License . else System.println(" | flag: false").out. Then.println(" | flag: true").out.number). enter the code to be applied on each line of data. select the three-dot function (.out.

The console displays the randomly generated data that was modified by the java command set through tJavaFlex. you have to modify the code. • In the End code field. Creative Commons License Talend Open Studio Components 167 .println("#\n## END"). If you rename this link. “row1” corresponds to the name of the link that comes out of tJavaFlex.out. In this example. enter the code that will be executed in the closing phase. the code indicates the end of the execution of tJavaFlex by displaying the END message: System. • Save your Job and press F6 to execute it.Custom Code components tJavaFlex In the Main code filed.

Custom Code components tJavaRow tJavaRow Propriétés du tJavaRow Component Family Custom Code Function tJavaRow allows you to enter customized code which you can integrate in a Talend programme. Related topic: Setting a Repository schema of Talend Open Studio User Guide Code Enter the Java code to be applied to each line of the data flow... The schema is either built-in or remotely stored in the Repository. tJavaRow allows you to broaden the functionality of Talend jobs. Knowledge of Java language is necessary. It must be linked to both an input and an output component. it defines the number of fields to be processed and passed on to the next component. With tJavaRow. hence can be reused. the schema automatically becomes built-in. Enter the Java code required to import. Purpose Basic settings Advanced settings Import tStatCatcher Statistics Usage This component is used as an intermediary between two other components. Repository: The schema already exists and is stored in the Repository. using the Java language. Schema and Edit Schema A schema is a row description. Related topic: Setting a built-in schema in the Talend Open Studio User Guide. you can enter the Java code to be applied to each row of the flow. the external library used in the Main code field of the Basic settings tab. Note that if you make changes.. Limitation Related scenario No scenario is available for this component yet. Click Edit Schema to make changes to the schema. Built-in: The schema is created and stored locally for this component only.. i.e. Select this check box to collect the log data at a component level. if required. 168 Talend Open Studio Components Creative Commons License .

Enter the Java code required to import. or click on the [. • In the Palette. Library Select the library you want to import from the list.Custom Code components tLibraryLoad tLibraryLoad tLibraryLoad Properties Famille de composant Custom Code Function Purpose Basic settings tLibraryLoad allows you to import a library. between double quotation marks. and slide a tLibraryLoad and tJava component onto the workspace. Lib Paths: Enter the access path to your library. if required. n/a Scenario: Checking the format of an e-mail addressl This scenario uses two components. Select this check box to collect the log data at component level. a tLibraryLoad and a tJava. the external library used in the Main code field of the Basic settings tab. The goal of this scenario is to check the format of an e-mail address and verify whether the format is valid or not.. Advanced settings Dynamic Libs Import tStatCatcher Statistics Utilisation Limitation This component may be used alone.. although it is more logical to use it as part of a Job. Creative Commons License Talend Open Studio Components 169 . open the Custom_Code folder.] button to browse to the library in your directory. tLibraryLoad allows you to load useable Java libraries in a Job. • Connect tLibraryLoad to tJava using a Trigger > OnSubjobOk link.

• Press F6 to save and run the Job.jar.Custom Code components tLibraryLoad • Double click on tLibraryLoad to display its Basic settings.regex.0.text.-]+@[\\w_. The code allows you to check whether the character string pertains to an e-mail address.oro.[\\w]+$".-]+\\. enter your code. • In the Basic settings tab. From the Library list.apache. based on the regular expression: "^[\\w_. type import org. • In the Import field of the Advanced settings tab. 170 Talend Open Studio Components Creative Commons License .8. select jakarta-oro-2. • Double click on tJava to display its Component view.*. as in the screenshot below.

Creative Commons License Talend Open Studio Components 171 .Custom Code components tLibraryLoad The Console displayes the boolean false. the e-mail address is not valid as the format is incorrect. Hence.

• Drop three components from the Palette onto the design workspace: tFileInputDelimited. • Right-click again tFileInputDelimited and link it to tPerl using a Trigger > OnSubjobOk link. 172 Talend Open Studio Components Creative Commons License . tPerl • Right-click tFileInputDelimited and connect it to tFileOutputExcel using a main Row. This link means that. Code Type in the Perl code based on the command and task you need to perform. following the arrow direction. This component requires an advanced Perl user level and is not meant to be used with a Row connection as is meant for single use. tPerl is an (Perl) editor that is a very flexible tool within a job. Advanced settings tStatCatcher Statistics Usage Limitation Typically used for debugging but can also be used to display a variable content.Custom Code components tPerl tPerl tPerl properties Component family Processing Function Purpose Basic settings tPerl transforms any data entered as argument of Perl commands. For further information about Perl functions syntax. see Talend Open Studio online Help (under Talend Open Studio User Guide > Perl) Select this check box to gather the job processing metadata at a job level as well as at each component level. Scenario: Displaying a number of processed lines This scenario is a three-component job showing in the Log the number of rows being processed and output in an XML file. tFileOutputExcel. the first component (tFileDelimited) will run before the second component (tPerl).

Click on Edit Schema and describe the content of the input file. • The Schema type is also built-in in this case. there is one name and the matching email per row. • Select the tFileOutputExcel component and define it accordingly. Creative Commons License Talend Open Studio Components 173 . • The Properties are not reused from or for another job stored in the repository. the text file gathers a list of names facing the relevant email addresses. • Define the Row and Field separators. • Enter a path or browse to the file containing the data to be processed. Therefore the Header field value is 1. In this example. • Then define the tPerl sub-job in order to get the number of rows transferred to the XML Output file.Custom Code components tPerl • Click once on tFileInputDelimited and select the Basic settings tab to define the component properties. And the fields are separated by a semi-colon. In this scenario. Sheet and synchronize the schema. of type String and with no length defined. • There is no footer nor limit value to be defined for this scenario. Key field being Email. but instead are used for this job only. • The first row of the file contains the labels of the columns. there are two columns labelled Name and Emails. Therefore select Built-In in the drop-down list. In this scenario. • Select the output file path. therefore it should be ignored in the job.

Note also that commands. The job runs smoothly and create an output xml file following the two-field schema defined: Name and Email. • Then switch to the Run Job tab and execute the job. press Ctrl+Space then select the relevant variable in the list. To access the list of available variables. The Perl command result is shown in the job log. 174 Talend Open Studio Components Creative Commons License . • For a better readability in the Run Job log. strings and variables are colored differently. add equal signs before and after the commands.Custom Code components tPerl • Enter the Perl command print to get the variable containing the number of rows read in tFileInputDelimited.

. The Data Quality family comprises dedicated components that help you improve the quality of your data.Data Quality components This chapter details the main components that you can find in the Data Quality family of the Talend Open Studio Palette. finding data based on fuzzy matching. and so on. calculating CRC. These components covers various needs such as narrow down filtering the unique row.

n/a Scenario: Adding a surrogate key to a file This scenario describes a Job adding a surrogate key to a delimited file schema. it defines the number of fields that will be processed and passed on to the next component. Schema and Edit Schema A schema is a row description.e.. • Connect them using a Main row connection. 176 Talend Open Studio Components Creative Commons License . a new CRC column is automatically added. hence can be reused in various projects and job designs. i. The longer the CRC. tAddCRCRow and tLogRow. Providing a unique ID helps improving the quality of processed data. Related topic: Setting a Repository schema of Talend Open Studio User Guide.Data Quality components tAddCRCRow tAddCRCRow tAddCRCRow properties Component family Data Quality Function Purpose Basic settings tAddCRCRow calculates a surrogate key based on one or several columns and adds it to the defined schema. Select this check box to collect log data at the component level. Built-in: The schema will be created and stored locally for this component only. Advanced Settings CRC type tStatCatcher Statistics Usage Limitation This component is an intermediary step. It requires an input flow as well as an output. The schema is either built-in or remote in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. • Drop the following components: tFileInputDelimited. Implication Select the check box facing the relevant columns to be used for the surrogate key checksum. the least overlap you will have. Select a CRC type in the list. Repository: The schema already exists and is stored in the Repository. In this component.

select the check boxes of the input flow columns to be used to calculate the CRC. set the File Name path and all related properties in case these are not stored in the Repository.html. • In the tAddCRCRow Component view. • Select CRC32 as CRC Type to get a longer surrogate key. In Java. check out http://java. in case the schema is not stored already in the Repository.5. Creative Commons License Talend Open Studio Components 177 . mind the data type column and in case of Date pattern to be filled in. select the Print values in cells of a table check box to display the output data in a table on the Console.0/docs/api/index. • In the Basic settings view of tLogRow. • Then save your Job and press F6 to execute it. • Create the schema through the Edit Schema button.Data Quality components tAddCRCRow • In the tFileInputDelimited Component view.com/j2se/1.sun. • Notice that a CRC column (read-only) has been added at the end of the schema.

178 Talend Open Studio Components Creative Commons License .Data Quality components tAddCRCRow An additional CRC Column has been added to the schema calculated on all previously selected columns (in this case all columns of the schema).

Creative Commons License Talend Open Studio Components 179 .Data Quality components tExtractRegexFields tExtractRegexFields tExtractRegexFields belongs to two component families: Data Quality and Processing. see tExtractRegexFields on page 1128. For more information on tExtractRegexFields.

Schema and Edit Schema A schema is a row description. It can return both a primary and a secondary code for a string. hence can be reused in various projects and job designs. that produces more accurate results than the original algorithm. it defines the number of fields that will be processed and passed on to the next component.Data Quality components tFuzzyMatch tFuzzyMatch tFuzzyMatch properties Component family Data Quality Function Purpose Basic settings Compares a column from the main flow with a reference column from the lookup flow and outputs the main flow data displaying the distance Helps ensuring the data quality of any source data against a reference data source. i.. (Levenshtein only) Set the maximum number of changes allowed to match the reference.e. Built-in: The schema will be created and stored locally for this component only. Metaphone: Based on a phonetic algorithm for indexing entries by their pronunciation. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Value and Match are added to the output schema automatically. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This accounts for some ambiguous cases as well as for multiple variants of surnames with common ancestry. Min Distance Max Distance 180 Talend Open Studio Components Creative Commons License . (Levenshtein only) Set the minimum number of changes allowed to match the reference. Double Metaphone: a new version of the Metaphone phonetic algorithm. It first loads the phonetics of all entries of the lookup reference and checks all entries of the main flow against the entries of the reference flow. only perfect matches are returned. It calculates the number of insertion. Two read-only columns. Matching type Select the relevant matching algorithm among: Levenshtein: Based on the edit distance theory. deletion or substitution required for an entry to match the reference entry. The schema is either built-in or remote in the Repository. If set to 0.

in case several matches are available. • Define the second tFileInputDelimited component the same way. tFileOutputDelimited. Unique Matching Matching item separator Usage This component is not startable (green background) and it requires two input components and an output component. Check the Module view for modules to be installed Scenario 1: Levenshtein distance of 0 in first names This scenario describes a four-component Job aiming at checking the edit distance between the First Name column of an input file with the data of the reference input file. all of them are displayed unless the unique match box is selected. Define the delimiter between all matches. • In the schema. In case several matches are available.Data Quality components tFuzzyMatch Matching Column Select the column of the main flow that needs to be checked against the reference (lookup) key column Select this check box if you want to get the best match possible. Browse the system to the input file to be analyzed and most importantly set the schema to be used for the flow to be checked. especially if you are in Built-in mode. Limitation/prerequisite Perl users: Make sure the relevant packages are installed. set the Type of data in the Java version. tFuzzyMatch. • Link the defined input to the tFuzzyMatch using a Main row link. • Define the first tFileInputDelimited Basic settings. Make sure the reference column is set as key column in the schema of the lookup flow. The output of this Levenshtein type check is displayed along with the content of the main flow on a table • Drag and drop the following components from the Palette to the design workspace: tFileInputDelimited (x2). Creative Commons License Talend Open Studio Components 181 .

No other parameters than the display delimiter is to be set for this scenario. • Select the method to be used to check the incoming data. clear the Case sensitive check box. In this example. • In this use case.Data Quality components tFuzzyMatch • Then connect the second input component to the tFuzzyMatch using a main row (which displays as a Lookup row on the design workspace). we want the distance be of 0 for the min. • The Schema should match the Main input flow schema in order for the main flow to be checked against the reference. These are standard matching information and are read-only. the distance is the number of char changes (insertion. • Also. This means only the exact matches will be output. the first name. • Note that two columns. 182 Talend Open Studio Components Creative Commons License . • And select the column of the main flow schema that will be selected. In this method. Value and Matching. • Then set the distance. • No need to select the Unique matching check box nor hence the separator. or for the max. • Select the tFuzzyMatch Basic settings. deletion or substitution) that needs to be carried out in order for the entry to fully match the reference. Levenshtein is the Matching type to be used. are added to the output schema. In this scenario. • Link the tFuzzyMatch to the standard output tLogRow.

hence only full matches with Value of 0 are displayed. • In the Component view of the tFuzzyMatch. A more obvious example is with a minimum distance of 1 and a max. This excludes straight away the exact matches (which would show a distance of 0). As the edit distance has been set to 0 (min and max). • No other change of the setting is required. • Change also the max distance to 2 as the max distance cannot be lower than the min distance. which will change the output displayed. The output will provide all matching entries showing a discrepancy of 2 characters at most. Creative Commons License Talend Open Studio Components 183 . Only the min and max distance settings in tFuzzyMatch component get modified. • Make sure the Matching item separator is defined. see Scenario 2: Levenshtein distance of 1 or 2 in first names on page 183. the output shows the result of a regular join between the main flow and the lookup (reference) flow. Scenario 2: Levenshtein distance of 1 or 2 in first names This scenario is based on the scenario 1 described above. change the min distance from 0 to 1. • Save the new Job and press F6 to run it.Data Quality components tFuzzyMatch • Save the Job and press F6 to execute the Job. as several references might be matching the main flow entry. distance of 2.

• Change the Matching type to Metaphone. • Save the Job and press F6. There is no min nor max distance to set as the matching method is based on the discrepancies with the phonetics of the reference. The phonetics value is displayed along with the possible matches. Scenario 3: Metaphonic distance in first name This scenario is based on the scenario 1 described above.Data Quality components tFuzzyMatch As the edit distance has been set to 2. to assess the distance between the main flow and the reference. You can also use another method. the metaphone. some entries of the main flow match several reference entries. 184 Talend Open Studio Components Creative Commons License .

the schema automatically becomes built-in. Select the column containing the max value of the tange. hence is defined as an intermediary step. they are described in a separate table below.e. i. Built-in: The schema will be created and stored locally for this component only. Click Edit Schema to make changes to the schema. The schema is either built-in or remote in the Repository. Note that if you make changes.Data Quality components tIntervalMatch tIntervalMatch tIntervalMatch properties Component family Data Quality Function tIntervalMatch receives a main flow and aggregates it based on join to a lookup flow (Java) or a given lookup file (Perl).. Select the check box if the boundary is strict. Lookup Column min/ bounds strictly (min) Lookup Column max/ bounds strictly (max) Usage Limitation Select the column containing the min value of the tange. Schema and Edit Schema A schema is a row description. PERL basic settings Creative Commons License Talend Open Studio Components 185 . Java only Search column Select the main flow column containing the values to be matched to a range of values Purpose Basic settings Column (LOOKUP) Select the lookup flow column containing the values to be returned when the Join is ok. Then it matches a specified value to a range of values and returns related information. n/a The Perl properties being quite different from the Java properties. This component handles flow of data therefore it requires input and output. hence can be reused in various projects and job flowcharts. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Select the check box if the boundary is strict. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. it defines the number of fields that will be processed and passed on to the next component. Helps to return a value based on a Join relation.

Character. hence is defined as an intermediary step. A second file used as lookup flow in Java and reference range file in Perl contains a list of sorted IP ranges and their corresponding country. hence can be reused in various projects and job flowcharts. etc. Perl only File Name Field separator Row separator Lookup index Column Enter the file that contains the range of values. in other words. Note that if you make changes. Perl and Java. a tIntervalMatch and a tLogRow. The schema is either built-in or remote in the Repository. string or regular expression to separate fields in the lookup file. it defines the number of fields that will be processed and passed on to the next component. It functions as a lookup flow. a incoming main flow provides 2 columns: Documents and IP dummy values. In this Job. Make sure the interval min and max columns are adjacent. This Job aims at retrieving each document’s country from their IP value. 1 for second col. Built-in: The schema will be created and stored locally for this component only. i. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Position of the min column in the lookup file: 0 for first col.Data Quality components tIntervalMatch Basic settings Schema and Edit Schema A schema is a row description.e. 186 Talend Open Studio Components Creative Commons License . Related topic: Setting a Repository schema of Talend Open Studio User Guide.. Click Edit Schema to make changes to the schema. the Job requires one tFileInputDelimited. the schema automatically becomes built-in. Select the main flow column containing the values to be matched to a range of values Search column Usage Limitation This component handles flow of data therefore it requires input and output. In Perl. For the time being. Repository: The schema already exists and is stored in the Repository. the Perl version of the tIntervalMatch does not accept a real Lookup flow (but only a reference file in the actual component’s settings) Scenario: Identifying Ip country (Perl and Java) The following scenario describes a Job designed in parallel in both languages. String (ex: “\n”on Unix) to distinguish rows in the lookup file. creating a Join between the main flow and the lookup flow.

• The schema is made of two columns. • (Java only) Don’t forget to define the Type of data. the Job requires one extra tFileInputDelimited. • (Both Java and Perl) Propagate the schema from the incoming main flow to the tIntervalMatch component. • Drop the components onto the design workspace. Creative Commons License Talend Open Studio Components 187 . a tIntervalMatch and a tLogRow.Data Quality components tIntervalMatch In Java. • Set the basic settings of the tFileInputDelimited component. respectively Document and IP • (Java only) Set the Type column on String for the Document column and Integer for the IP column. • (Java only) Set now the second tFileInputDelimited properties.

Set the Row and Field separator of the lookup file. • (Perl only) In Lookup column index field. • (Both Java and Perl) In the Search column field. the lookup file is defined directly in the setting of the tIntervalMatch. • (Perl only) In File Name field. • Set the other properties of the tIntervalMatch component. select the column where are the values to be returned. • (Java only) In the Column Lookup field. • (Perl only).Data Quality components tIntervalMatch • (Both Java and Perl) Note that the output schema from the tIntervalMatch component is read-only and is made of the input schema plus an extra Lookup column which will output the requested lookup data. set the inferior bound of the data range. • (Java only) Set the tIntervalMatch other properties such as the min and max column corresponding to the range bounds. • (Perl only) No need to set the lookup values to be returned as all values from the lookup will be outputted. select the main flow column containing the values to be matched to the range values. set the path to the lookup file. 188 Talend Open Studio Components Creative Commons License . This corresponds to the position of the column containing the min value of the range (0 for the first column).

Creative Commons License Talend Open Studio Components 189 . Both Perl and Java Jobs output the same result with slight differences in the way they display. The Perl results include the range values whereas the Java output only includes the requested return value (country).Data Quality components tIntervalMatch • (Both Java and Perl) The tLogRow component does not require any specific setting for this Job.

Select this check box to authorize only abbreviated region names. it will not be modified.e. Advanced settings Correct case Auto clean Abbreviate subcountry Allow only abbreviated subcountry tStatCatcher Statistics Usage Limitation This component acts as an intermediary. Data processing will be faster and will check that the address matches postal standards. Select this check box in order to correct the case. Repository: You have already created the schema and stored it in the Repository. it defines the number of fields that will be processed and passed on to the next component. n/a 190 Talend Open Studio Components Creative Commons License . if required. You can reuse it in various projects and job designs. Select this check box to collect log data for the job as a whole. i. Built-in: You create the schema and store it locally for this component only. For example. The schema is either built-in or remote in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide.Data Quality components tParseAddress tParseAddress tParseAddress properties Component Family Data Quality Function Purpose Basic settings This component analyses addresses in a defined schema column and parses them into different field types. Column to parse Country Select the column in which you want to analyze and parse data. Select this check box to automatically abbreviate region names. Cut data in several columns to sort the different parts. to put a capital letter at the beginning of a name. as well as for each component. It requires an input and an output flow. Select this check box to delete the non-alphanumerical characters before trying to parse addresses. Schema and Edit Schema A schema is a row description. Select the customers’ country. Related topic: Setting a Repository schema of Talend Open Studio User Guide.. in order to improve your data quality. If the name is already abbreviated.

Creative Commons License Talend Open Studio Components 191 .Data Quality components tParseAddress Related scenario No scenario is available for this component yet.

Select this check box to delete the non-alphanumerical characters before trying to parse addresses. Related topic: Setting a built-in schema of Talend Open Studio User Guide. The schema is either built-in or remote in the Repository. Note that if the name can be analyzed. i. Mr AB -> Mr AB Smith Extend titles Correct case Auto clean tStatCatcher Statistics 192 Talend Open Studio Components Creative Commons License . Select this check box to collect log data for the job as a whole.Data Quality components tParseName tParseName tParseName Properties Component Family Data Quality Function Purpose This component retrieves names presented in different forms and extracts each item according to its type. Repository: You have already created the schema and stored it in the Repository. Select this check box to ignore data containing joint names. to put a capital letter at the beginning of a name. If you deselect it. The component puts the names in order and performs the normal analysis. You can reuse it in various projects and job designs. as well as for each component. Select this check box in order to correct the case. Select this check box so that names will be processed regardless of the form they are presented in. It also rejects the incorrect items. Column to parse Select the column from which you want to extract the different items. in order to improve the quality of the processed data.e. its original order is not saved as a property. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Smith. if needed. Mr John Smith and Ms Mary Jones -> Mr John Smith Allow reversed. Basic settings Advanced settings Ignore joint names.. Deselect it in order to return and cut this data by type. Built-in: You create the schema and store it locally for this component only. The tParseName analyses a file containing names and extracts items according to their type. This will make the data processing faster. that is to say. Schema and Edit Schema A schema is a row description. you can only use “standard” titles. it defines the number of fields that will be processed and passed on to the next component. Select this check box to use all possible titles.

It requires an input and an output flow. n/a Related scenario No scenario is available for this component yet. Creative Commons License Talend Open Studio Components 193 .Data Quality components tParseName Usage Limitation This component acts as an intermediary.

This component is not startable as it requires an input flow. Built-in: The schema will be created and stored locally for this component only. 0: first column read 1: second column read n: position number of the column in the schema read. Lookup replacement Type in the position number of the column where column the replacement values are stored. Two read-only columns.. Schema and Edit Schema A schema is a row description. And it requires an output component. Lookup search column Type in the position number of the column to be searched in the lookup schema. 194 Talend Open Studio Components Creative Commons License . Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. In order to ensure the uniqueness of values being searched. make sure this column is marked as Key in your lookup schema. 0: first column read 1: second column read n: position number of the column in the schema read Column options Usage Select the columns of the main flow where the replacement is to be carried out. Value and Match are added to the output schema automatically. it defines the number of fields that will be processed and passed on to the next component.Data Quality components tReplaceList tReplaceList tReplaceList Properties Component family Data Quality Function Purpose Basic settings Carries out a Search & Replace operation in the input columns defined based on an external lookup. hence can be reused in various projects and job designs. Helps to cleanse all files before further processing. The schema is either built-in or remote in the Repository. i. Repository: The schema already exists and is stored in the Repository.e.

• The input schema is made of two columns: Names. tFileInputDelimited. tReplicate. • Select the tMysqlInput component and set the input flow parameters. • Drop the following components from the Palette to the design workspace: tMysqlInput. The column States gathered the name of the United States of America which are to be replaced by their respective code. States. in order to show the main flow before and after replacement. Note that if your input schemas are stored in the Repository. see Dropping components from the Metadata node in Talend Open Studio User Guide. For more information. The main flow is replicated and both outputs are displayed on the console.Data Quality components tReplaceList Scenario: Replacement from a reference file The following Job searches and replaces a list of countries with their corresponding codes. tReplaceList and tLogRow (x2). • Connect the components using Main Row connections via a right-click on each component. you can simply drag and drop the relevant node from the Repository’s Metadata Manager onto the design workspace to retrieve automatically the input components’ setting. Creative Commons License Talend Open Studio Components 195 . Notice that the main row coming from the reference flow (tFileInputDelimited) is called a lookup row. The relevant codes are taken from a reference file placed as lookup flow in the Job.

• The file includes two columns: Postal. State is the second column of the lookup input file. all columns are selected. make sure the State column is included in the Select statement. In this use case. • Check the tReplicate component setting. • In Lookup search index field. • Edit the lookup flow schema. type in the position index of the column being searched. • Make sure the lookup search column (in this use case: State) is a key. therefore type in 1 in this field. in order to ensure the uniqueness of the values being searched. • The schema is retrieved from the previous component of the main flow. • Then double-click on the tFileInputDelimited component. 196 Talend Open Studio Components Creative Commons License . The schema is simply duplicated into two identical flows. • The fields are delimited by semicolons and rows are separated by carriage returns. In this use case. State where Postal provides the zipcode corresponding to the name given in the respective row of the State column. to set the reference file. but no change to the schema can be made. • Select the tReplaceList and set the operation to carry out.Data Quality components tReplaceList • In the Query field.

• In both tLogRow components.Data Quality components tReplaceList • In Lookup replacement index field. The first flow output shows the State column with full state names as it comes from the main input flow. • In the Column options table. • Save the Job and press F6 to execute it. select the States column as in this use case. Creative Commons License Talend Open Studio Components 197 . the State names are to be replaced with their corresponding code. select the Print values in table cells check box for a better readability of the outputs. in this example: Postal for the State codes. The second flow output shows the States column after the State column names have been replaced with their respective codes. fill in the position number of the column containing the replacement values.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. Java only Use another schema for compliance check Date language/ Date format Define a reference schema as you expect the data to be. For the validation of date formats containing string such as 25 Dec 2007. In Perl. Base Schema and Edit Schema A schema is a row description. Select this check box to verify the data length against the base schema length definition Perl only Check all columns from schema Type Null (empty or zero) Max length Usage This component is an intermediary step in the flow allowing to exclude from the main flow the non-compliant data. and possibly a second output component for rejected data using Rejects link. select the type of which the data should be. hence can be reused in various projects and job designs. The schema is either built-in or remote in the Repository. null values. Related topic: Setting a built-in schema of Talend Open Studio User Guide.. nullability. Repository: The schema already exists and is stored in the Repository. Built-in: The schema will be created and stored locally for this component only. In Java. length of rows against reference values. For more information. 198 Talend Open Studio Components Creative Commons License .Data Quality components tSchemaComplianceCheck tSchemaComplianceCheck tSchemaComplianceCheck Properties Component family Data Quality Function Purpose Basic settings Validates all input rows against a reference schema or checks type. select the check box of the column of which you want the data type to be verified against the base schema definition. Select this check box if all checks are to be carried out on all columns of the base schema. This validation is mandatory for all columns. use the Date Language field and to distinguish the way months and days are ordered. Helps ensuring the data quality of any source data against a reference data source. It can be restrictive on data type. and/or length. it defines the number of fields that will be processed and passed on to the next component. This component cannot be a start component as it requires an input flow. Describe the structure and nature of your data to be processed as it is. in order to reject the non-compliant data. Select this check box to verify the nullability of the column against the base schema definition. It also requires at least one output component to gather the validated flow. The validation can be carried out in full or partly. see Rejects in Talend Open Studio User Guide.e. use the Date format field. i.

• Right-click again on the tSchemaComplianceCheck component and. tLogRow from the Palette to the design workspace. Creative Commons License Talend Open Studio Components 199 . This output flow will gather the valid data. data exceeding max length. wrong id and null values in non-nullable columns. This second output flow will gather the non-compliant data. tSchemaComplianceCheck. The output is double as the valid data are gathered into a dedicated delimited file. whereas the rejected data are displayed on the console. and notice that the schema passed through to the tLogRow contains already two columns: ErrorCode and ErrorMessage. • Now define the properties of each component. tFileOutputDelimited. These two column are read-only and provides information about the rejected data. • Then right-click on the tSchemaComplianceCheck component and select Row > Main to connect it to the tFileOutputDelimited. null value and length of an incoming flow against a defined reference schema. The incoming flow comes from a simple csv file which contains heterogeneous data including wrong data type. • Right-click on the tFileInputDelimited to connect it to the tSchemaComplianceCheck using a row main link. • Drop the following components: tFileInputDelimited. this time. • Select the Rejects link that you just connected. easing the error handling and troubleshooting if need be.Data Quality components tSchemaComplianceCheck Scenario: Validating dates against schema (java) This very basic scenario shows how to check the type. select Row > Rejects link to connect it to the tLogRow component.

You will define the actual type of the data on the tSchemaComplianceCheck Component view. • The Str_nullable column is the only nullable data. Col2Label. 200 Talend Open Studio Components Creative Commons License . and fill in the File Name browsing to the input file. • Leave the Type field as permissive as possible (especially in Java). The schema is made of six columns: id. So select the relevant check box. Date. Val and Str_Nullable. In this example: in. • Then double-click on tSchemaComplianceCheck component to set the validation parameters.Data Quality components tSchemaComplianceCheck • On the Component view of the tFileInputDelimited component.csv • Click Edit Schema to describe the data structure of this input file. leave the default parameters for a delimited file. Col3Label. Col2Label and Col3Label are length-limited to respectively 30 and 40 characters.

select the Statistics check box to display the flow dispatching rates before launching the execution. set the checks to be performed.Data Quality components tSchemaComplianceCheck • The Base schema should be automatically propagated from the input component. select the relevant Type check boxes for the columns which the type needs to be selected (Date). • Select the Check all columns from schema check box if you want to check all the columns against all parameters (type. Below is the setting for a job designed in Talend Open Studio with Java generation language: .The Val column should be checked for null values (as it should not be null).The Str_nullable should be checked for null values also (but it can be null).The Id type should be Int.The Col2Label and Col3Label should be checked for their Length . But you could also select the Use another schema for compliance check check box and define the schema description of the expected data. define the Date format and Date language. • The schema is propagated automatically from the tSchemaComplianceCheck to the output components. null values and length). Also. click on the Sync columns button. • In this example. • In Perl.The Date should of type Date . If not. we use the Checked columns table to set the validation parameters. Creative Commons License Talend Open Studio Components 201 . • Define the output file path on the tFileOutputDelimited properties. • On the Checked Columns table. • Then set the output components parameters. . . • Then on the Run tab.

202 Talend Open Studio Components Creative Commons License . • Also seven rows were not compliant with the reference schema. You can notice that the extra output columns in the Rejects link provide the error code as well as an error message such as: 2|Date:Date format not valid or 2|id:wrong type in order to ease the identification of the error. and therefore were directed to the console.Data Quality components tSchemaComplianceCheck • You can notice that three rows from the input flow were validated and therefore were directed to the tFileOutputDelimited.

the schema automatically becomes built-in. Repository: The schema already exists and is stored in the Repository. Note that if you make changes. Creative Commons License Talend Open Studio Components 203 . Schema and Edit Schema A schema is a row description. as the input data is randomly created. duplication cannot be avoided. Ensures data quality of input or output flow in a Job. it defines the number of fields that will be processed and passed on to the next component.. define them on the schema.Data Quality components tUniqRow tUniqRow tUniqRow Properties Component family Data Quality Function Purpose Basic settings Compares entries and removes the first encountered duplicate from the input flow. if you want the deduplication to be carried out on particular columns. n/a Scenario: Unduplicating entries Based on the tSortRow job. Click Sync columns to retrieve the schema from the previous component connected in the Job. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Case sensitive Select this check box to consider the lower or upper case. Built-in: The schema will be created and stored locally for this component only.e. In fact. i. The schema is either built-in or remote in the Repository. hence can be reused in various projects and job flowcharts. Click Edit Schema to make changes to the schema. the tUniqRow component is added to the Job in order to have unique entries in the output flow. Usage Limitation This component handles flow of data therefore it requires input and output. hence is defined as an intermediary step. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

The console displays the sorted and unique results 204 Talend Open Studio Components Creative Commons License . to set the Key on Names field to have unique entries in the output flow on this criteria. • Press F6 to run the Job again.Data Quality components tUniqRow • On the Basic settings tab panel of the tUniqRow component.. click Edit Schema. • Select the Case Sensitive check box to differentiate lower case and upper case..

reading and writing tables. committing transactions as a whole.Databases components This chapter details the main components which you can find in the Databases family of the Talend Open Studio Palette. The Databases family comprises the most popular database connectors. . More than 40 RDBMS are supported. as well as performing rollback for error handling. including: opening connection. These connectors cover various needs.

e. Built-in: The schema is created and stored locally for this component only. i. A schema is a row description. Repository: The schema already exists and is stored in the Repository. Trim all the String/Char columns Trim column 206 Talend Open Studio Components Creative Commons License .. Basic settings Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. see Setting up a DB connection of Talend Open Studio User Guide. Repository: Select the repository file where Properties are stored. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. This field is compulsory for DB data handling. The fields that come after are pre-filled in using the fetched data. hence can be reused. Select this check box to remove leading and trailing whitespace from all the String/Char columns. The schema is either built-in or remotely stored in the Repository. tAccessInput executes a DB query with a strictly defined statement which must correspond to the schema definition. Database Username and Password Schema and Edit Schema Name of the database DB user authentication data. Remove leading and trailing whitespace from defined columns. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Then it passes on the field list to the next component via a Main row link. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Property type Either Built-in or Repository Built-in: No property data stored centrally. For more information about setting up and storing database connection parameters.Databases components tAccessInput tAccessInput tAccessInput properties Component family Databases/Access Function Purpose tAccessInput reads a database and extracts fields based on a query.

Related scenarios For related topic. Creative Commons License Talend Open Studio Components 207 . Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in description of tContextLoad on page 1048.Databases components tAccessInput tStatCatcher Statistics Select this check box to collect log data at the component level.

Databases components tAccessOutput tAccessOutput tAccessOutput properties Component family Databases/Access Function Purpose tAccessOutput writes. The fields that come after are pre-filled in using the fetched data. updates. Repository: Select the repository file where Properties are stored. Note that only one table can be written at a time On the table defined. Name of the table to be written. tAccessOutput executes the action defined on the table and/or on the data contained in the table. Create a table if not exists: The table is created if it does not exist. Database Username and Password Table Action on table Name of the database DB user authentication data. you can perform one of the following operations: None: No operation is carried out. Basic settings 208 Talend Open Studio Components Creative Commons License . Built-in: No property data stored centrally. see Setting up a DB connection of Talend Open Studio User Guide. Drop and create a table: The table is removed and created again. Create a table: The table does not exist and gets created. Property type Either Built-in or Repository. Drop a table if exists and create: The table is removed if it already exists and created again. For more information about setting up and storing database connection parameters. Clear a table: The table content is deleted. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. based on the flow incoming from the preceding component in the Job. makes changes or suppresses entries in a database.

click the Advanced settings view where you can simultaneously define primary keys for the update and delete operations. Insert or update: Add entries or update existing ones. Die on error This check box is selected by default. Repository: The schema already exists and is stored in the Repository. If duplicates are found. You must specify at least one column as a primary key on which the Update and Delete operations are based. i. Job stops. Built-in: The schema is created and stored locally for this component only.e.. select the check boxes next to the column name on which you want to base the update operation. This option ensures transaction quality (but not rollback) and. above all. or action that require particular preprocessing. This option allows you to call SQL functions to perform actions on columns. If needed. To do that: Select the Use field options check box and then in the Key in update column. hence can be reused. This field is compulsory for DB data handling. you can retrieve the rows on error via a Row > Rejects link. This option is not offered if you create (with or without drop) the DB table. Schema and Edit Schema A schema is a row description.Databases components tAccessOutput Action on data On the data of the table defined. The schema is either built-in or remotely stored in the Repository. which are not insert. Clear the check box to skip the row on error and complete the process for error-free rows. you can perform: Insert: Add new entries to the table. Delete: Remove entries corresponding to the input flow. Update or insert: Update existing entries or create it if non existing. Do the same in the Key in delete column for the deletion operation. Number of rows to be completed before committing batches of rows together into the DB. Advanced settings Encoding Type Commit every Additional Columns Creative Commons License Talend Open Studio Components 209 . For an advanced use. Select the encoding type from the list or select Custom and define it manually. it defines the number of fields to be processed and passed on to the next component. better performance at executions. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Update: Make changes to existing entries. nor update or delete actions. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Select this check box to display each step during processing entries in a database. It allows you to carry out actions on a table or on the data of a table in a Access database. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. especially when there is double action on data.Databases components tAccessOutput Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. It also allows you to create a reject flow using a Row > Rejects link to filSchemaSchemater data in error. Use field options Enable debug mode Select this check box to customize a request. 210 Talend Open Studio Components Creative Commons License . tStatCatcher Statistics Select this check box to collect log data at the component level. Replace or After following the action to be performed on the reference column. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. This component must be used as an output component. For an example of tMySqlOutput in use. Position: Select Before. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

Related topic: Setting a built-in schema of Talend Open Studio User Guide. The fields that come after are pre-filled in using the fetched data. The schema is either built-in or remotely stored in the Repository. Repository: Select the repository file where Properties are stored. The SQLBuilder tool helps you write easily your SQL statements. Property type Either Built-in or Repository. Number of rows to be completed before committing batches of rows together into the DB. Purpose Basic settings Commit every Creative Commons License Talend Open Studio Components 211 . Repository: The schema already exists and is stored in the Repository.Databases components tAccessRow tAccessRow tAccessRow properties Component family Databases/Access Function tAccessRow is the specific component for this database query. Built-in: The schema is created and stored locally for this component only. The Query field gets accordingly filled in.e. It executes the SQL query stated onto the specified database.. Query type Either Built-in or Repository. DB Version Database Username and Password Schema and Edit Schema Select the Access database version that you are using. i. Depending on the nature of the query and the database. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Built-in: No property data stored centrally. it defines the number of fields to be processed and passed on to the next component. A schema is a row description. This option ensures transaction quality (but not rollback) and above all better performance on executions. hence can be reused. tAccessRow acts on the actual DB structure or on the data (although without handling data). Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Name of the database DB user authentication data. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

In the Set PreparedStatement Parameter table. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Parameter Type: Enter the parameter type. Related scenarios For related topics. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. This check box is selected by default. If needed. Clear the check box to skip the row on error and complete the process for error-free rows. Performance levels are increased Die on error Advanced settings Propagate QUERY’s recordset Encoding Type Use PreparedStatement Commit every Number of rows to be completed before committing batches of rows together into the DB. you can retrieve the rows on error via a Row > Rejects link. Parameter Value: Enter the parameter value. Select this column from the use column list. tStatCatcher Statistics Select this check box to collect log data at the component level. This option ensures transaction quality (but not rollback) and above all better performance on executions. Select this check box to insert the result of the query into a COLUMN of the current flow. Parameter Index: Enter the parameter position in the SQL instruction.Databases components tAccessRow Encoding Type Select the encoding from the list or select Custom and define it manually. Select this checkbox if you want to query the database using a PreparedStatement. This field is compulsory for DB data handling. 212 Talend Open Studio Components Creative Commons License . Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. This option is very useful if you need to execute the same query several times.

Close a transaction. n/a Related scenario No scenario is available for this component yet. Creative Commons License Talend Open Studio Components 213 . Component list Select the tAS400Connection component in the list if more than one connection are planned for the current Job. especially with tAS400Connection and tAS400Commit. This component is to be used along with AS400 components. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tAS400Close tAS400Close tAS400Close properties Component family Databases/AS400 Function Purpose Basic settings tAS400Close closes the transaction committed in the connected DB.

If you want to use a Row > Main connection to link tAS400Commit to your Job. n/a Related scenario This component is closely related to tAS400Connection and tAS400Rollback. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. 214 Talend Open Studio Components Creative Commons License . do not select the Close connection check box or your connection will be closed before the end of your first row commit. For tAS400Commit related scenario. Component family Databases/AS400 Function Purpose Validates the data processed through the Job into the connected DB.Databases components tAS400Commit tAS400Commit tAS400Commit Properties This component is closely related to tAS400Connection and tAS400Rollback. see tMysqlConnection on page 460. Component list Select the tAS400Connection component in the list if more than one connection are planned for the current Job. Clear this check box to continue to use the selected connection once the component has performed its task. especially with tAS400Connection and tAS400Rollback components. It usually doesn’t make much sense to use these components independently in a transaction. This check box is selected by default. It allows you to close the database connection once the commit is done. This component is to be used along with AS400 components. It usually doesn’t make much sense to use one of these without using a tAS400Connection component to open a connection for the current transaction. In this case. Using a unique connection. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. your data will be commited row by row.

DB Version Host Database Username and Password Encoding Type Select the AS400 version in use Database server IP address Name of the database DB user authentication data. Usage Limitation This component is to be used along with AS400components. n/a Creative Commons License Talend Open Studio Components 215 . This field is compulsory for DB data handling. especially with tAS400Commit and tAS400Rollback components. Select this check box to share your connection or fetch a connection shared by a parent or child Job. Component family Databases/AS400 Function Purpose Basic settings Opens a connection to the database for a current transaction. Shared DB Connection Name: set or type in the shared connection name.Databases components tAS400Connection tAS400Connection tAS400Connection Properties This component is closely related to tAS400Commit and tAS400Rollback. Select this check box to automatically commit a transaction when it is completed. This component allows you to commit all of the Job data to an output database in just a single transaction. Select the encoding from the list or select Custom and define it manually. Property type Either Built-in or Repository. The fields that come after are pre-filled in using the fetched data. Repository: Select the repository file where Properties are stored. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Built-in: No property data stored centrally. Use or register a shared DB Connection Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. once the data has been validated. It usually doesn’t make much sense to use one of the components without using a tAS400Connection component to open a connection for the current transaction.

For tAS400Connection related scenario. see tMysqlConnection on page 460. 216 Talend Open Studio Components Creative Commons License .Databases components tAS400Connection Related scenario This component is closely related to tAS400Commit and tAS400Rollback. It usually doesn’t make much sense to use one of these without using a tAS400Connection component to open a connection for the current transaction.

Built-in: The schema is created and stored locally for this component only. tAS400SInput executes a DB query with a strictly defined statement which must correspond to the schema definition. Property type Either Built-in or Repository Built-in: No property data stored centrally. Basic settings Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. The schema is either built-in or remotely stored in the Repository.e. This option is not available if you have selected the Use an existing connection check box in the Basic settings.Databases components tAS400Input tAS400Input tAS400Input properties Component family Databases/AS400 Function Purpose tAS400Input reads a database and extracts fields based on a query. For more information about setting up and storing database connection parameters. Creative Commons License Talend Open Studio Components 217 . Name of the database DB user authentication data. it defines the number of fields to be processed and passed on to the next component.. A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. see Setting up a DB connection of Talend Open Studio User Guide. Then it passes on the field list to the next component via a Main row link. Repository: Select the repository file where Properties are stored. Related topic: Setting a Repository schema of Talend Open Studio User Guide. i. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. DB Version Host Port Database Username and Password Schema and Edit Schema Select the AS 400 version in use Database server IP address Listening port number of DB server. The fields that come after are pre-filled in using the fetched data. hence can be reused.

Select this check box to remove leading and trailing whitespace from all the String/Char columns. 218 Talend Open Studio Components Creative Commons License . Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Related scenarios For related topic. This field is compulsory for DB data handling. Remove leading and trailing whitespace from defined columns.Databases components tAS400Input Encoding Type Select the encoding type from the list or select Custom and define it manually. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.

. Related topic: Setting a Repository schema of Talend Open Studio User Guide. The schema is either built-in or remotely stored in the Repository. You can reuse it in various projects and job flow charts.e. see Scenario: Get the ID for the last inserted record on page 467 of the tMysqlLastInsertId component. Usage Limitation This component is to be used as an intermediary component. Component list Select the relevant tAS400Connection component in the list if more than one connection is planned for the current job. i.Databases components tAS400LastInsertId tAS400LastInsertId tAS400LastInsertId properties Component family Databases Function Purpose Basic settings tAS400LastInsertId fetches the last inserted ID from a selected AS400 Connection. Built-in: You create and store the schema locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Repository: You have already created the schema and stored it in the Repository. tAS400LastInsertId obtains the primary key value of the record that was last inserted in an AS400 table by a user. Schema and Edit Schema A schema is a row description. Creative Commons License Talend Open Studio Components 219 . n/a Related scenario For a related scenario.

see Setting up a DB connection of Talend Open Studio User Guide. Property type Either Built-in or Repository. Name of the database DB user authentication data. Built-in: No property data stored centrally. DB Version Host Port Database Username and Password Table Action on table Select the AS400 version in use Database server IP address Listening port number of DB server.Databases components tAS400Output tAS400Output tAS400Output properties Component family Databases/DB2 Function Purpose tAS400Output writes. The fields that come after are pre-filled in using the fetched data. tAS400Output executes the action defined on the table and/or on the data contained in the table. Repository: Select the repository file where Properties are stored. Name of the table to be written. Create a table if not exists: The table is created if it does not exist. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Drop a table if exists and create: The table is removed if it already exists and created again. based on the flow incoming from the preceding component in the Job. updates. Drop and create a table: The table is removed and created again. Create a table: The table does not exist and gets created. For more information about setting up and storing database connection parameters. Note that only one table can be written at a time On the table defined. you can perform one of the following operations: None: No operation is carried out. Clear a table: The table content is deleted. Basic settings 220 Talend Open Studio Components Creative Commons License . makes changes or suppresses entries in a database.

. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. To do that: Select the Use field options check box and then in the Key in update column. Job stops. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. select the check boxes next to the column names you want to use as a base for the Update operation. you can perform: Insert: Add new entries to the table. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i. Related topic: Setting a Repository schema of Talend Open Studio User Guide. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Specify additional connection properties for the DB connection you are creating. The schema is either built-in or remotely stored in the Repository. Schema and Edit Schema A schema is a row description. Built-in: The schema is created and stored locally for this component only.e. Advanced settings Additional JDBC parameters Encoding Type Creative Commons License Talend Open Studio Components 221 . If needed. This option is not available if you have selected the Use an existing connection check box in the Basic settings. you can retrieve the rows on error via a Row > Rejects link. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. Repository: The schema already exists and is stored in the Repository. Die on error This check box is selected by default. For an advanced use. hence can be reused. it defines the number of fields to be processed and passed on to the next component. Clear the check box to skip the row on error and complete the process for error-free rows. This field is compulsory for DB data handling. If duplicates are found. Do the same in the Key in delete column for the Delete operation. Select the encoding type from the list or select Custom and define it manually. Update: Make changes to existing entries Insert or update: Add entries or update existing ones.Databases components tAS400Output Action on data On the data of the table defined.

It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Select this check box to display each step during processing entries in a database. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. see • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. especially when there is double action on data. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. This option ensures transaction quality (but not rollback) and. above all. This component must be used as an output component. tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. For an example of tMySqlOutput in use. Use field options Enable debug mode Select this check box to customize a request. or action that require particular preprocessing. Additional Columns This option is not offered if you create (with or without drop) the DB table. Commit every: Enter the number of rows to be completed before committing batches of rows together into the DB. Position: Select Before. 222 Talend Open Studio Components Creative Commons License . better performance at execution. This option allows you to call SQL functions to perform actions on columns. Replace or After following the action to be performed on the reference column.Databases components tAS400Output Use commit control Select this check box to have access to the Commit every field where you can define the commit operation. nor update or delete actions. which are not insert. It allows you to carry out actions on a table or on the data of a table in a AS400 database. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

especially with tAS400Connection and tAS400Commit.Databases components tAS400Rollback tAS400Rollback tAS400Rollback properties This component is closely related to tAS400Commit and tAS400Connection. see Scenario: Rollback from inserting data in mother/daughter tables on page 498 of the tMysqlRollback. n/a Related scenarios For tAS400Rollback related scenario. Component list Select the tAS400Connection component in the list if more than one connection are planned for the current Job. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Clear this check box to continue to use the selected connection once the component has performed its task. It usually does not make much sense to use these components independently in a transaction. Component family Databases/AS400 Function Purpose Basic settings tAS400Rollback cancels the transaction committed in the connected DB. Avoids involuntary commitment of part of a transaction. This component is to be used along with AS400 components. Creative Commons License Talend Open Studio Components 223 .

tAS400Row acts on the actual DB structure or on the data (although without handling data). It executes the SQL query stated onto the specified database. Repository: Select the repository file where Properties are stored. make sure that the available connection components are sharing the intended connection. see your studio user guide.Databases components tAS400Row tAS400Row tAS400Row properties Component family Databases/AS400 Function tAS400Row is the specific component for this database query. For more information about Dynamic settings. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job. Property type Either Built-in or Repository. The SQLBuilder tool helps you write easily your SQL statements. In this case. Depending on the nature of the query and the database. Name of the database DB user authentication data. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. Host Port Database Username and Password Database server IP address Listening port number of DB server. Otherwise. Purpose Basic settings 224 Talend Open Studio Components Creative Commons License . DB Version Use an existing connection Select the AS400 version in use Select this check box and click the relevant tAS400Connection component on the Component list to reuse the connection details you already defined. Built-in: No property data stored centrally. so if you need to use an existing connection from the other level. For more information on how to share a DB connection across Job levels. The row suffix means the component implements a flow in the job design although it doesn’t provide output. The fields that come after are pre-filled in using the fetched data.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. Parameter Type: Enter the parameter type. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Clear the check box to skip the row on error and complete the process for error-free rows.e. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Performance levels are increased Die on error Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. This check box is selected by default. hence can be reused. Commit every Creative Commons License Talend Open Studio Components 225 . Select this check box to insert the result of the query into a COLUMN of the current flow. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Specify additional connection properties for the DB connection you are creating. This option ensures transaction quality (but not rollback) and above all better performance on executions. you can retrieve the rows on error via a Row > Rejects link. Select this checkbox if you want to query the database using a PreparedStatement. Query type Either Built-in or Repository.Databases components tAS400Row Schema and Edit Schema A schema is a row description. Select this column from the use column list. Parameter Value: Enter the parameter value. Parameter Index: Enter the parameter position in the SQL instruction. Number of rows to be completed before committing batches of rows together into the DB. The Query field gets accordingly filled in. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. it defines the number of fields to be processed and passed on to the next component. This field is compulsory for DB data handling. i. In the Set PreparedStatement Parameter table. If needed.. Built-in: The schema is created and stored locally for this component only. This option is very useful if you need to execute the same query several times.

Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.Databases components tAS400Row tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios For related topics. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. 226 Talend Open Studio Components Creative Commons License .

tCreateTable covers needs related indirectly to the use of any database. Select the action to be carried out on the database among: Create table: when you know already that the table doesn’t exist. drops and creates or clear the specified table. The component properties may differ slightly according to the database type selected from the list. tCreateTable Properties Component family Databases Function Purpose Basic settings tCreateTable creates. Repository: Select the repository file where properties are stored. Create table when not exists: when you don’t know whether the table is already created or not Drop and create table: when you know that the table exists already and needs to be replaced. Built-in: No property data stored centrally. The fields that follow are pre-filled in using fetched data.Databases components tCreateTable tCreateTable You can find this component at the root of Databases group of the Palette of Talend Open Studio. Database Type Select the DBMS type from the list. Select this check box if you want to save the created table temporarily. This Java specific component helps create or drop any database table Property type Either Built-in or Repository. Table Action MySQL Temporary table Creative Commons License Talend Open Studio Components 227 .

make sure that the available connection components are sharing the intended connection. Name and path of the file to be processed. JavaDb. Database server IP address Firebird Firebird File Interbase Interbase File SQLite SQLite File JavaDb HSQLDb HSQLDb AS400/Oracle All database types except Access. so if you need to use an existing connection from the other level. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Oracle Access Connection Type Access File Drop-down list of available drivers. Otherwise. Select from the list the Server Mode that correspond to your DB setup. For more information about Dynamic settings. Name and path of the file to be processed. When a Job contains the parent Job and the child Job. PostgresPlus. Select from the list a framework for your database. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. 228 Talend Open Studio Components Creative Commons License . Select the database version in use. Postgresql Use an existing connection Select this check box in case you use a database connection component. Name and path of the file to be processed. Firebird. Browse to your database root. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Oracle. for example: tMysqlConnection or tOracleConnection. Name and path of the file to be processed. Component list presents only the connection components in the same Job level. HSQLDb. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Select this check box to enable the secured mode. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. For more information on how to share a DB connection across Job levels. SQLite and ODBC JavaDb DB Root Path Name of the database. if required. In this case. make sure the connection name is unique and distinctive all over through the two Job levels. MySQL.Databases components tCreateTable MSSQLServer. see your studio user guide. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. etc. SQLite and ODBC Framework Type Running Mode Use TLS/SSL Sockets DB Version Host All database types Database name except Access.

Built-in: The schema is created and stored locally for this component only.. JavaDb.Databases components tCreateTable All database types except Access. hence can be reused in various Jobs and projects. AS400. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Type in between quotes a name for the newly created table. More scenarios are available for specific DB Input components Scenario: Creating new table in a Mysql Database The Job described below aims at creating a table in a database. Repository: The schema already exists and is stored in the Repository. Creative Commons License Talend Open Studio Components 229 . The schema is either built-in or remotely stored in the Repository. DB Alias DB Server ODBC Name Username and Password Table name Schema and Edit Schema Name of the database. made of a dummy schema taken from a delimited file schema stored in the Repository. to make sure data type is correct. Name of the database. Select this check box to gather the job processing metadata at a Job level as well as at each component level. This Job is composed of a single component.e. SQLite and ODBC HSQLDb Informix ODBC Port Listening port number of the DB server. it defines the number of fields to be processed and passed on to the next component. tStatcatcher Statistics AS400/ MSSQL Server Additional JDBC Parameters Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Name of the database server. Firebird. This field is compulsory for DB data handling. Reset the DB type by clicking the relevant button. A schema is a row description. DB user authentication data. Advanced settings Encoding Select the encoding from the list or select Custom and define it manually. i. Specify additional connection properties for the DB connection you are creating. Interbase. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

see tMysqlConnection on page 460. • If you want to retrieve the Schema from the Metadata (it doesn’t need to be a DB connection Schema metadata).Databases components tCreateTable • Drop a tCreateTable component from the Databases family in the Palette to the design workspace. • From the Table Action list. • In the Basic settings view. 230 Talend Open Studio Components Creative Commons License . select Repository so that the connection fields that follow are automatically filled in. fill in a name for the table to be created. • In any case (Built-in or Repository) click Edit Schema to check the data type mapping. we won’t use this option. select Create table. select Repository then the relevant entry. select Mysql for this scenario. In this example. fill in the details manually as Built-in. If you have not defined your DB connection metadata in the DB connection directory under the Metadata node. • Select the Use Existing Connection check box only if you are using a dedicated DB connection component. • In the Table Name field. • In the Property type field. and from the Database Type list.

• Save your Job and press F6 to execute it. This allows you to map any data type to the relevant DB data type. The table is created empty but with all columns defined in the Schema. • Click OK to validate your changes and close the dialog box. Creative Commons License Talend Open Studio Components 231 .Databases components tCreateTable • Click the Reset DB Types button in case the DB type column is empty or shows discrepancies (marked in orange).

For more information about Dynamic settings. Name of the table to be written. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Note that only one table can be written at a time 232 Talend Open Studio Components Creative Commons License . you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Built-in: No property data stored centrally. Use an existing connection Select this check box and click the relevant tDB2Connection component on the Component List to reuse the connection details you already defined. so if you need to use an existing connection from the other level. The fields that come after are pre-filled in using the fetched data. Property type Either Built-in or Repository.Databases components tDB2BulkExec tDB2BulkExec tDB2BulkExec properties Component family Databases/DB2 Function Purpose Basic settings tDB2BulkExec executes the Insert action on the data provided. Otherwise. Component list presents only the connection components in the same Job level. Host Port Database Table Schema Username and Password Table Database server IP address Listening port number of DB server. As a dedicated component. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. tDB2BulkExec allows gains in performance during Insert operations to a DB2 database. make sure that the available connection components are sharing the intended connection. When a Job contains the parent Job and the child Job. DB user authentication data. Repository: Select the repository file where Properties are stored. For more information on how to share a DB connection across Job levels. see your studio user guide. Name of the database Name of the DB schema.

you can perform one of the following operations: None: No operation is carried out. Action on data Advanced settings Field terminated by Date Format Time Format Timestamp Format Remove load pending Load options Creative Commons License Talend Open Studio Components 233 .e. A schema is a row description. i. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. The schema is either built-in or remotely stored in the Repository. Value: enter a value for the parameter selected. you can perform: Insert: Add new entries to the table. tables blocked in "pending" status following a bulk load are de-blocked. Repository: You have already created the schema and stored it in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Job stops. Drop and create table: The table is removed and created again.. Schema and Edit Schema Data file Name of the file to be processed. Related topic: Setting a built-in schema of Talend Open Studio User Guide.Databases components tDB2BulkExec Action on table On the table defined. string or regular expression to separate fields. Use this field to define the way hours. Create table if not exists: The table is created if it does not exist. Drop table if exists and create: The table is removed if it already exists and created again. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Click + to add data loading options: Parameter: select a loading parameter from the list. hence can reuse it. Use this field to define the way date and time are ordered. If duplicates are found. Create table: The table does not exist and gets created. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow.. Clear table: The table content is deleted. minutes and seconds are ordered. When the box is ticked. On the data of the table defined. Use this field to define the way months and days are ordered. it defines the number of fields to be processed and passed on to the next component. Character. Built-in: You create the schema and store it locally for this component only.

see: • tMysqlOutputBulkExec Scenario: Inserting transformed data in MySQL database on page 490.Databases components tDB2BulkExec tStatCatcher Statistics Select this check box to collect log data at the component level. • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538. 234 Talend Open Studio Components Creative Commons License . Usage This dedicated component offers performance and flexibility of DB2 query handling. Related scenarios For tDB2BulkExec related topics.

n/a Related scenario No scenario is available for this component yet. especially with tDB2Connection and tDB2Commit. Component list Select the tDB2Connection component in the list if more than one connection are planned for the current Job. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. This component is to be used along with DB2 components. Creative Commons License Talend Open Studio Components 235 .Databases components tDB2Close tDB2Close tDB2Close properties Component family Databases/DB2 Function Purpose Basic settings tDB2Close closes the transaction committed in the connected DB. Close a transaction.

236 Talend Open Studio Components Creative Commons License . It allows you to close the database connection once the commit is done. do not select the Close connection check box or your connection will be closed before the end of your first row commit. This component is to be used along with DB2 components. For tDB2Commit related scenario. If you want to use a Row > Main connection to link tAS400Commit to your Job. Component family Databases/DB2 Function Purpose Validates the data processed through the Job into the connected DB. It usually doesn’t make much sense to use one of these without using a tDB2Connection component to open a connection for the current transaction. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. It usually doesn’t make much sense to use these components independently in a transaction. This check box is selected by default. your data will be commited row by row. especially with tDB2Connection and tDB2Rollback components.Databases components tDB2Commit tDB2Commit tDB2Commit Properties This component is closely related to tDB2Connection and tDB2Rollback. Component list Select the tDB2Connection component in the list if more than one connection are planned for the current Job. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Using a unique connection. Clear this check box to continue to use the selected connection once the component has performed its task. see tMysqlConnection on page 460. n/a Related scenario This component is closely related to tDB2Connection and tDB2Rollback. In this case.

Shared DB Connection Name: set or type in the shared connection name. Property type Either Built-in or Repository.. Host name Port Database Table Schema Username and Password Use or register a shared DB Connection Database server IP address. once the data has been validated. Name of the schema.Databases components tDB2Connection tDB2Connection tDB2Connection properties This component is closely related to tDB2Commit and tDB2Rollback. n/a Creative Commons License Talend Open Studio Components 237 . Select this check box to automatically commit a transaction when it is completed. Usage Limitation This component is to be used along with DB2 components. especially with tDB2Commit and tDB2Rollback. Built-in: No property data stored centrally. Component family Databases/DB2 Function Purpose Basic settings tDB2Connection opens a connection to the database for a current transaction. Select this check box to share your connection or fetch a connection shared by a parent or child Job. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. It usually does not make much sense to use one of these without using a tDB2Connection to open a connection for the current transaction. This component allows you to commit all of the Job data to an output database in just a single transaction. Listening port number of DB server. DB user authentication data. Name of the database. The fields that come after are pre-filled in using the fetched data. Repository: Select the repository file where Properties are stored.

Databases components tDB2Connection Related scenarios This component is closely related to tDB2Commit and tDB2Rollback. For tDB2Connection related scenario. It usually does not make much sense to use one of these without using a tDB2Connection component to open a connection for the current transaction. see tMysqlConnection on page 460. 238 Talend Open Studio Components Creative Commons License .

see your studio user guide. Property type Either Built-in or Repository. see Setting up a DB connection of Talend Open Studio User Guide. tDB2Input executes a DB query with a strictly defined order which must correspond to the schema definition. Built-in: No property data stored centrally. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Basic settings Creative Commons License Talend Open Studio Components 239 . Otherwise. make sure that the available connection components are sharing the intended connection. The fields that come after are pre-filled in using the fetched data. For more information on how to share a DB connection across Job levels. Then it passes on the field list to the next component via a Main row link. so if you need to use an existing connection from the other level. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Component list presents only the connection components in the same Job level. Name of the database DB user authentication data. For more information about Dynamic settings. For more information about setting up and storing database connection parameters. When a Job contains the parent Job and the child Job. Repository: Select the repository file where Properties are stored. Use an existing connection Select this check box and click the relevant tDB2Connection component on the Component list to reuse the connection details you already defined. Host Port Database Username and Password Database server IP address Listening port number of DB server.Databases components tDB2Input tDB2Input tDB2Input properties Component family Databases/DB2 Function Purpose tDB2Input reads a database and extracts fields based on a query.

Related scenarios For related topics. Remove leading and trailing whitespace from defined columns. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also the related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Repository: The schema already exists and is stored in the Repository.Databases components tDB2Input Schema and Edit Schema A schema is a row description. This field is compulsory for DB data handling. The schema is either built-in or remotely stored in the Repository. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Usage This component covers all possibilities of SQL queries onto a DB2 database. Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. it defines the number of fields to be processed and passed on to the next component. 240 Talend Open Studio Components Creative Commons License .. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. i. hence can be reused. Built-in: The schema is created and stored locally for this component only.

Component list presents only the connection components in the same Job level.Databases components tDB2Output tDB2Output tDB2Output properties Component family Databases/DB2 Function Purpose tDB2Output writes. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. see your studio user guide. tDB2Output executes the action defined on the table and/or on the data contained in the table. make sure the connection name is unique and distinctive all over through the two Job levels. When a Job contains the parent Job and the child Job. see Setting up a DB connection of Talend Open Studio User Guide. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. For more information about setting up and storing database connection parameters. Built-in: No property data stored centrally. makes changes or suppresses entries in a database. Host Port Database Username and Password Database server IP address Listening port number of DB server. Basic settings Creative Commons License Talend Open Studio Components 241 . see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Repository: Select the repository file where Properties are stored. For more information about Dynamic settings. Name of the database DB user authentication data. updates. The fields that come after are pre-filled in using the fetched data. make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels. Property type Either Built-in or Repository. based on the flow incoming from the preceding component in the Job. so if you need to use an existing connection from the other level. Otherwise. In this case. Use an existing connection Select this check box and click the relevant tDB2Connection component on the Component list to reuse the connection details you already defined.

Built-in: The schema is created and stored locally for this component only. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. Do the same in the Key in delete column for the deletion operation Action on data Schema and Edit Schema A schema is a row description. Clear a table: The table content is deleted. you can perform one of the following operations: None: No operation is carried out. Note that only one table can be written at a time On the table defined. You must specify at least one column as a primary key on which the Update and Delete operations are based. Drop a table if exists and create: The table is removed if it already exists and created again. Create a table if not exists: The table is created if it does not exist. Related topic: Setting a built-in schema of Talend Open Studio User Guide. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Job stops. it defines the number of fields to be processed and passed on to the next component.. Create a table: The table does not exist and gets created. On the data of the table defined. If duplicates are found. For an advanced use. Repository: The schema already exists and is stored in the Repository. click the Advanced settings view where you can simultaneously define primary keys for the update and delete operations. select the check boxes next to the column name on which you want to base the update operation. 242 Talend Open Studio Components Creative Commons License . To do that: Select the Use field options check box and then in the Key in update column.Databases components tDB2Output Table Action on table Name of the table to be written. you can perform: Insert: Add new entries to the table. Related topic: Setting a Repository schema of Talend Open Studio User Guide. hence can be reused.e. Drop and create a table: The table is removed and created again. i. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. The schema is either built-in or remotely stored in the Repository.

especially when there is double action on data. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. This component must be used as an output component.Databases components tDB2Output Die on error This check box is selected by default. This option ensures transaction quality (but not rollback) and. If needed. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For tDB2Output related topics. see • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. Creative Commons License Talend Open Studio Components 243 . nor update or delete actions. you can retrieve the rows on error via a Row > Rejects link. Position: Select Before. Clear the check box to skip the row on error and complete the process for error-free rows. above all. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. which are not insert. This option is not offered if you create (with or without drop) the DB table. This option allows you to call SQL functions to perform actions on columns. For an example of tMySqlOutput in use. Advanced settings Encoding Type Commit every Additional Columns Use field options Enable debug mode Select this check box to customize a request. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. or action that require particular preprocessing. It allows you to carry out actions on a table or on the data of a table in a DB2 database. better performance at execution. Select this check box to display each step during processing entries in a database. This field is compulsory for DB data handling. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Enter the number of rows to be completed before committing batches of rows together into the DB. tStatCatcher Statistics Select this check box to collect log data at the component level. Select the encoding type from the list or select Custom and define it manually. Replace or After following the action to be performed on the reference column.

Databases components tDB2Rollback tDB2Rollback tDB2Rollback properties This component is closely related to tDB2Commit and tDB2Connection. see Scenario: Rollback from inserting data in mother/daughter tables on page 498 of the tMysqlRollback. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. n/a Related scenarios For tDB2Rollback related scenario. Avoids to commit part of a transaction involuntarily. especially with tDB2Connection and tDB2Commit. This component is to be used along with DB2 components. Clear this check box to continue to use the selected connection once the component has performed its task. 244 Talend Open Studio Components Creative Commons License . Component list Select the tDB2Connection component in the list if more than one connection are planned for the current Job. It usually does not make much sense to use these components independently in a transaction. Component family Databases/DB2 Function Purpose Basic settings tDB2Rollback cancels the transaction committed in the connected DB.

Otherwise. so if you need to use an existing connection from the other level. The row suffix means the component implements a flow in the job design although it doesn’t provide output. When a Job contains the parent Job and the child Job. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. i.e. make sure that the available connection components are sharing the intended connection. Built-in: No property data stored centrally. it defines the number of fields to be processed and passed on to the next component. A schema is a row description. In this case. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Property type Either Built-in or Repository. Repository: Select the repository file where Properties are stored.. tDB2Row acts on the actual DB structure or on the data (although without handling data). It executes the SQL query stated onto the specified database.Databases components tDB2Row tDB2Row tDB2Row properties Component family Databases/DB2 Function tDB2Row is the specific component for this database query. Depending on the nature of the query and the database. The schema is either built-in or remotely stored in the Repository. Name of the database DB user authentication data. The SQLBuilder tool helps you write easily your SQL statements. Use an existing connection Select this check box and click the relevant tDB2Connection component on the Component list to reuse the connection details you already defined. Purpose Basic settings Creative Commons License Talend Open Studio Components 245 . The fields that come after are pre-filled in using the fetched data. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. see your studio user guide. For more information about Dynamic settings. Host Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server.

This field is compulsory for DB data handling. The Query field gets accordingly filled in. 246 Talend Open Studio Components Creative Commons License . Parameter Type: Enter the parameter type. Related topic: Setting a Repository schema of Talend Open Studio User Guide. If needed. Query type Either Built-in or Repository. Select this column from the use column list. Performance levels are increased Encoding Type Select the encoding from the list or select Custom and define it manually. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Select this checkbox if you want to query the database using a PreparedStatement. Parameter Value: Enter the parameter value. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. hence can be reused.Databases components tDB2Row Built-in: The schema is created and stored locally for this component only. This option is very useful if you need to execute the same query several times. you can retrieve the rows on error via a Row > Rejects link. This check box is selected by default. Parameter Index: Enter the parameter position in the SQL instruction. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. In the Set PreparedStatement Parameter table. Clear the check box to skip the row on error and complete the process for error-free rows. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This option ensures transaction quality (but not rollback) and above all better performance on executions. Repository: The schema already exists and is stored in the Repository. Select this check box to insert the result of the query into a COLUMN of the current flow. Number of rows to be completed before committing batches of rows together into the DB. Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository.

Databases components tDB2Row Related scenarios For tDB2Row related topics. Creative Commons License Talend Open Studio Components 247 . see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502.

see tDB2SCD on page 2.Databases components tDB2SCD tDB2SCD tDB2SCD belongs to two component families: Business Intelligence and Databases. 248 Talend Open Studio Components Creative Commons License . For more information on it.

Creative Commons License Talend Open Studio Components 249 . see tDB2SCD on page 2. For more information on it.Databases components tDB2SCDELT tDB2SCDELT tDB2SCDELT belongs to two component families: Business Intelligence and Databases.

the value to be returned is based on. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Name of the database DB user authentication data. 250 Talend Open Studio Components Creative Commons License . Select on the list the schema column.Databases components tDB2SP tDB2SP tDB2SP properties Component family Databases/DB2 Function Purpose Basic settings tDB2SP calls the database stored procedure. SP Name Is Function / Return result in Type in the exact name of the Stored Procedure Check this box.e. The fields that come after are pre-filled in using the fetched data. Repository: Select the repository file where Properties are stored. The schema is either built-in or remotely stored in the Repository. tDB2SP offers a convenient way to centralize multiple or complex queries in a database and call them easily. Built-in: No property data stored centrally. if a value only is to be returned.. Built-in: The schema is created and stored locally for this component only. hence can be reused. it defines the number of fields to be processed and passed on to the next component. Property type Either Built-in or Repository. Repository: The schema already exists and is stored in the Repository. Host Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. Related topic: Setting a Repository schema of Talend Open Studio User Guide. A schema is a row description. i.

Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. Select the encoding from the list or select Custom and define it manually. see tMysqlSP Scenario: Finding a State Label using a stored procedure on page 512. Check as well the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. It can be used as start component but only input parameters are thus allowed. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameters is to be returned as value. Note that the SP schema can hold more columns than there are parameters used in the procedure. Related scenarios For related topic.Databases components tDB2SP Parameters Click the Plus button and select the various Schema Columns that will be required by the procedures. RECORDSET: Input parameters is to be returned as a set of values. rather than single value. The Stored Procedures syntax should match the Database syntax. This field is compulsory for DB data handling. likely after modification through the procedure (function). Creative Commons License Talend Open Studio Components 251 . Encoding Type Usage Limitation This component is used as intermediary component.

Repository: Select the repository file where Properties are stored. This field is compulsory for DB data handling. it defines the number of fields to be processed and passed on to the next component. Select the encoding type from the list or select Custom and define it manually. A schema is a row description.. Property type Either Built-in or Repository Built-in: No property data stored centrally. The fields that come after are pre-filled in using the fetched data. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. a specific Input component (e. For more information about setting up and storing database connection parameters.: tMySQLInput for MySQL database) should always be preferred to the generic component. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.g. i.e. Name of the database DB user authentication data. Then it passes on the field list to the next component via a Main row link. Function Purpose Basic settings Advanced settings Encoding Type 252 Talend Open Studio Components Creative Commons License . hence can be reused. Related topic: Setting a built-in schema of Talend Open Studio User Guide. see Setting up a DB connection of Talend Open Studio User Guide. Connection type Database Username and Password Schema and Edit Schema Drop-down list of available DBMS drivers. tDBInput executes a DB query with a strictly defined order which must correspond to the schema definition. For performance reasons. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide.Databases components tDBInput tDBInput tDBInput properties Component family Databases/DB Generic tDBInput reads a database and extracts fields based on a query. Built-in: The schema is created and stored locally for this component only. The schema is either built-in or remotely stored in the Repository.

Scenario 1: Displaying selected data from DB table The following scenario creates a two-component Job. and define the properties: • The component property data are Built-In for this scenario. Creative Commons License Talend Open Studio Components 253 . • Enter the table name in the corresponding field. • Fill in the database name. • Double-click the tDBInput so the Component view shows up.This means that it is available for this Job and on this station only. • Right-click on the tDBInput component and select Row > Main. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries using a generic ODBC connection. reading data from a database using a DB query and outputting delimited data into the standard output (console). • Click on Edit Schema and create a 2-column description including shop code and sales. Drag this main row link onto the tLogRow component and release when the plug symbol displays. tStatCatcher Statistics Select this check box to collect log data at the component level. the username and password in the corresponding fields. • Drop a tDBInput and tLogRow component from the Palette to the design workspace. Remove leading and trailing whitespace from defined columns.Databases components tDBInput Trim all the String/Char columns Trim column Select this check box to remove leading and trailing whitespace from all the String/Char columns. • The schema is Built-In.

It allows you to dynamically feed the SQL query set in your tDBInput component. and click on Run to execute the Job. • Create a new parameter called explicitly StoreSQLQuery. In this case. • Set both tDBInput and tLogRow component as in tDBInput scenario 1. The DB is parsed and queried data is extracted from the specified table and passed on to the job log console. as we’ll select all columns of the schema. • Click on the second component to define it. 254 Talend Open Studio Components Creative Commons License . Enter a default value of 1. a pipe separator. Scenario 2: Using StoreSQLQuery variable StoreSQLQuery is a variable that can be used to debug a tDBInput scenario which does not operate correctly. the asterisk symbol makes sense. • Click anywhere on the design workspace to display the Contexts property panel. In this case. In this case. • Connect tDBInput to tJava using a trigger connection of the OnComponentOk type. You can view the output file straight on the console. • Enter the fields separator. • Use the same scenario as scenario 1 above and add a third component.Databases components tDBInput • Type in the query making sure it includes all columns in the same order as defined in the Schema. • Now go to the Run tab. we want the tDBInput to run before the tJava component. tJava. This value of 1 means the StoreSQLQuery is “true” for a use in the QUERY global variable.

• Go to your Run tab and execute the Job. Enter the System.Databases components tDBInput • Click on the tJava component to display the Component view. • The query entered in the tDBInput component shows at the end of the job results.Out. on the log: Creative Commons License Talend Open Studio Components 255 . press Ctrl+Space bar to access the variable list and select the global variable QUERY.println(“”)command to display the query content.

Property type Either Built-in or Repository. Specific Output component should always be preferred to generic component. Basic settings 256 Talend Open Studio Components Creative Commons License . see Setting up a DB connection of Talend Open Studio User Guide. Name of the database DB user authentication data. tDBOutput executes the action defined on the table and/or on the data contained in the table. Drop and create a table: The table is removed and created again. updates. Create a table if not exists: The table is created if it does not exist. you can perform one of the following operations: None: No operation is carried out. Clear a table: The table content is deleted. Built-in: No property data stored centrally. Name of the table to be written. Create a table: The table does not exist and gets created. Repository: Select the repository file where Properties are stored. For more information about setting up and storing database connection parameters. Note that only one table can be written at a time On the table defined. The fields that come after are pre-filled in using the fetched data. based on the flow incoming from the preceding component in the Job. Connection type Database Username and Password Table Action on table List of available drivers. Drop a table if exists and create: The table is removed if it already exists and created again. makes changes or suppresses entries in a database.Databases components tDBOutput tDBOutput tDBOutput properties Component family Databases Function Purpose tDBOutput writes. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

. This option ensures transaction quality (but not rollback) and. Schema and Edit Schema A schema is a row description. Do the same in the Key in delete column for the Delete operation. Built-in: The schema is created and stored locally for this component only. better performance at execution. Update: Make changes to existing entries Insert or update: Add entries or update existing ones.e. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. it defines the number of fields to be processed and passed on to the next component. To do that: Select the Use field options check box and then in the Key in update column. hence can be reused. Enter the number of rows to be completed before committing batches of rows together into the DB. If duplicates are found. Repository: The schema already exists and is stored in the Repository. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This field is compulsory for DB data handling. Clear the check box to skip the row on error and complete the process for error-free rows. select the check boxes next to the column names you want to use as a base for the Update operation. Advanced settings Encoding Type Commit every Creative Commons License Talend Open Studio Components 257 .Databases components tDBOutput Action on data On the data of the table defined. Select the encoding type from the list or select Custom and define it manually. If needed. i. you can perform: Insert: Add new entries to the table. Job stops. Die on error This check box is selected by default. above all. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. For an advanced use. you can retrieve the rows on error via a Row > Rejects link. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.Databases components tDBOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. In this use case. Position: Select Before. If this file is already described in your metadata. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Use field options Enable debug mode Select this check box to customize a request. which are not insert. color and registration references organized as follows: semi-colon as field separator. the file contains cars’ owner id. define the input flow parameters. This component must be used as an output component. tStatCatcher Statistics Select this check box to collect log data at the component level. or action that require particular preprocessing. makes. This option allows you to call SQL functions to perform actions on columns. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. • On the Basic settings tab of tFileInputDelimited. • Drop the three components required for this Job from the Palette to the design workspace. see Scenario 3: Retrieve data in error with a Reject link on page 483 Scenario: Displaying DB output This following scenario is a three-component Job aiming at creating a new table in the database defined and filling it with data. As the content of a DB is not viewable as such. especially when there is double action on data. Replace or After depending on the action to be performed on the reference column. a tLogRow component is used to display the main flow on the Run console. carriage return as row separator. Select this check box to display each step during processing entries in a database. It allows you to carry out actions on a table or on the data of a table in a database. The input file contains a header row to be considered in the schema. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. 258 Talend Open Studio Components Creative Commons License . For an example of tMySqlOutput in use. The tFileInputdelimited passes on the Input flow to the tDBoutput component. nor update or delete actions. you can retrieve the properties by selecting the relevant repository entry list.

but note that duplicate management is not supported natively. • To view the output flow easily. Press F6 to execute the Job. define the data structure in the built-in schema you edit. • Fill in the table name in the Table field. for this example. Note that you can store all the database connection details in different context variables. Creative Commons License Talend Open Studio Components 259 . See tUniqRow Properties on page 203 for further information.Databases components tDBOutput • And also. For more information about how to create and use context variables Defining Contexts and variables in Talend Open Studio User Guide. If you haven’t defined the schema already. if your schema is already loaded in the Repository. Select the database to connect to. • As Action on data. Define the field separator as a pipe symbol. • Then define the tDBOutput component to configure the output flow. The data flow incoming as input will be thus added to the selected table. connect the DBOuput component to an tLogRow component. select Insert. select Drop and create table in the list. Then select the operations to be performed: • As Action on table. This allows you to overwrite the possible existing table with the new selected data. Alternatively you can insert only extra rows into an existing table. select Repository as Schema and choose the relevant metadata entry in the list. • Restrict the extraction to 10 lines.

Databases components tDBOutput • As the processing can take some time to reach the tLogRow component. Related topic: tMysqlOutput properties on page 472 260 Talend Open Studio Components Creative Commons License . we recommend you to enable the Statistics functionality on the Run console.

It executes the SQL query stated onto the specified database. hence can be reused. The schema is either built-in or remotely stored in the Repository. Depending on the nature of the query and the database. A schema is a row description.Databases components tDBSQLRow tDBSQLRow tDBSQLRow properties Component family Databases/DB Generic tDBSQLRow is the generic component for database query. Query type Either Built-in or Repository. Repository: The schema already exists and is stored in the Repository. i. The SQLBuilder tool helps you write easily your SQL statements. Built-in: The schema is created and stored locally for this component only. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Database Username and Password Schema and Edit Schema Name of the database DB user authentication data. specific DB component should always be preferred to the generic component. Function Purpose Basic settings Advanced settings Propagate QUERY’s recordset Creative Commons License Talend Open Studio Components 261 . Repository: Select the repository file where Properties are stored. Select this column from the use column list. Related topic: Setting a Repository schema of Talend Open Studio User Guide.. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component.e. Built-in: No property data stored centrally. Property type Either Built-in or Repository. tDBSQLRow acts on the actual DB structure or on the data (although without handling data). Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Select this check box to insert the result of the query into a COLUMN of the current flow. The fields that come after are pre-filled in using the fetched data. The Query field gets accordingly filled in. For performance reasons.

262 Talend Open Studio Components Creative Commons License . This job has no output and is generally to be used before running a script. • Drag and drop a tDBSQLRow component from the Palette to the design workspace. Parameter Value: Enter the parameter value. This option is very useful if you need to execute the same query several times. Scenario: Resetting a DB auto-increment This scenario describes a single component Job which aims at re-initializing the DB auto-increment to 1. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Parameter Index: Enter the parameter position in the SQL instruction. This field is compulsory for DB data handling. Performance levels are increased Encoding Type Select the encoding from the list or select Custom and define it manually. Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. • On the Basic settings panel. Note: Use the relevant DBRow component according to the DB type you use. Parameter Type: Enter the parameter type. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab.Databases components tDBSQLRow Use PreparedStatement Select this checkbox if you want to query the database using a PreparedStatement. fill in the DB connection properties. In the Set PreparedStatement Parameter table. Number of rows to be completed before committing batches of rows together into the DB. Most of databases have their specific DBRow components. This option ensures transaction quality (but not rollback) and above all better performance on executions.

Databases components tDBSQLRow • The general connection information to the database is stored in the Repository. • The Schema is built-in for this Job and describes the Talend database structure. or else type in directly in the Query area: Alter table <TableName> auto_increment = 1 • Then click OK to validate the Basic settings. Then press F6 to run the Job. • The Query type is also built-in. The schema doesn’t really matter for this particular instance of Job as the action is made on the table auto-increment and not on data. Creative Commons License Talend Open Studio Components 263 . Click on the three dot button to launch the SQLbuilder editor. The Database Driver is a generic ODBC driver. The database autoincrement is reset to 1. Related topics: tMysqlRow properties on page 500.

hence can be reused. Click this button to retrieve the schema from the table.e. For more information about setting up and storing database connection parameters. The fields that come after are pre-filled in using the fetched data. Related topic: Setting a built-in schema of Talend Open Studio User Guide Repository: The schema already exists and is stored in the Repository. Property type Built-in or Repository Built-in: No properties stored centrally Repository: Select the repository file where Properties are stored.. i. Basic settings Query type and Query Enter your database query. 264 Talend Open Studio Components Creative Commons License .. see Setting up a DB connection of Talend Open Studio User Guide. Built-in: The schema is created and stored locally for this component only. taking care to ensure that the order of the fields corressponds exactly to that defined in the schema. User authentication information. Related topic: Setting a Repository schema of Talend Open Studio User Guide Table Name Enter the table name. Guess Query Guess schema Click this button to generate a query that corresponds to your table schema in the Query field. Host name Port Schema name Username et Password Schema and Edit Schema Database server IP address.The list of fields retrieved is then transmitted to the following component via a Main row link. A schema is a row description. Listening port number of the DB server Enter the schema name. The schema is either Built-in or remotely stored in the Repository. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. it defines the number of fields to be processed and passed on to the next component.Databases components tEXAInput tEXAInput tEXAInput properties Component Family Databases/EXA Function Purpose tEXAInput reads databases and extracts fields using queries. tEXAInput executes queries in databases according to a strict order which must correspond exactly to that defined in the schema.

Encoding Type Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect the log data and a component level. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Select the encoding type from the list or else select Custom and define it manually. Related scenarios For scenaris in which tEXAInput might be used. Select this check box to delete the spaces at the start and end of fields in all of the columns containing strings. This is an obligatory field.Databases components tEXAInput Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. Usage This component covers all possible SQL queries for EXA databases. see the following tBIInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Creative Commons License Talend Open Studio Components 265 . Deletes the spaces from the start and end of fields in the selected columns.

from the preceding component. Host Port Schema name Username and Password Table Action on table Database server IP address. updates. Property type Built-in or Repository Built-in: No properties stored centrally. Listening port number of the DB serve. Drop and create a table: The table is removed and created again.Databases components tEXAOutput tEXAOutput tEXAOutput properties Famille de composant Databases/EXA Function Purpose Basic settings tEXAOutput writes.. Repository: Select the repository file where Properties are stored. Create a table if not exists: The table is created if it does not exist. modifies or deletes data from databases. you can perform one of the following operations: None: No operation is carried out. see Setting up a DB connection of Talend Open Studio User Guide. You can only create one table at a time. For more information about setting up and storing database connection parameters. depending on the function of the input flow. The fields that come after are pre-filled in using the fetched data. Drop a table if exists and create: The table is removed if it already exists and created again. Enter the schema name. User authentication data. tEXAOutput executes the action defined on the table and/or on the table data. Clear a table: The table content is deleted. Name of the table to be created. Create a table: The table does not exist and gets created. 266 Talend Open Studio Components Creative Commons License . On the table defined. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

For an advanced use. Select the encoding type from the list or select Custom and define it manually. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow.. You must specify at least one column as a primary key on which the Update and Delete operations are based. The schema is either Built-in or remotely stored in the Repository. Specify additional connection properties for the DB connection you are creating. Die on error This check box is selected by default. you can perform: Insert: Add new entries to the table. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Built-in: The schema is created and stored locally for this component only. you can retrieve the rows on error via a Row > Rejects link. This is an obligatory field. Job stops. click the Advanced settings view where you can simultaneously define primary keys for the update and delete operations. Related topic: Setting a built-in schema of Talend Open Studio User Guide. If duplicates are found. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. hence can be reused. Advanced settings Use commit control Additional JDBC parameters Encoding Type Creative Commons License Talend Open Studio Components 267 . Do the same in the Key in delete column for the deletion operation . You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). To do that: Select the Use field options check box and then in the Key in update column. Repository: The schema already exists and is stored in the Repository. select the check boxes next to the column name on which you want to base the update operation. Schema and Edit Schema A schema is a row description. i. If needed. Select this box to display the Commit every field in which you can define the number of rows to be processed brefore comitting. it defines the number of fields to be processed and passed on to the next component.Databases components tEXAOutput Action on data On the data of the table defined. Related topic: Setting a Repository schema of Talend Open Studio User Guide.e. Clear the check box to skip the row on error and complete the process for error-free rows.

This option is not offered if you create (with or without drop) the DB table. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Replace or After. Related scenario For a scenario in which tEXAOutput might be used. This component must be used as an output component. depending on the action to be carried out on the reference column. For a user scenario. Enable debug mode tStatCatcher Statistics Select this check box to collect the log data at a component level. or action that require particular preprocessing Name: Enter the name of the column to be modified or inserted. see the tMySqlOutput example. It allows you to carry out actions on a table or on the data of a table in an EXA database. This option allows you to call SQL functions to perform actions on columns. Scenario 3: Retrieve data in error with a Reject link on page 483. This option guarantees the quality of the transaction (although there is no rollback option) and improves performance. see: • the tDBOutput Scenario: Displaying DB output on page 258 • the tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476 268 Talend Open Studio Components Creative Commons License . Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. Additional Columns Use field options Select this check box to customize a request.Databases components tEXAOutput Commit every Number of rows to be included in the batch before the data is written. Select this check box to display each step of the process by which the data is written in the database. SQL expression: Enter the SQL expression to be executed to modify or insert data in the corresponding columns. particularly when there are several actions to be carried out on the data. Position : Select Before. which are not insert. nor update or delete actions. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

User authentication information. It executes SQL queries on specified databases. or indeed the data. tEXARow acts on the actual structure of the database. Guess Query Click the Guess Query button to generate the query that corresponds to the table schema in the Query field. A schema is a row description. Built-in: Enter the query manually or with the help of the SQLBuilder. The Query field is then completed automatically. Host Port Schema name Username and Password Schema and Edit Schema Database server IP address. taking care to ensure that the field order matches that defined in the schema.e. although without modifying them. Built-in: The schema is created and stored locally for this component only. Property type Built-in ou Repository Built-in: No properties stored centrally. The fields that come after are pre-filled in using the fetched data. Built-in or Repository.. The schema is either Built-in or remotely stored in the Repository. Repository: Select the appropriate query from the Repository. hence can be reused. Related topic: Setting a built-in schema of Talend Open Studio User Guide.Databases components tEXARow tEXARow tEXARow properties Component Family Databases/EXA Function The tEXARow component is specific to this type of database. Depending on the nature of the query and the database. Talend Open Studio Components 269 Purpose Basic settings Query Creative Commons License . Enter your query. Enter the schema name. Related topic: Setting a Repository schema of Talend Open Studio User Guide Table Name Query type Name of the table to be processed. Listening port number of the DB serve. i. it defines the number of fields to be processed and passed on to the next component. Repository: The schema already exists and is stored in the Repository. Repository: Select the repository file where Properties are stored. The Row suffix indicates that it is used to channel a flow in a Job although it doesn’t produce any output data.

This is an obligatory field. you can retrieve the rows on error via a Row > Rejects link.Databases components tEXARow Die on error This check box is selected by default. Number of rows to be included in the batch before the data is written. Related scenarios For a scenario in which tEXARow might be used. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Select the particular column from the use column list. Select the encoding type from the list or select Custom and define it manually. see: • the tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • the tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502 270 Talend Open Studio Components Creative Commons License . Usage This component offers query flexibility as it covers all possible SQL query requirements. Specify additional connection properties for the DB connection you are creating. This option guarantees the quality of the transaction (although there is no rollback option) and improves performance. Select this check box to insert the query results in one of the flow columns. If needed. Clear the check box to skip the row on error and complete the process for error-free rows. Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Encoding Type Commit every tStatCatcher Statistics Select this check box to collect the log data at a component level..

Enter the path to the collection of interest on the database server. Opens a connection to an eXist database in order that a transaction may be carried out. you have the option of reusing the connection without having to set the properties again for each tEXist component used in the Job. User authentication information. Users can enter a different driver. URI Collection Driver URI of the database you want to connect to. Component family Databases/eXist Function Purpose tEXistConnection opens a connection to an eXist database in order that a transaction may be carried out. Username and Password Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. For tEXistConnection related scenario. This field is automatically populated with the standard driver. depending on their needs. This component is to be used along with the other tEXist components such as tEXistGet and tEXistPut. see tMysqlConnection on page 460. It usually does not make much sense to use one of these without using a tEXistConnection component to open a connection for the current transaction. n/a Usage Limitation Related scenarios This component is closely related to tEXistGet and tEXistPut.Databases components tEXistConnection tEXistConnection tEXistConnection properties This component is closely related to tEXistGet and tEXistPut. Creative Commons License Talend Open Studio Components 271 . Once you have set the connection properties in this component.

Users can enter a different driver. see your studio user guide. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined. This field is automatically populated with the standard driver. Select this check box to gather the job processing metadata at a job level as well as at each component level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Component list presents only the connection components in the same Job level. URI Collection Driver URI of the database you want to connect to. make sure that the available connection components are sharing the intended connection. When a Job contains the parent Job and the child Job.. Enter the path to the collection of interest on the database server. Username and Password Target Type Files Advanced settings tStatCatcher Statistics 272 Talend Open Studio Components Creative Commons License . In this case.Databases components tEXistDelete tEXistDelete tEXistDelete properties Component family Databases/eXist Function Purpose Basic settings This component deletes resources from an eXist database. Otherwise. or All. tEXistDelete deletes specified resources from remote eXist databases. Click the plus button to add the lines you want to use as filters: Filemask: enter the filename or filemask using wildcharacters (*) or regular expressions. Collection. Either Resource. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. User authentication information. so if you need to use an existing connection from the other level. For more information on how to share a DB connection across Job levels. make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings. depending on their needs.

n/a Related scenario No scenario is available for this component yet.Databases components tEXistDelete Usage Limitation This component is typically used as a single component sub-job but can also be used as an output or end object. Creative Commons License Talend Open Studio Components 273 .

see Use or register a shared DB connection in any database connection component corresponding to the database you are using. see your studio user guide. make sure the connection name is unique and distinctive all over through the two Job levels. Users can enter a different driver. Enter the path to the collection of interest on the database server. Otherwise. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined. This field is automatically populated with the standard driver. In this case. depending on their needs. When a Job contains the parent Job and the child Job.Databases components tEXistGet tEXistGet tEXistGet properties Component family Databases/eXist Function Purpose Basic settings This component retrieves resources from a remote DB server. URI Collection Driver URI of the database you want to connect to. make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels. so if you need to use an existing connection from the other level. tEXistGet downloads selected resources from a remote DB server to a defined local directory. Click the plus button to add the lines you want to use as filters: Filemask: enter the filename or filemask using wildcharacters (*) or regular expressions Username and Password Local directory Files 274 Talend Open Studio Components Creative Commons License . Component list presents only the connection components in the same Job level. For more information about Dynamic settings. User authentication information. Path to the file’s destination location. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.

n/a Related scenario No scenario is available for this component yet. Usage Limitation This component is typically used as a single component sub-job but can also be used as an output or end object. Creative Commons License Talend Open Studio Components 275 .Databases components tEXistGet Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level.

Click the plus button to add the lines you want to use as filters:. When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. Filemask: enter the filename or filemask using wildcharacters (*) or regular expressions.. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Enter the path to the collection of interest on the database server. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined. depending on their needs. Component list presents only the connection components in the same Job level. make sure that the available connection components are sharing the intended connection. make sure the connection name is unique and distinctive all over through the two Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. URI Collection Driver URI of the database you want to connect to. Server authentication information. Users can enter a different driver.Databases components tEXistList tEXistList tEXistList properties Component family Databases/eXist Function Purpose Basic settings This component lists the resources stored on a remote DB server. Either Resource. so if you need to use an existing connection from the other level. Collection or All contents: Username and Password Files Target Type 276 Talend Open Studio Components Creative Commons License . Otherwise. tEXistList lists the resources stored on a remote database server. This field is automatically populated with the standard driver. see your studio user guide. For more information about Dynamic settings. In this case.

n/a Related scenarios For a tEXistList related scenario. Usage Limitation This component is typically used along with a tEXistGet component to retrieve the files listed. see Scenario: Iterating on a remote directory on page 929 Creative Commons License Talend Open Studio Components 277 .Databases components tEXistList Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. for example.

make sure that the available connection components are sharing the intended connection. URI Collection Driver URI of the database you want to connect to. For more information on how to share a DB connection across Job levels. Users can enter a different driver. tEXistPut uploads specified files from a defined local directory to a remote DB server. Component list presents only the connection components in the same Job level. Enter a path to indicate where the resource is to be saved on the server. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job. Username and Password Local directory Files 278 Talend Open Studio Components Creative Commons License . In this case. For more information about Dynamic settings. Filemask: enter the filename or filemask using wildcharacters (*) or regular expressions. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined. see your studio user guide. depending on their needs. Click the plus button to add the lines you want to use as filters:. Otherwise. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.Databases components tEXistPut tEXistPut tEXistPut properties Component family Databases/eXist Function Purpose Basic settings This component uploads resources to a DB server. make sure the connection name is unique and distinctive all over through the two Job levels. User authentication information. Path to the source location of the file(s). so if you need to use an existing connection from the other level. This field is automatically populated with the standard driver.

Usage Limitation This component is typically used as a single component sub-job but can also be used as an output or end object. Creative Commons License Talend Open Studio Components 279 .Databases components tEXistPut Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. n/a Related scenario No scenario is available for this component yet.

Component list presents only the connection components in the same Job level.Databases components tEXistXQuery tEXistXQuery tEXistXQuery properties Component family Databases/eXist Function Purpose Basic settings This component uses local files containing XPath queries to query XML files stored on remote databases. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined. make sure that the available connection components are sharing the intended connection. For more information about Dynamic settings. Username and Password XQuery Input File Local Output 280 Talend Open Studio Components Creative Commons License . URI Collection Driver URI of the database you want to connect to. For more information on how to share a DB connection across Job levels. Users can enter a different driver. so if you need to use an existing connection from the other level. Enter the path to the XML file location on the database. Browse to the directory in which the query results should be saved. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. This field is automatically populated with the standard driver. DB server authentication information. tEXistXQuery queries XML files located on remote databases and outputs the results to an XML file stored locally. make sure the connection name is unique and distinctive all over through the two Job levels. Otherwise. depending on their needs. When a Job contains the parent Job and the child Job. see your studio user guide. In this case. Browse to the local file containing the query to be executed. see Use or register a shared DB connection in any database connection component corresponding to the database you are using.

Databases components tEXistXQuery Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Usage Limitation This component is typically used as a single component Job but can also be used as part of a more complex Job. Creative Commons License Talend Open Studio Components 281 . n/a Related scenario No scenario is available for this component yet.

make sure that the available connection components are sharing the intended connection. so if you need to use an existing connection from the other level. tEXistXUpdate processes XML file records and updates the existing records on the DB server.. DB server authentication information. Component list presents only the connection components in the same Job level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Users can enter a different driver. Username and Password Update File Advanced settings tStatCatcher Statistics 282 Talend Open Studio Components Creative Commons License . make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings. For more information on how to share a DB connection across Job levels. Enter the path to the collection and file of interest on the database server. This field is automatically populated with the standard driver. When a Job contains the parent Job and the child Job. see your studio user guide. depending on their needs. URI Collection Driver URI of the database you want to connect to. Otherwise. In this case. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Select this check box to gather the job processing metadata at a job level as well as at each component level. Use an existing Select this check box and click the relevant connection/Compon tEXistConnection component on the ent List Component list to reuse the connection details you already defined.Databases components tEXistXUpdate tEXistXUpdate tEXistXUpdate properties Component family Databases/eXist Function Purpose Basic settings This component processes XML file records and updates the records on the DB server. Browse to the local file in the local directory to be used to update the records on the database.

n/a Related scenario No scenario is available for this component yet. Creative Commons License Talend Open Studio Components 283 .Databases components tEXistXUpdate Usage Limitation This component is typically used as a single component sub-job but can also be used as part of a more complex Job.

n/a Related scenario No scenario is available for this component yet.Databases components tFirebirdClose tFirebirdClose tFirebirdClose properties Component family Databases/Firebird Function Purpose Basic settings tFirebirdClose closes the transaction committed in the connected DB. 284 Talend Open Studio Components Creative Commons License . Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component list Select the tFirebirdConnection component in the list if more than one connection are planned for the current Job. especially with tFirebirdConnection and tFirebirdCommit. This component is to be used along with Firebird components. Close a transaction.

If you want to use a Row > Main connection to link tAS400Commit to your Job. In this case.Databases components tFirebirdCommit tFirebirdCommit tFirebirdCommit Properties This component is closely related to tFirebirdConnection and tFirebirdRollback. especially with tFirebirdConnection and tFirebirdRollback components. Using a unique connection. It usually doesn’t make much sense to use one of these without using a tFirebirdConnection component to open a connection for the current transaction. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. your data will be commited row by row. It allows you to close the database connection once the commit is done. This component is to be used along with Firebird components. see tMysqlConnection on page 460. Component list Select the tFirebirdConnection component in the list if more than one connection are planned for the current Job. n/a Related scenario This component is closely related to tFirebirdConnection and tFirebirdRollback. It usually doesn’t make much sense to use these components independently in a transaction. This check box is selected by default. Creative Commons License Talend Open Studio Components 285 . Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component family Databases/Firebird Function Purpose Validates the data processed through the Job into the connected DB. Clear this check box to continue to use the selected connection once the component has performed its task. For tFirebirdCommit related scenario. do not select the Close connection check box or your connection will be closed before the end of your first row commit.

Name of the database. 286 Talend Open Studio Components Creative Commons License . n/a Related scenarios This component is closely related to tFirebirdCommit and tFirebirdRollback. Property type Either Built-in or Repository. It usually does not make much sense to use one of these without using a tFirebirdConnection to open a connection for the current transaction. DB user authentication data. once the data has been validated. This component allows you to commit all of the Job data to an output database in just a single transaction. Shared DB Connection Name: set or type in the shared connection name. Built-in: No property data stored centrally..Databases components tFirebirdConnection tFirebirdConnection tFirebirdConnection properties This component is closely related to tFirebirdCommit and tFirebirdRollback. Repository: Select the repository file where Properties are stored. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Usage Limitation This component is to be used along with Firebird components. Host name Database Username and Password Use or register a shared DB Connection Database server IP address. It usually does not make much sense to use one of these without using a tFirebirdConnection component to open a connection for the current transaction. The fields that come after are pre-filled in using the fetched data. Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. Select this check box to automatically commit a transaction when it is completed. Component family Databases/Firebird Function Purpose Basic settings tFirebirdConnection opens a connection to the database for a current transaction. especially with tFirebirdCommit and tFirebirdRollback. Select this check box to share your connection or fetch a connection shared by a parent or child Job.

Databases components tFirebirdConnection For tFirebirdConnection related scenario. Creative Commons License Talend Open Studio Components 287 . see tMysqlConnection on page 460.

helps to decide the row set to work with at a time and thus optimize performance. This field is compulsory for DB data handling. Host Database Username and Password Schema and Edit Schema Database server IP address Name of the database DB user authentication data. 288 Talend Open Studio Components Creative Commons License . Built-in: The schema is created and stored locally for this component only. Enable stream Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. i. The fields that come after are pre-filled in using the fetched data. Remove leading and trailing whitespace from defined columns. tFirebirdInput executes a DB query with a strictly defined order which must correspond to the schema definition. Property type Either Built-in or Repository Built-in: No property data stored centrally. Basic settings Advanced Settings Encoding Type Select the encoding type from the list or select Custom and define it manually. it defines the number of fields to be processed and passed on to the next component.Databases components tFirebirdInput tFirebirdInput tFirebirdInput properties Component family Databases/FireBird Function Purpose tFirebirdInput reads a database and extracts fields based on a query. Then it passes on the field list to the next component via a Main row link. The schema is either built-in or remotely stored in the Repository.. A schema is a row description. hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. When selected. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Repository: Select the repository file where Properties are stored. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.

Creative Commons License Talend Open Studio Components 289 . see generic tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Related scenarios For related topics.Databases components tFirebirdInput Usage This component covers all possibilities of SQL queries onto a FireBird database.

Note that only one table can be written at a time On the table defined. based on the flow incoming from the preceding component in the Job. Create a table if not exists: The table is created if it does not exist.Databases components tFirebirdOutput tFirebirdOutput tFirebirdOutput properties Component family Databases/FireBird Function Purpose tFirebirdOutput writes. Host Port Database Username and Password Table Action on table Database server IP address Listening port number of DB server. Name of the table to be written. Basic settings 290 Talend Open Studio Components Creative Commons License . Drop a table if exists and create: The table is removed if it already exists and created again. updates. Property type Either Built-in or Repository. tFirebirdOutput executes the action defined on the table and/or on the data contained in the table. you can perform one of the following operations: None: No operation is carried out. Name of the database DB user authentication data. Create a table: The table does not exist and gets created. Drop and create a table: The table is removed and created again. makes changes or suppresses entries in a database. Clear a table: The table content is deleted. The fields that come after are pre-filled in using the fetched data. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored.

click the Advanced settings view where you can simultaneously define primary keys for the update and delete operations.e. Clear the check box to skip the row on error and complete the process for error-free rows. better performance at execution. This option ensures transaction quality (but not rollback) and. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Enter the number of rows to be completed before committing batches of rows together into the DB. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. you can perform: Insert: Add new entries to the table. Repository: The schema already exists and is stored in the Repository. If needed. above all. Die on error This check box is selected by default. You must specify at least one column as a primary key on which the Update and Delete operations are based. Job stops. If duplicates are found. it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. select the check boxes next to the column name on which you want to base the update operation. i. Select the encoding type from the list or select Custom and define it manually. This field is compulsory for DB data handling. Do the same in the Key in delete column for the deletion operation Schema and Edit Schema A schema is a row description.Databases components tFirebirdOutput Action on data On the data of the table defined. For an advanced use. you can retrieve the rows on error via a Row > Rejects link. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Related topic: Setting a built-in schema of Talend Open Studio User Guide. Advanced settings Encoding Type Commit every Creative Commons License Talend Open Studio Components 291 . hence can be reused. To do that: Select the Use field options check box and then in the Key in update column.. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow.

Use field options Enable debug mode Select this check box to customize a request. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. Position: Select Before. especially when there is double action on data. For an example of tMySqlOutput in use. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. which are not insert. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. or action that require particular preprocessing.Databases components tFirebirdOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. This component must be used as an output component. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. It allows you to carry out actions on a table or on the data of a table in a Firebird database. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. This option allows you to call SQL functions to perform actions on columns. tStatCatcher Statistics Select this check box to collect log data at the component level. nor update or delete actions. 292 Talend Open Studio Components Creative Commons License . Replace or After following the action to be performed on the reference column. Select this check box to display each step during processing entries in a database.

it defines the number of fields to be processed and passed on to the next component. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. Host Database Username and Password Schema and Edit Schema Database server IP address Name of the database DB user authentication data. Purpose Basic settings Creative Commons License Talend Open Studio Components 293 . Repository: Select the repository file where Properties are stored. see your studio user guide.e. make sure that the available connection components are sharing the intended connection.Databases components tFirebirdRow tFirebirdRow tFirebirdRow properties Component family Databases/FireBird Function tFirebirdRow is the specific component for this database query. The schema is either built-in or remotely stored in the Repository. For more information about Dynamic settings. The SQLBuilder tool helps you write easily your SQL statements. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Otherwise. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. It executes the SQL query stated onto the specified database. Property type Either Built-in or Repository. Component list presents only the connection components in the same Job level. A schema is a row description. The fields that come after are pre-filled in using the fetched data.. so if you need to use an existing connection from the other level. Use an existing connection Select this check box and click the relevant tFirebirdConnection component on the Component list to reuse the connection details you already defined. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Depending on the nature of the query and the database. When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. i. tFirebirdRow acts on the actual DB structure or on the data (although without handling data). Built-in: No property data stored centrally.

hence can be reused. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Repository: The schema already exists and is stored in the Repository. Select this checkbox if you want to query the database using a PreparedStatement. The Query field gets accordingly filled in. Parameter Value: Enter the parameter value. This option is very useful if you need to execute the same query several times. Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. This field is compulsory for DB data handling. Select this check box to insert the result of the query into a COLUMN of the current flow. Related topic: Setting a Repository schema of Talend Open Studio User Guide. If needed. 294 Talend Open Studio Components Creative Commons License . Clear the check box to skip the row on error and complete the process for error-free rows. This check box is selected by default. Select this column from the use column list. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository.Databases components tFirebirdRow Built-in: The schema is created and stored locally for this component only. Parameter Index: Enter the parameter position in the SQL instruction. Query type Either Built-in or Repository. Parameter Type: Enter the parameter type. In the Set PreparedStatement Parameter table. Number of rows to be completed before committing batches of rows together into the DB. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. you can retrieve the rows on error via a Row > Rejects link. Performance levels are increased Encoding Type Select the encoding from the list or select Custom and define it manually. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This option ensures transaction quality (but not rollback) and above all better performance on executions.

see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Creative Commons License Talend Open Studio Components 295 .Databases components tFirebirdRow Related scenarios For related topics.

DB user authentication data. The fields that come after are pre-filled in using the fetched data. Use an existing connection Select this check box if you use a configured tGreenplumConnection. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. make sure the connection name is unique and distinctive all over through the two Job levels. which details are given in a different section. In this case. Component list presents only the connection components in the same Job level. tGreenplumBulkExec is a component which is specifically designed to improve performance when loading data in ParAccel database. When a Job contains the parent Job and the child Job. Property type Either Built-in or Repository Built-in: No property data stored centrally. 296 Talend Open Studio Components Creative Commons License .Databases components tGreenplumBulkExec tGreenplumBulkExec tGreenplumBulkExec Properties tGreenplumOutputBulk and tGreenplumlBulkExec components are generally used together. For more information about Dynamic settings. For more information on how to share a DB connection across Job levels. This execution in two steps is unified in the tGreenplumOutputBulkExec component. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Listening port number of DB server. Otherwise. make sure that the available connection components are sharing the intended connection. Repository: Select the repository file where Properties are stored. Component Family Databases/Greenplum Function Purpose Basic settings tGreenplumBulkExec performs an Insert action on the data. The point of offering two separated components is to enable you to do transformations before changing data in the database. to generate the output file which will be used as a parameter in the SQL query execution. see your studio user guide. Name of the database. Host Port Database Schema Username and Password Database server IP address. so if you need to use an existing connection from the other level. Exact name of the schema.

Drop and create a table: The table is removed and created again. A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide.. Character. with the names of each column in the file File type Null string Fields terminated by Escape char Text enclosure Force not null for columns Select the file type to process. tStatCatcher Statistics Select this check box to collect log data at the component level.e. Clear a table: The table content is deleted. The schema is either built-in or remotely stored in the Repository. Create a table: The table does not exist and gets created. Filename Schema and Edit Schema Advanced settings Action on data Select the operation you want to perform: Bulk insert Bulk update The details asked will be different according to the action chosen.Databases components tGreenplumBulkExec Table Action on table Name of the table to be written. Creative Commons License Talend Open Studio Components 297 . Note that only one table can be written at a time On the table defined. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. it defines the number of fields to be processed and passed on to the next component. string or regular expression to separate fields. Define the columns nullability Force not null:: Select the check box next to the column you want to define as not null. Path and name of the file to be processed. Character of the row to be escaped Character used to enclose text. String displayed to indicate that the value is null. i. Create a table if not exists: The table is created if it does not exist. Drop a table if exists and create: The table is removed if it already exists and created again. hence can be reused. row Contains a header line Specify that the table contains header. Copy the OID for each Retrieve the ID item for each row. Built-in: The schema is created and stored locally for this component only. you can perform one of the following operations: None: No operation is carried out.

Related scenarios For more information about tGreenplumBulkExec. Used together they offer gains in performance while feeding a Greenplum database. • Scenario: Truncating and inserting file data into Oracle DB on page 538 from tOracleBulkExec. see: • Scenario: Inserting transformed data in MySQL database on page 490 from tMysqlOutputBulk. • Scenario: Inserting data in MySQL database on page 495 from tMysqlOutputBulkExec.Databases components tGreenplumBulkExec Usage This component is generally used with a tGreenplumOutputBulk component. 298 Talend Open Studio Components Creative Commons License .

n/a Related scenario No scenario is available for this component yet.Databases components tGreenplumClose tGreenplumClose tGreenplumClose properties Component family Databases/Greenplum Function Purpose Basic settings tGreenplumClose closes the transaction committed in the connected DB. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tGreenplumConnection and tGreenplumCommit. Close a transaction. Creative Commons License Talend Open Studio Components 299 . This component is to be used along with Greenplum components. Component list Select the tGreenplumConnection component in the list if more than one connection are planned for the current Job.

do not select the Close connection check box or your connection will be closed before the end of your first row commit. n/a Related scenario This component is closely related to tGreenplumConnection and tGreenplumRollback. In this case.Databases components tGreenplumCommit tGreenplumCommit tGreenplumCommit Properties This component is closely related to tGreenplumConnection and tGreenplumRollback. 300 Talend Open Studio Components Creative Commons License . Component list Select the tGreenplumConnection component in the list if more than one connection are planned for the current Job. especially with tGreenplumConnection and tGreenplumRollback components. This check box is selected by default. your data will be commited row by row. This component is to be used along with Greenplum components. see tMysqlConnection on page 460. It usually doesn’t make much sense to use one of these without using a tGreenplumConnection component to open a connection for the current transaction. Component family Databases/Greenplum Function Purpose Validates the data processed through the Job into the connected DB. It allows you to close the database connection once the commit is done. It usually doesn’t make much sense to use these components independently in a transaction. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. If you want to use a Row > Main connection to link tAS400Commit to your Job. For tGreenplumCommit related scenario. Using a unique connection. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. Clear this check box to continue to use the selected connection once the component has performed its task.

Name of the database. Select this check box to share your connection or fetch a connection shared by a parent or child Job. especially with tGreenplumCommit and tGreenplumRollback. It usually does not make much sense to use one of these without using a tGreenplumConnection to open a connection for the current transaction. Exact name of the schema. This field is compulsory for DB data handling. Repository: Select the repository file where Properties are stored. Select the encoding type from the list or select Custom and define it manually. n/a Creative Commons License Talend Open Studio Components 301 . Listening port number of DB server. The fields that come after are pre-filled in using the fetched data. This component allows you to commit all of the Job data to an output database in just a single transaction. DB user authentication data. Select this check box to automatically commit a transaction when it is completed. Shared DB Connection Name: set or type in the shared connection name. Property type Either Built-in or Repository.Databases components tGreenplumConnection tGreenplumConnection tGreenplumConnection properties This component is closely related to tGreenplumCommit and tGreenplumRollback. Usage Limitation This component is to be used along with Greenplum components. Host Port Database Schema Username and Password Encoding Type Database server IP address. Use or register a shared DB Connection Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. once the data has been validated. Built-in: No property data stored centrally. Component family Databases/Greenplum Function Purpose Basic settings tGreenplumConnection opens a connection to the database for a current transaction.

It usually does not make much sense to use one of these without using a tGreenplumConnection component to open a connection for the current transaction. see tMysqlConnection on page 460. 302 Talend Open Studio Components Creative Commons License . For tGreenplumConnection related scenario.Databases components tGreenplumConnection Related scenarios This component is closely related to tGreenplumCommit and tGreenplumRollback.

Property type Either Built-in or Repository Built-in: No property data stored centrally. The schema is either built-in or remotely stored in the Repository. hence can be reused. i. tGreenplumInput executes a DB query with a strictly defined order which must correspond to the schema definition. A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. see Setting up a DB connection of Talend Open Studio User Guide. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.Databases components tGreenplumInput tGreenplumInput tGreenplumInput properties Component family Databases/Greenplum Function Purpose tGreenplumInput reads a database and extracts fields based on a query.. Then it passes on the field list to the next component via a Main row link. DB user authentication data. Repository: The schema already exists and is stored in the Repository. Listening port number of DB server. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: Select the repository file where Properties are stored. Name of the database. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. For more information about setting up and storing database connection parameters. Exact name of the schema. Built-in: The schema is created and stored locally for this component only. Host Port Database Schema Username and Password Schema and Edit Schema Database server IP address. Basic settings Creative Commons License Talend Open Studio Components 303 . The fields that come after are pre-filled in using the fetched data.e.

When selected. This field is compulsory for DB data handling. Usage This component covers all possibilities of SQL queries onto a FireBird database. see generic tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios For related topics.Databases components tGreenplumInput Guess schema Advanced settings Encoding Type Click the Guess schema button to retrieve the table schema. Remove leading and trailing whitespace from defined columns. 304 Talend Open Studio Components Creative Commons License . Select this check box to remove leading and trailing whitespace from all the String/Char columns. helps to decide the row set to work with at a time and thus optimize performance. Select the encoding type from the list or select Custom and define it manually.

Host Port Database Username and Password Database server IP address. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise. see your studio user guide. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. modifies or deletes the data in a database. make sure that the available connection components are sharing the intended connection. The fields that come after are pre-filled in using the fetched data. For more information about setting up and storing database connection parameters. make sure the connection name is unique and distinctive all over through the two Job levels. Creative Commons License Talend Open Studio Components 305 . When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. tGreenplumOutput executes the action defined on the table and/or on the data of a table. In this case. Listening port number of DB server.Databases components tGreenplumOutput tGreenplumOutput tGreenplumOutput Properties Component Family Databases/Greenplum Function Purpose Basic settings tGreenplumOutput writes. so if you need to use an existing connection from the other level. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. updates. For more information about Dynamic settings. Component list presents only the connection components in the same Job level. Use an existing connection Select this check box if you use a configured tGreenplumConnection. see Setting up a DB connection of Talend Open Studio User Guide. Name of the database DB user authentication data. according to the input flow form the previous component. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository Built-in: No property data stored centrally.

it defines the number of fields to be processed and passed on to the next component. If duplicates are found. Related topic: Setting a built-in schema of Talend Open Studio User Guide. hence can be reused. you can perform one of the following operations: None: No operation is carried out. On the data of the table defined. Clear a table: The table content is deleted. To do that: Select the Use field options check box and then in the Key in update column. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. select the check boxes next to the column names you want to use as a base for the Update operation. Drop and create a table: The table is removed and created again. Create a table if not exists: The table is created if it does not exist. 306 Talend Open Studio Components Creative Commons License . Update: Make changes to existing entries Insert or update: Add entries or update existing ones.. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Drop a table if exists and create: The table is removed if it already exists and created again.Databases components tGreenplumOutput Table Action on table Name of the table to be written. Repository: The schema already exists and is stored in the Repository. Action on data Schema and Edit Schema A schema is a row description. you can perform: Insert: Add new entries to the table. Do the same in the Key in delete column for the Delete operation. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Job stops. Create a table: The table does not exist and gets created. For an advanced use. Note that only one table can be written at a time On the table defined. The schema is either built-in or remotely stored in the Repository. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. i.e. Built-in: The schema is created and stored locally for this component only.

It allows you to do actions on a table or the data in a table in a Greenplum database. Enter the number of rows to be completed before committing batches of rows together into the DB. you can retrieve the rows on error via a Row > Rejects link. above all. Related scenarios For a related scenario.Databases components tGreenplumOutput Die on error This check box is selected by default. better performance at execution. Usage This component covers all possibilities of SQL queries onto a database. This field is compulsory for DB data handling. • Scenario 1: Adding a new column and altering data in a DB table on page 476 from tMySQLOutput. For a usage example. which are not insert. If needed. Creative Commons License Talend Open Studio Components 307 . Replace or After following the action to be performed on the reference column. It enables you to create a reject flow. nor update or delete actions. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. or action that require particular preprocessing. with a Row > Rejects link filtering the data in error. This option is not offered if you create (with or without drop) the DB table. This option allows you to call SQL functions to perform actions on columns. tStatCatcher Statistics Select this check box to collect log data at the component level. Position: Select Before. Select the encoding type from the list or select Custom and define it manually. Advanced settings Encoding Type Commit every Additional Columns Use field options Select this check box to customize a request. see: • Scenario: Displaying DB output on page 258 from tDBOutput. This option ensures transaction quality (but not rollback) and. see Scenario 3: Retrieve data in error with a Reject link on page 483 from component tMysqlOutput. especially when there is double action on data. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. Clear the check box to skip the row on error and complete the process for error-free rows.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select this check to include the column header. Related topic: Setting a built-in schema of Talend Open Studio User Guide. The schema is either built-in or remote in the Repository. detailed in a separate section. string or regular expression to separate fields. it defines the number of fields that will be processed and passed on to the next component. i. These two steps compose the tGreenplumOutputBulkExec component. the fields to follow are pre-filled in using fetched data.. Related topic: Defining variables from the Component view of Talend Open Studio User Guide.e. Property type Either Built-in or Repository. Character. When selected. Component family Databases/Greenplum Function Purpose Basic settings Writes a file with columns based on the defined delimiter and the Greenplum standards Prepares the file to be used as parameter in the INSERT query to feed the Greenplum database. Append Schema and Edit Schema Advanced settings Row separator Field separator Include header String (ex: “\n”on Unix) to distinguish rows. Repository: The schema already exists and is stored in the Repository. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Repository: Select the Repository file where Properties are stored. Select this check box to add the new rows at the end of the records A schema is a row description. Built-in: No property data stored centrally.Databases components tGreenplumOutputBulk tGreenplumOutputBulk tGreenplumOutputBulk properties tGreenplumOutputBulk and tGreenplumBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. 308 Talend Open Studio Components Creative Commons License . File Name Name of the file to be processed. hence can be reused in various projects and job designs. Built-in: The schema will be created and stored locally for this component only.

Related scenarios For uses cases in relation with tGreenplumOutputBulk. tStaCatcher statistics Usage This component is to be used along with tGreenplumBulkExec component. Select this check box to collect log data at the component level. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 Creative Commons License Talend Open Studio Components 309 . Used together they offer gains in performance while feeding a Greenplum database.Databases components tGreenplumOutputBulk Encoding Type Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

A schema is a row description. Name of the file to be processed. Name of the table to be written. Create a table if not exists: The table is created if it does not exist. Built-in: No property data stored centrally. The schema is either built-in or remotely stored in the Repository. Create a table: The table does not exist and gets created. you can perform one of the following operations: None: No operation is carried out. DB user authentication data. Name of the database. Repository: Select the repository file where Properties are stored. Host Port Database name Schema Username and Password Table Database server IP address Listening port number of DB server. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. Drop and create a table: The table is removed and created again. i. Property type Either Built-in or Repository.. You have the possibility to rollback the operation. The fields that come after are pre-filled in using the fetched data. it defines the number of fields to be processed and passed on to the next component. Clear a table: The table content is deleted.Databases components tGreenplumOutputBulkExec tGreenplumOutputBulkExec tGreenplumOutputBulkExec properties Component family Databases/Greenplum Function Purpose Basic settings Executes the action on the data provided. it allows gains in performance during Insert operations to a Greenplum database. Built-in: You create and store the schema locally for this component only. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Exact name of the schema. As a dedicated component. Action on table File Name Schema and Edit Schema 310 Talend Open Studio Components Creative Commons License . On the table defined.

Select this check box to collect log data at the component level. String (ex: “\n”on Unix) to distinguish rows. string or regular expression to separate fields. You can reuse it in various projects and job flowcharts. with the names of each column in the file File type Null string Row separator Fields terminated by Escape char Text enclosure Force not null for columns tStatCatcherStatistics Usage Limitation Select the file type to process. row Contains a header line Specify that the table contains header. String displayed to indicate that the value is null. Advanced settings Action on data Select the operation you want to perform: Bulk insert Bulk update The details asked will be different according to the action chosen. This component is mainly used when no particular transformation is required on the data to be loaded onto the database. Character of the row to be escaped Character used to enclose text.Databases components tGreenplumOutputBulkExec Repository: You have already created the schema and stored it in the Repository. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 Creative Commons License Talend Open Studio Components 311 . Related topic: Setting a Repository schema of Talend Open Studio User Guide. Copy the OID for each Retrieve the ID item for each row. Define the columns nullability Force not null: Select the check box next to the column you want to define as not null. Character. n/a Related scenarios For uses cases in relation with tGreenplumOutputBulkExec.

Avoids to commit part of a transaction involuntarily. Clear this check box to continue to use the selected connection once the component has performed its task. It usually does not make much sense to use these components independently in a transaction. 312 Talend Open Studio Components Creative Commons License . Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tGreenplumRollback tGreenplumRollback tGreenplumRollback properties This component is closely related to tGreenplumCommit and tGreenplumConnection. especially with tGreenplumConnection and tGreenplumCommit. This component is to be used along with Greenplum components. Component list Select the tGreenplumConnection component in the list if more than one connection are planned for the current Job. see Scenario: Rollback from inserting data in mother/daughter tables on page 498. n/a Related scenarios For tGreenplumRollback related scenario. Component family Databases/Greenplum Function Purpose Basic settings tGreenplumRollback cancels the transaction committed in the connected DB.

In this case. Otherwise. For more information on how to share a DB connection across Job levels. Component list presents only the connection components in the same Job level. see your studio user guide. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Repository: Select the repository file where Properties are stored. The row suffix means the component implements a flow in the job design although it doesn’t provide output. It executes the SQL query stated onto the specified database. Name of the database Exct name of the schema. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Use an existing connection Select this check box and click the relevant tFirebirdConnection component on the Component list to reuse the connection details you already defined. The fields that come after are pre-filled in using the fetched data. Depending on the nature of the query and the database. make sure the connection name is unique and distinctive all over through the two Job levels. Purpose Basic settings Creative Commons License Talend Open Studio Components 313 . so if you need to use an existing connection from the other level. For more information about Dynamic settings. tGreenplumRow acts on the actual DB structure or on the data (although without handling data). DB user authentication data. The SQLBuilder tool helps you write easily your SQL statements. make sure that the available connection components are sharing the intended connection. Host Port Database Schema Username et Password Database server IP address Listening port number of DB server. Property type Either Built-in or Repository. When a Job contains the parent Job and the child Job. Built-in: No property data stored centrally.Databases components tGreenplumRow tGreenplumRow tGreenplumRow Properties Component Family Databases/Greenplum Function tGreenplumRow is the specific component for this database query.

Performance levels are increased Query Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. The Query field gets accordingly filled in. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Related topic: Setting a Repository schema of Talend Open Studio User Guide. If needed.e. hence can be reused.. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder. Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. This option is very useful if you need to execute the same query several times. you can retrieve the rows on error via a Row > Rejects link. This check box is selected by default. it defines the number of fields to be processed and passed on to the next component. Parameter Type: Enter the parameter type. Table Name Query type Name of the table to be read. Select this checkbox if you want to query the database using a PreparedStatement. define the represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Built-in: The schema is created and stored locally for this component only. 314 Talend Open Studio Components Creative Commons License . Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Either Built-in or Repository. In the Set PreparedStatement Parameter table. Select this check box to insert the result of the query into a COLUMN of the current flow.Databases components tGreenplumRow Schema and Edit Schema A schema is a row description. Parameter Value: Enter the parameter value. Repository: The schema already exists and is stored in the Repository. Clear the check box to skip the row on error and complete the process for error-free rows. i. This field is compulsory for DB data handling. Parameter Index: Enter the parameter position in the SQL instruction. Repository: Select the relevant query stored in the Repository. Select this column from the use column list.

tStatCatcher Statistics Select this check box to collect log data at the component level. see: • Scenario: Resetting a DB auto-increment on page 262 from tDBSQLRow. • Scenario 1: Removing and regenerating a MySQL table index on page 502 from tMySQLRow. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. This option ensures transaction quality (but not rollback) and above all better performance on executions. Creative Commons License Talend Open Studio Components 315 .Databases components tGreenplumRow Commit every Number of rows to be completed before committing batches of rows together into the DB. Related scenarios For a related scenario.

see tGreenplumSCD on page 7. For more information on it. 316 Talend Open Studio Components Creative Commons License .Databases components tGreenplumSCD tGreenplumSCD tGreenplumSCD belongs to two component families: Business Intelligence and Databases.

tStatCatcher Statistics Select this check box to collect the log data at a component level. It requires an output component. Creative Commons License Talend Open Studio Components 317 . see tMysqlConnection on page 460. Component list If there is more than one connection used in the Job. It is generally used along with tHiveConnection as the latter allows you to open a connection for the transaction which is underway. select tHiveConnection from the list. This component closes connection to a Hive databases. This component is generally used as an input component.Databases components tHiveClose tHiveClose tHiveClose properties Component Family Databases/Hive Function Purpose Basic settings Advanced settings Usage Limitation tHiveClose closes an active connection to a database. n/a Related scenario This component is for use with tHiveConnection. For a scenario in which tHiveClose might be used.

DB user authentication data. This component allows you to commit all of the Job data to an output database in just a single transaction. Property type Built-in or Repository. This field is compulsory for DB data handling. Select this check box to share your connection or fetch a connection shared by a parent or child Job.Databases components tHiveConnection tHiveConnection tHiveConnection properties Database Family Databases/Hive Function Purpose Basic settings tIHiveConnection opens a connection to a database in order that a transaction may be made. Built-in: No property data stored centrally. Name of the database. Host Port Database Username et Password Encoding Type Database server IP address. Repository: Select the repository file where the Properties are stored. see Scenario: Inserting data in mother/daughter tables on page 460. Use or register a shared DB Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect the log data at a component level. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. might be used.. DB server listening port. The fields that follow are filled in automatically using the fetched data. 318 Talend Open Studio Components Creative Commons License . particularly tHiveClose. n/a Related scenario For a scenario in which tHiveConnection. once the data has been validated. This component is generally used with other Informix components. Shared DB Connection Name: set or type in the shared connection name. Select the encoding type from the list or select Custom and define it manually.

The schema is either built-in or remotely stored in the Repository.e. it defines the number of fields to be processed and passed on to the next component. In this case. Use an existing connection Select this check box and click the relevant tHiveConnection component from the Component List to reuse the connection details you already defined. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. The fields that follow are filled in automatically using the fetched data. For more information about Dynamic settings. Purpose Basic settings Creative Commons License Talend Open Studio Components 319 . The row suffix means the component implements a flow in the job design although it doesn’t provide output. see your studio user guide. It executes the SQL query stated in the specified database. Depending on the nature of the query and the database. Repository: Select the repository file where Properties are stored. The SQLBuilder tool helps you write your SQL statements easily. Component list presents only the connection components in the same Job level. A schema is a row description. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. make sure the connection name is unique and distinctive all over through the two Job levels. When a Job contains the parent Job and the child Job. make sure that the available connection components are sharing the intended connection.Databases components tHiveRow tHiveRow tHiveRow properties Component family Databases/Hive Function tHiveRow is the dedicated component for this database.. tHiveRow acts on the actual DB structure or on the data (although without handling data). Property type Either Built-in or Repository. so if you need to use an existing connection from the other level. Otherwise. Name of the database DB user authentication data. Host Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. i. Built-in: No property data stored centrally.

Table Name Query type Name of the table to be processed. Clear the check box to skip the row on error and complete the process for error-free rows. you can retrieve the rows on error via a Row > Rejects link. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Related scenarios For related topics. This field is compulsory for DB data handling. Usage This component offers the benefit of flexible DB queries and covers all possible Hive QL queries. Either Built-in or Repository. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository.Databases components tHiveRow Built-in: The schema is created and stored locally for this component only. Repository: The schema already exists and is stored in the Repository. If needed. This check box is selected by default. Select this column from the use column list. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Select this check box to insert the result of the query into a COLUMN of the current flow. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Query Die on error Advanced settings Propagate QUERY’s recordset Encoding Type tStatCatcher Statistics Select this check box to collect log data at the component level. 320 Talend Open Studio Components Creative Commons License . The Query field gets accordingly filled in. Select the encoding from the list or select Custom and define it manually. hence can be reused.

Database server IP address Listening port number of DB server. A schema is a row description.Databases components tHSQLDbInput tHSQLDbInput tHSQLDbInput properties Component family Databases/HSQLDb Function Purpose tHSQLDbInput reads a database and extracts fields based on a query. The schema is either built-in or remotely stored in the Repository. Repository: The schema already exists and is stored in the Repository. The fields that come after are pre-filled in using the fetched data. i. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. select this check box to enable the secured mode if required. For more information about setting up and storing database connection parameters.. hence can be reused. Repository: Select the repository file where Properties are stored. Running Mode Select on the list the Server Mode corresponding to your DB setup among the four propositions : HSQLDb Server. Built-in: The schema is created and stored locally for this component only. HSQLDb In Memory. tHSQLDbInput executes a DB query with a strictly defined order which must correspond to the schema definition. Basic settings Use TLS/SSL sockets Host Port Database Alias Username and Password Schema and Edit Schema Creative Commons License Talend Open Studio Components 321 . Then it passes on the field list to the next component via a Main row link. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Alias name of the database DB user authentication data. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. HSQLDb WebServer. see Setting up a DB connection of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Property type Either Built-in or Repository Built-in: No property data stored centrally. HSQLDb In Process Persistent. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Related scenarios For related topics. Usage This component covers all possibilities of SQL queries onto an HSQLDb database. Remove leading and trailing whitespace from defined columns. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 322 Talend Open Studio Components Creative Commons License . tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tHSQLDbInput Advanced settings Trim all the String/Char columns Trim column Select this check box to remove leading and trailing whitespace from all the String/Char columns.

Select this check box to enable the secured mode if required. HSQLDb In Process Persistent. tHSQLDbOutput executes the action defined on the table and/or on the data contained in the table.Databases components tHSQLDbOutput tHSQLDbOutput tHSQLDbOutput properties Component family Databases/HSQLDb Function Purpose tHSQLDbOutput writes. The fields that come after are pre-filled in using the fetched data. For more information about setting up and storing database connection parameters. Name of the table to be written. see Setting up a DB connection of Talend Open Studio User Guide. Built-in: No property data stored centrally. Note that only one table can be written at a time Basic settings Use TLS/SSL sockets Host Port Database Username and Password Table Creative Commons License Talend Open Studio Components 323 . HSQLDb In Memory. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Database server IP address Listening port number of DB server. makes changes or suppresses entries in a database. updates. based on the flow incoming from the preceding component in the Job. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. Running Mode Select on the list the Server Mode corresponding to your DB setupamong the four propositions : HSQLDb Server. Name of the database DB user authentication data. HSQLDb WebServer.

Drop a table if exists and create: The table is removed if it already exists and created again. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i.. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. select the check boxes next to the column names you want to use as a base for the Update operation.e. you can perform one of the following operations: None: No operation is carried out. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Create a table if not exists: The table is created if it does not exist. On the data of the table defined. hence can be reused. For an advanced use. Action on data Schema and Edit Schema A schema is a row description. Drop and create a table: The table is removed and created again. you can perform: Insert: Add new entries to the table.Databases components tHSQLDbOutput Action on table On the table defined. Job stops. Create a table: The table does not exist and gets created. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Clear a table: The table content is deleted. Do the same in the Key in delete column for the Delete operation. To do that: Select the Use field options check box and then in the Key in update column. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Repository: The schema already exists and is stored in the Repository. 324 Talend Open Studio Components Creative Commons License . click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. If duplicates are found. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. it defines the number of fields to be processed and passed on to the next component. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s).

Creative Commons License Talend Open Studio Components 325 . better performance at execution. or action that require particular preprocessing. above all. Position: Select Before. For an example of tMySqlOutput in use. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. you can retrieve the rows on error via a Row > Rejects link. If needed. which are not insert. This option ensures transaction quality (but not rollback) and. This component must be used as an output component. Advanced settings Encoding Type Commit every Additional Columns Use field options Enable debug mode Select this check box to customize a request. tStatCatcher Statistics Select this check box to collect log data at the component level. Select the encoding type from the list or select Custom and define it manually. see • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. Replace or After following the action to be performed on the reference column. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. It allows you to carry out actions on a table or on the data of a table in a MySQL database. This field is compulsory for DB data handling. Enter the number of rows to be completed before committing batches of rows together into the DB. This option allows you to call SQL functions to perform actions on columns. Select this check box to display each step during processing entries in a database. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics.Databases components tHSQLDbOutput Die on error This check box is selected by default. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Clear the check box to skip the row on error and complete the process for error-free rows. especially when there is double action on data. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. This option is not offered if you create (with or without drop) the DB table. nor update or delete actions.

Property type Either Built-in or Repository.Databases components tHSQLDbRow tHSQLDbRow tHSQLDbRow properties Component family Databases/HSQLDb Function tHSQLDbRow is the specific component for this database query. The row suffix means the component implements a flow in the job design although it doesn’t provide output. HSQLDb WebServer. HSQLDb In Process Persistent. Depending on the nature of the query and the database.e. Repository: Select the repository file where Properties are stored. it defines the number of fields to be processed and passed on to the next component. Query type Either Built-in or Repository. i. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Running Mode Select on the list the Server Mode corresponding to your DB setup among the four propositions : HSQLDb Server. The Query field gets accordingly filled in.. Name of the database DB user authentication data. Related topic: Setting a Repository schema of Talend Open Studio User Guide. The schema is either built-in or remotely stored in the Repository. hence can be reused. Select this check box to enable the secured mode if required. The fields that come after are pre-filled in using the fetched data. The SQLBuilder tool helps you write easily your SQL statements. A schema is a row description. Repository: The schema already exists and is stored in the Repository. HSQLDb In Memory. Built-in: No property data stored centrally. It executes the SQL query stated onto the specified database. Database server IP address Listening port number of DB server. Built-in: The schema is created and stored locally for this component only. Purpose Basic settings Use TLS/SSL sockets Host Port Database Alias Username and Password Schema and Edit Schema 326 Talend Open Studio Components Creative Commons License . Related topic: Setting a built-in schema of Talend Open Studio User Guide. tHSQLDbRow acts on the actual DB structure or on the data (although without handling data).

If needed. Select this check box to insert the result of the query into a COLUMN of the current flow. Related scenarios For related topics. Clear the check box to skip the row on error and complete the process for error-free rows. Creative Commons License Talend Open Studio Components 327 . This option ensures transaction quality (but not rollback) and above all better performance on executions. Select this column from the use column list. This check box is selected by default.Databases components tHSQLDbRow Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. This field is compulsory for DB data handling. Die on error Advanced settings Propagate QUERY’s recordset Encoding Type Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Select the encoding from the list or select Custom and define it manually. Number of rows to be completed before committing batches of rows together into the DB. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. you can retrieve the rows on error via a Row > Rejects link.

tInformixBulkExec is a dedicated component which improves performance during Insert operations in Informix databases. For more information on how to share a DB connection across Job levels. Name of the Informix instance to be used. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. see your studio user guide. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. make sure the connection name is unique and distinctive all over through the two Job levels. Component list presents only the connection components in the same Job level. so if you need to use an existing connection from the other level. Execution Platform Use an existing connection Select the operating system you are using. This information can generally be found in the SQL hosts file. make sure that the available connection components are sharing the intended connection. Otherwise. 328 Talend Open Studio Components Creative Commons License . Repository: Select the repository file where Properties are stored. Name of the schema. DB user authentication data. When a Job contains the parent Job and the child Job. Select this check box and click the relevant tInformixBulkExec component on the Component List to reuse the connection details you already defined. In this case. The fields that come after are pre-filled in using the fetched data. Name of the database. Host Port Database Schema Username et Password Instance Database server IP address. For more information about Dynamic settings. DB server listening port.Databases components tInformixBulkExec tInformixBulkExec tInformixBulkExec Properties Component Family Databases/Informix Function Purpose Basic settings tInformixBulkExec executes Insert operations on the data supplied. Property type Built-in or Repository Built-in: No property data stored centrally.

Related topic:Defining variables from the Component view of Talend Open Studio User Guide. If duplicates are found. you can perform one of the following operations: None: No operation is carried out. Clear a table: The table content is deleted. you can perform the following operations: Insert: Add new data to the table. Delete: Delete the entry data which corresponds to the input flow.e. Schema and Edit Schema Informix Directory Data file Indicate the access path to your Informix directory. Note that only one table can be written at a time. Insert or update: Add data or update the existing data. Drop a table if exists and create: The table is removed if it already exists and created again. On the table defined. The schema is either built-in or remotely stored in the Repository. i. On the data of the table defined. Action on data Creative Commons License Talend Open Studio Components 329 . from both the Basic Settings and the Advanced Settings. A schema is a row description. Name of the file to be processed. Update: Update the existing table data. Create a table: The table does not exist and gets created. Drop and create a table: The table is removed and created again. to optimise these operations. hence can be reused in various projects and job designs. Update or insert : Update the existing entries or create them if they do not already exist. It is possible to define the columns which should be used as the key from the schema. it defines the number of fields to be processed and passed on to the next component. the job stops. Repository: The schema already exists and is stored in the Repository. You must specify at least one key upon which the Update and Delete operations are to be based. Built-in: The schema will be created and stored locally for this component only.Databases components tInformixBulkExec Table Action on table Name of the table to be written. Related topic: Setting a built-in schema of Talend Open Studio User Guide.. Create a table if not exists: The table is created if it does not exist. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Select the date format that you want to apply. This component offers database query flexibility and covers all possible DB2 queries which may be required. Enter the number of rows in error at which point the Job should stop. Scénario associé For a scenario in which tInformixBulkExec might be used. see: • the tMysqlOutputBulkExec Scenario: Inserting transformed data in MySQL database on page 490. • the tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538. Select this check box to define the decimal separator in the Decimal separator field. Output Usage Where the output should go. Enter the numbere of rows to be processed before the commit. 330 Talend Open Studio Components Creative Commons License . Character. Field terminated by Set DBMONEY Set DBDATE Rows Before Commit Bad Rows Before Abort tStatCatcher Statistics Select this check box to colelct the log data at component level.Databases components tInformixBulkExec Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings. string or regular expression which separates the fields.

n/a Related scenario This component is for use with tInformixConnection and tInformixRollback. They are generally used along with tInformixConnection as the latter allows you to open a connection for the transaction which is underway. tStatCatcher Statistics Select this check box to collect the log data at a component level. Creative Commons License Talend Open Studio Components 331 .Databases components tInformixClose tInformixClose tInformixClose properties Component Family Databases/Informix Function Purpose Basic settings Advanced settings Usage Limitation tInformixClose closes an active connection to a database. select tInformixConnection from the list. To see a scenario in which tInformixClose might be used. This component is generally used as an input component. It requires an output component. This component closes connection to Informix databases. see tMysqlConnection on page 460. Component list If there is more than one connection used in the Job.

see tMysqlConnection on page 460. This component is generally used along with Informix components. select tInformixConnection from the list. your data will be committed row by row.Databases components tInformixCommit tInformixCommit tInformixCommit properties This component is closely related to tInformixConnection and tInformixRollback. 332 Talend Open Studio Components Creative Commons License . make a global commit just once instead of commiting every row or batch of rows separately. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect the log data at a component level. Clear the check box to continue using the connection once the component has completed its task. This improves performance. Component Family Databases/Informix Function Purpose Basic settings tInformixCommit validates data processed in a job from a connected database. They are generally used to execute transactions together. If this is the case. Component list Close connection If there is more than one connection in the Job. It means that the database conenction will be closed once the commit has been made. They are generally used along with tInformixConnection as the latter allows you to open a connection for the transaction which is underway To see a scenario in which tInformixCommit might be used. n/a Related Scenario This component is for use with tInformixConnection and tInformixRollback. This check box is selected by default. particularly tInformixConnection and tInformixRollback. do not select this check bx otherwise the conenction will be closed before the commit of your first row is finalized. Using a single connection. If you are using a Row > Main type connection to link tInformixCommit to your Job.

you can choose whether to activate the Auto Commit option. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Creative Commons License Talend Open Studio Components 333 . This information can generally be found in the SQL hosts file. with tInformixConnection opening the connection for the transaction. Repository: Select the repository file where Properties are stored. They are generally used along with tInformixConnection. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Select this check box to share your connection or fetch a connection shared by a parent or child Job. The fields that come after are pre-filled in using the fetched data. mode. Built-in: No property data stored centrally. Name of the schema DB user authentication data. Name of the database. This component allows you to commit all of the Job data to an output database in just a single transaction.. If the check box is selected. once the data has been validated. Clear this check box when the database is configured in NO_LOG. Database Family Databases/Informix Function Purpose Basic settings tInformixConnection opens a connection to a database in order that a transaction may be made. Host Port Database Schema Username et Password Instance Database server IP address. Property type Built-in ou Repository. DB server listening port. Name of the Informix instance to be used. Shared DB Connection Name: set or type in the shared connection name. Additional JDBC parameters Use or register a shared DB Connection Advanced settings Use Transaction tStatCatcher Statistics Select this check box to collect the log data at a component level.Databases components tInformixConnection tInformixConnection tInformixConnection properties This component is closely related to tInformixCommit and tInformixRollback. Specify additional connection properties for the DB connection you are creating.

might be used. 334 Talend Open Studio Components Creative Commons License .Databases components tInformixConnection Usage Limitation This component is generally used with other Informix components. see Scenario: Inserting data in mother/daughter tables on page 460. particularly tInformixCommit and tInformixRollback. n/a Related scenario For a scenario in which the tInformixConnection.

The fields that come after are pre-filled in using the fetched data. Built-in: The schema is created and stored locally for this component only. This field is compulsory for DB data handling.Databases components tInformixInput tInformixInput tInformixInput properties Component family Databases/Informix Function Purpose tInformixInput reads a database and extracts fields based on a query. i. The schema is either built-in or remotely stored in the Repository. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. hence can be reused.e. Name of the database Name of the database server DB user authentication data. Basic settings Usage This component covers all possibilities of SQL queries onto a DB2 database. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: Select the repository file where Properties are stored. Host Port Database DB server Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server.. Property type Either Built-in or Repository Built-in: No property data stored centrally. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. Then it passes on the field list to the next component via a Main row link. Creative Commons License Talend Open Studio Components 335 . A schema is a row description. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. it defines the number of fields to be processed and passed on to the next component. Encoding Type Select the encoding from the list or select Custom and define it manually. tInformixInput executes a DB query with a strictly defined order which must correspond to the schema definition. see Setting up a DB connection of Talend Open Studio User Guide. For more information about setting up and storing database connection parameters.

336 Talend Open Studio Components Creative Commons License . see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also the tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049.Databases components tInformixInput Related scenarios For related topics.

updates. Name of the database Name of the database server DB user authentication data. Note that only one table can be written at a time On the table defined. makes changes or suppresses entries in a database. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. based on the flow incoming from the preceding component in the Job. Create a table if not exists: The table is created if it does not exist. Clear a table: The table content is deleted. Built-in: No property data stored centrally. Name of the table to be written. see Setting up a DB connection of Talend Open Studio User Guide. Repository: Select the repository file where Properties are stored. tInformixOutput executes the action defined on the table and/or on the data contained in the table. Drop a table if exists and create: The table is removed if it already exists and created again. Create a table: The table does not exist and gets created. you can perform one of the following operations: None: No operation is carried out. The fields that come after are pre-filled in using the fetched data. Property type Either Built-in or Repository. For more information about setting up and storing database connection parameters. Drop and create a table: The table is removed and created again. Basic settings Creative Commons License Talend Open Studio Components 337 .. Host Port Database DB server Username and Password Table Action on table Database server IP address Listening port number of DB server.Databases components tInformixOutput tInformixOutput tInformixOutput properties Component family Databases/Informix Function Purpose tInformixOutput writes.

Repository: The schema already exists and is stored in the Repository. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Do the same in the Key in delete column for the Delete operation.Databases components tInformixOutput Action on data On the data of the table defined. select the check boxes next to the column names you want to use as a base for the Update operation. For an advanced use.. The gain in system performance is huge. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. Number of rows per insert:: enter the number of rows to be inserted as one block. hence can be reused. Clear the check box to skip the row on error and complete the process for error-free rows. Advanced settings Additional JDBC parameters Extend Insert 338 Talend Open Studio Components Creative Commons License . Related topic: Setting a built-in schema of Talend Open Studio User Guide. Schema and Edit Schema A schema is a row description. If needed. i. If duplicates are found. Specify additional connection properties for the DB connection you are creating.e. you can perform: Insert: Add new entries to the table. Note that too high value decreases performance due to memory issues. Job stops. you can retrieve the rows on error via a Row > Rejects link. Built-in: The schema is created and stored locally for this component only. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. it defines the number of fields to be processed and passed on to the next component. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Die on error This check box is selected by default. To do that: Select the Use field options check box and then in the Key in update column. The schema is either built-in or remotely stored in the Repository. Select this check box to carry out a bulk insert of a definable set of lines instead of inserting lines one by one.

Replace or After following the action to be performed on the reference column. above all. which are not insert. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. For an example of tMySqlOutput in use. Number of rows to be completed before committing batches of rows together into the DB. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. tStatCatcher Statistics Select this check box to collect log data at the component level. better performance at executions. This option is not offered if you create (with or without drop) the DB table. to optimize the insertion of batches of data. This component must be used as an output component. This field is compulsory for DB data handling. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. especially when there is double action on data. Select this check box to display each step during processing entries in a database. Position: Select Before. or action that require particular preprocessing. This option ensures transaction quality (but not rollback) and. Creative Commons License Talend Open Studio Components 339 . see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For tInformixOutput related topics. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. enables you to define the number of lines in each processed batch. When selected.Databases components tInformixOutput Encoding Type Select the encoding type from the list or select Custom and define it manually. Ensure the check box is selected. It allows you to carry out actions on a table or on the data of a table in a Informix database. Commit every Additional Columns Use field options Enable debug mode Use Batch Size Optimize the batch insertion Select this check box to customize a request. This option allows you to call SQL functions to perform actions on columns. see • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. nor update or delete actions.

it defines the number of fields that will be processed and passed on to the next component. detailed in another section. Select this check box to append new rows to the end of the file. Repository: The schema already exists and is stored in the Repository. The schema is either built-in or remote in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. The advantage of using two components is that the transformations can be processed before the data is loaded in the database. Select the date format that you want to apply. Component family Databases/Informix Function Purpose Basic settings Writes a file composed of columns. The fields that come after are pre-filled in using the fetched data. hence can be reused in various projects and job designs. string or regular expression used to separate fields Select this box if you want to define the decimal separator in the corresponding field. based on a defined delimiter and on Informix standards. 340 Talend Open Studio Components Creative Commons License . A schema is a row description.e. i.Databases components tInformixOutputBulk tInformixOutputBulk tInformixOutputBulk properties tInformixOutputBulk and tInformixBulkExec are generally used together to generate an output file for use as a parameter in the execution of an SQL query. File Name Name of the file to be processed. Built-in: No property data stored centrally Repository: Select the repository file where Properties are stored. Append Schema and Edit Schema Advanced settings Row separator Field separator Set DBMONEY Set DBDATE String (ex: “\n”on Unix) to distinguish rows. Related topic: Defining variables from the Component view of Talend Open Studio User Guide. Property type Built-in ou Repository. Character. Prepares the file to be used as a parmameter in the INSERT query used to feed Informix databases. Related topic: Setting a Repository schema of Talend Open Studio User Guide.. This two step execution is unified in the tInformixOutputBulkExec component. Built-in: The schema will be created and stored locally for this component only.

Custom the flush buffer size Select this box in order to customize the memory size used to store the data temporarily. Usage This component is generally used along with tInformixBulkExec. Encoding Type tStatCatcher Statistics Select this check box to collect log data at the component level. Together. see: • the tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490. Select the encoding from the list or select Custom and define it manually. they improve performance levels when adding data to an Informix database. The option exists allows you to create a folder for the output file if it doesn’t already exist.Databases components tInformixOutputBulk Create directory if not This check box is selected automatically. Creative Commons License Talend Open Studio Components 341 . • the tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495. This field is compulsory for DB data handling. In the Row number field enter the number of rows at which point the memory should be freed. Related scenario For a scenario in which tInformixOutputBulk might be used.

make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. see your studio user guide. No properties stored centrally Repository: Select the Repository file where Properties are stored. make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings. This information can generally be found in the SQL hosts file. Component list presents only the connection components in the same Job level. the fields to follow are pre-filled in using fetched data Execution platform Use an existing connection Select the operating system you are using. When selected. DB server listening port. 342 Talend Open Studio Components Creative Commons License . Property Type Built-in ou Repository. Name of the Informix instance to be used. Otherwise. Select the check box and choose the appropriate tInformixConnection component from the list to use pre-defined connection parameters. so if you need to use an existing connection from the other level. When a Job contains the parent Job and the child Job. Host Port Database Schema Username et Password Instance Database server IP address. In this case. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. tInformixOutputBulkExec is a dedicated componant which improves performance during Insert operations in Informix databases. DB user authentication data. Name of the schema. Name of the database.Databases components tInformixOutputBulkExec tInformixOutputBulkExec tInformixOutputBulkExec properties Component Family Databases/Informix Function Purpose Basic settings tInformixOutputBulkExec carries out Insert operations using the data provided.

Drop a table if exists and create: The table is removed if it already exists and created again. String (ex: “\n”on Unix) to distinguish rows. You can reuse it in various projects and job flowcharts.e. Specify additional connection properties for the DB connection you are creating. Repository: You have already created the schema and stored it in the Repository. it defines the number of fields to be processed and passed on to the next component. Name of the file to be processed. Select this check box to add rows to the end of the file. Character. Built-in: The schema will be created and stored locally for this component only. Select the operation you want to perform: Bulk insert Bulk update The details asked will be different according to the action chosen. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Create a table if not exists: The table is created if it does not exist. Select the date format you want to apply. string or regular expression used to separate the fields Select this check box to define the decimal separator used in the corresponding field. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Note that only one table can be written at a time and the table must already exist for the insert operation to be authorised. Drop and create a table: The table is removed and created again. Create a table: The table does not exist and gets created. you can perform one of the following operations: None: No operation is carried out. Append Action on data Advanced settings Additional JDBC parameters Row separator Fields terminated by Set DBMONEY Set DBDATE Creative Commons License Talend Open Studio Components 343 . This option is not available if you have selected the Use an existing connection check box in the Basic settings. i.Databases components tInformixOutputBulkExec Table Name of the table to be written. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Action on table Schema et Edit Schema Informix Directory Data file Indicate the access path to your Informix directory. On the table defined. Clear a table: The table content is deleted. A schema is a row description..

n/a Related scenario For a scenarion in which tInformixOutputBulkExec might be used. This field is compulsory for DB data handling. Create directory if not This check box is selected by default. It creates a exists directory to hold the output table if required. • the tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495. Custom the flush buffer size Select this box in order to customize the memory size used to store the data temporarily. In the Row number field enter the number of rows at which point the memory should be freed. see: • the tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490. Encoding Type tStatCatcher Statistics Select this check box to collect the log data at a component level. 344 Talend Open Studio Components Creative Commons License .Databases components tInformixOutputBulkExec Rows Before Commit Bad Rows Before Abort Enter the number of rows to be processed before the commit. Select the encoding from the list or select Custom and define it manually. This component is generally used when no particular transformation is required on the data to be inserted in the database. Output Usage Limitation Where the output should go. Enter the number of rows in error at which point the Job should stop.

This component must be used with other Informix components.Databases components tInformixRollback tInformixRollback tInformixRollback properties This component is closely related to tInformixCommit and tInformixConnection. see the tMysqlRollback Scenario: Rollback from inserting data in mother/daughter tables on page 498. Creative Commons License Talend Open Studio Components 345 . They are generally used together to execute transactions. Famille de composant Databases/Informix Function Purpose Basic settings tInformixRollback cancels transactions in connected databases. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect the log data at a component level. Component list Select the tInformixConnection component from the list if you plan to add more than one connection to the Job. This component prevents involuntary transaction commits. n/a Related Scenario For a scenario in which tInformixRollback might be used. Clear this checkbox if you want to continue to use the connection once the component has completed its task. particularly tInformixConnection and tInformixCommit.

When a Job contains the parent Job and the child Job. so if you need to use an existing connection from the other level. Name of the database DB user authentication data. Otherwise. see your studio user guide. make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels. Host Port Database Username and Password Database server IP address Listening port number of DB server. Purpose Basic settings 346 Talend Open Studio Components Creative Commons License . For more information about Dynamic settings. Depending on the nature of the query and the database. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Component list presents only the connection components in the same Job level. Property type Either Built-in or Repository. Built-in: No property data stored centrally. make sure the connection name is unique and distinctive all over through the two Job levels. The row suffix means the component implements a flow in the job design although it doesn’t provide output.Databases components tInformixRow tInformixRow tInformixRow properties Component family Databases/Informix Function tInformixRow is the specific component for this database query. The SQLBuilder tool helps you write easily your SQL statements. The fields that come after are pre-filled in using the fetched data. In this case. Repository: Select the repository file where Properties are stored. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. tInformixRow acts on the actual DB structure or on the data (although without handling data). It executes the SQL query stated onto the specified database. Use an existing connection Select this check box and click the relevant tInformixConnection component on the Component list to reuse the connection details you already defined.

Parameter Type: Enter the parameter type. This option is very useful if you need to execute the same query several times. Clear the check box to skip the row on error and complete the process for error-free rows. Select this check box to insert the result of the query into a COLUMN of the current flow. If needed. Select this checkbox if you want to query the database using a PreparedStatement. Parameter Index: Enter the parameter position in the SQL instruction. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Built-in: The schema is created and stored locally for this component only. This option ensures transaction quality (but not rollback) and above all better performance on executions. In the Set PreparedStatement Parameter table. 347 Commit every Creative Commons License Talend Open Studio Components . Select this column from the use column list. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository.. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. you can retrieve the rows on error via a Row > Rejects link. This field is compulsory for DB data handling. The schema is either built-in or remotely stored in the Repository. Performance levels are increased Die on error Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. hence can be reused. This check box is selected by default.Databases components tInformixRow Schema and Edit Schema A schema is a row description. Number of rows to be completed before committing batches of rows together into the DB. Repository: The schema already exists and is stored in the Repository.e. Related topic: Setting a built-in schema of Talend Open Studio User Guide. The Query field gets accordingly filled in. Specify additional connection properties for the DB connection you are creating. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. i. it defines the number of fields to be processed and passed on to the next component. Parameter Value: Enter the parameter value. Query type Either Built-in or Repository.

Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. 348 Talend Open Studio Components Creative Commons License .Databases components tInformixRow tStatCatcher Statistics Select this check box to collect log data at the component level. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Related scenarios For related topics.

Creative Commons License Talend Open Studio Components 349 .Databases components tInformixSCD tInformixSCD The tInformixSCD component belongs to two different families: Business Intelligence and Databases. For further information. see tInformixSCD on page 9.

350 Talend Open Studio Components Creative Commons License .Databases components tInformixSP tInformixSP tInformixSP properties Component Family Databases/Informix Function Purpose Basic settings tInformixSP calls procedures stored in a database. For more information on how to share a DB connection across Job levels. tInformixSP allows you to centralise multiple and complex queries in a database and enables you to call them more easily. Built-in: No properties stored centrally. make sure that the available connection components are sharing the intended connection. The fields that come after are pre-filled in using the fetched data. Name of the database. Name of the Informix instance to be used. Otherwise. see your studio user guide. so if you need to use an existing connection from the other level. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Repository: Select the repository file where Properties are stored. Host Port Database Schema Username et Password Instance Database server IP address. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Use an existing connection Select the check box and choose the appropriate tInformixConnection component from the list to use pre-defined connection parameters. Property type Built-in ou Repository. When a Job contains the parent Job and the child Job. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. For more information about Dynamic settings. Component list presents only the connection components in the same Job level. User authentication information. This information can generally be found in the SQL hosts file. Name of the schema. Listening port number of DB server.

e. Note that the SP schema can hold more columns than there are paramaters used in the procedure. You can reuse it in various projects and job flowcharts. rather than single value. likely after modification through the procedure (function). The stored procedure syntax must correspond to that of the database.Databases components tInformixSP Schema and Edit Schema In a stored procedure. SP Name Is Function / Return result in Enter the exact name of the stored procedure (SP). Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. Repository: You have already created the schema and stored it in the Repository. Click the Plus button and select the various Schema Columns that will be required by the procedures. see: Creative Commons License Talend Open Studio Components 351 . Parameters Use Transaction Advanced settings Additional JDBC parameters tStatCatcher Statistics Select this check box to collect log data at a component level. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Clear this check box if the database is configured in the NO_LOG mode. Usage Limitation This is an intermediary component? It can also be used as an entry component. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Built-in: The schema is created and stored locally for this component only. it defines the number of fields to be processed and passed on to the next component. A schema is a row description. a schema is an input parameter. only the entry parameters are authorized. Related topic: Setting a built-in schema of Talend Open Studio User Guide. RECORDSET: Input parameters is to be returned as a set of values. Specify additional connection properties for the DB connection you are creating. Related scenario For a scenarion in which tInformixSP may be used.. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameters is to be returned as value. select the the schema column upon which the value to be obtained is based. In this case. i. The schema is either Built-in or remotely stored in the Repository. Select this check box if only one value must be returned. From the list.

see the tParseRecordSet on page 591 if you want to analyse a set of records in a table or SQL query. • the tOracleSP Scenario: Checking number format using a stored procedure on page 564 Also. 352 Talend Open Studio Components Creative Commons License .Databases components tInformixSP • the tMysqlSP Scenario: Finding a State Label using a stored procedure on page 512.

Component list Select the tIngresConnection component in the list if more than one connection are planned for the current Job.Databases components tIngresClose tIngresClose tIngresClose properties Component family Databases/Ingres Function Purpose Basic settings tIngresClose closes the transaction committed in the connected DB. Close a transaction. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tIngresConnection and tIngresCommit. This component is to be used along with Ingres components. Creative Commons License Talend Open Studio Components 353 . n/a Related scenario No scenario is available for this component yet.

especially with tIngresConnection and tIngresRollback. 354 Talend Open Studio Components Creative Commons License . see Scenario: Inserting data in mother/daughter tables on page 460. n/a Related scenario For tIngresCommit related scenario. It allows you to close the database connection once the commit is done. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component list Select the tIngresConnection component in the list if more than one connection are planned for the current Job. Clear this check box to continue to use the selected connection once the component has performed its task. your data will be commited row by row. This component is to be used along with Ingres components.Databases components tIngresCommit tIngresCommit tIngresCommit Properties This component is closely related to tIngresConnection and tIngresRollback. do not select the Close connection check box or your connection will be closed before the end of your first row commit. If you want to use a Row > Main connection to link tAS400Commit to your Job. It usually does not make much sense to use these components independently in a transaction. In this case. Component family Databases/Ingres Function Purpose Validates the data processed through the Job into the connected DB Using a unique connection. This check box is selected by default. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance.

This component allows you to commit all of the Job data to an output database in just a single transaction. Listening port number of DB server. It usually does not make much sense to use one of these without using a tIngresConnection component to open a connection for the current transaction. Built-in: No property data stored centrally. Server Port Database Username and Password Use or register a shared DB Connection Database server IP address. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Shared DB Connection Name: set or type in the shared connection name. n/a Related scenarios For tIngresConnection related scenario. The fields that come after are pre-filled in using the fetched data. especially with tIngresCommit and tIngresRollback. Name of the database DB user authentication data. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. see Scenario: Inserting data in mother/daughter tables on page 460.Databases components tIngresConnection tIngresConnection tIngresConnection Properties This component is closely related to tIngresCommit and tIngresRollback. Creative Commons License Talend Open Studio Components 355 . once the data has been validated. Select this check box to share your connection or fetch a connection shared by a parent or child Job. Component family Databases/Ingres Function Purpose Basic settings Opens a connection to the database for a current transaction. Usage Limitation This component is to be used along with Ingres components.

Built-in: The schema is created and stored locally for this component only. Property type Either Built-in or Repository Built-in: No property data stored centrally. Repository: The schema already exists and is stored in the Repository. A schema is a row description.Databases components tIngresInput tIngresInput tIngresInput properties Component family Databases/Ingres Function Purpose tIngresInput reads a database and extracts fields based on a query. For more information about setting up and storing database connection parameters. Name of the database DB user authentication data. Repository: Select the repository file where Properties are stored. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Remove leading and trailing whitespace from defined columns. Then it passes on the field list to the next component via a Main row link. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i. tIngresInput executes a DB query with a strictly defined order which must correspond to the schema definition. 356 Talend Open Studio Components Creative Commons License . Related topic: Setting a Repository schema of Talend Open Studio User Guide. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. hence can be reused. it defines the number of fields to be processed and passed on to the next component.. Server Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server.e. see Setting up a DB connection of Talend Open Studio User Guide. The fields that come after are pre-filled in using the fetched data. Basic settings Advanced settings Trim all the String/Char columns Trim column Select this check box to remove leading and trailing whitespace from all the String/Char columns.

Databases components tIngresInput tStatCatcher Statistics Select this check box to collect log data at the component level. the tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Creative Commons License Talend Open Studio Components 357 . Usage This component covers all possibilities of SQL queries onto an Ingres database. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also. Related scenarios For related topics.

Name of the table to be written. Repository: Select the repository file where Properties are stored. Drop a table if exists and create: The table is removed if it already exists and created again. makes changes or suppresses entries in a database. Built-in: No property data stored centrally. Name of the database DB user authentication data. Drop and create a table: The table is removed and created again. For more information about setting up and storing database connection parameters. Host Port Database Username and Password Table Action on table Database server IP address Listening port number of DB server. see Setting up a DB connection of Talend Open Studio User Guide. based on the flow incoming from the preceding component in the Job. Create a table if not exists: The table is created if it does not exist. Note that only one table can be written at a time On the table defined. Property type Either Built-in or Repository. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. tIngresOutput executes the action defined on the table and/or on the data contained in the table. Clear a table: The table content is deleted. The fields that come after are pre-filled in using the fetched data.Databases components tIngresOutput tIngresOutput tIngresOutput properties Component family Databases/Ingres Function Purpose tIngresOutput writes. updates. Create a table: The table does not exist and gets created. you can perform one of the following operations: None: No operation is carried out. Basic settings 358 Talend Open Studio Components Creative Commons License .

it defines the number of fields to be processed and passed on to the next component. Advanced settings Encoding Type Commit every Creative Commons License Talend Open Studio Components 359 . If needed. select the check boxes next to the column names you want to use as a base for the Update operation. better performance at execution. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. Built-in: The schema is created and stored locally for this component only. Die on error This check box is selected by default. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. This option ensures transaction quality (but not rollback) and. For an advanced use. Schema and Edit Schema A schema is a row description. i. Clear the check box to skip the row on error and complete the process for error-free rows. above all.. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based.Databases components tIngresOutput Action on data On the data of the table defined..e. The schema is either built-in or remotely stored in the Repository. This field is compulsory for DB data handling. To do that: Select the Use field options check box and then in the Key in update column. Do the same in the Key in delete column for the Delete operation. Enter the number of rows to be completed before committing batches of rows together into the DB. you can perform: Insert: Add new entries to the table. you can retrieve the rows on error via a Row > Rejects link. If duplicates are found. Job stops. Select the encoding type from the list or select Custom and define it manually. Repository: The schema already exists and is stored in the Repository. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s).

This option allows you to call SQL functions to perform actions on columns. or action that require particular preprocessing. For an example of tMySqlOutput in use. nor update or delete actions. Replace or After following the action to be performed on the reference column. which are not insert. Position: Select Before. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Select this check box to display each step during processing entries in a database. 360 Talend Open Studio Components Creative Commons License . see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. It allows you to carry out actions on a table or on the data of a table in a Ingres database. Use field options Enable debug mode Select this check box to customize a request. This component must be used as an output component. tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data.Databases components tIngresOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. especially when there is double action on data. It also allows you to create a reject flow using a Row > Rejects link to filter data in error.

n/a Related scenarios For tIngresRollback related scenario. Avoids to commit part of a transaction involuntarily. Component list Select the tIngresConnection component in the list if more than one connection are planned for the current Job. see Scenario: Rollback from inserting data in mother/daughter tables on page 498. Component family Databases/Ingres Function Purpose Basic settings tIngresRollback cancels the transaction committed in the connected DB.Databases components tIngresRollback tIngresRollback tIngresRollback properties This component is closely related to tIngresCommit and tIngresConnection. Clear this check box to continue to use the selected connection once the component has performed its task. Creative Commons License Talend Open Studio Components 361 . It usually does not make much sense to use these components independently in a transaction. especially with tIngresConnection and tIngresCommit. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. This component is to be used along with Ingres components.

Repository: Select the repository file where Properties are stored. it defines the number of fields to be processed and passed on to the next component. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Query type Either Built-in or Repository. tIngresRow acts on the actual DB structure or on the data (although without handling data). Host Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. Name of the database DB user authentication data. Built-in: The schema is created and stored locally for this component only.e. It executes the SQL query stated onto the specified database. Repository: The schema already exists and is stored in the Repository.. hence can be reused. i. A schema is a row description. Built-in: No property data stored centrally.Databases components tIngresRow tIngresRow tIngresRow properties Component family Databases/Ingres Function tIngresRow is the specific component for this database query. Property type Either Built-in or Repository. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. The SQLBuilder tool helps you write easily your SQL statements. The Query field gets accordingly filled in. Depending on the nature of the query and the database. The fields that come after are pre-filled in using the fetched data. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Purpose Basic settings 362 Talend Open Studio Components Creative Commons License . The schema is either built-in or remotely stored in the Repository. The row suffix means the component implements a flow in the job design although it doesn’t provide output.

you can retrieve the rows on error via a Row > Rejects link. This option is very useful if you need to execute the same query several times. Clear the check box to skip the row on error and complete the process for error-free rows. Select this column from the use column list. In the Set PreparedStatement Parameter table. Creative Commons License Talend Open Studio Components 363 . Performance levels are increased Advanced Settings Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. If needed. Select this checkbox if you want to query the database using a PreparedStatement. Parameter Value: Enter the parameter value. Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Parameter Type: Enter the parameter type. Number of rows to be completed before committing batches of rows together into the DB.Databases components tIngresRow Die on error This check box is selected by default. Related scenarios For related topics. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. This option ensures transaction quality (but not rollback) and above all better performance on executions. Parameter Index: Enter the parameter position in the SQL instruction. Select this check box to insert the result of the query into a COLUMN of the current flow. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. This field is compulsory for DB data handling.

For more information on it. 364 Talend Open Studio Components Creative Commons License .Databases components tIngresSCD tIngresSCD tIngresSCD belongs to two component families: Business Intelligence and Databases. see tIngresSCD on page 11.

Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Close a transaction. This component is to be used along with Interbase components. Creative Commons License Talend Open Studio Components 365 .Databases components tInterbaseClose tInterbaseClose tInterbaseClose properties Component family Databases/Interbase Function Purpose Basic settings tInterbaseClose closes the transaction committed in the connected DB. Component list Select the tInterbaseConnection component in the list if more than one connection are planned for the current Job. n/a Related scenario No scenario is available for this component yet. especially with tInterbaseConnection and tInterbaseCommit.

especially with the tInterbaseConnection and tInterbaseRollback components. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance.Databases components tInterbaseCommit tInterbaseCommit tInterbaseCommit Properties This component is closely related to tInterbaseConnection and tInterbaseRollback. For tInterbaseCommit related scenario. n/a Related scenario This component is closely related to tInterbaseConnection and tInterbaseRollback. This component is to be used along with Interbase components. your data will be commited row by row. see tMysqlConnection on page 460. 366 Talend Open Studio Components Creative Commons License . It usually doesn’t make much sense to use JDBC components without using the tInterbaseConnection component to open a connection for the current transaction. If you want to use a Row > Main connection to link tAS400Commit to your Job. Component family Databases/Interbase Function Purpose Validates the data processed through the Job into the connected DB. In this case. Clear this check box to continue to use the selected connection once the component has performed its task. do not select the Close connection check box or your connection will be closed before the end of your first row commit. Component list Select the tInterbaseConnection component in the list if more than one connection are planned for the current Job. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. It usually doesn’t make much sense to use JDBC components independently in a transaction. Using a unique connection.

The fields that come after are pre-filled in using the fetched data. It usually does not make much sense to use one of these without using a tInterbaseConnection to open a connection for the current transaction. DB user authentication data. Creative Commons License Talend Open Studio Components 367 . Select this check box to share your connection or fetch a connection shared by a parent or child Job. Built-in: No property data stored centrally. once the data has been validated. Host name Database Username and Password Use or register a shared DB Connection Database server IP address. It usually does not make much sense to use one of these without using a tInterbaseConnection component to open a connection for the current transaction. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Shared DB Connection Name: set or type in the shared connection name. especially with tInterbaseCommit and tInterbaseRollback. Name of the database. This component allows you to commit all of the Job data to an output database in just a single transaction. Repository: Select the repository file where Properties are stored.Databases components tInterbaseConnection tInterbaseConnection tInterbaseConnection properties This component is closely related to tInterbaseCommit and tInterbaseRollback. Component family Databases/Interbase Function Purpose Basic settings tInterbaseConnection opens a connection to the database for a current transaction. n/a Related scenarios This component is closely related to tInterbaseCommit and tInterbaseRollback. Usage Limitation This component is to be used along with Interbase components. Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. Select this check box to automatically commit a transaction when it is completed. Property type Either Built-in or Repository.

368 Talend Open Studio Components Creative Commons License . see tMysqlConnection on page 460.Databases components tInterbaseConnection For tInterbaseConnection related scenario.

Host Database Username and Password Schema and Edit Schema Database server IP address Name of the database DB user authentication data. Select this check box to remove leading and trailing whitespace from all the String/Char columns. The schema is either built-in or remotely stored in the Repository. Repository: The schema already exists and is stored in the Repository.Databases components tInterbaseInput tInterbaseInput tInterbaseInput properties Component family Databases/Interbase Function Purpose tInterbaseInput reads a database and extracts fields based on a query. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Then it passes on the field list to the next component via a Main row link. see Setting up a DB connection of Talend Open Studio User Guide. 369 Trim all the String/Char columns Trim column Creative Commons License Talend Open Studio Components . A schema is a row description. it defines the number of fields to be processed and passed on to the next component. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Property type Either Built-in or Repository Built-in: No property data stored centrally. For more information about setting up and storing database connection parameters. This field is compulsory for DB data handling. hence can be reused. tInterbaseInput executes a DB query with a strictly defined order which must correspond to the schema definition.e. i. Remove leading and trailing whitespace from defined columns. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Repository: Select the repository file where Properties are stored. Built-in: The schema is created and stored locally for this component only.. Basic settings Advanced settings Encoding Type Select the encoding from the list or select Custom and define it manually. The fields that come after are pre-filled in using the fetched data. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Usage This component covers all possibilities of SQL queries onto an Interbase database. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also the related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049.Databases components tInterbaseInput tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios For related topics. 370 Talend Open Studio Components Creative Commons License .

Create a table: The table does not exist and gets created. Name of the table to be written. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Note that only one table can be written at a time On the table defined. see Setting up a DB connection of Talend Open Studio User Guide. tInterbaseOutput executes the action defined on the table and/or on the data contained in the table. Create a table if not exists: The table is created if it does not exist. Basic settings Creative Commons License Talend Open Studio Components 371 .. For more information about setting up and storing database connection parameters.Databases components tInterbaseOutput tInterbaseOutput tInterbaseOutput properties Component family Databases/Interbase Function Purpose tInterbaseOutput writes. Drop and create a table: The table is removed and created again. Property type Either Built-in or Repository. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Host Database Username and Password Table Action on table Database server IP address Name of the database DB user authentication data. updates. Clear a table: The table content is deleted. Drop table if exists and create: The table is removed if it already exists and created again. makes changes or suppresses entries in a database. you can perform one of the following operations: None: No operation is carried out. based on the flow incoming from the preceding component in the Job. Built-in: No property data stored centrally.

Die on error This check box is selected by default. select the check boxes next to the column names you want to use as a base for the Update operation.. Select the encoding type from the list or select Custom and define it manually. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow.e. The schema is either built-in or remotely stored in the Repository. Job stops. To do that: Select the Use field options check box and then in the Key in update column. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Clear the check box to skip the row on error and complete the process for error-free rows. above all. If needed. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. better performance at execution. Do the same in the Key in delete column for the Delete operation. i. hence can be reused. If duplicates are found. For an advanced use. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). This option ensures transaction quality (but not rollback) and. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. it defines the number of fields to be processed and passed on to the next component. Repository: The schema already exists and is stored in the Repository. you can perform: Insert: Add new entries to the table. Clear data in table Schema and Edit Schema Wipes out data from the selected table before action. Built-in: The schema is created and stored locally for this component only. A schema is a row description. Enter the number of rows to be completed before committing batches of rows together into the DB. you can retrieve the rows on error via a Row > Rejects link. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. This field is compulsory for DB data handling.Databases components tInterbaseOutput Action on data On the data of the table defined.. Advanced settings Encoding Type Commit every 372 Talend Open Studio Components Creative Commons License .

For an example of tMySqlOutput in use. which are not insert. Use field options Enable debug mode Select this check box to customize a request. Replace or After following the action to be performed on the reference column. It allows you to carry out actions on a table or on the data of a table in a Interbase database. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. nor update or delete actions. see • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. Select this check box to display each step during processing entries in a database. Creative Commons License Talend Open Studio Components 373 . see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. Position: Select Before. especially when there is double action on data. tStatCatcher Statistics Select this check box to collect log data at the component level. This component must be used as an output component. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. This option allows you to call SQL functions to perform actions on columns. or action that require particular preprocessing.Databases components tInterbaseOutput Additional Columns This option is not offered if you create (with or without drop) the DB table.

This component is to be used along with Interbase components. It usually does not make much sense to use these components independently in a transaction. especially with tInterbaseConnection and tInterbaseCommit. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. 374 Talend Open Studio Components Creative Commons License . Component family Databases/Interbase Function Purpose Basic settings tInterbaseRollback cancels the transaction committed in the connected DB. n/a Related scenarios For tInterbaseRollback related scenario. Clear this check box to continue to use the selected connection once the component has performed its task. Component list Select the tInterbaseConnection component in the list if more than one connection are planned for the current Job.Databases components tInterbaseRollback tInterbaseRollback tInterbaseRollback properties This component is closely related to tInterbaseCommit and tInterbaseConnection. Avoids to commit part of a transaction involuntarily. see Scenario: Rollback from inserting data in mother/daughter tables on page 498 of the tMysqlRollback.

see your studio user guide. It executes the SQL query stated onto the specified database. For more information about Dynamic settings. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. tInterbaseRow acts on the actual DB structure or on the data (although without handling data). Purpose Basic settings Creative Commons License Talend Open Studio Components 375 .Databases components tInterbaseRow tInterbaseRow tInterbaseRow properties Component family Databases/Interbase Function tInterbaseRow is the specific component for this database query. i. A schema is a row description. Otherwise. The row suffix means the component implements a flow in the job design although it doesn’t provide output. The fields that come after are pre-filled in using the fetched data. Host Database Username and Password Schema and Edit Schema Database server IP address Name of the database DB user authentication data. make sure that the available connection components are sharing the intended connection. When a Job contains the parent Job and the child Job. Property type Either Built-in or Repository. Repository: Select the repository file where Properties are stored. The schema is either built-in or remotely stored in the Repository. Component list presents only the connection components in the same Job level. so if you need to use an existing connection from the other level. For more information on how to share a DB connection across Job levels. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Depending on the nature of the query and the database. The SQLBuilder tool helps you write easily your SQL statements. In this case. it defines the number of fields to be processed and passed on to the next component.e. make sure the connection name is unique and distinctive all over through the two Job levels.. Use an existing connection Select this check box and click the relevant tInterbaseConnection component on the Component list to reuse the connection details you already defined. Built-in: No property data stored centrally.

Repository: The schema already exists and is stored in the Repository. Performance levels are increased Encoding Type Select the encoding from the list or select Custom and define it manually. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Parameter Type: Enter the parameter type. If needed.Databases components tInterbaseRow Built-in: The schema is created and stored locally for this component only. In the Set PreparedStatement Parameter table. Related topic: Setting a built-in schema of Talend Open Studio User Guide. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Parameter Index: Enter the parameter position in the SQL instruction. hence can be reused. Query type Either Built-in or Repository. Number of rows to be completed before committing batches of rows together into the DB. Parameter Value: Enter the parameter value. Select this column from the use column list. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. This option ensures transaction quality (but not rollback) and above all better performance on executions. Select this check box to insert the result of the query into a COLUMN of the current flow. Related topic: Setting a Repository schema of Talend Open Studio User Guide. This check box is selected by default. The Query field gets accordingly filled in. Clear the check box to skip the row on error and complete the process for error-free rows. 376 Talend Open Studio Components Creative Commons License . you can retrieve the rows on error via a Row > Rejects link. This option is very useful if you need to execute the same query several times. Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. Select this checkbox if you want to query the database using a PreparedStatement. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. This field is compulsory for DB data handling.

Creative Commons License Talend Open Studio Components 377 .Databases components tInterbaseRow Related scenarios For related topics. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502.

it defines the number of fields to be processed and passed on to the next component. Built-in: The schema is created and stored locally for this component only. see Setting up a DB connection of Talend Open Studio User Guide. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Basic settings Advanced settings Encoding Type Select the encoding from the list or select Custom and define it manually. The fields that come after are pre-filled in using the fetched data.. A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Trim all the String/Char columns 378 Talend Open Studio Components Creative Commons License . Select this check box to remove leading and trailing whitespace from all the String/Char columns.e. Repository: Select the repository file where Properties are stored. This field is compulsory for DB data handling. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. i. Repository: The schema already exists and is stored in the Repository. For more information about setting up and storing database connection parameters. DB user authentication data. Then it passes on the field list to the next component via a Main row link. hence can be reused. Property type Either Built-in or Repository Built-in: No property data stored centrally. tJavaDBInput executes a DB query with a strictly defined order which must correspond to the schema definition. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.Databases components tJavaDBInput tJavaDBInput tJavaDBInput properties Component family Databases/JavaDB Function Purpose tJavaDBInput reads a database and extracts fields based on a query. Framework Database DB root path Username and Password Schema and Edit Schema Select your Java database framework on the list Name of the database Browse to your database root.

Databases components tJavaDBInput Trim column Remove leading and trailing whitespace from defined columns. Creative Commons License Talend Open Studio Components 379 . Usage This component covers all possibilities of SQL queries onto a database. see tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 See also the related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Related scenarios For related topics. tStatCatcher Statistics Select this check box to collect log data at the component level.

Drop and create a table: The table is removed and created again. The fields that come after are pre-filled in using the fetched data. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. see Setting up a DB connection of Talend Open Studio User Guide. Built-in: No property data stored centrally. DB user authentication data. Note that only one table can be written at a time On the table defined. Create a table if not exists: The table is created if it does not exist. makes changes or suppresses entries in a database. Create a table: The table does not exist and gets created. Name of the table to be written.Databases components tJavaDBOutput tJavaDBOutput tJavaDBOutput properties Component family Databases/JavaDB Function Purpose tJavaDBOutput writes. you can perform one of the following operations: None: No operation is carried out. Framework Database DB root path Username and Password Table Action on table Select your Java database framework on the list Name of the database Browse to your database root. Repository: Select the repository file where Properties are stored. Clear a table: The table content is deleted. tJavaDBOutput executes the action defined on the table and/or on the data contained in the table. Drop table if exists and create: The table is removed if it already exists and created again. For more information about setting up and storing database connection parameters. Basic settings 380 Talend Open Studio Components Creative Commons License . based on the flow incoming from the preceding component in the Job. updates. Property type Either Built-in or Repository.

you can perform: Insert: Add new entries to the table.Databases components tJavaDBOutput Action on data On the data of the table defined. select the check boxes next to the column names you want to use as a base for the Update operation. Schema and Edit Schema A schema is a row description. Die on error This check box is selected by default. it defines the number of fields to be processed and passed on to the next component. If duplicates are found. Job stops. i. Select the encoding type from the list or select Custom and define it manually. To do that: Select the Use field options check box and then in the Key in update column. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. Do the same in the Key in delete column for the Delete operation. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. The schema is either built-in or remotely stored in the Repository.. Repository: The schema already exists and is stored in the Repository.e. Enter the number of rows to be completed before committing batches of rows together into the DB. Advanced settings Encoding Type Commit every Creative Commons License Talend Open Studio Components 381 . This field is compulsory for DB data handling. above all. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). hence can be reused. This option ensures transaction quality (but not rollback) and. better performance at execution. you can retrieve the rows on error via a Row > Rejects link. Related topic: Setting a built-in schema of Talend Open Studio User Guide. If needed. Clear the check box to skip the row on error and complete the process for error-free rows. Built-in: The schema is created and stored locally for this component only. For an advanced use. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

This component must be used as an output component. Replace or After following the action to be performed on the reference column. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. which are not insert. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. tStatCatcher Statistics Select this check box to collect log data at the component level. For an example of tMySqlOutput in use. It allows you to carry out actions on a table or on the data of a table in a Java database. 382 Talend Open Studio Components Creative Commons License . see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For related topics. or action that require particular preprocessing.Databases components tJavaDBOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. Position: Select Before. This option allows you to call SQL functions to perform actions on columns. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Use field options Enable debug mode Select this check box to customize a request. nor update or delete actions. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Select this check box to display each step during processing entries in a database. especially when there is double action on data. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data.

Repository: Select the repository file where Properties are stored. Built-in: No property data stored centrally. Built-in: The schema is created and stored locally for this component only. The SQLBuilder tool helps you write easily your SQL statements. The Query field gets accordingly filled in. The row suffix means the component implements a flow in the job design although it doesn’t provide output. i. Related topic: Setting a built-in schema of Talend Open Studio User Guide. It executes the SQL query stated onto the specified database.. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. The schema is either built-in or remotely stored in the Repository. Query type Either Built-in or Repository. tJavaDBRow acts on the actual DB structure or on the data (although without handling data).e. DB user authentication data. Depending on the nature of the query and the database. Purpose Basic settings Creative Commons License Talend Open Studio Components 383 . Framework Database DB root path Username and Password Schema and Edit Schema Select your Java database framework on the list Name of the database Browse to your database root. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. hence can be reused. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. The fields that come after are pre-filled in using the fetched data.Databases components tJavaDBRow tJavaDBRow tJavaDBRow properties Component family Databases/JavaDB Function tJavaDBRow is the specific component for this database query. Property type Either Built-in or Repository. A schema is a row description.

384 Talend Open Studio Components Creative Commons License . see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Select this column from the use column list. If needed. Parameter Index: Enter the parameter position in the SQL instruction.Databases components tJavaDBRow Die on error This check box is selected by default. Performance levels are increased Advanced settings Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. This option is very useful if you need to execute the same query several times. Select this checkbox if you want to query the database using a PreparedStatement. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. This option ensures transaction quality (but not rollback) and above all better performance on executions. Number of rows to be completed before committing batches of rows together into the DB. In the Set PreparedStatement Parameter table. Parameter Type: Enter the parameter type. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Parameter Value: Enter the parameter value. This field is compulsory for DB data handling. Related scenarios For related topics. Select this check box to insert the result of the query into a COLUMN of the current flow. you can retrieve the rows on error via a Row > Rejects link. Clear the check box to skip the row on error and complete the process for error-free rows.

Databases components tJDBCColumnList tJDBCColumnList tJDBCColumnList Properties Component family Databases/JDBC Function Purpose Basic settings Iterates on all columns of a given table through a defined JDBC connection. Creative Commons License Talend Open Studio Components 385 . Table name Usage Limitation This component is to be used along with JDBC components. especially with tJDBCConnection. see Scenario: Iterating on a DB table and listing its column names on page 455. Lists all column names of a given JDBC table. Component list Select the tJDBCConnection component in the list if more than one connection are planned for the current Job. Enter the name of the tabe. n/a Related scenario For tJDBCColumnList related scenario.

n/a Related scenario No scenario is available for this component yet.Databases components tJDBCClose tJDBCClose tJDBCClose properties Component family Databases/JDBC Function Purpose Basic settings tJDBCClose closes the transaction committed in the connected DB. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. 386 Talend Open Studio Components Creative Commons License . especially with tJDBCConnection and tJDBCCommit. Close a transaction. Component list Select the tJDBCConnection component in the list if more than one connection are planned for the current Job. This component is to be used along with JDBC components.

see tMysqlConnection on page 460. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. It usually doesn’t make much sense to use JDBC components independently in a transaction. This check box is selected by default. n/a Related scenario This component is closely related to tJDBCConnection and tJDBCRollback. especially with the tJDBCConnection and tJDBCRollback components.Databases components tJDBCCommit tJDBCCommit tJDBCCommit Properties This component is closely related to tJDBCConnection and tJDBCRollback. your data will be commited row by row. Creative Commons License Talend Open Studio Components 387 . It usually doesn’t make much sense to use JDBC components without using the tJDBCConnection component to open a connection for the current transaction. In this case. do not select the Close connection check box or your connection will be closed before the end of your first row commit. Component family Databases/JDBC Function Purpose Validates the data processed through the Job into the connected DB. Using a unique connection. Component list Select the tJDBCConnection component in the list if more than one connection are planned for the current Job. It allows you to close the database connection once the commit is done. This component is to be used along with JDBC components. Clear this check box to continue to use the selected connection once the component has performed its task. If you want to use a Row > Main connection to link tAS400Commit to your Job. For tJDBCCommit related scenario. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.

. Usage Limitation This component is to be used along with JDBC components.Databases components tJDBCConnection tJDBCConnection tJDBCConnection Properties This component is closely related to tJDBCCommit and tJDBCRollback. Select this check box to display the Auto Commit check box. Driver JAR Driver Class Username and Password Encoding type Use or register a shared DB Connection Advanced settings Use Auto-Commit tStatCatcher Statistics Select this check box to collect log data at the component level. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. enter: jdbc:mysql://IP address/database name to connect to a mysql database. This field is compulsory for DB data handling. the auto-commit statement will be removed from the codes. once the data has been validated.mysql.jdbc. This component allows you to commit all of the Job data to an output database in just a single transaction. enter com. It usually doesn’t make much sense to use one of JDBC components without using the tJDBCConnection component to open a connection for the current transaction. Component family Databases/JDBC Function Purpose Basic settings Opens a connection to the database for a current transaction. Select this check box to share your connection or fetch a connection shared by a parent or child Job. Select from the drop-down list a desired available driver. Enter your DB authentication data. For example. Shared DB Connection Name: set or type in the shared connection name. For example. or download one from a local directory through clicking the three dots [. Once you clear the Use Auto-Commit check box. Select the encoding type from the list or select Custom and define it manually. Select it to activate auto commit mode. n/a 388 Talend Open Studio Components Creative Commons License ..Driver as a driver class to connect to a mysql database. JDBC URL Enter the JDBC URL to connect to the desired DB. Enter the driver class related o your connection.] button. especially with the tJDBCCommit and tJDBCRollback components.

It usually doesn’t make much sense to use one of JDBC components without using the tJDBCConnection component to open a connection for the current transaction. see tMysqlConnection on page 460. For tJDBCConnection related scenario.Databases components tJDBCConnection Related scenario This component is closely related to tJDBCCommit and tJDBCRollback. Creative Commons License Talend Open Studio Components 389 .

Databases components tJDBCInput tJDBCInput tJDBCInput properties Component family Databases/JDBC Function Purpose tJDBC reads any database using a JDBC API connection and extracts fields based on a query. see Setting up a DB connection of Talend Open Studio User Guide. For more information about Dynamic settings. see your studio user guide. Property type Either Built-in or Repository Built-in: No property data stored centrally. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. For more information on how to share a DB connection across Job levels. The fields that come after are pre-filled in using the fetched data. Basic settings 390 Talend Open Studio Components Creative Commons License . For more information about setting up and storing database connection parameters. In this case. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Repository: Select the repository file where Properties are stored. JDBC URL Driver JAR Class Name Type in the database location path Select the driver JAR on the list or click the three button to add a new JAR to the list. Type in the Class name to be pointed to in the driver. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise. Component list presents only the connection components in the same Job level. make sure the connection name is unique and distinctive all over through the two Job levels. When a Job contains the parent Job and the child Job. Then it passes on the field list to the next component via a Main row link. Use an existing connection Select this check box and click the relevant tJDBCConnection component on the Component list to reuse the connection details you already defined. make sure that the available connection components are sharing the intended connection. tJDBC executes a DB query with a strictly defined order which must correspond to the schema definition. so if you need to use an existing connection from the other level.

When selected. helps to decide the row set to work with at a time and thus optimize performance. Repository: The schema already exists and is stored in the Repository.Databases components tJDBCInput Username and Password Schema and Edit Schema DB user authentication data. i. it defines the number of fields to be processed and passed on to the next component. A schema is a row description. Table Name Type in the name of the table Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Remove leading and trailing whitespace from defined columns.. Advanced settings Encoding Type Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. Creative Commons License Talend Open Studio Components 391 .e. Built-in: The schema is created and stored locally for this component only. hence can be reused. The schema is either built-in or remotely stored in the Repository. Related scenarios Related topic in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component covers all possibilities of SQL queries onto any JDBC connected database. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

The fields that come after are pre-filled in using the fetched data. JDBC URL Driver JAR Class Name Type in the database location path Select the driver JAR on the list or click the three button to add a new JAR to the list. For more information about setting up and storing database connection parameters. see Setting up a DB connection of Talend Open Studio User Guide. so if you need to use an existing connection from the other level. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case.Databases components tJDBCOutput tJDBCOutput tJDBCOutput properties Component family Databases/JDBC Function Purpose Basic settings tJDBCOutput writes. Component list presents only the connection components in the same Job level. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Type in the Class name to be pointed to in the driver. based on the flow incoming from the preceding component in the Job. make sure that the available connection components are sharing the intended connection. Use an existing connection Select this check box and click the relevant tJDBCConnection component on the Component list to reuse the connection details you already defined. Otherwise. tJDBCOutput executes the action defined on the data contained in the table. makes changes or suppresses entries in any type of database connected to a JDBC API. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. For more information about Dynamic settings. 392 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository Built-in: No property data stored centrally. When a Job contains the parent Job and the child Job. updates. see your studio user guide. make sure the connection name is unique and distinctive all over through the two Job levels. Repository: Select the repository file where Properties are stored.

Do the same in the Key in delete column for the Delete operation. Built-in: The schema is created and stored locally for this component only. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). you can perform: Insert: Add new entries to the table. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. it defines the number of fields to be processed and passed on to the next component. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. Name of the table to be written. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. select the check boxes next to the column names you want to use as a base for the Update operation. Select the encoding type from the list or select Custom and define it manually. Die on error This check box is selected by default. Note that only one table can be written at a time On the data of the table defined. If needed. better performance at execution.e. This option ensures transaction quality (but not rollback) and. 393 Advanced settings Encoding Type Commit every Creative Commons License Talend Open Studio Components .. This field is compulsory for DB data handling. The schema is either built-in or remotely stored in the Repository. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. you can retrieve the rows on error via a Row > Rejects link. Related topic: Setting a Repository schema of Talend Open Studio User Guide. hence can be reused. To do that: Select the Use field options check box and then in the Key in update column. Clear the check box to skip the row on error and complete the process for error-free rows.Databases components tJDBCOutput Username and Password Table Action on data DB user authentication data. Schema and Edit Schema A schema is a row description. Job stops. i. For an advanced use. Enter the number of rows to be completed before committing batches of rows together into the DB. above all. If duplicates are found.

It also allows you to create a reject flow using a Row > Rejects link to filter data in error.Databases components tJDBCOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. This component must be used as an output component. or action that require particular preprocessing. Position: Select Before. Use field options Enable debug mode Use Batch Size Select this check box to customize a request. It allows you to carry out actions on a table or on the data of a table in a JDBC database. which are not insert. This option allows you to call SQL functions to perform actions on columns. nor update or delete actions. Replace or After following the action to be performed on the reference column. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For tJDBCOutput related topics. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. enables you to define the number of lines in each processed batch. 394 Talend Open Studio Components Creative Commons License . Select this check box to display each step during processing entries in a database. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. For an example of tMySqlOutput in use. especially when there is double action on data. When selected. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. tStatCatcher Statistics Select this check box to collect log data at the component level.

especially with tOracleConnection and tOracleCommit components. Component list Select the tJDBCConnection component in the list if more than one connection are planned for the current Job. This component is to be used along with Oracle components. n/a Related scenario This component is closely related to tJDBCConnection and tJDBCCommit. It usually doesn’t make much sense to use JDBC components without using the tJDBCConnection component to open a connection for the current transaction. For tJDBCRollback related scenario.Databases components tJDBCRollback tJDBCRollback tJDBCRollback properties This component is closely related to tJDBCCommit and tJDBCConnection. It usually doesn’t make much sense to use JDBC components independently in a transaction. see tMysqlRollback on page 498. Clear this check box to continue to use the selected connection once the component has performed its task.. Component family Databases/JDBC Function Purpose Basic settings Cancels the transaction committed in the connected DB. Avoid commiting part of a transaction accidentally. Creative Commons License Talend Open Studio Components 395 . Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.

see your studio user guide. Use an existing connection Select this check box and click the relevant tJDBCConnection component on the Component list to reuse the connection details you already defined. make sure the connection name is unique and distinctive all over through the two Job levels.. tJDBCRow acts on the actual DB structure or on the data (although without handling data). In this case. When a Job contains the parent Job and the child Job. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about Dynamic settings.e. JDBC URL Driver JAR Class Name Username and Password Schema and Edit Schema Type in the database location path Select the driver JAR on the list or click the three button to add a new JAR to the list. Type in the Class name to be pointed to in the driver. Depending on the nature of the query and the database. make sure that the available connection components are sharing the intended connection. The schema is either built-in or remotely stored in the Repository. The row suffix means the component implements a flow in the job design although it doesn’t provide output. For more information on how to share a DB connection across Job levels. DB user authentication data. Component list presents only the connection components in the same Job level. so if you need to use an existing connection from the other level.Databases components tJDBCRow tJDBCRow tJDBCRow properties Component family Databases/JDBC Function tJDBCRow is the component for any type database using a JDBC API. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. it defines the number of fields to be processed and passed on to the next component. A schema is a row description. Otherwise. Built-in: The schema is created and stored locally for this component only. It executes the SQL query stated onto the specified database. i. Related topic: Setting a built-in schema of Talend Open Studio User Guide. The SQLBuilder tool helps you write easily your SQL statements. Purpose Basic settings 396 Talend Open Studio Components Creative Commons License .

Parameter Value: Enter the parameter value. This option ensures transaction quality (but not rollback) and above all better performance on executions. In the Set PreparedStatement Parameter table. Query type Either Built-in or Repository. Select this check box to insert the result of the query into a COLUMN of the current flow. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. This field is compulsory for DB data handling.Databases components tJDBCRow Repository: The schema already exists and is stored in the Repository. Parameter Index: Enter the parameter position in the SQL instruction. Related scenarios For related topics. Number of rows to be completed before committing batches of rows together into the DB. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Clear the check box to skip the row on error and complete the process for error-free rows. The Query field gets accordingly filled in. you can retrieve the rows on error via a Row > Rejects link. Performance levels are increased Encoding Type Select the encoding from the list or select Custom and define it manually. Select this checkbox if you want to query the database using a PreparedStatement. Usage This component offers the flexibility benefit of any type DB JDBC connection and covers all possibilities of SQL queries. Select this column from the use column list. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 Creative Commons License Talend Open Studio Components 397 . If needed. hence can be reused. This option is very useful if you need to execute the same query several times. This check box is selected by default. Parameter Type: Enter the parameter type. Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Commit every tStatCatcher Statistics Select this check box to collect log data at the component level.

Databases components tJDBCRow • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. 398 Talend Open Studio Components Creative Commons License .

rather than single value. the schema is an input parameter. Built-in: The schema is created and stored locally for this component only. The schema is either built-in or remotely stored in the Repository. JDBC URL Driver JAR Class Name Username and Password Schema and Edit Schema Type in the database location path Select the driver JAR on the list or click the three button to add a new JAR to the list.Databases components tJDBCSP tJDBCSP tJDBCSP Properties Component family Databases/JDBC Function Purpose Basic settings tJDBCSP calls the specified database stored procedure. Type in the Class name to be pointed to in the driver.e. Related topic: Setting a built-in schema of Talend Open Studio User Guide. tJDBCSP offers a convenient way to centralize multiple or complex queries in a database and call them easily.. Creative Commons License Talend Open Studio Components 399 . Note that the SP schema can hold more columns than there are paramaters used in the procedure. Select on the list the schema column. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository. RECORDSET: Input parameters is to be returned as a set of values. if a value only is to be returned. In SP principle. A schema is a row description. Click the Plus button and select the various Schema Columns that will be required by the procedures. Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. DB user authentication data. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameters is to be returned as value. likely after modification through the procedure (function). i. the value to be returned is based on. hence can be reused. it defines the number of fields to be processed and passed on to the next component. SP Name Is Function / Return result in Parameters Type in the exact name of the Stored Procedure Select this check box .

• tOracleSP Scenario: Checking number format using a stored procedure on page 564 Check as well the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. see: • tMysqlSP Scenario: Finding a State Label using a stored procedure on page 512.Databases components tJDBCSP Usage Limitation This component is used as intermediary component. 400 Talend Open Studio Components Creative Commons License . The Stored Procedures syntax should match the Database syntax. It can be used as start component but only input parameters are thus allowed. Related scenario For related scenarios.

Usage Limitation This component is to be used along with JDBC components. see Scenario: Iterating on a DB table and listing its column names on page 455. Component list Select the tJDBCConnection component in the list if more than one connection are planned for the current Job. n/a Related scenario For tJDBCTableList related scenario. Where clause for table Enter the Where clause to identify the tables to iterate name selection on. especially with tJDBCConnection.Databases components tJDBCTableList tJDBCTableList tJDBCTableList Properties Component family Databases/JDBC Function Purpose Basic settings Iterates on a set of table names through a defined JDBC connection. Lists the names of a given set of JDBC tables using a select statement based on a Where clause. Creative Commons License Talend Open Studio Components 401 .

Once selected. Always is to be used: Always: Always dereference aliases Never: Never dereferences aliases. When this option is chosen. Then it passes on the field list to the next component via a Main row link. TLS: certificate is used. When selected. Searching:Dereferences aliases only after name resolution. Never improves search performance if you are sure that no alias is to be dereferenced. Note that the login must match the LDAP syntax requirement to be valid. Type in the filter as expected by the LDAP directory db. the fields to follow are pre-filled in using fetched data. Select the protocol type on the list.Databases components tLDAPAttributesInput tLDAPAttributesInput tLDAPAttributesInput Properties Component family Databases/LDAP Function Purpose tLDAPAttributesInput analyses each object found via the LDAP query and lists a collection of attributes associated with the object. Path to user’s authorised tree leaf. the Advanced CA check box appears. However. Repository: Select the Repository file where Properties are stored. Type in the value separator in multi-value fields. LDAP : no encryption is used LDAPS: secured LDAP.g. When this option is chosen. the Advanced CA check box appears and is used the same way as that of the LDAPS type. Select the Authentication check box if LDAP login is required. By default. Finding: Dereferences aliases only during name resolution Basic settings Authentication User and Password Filter Multi valued field separator Alias dereferencing 402 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository Built-in: No property data stored centrally. you can still deactivate this certificate validation by selecting the Trust all certs check box. the advanced mode allows you to specify the directory and the keystore password of the certificate file for storing a specific CA.: “cn=Directory Manager”. e. Select the option on the list. Host Port Base DN Protocol LDAP Directory server IP address Listening port number of server. tLDAPAttributesInput executes an LDAP query based on the given filter and corresponding to the schema definition.

. including the GetResultName variable to retrieve automatically the relevant Base Creative Commons License Talend Open Studio Components 403 . Hence you should use the Built-in mode. If needed. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Note: Press Ctrl + Space bar to access the global variable list. it defines the number of fields to be processed and passed on to the next component. Fill in a timeout period for the directory. As this component is intended to list the attributes associated with a LDAP object. even though you may need to add some new columns. Clear the check box to skip the row on error and complete the process for error-free rows.objectattributes: list of attributes that are essential for the analysed object. you can retrieve the rows on error via a Row > Rejects link.e. i. Select this check box to gather the job processing metadata at a job level as well as at each component level. A schema is a row description. This check box is selected by default. access Specify the number of entries returned at a time by the LDAP server.optionalattributes: list of optional attributes to these classes . its schema is then pre-defined. Usage This component covers all possibilities of LDAP queries.mandatoryattributes: list of mandatory attributes to these classes .objectclass: list of object classes . Limit Time Limit Paging Die on error Schema and Edit Schema Advanced settings Class Definition Root tStatCatcher Statistics Specify the root of the object class definition namespace. You should retain these established columns. Built-in: The schema is created and stored locally for this component only.Databases components tLDAPAttributesInput Referral handling Select the option on the list: Ignore: does not handle request redirections Follow:does handle request redirections Fill in a limit number of records to be read If needed. Repository: The schema already exists and is stored in the Repository. The pre-defined schema lists: .

Hence for tLDAPInput related scenario.Databases components tLDAPAttributesInput Related scenario The tLDAPAttributesInput component follows the usage similar to that of tLDAPInput. see Scenario: Displaying LDAP directory’s filtered content on page 406. 404 Talend Open Studio Components Creative Commons License .

g. For more information about setting up and storing database connection parameters. Property type Either Built-in or Repository Built-in: No property data stored centrally. Note that the login must match the LDAP syntax requirement to be valid. the fields to follow are pre-filled in using fetched data. see Setting up a DB connection of Talend Open Studio User Guide. Once selected. Then it passes on the field list to the next component via a Main row link.: “cn=Directory Manager”. LDAP : no encryption is used LDAPS: secured LDAP. TLS: certificate is used When this option is chosen. Repository: Select the Repository file where Properties are stored. When selected. When this option is chosen. e. Path to user’s authorised tree leaf. Host Port Base DN Protocol LDAP Directory server IP address Listening port number of server. the advanced mode allows you to specify the directory and the keystore password of the certificate file for storing a specific CA. Basic settings Authentication User and Password Filter Multi valued field separator Creative Commons License Talend Open Studio Components 405 . Type in the value separator in multi-value fields. tLDAPInput executes an LDAP query based on the given filter and corresponding to the schema definition. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. you can still deactivate this certificate validation by selecting the Trust all certs check box. the Advanced CA check box appears and is used the same way as that of the LDAPS type.Databases components tLDAPInput tLDAPInput tLDAPInput Properties Component family Databases/LDAP Function Purpose tLDAPInput reads a directory and extracts data based on the defined filter. Select the Authentication check box if LDAP login is required. Type in the filter as expected by the LDAP directory db. However. Select the protocol type on the list. the Advanced CA check box appears.

Searching:Dereferences aliases only after name resolution. hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide. A schema is a row description. Repository: The schema already exists and is stored in the Repository. Always is to be used: Always: Always dereference aliases Never: Never dereferences aliases. access Specify the number of entries returned at a time by the LDAP server. Fill in a timeout period for the directory. This check box is selected by default.e. By default. • Drop the tLDAPInput component along with a tLogRow from the Palette to the design workspace. Clear the check box to skip the row on error and complete the process for error-free rows. you can retrieve the rows on error via a Row > Rejects link. 406 Talend Open Studio Components Creative Commons License . Finding: Dereferences aliases only during name resolution Select the option on the list: Ignore: does not handle request redirections Follow:does handle request redirections Fill in a limit number of records to be read If needed. Never improves search performance if you are sure that no alias is to be dereferenced. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i. Built-in: The schema is created and stored locally for this component only. Note: Press Ctrl + Space bar to access the global variable list.. The schema is either built-in or remotely stored in the Repository. Referral handling Limit Time Limit Paging Die on error Schema and Edit Schema Usage This component covers all possibilities of LDAP queries. including the GetResultName variable to retrieve automatically the relevant Base Scenario: Displaying LDAP directory’s filtered content The Job described below simply filters the LDAP directory and displays the result on the console.Databases components tLDAPInput Alias dereferencing Select the option on the list. it defines the number of fields to be processed and passed on to the next component. If needed. • Set the tLDAPInput properties.

• No particular Base DN is to be set. the filter is: (&(objectClass=inetorgperson)&(uid=PIERRE DUPONT)). • Select the Authentication check box and fill in the login information if required to read the directory. • Set Ignore as Referral handling. Host can be the IP address of the LDAP directory server or its DNS name. In this example: a simple LDAP protocol is used. • In the Filter area. no authentication is needed. • Fill in Multi-valued field separator with a comma as some fields may hold more than one value. • Then select the relevant Protocol on the list. • In Built-In mode. fill in the Host and Port information manually. • As we don’t know if some aliases are used in the LDAP directory. select Always on the list. • Set the limit to 100 for this use case.Databases components tLDAPInput • Set the Property type on Repository if you stored the LDAP connection details in the Metadata Manager in the Repository. type in the command. Creative Commons License Talend Open Studio Components 407 . Then select the relevant entry on the list. In this example. separated by a comma. the data selection is based on. In this use case.

no particular setting is required. the schema is made of 6 columns including the objectClass and uid columns which get filtered on. In this example. Only one entry of the directory corresponds to the filter criteria given in the tLDAPInput component. • In the tLogRow component.Databases components tLDAPInput • Set the Schema as required by your LDAP directory. 408 Talend Open Studio Components Creative Commons License .

Select the protocol type on the list. Once selected. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored.: “cn=Directory Manager”. Host Port Base DN Protocol LDAP Directory server IP address. The fields that come after are pre-filled in using the fetched data. For more information about setting up and storing database connection parameters. However. Basic settings User and Password Multi valued field separator Creative Commons License Talend Open Studio Components 409 . Property type Either Built-in or Repository. When this option is chosen. Listening port number of server. Then it passes on the field list to the next component via a Main row link. string or regular expression to separate data in a multi-value field.Databases components tLDAPOutput tLDAPOutput tLDAPOutput Properties Component family Databases/LDAP Function Purpose tLDAPOutput writes into an LDAP directory.g. see Setting up a DB connection of Talend Open Studio User Guide. Path to user’s authorized tree leaf. e. TLS: certificate is used When this option is chosen. the Advanced CA check box appears and is used the same way as that of the LDAPS type. the advanced mode allows you to specify the directory and the keystore password of the certificate file for storing a specific CA. the Advanced CA check box appears. LDAP : no encryption is used LDAPS: secured LDAP. Character. you can still deactivate this certificate validation by selecting the Trust all certs check box. tLDAPOutput executes an LDAP query based on the given filter and corresponding to the schema definition. Fill in the User and Password as required by the directory Note that the login must match the LDAP syntax requirement to be valid. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

Repository: The schema already exists and is stored in the Repository. This component allows you to carry out actions on a table or on the data of a table in an database. Insert or Update: insert new data or update existing ones. Advanced settings Usage tStatCatcher Statistics This component covers all possibilities of LDAP queries. Clear the check box to skip the row on error and complete the process for error-free rows. Select this check box to gather the job processing metadata at a job level as well as at each component level. Never improves search performance if you are sure that no aliases is to be dereferenced. it defines the number of fields to be processed and passed on to the next component.Databases components tLDAPOutput Alias dereferencing Select the option on the list. Referral handling Insert mode DN Column Name Schema and Edit Schema Die on error This check box is selected by default. A schema is a row description. Related topic: Setting a Repository schema of Talend Open Studio User Guide. To keep it simple. Searching:Dereferences aliases only after name resolution.. i.e. see Scenario 3: Retrieve data in error with a Reject link on page 483 Scenario: Editing data in a LDAP directory The following scenario describes a Job that reads an LDAP directory. If needed. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Insert: insert new data. Finding: Dereferences aliases only during name resolution Select the option on the list: Ignore: does not handle request redirections Follow:does handle request redirections Select the editing mode on the list: Add: add a value in a multi-value attribute. updates the email of a selected entry and displays the output before writing the LDAP directory. hence can be reused. Delete: remove the selected data from the directory. no alias dereferencing nor referral handling is performed. Select in the list the type of the LDAP input entity used. Note: Press Ctrl + Space bar to access the global variable list. The schema is either built-in or remotely stored in the Repository. Always is to be used: Always: Always dereference aliases Never: Never dereferences aliases. including the GetResultName variable to retrieve the relevant DN Base automatically. By default. you can retrieve the rows on error via a Row > Reject link. For an example of tMySqlOutput in use. Updata: updates the existing data. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This scenario is based on LDAPInput’s Scenario: 410 Talend Open Studio Components Creative Commons License . Built-in: The schema is created and stored locally for this component only.

objectclass. • Drag & drop the uid column from the input table to the output as no change is required on this column. In this example. • Connect the input component to the tMap then to the tLogRow and to the output component. whom email is to be updated. set the connection details to the LDAP directory server as well as the filter as described in Scenario: Displaying LDAP directory’s filtered content on page 406.com. Creative Commons License Talend Open Studio Components 411 . the GetResultName global variable is used to retrieve this path automatically.Dupont@talend. • In the Expression field of the dn column (output). • In the tLDAPInput Component view. • Drop the tLDAPInput. • Then open the mapper to set the edit to be carried out. • In the mail column’s expression field. by removing the unused fields: dc. fill in with the exact expression expected by the LDAP server to reach the target tree leaf and allow directory writing on the condition that you haven’t set it already in the Base DN field of the tLDAPOutput component. • In this use case. tLDAPOutput. we change to Pierre. related to an organisational person. • Change the schema to make it simpler. The result returned was a single entry.Databases components tLDAPOutput Displaying LDAP directory’s filtered content on page 406. ou. • The tLogRow component doesn’t need any particular setting. type in the new email that will overwrite the current data in the LDAP directory. Press Ctrl+Space bar to access the variable list and select tLDAPInput_1_RESULT_NAME. • Click OK to validate the changes. tMap and tLogRow components from the Palette to the design workspace.

therefore only the highest accessible leaf is given: o=directoryRoot. the full DN is provided by the dn output from the tMap component. The output shows the following fields: dn. • Select the relevant protocol to be used: LDAP for this example. • The Insert mode for this use case is Update (the email address). • In Base DN field.Databases components tLDAPOutput • Then select the tLDAPOutput component to set the directory writing properties. • The schema was provided by the previous component through the propagation operation. set the highest tree leaf you have the rights to access. • Save the Job and execute. 412 Talend Open Studio Components Creative Commons License . respectively Always and Ignore. then fill in it here. uid and mail as defined in the Job. • Set the Port and Host details manually if they aren’t stored in the Repository. • Use the default setting of Alias Dereferencing and Referral Handling fields. In this use case. If you haven’t set previously the exact and full path of the target DN you want to access. • Then fill in the User and Password as expected by the LDAP directory.

Select the protocol type on the list. A schema is a row description. Built-in: The schema is created and stored locally for this component only. i. Select the option on the list: Ignore: does not handle request redirections. Note that the login must match the LDAP syntax requirement to be valid. Fill in user authentication information. LDAPS: secured LDAP.Databases components tLDAPRenameEntry tLDAPRenameEntry tLDAPRenameEntry properties Component family Databases/LDAP Function Purpose Basic settings tLDAPRenameEntry renames entries in an LDAP directory. LDAP: no encryption is used. Finding: Dereferences aliases only during name resolution. Property type Either Built-in or Repository. Host Port Base DN Protocol LDAP directory server IP address. Always is to be used: Always: Always dereference aliases. Select from the list the schema column that holds the old DN (Previous DN) and the column that holds the new DN (New DN). User and Password Alias dereferencing Referrals handling Previous DN and New DN Schema and Edit Schema Creative Commons License Talend Open Studio Components 413 . Repository: Select the repository file where Properties are stored. Select the option on the list.e. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Never improves search performance if you are sure that no alias is to be dereferenced.: “cn=Directory Manager”. Path to user’s authorized tree leaf. Never: Never dereferences aliases. By default. Searching: Dereferences aliases only after name resolution. Built-in: No property data stored centrally. The fields that come after are pre-filled in using the fetched data. e. The schema is either built-in or remotely stored in the Repository. it defines the number of fields to be processed and passed on to the next component. Number of the listening port of the server. The tLDAPRenameEntry component rename ones or more entries in a specific LDAP directory.g. Follow: does handle request redirections. TLS: certificate is used..

you can retrieve the rows on error via a Row > Reject link. Related scenarios For use cases in relation with tLDAPRenameEntry.Databases components tLDAPRenameEntry Repository: The schema already exists and is stored in the Repository. 414 Talend Open Studio Components Creative Commons License . Die on error This check box is selected by default. It is usually used as a one-component subjob but you can use it with other components as well. Clear the check box to skip the row on error and complete the process for error-free rows. Advanced settings Usage tStatCatcher Statistics This component covers all possibilities of LDAP queries. • tLDAPOutput Scenario: Editing data in a LDAP directory on page 410. including the GetResultName variable to retrieve automatically the relevant DN Base. hence can be reused. Select this check box to collect log data at the component level. Note: Press Ctrl + Space bar to access the global variable list. If needed. Related topic: Setting a Repository schema of Talend Open Studio User Guide. see the following scenarios: • tLDAPInput Scenario: Displaying LDAP directory’s filtered content on page 406.

i. Table name Type in the table name. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Property type Either Built-in or Repository Built-in: No property data stored centrally. DB user authentication data. A schema is a row description.. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Then it passes on the field list to the next component via a Main row link.e. Built-in: The schema is created and stored locally for this component only. Creative Commons License Talend Open Studio Components 415 . Name of the database. The fields that come after are pre-filled in using the fetched data. tMaxDBInput executes a DB query with a strictly defined order which must correspond to the schema definition. Host name Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. For more information about setting up and storing database connection parameters.Databases components tMaxDBInput tMaxDBInput tMaxDBInput properties Component Family Databases/MaxDB Function Purpose tMaxDBInput reads a database and extracts fields based on a query. hence can be reused. The schema is either built-in or remotely stored in the Repository. Repository: The schema already exists and is stored in the Repository. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. see Setting up a DB connection of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Basic settings Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Repository: Select the repository file where Properties are stored.

see: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 416 Talend Open Studio Components Creative Commons License .Databases components tMaxDBInput Guess schema Advanced settings Trim all the String/Char columns Trim column Click the Guess schema button to retrieve the table schema. Related scenario For a related scenario. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Remove leading and trailing whitespace from defined columns. tStatCatcher Statistics Select this check box to collect log data at the component level.

Name of the database. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Repository: Select the repository file where Properties are stored. you can perform one of the following operations: None: No operation is carried out. Create table if not exists: The table is created if it does not exist. see Setting up a DB connection of Talend Open Studio User Guide. Basic settings Action on table Creative Commons License Talend Open Studio Components 417 . On the table defined. makes changes or suppresses entries in a database. based on the flow incoming from the preceding component in the job. Drop and create table: The table is removed and created again. For more information about setting up and storing database connection parameters. You do not have the possibility to rollback the operation. Listening port number of DB server. Create table: The table does not exist and gets created. DB user authentication data. tMaxDBOutput executes the action defined on the table and/or on the data contained in the table. updates. Property type Either Built-in or Repository Built-in: No property data stored centrally. Clear table: The table content is deleted. The fields that come after are pre-filled in using the fetched data. Name of the table to be written.Databases components tMaxDBOutput tMaxDBOutput tMaxDBOutput properties Component Family Databases/MaxDB Function Purpose tMaxDBOutput writes. Truncate table: The table content is deleted. Host Port Database Username and Password Table Database server IP address.

better performance at execution. Built-in: The schema is created and stored locally for this component only. The schema is either built-in or remotely stored in the Repository. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. Related topic: Setting a built-in schema of Talend Open Studio User Guide. select the check boxes next to the column names you want to use as a base for the Update operation. you can perform: Insert: Add new entries to the table. This field is compulsory for DB data handling. For an advanced use. above all.Databases components tMaxDBOutput Action on data On the data of the table defined. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. Repository: The schema already exists and is stored in the Repository. Set the encoding manually. Advanced settings Encoding Commit every 418 Talend Open Studio Components Creative Commons License . Do the same in the Key in delete column for the Delete operation. Schema and Edit Schema A schema is a row description. job stops.e. This option ensures transaction quality (but not rollback) and. it defines the number of fields to be processed and passed on to the next component. If duplicates are found. Clear the check box to skip the row on error and complete the process for error-free rows.. Enter the number of rows to be completed before committing batches of rows together into the DB. Related topic: Setting a Repository schema of Talend Open Studio User Guide. you can retrieve the rows on error via a Row > Rejects link. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). If needed. hence can be reused. i. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. Die on error This check box is selected by default. To do that: Select the Use field options check box and then in the Key in update column.

especially when there is double action on data. tStatCatcher Statistics Select this check box to collect log data at the component level. see: • Scenario: Displaying DB output on page 258 from tDBOutput. nor update or delete actions. This component must be used as an output component. see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenario For a related scenario. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. This option allows you to call SQL functions to perform actions on columns. • Scenario 1: Adding a new column and altering data in a DB table on page 476 from tMySQLOutput. Creative Commons License Talend Open Studio Components 419 . Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. It allows you to carry out actions on a table or on the data of a table in a database. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. or action that require particular preprocessing.Databases components tMaxDBOutput Additional Columns This option is not offered if you create (with or without drop) the DB table. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Position: Select Before. which are not insert. Replace or After following the action to be performed on the reference column. For an example of tMySqlOutput in use. Use field options Enable debug mode Select this check box to customize a request. Select this check box to display each step during processing entries in a database.

Purpose Basic settings Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Host Port Database Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. Name of the database. DB user authentication data. Depending on the nature of the query and the database. A schema is a row description. Clear the check box to skip the row on error and complete the process for error-free rows.. Die on error 420 Talend Open Studio Components Creative Commons License . Repository: The schema already exists and is stored in the Repository. Built-in: The schema is created and stored locally for this component only. Table name Type in the table name. If needed.Databases components tMaxDBRow tMaxDBRow tMaxDBRow properties Component Family Databases/MaxDB Function tMaxDBRow is the specific component for this database query. it defines the number of fields to be processed and passed on to the next component. The SQLBuilder tool helps you write easily your SQL statements. you can retrieve the rows on error via a Row > Rejects link. Property type Either Built-in or Repository Built-in: No property data stored centrally. The row suffix means the component implements a flow in the job design although it doesn’t provide output. The fields that come after are pre-filled in using the fetched data. This check box is selected by default. hence can be reused. tMaxDBRow acts on the actual DB structure or on the data (although without handling data). It executes the SQL query stated onto the specified database.e. Repository: Select the repository file where Properties are stored. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i. The schema is either built-in or remotely stored in the Repository. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

This option ensures transaction quality (but not rollback) and above all better performance on executions. This field is compulsory for DB data handling. Parameter Value: Enter the parameter value. Parameter Index: Enter the parameter position in the SQL instruction. This option is very useful if you need to execute the same query several times. Select this column from the use column list. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Parameter Type: Enter the parameter type. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Related scenario For a related scenario. see: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Creative Commons License Talend Open Studio Components 421 . Number of rows to be completed before committing batches of rows together into the DB. In the Set PreparedStatement Parameter table. tStatCatcher Statistics Select this check box to collect log data at the component level. Performance levels are increased Encoding Commit every Set manually the encoding type.Databases components tMaxDBRow Advanced settings Propagate QUERY’s recordset Use PreparedStatement Select this check box to insert the result of the query into a COLUMN of the current flow. Select this checkbox if you want to query the database using a PreparedStatement.

Databases components tMSSqlBulkExec tMSSqlBulkExec tMSSqlBulkExec properties tMSSqlOutputBulk and tMSSqlBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. Otherwise. As a dedicated component. These two steps compose the tMSSqlOutputBulkExec component. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. Name of the schema. Repository: Select the Repository file where Properties are stored. DB user authentication data. For more information about Dynamic settings. Built-in: No property data is stored centrally. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. When a Job contains the parent Job and the child Job. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. Component family Databases/MSSql Function Purpose Basic settings Executes the Insert action on the data provided. make sure that the available connection components are sharing the intended connection. see your studio user guide. the fields to follow are pre-filled in using fetched data. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading in the database. detailed in a separate section. In this case. When selected. Component list presents only the connection components in the same Job level. 422 Talend Open Studio Components Creative Commons License . For more information on how to share a DB connection across Job levels. make sure the connection name is unique and distinctive all over through the two Job levels. Name of the database. so if you need to use an existing connection from the other level. tMSSqlBulkExec offers gains in performance while carrying out the Insert operations to a MSSql database Property type Either Built-in or Repository.

Repository: The schema already exists and is stored in the Repository. hence can be reused. You do not have the possibility to rollback the operation.. it defines the number of fields to be processed and passed on to the next component. Select the action to be carried out Bulk insert Bulk update Bcp query out Depending on the action selected. string or regular expression to separate fields. i. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Drop and create table: The table is removed and created again. the requied information varies.Databases components tMSSqlBulkExec Table Name of the table to be written. Truncate table: The table content is deleted. Create table if not exists: The table is created if it does not exist. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Create table: The table does not exist and gets created. Specify additional connection properties for the DB connection you are creating. Related topic: Setting a built-in schema of Talend Open Studio User Guide. On the table defined. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Clear table: The table content is deleted. you can perform one of the following operations: None: No operation is carried out.e. A schema is a row description. Built-in: The schema is created and stored locally for this component only. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. string or regular expression to separate rows. Character. The schema is either built-in or remotely stored in the Repository. Character. Action on table Schema and Edit Schema Remote File Name Name of the file to be processed. Type in the number of the row where the action should start This value can be any of the followings: OEM (by default value) ACP RAW User-defined Advanced settings Action Bulk insert & Bulk update Additional JDBC parameters Fields terminated Rows terminated First row Code page Creative Commons License Talend Open Studio Components 423 .

tStatCatcher Statistics Select this check box to collect log data at the component level. Used together. Related scenarios For uses cases in relation with tMSSqlBulkExec. Usage This component is to be used along with tMSSqlOutputBulk component. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 424 Talend Open Studio Components Creative Commons License . to global variable.Databases components tMSSqlBulkExec Data file type Output Select the type of data being handled. Bcp query out Fields terminated Rows terminated Data file type Output Character. Select the type of output to pass the processed data onto: to console: data is viewed in the Log view. string or regular expression to separate fields. Select the type of output for the standard output of the MSSql database: to console. Character. Select the type of data being handled. string or regular expression to separate rows. to global variable: data is put in output variable linked to a tsystem component tStatCatcher Statistics Select this check box to collect log data at the component level. they can offer gains in performance while feeding a MSSql database.

Databases components Creative Commons License Talend Open Studio Components 425 .

n/a Related scenario For tMSSqlColumnList related scenario. Lists all column names of a given MSSql table. Enter the name of the tabe.Databases components tMSSqlColumnList tMSSqlColumnList tMSSqlColumnList Properties Component family Databases/MS SQL Function Purpose Basic settings Iterates on all columns of a given table through a defined MS SQL connection. see Scenario: Iterating on a DB table and listing its column names on page 455. especially with tMSSqlConnection. Table name Usage Limitation This component is to be used along with MSSql components. Component list Select the tMSSqlConnection component in the list if more than one connection are planned for the current job. 426 Talend Open Studio Components Creative Commons License .

n/a Related scenario No scenario is available for this component yet. Component list Select the tMssqlConnection component in the list if more than one connection are planned for the current Job. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tMssqlConnection and tMssqlCommit.Databases components tMSSqlClose tMSSqlClose tMSSqlClose properties Component family Databases/MSSql Function Purpose Basic settings tMssqlClose closes the transaction committed in the connected DB. This component is to be used along with tMssql components. Close a transaction. Creative Commons License Talend Open Studio Components 427 .

Component family Databases/MSSql Function Purpose tMSSqlCommit validates the data processed through the job into the connected DB. This component is to be used along with Mssql components. It usually does not make much sense to use these components independently in a transaction. 428 Talend Open Studio Components Creative Commons License .. It allows you to close the database connection once the commit is done. Clear this check box to continue to use the selected connection once the component has performed its task. see Scenario: Inserting data in mother/daughter tables on page 460. do not select the Close connection check box or your connection will be closed before the end of your first row commit. Basic settings Close connection Advanced settings tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. This check box is selected by default. your data will be commited row by row.Databases components tMSSqlCommit tMSSqlCommit tMSSqlCommit properties This component is closely related to tMSSqlConnection and tMSSqlRollback. Component list Select the tMSSqlConnection component in the list if more than one connection are planned for the current Job. For a tMSSqlCommit related scenario. n/a Usage Limitation Related scenarios This component is closely related to tMSSqlConnection and tMSSqlRollback. In this case. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. Using a unique connection. It usually does not make much sense to use one of these without using a tMSSqlConnection component to open a connection for the current transaction. If you want to use a Row > Main connection to link tAS400Commit to your Job.. especially with tMSSqlConnection and tMSSqlRollback components.

DB user authentication data. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. n/a Creative Commons License Talend Open Studio Components 429 . Select the encoding type from the list or select Custom and define it manually. Usage Limitation This component is to be used along with MSSql components. Property type Either Built-in or Repository. Listening port number of DB server. The fields that come after are pre-filled in using the fetched data. Component family Databases/MSSQL Function Purpose Basic settings tMSSqlConnection opens a connection to the database for a current transaction. Host Port Schema Database Username and Password Encoding type Database server IP address. This component allows you to commit all of the Job data to an output database in just a single transaction. Both components are usually used with a tMSSqlConnection component to open a connection for the current transaction. Built-in: No property data stored centrally. especially with tMSSqlCommit and tMSSqlRollback.Databases components tMSSqlConnection tMSSqlConnection tMSSqlConnection properties This component is closely related to tMSSqlCommit and tMSSqlRollback. Name of the database. This field is compulsory for DB data handling. Schema name. once the data has been validated. Additional JDBC parameters Use or register a shared DB Connection Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. Select this check box to share your connection or fetch a connection shared by a parent or child Job. Repository: Select the repository file where Properties are stored. Select this check box to automatically commit a transaction when it is completed. Shared DB Connection Name: set or type in the shared connection name. Specify additional connection properties for the DB connection you are creating.

see Scenario: Inserting data in mother/daughter tables on page 460. It usually does not make much sense to use one if these without using a tMSSqlConnection component to open a connection for the current transaction.Databases components tMSSqlConnection Related scenarios This component is closely related to tMSSqlCommit and tMSSqlRollback. 430 Talend Open Studio Components Creative Commons License . For tMSSqlConnection related scenario.

When a Job contains the parent Job and the child Job. In this case. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Repository: Select the repository file where Properties are stored. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. For more information on how to share a DB connection across Job levels. make sure the connection name is unique and distinctive all over through the two Job levels. The fields that come after are pre-filled in using the fetched data. Host Port Database Schema Database server IP address Listening port number of DB server. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. tMSSqlInput executes a DB query with a strictly defined order which must correspond to the schema definition. so if you need to use an existing connection from the other level. Then it passes on the field list to the next component via a Main row link. see your studio user guide.Databases components tMSSqlInput tMSSqlInput tMSSqlInput properties Component family Databases/MS SQL Server tMSSqlInput reads a database and extracts fields based on a query. For more information about setting up and storing database connection parameters. Property type Either Built-in or Repository Built-in: No property data stored centrally. Otherwise. Name of the database Name of the schema Function Purpose Basic settings Creative Commons License Talend Open Studio Components 431 . see Setting up a DB connection of Talend Open Studio User Guide. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about Dynamic settings. make sure that the available connection components are sharing the intended connection. Component list presents only the connection components in the same Job level.

e. Repository: The schema already exists and is stored in the Repository. Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating.. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Encoding Type Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Built-in: The schema is created and stored locally for this component only. 432 Talend Open Studio Components Creative Commons License . hence can be reused. Select the encoding from the list or select Custom and define it manually. Remove leading and trailing whitespace from defined columns.. Usage This component covers all possibilities of SQL queries onto a MS SQL server database.Databases components tMSSqlInput Username and Password Schema and Edit Schema DB user authentication data. A schema is a row description. This field is compulsory for DB data handling. i. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Related scenarios Related topics in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. The schema is either built-in or remotely stored in the Repository. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. Function Purpose Basic settings Advanced settings Usage tStatCatcher Statistics Select this check box to collect log data at the component level. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component.e. Schema and Edit Schema A schema is a row description. tMSSqlLastInsertId enables you to retrieve the last primary keys added by a user to a MSSql table. see Scenario: Get the ID for the last inserted record on page 467. Related scenario For a related scenario. Repository: The schema already exists and is stored in the Repository. Component list Select the tMSSqlConnection component on the Component list to reuse the connection details you already defined. if there are more than one component in this list. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only.. i. This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.. hence can be reused. Creative Commons License Talend Open Studio Components 433 .Databases components tMSSqlLastInsertId tMSSqlLastInsertId tMSSqlLastInsertId properties Component Family Databases/MS SQL server tMSSqlLastInsertId displays the last IDs added to a table from a MSSql specified connection.

For more information on how to share a DB connection across Job levels. make sure the connection name is unique and distinctive all over through the two Job levels. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. Component list presents only the connection components in the same Job level. updates. Built-in: No property data stored centrally. see Setting up a DB connection of Talend Open Studio User Guide. The fields that come after are pre-filled in using the fetched data. Repository: Select the repository file where Properties are stored. makes changes or suppresses entries in a database. make sure that the available connection components are sharing the intended connection. based on the flow incoming from the preceding component in the job. Name of the database Name of the schema Function Purpose Basic settings 434 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.Databases components MSSqlOutput MSSqlOutput tMSSqlOutput properties Component family Databases/MS SQL server tMSSqlOutput writes. Otherwise. In this case. so if you need to use an existing connection from the other level. tMSSqlOutput executes the action defined on the table and/or on the data contained in the table. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Host Port Database Schema Database server IP address Listening port number of DB server. see your studio user guide. When a Job contains the parent Job and the child Job. For more information about setting up and storing database connection parameters. For more information about Dynamic settings.

it defines the number of fields to be processed and passed on to the next component. Create a table: The table does not exist and gets created. If duplicates are found.. Turn on identity insert Select this check box to use your own sequence for the identity value of the inserted records (instead of having the SQL Server pick the next sequential value). Truncate table: The table content is deleted. Do the same in the Key in delete column for the Delete operation. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Drop and create a table: The table is removed and created again. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. select the check boxes next to the column names you want to use as a base for the Update operation. Action on data On the data of the table defined. The schema is either built-in or remotely stored in the Repository. you can perform one of the following operations: None: No operation is carried out. For an advanced use. To do that: Select the Use field options check box and then in the Key in update column. You do not have the possibility to rollback the operation. Drop a table if exists and create: The table is removed if it already exists and created again. Insert if not exist : Add new entries to the table if they do not exist. 435 Creative Commons License Talend Open Studio Components . Create a table if not exists: The table is created if it does not exist. you can perform: Insert: Add new entries to the table. Name of the table to be written. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). job stops. Schema and Edit Schema A schema is a row description. Note that only one table can be written at a time On the table defined. Clear a table: The table content is deleted.Databases components MSSqlOutput Username and Password Table Action on table DB user authentication data. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based.e. i.

This field is compulsory for DB data handling. nor update or delete actions. Use field options Enable debug mode Support null in “SQL WHERE” statement Select this check box to customize a request. you can retrieve the rows on error via a Row > Rejects link. Die on error This check box is selected by default. especially when there is double action on data. This option ensures transaction quality (but not rollback) and.Databases components MSSqlOutput Built-in: The schema is created and stored locally for this component only. hence can be reused. This option is not offered if you create (with or without drop) the DB table. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. If needed. Replace or After following the action to be performed on the reference column. Position: Select Before. Advanced settings Additional JDBC parameters Encoding Type Commit every Additional Columns tStatCatcher Statistics Select this check box to collect log data at the component level. This option allows you to call SQL functions to perform actions on columns. Clear the check box to skip the row on error and complete the process for error-free rows. Select this check box if you want to deal with the Null values contained in a DB table. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select this check box to display each step during processing entries in a database. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. Select the encoding type from the list or select Custom and define it manually. which are not insert. above all. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Specify additional connection properties for the DB connection you are creating. 436 Talend Open Studio Components Creative Commons License . Enter the number of rows to be completed before committing batches of rows together into the DB. This option is not available if you have selected the Use an existing connection check box in the Basic settings. better performance at execution. Make sure the Nullable check box is selected for the corresponding columns in the schema. or action that require particular preprocessing.

see Scenario 3: Retrieve data in error with a Reject link on page 483 Related scenarios For tMSSqlOutput related topics. It also allows you to create a reject flow using a Row > Rejects link to filter data in error.Databases components MSSqlOutput Use Batch Size Usage When selected. It allows you to carry out actions on a table or on the data of a table in a MSSql database. This component must be used as an output component. For an example of tMySqlOutput in use. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. enables you to define the number of lines in each processed batch. Creative Commons License Talend Open Studio Components 437 .

Built-in: The schema will be created and stored locally for this component only. Property type Either Built-in or Repository. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Select this check box to add the new rows at the end of the records. the fields to follow are pre-filled in using fetched data. Component family Databases/MSSql Function Purpose Basic settings Writes a file with columns based on the defined delimiter and the MSSql standards. Character. Prepares the file to be used as parameter in the INSERT query to feed the MSSql database. Related topic: Defining variables from the Component view of Talend Open Studio User Guide. i. Repository: The schema already exists and is stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. The schema is either built-in or remote in the Repository. Built-in: No property data stored centrally. When selected. These two steps compose the tMSSqlOutputBulkExec component. Repository: Select the Repository file where Properties are stored.Databases components tMSSqlOutputBulk tMSSqlOutputBulk tMSSqlOutputBulk properties tMSSqlOutputBulk and tMSSqlBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. Select this check to include the column header. detailed in a separate section. A schema is a row description. 438 Talend Open Studio Components Creative Commons License .e. Append Schema and Edit Schema Advanced settings Row separator Field separator Include header String (ex: “\n”on Unix) to distinguish rows. hence can be reused in various projects and job designs. string or regular expression to separate fields. File Name Name of the file to be processed. it defines the number of fields that will be processed and passed on to the next component. Related topic: Setting a built-in schema of Talend Open Studio User Guide..

tStaCatcher statistics Usage This component is to be used along with tMSSqlBulkExec component.Databases components tMSSqlOutputBulk Encoding Type Select the encoding from the list or select Custom and define it manually. Select this check box to collect log data at the component level. Related scenarios For uses cases in relation with tMSSqlOutputBulk. Used together they offer gains in performance while feeding a MSSql database. This field is compulsory for DB data handling. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 Creative Commons License Talend Open Studio Components 439 .

so if you need to use an existing connection from the other level. As a dedicated component. make sure that the available connection components are sharing the intended connection. When a Job contains the parent Job and the child Job. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about Dynamic settings. Component list presents only the connection components in the same Job level. Action Select the action to be carried out Bulk insert Bulk update Either Built-in or Repository. Host Port DB name Schema Username and Password Database server IP address Listening port number of DB server. it allows gains in performance during Insert operations to a MSSql database. make sure the connection name is unique and distinctive all over through the two Job levels.Databases components tMSSqlOutputBulkExec tMSSqlOutputBulkExec tMSSqlOutputBulkExec properties Component family Databases/MSSql Function Purpose Basic settings Executes the action on the data provided. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. In this case. The fields that come after are pre-filled in using the fetched data. Name of the database Name of the database schema DB user authentication data. Otherwise. Property type 440 Talend Open Studio Components Creative Commons License . see your studio user guide. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. For more information on how to share a DB connection across Job levels. Repository: Select the repository file where Properties are stored. Built-in: No property data stored centrally.

Create a table if not exists: The table is created if it does not exist. Select this check box to add the new rows at the end of the records Specify additional connection properties for the DB connection you are creating. Truncate table: The table content is deleted. Type in the number of the row where the action should start. OEM code pages used to map a specific set of characters to numerical code point values. String (ex: “\n”on Unix) to distinguish rows. You do not have the possibility to rollback the operation. Create a table: The table does not exist and gets created.e. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Built-in: You create and store the schema locally for this component only. The schema is either built-in or remotely stored in the Repository. i. it defines the number of fields to be processed and passed on to the next component. You can reuse it in various projects and job flowcharts. Select the type of data being handled. Select this check box to include the column header. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Action on table Schema and Edit Schema File Name Name of the file to be processed. string or regular expression to separate fields. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic:Defining variables from the Component view of Talend Open Studio User Guide.Databases components tMSSqlOutputBulkExec Table Name of the table to be written. Repository: You have already created the schema and stored it in the Repository. Related topic: Setting a built-in schema of Talend Open Studio User Guide. You have the possibility to rollback the operation. Character. On the table defined. A schema is a row description. Append Advanced settings Additional JDBC parameters Field separator Row separator First row Include header Code page Data file type Creative Commons License Talend Open Studio Components 441 .. you can perform one of the following operations: None: No operation is carried out. Clear a table: The table content is deleted. Drop and create a table: The table is removed and created again.

see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 442 Talend Open Studio Components Creative Commons License . Select this check box to collect log data at the component level.Databases components tMSSqlOutputBulkExec Encoding Type Select the encoding from the list or select Custom and define it manually. tStaCatcher statistics Usage Limitation This component is mainly used when no particular transformation is required on the data to be loaded onto the database. This field is compulsory for DB data handling. n/a Related scenarios For uses cases in relation with tMSSqlOutputBulkExec.

This component is to be used along with MSSql components. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component family Databases Function Purpose Basic settings Cancel the transaction commit in the connected DB. Clear this check box to continue to use the selected connection once the component has performed its task.Databases components tMSSqlRollback tMSSqlRollback tMSSqlRollback properties This component is closely related to tMSSqlCommit and tMSSqlConnection. especially with tMSSqlConnection and tMSSqlCommit components. n/a Related scenario For tMSSqlRollback related scenario. Component list Select the tMSSqlConnection component in the list if more than one connection are planned for the current job. It usually doesn’t make much sense to use these components independently in a transaction. see Scenario: Rollback from inserting data in mother/daughter tables on page 498 of the tMysqlRollback. Creative Commons License Talend Open Studio Components 443 . Avoids to commit part of a transaction involuntarily.

Built-in: No property data stored centrally. tMSSqlRow acts on the actual DB structure or on the data (although without handling data). you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Name of the database Name of the schema DB user authentication data. Component list presents only the connection components in the same Job level. The fields that come after are pre-filled in using the fetched data. Otherwise. For more information about Dynamic settings. Purpose Basic settings 444 Talend Open Studio Components Creative Commons License . so if you need to use an existing connection from the other level. It executes the SQL query stated onto the specified database. The SQLBuilder tool helps you write easily your SQL statements. make sure that the available connection components are sharing the intended connection. Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. Property type Either Built-in or Repository. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. In this case. Depending on the nature of the query and the database. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. For more information on how to share a DB connection across Job levels. make sure the connection name is unique and distinctive all over through the two Job levels. see your studio user guide.Databases components tMSSqlRow tMSSqlRow tMSSqlRow properties Component family Databases/DB2 Function tMSSqlRow is the specific component for this database query. Repository: Select the repository file where Properties are stored. When a Job contains the parent Job and the child Job.

Related topic: Setting a built-in schema of Talend Open Studio User Guide. Query Die on error Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Creative Commons License Talend Open Studio Components 445 . This check box is selected by default. it defines the number of fields to be processed and passed on to the next component. Repository: The schema already exists and is stored in the Repository. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Query type Either Built-in or Repository..Databases components tMSSqlRow Schema and Edit Schema A schema is a row description. Turn on identity insert Select this check box to use your own sequence for the identity value of the inserted records (instead of having the SQL Server pick the next sequential value). Specify additional connection properties for the DB connection you are creating. Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Related topic: Setting a Repository schema of Talend Open Studio User Guide. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Select this column from the use column list. i. Built-in: The schema is created and stored locally for this component only. Clear the check box to skip the row on error and complete the process for error-free rows. If needed.e. Select this check box to insert the result of the query into a COLUMN of the current flow. you can retrieve the rows on error via a Row > Rejects link. Table name Name of the table to be used. The schema is either built-in or remotely stored in the Repository. hence can be reused. The Query field gets accordingly filled in.

446 Talend Open Studio Components Creative Commons License . Parameter Type: Enter the parameter type. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Performance levels are increased Encoding Type Commit every Set manually the encoding type. Related scenarios For related topics.Databases components tMSSqlRow Use PreparedStatement Select this checkbox if you want to query the database using a PreparedStatement. Number of rows to be completed before committing batches of rows together into the DB. tStatCatcher Statistics Select this check box to collect log data at the component level. This option is very useful if you need to execute the same query several times. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. Parameter Index: Enter the parameter position in the SQL instruction. In the Set PreparedStatement Parameter table. Parameter Value: Enter the parameter value. This field is compulsory for DB data handling. This option ensures transaction quality (but not rollback) and above all better performance on executions.

see tMSSqlSCD on page 17. Creative Commons License Talend Open Studio Components 447 .Databases components tMSSqlSCD tMSSqlSCD tMSSqlSCD belongs to two component families: Business Intelligence and Databases. For more information on it.

make sure the connection name is unique and distinctive all over through the two Job levels.Databases components tMSSqlSP tMSSqlSP tMSSqlSP Properties Component family Databases/MSSql Function Purpose Basic settings tMSSqlSP calls the database stored procedure. DB user authentication data. Repository: Select the repository file where Properties are stored. so if you need to use an existing connection from the other level. it defines the number of fields to be processed and passed on to the next component. In this case. When a Job contains the parent Job and the child Job. A schema is a row description. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Built-in: No property data stored centrally.e. Component list presents only the connection components in the same Job level. Host Port Database Schema Username and Password Schema and Edit Schema Database server IP address Listening port number of DB server. i. Name of the database. In SP principle. For more information about Dynamic settings. The schema is either built-in or remotely stored in the Repository. 448 Talend Open Studio Components Creative Commons License . see your studio user guide. Property type Either Built-in or Repository.. make sure that the available connection components are sharing the intended connection. tMSSqlSP offers a convenient way to centralize multiple or complex queries in a database and call them easily. the schema is an input parameter. Use an existing connection Select this check box and click the relevant tMSSqlConnection component on the Component list to reuse the connection details you already defined. Otherwise. Name of the schema. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. The fields that come after are pre-filled in using the fetched data.

Select the encoding type from the list or select Custom and define it manually. SP Name Is Function / Return result in Parameters Type in the exact name of the Stored Procedure Select this check box. Click the Plus button and select the various Schema Columns that will be required by the procedures. Related topic: Setting a Repository schema of Talend Open Studio User Guide. the value to be returned is based on.Databases components tMSSqlSP Built-in: The schema is created and stored locally for this component only. likely after modification through the procedure (function). This field is compulsory for DB data handling Advanced settings Additional JDBC parameters Encoding Type tStatCatcher Statistics Select this check box to collect log data at the component level. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Creative Commons License Talend Open Studio Components 449 . see: • tMysqlSP Scenario: Finding a State Label using a stored procedure on page 512. Related scenario For related scenarios. RECORDSET: Input parameters is to be returned as a set of values. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameters is to be returned as value. Repository: The schema already exists and is stored in the Repository. Usage Limitation This component is used as intermediary component. Specify additional connection properties for the DB connection you are creating. hence can be reused. Related topic: Setting a built-in schema of Talend Open Studio User Guide. It can be used as start component but only input parameters are thus allowed. if only a value is to be returned. The Stored Procedures syntax should match the Database syntax. rather than single value. Select on the list the schema column. Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. • tOracleSP Scenario: Checking number format using a stored procedure on page 564 Check as well the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. Note that the SP schema can hold more columns than there are paramaters used in the procedure.

Lists the names of a given set of MSSql tables using a select statement based on a Where clause. see Scenario: Iterating on a DB table and listing its column names on page 455. especially with tMSSqlConnection. Component list Select the tMSSqlConnection component in the list if more than one connection are planned for the current job. This component is to be used along with MSSql components. Where clause for table Enter the Where clause to identify the tables to iterate name selection on.Databases components tMSSqlTableList tMSSqlTableList tMSSqlTableList Properties Component family Databases/MS SQL Function Purpose Basic settings Iterates on a set of table names through a defined MS SQL connection. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. 450 Talend Open Studio Components Creative Commons License . n/a Related scenario For tMSSqlTableList related scenario.

the fields to follow are pre-filled in using fetched data. Otherwise. detailed in a separate section. Built-in: No property data stored centrally. When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. make sure that the available connection components are sharing the intended connection. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading in the database. These two steps compose the tMysqlOutputBulkExec component. Component list presents only the connection components in the same Job level. Creative Commons License Talend Open Studio Components 451 . see your studio user guide. Select this check box when using a configured tMysqlConnection component. so if you need to use an existing connection from the other level. tMysqlBulkExec offers gains in performance while carrying out the Insert operations to a Mysql database Property type Either Built-in or Repository. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. make sure the connection name is unique and distinctive all over through the two Job levels. In this case. For more information about Dynamic settings. As a dedicated component. Name of the database DB user authentication data. When selected. Component family Databases/Mysql Function Purpose Basic settings Executes the Insert action on the data provided. Host Port Database Username and Password Database server IP address Listening port number of DB server. Repository: Select the Repository file where Properties are stored. DB Version Use an existing connection Select the version of My SQL that you are using. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.Databases components tMysqlBulkExec tMysqlBulkExec tMysqlBulkExec properties tMysqlOutputBulk and tMysqlBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated.

Clear table: The table content is deleted.. Character used to enclose text. Character or sequence of characters used to separate lines. Lines terminated by Fields terminated by Enclosed by Action on data Records contain NULL value 452 Talend Open Studio Components Creative Commons License . Truncate table: The table content is deleted. A schema is a row description. Related topic: Setting a Repository schema of Talend Open Studio User Guide. it defines the number of fields to be processed and passed on to the next component. Built-in: The schema is created and stored locally for this component only. Update records in table: Make changes to existing records. you can perform one of the following operations: None: No operation is carried out. If you do not check this box. The schema is either built-in or remotely stored in the Repository. the null values from the input data flow will be considered as empty fields in the output data flow. Drop and create table: The table is removed and created again. You do not have the possibility to rollback the operation. Create table if not exists: The table is created if it does not exist. i. Name of the table to be written. Table Local file Name Schema and Edit Schema Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. you can perform: Insert records in table: Add new records to the table. Ignore records in table: Ignore the existing records. hence can be reused. Repository: The schema already exists and is stored in the Repository. On the data of the table defined. Name of the file to be processed. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Character. Replace records in table: Replace existing records with new ones. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. You have the possibility to rollback the operation. Check this box if you want to retrieve the null values from the input data flow. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. or insert the new ones.Databases components tMysqlBulkExec Action on table On the table defined. Related topic: Setting a built-in schema of Talend Open Studio User Guide.e. string or regular expression to separate fields. Create table: The table does not exist and gets created.

Databases components tMysqlBulkExec Encoding Type Select the encoding from the list or select Custom and define it manually. Used together. they can offer gains in performance while feeding a Mysql database. n/a Limitation Related scenarios For uses cases in relation with tMysqlBulkExec. tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component is to be used along with tMysqlOutputBulk component. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538 Creative Commons License Talend Open Studio Components 453 . This field is compulsory for DB data handling.

This component is to be used along with Mysql components. Close a transaction. 454 Talend Open Studio Components Creative Commons License .Databases components tMysqlClose tMysqlClose tMysqlClose properties Component family Databases/Mysql Function Purpose Basic settings tMysqlClose closes the transaction committed in the connected DB. n/a Related scenario No scenario is available for this component yet. Component list Select the tMysqlConnection component in the list if more than one connection are planned for the current Job. especially with tMysqlConnection and tMysqlCommit. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.

Enter the name of the table. n/a Scenario: Iterating on a DB table and listing its column names The following Java scenario creates a five-component job that iterates on a given table name from a Mysql database using a Where clause and lists all column names present in the table. tMysqlTableList. Creative Commons License Talend Open Studio Components 455 . • Connect tFixedFlowInput to tLogRow using a Row Main link. especially with tMysqlConnection. Table name Usage Limitation This component is to be used along with Mysql components.Databases components tMysqlColumnList tMysqlColumnList tMysqlColumnList Properties Component family Databases/MySQL Function Purpose Basic settings Iterates on all columns of a given table through a defined Mysql connection. and tFixedFlowInput using Iterate links. tMysqlColumnList. Lists all column names of a given Mysql table. • Connect tMysqlTableList. • Connect tMysqlConnection to tMysqlTableList using an OnSubjobOk link. tMysqlColumnList. and tLogRow. • Drop the following components from the Palette onto the design workspace: tMysqlConnection. tFixedFlowInput. Component list Select the tMysqlConnection component in the list if more than one connection are planned for the current job.

In this example. In this scenario. For more information about Metadata.Databases components tMysqlColumnList • In the design workspace. • Enter a Where clause using the right syntax in the corresponding field to iterate on the table name(s) you want to list on the console. the table we want to iterate on is called customer. select tMysqlColumnList and click the Component tab to define its basic settings. 456 Talend Open Studio Components Creative Commons License . select tMysqlConnection and click the Component tab to define its basic settings. • In the design workspace. we want to connect to a Mysql database called customers. set the database connection details manually or select them from the context variable list. • In the design workspace. through a Ctrl+Space click in the corresponding field if you have stored them locally as Metadata DB connection entries. • In the Basic settings view. select the relevant Mysql connection component if more than one connection is used. see Defining Metadata items of Talend Open Studio User Guide. select tMysqlTableList and click the Component tab to define its basic settings. • On the Component list.

• In the design workspace. select tFixedFlowInput and click the Component tab to define its basic settings. The defined columns display in the Values panel of the Basic settings view. In this scenario.] button next to Edit Schema to define the data you want to use as input. • In the Table name field. select the relevant Mysql connection component if more than one connection is used.Databases components tMysqlColumnList • On the Component list. • Save your job and press F6 to execute it. In this scenario...get("tMysqlTableList_1_CURRENT_TABLE")) and ((String)globalMap. • Click OK to close the dialog box.get("tMysqlColumnList_1_COLUMN_NAME")) for the TableName and ColumnName respectively. select tLogRow. • In the design workspace. select ((String)globalMap. we want to list the columns present in the DB table called customer. • Click the Component tab and define the basic settings for tLogRow as needed. • Set the Schema to Built-In and click the three-dot [. • Click in the Value cell for each of the two defined columns and press Ctrl+Space to access the global variable list. Creative Commons License Talend Open Studio Components 457 . the first for the table name and the second for the column name. • From the global variable list. the schema is made of two columns. enter the name of the DB table you want to list its column names. and accept propagating the changes when prompted by the system.

458 Talend Open Studio Components Creative Commons License .Databases components tMysqlColumnList The name of the DB table is displayed on the console along with all its column names.

It usually doesn’t make much sense to use these components independently in a transaction. see Scenario: Inserting data in mother/daughter tables on page 460. Component list Select the tMysqlConnection component in the list if more than one connection are planned for the current job. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. n/a Related scenario This component is closely related to tMysqlConnection and tMysqlRollback. do not select the Close connection check box or your connection will be closed before the end of your first row commit. It usually doesn’t make much sense to use one of these without using a tMysqlConnection component to open a connection for the current transaction. This component is to be used along with Mysql components. especially with tMysqlConnection and tMysqlRollback components. This check box is selected by default. Clear this check box to continue to use the selected connection once the component has performed its task. It allows you to close the database connection once the commit is done. For tMysqlCommit related scenario. Component family Databases/MySQL Function Purpose Validates the data processed through the job into the connected DB Using a unique connection. In this case. Creative Commons License Talend Open Studio Components 459 . this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. If you want to use a Row > Main connection to link tAS400Commit to your Job. your data will be commited row by row.Databases components tMysqlCommit tMysqlCommit tMysqlCommit Properties This component is closely related to tMysqlConnection and tMysqlRollback.

Built-in: No property data stored centrally. 460 Talend Open Studio Components Creative Commons License . This field is compulsory for DB data handling. once the data has been validated. The fields that come after are pre-filled in using the fetched data. who want to carry out multiple table insertions using a parent table id to feed a child table. Component family Databases/MySQL Function Purpose Basic settings Opens a connection to the database for a current transaction. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. follow the steps described below to create the relevant tables using an engine such as innodb. As a prerequisite to this job. n/a Scenario: Inserting data in mother/daughter tables The following job is dedicated to advanced database users. DB user authentication data. Specify additional connection properties for the DB connection you are creating. Select the encoding from the list or select Custom and define it manually. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. This component allows you to commit all of the Job data to an output database in just a single transaction. Name of the database. Use or register a shared DB Connection Usage Limitation This component is to be used along with Mysql components.Databases components tMysqlConnection tMysqlConnection tMysqlConnection Properties This component is closely related to tMysqlCommit and tMysqlRollback. Select this check box to share your connection or fetch a connection shared by a parent or child Job. Host Port Database Additional JDBC parameters Username and Password Encoding Type Database server IP address Listening port number of DB server. It usually doesn’t make much sense to use one of these without using a tMysqlConnection component to open a connection for the current transaction. especially with tMysqlCommit and tMysqlRollback components. Shared DB Connection Name: set or type in the shared connection name.

the tFileList component using an OnComponentOk link to define the execution order. such as the directory.CURRENT_FILEPATH Creative Commons License Talend Open Studio Components 461 . name varchar(10). primary key(id)) engine=innodb. Set the File Name field to the global variable: tFileList_1. • Once connected to the relevant database. Use a Row link for each for these connections representing the main data flow. type in the following command to create the parent table: create table f1090_mum(id int not null auto_increment. years int) engine=innodb. tMysqlOutput (x2). set the connection details manually or fetch them from the Repository if you centrally stored them as a Metadata DB connection entry. tFileInputDelimited. • Drag and drop the following components from the Palette: tFileList. connect to your Mysql server. • On the tFileInputDelimited component’s Basic settings panel. • Connect the tFileList component to the input file component using an Iterate link as the name of the file to be processed will be dynamically filled in from the tFileList directory using a global variable. tMap. press Ctrl+Space bar to access the variable list.Databases components tMysqlConnection • In a command line editor. name where files will be fetched from. • In the tMysqlConnection Component view. Back into Talend Open Studio. the job requires seven components including tMysqlConnection and tMysqlCommit. For more information about Metadata. • Then create the second table: create table baby (id_baby int not null. • Add a tMysqlConnection component and connect it to the starter component of this job. see Defining Metadata items in Talend Open Studio User Guide. • Connect the tFileInputDelimited component to the tMap and dispatch the flow between the two output Mysql DB components. • Set the tFileList component properties. in this example.

one called mum for the parent table. • In each of the tMysqlOutput components’ Basic settings panel. • Then set the schema manually through the Edit schema feature or select the schema from the Repository. make sure the data type is correctly set. the second called baby. • Then connect the output row link to distribute correctly the flow to the relevant DB output component. 462 Talend Open Studio Components Creative Commons License . In Java version. for the child table. ignore the field as this command will get overridden by the tMysqlCommit. add two output tables. defining the row and field separators according to your file structure. and drop it to the mum table.Databases components tMysqlConnection • Set the rest of the fields as usual. • Drag the Years column from the Input area and drop it to the baby table. In Java version. in accordance with the nature of the data processed. select the Use an existing connection check box to retrieve the tMysqlConnection details. • Change the encoding if different from the default one. • Make sure the mum table is on the top of the baby table as the order is determining for the flow sequence hence the DB insert to perform correctly. • In the tMap Output area. • Notice (in Perl version) that the Commit every field doesn’t show anymore as you are supposed to use the tMysqlCommit instead to manage the global transaction commit. • Drag the Name column from the Input area.

set the id_baby column so that it reuses the id from the parent table.Databases components tMysqlConnection • Set the Table name making sure it corresponds to the correct table. • There is no action on the table as they are already created. • Select Insert as Action on data for both output components. • In the Additional columns area of the DB output component corresponding to the child table (f1090_baby). • Click on Sync columns to retrieve the schema set in the tMap. select in the list the connection to be used. • Add the tMysqlCommit component to the design workspace and connect it from the tFileList component using a OnComponentOk connection in order for the job to terminate with the transaction commit. • In the SQL expression field type in: '(Select Last_Insert_id())' • The position is Before and the Reference column is years. in this example either f1090_mum or f1090_baby. • Change the encoding type if need be. Creative Commons License Talend Open Studio Components 463 . • On the tMysqlCommit Component view. • Save your job and press F6 to execute it.

464 Talend Open Studio Components Creative Commons License .Databases components tMysqlConnection The parent table id has been reused to feed the id_baby column.

see Setting up a DB connection of Talend Open Studio User Guide. For more information about Dynamic settings. Otherwise. For more information about setting up and storing database connection parameters. In this case. Repository: Select the repository file where Properties are stored. Name of the database DB user authentication data. Use an existing connection Select this check box when using a configured tMysqlConnection component. Property type Either Built-in or Repository Built-in: No property data stored centrally. Component list presents only the connection components in the same Job level. Then it passes on the field list to the next component via a Main row link.Databases components tMysqlInput tMysqlInput tMysqlInput properties Component family Databases/MySQL Function Purpose tMysqlInput reads a database and extracts fields based on a query. Host Port Database Username and Password Database server IP address Listening port number of DB server. make sure that the available connection components are sharing the intended connection. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information on how to share a DB connection across Job levels. tMysqlInput executes a DB query with a strictly defined order which must correspond to the schema definition. The fields that come after are pre-filled in using the fetched data. Basic settings Creative Commons License Talend Open Studio Components 465 . Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. make sure the connection name is unique and distinctive all over through the two Job levels. so if you need to use an existing connection from the other level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job. see your studio user guide.

Databases components tMysqlInput Schema and Edit Schema A schema is a row description.e. Usage This component covers all possibilities of SQL queries onto a Mysql database. Built-in: The schema is created and stored locally for this component only. When you need to handle data of the time-stamp type 0000-00-00 00:00:00 using this component. Remove leading and trailing whitespace from defined columns. When selected. Select this check box to remove leading and trailing whitespace from all the String/Char columns. The schema is either built-in or remotely stored in the Repository. Encoding Type Enable stream Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. it defines the number of fields to be processed and passed on to the next component.. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. set the parameter as: noDatetimeStringSync=true&zeroDateTimeBehavior=convertToNull. Related scenarios Related topic in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. hence can be reused. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. 466 Talend Open Studio Components Creative Commons License . Repository: The schema already exists and is stored in the Repository. Table Name Name of the table to be read. helps to decide the row set to work with at a time and thus optimize performance. This field is compulsory for DB data handling. Select the encoding type from the list or select Custom and define it manually. Related topic: Setting a Repository schema of Talend Open Studio User Guide. i. This option is not available if you have selected the Use an existing connection check box in the Basic settings.

tFileInputDelimited. You can reuse it in various projects and job flow charts. tMySqlOutput. Related topic: Setting a built-in schema of Talend Open Studio User Guide. • Connect tMySqlConnection to tFileInputDelimited using an OnSubjobOk link. Extend Insert allows you to make a batch insertion. verify that the Extend Insert check box in the Advanced Settings tab is not selected. it defines the number of fields to be processed and passed on to the next component.. however. tMysqlLastInsertId. and finally fetches the last inserted ID on the existing connection. If you use this component with tMySqlOutput. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Limitation n/a Scenario: Get the ID for the last inserted record The following Java scenario creates a job that opens a connection to Mysql database. Component list Select the relevant tMysqlConnection component in the list if more than one connection is planned for the current job. writes the defined data into the database. tMysqlLastInsertId obtains the primary key value of the record that was last inserted in a Mysql table by a user.e. only the ID of the last line in the last batch will be returned. Repository: You have already created the schema and stored it in the Repository. Built-in: You create and store the schema locally for this component only.Databases components tMysqlLastInsertId tMysqlLastInsertId tMysqlLastInsertId properties Component family Databases Function Purpose Basic settings tMysqlLastInsertId fetches the last inserted ID from a selected MySQL Connection. Usage This component is to be used as an intermediary component. • Drop the following components from the Palette onto the design workspace: tMySqlConnection. tMySqlCommit. if the check box is selected. Creative Commons License Talend Open Studio Components 467 . and tLogRow. • Connect tFileInputDelimited to tMySqlCommit using an OnSubjobOk link. Schema and Edit Schema A schema is a row description. i. • Connect tFileInputdelimited to the three other components using Row Main links. The schema is either built-in or remotely stored in the Repository.

select the relevant tMysqlConnection if more than one connection is used. • Click the Component tab to define the basic settings for tMysqlConnection. select tFileInputDelimited. • In the design workspace. through a Ctrl+Space click in the corresponding field if you stored them locally as Metadata DB connection entries. select tMysqlConnection.Databases components tMysqlLastInsertId • In the design workspace. 468 Talend Open Studio Components Creative Commons License . • In the Basic settings view. • Click the Component tab to define the basic settings of tFileInputDelimited. see Defining Metadata items of Talend Open Studio User Guide. • On the Component List. set the connection details manually or select them from the context variable list. • In the design workspace. select tMysqlCommit and click the Component tab to define its basic settings. For more information about Metadata.

Then define the Field separator used to delimit fields in a row. • Set Schema to Built in and click the three-dot button next to Edit Schema to define the data to pass on to the next component.Databases components tMysqlLastInsertId • Set Property Type to Built-In. name and age. • Set the header. The file used in this example is Customers. In this scenario. • Click the Component tab to define the basic settings of tMySqlOuptput. the footer and the number of processed rows as necessary. Creative Commons License Talend Open Studio Components 469 . The first holds three employees’ names and the second holds the corresponding age for each. the schema consists of two columns. • Define the Row separator that allow to identify the end of a row. In this scenario. select tMySqlOutput. Related topics: Setting a built-in schema and Setting a Repository schema of Talend Open Studio User Guide. • Fill in a path to the processed file in the File Name field. we have one header. • In the design workspace.

• Set Schema to Built-In and click Sync columns to synchronize columns with the previous component. select tMySqlLastInsertId. if more than one connection is used. In this example. in this example: employee. • On the Component List. In this example. enter the name of the table where to write the employees’ list. • Select relevant actions on the Action on table and Action on data lists. • Click the Component tab to define the basic settings of tMySqlLastInserId. • In the design workspace.Databases components tMysqlLastInsertId • Select the Use an existing connection check box. • In the Table field. no action is carried out on table. 470 Talend Open Studio Components Creative Commons License . select the relevant tMysqlConnection. and the action carried out on data is Insert. the schema to be inserted into the MySql database table consists of the two columns name and age.

• Save your job and press F6 to execute it. you can see the read-only column last_insert_id that will fetch the last inserted ID on the existing connection. Creative Commons License Talend Open Studio Components 471 . see tLogRow on page 1023. In the output schema of tMySqlLastInsertId. select tLogRow and click the Component tab to define its basic settings. • In the design workspace.Databases components tMysqlLastInsertId • Set Schema to Built-In and click Sync columns to synchronize columns with the previous component. tMysqlLastInsertId fetched the last inserted ID for each line on the existing connection. For more information.

. Repository: Select the repository file where Properties are stored. see your studio user guide. Basic settings 472 Talend Open Studio Components Creative Commons License . For more information about setting up and storing database connection parameters. Name of the database Select the MySQL version you are using. Otherwise. make sure the connection name is unique and distinctive all over through the two Job levels. so if you need to use an existing connection from the other level. tMysqlOutput executes the action defined on the table and/or on the data contained in the table. based on the flow incoming from the preceding component in the job. see Setting up a DB connection of Talend Open Studio User Guide. Host Port Database Database server IP address Listening port number of DB server. Built-in: No property data stored centrally. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. In this case. When a Job contains the parent Job and the child Job. Property type Either Built-in or Repository.Databases components tMysqlOutput tMysqlOutput tMysqlOutput properties Component family Databases/MySQL Function Purpose tMysqlOutput writes. makes changes or suppresses entries in a database. Use an existing connection Select this check box when using a configured tMysqlConnection component. updates. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about Dynamic settings. The fields that come after are pre-filled in using the fetched data. DB Version Java only. For more information on how to share a DB connection across Job levels. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. make sure that the available connection components are sharing the intended connection. Component list presents only the connection components in the same Job level.

Clear a table: The table content is deleted. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). You must specify at least one column as a primary key on which the Update and Delete operations are based.Databases components tMysqlOutput Username and Password Table Action on table DB user authentication data. Create a table if not exists: The table is created if it does not exist. Drop a table if exists and create: The table is removed if it already exists and created again. Do the same in the Key in delete column for the deletion operation. Insert or update on duplicate key or unique index: Add entries if the inserted value does not exist or update entries if the inserted value already exists and there is a risk of violating a unique index or primary key. If duplicates are found. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Name of the table to be written. Insert Ignore: Add only new rows to prevent duplicate key errors. you can perform: Insert: Add new entries to the table. click the Advanced settings view where you can simultaneously define primary keys for the update and delete operations. On the data of the table defined. Update or insert: Update existing entries or creates them if they do not exist. Delete: Remove entries corresponding to the input flow. Note that only one table can be written at a time On the table defined. select the check boxes next to the column name on which you want to base the update operation. Truncate table: The table content is quickly deleted. you can perform one of the following operations: None: No operation is carried out. Drop and create a table: The table is removed and created again. However. To do that: Select the Use field options check box and then in the Key in update column. you will not be able to rollback the operation. Action on data Creative Commons License Talend Open Studio Components 473 . For an advanced use. the job stops. Create a table: The table does not exist and gets created.

This field is compulsory for DB data handling. you can retrieve the rows in error via a Row > Rejects link. Related topic: Setting a Repository schema of Talend Open Studio User Guide. hence can be reused. If needed. Select this check box to carry out a bulk insert of a defined set of lines instead of inserting lines one by one. i. This check box is selected by default. Number of rows to be included in the batch before it is committed to the DB. Number of rows per insert:: enter the number of rows to be inserted per operation.. however. a higher performance level. You should therefore clear the checkbox if you are using a Row > Rejects link with this component. Advanced settings Additional JDBC parameters Java only. The gain in system performance is considerable. Repository: The schema already exists and is stored in the Repository. Note that the higher the value specidied. it defines the number of fields to be processed and passed on to the next component. Extend Insert Encoding Type Select the encoding type from the list or select Custom and define it manually. above all. This option is not compatible with the Reject link.e. Built-in: The schema is created and stored locally for this component only.Databases components tMysqlOutput Schema and Edit Schema A schema is a row description. if the check box is selected. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Clear the check box to skip the row in error and complete the process for error-free rows. This option ensures transaction quality (but not rollback) and. only the ID of the last line of the last batch will be returned. ensure that the Extend Insert check box in Advanced Settings is not selected. Extend Insert allows for batch loading. Specify additional connection properties for the DB connection you are creating. The schema is either built-in or remotely stored in the Repository.. Commit every 474 Talend Open Studio Components Creative Commons License . Die on error Java only. the lower performance levels shall be due to the increase in memory demands. Related topic: Setting a built-in schema of Talend Open Studio User Guide. If you are using this component with tMysqlLastInsertID.

Use Hint Options Java only.Databases components tMysqlOutput Additional Columns This option is not available if you have just created the DB table (even if you delete it beforehand).POSITION: specify where you put the hint in a SQL statement. This component must be used as an output component. update or delete actions. It allows you to carry out actions on a table or on the data of a table in a MySQL database.. Use field options Select this check box to customize a request. using the syntax /*+ */. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. For an example of tMySqlOutput in use. Select this check box to activate the hint configuration area which helps you optimize a query’s execution.HINT: specify the hint you need. This option allows you to call SQL functions to perform actions on columns. see Scenario 3: Retrieve data in error with a Reject link on page 483 Creative Commons License Talend Open Studio Components 475 .. Use duplicate key update mode insert tStatCatcher Statistics Select this check box to collect log data at the component level. particularly if multiple actions are being carried out on the data. .. Reference column: Type in a reference column that tMySqlOutput can use to locate or replace the new column. Java only. Enable debug mode Java only. To use this option you must first of all select the Insert mode in the Action on data list found in the Basic Settings view and select the Extend Insert mode in the Advanced settings view. Replace or After. Name: Type in the name of the schema column to be altered or inserted SQL expression: Type in the SQL statement to be executed in order to alter or insert the data in the corrsponding column. Position: Select Before. It also allows you to create a reject flow using a Row > Rejects link to filter data in error.SQL STMT: select the SQL statement you need to use. depending on the action to be performed on the reference column. provided that these are not insert. or the column to be modified. parameters are: . or actions that require pre-processing. In this area. . Select this check box to execute insert or update actions in the Extend Insert mode.. Select this check box to display each step involved in the process of writing data in the database.

• Set the Schema to Built-In. tMap and tMySQLOutput. and eventually altering the data to be inserted based on an SQL expression using the tMysqlOutput component. and tMysqlOutput using the Row Main link. • Click the Edit schema three-dot button to define the data to pass on to the tMap component. 476 Talend Open Studio Components Creative Commons License . • Click OK to close the dialog box. • Click the RowGenerator Editor three-dot button to open the editor and define the data to be generated. • Drop the following components from the Palette onto the design workspace: tRowGenerator. name and random_date. two columns in this scenario. duplicating a column to be altered using the tMap component. select tRowGenerator to display its Basic settings view. • In the design workspace.Databases components tMysqlOutput Scenario 1: Adding a new column and altering data in a DB table This Java scenario is a three-component job that aims at creating random data using a tRowGenerator. tMap. • Connect tRowGenerator.

The Map editor opens displaying the input metadata of the tRowGenerator component. • Double-click the tMap component to open the Map editor. • In the Schema editor panel of the Map editor. click the plus button of the output table to add two rows and define the first as random_date and the second as random_date1. Creative Commons License Talend Open Studio Components 477 .Databases components tMysqlOutput • Click in the corresponding Functions fields and select a function for each of the two columns. • In the Number of Rows for Rowgenerator field. enter 10 to generate ten first name rows and click Ok to close the editor. getFirstName for the first column and getrandomDate for the second column.

Databases components tMysqlOutput In this scenario. drag the random_date row from the input table to the random_date and random_date1 rows in the output table. • In the Map editor. 478 Talend Open Studio Components Creative Commons License . double-click the tMysqlOutput component to display its Basic settings view and set its parameters. we want to duplicate the random_date column and adapt the schema in order to alter the data in the output component. • In the design workspace. • Click OK to close the editor.

Databases components tMysqlOutput • Set Property Type to Repository and then click the three-dot button to open the [Repository content] dialog box and select the correct DB connection. • On the Action on table list. click Sync columns to synchronize with the columns coming from the tMap component. • Click the three-dot button next to the Table field and select the table to be altered. Dates in this scenario. • Click the Advanced settings tab to display the corresponding view and set the advanced parameters. select Insert on the Action on data list. select Built-in on the property type list and set the connection detail manually. select Drop table if exists and create. The connection details display automatically in the corresponding fields. If you have not stored the DB connection details in the Metadata entry in the Repository. Creative Commons License Talend Open Studio Components 479 . • If needed.

the data itself gets altered using an SQL expression that adds one month to the randomly picked-up date of the random_date_1 column.Databases components tMysqlOutput • In the Additional Columns area. • Drop tFileInputDelimited and tMySQLOutput from the Palette onto the design workspace. Also. -Select Replace on the Position list. set the alteration to be performed on columns. For this job we duplicated the random_date_1 column in the DB table before replacing one instance of it with the One_Month_Later column. ex: 2007-08-12 becomes 2007-09-12. • Double-click tFileInputDelimited to display its Basic settings view and define the component properties. • Save your job and press F6 to execute it. In this scenario. the One_month_later column replaces random_date_1. • Connect the two components together using a Row Main link. -Enter Random_date1 on the Reference column list. Scenario 2: Updating data in a database table This Java scenario describes a two-component Job that updates data in a MySQL table according to that in a delimited file. interval 1 month)” in this scenario. -Enter One_Month_Later in the Name cell. “adddate(Random_date. -In the SQL expression cell. The new One_month_later column replaces the random_date1 column in the DB table and adds one month to each of the randomly generated dates. Related topic: tDBOutput properties on page 256. 480 Talend Open Studio Components Creative Commons License . enter the relevant addition script to be performed. The aim of this workaround was to be able to view upfront the modification performed.

In this example. select Built-In to define manually the metadata of the delimited file. Otherwise. we use the customer_update file that holds four columns: id. the number of processed lines is limited to 2000. Creative Commons License Talend Open Studio Components 481 . CustomerAddress and idState. click the three-dot button and browse to the source delimited file that contains the modifications to propagate in the MySQL table. For more information about storing metadata.Databases components tMysqlOutput • From the Property Type list. • In the File Name field. Header is set to 1 since the first row holds the names of columns. Also. • Define the row and field separators used in the source file in the corresponding fields. select Repository if you have already stored the metadata of the delimited file in the Metadata node in the Repository tree view. see Setting up a File Delimited schema on page 166 of Talend Open Studio User Guide. • If needed. therefore it should be ignored. Footer and Limit. Some of the data in these four columns is different from that in the MySQL table. • Select Built in from the Schema list then click the three-dot button next to Edit Schema to open a dialog box where you can describe the data structure of the source delimited file that you want to pass to the component that follows. In this example. set Header. CustomerName.

see Setting up a DB connection on page 146 of Talend Open Studio User Guide. select the operation you want to perform.Databases components tMysqlOutput • Select the Key check box(es) next to the column name(s) you want to define as key column(s). • Save your Job and press F6 to execute it. select the operation you want to perform on the data. • From the Action on table list. click the three-dot button next to Edit schema to open a dialog box where you can check the retrieved schema. enter the name of the table to update. None in this example since the table already exists. For more information about storing metadata. • From the Action on data list. • Click Sync columns to retrieve the schema of the preceding component. • In the design workspace. If needed. select Repository if you have already stored the connection metadata in the Metadata node in the Repository tree view. Otherwise. double-click tMysqlOutput to open its Basic settings view where you can define its properties. the Job is automatically interrupted and an error message displays on the console. • From the Property Type list. 482 Talend Open Studio Components Creative Commons License . • In the Table field. It is necessary to define at least one column as a key column for the Job to be executed correctly. Update in this example. • Fill in the database connection information in the corresponding fields. select Built-In to define manually the connection information. Otherwise.

Creative Commons License Talend Open Studio Components 483 . In the [Components] dialog box. select tFileInputDelimited and click OK. customers. select the customer file metadata that you want to migrate and drop it onto the workspace. CustomerName. you can verify if the MySQL table. CustomerAddress and idState. has been modified according to the delimited file. the database table has always the four columns id.Databases components tMysqlOutput Using you DB browser. In the above example. but certain fields have been modified according to the data in the delimited file used. The component properties will be filled in automatically. Scenario 3: Retrieve data in error with a Reject link This scenario describes a four-component Job that carries out migration from a customer file to a MySQL database table and redirects data in error towards a CSV file using a Reject link. • In the Repository.

• From the Palette. expand the Metadata node. Name this second link out. and the tMap and Localhost with a Row Main link. • Link the Localhost to the tFileOutputDelimited using a Row > Reject link. 484 Talend Open Studio Components Creative Commons License . • Click the [. You can also select the Built-in mode and fill in the fields manually. see Setting a built-in schema and Setting a Repository schema in the Talend Open Studio User Guide. • In the Property Type list. type in between inverted commas the row and field separator used in the file.. • In the Repository. Drop a tFileInputDelimited component from the family File > Input.. select tMysqlOutput and click OK.. For more information. • If you have not stored the database connection details under the Db Connections node in the Repository. type in the number of headers and footers to ignore. • Link the customers component to the tMap component.] button next to the File Name field. and drop it onto the workspace. • From the Palette. Drop it onto the workspace. in the Palette. • In the Row and Field Separator fields.. In the [Components] dialog box. Footer and Limit fields. The database connection properties will be automatically filled in. and fill in the path and the name of the file you want to use. drop a tMap from the Processing family onto the workspace. select Repository and click the [. • In the Header. and fill in its properties manually in the Component tab.] button in order to select the metadata containing the connection to your file. followed by the Db Connections node and select the connection required to migrate your data to the appropriate database. • Double-click the customers component to display the Component view. drop a tMysqlOutput from the Databases family in the Palette and fill in its properties manually in the Component tab. select a tFileOutputDelimited from the File > Output family.Databases components tMysqlOutput • If you have not stored the information about your customer file under the Metadata node in the Repository. and the number of rows to which processing should be limited.

CustomerAddress. You can also click the [..Databases components tMysqlOutput • In the Schema list.. on the right. idSate.] button in order to select the schema of your file. RegTime and RegisterTime columns on the table on the left and drop them on the out table. select Repository and click the [..] button next to the Edit schema field. Creative Commons License Talend Open Studio Components 485 . id2. and set the schema manually. if it is stored under the Metadata node in the Repository. CustomerName.. The schema is as follows: • Double-click the tMap component to open its editor. • Select the id.

. we call it customers_data. In this scenario. You can also select the Built-in mode and set the fields manually. • Click the Sync columns button to retrieve the schema from the previous component. in the right table. 486 Talend Open Studio Components Creative Commons License . type in the name of the table to be created. • Click OK. The connection details will be automatically filled in. • In the Property Type list. • In the Action on data list. retrieved with the Reject link. change the length of the CustomerName column to 28 to create an error.] button to select the connection to the database metadata. • In the workspace. Thus.Databases components tMysqlOutput • In the Schema editor area. any data for which the length is greater than 28 will create errors.. at the bottom of the tMap editor. select the Create table option. select Repository and click the [. double-click the output Localhost component to display its Component view. • In the Table field.

. • Click the [. • Save your Job and press F6 to execute it. Creative Commons License Talend Open Studio Components 487 . • Click the Advanced settings tab of the Component view to set the advanced parameters of the component. • Double-click the tFileOutputDelimited component to set its properties in the Component view.Databases components tMysqlOutput • Make sure the Die on error check box isn’t selected.. so that the Job can be executed despite the error you just created. because this option is not compatible with the Reject link. • Click the Sync columns button to retrieve the schema of the previous component. • Deselect the Extend Insert check box which enables you to insert rows in batch.] button next to the File Name field to fill in the path and name of the output file.

as well as the error type met.Databases components tMysqlOutput The data in error are sent to the delimited file. Here. 488 Talend Open Studio Components Creative Commons License . we have: Data truncation.

String (ex: “\n”on Unix) to distinguish rows. it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository. Repository: The schema already exists and is stored in the Repository.. Component family Databases/MySQL Function Purpose Basic settings Writes a file with columns based on the defined delimiter and the MySql standards Prepares the file to be used as parameter in the INSERT query to feed the MySQL database. File Name Name of the file to be processed. Built-in: The schema will be created and stored locally for this component only. Property type Either Built-in or Repository. string or regular expression to separate fields. Field separator Row separator Append Include header Schema and Edit Schema Creative Commons License Talend Open Studio Components 489 . detailed in a separate section. Built-in: No property data stored centrally. i. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. A schema is a row description. Repository: Select the Repository file where Properties are stored. The following fields are pre-filled in using fetched data. Select this check box to add the new rows at the end of the file Select this check box to include the column header to the file.Databases components tMysqlOutputBulk tMysqlOutputBulk tMysqlOutputBulk properties tMysqlOutputBulk and tMysqlBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. hence can be reused in various projects and job designs.e. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. These two steps compose the tMysqlOutputBulkExec component. Related topic:Defining variables from the Component view of Talend Open Studio User Guide Character.

Used together they offer gains in performance while feeding a MySQL database.Databases components tMysqlOutputBulk Encoding Type Select the encoding from the list or select Custom and define it manually. • Connect the main flow using row main links. of type OnComponentOk. • Drag and drop a tRowGenerator. • Define the schema of the rows to be generated and the nature of data to generate. 490 Talend Open Studio Components Creative Commons License . City which all are defined as string data but the ID that is of integer type. First Name. The first step includes a tranformation phase of the data included in the file. Usage This component is to be used along with tMySQlBulkExec component. • A tRowGenerator is used to generate random data. In this example. Double-click on the tRowGenerator component to launch the editor. first step is to create the file. including transformed data. • And connect the start component (tRowgenerator in this example) to the tMysqlBulkExec using a trigger connection. Last Name. a tMysqlOutputBulk as well as a tMysqlBulkExec component. the clients file to be produced will contain the following columns: ID. Two steps are required in this job. Scenario: Inserting transformed data in MySQL database This scenario describes a four-component job which aims at fueling a database with data contained in a file. Address. that will then be used in the second step. This field is compulsory for DB data handling. a tMap.

To hide them away. • Then select the tMap component to set the transformation. click on Columns list button next to the toolbar. • Drag and drop all columns from the input table to the output table. • Apply the transformation on the LastName column by adding uc in front of it. • Use the plus button to add as many columns to your schema definition. • Click OK to validate the transformation. such as Precision or Parameters. • Click the Refresh button to preview the first generated row of your output. Creative Commons License Talend Open Studio Components 491 . and uncheck the relevant entries.Databases components tMysqlOutputBulk • Some schema information don’t necessarily need to be displayed. • Then double-click on the tMysqlOutputBulk component.

The clients database table is filled with data from the file including upper-case last name as transformed in the job. • Then double-click on the tMysqlBulkExec to set the INSERT query to be executed. We recommend you to store this type of information in the Repository. to retrieve relevant data. so that you can retrieve them at any time for any job. • Make sure the encoding corresponds to the data encoding. if you accepted it when prompted. 492 Talend Open Studio Components Creative Commons License .Databases components tMysqlOutputBulk • Define the name of the file to be produced in File Name field. • Click OK to validate the output. don’t include the header information as the table should already contain it. • Set the table to be filled in with the collected data. If the delimited file information is stored in the Repository. • The encoding is the default one for this use case. In this use case the file name is clients. • Define the database connection details. • The schema is propagated from the tMap component. • In this example. • Fill in the column delimiters in the Field terminated by area.txt. in the Table field. select it in Property type field. • Then press F6 to run the job.

Related topic: tMysqlOutputBulkExec properties on page 494 Creative Commons License Talend Open Studio Components 493 .Databases components tMysqlOutputBulk For simple Insert operations that don’t include any transformations. the use of tMysqlOutputBulkExec allows you to skip a step in the process and thus improves performance.

As a dedicated component. Create a table if doesn’t exist: The table is created if it does not already exist. On the table defined. A schema is a description of rows. DB Version Host Port Database Username and Password Select the version of MySQL that you are using. you can perform one of the following operations: None: No operation is carried out.Databases components tMysqlOutputBulkExec tMysqlOutputBulkExec tMysqlOutputBulkExec properties Component family Databases/MySQL Function Purpose Basic settings Executes the Insert action on the data provided. Clear a table: The table content is deleted. Create a table: The table does not exist and gets created. it improves performance during Insert operations to a MySQL database. Drop and create a table: The table is removed and created again. In Java. It defines the number of fields which are treated and passed on to the following component. Name of the database DB user authentication data. Database server IP address Listening port number of DB server. Property type Either Built-in or Repository. Action on table Table Local FileName Append Schema and Edit Schema 494 Talend Open Studio Components Creative Commons License . The fields that follow are filled automatically using the fetched data. use tCreateTable as substitute for this function. Note that only one table can be written at a time and that the table must already exist for the insert operation to succeed Name of the file to be processed. Related topic:Defining variables from the Component view of Talend Open Studio User Guide Select the check box for this option to append new rows to the end of the file. Name of the table to be written. in the Repository. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored. The schema is either local (Built-in) or remote.

Replace records in table: Replace existing records with new one. Customize the amount of memory used to temporarily store output data. Creative Commons License Talend Open Studio Components 495 . This option is not available if you have selected the Use an existing connection check box in the Basic settings. If you clear the check box. enter the number of rows after which the memory is to be freed again.Databases components tMysqlOutputBulkExec Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. This check box is selected by default. you can carry out the following opertaions: Insert records in table: Add new records to the table. string or regular expression to separate fields. This check box is selected by default. although no data is transformed. String (ex: “\n”on Unix) to distinguish rows. n/a Scenario: Inserting data in MySQL database This scenario describes a two-component job which carries out the same operation as the one described for tMysqlOutputBulk properties on page 489 and tMysqlBulkExec properties on page 451. In the Row number field. the NULL values will automatically be replaced with empty values. Usage Limitation This component is mainly used when no particular transformation is required on the data to be loaded onto the database. Ignore records in table: Ignore existing records or insert the new ones. Update records in table: Make changes to existing records. Row separator Field separator Escape char Text enclosure Create directory if does not exist Custom the flush buffer size Action on data Records contain NULL value Encoding Type tStatCatcher Statistics Select this check box to collect the log data at the component level. Character of the row to be escaped Character used to enclose the text. Select the encoding from the list or select Custom and define it manually. Character. It creates a directory to hold the output table if required. It allows you to take account of NULL value fields. On the data of the table defined. This field is compulsory for DB data handling.

The schema is made of four columns including: ID. First Name. • Click on the Advanced settings tab to define the component’s advanced parameters. In the component view. • Connect the components using a link such as Row > Main. In this example. the file is clients. if necessary. under the Metadata node.txt. concerning the conservation of connection details in the Repository. indicate the access path and the name of the file which contains the data to be added to the table. the name being clients in this example.Databases components tMysqlOutputBulkExec • Drop a tRowGenerator and a tMysqlOutputBulkExec component from the Palette to the design workspace. Address and City. enter the name of the table you want to populate. double-click the tMysqlOutputBulkExec to display the Component view and set the properties. see Setting a built-in schema and Setting a Repository schema in the Talend Open Studio User Guide. For further information. 496 Talend Open Studio Components Creative Commons License . select Repository in the Property Type field and then select the appropriate connection in the adjacent field. • Define the database connection details. • In the Action on table field. • In the Table field. select the None option as you want to insert the data into a table which already exists. Last Name. Consult the recommendations detailed in the Scenario: Inserting transformed data in MySQL database on page 490. • Set the tRowGenerator parameters the same way as in the Scenario: Inserting transformed data in MySQL database on page 490. The following fields will be filled in automatically. • In the Local filename field. • In the workspace.

• Press F6 to run the job. but the data might differ as these are regenerated randomly everytime the job is run. Creative Commons License Talend Open Studio Components 497 .Databases components tMysqlOutputBulkExec • In the Action on data list. select the Insert records in table to insert the new data in the table. The result should be pretty much the same as in Scenario: Inserting transformed data in MySQL database on page 490.

• Drag and drop a tMysqlRollback to the design workspace and connect it to the Start component.Databases components tMysqlRollback tMysqlRollback tMysqlRollback properties This component is closely related to tMysqlCommit and tMysqlConnection. 498 Talend Open Studio Components Creative Commons License . especially with tMysqlConnection and tMysqlCommit components. Avoids to commit part of a transaction involuntarily. Component family Databases Function Purpose Basic settings Cancel the transaction commit in the connected DB. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. n/a Scenario: Rollback from inserting data in mother/daughter tables Based on the tMysqlConnection Scenario: Inserting data in mother/daughter tables on page 460. This component is to be used along with Mysql components. It usually doesn’t make much sense to use these components independently in a transaction. insert a rollback function in order to prevent unwanted commit. Clear this check box to continue to use the selected connection once the component has performed its task. Component list Select the tMysqlConnection component in the list if more than one connection are planned for the current job.

This complementary element to the job ensures that the transaction won’t be partly committed.Databases components tMysqlRollback • Set the Rollback unique field on the relevant DB connection. Creative Commons License Talend Open Studio Components 499 .

Name of the database DB user authentication data. Purpose Basic settings 500 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository. Built-in: No property data stored centrally. Otherwise. Repository: Select the repository file where Properties are stored. Depending on the nature of the query and the database. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. The SQLBuilder tool helps you write easily your SQL statements. The fields that come after are pre-filled in using the fetched data. In this case.Databases components tMysqlRow tMysqlRow tMysqlRow properties Component family Databases/MySQL Function tMysqlRow is the specific component for this database query. tMysqlRow acts on the actual DB structure or on the data (although without handling data). make sure that the available connection components are sharing the intended connection. make sure the connection name is unique and distinctive all over through the two Job levels. For more information on how to share a DB connection across Job levels. so if you need to use an existing connection from the other level. The row suffix means the component implements a flow in the job design although it doesn’t provide output. For more information about Dynamic settings. Component list presents only the connection components in the same Job level. It executes the SQL query stated in the specified database. Host Port Database Username and Password Database server IP address Listening port number of DB server. Select this check box and click the relevant tMysqlConnection component on the Component list to reuse the connection details you already defined. When a Job contains the parent Job and the child Job. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. DB Version Use an existing connection Select the MySQL version that you are using. see your studio user guide.

it defines the number of fields to be processed and passed on to the next component. Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Performance levels are increased Query Die on error Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. The schema is either built-in or remotely stored in the Repository. Parameter Type: Enter the parameter type. This option is very useful if you need to execute the same query several times. Specify additional connection properties for the DB connection you are creating. Select this column from the use column list. Either Built-in or Repository.Databases components tMysqlRow Schema and Edit Schema A schema is a row description. 501 Creative Commons License Talend Open Studio Components . Related topic: Setting a built-in schema of Talend Open Studio User Guide. Built-in: The schema is created and stored locally for this component only. In the Set PreparedStatement Parameter table. Clear the check box to skip the row on error and complete the process for error-free rows. The Query field gets accordingly filled in. Parameter Index: Enter the parameter position in the SQL instruction. Select this checkbox if you want to query the database using a PreparedStatement. Table Name Query type Name of the table to be processed. Related topic: Setting a Repository schema of Talend Open Studio User Guide.e. This check box is selected by default. i. Repository: The schema already exists and is stored in the Repository. Select this check box to insert the result of the query in a COLUMN of the current flow. This field is compulsory for DB data handling. you can retrieve the rows on error via a Row > Rejects link. This option is not available if you have selected the Use an existing connection check box in the Basic settings.. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. hence can be reused. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Parameter Value: Enter the parameter value. If needed.

link the first tMysqlRow to tRowGenerator and tRowGenerator to the second tMysqlRow. • Propagate the properties and schema details onto the other components of the job. tRowGenerator. • Select and drop the following components onto the design workspace: tMysqlRow (x2). 502 Talend Open Studio Components Creative Commons License . • The query being stored in the Metadata area of the Repository. Scenario 1: Removing and regenerating a MySQL table index This scenario describes a four-component job that removes a table index. type in the following SQL statement to alter the database entries: drop index <index_name> on <table_name> • Select the second tMysqlRow component. • In Property type as well in Schema. • If you didn’t store your query in the Repository. • Connect tRowGenerator to tMysqlIntput. select the relevant DB entry in the list. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. check the DB properties and schema. applies a select insert action onto a table then regenerates the index. • Select the tMysqlRow to fill in the DB Basic settings.Databases components tMysqlRow Commit every Number of rows to be completed before committing batches of rows together into the DB. tStatCatcher Statistics Select this check box to collect log data at the component level. you can also select Repository in the Query type field and the relevant query entry. • The DB connection details and the table schema are accordingly filled in. and tMysqlOutput. This option ensures transaction quality (but not rollback) and above all better performance on executions. • Using a OnComponentOk connections.

• Slide the metadata onto the workspace and double-click tFileInputDelimited in the Components dialog box so that the tFileInputDelimited component is created with the parameters already set. • The schema should be automatically inherited from the data flow coming from the tLogRow. we are using the customers metadata. • Press F6 to run the job. we use a PreparedStatement object which means that the query is executed only once rather than against each row in turn. For further information concerning the creation of metadata in delimited files.Databases components tMysqlRow • Type in the SQL statement to recreate an index on the table using the following statement: create index <index_name> on <table_name> (<column_name>) The tRowGenerator component is used to generate automatically the columns to be added to the DB output table defined. • Select the tMysqlOutput component and fill in the DB connection properties either from the Repository or manually the DB connection details are specific for this use only. These sections are all in the Talend Open Studio Components User Guide. Here. For this scenario. In order to process a large volume of data quickly. we use a file and a database for which we have already stored the connection and properties in the Rerpository metadata. • No additional Columns is required for this job. see Setting up a DB connection and for further information as to the usage of metadata. Then each row is sentas a parameter. • In the Repository. • The Action on table is None and the Action on data is Insert. The table to be fed is named: comprehensive. you can notice that the index is dropped at the start of the job and recreated at the end of the insert action. Related topics: tDBSQLRow properties on page 261. expand the Metadata and File delimited nodes. • Select the metadata which corresponds to the client file you want to use in the Job. Scénario 2: Using PreparedStatement objects to query data This scenario describes a four component job which allows you to link a table column with a client file. while the file contains the customer information including the ID of the State in which they live. see Setting a Repository schema. If you manage to watch the action on DB data. using an SQL query. For further information concerning the creation of database connection metadata. We want to retrieve the name of the State for each client. Creative Commons License Talend Open Studio Components 503 . The MySQL table contains a list of all the American States along with the State ID. consult Setting up a File Delimited schema. Edit the schema to check its structure and check that it corresponds to the schema expected on the DB table specified.

Rename this column LabelStateRecordSet and select Object from the Type list. • Connect the four components using Row > Main type links. 504 Talend Open Studio Components Creative Commons License .. select the tMysqlRow.] next to the Edit schema field to add a column into which the name of the State will be inserted. Click OK to save your modifications.Databases components tMysqlRow • In the Schema list. Then click on [.. • Click on the [+] button to add a column to the schema. tParseRecordSet and tFileOutputDelimited components and drop them onto the workspace. • From the Palette. select Built-in so that you can modify the component’s schema.

• Click Advanced settings to set the components advanced properties. Host. or click directly on the Sync columns button to retrieve the schemma from the preceding component.. If you are using the Built-in mode. The DB Version. us_state: "SELECT LabelState FROM us_state WHERE idState=?". select Repository and click on the [. select Built-in to set the schema properties manually and add the LabelStateRecordSet column. Database.] button to select a database connection from the metadata in the Repository. “?”.Databases components tMysqlRow • Double click tMysqlRow to set its properties in the Basic settings tab of the Component view. complete these fields manually. Creative Commons License Talend Open Studio Components 505 . • In the Query field. enter the SQL query you want to use. The question mark. Here. Username and Password fields are completed automatically. we want to retrieve the names of the American States from the LabelState column of the MySQL table. represents the parameter to be set in the Advanced settings tab. Port.. • From the Schema list. • In the Property Type list.

• Double click tParseRecordSet to set its properties in the Basic settings tab of the Component view. enter “row1. select Int from the list. hence. • In the Parameter Index cell. • Select the Use PreparedStatement check box and define the parameter used in the query in the Set PreparedStatement Parameters table. • Click on the [+] button to add a parameter. enter the parameter value. the parameter is a whole number.idState”. • In the Parameter Type cell. enter the type of parameter. Here. Here. enter the parameter position in the SQL instruction. • In the Parameter Value cell.Databases components tMysqlRow • Select the Propagate QUERY’s recordset check box and select the LabelStateRecordSet column from the use column list to insert the query results in that column. 506 Talend Open Studio Components Creative Commons License . we want to retrieve the name of the State based on the State ID for every client in the input file. Enter “1” as we are only using one parameter in this example. Hence.

• Click Sync columns to retrieve the schema from the preceding component. The Attribute table is automatically completed with the schema columns. select the preceding components column for analysis. • Click on the Sync columns button to retrieve the schema from the preceding component. select LabelStateRecordSet. Creative Commons License Talend Open Studio Components 507 . enter the access path and name of the output file.Databases components tMysqlRow • From the Prev. • Save your Job and press F6 to run it. Comp. In this example. in the Value field which corresponds to the LabelStateRecordSet. • In the Attribute table. • In the File Name field. In this example. Column list. within double quotation marks. enter the name of the column containing the State names to be retrieved and matched with each client. • Double click tFileOutputDelimited to set its properties in the Basic settings tab of the Component view. enter “LabelState”.

508 Talend Open Studio Components Creative Commons License .Databases components tMysqlRow A column containing the name of the American State corrresponding to each client is added to the file.

see tMysqlSCD on page 19.Databases components tMysqlSCD tMysqlSCD tMysqlSCD belongs to two component families: Business Intelligence and Databases. Creative Commons License Talend Open Studio Components 509 . For more information on it.

see tMysqlSCDELT on page 31.Databases components tMysqlSCDELT tMysqlSCDELT tMysqlSCDELT belongs to two component families: Business Intelligence and Databases. 510 Talend Open Studio Components Creative Commons License . For more information on it.

Databases components tMysqlSP tMysqlSP tMysqlSP Properties Component family Databases/Mysql Function Purpose Basic settings tMysqlSP calls the database stored procedure. if a value only is to be returned. Related topic: Setting a built-in schema of Talend Open Studio User Guide. In SP principle. Schema and Edit Schema Creative Commons License Talend Open Studio Components 511 . i. Select on the list the schema column. Name of the database DB user authentication data. SP Name Is Function / Return result in Type in the exact name of the Stored Procedure Select this check box. Property type Either Built-in or Repository. Built-in: The schema is created and stored locally for this component only. tMysqlSP offers a convenient way to centralize multiple or complex queries in a database and call them easily. Host Port Database Username and Password Encoding Type Database server IP address Listening port number of DB server. Repository: The schema already exists and is stored in the Repository. Built-in: No property data stored centrally. The schema is either built-in or remotely stored in the Repository. hence can be reused. Select the encoding from the list or select Custom and define it manually.. This field is compulsory for DB data handling. it defines the number of fields to be processed and passed on to the next component.e. the value to be returned is based on. the schema is an input parameter. Related topic: Setting a Repository schema of Talend Open Studio User Guide. The fields that come after are pre-filled in using the fetched data. A schema is a row description. Repository: Select the repository file where Properties are stored.

tMysqlSP. A stored procedure is used to carry out this operation. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameters is to be returned as value. It can be used as start component but only input parameters are thus allowed. • Connect the components using the Row Main link. • The tRowGenerator is used to generate the odd id number. Scenario: Finding a State Label using a stored procedure The following job aims at finding the State labels matching the odd State IDs in a Mysql two-column table. Usage Limitation This component is used as intermediary component. • Click on the Plus button to add a column to the schema to generate. RECORDSET: Input parameters is to be returned as a set of values. Double-click on the component to launch the editor. • Select the Key check box and define the Type to Int. • The Length equals to 2 digits max. 512 Talend Open Studio Components Creative Commons License . Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. The Stored Procedures syntax should match the Database syntax. Note that the SP schema can hold more columns than there are paramaters used in the procedure. likely after modification through the procedure (function). rather than single value.Databases components tMysqlSP Parameters Click the Plus button and select the various Schema Columns that will be required by the procedures. • Drag and drop the following components used in this example: tRowGenerator. tLogRow.

set manually the connection information. • Click Sync Column to retrieve the generated schema from the preceding component. The connection details get filled in automatically. • Change the Value of step from 1 to 2 for this example. still starting from 1.Databases components tMysqlSP • Use the preset function called sequence but customize the Parameters in the lower part of the window. • Set the Number of generated rows to 25 in order for all the odd State id (of 50 states) to be generated. • Else. • Click OK to validate the configuration. Creative Commons License Talend Open Studio Components 513 . • Set the Property type field to Repository and select the relevant entry on the list. • Then select the tMysqlSP component and define its properties.

• Type in the name of the procedure in the SP Name field as it is called in the Database. set the tLogRow component properties. In this example. END $$ • In the Parameters area. 514 Talend Open Studio Components Creative Commons License . • And select the Print values in cells of a table check box for reading convenience. • Then save your Job and execute it.`getstate` $$ CREATE DEFINER=`root`@`localhost` PROCEDURE `getstate`(IN pid INT. OUT pstate VARCHAR(50)) BEGIN SELECT LabelState INTO pstate FROM us_states WHERE idState = pid. • Select the encoding type on the list. • Eventually. • Set the Column field to ID. and the Type field to IN as it will be given as input parameter to the procedure. The procedure to be executed states as follows: DROP PROCEDURE IF EXISTS `talend`.Databases components tMysqlSP • Then click Edit Schema and add an extra column to hold the State Label to be output. in addition to the ID. • Add a second line and set the Column field to State and the Type to Out as this is the output parameter to be returned. • Synchronize the schema with the preceding component. Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. getstate. The output shows the state labels corresponding to the odd state ids as defined in the procedure. click the plus button to add a line to the table.

The [Components] dialog box displays. expand Metadata and right click DB Connections to create a connection to the relevant database and to store the connection information locally. especially with tMysqlConnection. Usage Limitation This component is to be used along with Mysql components. • Select tMySQLConnection and click OK. Where clause for table Enter the Where clause to identify the tables to iterate name selection on. n/a Scenario: Iterating on DB tables and deleting their content using a user-defined SQL template The following Java scenario creates a three-component job that iterates on given table names from a MySQL database using a WHERE clause. • Drop the following two components from the Palette onto the design workspace: tMysqlTableList and tELT. • Connect tMysqlConnection to tMysqlTableList using an OnSubjobOk link. For advanced use. drop a tMySQLConnection component in the design workspace and fill the connection details manually.Databases components tMysqlTableList tMysqlTableList tMysqlTableList Properties Component family Databases/MySQL Function Purpose Basic settings Iterates on a set of table names through a defined Mysql connection. start with creating a connection to the database that contains the tables you want to empty of their content. Component list Select the tMysqlConnection component in the list if more than one connection are planned for the current job. see Defining Metadata items of Talend Open Studio User Guide. • In the Repository tree view. For more information about Metadata. The tMySQLConnection components displays on the design workspace with all connection details automatically filled in its Basic settings view. Otherwise. • Drop the database connection you created from the Repository onto the design workspace. Lists the names of a given set of Mysql tables using a select statement based on a Where clause. It then deletes the content of the tables directly on the DBMS using a user-defined SQL template. Creative Commons License Talend Open Studio Components 515 .

we want the job to iterate on all the tables which names start with “ex”. • Enter a WHERE clause using the right syntax in the corresponding field to iterate on the table name(s) you want to delete the content of. • If needed. In this scenario. we want to connect to a MySQL database called examples. 516 Talend Open Studio Components Creative Commons License . double-click tELT to display its Basic settings view and define its settings.Databases components tMysqlTableList • Connect tMysqlTableList to tELT using an Iterate link. • On the Component list. double-click tMysqlTableList to display its Basic settings view and define its settings. select the relevant MySQL connection component if more than one connection is used. In this example. double-click tMysqlConnection to display its Basic settings view and verify the connection details. • In the design workspace. • In the design workspace.

• Click in the Table name field and press Ctrl+Space to access the global variable list. • From the global variable list. • On the Component list.get("tMysqlTableList_1_CURRENT_TABLE")). The New SQLTemplate wizard opens. Creative Commons License Talend Open Studio Components 517 . To create the user-defined SQL template: • In the Repository tree view. select ((String)globalMap. enter the name of the database containing the tables you want to process. expand SQL Templates and MySQL in succession. select the relevant MySQL connection component if more than one connection is used. • Right-click UserDefined and select Create SQLTemplate from the drop-down list.Databases components tMysqlTableList • In Database Name.

An SQL pattern editor opens on the design workspace. deleting the content of all tables which names start with “ex” in this example.Databases components tMysqlTableList • Enter a name for the new SQL template and fill in the other fields If needed and then click Finish to close the wizard. • Press Ctrl+S to save the new user-defined SQL template. you must use the correct variable name attached to the table name parameter (“__TABLE-NAME__” in this example). The next step is to add the new user-defined SQL template to the SQL template list in the tELT component. • Delete the existing code and enter the code necessary to carry out the desired action. 518 Talend Open Studio Components Creative Commons License . To display the variable name used. In the SQL template code. put your pointer in the Table Name field in the basic settings of the tELT component.

• Click in the first line to display a drop-down arrow and then click the arrow to display the SQL template list. • Click the Add button and add two SQL template lines. • Select in the list the user-defined SQL template you already created. Related scenario For tMysqlTableList related scenario. • Save your job and press F6 to execute it. click the SQL Templates tab to display the SQLTemplate List. see Scenario: Iterating on a DB table and listing its column names on page 455.Databases components tMysqlTableList To add the user-defined SQL template to the SQL template list: • In the Component view of tELT. All tables in the MySQL examples database which names begin with “ex” are emptied from their content. • Make sure that the SQL template in the second line is Commit. Creative Commons License Talend Open Studio Components 519 .

make sure the connection name is unique and distinctive all over through the two Job levels. make sure that the available connection components are sharing the intended connection.e. Use an existing connection Select this check box when you are using the component tNetezzaConnection.Databases components tNetezzaBulkExec tNetezzaBulkExec tNetezzaBulkExec properties Component family Databases/Netezza Function Purpose Basic settings Executes the Insert action on the data provided. see your studio user guide. DB user authentication data. Schema and Edit Schema 520 Talend Open Studio Components Creative Commons License . Repository: Select the Repository file where Properties are stored. In this case. Otherwise. Component list presents only the connection components in the same Job level. When selected. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. For more information on how to share a DB connection across Job levels. The schema is either built-in or remotely stored in the Repository. it defines the number of fields to be processed and passed on to the next component. For more information about Dynamic settings. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. As a dedicated component. Built-in: No property data stored centrally. so if you need to use an existing connection from the other level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Host Port Database Username and Password Table Database server IP address Listening port number of DB server. i. Name of the table to be written. A schema is a row description. When a Job contains the parent Job and the child Job. Name of the database. tNetezzaBulkExec offers gains in performance while carrying out the Insert operations to a Netezza database Property type Either Built-in or Repository. the fields to follow are pre-filled in using fetched data..

Character of the row to be escaped. Enter the number of rows to be skipped. Creative Commons License Talend Open Studio Components 521 . Use Date delimiter to specify the separator between date values. Enter the maximum error limit that will not stop the process. • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. hence can be reused. Usage Limitation This component offers performance and flexibility of Netezza DB query handling. • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538. Use Time format to distinguish the time is represented in a string. n/a Related scenarios For uses cases in relation with tNetezzaBulkExec. Use Time delimiter to specify the separator between time values. File Name Name of the file to be processed. This field is compulsory for DB data handling. Repository: The schema already exists and is stored in the Repository. months and days are represented in a string. Select this check box to use data enclosure characters. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490. Use Date format to distinguish the way years. Related topic: Setting a Repository schema of Talend Open Studio User Guide. String (ex: “\n”on Unix) to distinguish rows. string or regular expression to separate fields.Databases components tNetezzaBulkExec Built-in: The schema is created and stored locally for this component only. Character. Advanced settings Field Separator Require quotes (“) around data files Row Separator Escape character Date format / Date delimiter Time format/ Time delimiter Encoding Max Errors Skip Rows tStatCatcher Statistics Select this check box to collect log data at the component level. Select the encoding from the list or select Custom and define it manually.

Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tNetezzaConnection and tNetezzaCommit. This component is to be used along with Netezza components. Component list Select the tNetezzaConnection component in the list if more than one connection are planned for the current Job. 522 Talend Open Studio Components Creative Commons License . n/a Related scenario No scenario is available for this component yet.Databases components tNetezzaClose tNetezzaClose tNetezzaClose properties Component family Databases/Netezza Function Purpose Basic settings tNetezzaClose closes the transaction committed in the connected DB. Close a transaction.

Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component family Databases/Netezza Function Purpose tNetezzaCommit validates the data processed through the Job into the connected DB Using a unique connection. It allows you to close the database connection once the commit is done. If you want to use a Row > Main connection to link tAS400Commit to your Job. Creative Commons License Talend Open Studio Components 523 . this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. In this case. This component is to be used along with Netezza components. your data will be commited row by row. Component list Select the tNetezzaConnection component in the list if more than one connection are planned for the current Job.Databases components tNetezzaCommit tNetezzaCommit tNetezzaCommit Properties This component is closely related to tNetezzaConnection and tNetezzaRollback. especially with tNetezzaConnection and tNetezzaRollback. It usually does not make much sense to use one of these without using a tNetezzaConnection component to open a connection for the current transaction. Clear this check box to continue to use the selected connection once the component has performed its task. see Scenario: Inserting data in mother/daughter tables on page 460. do not select the Close connection check box or your connection will be closed before the end of your first row commit. n/a Related scenario This component is closely related to tNetezzaConnection and tNetezzaRollback. This check box is selected by default. It usually does not make much sense to use these components independently in a transaction. For tNetezzaCommit related scenario.

This component allows you to commit all of the Job data to an output database in just a single transaction. Host Port Database Username and Password Additional JDBC Parameters Encoding Type Database server IP address Listening port number of DB server. This field is compulsory for DB data handling. especially with tNetezzaCommit and tNetezzaRollback. Built-in: No property data stored centrally. see Scenario: Inserting data in mother/daughter tables on page 460. Name of the database DB user authentication data. The fields that come after are pre-filled in using the fetched data. Use or register a shared DB Connection Usage Limitation This component is to be used along with Netezza components. Specify additional connection properties for the DB connection you are creating. n/a Related scenarios For tNetezzaConnection related scenario. Select this check box to share your connection or fetch a connection shared by a parent or child Job. 524 Talend Open Studio Components Creative Commons License .Databases components tNetezzaConnection tNetezzaConnection tNetezzaConnection Properties This component is closely related to tNetezzaCommit and tNetezzaRollback. Shared DB Connection Name: set or type in the shared connection name. Repository: Select the repository file where Properties are stored. Select the encoding from the list or select Custom and define it manually. It usually does not make much sense to use one of these without using a tNetezzaConnection component to open a connection for the current transaction. once the data has been validated. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Property type Either Built-in or Repository. Component family Databases/Netezza Function Purpose Basic settings tNetezzaConnection opens a connection to the database for a current transaction.

Name of the database DB user authentication data. Use an existing connection Select this check box when using a tNetezzaConnection component. For more information on how to share a DB connection across Job levels. see Setting up a DB connection of Talend Open Studio User Guide. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Built-in: No property data stored centrally. Otherwise. For more information about setting up and storing database connection parameters. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Then it passes on the field list to the next component via a Main row link. make sure the connection name is unique and distinctive all over through the two Job levels. see your studio user guide. The fields that come after are pre-filled in using the fetched data. For more information about Dynamic settings. In this case. Component list presents only the connection components in the same Job level. Property type Either Built-in or Repository. When a Job contains the parent Job and the child Job. tNetezzaInput executes a DB query with a strictly defined order which must correspond to the schema definition. Basic settings Creative Commons License Talend Open Studio Components 525 . make sure that the available connection components are sharing the intended connection. Repository: Select the repository file where Properties are stored. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.Databases components tNetezzaInput tNetezzaInput tNetezzaInput properties Component family Databases/Netezza Function Purpose tNetezzaInput reads a database and extracts fields based on a query. so if you need to use an existing connection from the other level. Host Port Database Username and Password Database server IP address Listening port number of DB server.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i.Databases components tNetezzaInput Schema and Edit Schema A schema is a row description. Select this check box to remove leading and trailing whitespace from all the String/Char columns. Related scenarios Related scenarios for tNetezzaInput are: • Scenario 1: Displaying selected data from DB table on page 253. helps to decide the row set to work with at a time and thus optimize performance. Usage This component covers all possibilities of SQL queries onto a Netezza database.. Repository: The schema already exists and is stored in the Repository. This field is compulsory for DB data handling. • Scenario 2: Using StoreSQLQuery variable on page 254. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Table Name Name of the table to be read. hence can be reused. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually.e. When selected. Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Remove leading and trailing whitespace from defined columns. 526 Talend Open Studio Components Creative Commons License . Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. it defines the number of fields to be processed and passed on to the next component.

you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. updates. Host Port Database Username and Password Database server IP address Listening port number of DB server. tNetezzaOutput executes the action defined on the table and/or on the data contained in the table. Component list presents only the connection components in the same Job level. Name of the database DB user authentication data. Built-in: No property data stored centrally. makes changes or suppresses entries in a database. For more information about Dynamic settings. see Setting up a DB connection of Talend Open Studio User Guide. make sure the connection name is unique and distinctive all over through the two Job levels. The fields that come after are pre-filled in using the fetched data. so if you need to use an existing connection from the other level. In this case.Databases components tNetezzaOutput tNetezzaOutput tNetezzaOutput properties Component family Databases/Netezza Function Purpose tNetezzaOutput writes. Property type Either Built-in or Repository. Basic settings Creative Commons License Talend Open Studio Components 527 . For more information on how to share a DB connection across Job levels. For more information about setting up and storing database connection parameters. Otherwise. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. based on the flow incoming from the preceding component in the designed Job. Use an existing connection Select this check box when using a tNetezzaConnection component. Repository: Select the repository file where Properties are stored. see your studio user guide. make sure that the available connection components are sharing the intended connection. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job.

528 Talend Open Studio Components Creative Commons License . Do the same in the Key in delete column for the Delete operation. Drop a table if exists and create: The table is removed if it already exists and created again. Repository: The schema already exists and is stored in the Repository. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations.. To do that: Select the Use field options check box and then in the Key in update column. Drop and create a table: The table is removed and created again. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Note that only one table can be written at a time On the table defined. it defines the number of fields to be processed and passed on to the next component. you can perform: Insert: Add new entries to the table. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. On the data of the table defined. job stops. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Clear a table: The table content is deleted. The schema is either built-in or remotely stored in the Repository. you can perform one of the following operations: None: No operation is carried out.e. Action on data Schema and Edit Schema A schema is a row description. i. select the check boxes next to the column names you want to use as a base for the Update operation. Create a table if not exists: The table is created if it does not exist. For an advanced use. Built-in: The schema is created and stored locally for this component only. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. If duplicates are found. hence can be reused.Databases components tNetezzaOutput Table Action on table Name of the table to be written. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Create a table: The table does not exist and gets created. Update: Make changes to existing entries Insert or update: Add entries or update existing ones..

This option is not offered if you create (with or without drop) the DB table. which are not insert. If needed. tStatCatcher Statistics Select this check box to collect log data at the component level. Clear the check box to skip the row on error and complete the process for error-free rows. or action that require particular preprocessing. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. you can retrieve the rows on error via a Row > Rejects link. The gain in system performance is huge. see Scenario 3: Retrieve data in error with a Reject link on page 483 Creative Commons License Talend Open Studio Components 529 . Advanced settings Additional JDBC parameters Extend Insert Encoding Type Select the encoding type from the list or select Custom and define it manually. Position: Select Before. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. This component must be used as an output component. Note that too high value decreases performance due to memory issues.Databases components tNetezzaOutput Die on error This check box is selected by default. This field is compulsory for DB data handling. Select this check box to carry out a bulk insert of a definable set of lines instead of inserting lines one by one. above all. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Number of rows to be completed before committing batches of rows together into the DB. This option ensures transaction quality (but not rollback) and. especially when there is double action on data. For an example of tMySqlOutput in use. Specify additional connection properties for the DB connection you are creating. It allows you to carry out actions on a table or on the data of a table in a Netezza database. This option allows you to call SQL functions to perform actions on columns. better performance at executions. Commit every Additional Columns Use field options Select this check box to customize a request. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Number of rows per insert: enter the number of rows to be inserted as one block. Replace or After following the action to be performed on the reference column. nor update or delete actions.

530 Talend Open Studio Components Creative Commons License .Databases components tNetezzaOutput Related scenarios For tNetezzaOutput related topics. see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476.

Databases components tNetezzaRollback tNetezzaRollback tNetezzaRollback properties This component is closely related to tNetezzaCommit and tNetezzaConnection. see Scenario: Rollback from inserting data in mother/daughter tables on page 498. n/a Related scenarios For tNetezzaRollback related scenario. Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component list Select the tNetezzaConnection component in the list if more than one connection are planned for the current job. Creative Commons License Talend Open Studio Components 531 . Component family Databases/Netezza Function Purpose Basic settings tNetezzaRollback cancels the transaction committed in the connected DB. Clear this check box to continue to use the selected connection once the component has performed its task. especially with tNetezzaConnection and tNetezzaCommit. This component is to be used along with Netezza components. This component avoids to commit part of a transaction involuntarily. It usually does not make much sense to use these components independently in a transaction.

It executes the SQL query stated onto the specified database. Host Port Database Username and Password Database server IP address Listening port number of DB server. make sure that the available connection components are sharing the intended connection. In this case. The row suffix means that the component implements a flow in the job design although it does not provide output. tNetezzaRow acts on the actual DB structure or on the data (although without handling data). Otherwise. For more information on how to share a DB connection across Job levels. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. make sure the connection name is unique and distinctive all over through the two Job levels. Use an existing connection Select this check box and click the relevant tNetezzaConnection component on the Component list to reuse the connection details you already defined. Built-in: No property data stored centrally. When a Job contains the parent Job and the child Job. Repository: Select the repository file where Properties are stored. so if you need to use an existing connection from the other level.Databases components tNetezzaRow tNetezzaRow tNetezzaRow properties Component family Databases/Netezza Function tNetezzaRow is the specific component for this database query. Name of the database DB user authentication data. The SQLBuilder tool helps you write easily your SQL statements. For more information about Dynamic settings. Depending on the nature of the query and the database. Component list presents only the connection components in the same Job level. see your studio user guide. Purpose Basic settings 532 Talend Open Studio Components Creative Commons License . Property type Either Built-in or Repository. The fields that come after are pre-filled in using the fetched data. see Use or register a shared DB connection in any database connection component corresponding to the database you are using.

This option is not available if you have selected the Use an existing connection check box in the Basic settings. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. Performance levels are increased Die on error Advanced settings Additional JDBC parameters Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. i. Select this check box to insert the result of the query into a COLUMN of the current flow. hence can be reused. Repository: The schema already exists and is stored in the Repository. you can retrieve the rows on error via a Row > Rejects link.e. Built-in: The schema is created and stored locally for this component only. If needed. it defines the number of fields to be processed and passed on to the next component. In the Set PreparedStatement Parameter table. Clear the check box to skip the row on error and complete the process for error-free rows. Parameter Index: Enter the parameter position in the SQL instruction. The schema is either built-in or remotely stored in the Repository. Specify additional connection properties for the DB connection you are creating. The Query field gets accordingly filled in.Databases components tNetezzaRow Schema and Edit Schema A schema is a row description. Either Built-in or Repository. This check box is selected by default. Select this column from the use column list. This option is very useful if you need to execute the same query several times. This field is compulsory for DB data handling. Creative Commons License Talend Open Studio Components 533 . define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Parameter Type: Enter the parameter type. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Parameter Value: Enter the parameter value. Table Name Query type Enter the name of the table to be processed. Select this checkbox if you want to query the database using a PreparedStatement.. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Related topic: Setting a built-in schema of Talend Open Studio User Guide.

Related scenarios For a tNetezzaRow related scenario. tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tNetezzaRow Commit every Number of rows to be completed before committing batches of rows together into the DB. see Scenario 1: Removing and regenerating a MySQL table index on page 502. This option ensures transaction quality (but not rollback) and above all better performance on executions. 534 Talend Open Studio Components Creative Commons License . Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.

the the full database connection details are required. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Schema name. When a Job contains the parent Job and the child Job. replaces or truncate data in an Oracle database. In Java projects. make sure that the available connection components are sharing the intended connection. appends. Use an existing connection Select this check box when you are using the component tOracleConnection. Connection type DB Version Host Port Database Schema Service Name Perl only Username and Password Drop-down list of available drivers Select the Oracle version in use IP address of the database server Port number listening the database server Database name. it allows gains in performance during operations performed on data of an Oracle database. Property type Either Built-in or Repository. For more information on how to share a DB connection across Job levels. Built-in: No property data stored centrally. see your studio user guide. Component list presents only the connection components in the same Job level. Oracle Service Name or SID in Oracle database. As a dedicated component. In this case. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Creative Commons License Talend Open Studio Components 535 . make sure the connection name is unique and distinctive all over through the two Job levels. The fields that come after are pre-filled in using the fetched data. DB user authentication data.Databases components tOracleBulkExec tOracleBulkExec tOracleBulkExec properties Component family Databases/Oracle Function Purpose Basic settings tOracleBulkExec inserts. Repository: Select the repository file where Properties are stored. For more information about Dynamic settings. Otherwise. so if you need to use an existing connection from the other level.

i. Drop and create a table: The table is removed and created again. Whitespace: the separator used is a space. it defines the number of fields to be processed and passed on to the next component. On the data of the table defined.Databases components tOracleBulkExec Table Action on table Name of the table to be written.ctl) and specify its path in the . job stops. 536 Talend Open Studio Components Creative Commons License . A schema is a row description. you can perform one of the following operations: None: No operation is carried out. Select this check box to change the separator used for the numbers.. you can perform: Insert: Inserts rows to an empty table. Clear a table: The table content is deleted. Fixed: set the Record length. Note that only one table can be written at a time On the table defined. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Other terminator: Set another terminator in the Field terminator field. the schema is an input parameter. Define the record format: Default: format parameters are set by default. The schema is either built-in or remotely stored in the Repository. EOF (used for loading LOBs from lobfile): the separator used is an EOF character (End Of File). manually Fields terminated by Character. Create a table if doesn’t exist: The table is created if it does not exist.e. If duplicates are found.ctl file name field. Data file name Action on data Schema and Edit schema Advanced settings Advanced separator (for number) Use existing control file Record format Specify . Update: Update the existing data of the table. Stream: set Record terminator. Variable: set the Field size of the record length. Create a table: The table does not exist and gets created. string or regular expression to separate fields: None: no separator is used. Truncate table: The table content is deleted. Append: Adds rows to the existing data of the table Replace: Overwrites some rows of the table Truncate: Drops table entries and inserts new input flow data.ctl file’s INTO Select this check box to manually fill in the INTO TABLE clause TABLE clause of the control file. Name of the file to be processed. Select this check box if you use a control file (. You do not have the possibility to rollback the operation. In Stored Procedure principle.

Use schema’s Date Pattern to load Date field Specify field condition Select this check box to define data loading condition. This field is compulsory for database data handling. to global variable. Click + to add data loading options: Parameter: select a loading parameter from the list. Select this check box to use the date pattern of the schema in the date field. This field is compulsory for DB data handling.Databases components tOracleBulkExec Use fields enclosure Select this check box if you want to use enclosing characters for the text: Fields enclosure (left part): character delimiting the left of the field. Data enclosure characters. Value: enter a value for the parameter selected. Select the encoding type from the list or select Custom and define it manually. Field enclosure (right part): character delimiting the right of the field. Select this check box to load null columns. select the language used for the data that are not used in Unicode. string or regular expression to separate fields. Fields terminated by Perl only Perl only Perl only Usage Fields optionnally enclosed by Encoding Character. Select this check box to modify the territory conventions used for day and weeks numbering. This dedicated component offers performance and flexibility of Oracle DB query handling. Preserve blanks Trailing null columns Load options Select this check box to preserve the blanks. Select this check box to uppercase the names of the columns and the name of the table. Your OS value is the default value used. Select the type of output for the standard output of the Oracle database: to console. Creative Commons License Talend Open Studio Components 537 . NLS Language Set Parameter NLS_TERRITORY Encoding Type Output Convert columns and table names to uppercase tStatCatcher Statistics Select this check box to collect log data at the component level. Select the encoding from the list or select Custom and define it manually. In the list.

if it isn’t stored either in the Repository. Contract_Value. tFileOutputDelimited. ID_Client. including output File Name. • Change the default encoding to AL32UTF8 encoding type. tOracleBulkExec from the Palette to the design workspace • Connect the tOracleInput with the tFileOutputDelimited using a row main link. • Define the tFileOutputDelimited component parameters. Row separator and Fields delimiter. Contract_type. the schema is as follows: ID_Contract. The related job is composed of three components that respectively creates the content. • Define the Oracle connection details. • Then double-click on the tOracleBulkExec to define the DB feeding properties. In this example. • And connect the tOracleInput to the tOracleBulkExec using a OnSubjobOk trigger link.Databases components tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB This scenario describes how to truncate the content of an Oracle DB and load an input file content. output this content into a file to be loaded onto the Oracle database after the DB table has been truncated. • Set also the Encoding to the Oracle encoding type as above. • Define the schema. 538 Talend Open Studio Components Creative Commons License . • Drop the following components: tOracleInput. We recommend you to store the DB connection details in the Metadata repository in order to retrieve them easily at any time in any job.

. Port. In this scenario. • Thus. • Fill in the name of the Table to be fed and the Action on data to be carried out. select Repository mode if you stored the database connection details under the Metadata node of the Repository or select Built-in mode to define them manually.] button next to the Edit schema field to describe the structure of the data to be passed on to the next component.Databases components tOracleBulkExec • In the Property Type. and click [. select Built-in mode. Database. Username. • Click the Advanced settings view to configure the advanced settings of the component. we use the Built-in mode. • In the Schema field. Creative Commons License Talend Open Studio Components 539 . in this use case: insert. Schema.. set the connection parameters in the following fields: Host. and Password.

Field terminated by.Databases components tOracleBulkExec • Select the Use an existing control file check box if you want to use a control file (. Trailing null columns. 540 Talend Open Studio Components Creative Commons License . Preserve blanks. • Define the Encoding as in preceding steps. Or. NLS Language et Set Parameter NLS_TERRITORY according to your database.ctl file’s INTO TABLE clause manually. Use field enclosure.ctl) storing the status of the physical structure of the database. fill in the following fields manually: Record format. Related topic: Scenario: Inserting data in MySQL database on page 495. in the Output field. Use schema’s Date Pattern to load Date field. Load options. Specify . • For this scenario. select to console to output the standard output f the database to the console. Press F6 to run the job. The log output displays in the Run tab and the table is fed with the parameter file data. Specify field condition.

n/a Related scenario No scenario is available for this component yet. Close a transaction. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Creative Commons License Talend Open Studio Components 541 . This component is to be used along with Oracle components.Databases components tOracleClose tOracleClose tOracleClose properties Component family Databases/Oracle Function Purpose Basic settings tOracleClose closes the transaction committed in the connected DB. especially with tOracleConnection and tOracleCommit. Component list Select the tOracleConnection component in the list if more than one connection are planned for the current Job.

This check box is selected by default. If you want to use a Row > Main connection to link tAS400Commit to your Job. This component is to be used along with Oracle components. It usually doesn’t make much sense to use one of these without using a tOracleConnection component to open a connection for the current transaction. see tMysqlConnection on page 460. especially with tOracleConnection and tOracleRollback components. Component family Databases/Oracle Function Purpose Validates the data processed through the job into the connected DB Using a unique connection. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tOracleCommit tOracleCommit tOracleCommit Properties This component is closely related to tOracleConnection and tOracleRollback. For tOracleCommit related scenario. It usually doesn’t make much sense to use these components independently in a transaction. n/a Related scenario This component is closely related to tOracleConnection and tOracleRollback. do not select the Close connection check box or your connection will be closed before the end of your first row commit. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. Component list Select the tOracleConnection component in the list if more than one connection are planned for the current job. your data will be commited row by row. It allows you to close the database connection once the commit is done. Clear this check box to continue to use the selected connection once the component has performed its task. In this case. 542 Talend Open Studio Components Creative Commons License .

This component allows you to commit all of the Job data to an output database in just a single transaction. TNS File: Enter the path to the tns file manually or browse to the file by clicking the three-dot button next to the filed. once the data has been validated. One tns file may have many contexts. Component family Databases/Oracle Function Purpose Basic settings Opens a connection to the database for a current transaction. Select a DB Connection in Tns File: Click the three-dot button to display all the contexts held in the tns file and select the desired one. Property type Either Built-in or Repository. Select the Oracle version in use Select this check box to use the metadata of a context included in a tns file. The fields that come after are pre-filled in using the fetched data. Built-in: No property data stored centrally. Name of the database Name of the schema DB user authentication data. Connection type DB Version Use tns file Drop-down list of available drivers. Host Port Database Schema Username and Password Encoding Type Database server IP address Listening port number of DB server. Repository: Select the repository file where Properties are stored. This field is compulsory for DB data handling. Creative Commons License Talend Open Studio Components 543 . It usually doesn’t make much sense to use one of these without using a tOracleConnection component to open a connection for the current transaction.Databases components tOracleConnection tOracleConnection tOracleConnection Properties This component is closely related to tOracleCommit and tOracleRollback. Select the encoding from the list or select Custom and define it manually.

For tOracleConnection related scenario.Databases components tOracleConnection Use or register a shared DB Connection Select this check box to share your connection or fetch a connection shared by a parent or child Job. 544 Talend Open Studio Components Creative Commons License . see tMysqlConnection on page 460. Shared DB Connection Name: set or type in the shared connection name. n/a Related scenario This component is closely related to tOracleCommit and tOracleRollback. Usage Limitation This component is to be used along with Oracle components. especially with tOracleCommit and tOracleRollback components. It usually doesn’t make much sense to use one of these without using a tOracleConnection component to open a connection for the current transaction. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child.

Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository Built-in: No property data stored centrally. Host Port Database Oracle schema Database server IP address Listening port number of DB server. Name of the database Oracle schema name. tOracleInput executes a DB query with a strictly defined order which must correspond to the schema definition. For more information on how to share a DB connection across Job levels. make sure that the available connection components are sharing the intended connection. In this case. Otherwise. Select the Oracle version in use Select this check box when using a configured tOracleConnection component. For more information about Dynamic settings. Basic settings Creative Commons License Talend Open Studio Components 545 . Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Connection type DB Version Use an existing connection Drop-down list of available drivers. make sure the connection name is unique and distinctive all over through the two Job levels. see Setting up a DB connection of Talend Open Studio User Guide. see your studio user guide.Databases components tOracleInput tOracleInput tOracleInput properties Component family Databases/Oracle Function Purpose tOracleInput reads a database and extracts fields based on a query. The fields that come after are pre-filled in using the fetched data. When a Job contains the parent Job and the child Job. Component list presents only the connection components in the same Job level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about setting up and storing database connection parameters. so if you need to use an existing connection from the other level. Then it passes on the field list to the next component via a Main row link.

Related topic: Setting a Repository schema of Talend Open Studio User Guide. i. Table name Database table name.e. Repository: The schema already exists and is stored in the Repository. The schema is either built-in or remotely stored in the Repository. This field is compulsory for DB data handling. Encoding Type Select the encoding type from the list or select Custom and define it manually. 546 Talend Open Studio Components Creative Commons License .. Related scenarios Related topics in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. hence can be reused. helps to decide the row set to work with at a time and thus optimize performance. Advanced settings tStatCatcher Statistics Select this check box to collect log data at the component level. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Use cursor Trim all the String/Char columns Trim column Usage This component covers all possibilities of SQL queries onto a Oracle database. Select this check box to remove leading and trailing whitespace from all the String/Char columns. A schema is a row description. Built-in: The schema is created and stored locally for this component only.Databases components tOracleInput Username and Password Schema and Edit Schema DB user authentication data. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Remove leading and trailing whitespace from defined columns. When selected. it defines the number of fields to be processed and passed on to the next component.

Batch Size.Databases components tOracleOutput tOracleOutput tOracleOutput properties Component family Databases/Oracle Function Purpose tOracleOutput writes. For more information on how to share a DB connection across Job levels. Otherwise. When you deselect it. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. make sure that the available connection components are sharing the intended connection. see your studio user guide. For more information about setting up and storing database connection parameters. based on the flow incoming from the preceding component in the job. makes changes or suppresses entries in a database. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. tOracleOutput executes the action defined on the table and/or on the data contained in the table. DB Version Drop-down list of available drivers. see Setting up a DB connection of Talend Open Studio User Guide. Repository: Select the repository file where Properties are stored. When a Job contains the parent Job and the child Job. In this case. Property type Either Built-in or Repository. For more information about Dynamic settings. The fields that come after are pre-filled in using the fetched data. Component list presents only the connection components in the same Job level. a check box appears (selected by default and followed by a field) in the Advanced settings. so if you need to use an existing connection from the other level. Connection type This field is Java only. Use an existing connection Select this check box when using a tOracleConnection component. make sure the connection name is unique and distinctive all over through the two Job levels. Built-in: No property data stored centrally. updates. Select the Oracle version in use Basic settings Creative Commons License Talend Open Studio Components 547 . which enables you to define the number of lines in each processed batch.

Databases components
tOracleOutput

Host Port Database Username and Password This field is Perl only. Oracle schema Table Action on table

Database server IP address Listening port number of DB server. Name of the database DB user authentication data. Name of the Oracle schema Name of the table to be written. Note that only one table can be written at a time On the table defined, you can perform one of the following operations: None: No operation is carried out. Drop and create a table: The table is removed and created again. Create a table: The table does not exist and gets created. Create a table if not exists: The table is created if it does not exist. Drop a table if exists and create: The table is removed if it already exists and created again. Clear a table: The table content is deleted. On the data of the table defined, you can perform: Insert: Add new entries to the table. If duplicates are found, job stops. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). For an advanced use, click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. To do that: Select the Use field options check box and then in the Key in update column, select the check boxes next to the column names you want to use as a base for the Update operation. Do the same in the Key in delete column for the Delete operation..

Action on data

Schema and Edit Schema

A schema is a row description, i.e., it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository.

548

Talend Open Studio Components

Creative Commons License

Databases components
tOracleOutput

Built-in: The schema is created and stored locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide. This option is Java only. Die on error This check box is selected by default. Clear the check box to skip the row on error and complete the process for error-free rows. If needed, you can retrieve the rows on error via a Row > Rejects link. Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Select this check box to override variables already set for a NLS language environment. Select the encoding type from the list or select Custom and define it manually. This field is compulsory for DB data handling. Enter the number of rows to be completed before committing batches of rows together into the DB. This option ensures transaction quality (but not rollback) and, above all, better performance at execution.

Advanced settings

Additional JDBC parameters

Java only. This field is Perl only. Override any existing NLS_LANG environment variable Encoding Type

Commit every

tStatCatcher Statistics Select this check box to collect log data at the component level. Additional Columns This option is not offered if you create (with or without drop) the DB table. This option allows you to call SQL functions to perform actions on columns, which are not insert, nor update or delete actions, or action that require particular preprocessing. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. Position: Select Before, Replace or After following the action to be performed on the reference column. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. Use field options Java only. Select this check box to customize a request, especially when there is double action on data.

Creative Commons License

Talend Open Studio Components

549

Databases components
tOracleOutput

Use Hint Options Java only.

Select this check box to activate the hint configuration area which helps you optimize a query’s execution. In this area, parameters are: - HINT: specify the hint you need, using the syntax /*+ */. - POSITION: specify where you put the hint in a SQL statement. - SQL STMT: select the SQL statement you need to use. Select this check box to set the names of columns and table in upper case. Select this check box to display each step during processing entries in a database. When selected, enables you to define the number of lines in each processed batch. This option is available only when you do not Use an existing connection in Basic settings.

Java only. Java only.

Convert columns and table to uppercase Enable debug mode Use Batch Size

Java only.

Java only. Usage

Support null in “SQL WHERE” statement

Select this check box to validate null in “SQL WHERE” statement.

This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. This component must be used as an output component. It allows you to carry out actions on a table or on the data of a table in a Oracle database. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. For an example of tMySqlOutput in use, see Scenario 3: Retrieve data in error with a Reject link on page 483

Related scenarios
For tOracleOutput related topics, see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476.

550

Talend Open Studio Components

Creative Commons License

Databases components
tOracleOutputBulk

tOracleOutputBulk
tOracleOutputBulk properties
tOracleOutputBulk and tOracleBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. These two steps compose the tOracleOutputBulkExec component, detailed in a separate section. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading.
Component family Databases/Oracle

Function Purpose Basic settings

Writes a file with columns based on the defined delimiter and the Oracle standards Prepares the file to be used as parameter in the INSERT query to feed the Oracle database. Property type Either Built-in or Repository. Built-in: No property data stored centrally. Repository: Select the Repository file where Properties are stored. The following fields are pre-filled in using fetched data. File Name Name of the file to be processed. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Select this check box to add the new rows at the end of the file A schema is a row description, i.e., it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository. Built-in: The schema will be created and stored locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository, hence can be reused in various projects and job designs. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Append Schema and Edit Schema

Advanced settings

Advanced separator (for number)

Select this check box to change data separators for numbers: Thousands separator: define separators you want to use for thousands. Decimal separator: define separators you want to use for decimals.

Creative Commons License

Talend Open Studio Components

551

Databases components
tOracleOutputBulk

Field separator Row separator Encodind Type

Character, string or regular expression to separate fields. String (ex: “\n”on Unix) to separate rows. Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Usage This component is to be used along with tOracleBulkExec component. Used together they offer gains in performance while feeding a Oracle database.

Related scenarios
For uses cases in relation with tOracleOutputBulk, see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538

552

Talend Open Studio Components

Creative Commons License

Databases components
tOracleOutputBulkExec

tOracleOutputBulkExec
tOracleOutputBulkExec properties
Component family Databases/Oracle

Function Purpose Basic settings

Executes the Insert action on the data provided. As a dedicated component, it allows gains in performance during Insert operations to an Oracle database. Property type Either Built-in or Repository. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Use an existing connection Select this check box and click the relevant tOracleConnection component on the Component list to reuse the connection details you already defined. When a Job contains the parent Job and the child Job, Component list presents only the connection components in the same Job level, so if you need to use an existing connection from the other level, make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels, see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise, you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case, make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings, see your studio user guide. Connection type DB Version Host Port Database Schema Username and Password Table List of available drivers Select the Oracle version in use Database server IP address Listening port number of DB server. Name of the database Name of the schema DB user authentication data. Name of the table to be written. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Talend Open Studio Components 553

Creative Commons License

Databases components
tOracleOutputBulkExec

Action on table

On the table defined, you can perform one of the following operations: None: No operations is carried out. Drop and create the table: The table is removed and created again. Create a table: The table does not exist and gets created. Create table if doesn’t exist: The table is created if does not exist. Clear a table: The table content is deleted. Truncate table: The table content is deleted. You do not have the possibility to rollback the operation. Name of the file to be processed. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. This check box is selected by default. It creates a directory to hold the output table if required. Select this check box to add the new rows at the end of the file. On the data of the table defined, you can perform: Insert: Add new entries to the table. If duplicates are found, job stops. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Update or insert: Update existing entries or create it if non existing Truncate: Remove all entries from table. Character, string or regular expression to separate fields. Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. Select this check box to change data separators for numbers: Thousands separator: define separators you want to use for thousands. Decimal separator: define separators you want to use for decimals. Select this check box and browse to the .ctl control file you want to use. Character, string or regular expression to separate fields. String (ex: “\n”on Unix) to separate rows.

File Name

Create directory if not exists Append Action on data

Field separator Encoding Type

Advanced settings

Advanced separator (for number)

Use existing control file Field separator Row separator

Specify .ctl file’s INTO Select this check box to enter manually the INTO TABLE clause TABLE clause of the control file directly into the manually code. Use schema’s Date Pattern to load Date field Select this check box to use the date model indicated in the schema for dates.

554

Talend Open Studio Components

Creative Commons License

Databases components
tOracleOutputBulkExec

Specify field condition Select this check box to define a condition for loading data. Preserve blanks Trailing null columns Load options Select this check box to preserve blank spaces. Select this check box to load data with all empty columns. Click + to add data loading options: Parameter: select a loading parameter from the list. Value: enter a value for the parameter selected. From the drop-down list, select the language for your data if the data is not in Unicode. Select this check box to modify the conventions used for date and time formats. The default value is that of the operating system. Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. Select the type of output for the standard output of the Oracle database: to console, to global variable. Select this check box to put columns and table names in upper case.

NLS Language Set Parameter NLS_TERRITORY Encoding Type

Output

Convert columns and table names to uppercase

tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Usage Limitation This component is mainly used when no particular transformation is required on the data to be loaded onto the database. n/a

Related scenarios
For uses cases in relation with tOracleOutputBulkExec, see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490. • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495. • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538.

Creative Commons License

Talend Open Studio Components

555

Databases components
tOracleRollback

tOracleRollback
tOracleRollback properties
This component is closely related to tOracleCommit and tOracleConnection. It usually doesn’t make much sense to use these components independently in a transaction.
Component family Databases

Function Purpose Basic settings

Cancel the transaction commit in the connected DB. Avoids to commit part of a transaction involuntarily. Component list Select the tOracleConnection component in the list if more than one connection are planned for the current job. Clear this check box to continue to use the selected connection once the component has performed its task.

Close Connection

Advanced settings Usage Limitation

tStatCatcher Statistics Select this check box to collect log data at the component level. This component is to be used along with Oracle components, especially with tOracleConnection and tOracleCommit components. n/a

Related scenario
This component is closely related to tOracleConnection and tOracleCommit. It usually doesn’t make much sense to use one of these without using a tOracleConnection component to open a connection for the current transaction. For tOracleRollback related scenario, see tMysqlRollback on page 498.

556

Talend Open Studio Components

Creative Commons License

Databases components
tOracleRow

tOracleRow
tOracleRow properties
Component family Databases/Oracle

Function

tOracleRow is the specific component for this database query. It executes the SQL query stated onto the specified database. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Depending on the nature of the query and the database, tOracleRow acts on the actual DB structure or on the data (although without handling data). The SQLBuilder tool helps you write easily your SQL statements. Property type Either Built-in or Repository. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Use an existing connection Select this check box and click the relevant tOracleConnection component on the Component list to reuse the connection details you already defined. When a Job contains the parent Job and the child Job, Component list presents only the connection components in the same Job level, so if you need to use an existing connection from the other level, make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels, see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise, you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case, make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings, see your studio user guide. Connection type Host Port Database Username and Password Drop-down list of available drivers. Database server IP address Listening port number of DB server. Name of the database DB user authentication data.

Purpose

Basic settings

Creative Commons License

Talend Open Studio Components

557

Databases components
tOracleRow

Schema and Edit Schema

A schema is a row description, i.e., it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Query type

Either Built-in or Repository. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository. The Query field gets accordingly filled in.

Query

Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. This check box is selected by default. Clear the check box to skip the row on error and complete the process for error-free rows. If needed, you can retrieve the rows on error via a Row > Rejects link. Select this check box to insert the result of the query into a COLUMN of the current flow. Select this column from the use column list. Select this checkbox if you want to query the database using a PreparedStatement. In the Set PreparedStatement Parameter table, define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Parameter Index: Enter the parameter position in the SQL instruction. Parameter Type: Enter the parameter type. Parameter Value: Enter the parameter value. This option is very useful if you need to execute the same query several times. Performance levels are increased

Die on error

Advanced settings

Propagate QUERY’s recordset Use PreparedStatement

Encoding Type

Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. Number of rows to be completed before committing batches of rows together into the DB. This option ensures transaction quality (but not rollback) and above all better performance on executions.

Commit every

tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.

558

Talend Open Studio Components

Creative Commons License

Databases components
tOracleRow

Related scenarios
For related topics, see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502.

Creative Commons License

Talend Open Studio Components

559

Databases components
tOracleSCD

tOracleSCD
tOracleSCD belongs to two component families: Business Intelligence and Databases. For more information on it, see tOracleSCD on page 34.

560

Talend Open Studio Components

Creative Commons License

Databases components
tOracleSCDELT

tOracleSCDELT
tOracleSCDELT belongs to two component families: Business Intelligence and Databases. For more information on it, see tOracleSCDELT on page 36.

Creative Commons License

Talend Open Studio Components

561

Databases components
tOracleSP

tOracleSP
tOracleSP Properties
Component family Databases/Oracle

Function Purpose Basic settings

tOracleSP calls the database stored procedure. tOracleSP offers a convenient way to centralize multiple or complex queries in a database and call them easily. Use an existing connection Select this check box to use an established connection from tOracleConnection. Once you select it, the Component list field appears allowing you to choose the tOracleConnection component to be used from those already established on the studio workspace. For more information on tOracleConnection, see section tOracleConnection on page 543. When a Job contains the parent Job and the child Job, Component list presents only the connection components in the same Job level, so if you need to use an existing connection from the other level, make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels, see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise, you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case, make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings, see your studio user guide. Connection type The type may be: - Oracle SID - Oracle Service Name - Oracle OCI Either Built-in or Repository. Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. DB Version Host Port Database Schema Select the Oracle version in use Database server IP address Listening port number of DB server. Name of the database Name of the Schema

Property type

562

Talend Open Studio Components

Creative Commons License

Databases components
tOracleSP

Username and Password Schema and Edit Schema

DB user authentication data. In SP principle, the schema is an input parameter. A schema is a row description, i.e., it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

SP Name Is Function / Return result in

Type in the exact name of the Stored Procedure (or Function) Select this check box, if the stored procedure is a function and one value only is to be returned. Select on the list the schema column, the value to be returned is based on. Click the Plus button and select the various Schema Columns that will be required by the procedures. Note that the SP schema can hold more columns than there are paramaters used in the procedure. Select the Type of parameter: IN: Input parameter OUT: Output parameter/return value IN OUT: Input parameter is to be returned as value, likely after modification through the procedure (function). RECORDSET: Input parameters is to be returned as a set of values, rather than single value. Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records. The Custom Type is used when a Schema Column you want to use is user-defined. Two Custom Type columns are available in the Parameters table. In the first Custom Type column: - Select the check box in the Custom Type column when the corresponding Schema Column you want to use is of user-defined type. - If all listed Schema Columns in the Parameters table are of custom type, you can select the check box before Custom Type once for them all. In the second Custom Type column, you can precise what the custom type is. The type may be: - STRUCT: used for one element. - ARRAY: used for a collection of elements.

Parameters

Creative Commons License

Talend Open Studio Components

563

Databases components
tOracleSP

In the Custom name column, specify the name of the custom type that you have given to this type. When an OUT parameter uses the custom type, make sure that its corresponding Schema Column has chosen the Object type in the schema table. Advanced settings Additional JDBC parameters Specify additional connection properties for the DB connection you are creating. This option is not available if you have selected the Use an existing connection check box in the Basic settings. Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. In the list, select the language used for the data that are not used in Unicode. Select the conventions used for date and time formats. The default value is that of the operating system.

Encoding Type

NLS Language NLS Territory

tStatCatcher Statistics Select this check box to gather the job processing metadata at a job level as well as at each component level. Usage Limitation This component is used as intermediary component. It can be used as start component but only input parameters are thus allowed. The Stored Procedures syntax should match the Database syntax. When the parameters set in this component are of Custom Type, the tJava family components should be placed before the component in order for users to define values for the custom-type parameters, or after the component so as to read and output the Out-type custom parameters.

Scenario: Checking number format using a stored procedure
The following job aims at connecting to an Oracle Database containing Social Security Numbers and their holders’ name, calling a stored procedure that checks the SSN format of against a standard ###-##-#### format. Then the verification output results, 1 for valid format and 0 for wrong format get displayed onto the execution console.

564

Talend Open Studio Components

Creative Commons License

Databases components
tOracleSP

• Drag and drop the following components from the Palette: tOracleConnection, tOracleInput, tOracleSP and tLogRow. • Link the tOracleConnection to the tOracleInput using a Then Run connection as no data is handled here. • And connect the other components using a Row Main link as rows are to be passed on as parameter to the SP component and to the console. • In the tOracleConnection, define the details of connection to the relevant Database. You will then be able to reuse this information in all other DB-related components. • Then select the tOracleInput and define its properties.

• Select the Use an existing connection check box and select the tOracleConnection component in the list in order to reuse the connection details that you already set. • Select Repository as Property type as the Oracle schema is defined in the DB Oracle connection entry of the Repository. If you haven’t recorded the Oracle DB details in the Repository, then fill in the Schema name manually. • Then select Repository as Schema, and retrieve the relevant schema corresponding to your Oracle DB table.

• In this example, the SSN table has a four-column schema that includes ID, NAME, CITY and SSNUMBER. • In the Query field, type in the following Select query or select it in the list, if you stored it in the Repository. select ID, NAME, CITY, SSNUMBER from SSN • Then select the tOracleSP and define its Basic settings.

Creative Commons License

Talend Open Studio Components

565

Databases components
tOracleSP

• Like for the tOracleInput component, select Repository in the Property type field and select the Use an existing connection check box, then select the relevant entries in the respective list. • The schema used for the tOracleSP slightly differs from the input schema. Indeed, an extra column (SSN_Valid) is added to the Input schema. This column will hold the format validity status (1 or 0) produced by the procedure.

• In the SP Name field, type in the exact name of the stored procedure (or function) as called in the Database. In this use case, the stored procedure name is is_ssn.

566

Talend Open Studio Components

Creative Commons License

Databases components
tOracleSP

• The basic function used in this particular example is as follows: CREATE OR REPLACE FUNCTION is_ssn(string_in VARCHAR2) RETURN PLS_INTEGER IS -- validating ###-##-#### format BEGIN IF TRANSLATE(string_in, '0123456789A', 'AAAAAAAAAAB') = 'AAA-AA-AAAA' THEN RETURN 1; END IF; RETURN 0; END is_ssn; / • As a return value is expected in this use case, the procedure acts as a function, so select the Is function check box. • The only return value expected is based on the ssn_valid column, hence select the relevant list entry. • In the Parameters area, define the input and output parameters used in the procedure. In this use case, only the SSNumber column from the schema is used in the procedure. • Click the plus sign to add a line to the table and select the relevant column (SSNumber) and type (IN). • Then select the tLogRow component and click Sync Column to make sure the schema is passed on from the preceding tOracleSP component.

• Select the Print values in cells of a table check box to facilitate the output reading. • Then save your job and press F6 to run it.

On the console, you can read the output results. All input schema columns are displayed eventhough they are not used as parameters in the stored procedure.

Creative Commons License

Talend Open Studio Components

567

Databases components
tOracleSP

The final column shows the expected return value, i.e. whether the SS Number checked is valid or not. Check the tParseRecordSet component if you want to analyze a set of records from a database table or DB query and return single records.

568

Talend Open Studio Components

Creative Commons License

Databases components
tOracleTableList

tOracleTableList

tOracleTableList properties
Component family Databases/Oracle

Function Purpose Basic settings

tOracleTableList iterates on a set of tables through a defined Oracle connection. This component lists the names of specified Oracle tables using a SELECT statement based on a WHERE clause. Component list Select the tOracleConnection component in the list if more than one connection is planned for the current Job.

Where clause for table Enter the WHERE clause that will be used to identify name selection the tables to iterate on. Usage Limitation This component is to be used along with other Oracle components, especially with tOracleConnection. n/a

Related scenarios
For a a tOracleTablerList related scenario, see Scenario: Iterating on DB tables and deleting their content using a user-defined SQL template on page 515.

Creative Commons License

Talend Open Studio Components

569

Databases components
tParAccelBulkExec

tParAccelBulkExec

tParAccelBulkExec Properties
tParAccelOutputBulk and tParAccelBulkExec components are generally used together, to generate the output file which will be used as a parameter in the SQL query execution. This execution in two steps is unified in the tParAccelOutputBulkExec component, which details are given in a different section. The point of offering two separated components is to enable you to do transformations before changing data in the database.
Component Family Databases/ParAccel

Function Purpose Basic settings

tParAccelBulkExec performs an Insert action on the data. tParAccelBulkExec is a component which is specifically designed to improve performance when loading data in ParAccel database. Property type Either Built-in or Repository Built-in: No property data stored centrally. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Use an existing connection Select this check box if you use a configured tParAccelConnection. When a Job contains the parent Job and the child Job, Component list presents only the connection components in the same Job level, so if you need to use an existing connection from the other level, make sure that the available connection components are sharing the intended connection. For more information on how to share a DB connection across Job levels, see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Otherwise, you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. In this case, make sure the connection name is unique and distinctive all over through the two Job levels. For more information about Dynamic settings, see your studio user guide. Host Port Database Schema Username and Password Database server IP address. Listening port number of DB server. Database name. Exact name of the schema. DB user authentication data.

570

Talend Open Studio Components

Creative Commons License

Databases components
tParAccelBulkExec

Table Action on table

Name of the table to be written. Note that only one table can be written at a time On the table defined, you can perform one of the following operations: None: No operation is carried out. Drop and create a table: The table is removed and created again. Create a table: The table does not exist and gets created. Create a table if not exists: The table is created if it does not exist. Drop a table if exists and create: The table is removed if already exists and created again. Clear a table: The table content is deleted. A schema is a row description, i.e., it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Built-in: The schema is created and stored locally for this component only. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: Setting a Repository schema of Talend Open Studio User Guide.

Schema and Edit Schema

Advanced settings

Copy mode Filename File Type Field Layout Field separator Explicit IDs Remove Quotes Max. Errors Date Format Time/Timestamp Format Additional COPY Options Log file Logging level Select the information type you want to record in your log file. Type in the maximum number of errors before your Job stops. Type in the date format to be used. Name and path of the file to be processed. Select in the list the file type. Select in the list the field layout. Character, string or regular expression to separate fields.

tStatCatcher Statistics Select this check box to collect log data at the component level.

Creative Commons License

Talend Open Studio Components

571

Databases components
tParAccelBulkExec

Usage

This component covers all possibilities of SQL queries onto a database. It allows you to do actions on a table or the data in a table in a Greenplum database. It enables you to create a reject flow, with a Row > Reject link filtering the data in error. For a usage example, see Scenario 3: Retrieve data in error with a Reject link on page 483 from component tMysqlOutput.

Related scenarios
For a related scenario, see: • Scenario: Displaying DB output on page 258 from tDBOutput. • Scenario 1: Adding a new column and altering data in a DB table on page 476 from tMySQLOutput.

572

Talend Open Studio Components

Creative Commons License

Databases components
tParAccelClose

tParAccelClose
tParAccelClose properties
Component family Databases/ParAccel

Function Purpose Basic settings

tParAccelClose closes the transaction committed in the connected DB. Close a transaction. Component list Select the tParAccelConnection component in the list if more than one connection are planned for the current Job.

Advanced settings Usage Limitation

tStatCatcher Statistics Select this check box to collect log data at the component level. This component is to be used along with ParAccel components, especially with tParAccelConnection and tParAccelCommit. n/a

Related scenario
No scenario is available for this component yet.

Creative Commons License

Talend Open Studio Components

573

In this case. It usually doesn’t make much sense to use these components independently in a transaction. For tParAccelCommit related scenario. Component family Databases/ParAccel Function Purpose Validates the data processed through the job into the connected DB. If you want to use a Row > Main connection to link tAS400Commit to your Job. Using a unique connection. This check box is selected by default. Component list Select the tParAccelConnection component in the list if more than one connection are planned for the current job. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Clear this check box to continue to use the selected connection once the component has performed its task. especially with tParAccelConnection and tParAccelRollback components. your data will be commited row by row. 574 Talend Open Studio Components Creative Commons License . do not select the Close connection check box or your connection will be closed before the end of your first row commit.Databases components tParAccelCommit tParAccelCommit tParAccelCommit Properties This component is closely related to tParAccelConnection and tParAccelRollback. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. It usually doesn’t make much sense to use one of these without using a tParAccelConnection component to open a connection for the current transaction. It allows you to close the database connection once the commit is done. n/a Related scenario This component is closely related to tParAccelConnection and tParAccelRollback. This component is to be used along with ParAccel components. see tMysqlConnection on page 460.

Use or register a shared DB Connection Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Select this check box to automatically commit a transaction when it is completed. n/a Creative Commons License Talend Open Studio Components 575 . This component allows you to commit all of the Job data to an output database in just a single transaction. especially with tParAccelCommit and tParAccelRollback components. Built-in: No property data stored centrally. Select this check box to share your connection or fetch a connection shared by a parent or child Job.Databases components tParAccelConnection tParAccelConnection tParAccelConnection Properties This component is closely related to tParAccelCommit and tParAccelRollback. Name of the database Name of the schema DB user authentication data. The fields that come after are pre-filled in using the fetched data. once the data has been validated. Shared DB Connection Name: set or type in the shared connection name. It usually doesn’t make much sense to use one of these without using a tParAccelConnection component to open a connection for the current transaction. Component family Databases/ParAccel Function Purpose Basic settings Opens a connection to the database for a current transaction. Usage Limitation This component is to be used along with ParAccel components. Host Port Database Schema Username and Password Encoding Type Database server IP address Listening port number of DB server. Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

see tMysqlConnection on page 460.Databases components tParAccelConnection Related scenario This component is closely related to tParAccelCommit and tParAccelRollback. For tParAccelConnection related scenario. It usually doesn’t make much sense to use one of these without using a tParAccelConnection component to open a connection for the current transaction. 576 Talend Open Studio Components Creative Commons License .

tParAccelInput executes a DB query with a strictly defined order which must correspond to the schema definition. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. Otherwise. Component list presents only the connection components in the same Job level. Repository: Select the repository file where Properties are stored.Databases components tParAccelInput tParAccelInput tParAccelInput properties Component family Databases/ ParAccel Function Purpose tParAccelInput reads a database and extracts fields based on a query. see your studio user guide. so if you need to use an existing connection from the other level. see Setting up a DB connection of Talend Open Studio User Guide. Basic settings Creative Commons License Talend Open Studio Components 577 . Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. Use an existing connection Select this check box when using a configured tParAccelConnection component. Then it passes on the field list to the next component via a Main row link. For more information about Dynamic settings. In this case. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. make sure that the available connection components are sharing the intended connection. make sure the connection name is unique and distinctive all over through the two Job levels. Name of the database Exact name of the schema DB user authentication data. Property type Either Built-in or Repository Built-in: No property data stored centrally. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. The fields that come after are pre-filled in using the fetched data. For more information about setting up and storing database connection parameters.

The schema is either built-in or remotely stored in the Repository. it defines the number of fields to be processed and passed on to the next component. Related topic: Setting a built-in schema of Talend Open Studio User Guide. helps to decide the row set to work with at a time and thus optimize performance. i. hence can be reused. Remove leading and trailing whitespace from defined columns. Repository: The schema already exists and is stored in the Repository. This field is compulsory for DB data handling. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. Guess schema Advanced settings Encoding Type Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios Related topics in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 578 Talend Open Studio Components Creative Commons License . Select this check box to remove leading and trailing whitespace from all the String/Char columns..Databases components tParAccelInput Schema and Edit Schema A schema is a row description. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Usage This component covers all possibilities of SQL queries onto a ParAccel database. Click the Guess schema button to retrieve the table schema.e. Built-in: The schema is created and stored locally for this component only. Table name Name of the table to be read. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. When selected. Select the encoding type from the list or select Custom and define it manually.

Creative Commons License Talend Open Studio Components 579 . you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Database name. For more information about Dynamic settings. For more information about setting up and storing database connection parameters. make sure that the available connection components are sharing the intended connection. Otherwise. Repository: Select the repository file where Properties are stored. Use an existing connection Select this check box if you use a configured tParAccelConnection. Component list presents only the connection components in the same Job level. Listening port number of DB server. see your studio user guide. so if you need to use an existing connection from the other level. In this case. see Setting up a DB connection of Talend Open Studio User Guide. Exact name of the schema. modifies or deletes the data in a database. updates. tParAccelOutput executes the action defined on the table and/or on the data of a table. according to the input flow form the previous component.Databases components tParAccelOutput tParAccelOutput tParAccelOutput Properties Component Family Databases/ParAccel Function Purpose Basic settings tParAccelOutput writes. For more information on how to share a DB connection across Job levels. When a Job contains the parent Job and the child Job. make sure the connection name is unique and distinctive all over through the two Job levels. DB user authentication data. Property type Either Built-in or Repository Built-in: No property data stored centrally. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. The fields that come after are pre-filled in using the fetched data. Host Port Database Schema Username et Password Database server IP address. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view.

select the check boxes next to the column names you want to use as a base for the Update operation. Action on data Schema and Edit Schema A schema is a row description. Clear a table: The table content is deleted. i. you can perform one of the following operations: None: No operation is carried out.e. Related topic: Setting a Repository schema of Talend Open Studio User Guide. 580 Talend Open Studio Components Creative Commons License . If duplicates are found. Drop and create a table: The table is removed and created again. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. Repository: The schema already exists and is stored in the Repository. You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s). Do the same in the Key in delete column for the Delete operation. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. it defines the number of fields to be processed and passed on to the next component. Create a table: The table does not exist and gets created. Built-in: The schema is created and stored locally for this component only. The schema is either built-in or remotely stored in the Repository. On the data of the table defined.. Note that only one table can be written at a time On the table defined. you can perform: Insert: Add new entries to the table.Databases components tParAccelOutput Table Action on table Name of the table to be written. For an advanced use. To do that: Select the Use field options check box and then in the Key in update column. Create a table if not exists: The table is created if it does not exist. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. hence can be reused. job stops. Drop a table if exists and create: The table is removed if already exists and created again.

nor update or delete actions. Related scenarios For a related scenario. above all. Usage This component covers all possibilities of SQL queries onto a database. • Scenario 1: Adding a new column and altering data in a DB table on page 476 from tMySQLOutput. Position: Select Before. which are not insert. or action that require particular preprocessing. see Scenario 3: Retrieve data in error with a Reject link on page 483 from component tMysqlOutput. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. For a usage example. see: • Scenario: Displaying DB output on page 258 from tDBOutput. It enables you to create a reject flow. you can retrieve the rows on error via a Row > Rejects link. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. It allows you to do actions on a table or the data in a table in a ParAccel database. Creative Commons License Talend Open Studio Components 581 . Replace or After following the action to be performed on the reference column. Select the encoding type from the list or select Custom and define it manually. This option is not offered if you create (with or without drop) the DB table. with a Row > Rejects link filtering the data in error. especially when there is double action on data. Clear the check box to skip the row on error and complete the process for error-free rows. Enter the number of rows to be completed before committing batches of rows together into the DB. Advanced settings Encoding Type Commit every Additional Columns Use field options Select this check box to customize a request.Databases components tParAccelOutput Die on error This check box is selected by default. tStatCatcher Statistics Select this check box to collect log data at the component level. This option ensures transaction quality (but not rollback) and. If needed. better performance at execution. This option allows you to call SQL functions to perform actions on columns. This field is compulsory for DB data handling.

string or regular expression to separate fields. detailed in a separate section. Select this check box to add the new rows at the end of the file A schema is a row description. Property type Either Built-in or Repository. 582 Talend Open Studio Components Creative Commons License . Character. hence can be reused in various projects and job designs. The schema is either built-in or remote in the Repository. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. The following fields are pre-filled in using fetched data. Repository: Select the Repository file where Properties are stored. Select this check box to include the column header. Related topic: Setting a built-in schema of Talend Open Studio User Guide. it defines the number of fields that will be processed and passed on to the next component. Component family Databases/ParAccel Function Purpose Basic settings Writes a file with columns based on the defined delimiter and the ParAccel standards Prepares the file to be used as parameter in the INSERT query to feed the ParAccel database.e. File Name Name of the file to be processed. Append Schema and Edit Schema Advanced settings Row separator Field separator Include header String (ex: “\n”on Unix) to distinguish rows.. Repository: The schema already exists and is stored in the Repository. Built-in: No property data stored centrally.Databases components tParAccelOutputBulk tParAccelOutputBulk tParAccelOutputBulk properties tParAccelOutputBulk and tParAccelBulkExec components are used together to output the file that will be then used as parameter to execute the SQL query stated. i. Related topic: Setting a Repository schema of Talend Open Studio User Guide. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Built-in: The schema will be created and stored locally for this component only. These two steps compose the tParAccelOutputBulkExec component.

Databases components tParAccelOutputBulk Encoding Type Select the encoding type from the list or select Custom and define it manually. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538 Creative Commons License Talend Open Studio Components 583 . This field is compulsory for DB data handling. tStatCatcher Statistics Select this check box to collect log data at the component level. Usage This component is to be used along with tParAccelBulkExec component. Used together they offer gains in performance while feeding a ParAccel database. Related scenarios For uses cases in relation with tParAccelOutputBulk.

hence can be reused. it defines the number of fields to be processed and passed on to the next component. Drop and create a table: The table is removed and created again. Related topic: Setting a Repository schema of Talend Open Studio User Guide.e. Name of the table to be written. Note that only one table can be written at a time On the table defined. Create a table if not exists: The table is created if it does not exist. Host Port Database Schema Username and Password Table Action on table Database server IP address. Create a table: The table does not exist and gets created. i. Exact name of the schema. Built-in: The schema is created and stored locally for this component only. The fields that come after are pre-filled in using the fetched data. Schema and Edit Schema 584 Talend Open Studio Components Creative Commons License . you can perform one of the following operations: None: No operation is carried out. Repository: The schema already exists and is stored in the Repository. Database name.. Repository: Select the repository file where Properties are stored. Clear a table: The table content is deleted. Property type Either Built-in or Repository Built-in: No property data stored centrally. Listening port number of DB server.Databases components tParAccelOutputBulkExec tParAccelOutputBulkExec tParAccelOutputBulkExec Properties Component Family Databases/ParAccel Function Purpose Basic settings tParAccelOutputBulkExec performs an Insert action on the data. The schema is either built-in or remotely stored in the Repository. A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Drop a table if exists and create: The table is removed if already exists and created again. DB user authentication data. tParAccelOutputBulkExec is a component which is specifically designed to improve performance when loading data in ParAccel database.

Name and path of the file to be processed.Databases components tParAccelOutputBulkExec Copy mode Filename Advanced settings File Type Row separator Fields terminated by Append Explicit IDs Remove Quotes Max. • Scenario 1: Adding a new column and altering data in a DB table on page 476 from tMySQLOutput. String (ex: “\n”on Unix) to distinguish rows. For a usage example. Errors Date Format Time/Timestamp Format Additional COPY Options Log file Logging level Select the information type you want to record in your log file. string or regular expression to separate fields. Select in the list the file type. Creative Commons License Talend Open Studio Components 585 . see Scenario 3: Retrieve data in error with a Reject link on page 483 from component tMysqlOutput. It enables you to create a reject flow. Select this check box to add the new rows at the end of the file. see: • Scenario: Displaying DB output on page 258 from tDBOutput. Usage This component covers all possibilities of SQL queries onto a database. tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios For a related scenario. with a Row > Reject link filtering the data in error. Type in the maximum number of errors before your Job stops. It allows you to do actions on a table or the data in a table in a ParAccel database. Character. Type in the date format to be used.

Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. Component list Select the tParAccelConnection component in the list if more than one connection are planned for the current job. Component family Databases Function Purpose Basic settings Cancel the transaction commit in the connected DB.Databases components tParAccelRollback tParAccelRollback tParAccelRollback properties This component is closely related to tParAccelCommit and tParAccelConnection. Avoids to commit part of a transaction involuntarily. It usually doesn’t make much sense to use these components independently in a transaction. This component is to be used along with ParAccel components. see tMysqlRollback on page 498. especially with tParAccelConnection and tParAccelCommit components. For tParAccelRollback related scenario. 586 Talend Open Studio Components Creative Commons License . It usually doesn’t make much sense to use one of them without using a tParAccelConnection component to open a connection for the current transaction. Clear this check box to continue to use the selected connection once the component has performed its task. n/a Related scenario This component is closely related to tParAccelConnection and tParAccelCommit.

so if you need to use an existing connection from the other level. The fields that come after are pre-filled in using the fetched data. The row suffix means the component implements a flow in the job design although it doesn’t provide output. For more information about Dynamic settings. When a Job contains the parent Job and the child Job. see Use or register a shared DB connection in any database connection component corresponding to the database you are using.Databases components tParAccelRow tParAccelRow tParAccelRow Properties Component Family Databases/ParAccel Function tParAccelRow is the specific component for this database query. Repository: Select the repository file where Properties are stored. The SQLBuilder tool helps you write easily your SQL statements. Host Port Database Schema Username et Password Database server IP address Listening port number of DB server. Component list presents only the connection components in the same Job level. For more information on how to share a DB connection across Job levels. Purpose Basic settings Creative Commons License Talend Open Studio Components 587 . make sure that the available connection components are sharing the intended connection. Otherwise. Use an existing connection Select this check box and click the relevant tFirebirdConnection component on the Component list to reuse the connection details you already defined. Depending on the nature of the query and the database. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Name of the database Exct name of the schema. It executes the SQL query stated onto the specified database. make sure the connection name is unique and distinctive all over through the two Job levels. tParAccelRow acts on the actual DB structure or on the data (although without handling data). DB user authentication data. see your studio user guide. Property type Either Built-in or Repository. In this case. Built-in: No property data stored centrally.

i. Related topic: Setting a built-in schema of Talend Open Studio User Guide. This check box is selected by default. Repository: Select the relevant query stored in the Repository. Performance levels are increased Query Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. Either Built-in or Repository. Select this checkbox if you want to query the database using a PreparedStatement. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder. Select this check box to insert the result of the query into a COLUMN of the current flow. Built-in: The schema is created and stored locally for this component only. Parameter Index: Enter the parameter position in the SQL instruction.. you can retrieve the rows on error via a Row > Rejects link. Parameter Value: Enter the parameter value. it defines the number of fields to be processed and passed on to the next component. If needed.Databases components tParAccelRow Schema and Edit Schema A schema is a row description. Select this column from the use column list. Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. This option is very useful if you need to execute the same query several times. Clear the check box to skip the row on error and complete the process for error-free rows. In the Set PreparedStatement Parameter table. Table Name Query type Name of the table to be read. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. This field is compulsory for DB data handling. 588 Talend Open Studio Components Creative Commons License . Parameter Type: Enter the parameter type. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide.e. Repository: The schema already exists and is stored in the Repository. hence can be reused. Guess Query Click the Guess Query button to generate the query which corresponds to your table schema in the Query field. The Query field gets accordingly filled in.

see: • Scenario: Resetting a DB auto-increment on page 262 from tDBSQLRow. Creative Commons License Talend Open Studio Components 589 . This option ensures transaction quality (but not rollback) and above all better performance on executions. tStatCatcher Statistics Select this check box to collect log data at the component level. • Scenario 1: Removing and regenerating a MySQL table index on page 502 from tMySQLRow. Related scenarios For a related scenario.Databases components tParAccelRow Commit every Number of rows to be completed before committing batches of rows together into the DB. Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries.

590 Talend Open Studio Components Creative Commons License . For more information on it.Databases components tParAccelSCD tParAccelSCD tParAccelSCD belongs to two component families: Business Intelligence and Databases. see tParAccelSCD on page 39.

e.. This component is mainly designed for a use with the SP component Recordset feature. Repository: The schema already exists and is stored in the Repository. hence can be reused. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Built-in: The schema is created and stored locally for this component only. In SP principle. i. It can be used as start component but only input parameters are thus allowed. Prev. Comp. tParseRecordSet properties Component family Databases Function Purpose Basic settings tParseRecordSet parses a set of records from a database table or DB query and possibly returns single records. it defines the number of fields to be processed and passed on to the next component. The schema is either built-in or remotely stored in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. A schema is a row description. see: Scénario 2: Using PreparedStatement objects to query data on page 503 Creative Commons License Talend Open Studio Components 591 .Databases components tParseRecordSet tParseRecordSet You can find this component at the root of Databases group of the Palette of Talend Open Studio. Related Scenario For an example of tParseRecordSet in use.Parses a recordset rather than individual records from a table. . Attribute table Set the position value of each column for single records from the recordset. the schema is an input parameter. Usage Limitation This component is used as intermediary component. Column list Schema and Edit Schema Set the column from the database that holds the recordset. tParseRecordSet covers needs related indirectly to the use of any database.

Name of the table to be written. Host Port Database Schema Username and Password Table Database server IP address Listening port number of DB server. In this case. see your studio user guide. When a Job contains the parent Job and the child Job. For more information on how to share a DB connection across Job levels. Property type Either Built-in or Repository. Otherwise. As a dedicated component. Built-in: No property data stored centrally. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. so if you need to use an existing connection from the other level. Component list presents only the connection components in the same Job level. Name of the database Name of the DB schema. make sure that the available connection components are sharing the intended connection. For more information about Dynamic settings. tPostgresPlusBulkExec allows gains in performance during Insert operations to a DB2 database. Note that only one table can be written at a time Function Purpose Basic settings 592 Talend Open Studio Components Creative Commons License . make sure the connection name is unique and distinctive all over through the two Job levels. DB user authentication data. The fields that come after are pre-filled in using the fetched data. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.Databases components tPostgresPlusBulkExec tPostgresPlusBulkExec tPostgresPlusBulkExec properties Component family Databases/PostgresPl us tPostgresPlusBulkExec executes the Insert action on the data provided. Use an existing connection Select this check box and click the relevant tPostgresPlusConnection component on the Component List to reuse the connection details you already defined. Repository: Select the repository file where Properties are stored.

Related scenarios For tPostgresPlusBulkExec related topics. string or regular expression to separate fields. The schema is either built-in or remotely stored in the Repository. Repository: You have already created the schema and stored it in the Repository. see: • tMysqlOutputBulkExec Scenario: Inserting transformed data in MySQL database on page 490. A schema is a row description. Create table: The table does not exist and gets created.. Related topic: Setting a built-in schema of Talend Open Studio User Guide. You do not have the possibility to rollback the operation. Usage This dedicated component offers performance and flexibility of DB2 query handling. Character. Clear table: The table content is deleted. Related topic: Setting a Repository schema of Talend Open Studio User Guide.Databases components tPostgresPlusBulkExec Action on table On the table defined. Field terminated by tStatCatcher Statistics Select this check box to collect log data at the component level. • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538. it defines the number of fields to be processed and passed on to the next component.e. you can perform one of the following operations: None: No operation is carried out. Creative Commons License Talend Open Studio Components 593 . Create table if not exists: The table is created if it does not exist. Schema and Edit Schema Advanced settings Action Select the action to be carried out Bulk insert Bulk update Depending on the action selected. Truncate table: The table content is deleted. i. the required information varies. hence can reuse it. Drop and create table: The table is removed and created again. Built-in: You create the schema and store it locally for this component only.

especially with tPostgresPlusConnection and tPostgresPlusCommit. Component list Select the tPostgresPlusConnection component in the list if more than one connection are planned for the current Job. 594 Talend Open Studio Components Creative Commons License . Close a transaction. n/a Related scenario No scenario is available for this component yet. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level.Databases components tPostgresPlusClose tPostgresPlusClose tPostgresPlusClose properties Component family Databases/Postgres Function Purpose Basic settings tPostgresPlusClose closes the transaction committed in the connected DB. This component is to be used along with PostgresPlus components.

Creative Commons License Talend Open Studio Components 595 . n/a Function Purpose Basic settings Close Connection Related scenario This component is closely related to tPostgresPlusConnection and tPostgresPlusRollback. If you want to use a Row > Main connection to link tAS400Commit to your Job.Databases components tPostgresPlusCommit tPostgresPlusCommit tPostgresPlusCommit Properties This component is closely related to tPostgresPlusConnection and tPostgresPlusRollback. It usually doesn’t make much sense to use PostgresPlus components without using the tPostgresPlusConnection component to open a connection for the current transaction. This component is to be used along with PostgresPlus components. Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. It usually doesn’t make much sense to use JDBC components independently in a transaction. It allows you to close the database connection once the commit is done. Component family Databases/PostgresPl us Validates the data processed through the Job into the connected DB. Component list Select the tPostgresPlusConnection component in the list if more than one connection are planned for the current Job. In this case. Using a unique connection. especially with the tPostgresPlusConnection and tPostgresPlusRollback components. For tPostgresPlusCommit related scenario. This check box is selected by default. your data will be commited row by row. do not select the Close connection check box or your connection will be closed before the end of your first row commit. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. see tMysqlConnection on page 460. Clear this check box to continue to use the selected connection once the component has performed its task.

Repository: Select the repository file where Properties are stored. Property type Either Built-in or Repository. Select this check box to share your connection or fetch a connection shared by a parent or child Job. The fields that come after are pre-filled in using the fetched data. Function Purpose Basic settings Use or register a shared DB Connection Advanced settings Auto commit tStatCatcher Statistics Select this check box to gather the job processing metadata at a Job level as well as at each component level. Built-in: No property data stored centrally. Usage Limitation This component is to be used along with PostgresPlus components. It usually doesn’t make much sense to use one of PostgresPlus components without using the tPostgresPlusConnection component to open a connection for the current transaction. especially with the tPostgresPlusCommit and tPostgresPlusRollback components. once the data has been validated. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child. Select this check box to automatically commit a transaction when it is completed. Name of the database Exact name of the schema Enter your DB authentication data.Databases components tPostgresPlusConnection tPostgresPlusConnection tPostgresPlusConnection Properties This component is closely related to tPostgresPlusCommit and tPostgresPlusRollback. Component family Databases/PostgresPl us Opens a connection to the database for a current transaction. Shared DB Connection Name: set or type in the shared connection name. This component allows you to commit all of the Job data to an output database in just a single transaction. This field is compulsory for DB data handling. Select the encoding type from the list or select Custom and define it manually. Host Port Database Schema Username and Password Encoding type Database server IP address Listening port number of DB server. n/a 596 Talend Open Studio Components Creative Commons License .

see tMysqlConnection on page 460.Databases components tPostgresPlusConnection Related scenario This component is closely related to tPostgresPlusCommit and tPostgresPlusRollback. It usually doesn’t make much sense to use one of PostgresPlus components without using the tPostgresPlusConnection component to open a connection for the current transaction. For tPostgresPlusConnection related scenario. Creative Commons License Talend Open Studio Components 597 .

In this case. make sure the connection name is unique and distinctive all over through the two Job levels. Property type Either Built-in or Repository Built-in: No property data stored centrally. Function Purpose Basic settings 598 Talend Open Studio Components Creative Commons License . Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. so if you need to use an existing connection from the other level.Databases components tPostgresPlusInput tPostgresPlusInput tPostgresPlusInput properties Component family Databases/ PostgresPlus tPostgresPlusInput reads a database and extracts fields based on a query. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Name of the database Exact name of the schema DB user authentication data. For more information on how to share a DB connection across Job levels. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Component list presents only the connection components in the same Job level. Then it passes on the field list to the next component via a Main row link. Use an existing connection Select this check box when using a configured tPostgresplusConnection component. see your studio user guide. make sure that the available connection components are sharing the intended connection. For more information about setting up and storing database connection parameters. see Setting up a DB connection of Talend Open Studio User Guide. tPostgresPlusInput executes a DB query with a strictly defined order which must correspond to the schema definition. When a Job contains the parent Job and the child Job. For more information about Dynamic settings. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. Otherwise. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually.

This field is compulsory for DB data handling. Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. Table name Name of the table to be read. Related topic: Setting a Repository schema of Talend Open Studio User Guide.Databases components tPostgresPlusInput Schema and Edit Schema A schema is a row description. Related topic: Setting a built-in schema of Talend Open Studio User Guide. i. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Repository: The schema already exists and is stored in the Repository. Related scenarios Related topics in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Creative Commons License Talend Open Studio Components 599 . helps to decide the row set to work with at a time and thus optimize performance. hence can be reused. When selected. it defines the number of fields to be processed and passed on to the next component. Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. Select this check box to remove leading and trailing whitespace from all the String/Char columns..e. Usage This component covers all possibilities of SQL queries onto a Postgresql database. Remove leading and trailing whitespace from defined columns. Built-in: The schema is created and stored locally for this component only. The schema is either built-in or remotely stored in the Repository.

tPostgresPlusOutput executes the action defined on the table and/or on the data contained in the table. Name of the database Exact name of the schema Function Purpose Basic settings 600 Talend Open Studio Components Creative Commons License . see Use or register a shared DB connection in any database connection component corresponding to the database you are using. so if you need to use an existing connection from the other level. make sure the connection name is unique and distinctive all over through the two Job levels. Property type Either Built-in or Repository. For more information about Dynamic settings. Repository: Select the repository file where Properties are stored. For more information on how to share a DB connection across Job levels. makes changes or suppresses entries in a database.Databases components tPostgresPlusOutput tPostgresPlusOutput tPostgresPlusOutput properties Component family Databases/PostgresPl us tPostgresPlusOutput writes. make sure that the available connection components are sharing the intended connection. In this case. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. based on the flow incoming from the preceding component in the job. Component list presents only the connection components in the same Job level. When a Job contains the parent Job and the child Job. Built-in: No property data stored centrally. The fields that come after are pre-filled in using the fetched data. Use an existing connection Select this check box when using a configured tPostgresPlusConnection component. Otherwise. Host Port Database Schema Database server IP address Listening port number of DB server. see your studio user guide. updates. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. For more information about setting up and storing database connection parameters. see Setting up a DB connection of Talend Open Studio User Guide.

You can do that by clicking Edit Schema and selecting the check box(es) next to the column(s) you want to set as primary key(s).e. For an advanced use. Name of the table to be written. Update: Make changes to existing entries Insert or update: Add entries or update existing ones. Create a table if not exists: The table is created if it does not exist. Do the same in the Key in delete column for the Delete operation. It is necessary to specify at least one column as a primary key on which the Update and Delete operations are based. Clear a table: The table content is deleted. it defines the number of fields to be processed and passed on to the next component. you can perform one of the following operations: None: No operation is carried out. Built-in: The schema is created and stored locally for this component only. On the data of the table defined.Databases components tPostgresPlusOutput Username and Password Table Action on table DB user authentication data. Drop and create a table: The table is removed and created again. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Create a table: The table does not exist and gets created. Action on data Schema and Edit Schema A schema is a row description. you can perform: Insert: Add new entries to the table.. click the Advanced settings view where you can simultaneously define primary keys for the Update and Delete operations. i. Creative Commons License Talend Open Studio Components 601 . To do that: Select the Use field options check box and then in the Key in update column. Truncate table: The table content is deleted. Update or insert: Update existing entries or create it if non existing Delete: Remove entries corresponding to the input flow. Note that only one table can be written at a time On the table defined. You don not have the possibility to rollback the operation. job stops. Drop a table if exists and create: The table is removed if already exists and created again. select the check boxes next to the column names you want to use as a base for the Update operation. If duplicates are found. The schema is either built-in or remotely stored in the Repository.

better performance at execution. hence can be reused. This component must be used as an output component. This option allows you to call SQL functions to perform actions on columns. Enter the number of rows to be completed before committing batches of rows together into the DB. Usage This component offers the flexibility benefit of the DB query and covers all of the SQL queries possible. It allows you to carry out actions on a table or on the data of a table in a PostgresPlus database. This option ensures transaction quality (but not rollback) and. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Position: Select Before. For an example of tMySqlOutput in use. This field is compulsory for DB data handling. you can retrieve the rows on error via a Row > Rejects link. Clear the check box to skip the row on error and complete the process for error-free rows. Use field options Enable debug mode Select this check box to customize a request. Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column. It also allows you to create a reject flow using a Row > Rejects link to filter data in error. Die on error This check box is selected by default. above all. Select the encoding type from the list or select Custom and define it manually. especially when there is double action on data. Advanced settings Encoding Type Commit every Additional Columns tStatCatcher Statistics Select this check box to collect log data at the component level. Select this check box to display each step during processing entries in a database. or action that require particular preprocessing. see Scenario 3: Retrieve data in error with a Reject link on page 483 602 Talend Open Studio Components Creative Commons License .Databases components tPostgresPlusOutput Repository: The schema already exists and is stored in the Repository. If needed. which are not insert. nor update or delete actions. This option is not offered if you create (with or without drop) the DB table. Name: Type in the name of the schema column to be altered or inserted as new column SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data. Replace or After following the action to be performed on the reference column.

see: • tDBOutput Scenario: Displaying DB output on page 258 • tMySQLOutput Scenario 1: Adding a new column and altering data in a DB table on page 476. Creative Commons License Talend Open Studio Components 603 .Databases components tPostgresPlusOutput Related scenarios For tPostgresPlusOutput related topics.

i. string or regular expression to separate fields. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. These two steps compose the tPostgresPlusOutputBulkExec component. File Name Name of the file to be processed. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading. Property type Either Built-in or Repository. Repository: Select the Repository file where Properties are stored. Character.Databases components tPostgresPlusOutputBulk tPostgresPlusOutputBulk tPostgresPlusOutputBulk properties tPostgresplusOutputBulk and tPostgresplusBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated.. it defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Select this check box to add the new rows at the end of the file Select this check box to include the column header to the file. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Built-in: The schema will be created and stored locally for this component only. String (ex: “\n”on Unix) to distinguish rows. hence can be reused in various projects and job designs. detailed in a separate section. Function Purpose Basic settings Field separator Row separator Append Include header Schema and Edit Schema 604 Talend Open Studio Components Creative Commons License .e. Built-in: No property data stored centrally. Repository: The schema already exists and is stored in the Repository. Component family Databases/PostgresPl us Writes a file with columns based on the defined delimiter and the PostgresPlus standards Prepares the file to be used as parameter in the INSERT query to feed the PostgresPlus database. A schema is a row description. The following fields are pre-filled in using fetched data.

Related scenarios For uses cases in relation with tPostgresplusOutputBulk. Usage This component is to be used along with tPostgresPlusBulkExec component. Used together they offer gains in performance while feeding a PostgresPlus database. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538 Creative Commons License Talend Open Studio Components 605 .Databases components tPostgresPlusOutputBulk Encoding Type Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling.

Name of the database Exact name of the schema DB user authentication data. Drop and create a table: The table is removed and created again. it allows gains in performance during Insert operations to a PostgresPlus database. The schema is either built-in or remote in the Repository. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Name of the table to be written. As a dedicated component. String displayed to indicate that the value is null. Create a table: The table does not exist and gets created. On the table defined. i. it defines the number of fields that will be processed and passed on to the next component. Select the type of file being handled.Databases components tPostgresPlusOutputBulkExec tPostgresPlusOutputBulkExec tPostgresPlusOutputBulkExec properties Component family Databases/PostgresPl us Executes the Insert action on the data provided. Function Purpose Basic settings Action on table Schema and Edit Schema Advanced settings Action File type Null string 606 Talend Open Studio Components Creative Commons License . Select the action to be carried out Bulk insert Bulk update Depending on the action selected. you can perform one of the following operations: None: No operation is carried out. Built-in: No property data stored centrally. the required information varies. A schema is a row description. Create a table if not exists: The table is created if it does not exist.. Property type Either Built-in or Repository. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Host Port Database Schema Username and Password Table Database server IP address Listening port number of DB server. Clear a table: The table content is deleted.e.

Databases components tPostgresPlusOutputBulkExec Row separator Field terminated by Text enclosure String (ex: “\n”on Unix) to distinguish rows. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538 Creative Commons License Talend Open Studio Components 607 . string or regular expression to separate fields. tStatCatcher Statistics Select this check box to collect log data at the component level. Related scenarios For uses cases in relation with tPostgresPlusOutputBulkExec. Usage This component is mainly used when no particular tranformation is required on the data to be loaded onto the database. Character. Character used to enclose text.

This component is to be used along with PostgresPlus components.Databases components tPostgresPlusRollback tPostgresPlusRollback tPostgresPlusRollback properties This component is closely related to tPostgresPlusCommit and tPostgresPlusConnection. This component avoids to commit part of a transaction involuntarily. Clear this check box to continue to use the selected connection once the component has performed its task. Component list Select the tPostgresPlusConnection component in the list if more than one connection are planned for the current job. It usually does not make much sense to use these components independently in a transaction. Function Purpose Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. n/a Related scenarios For tPostgresPlusRollback related scenario. 608 Talend Open Studio Components Creative Commons License . Component family Databases/PostgresPl us tPostgresPlusRollback cancels the transaction committed in the connected DB. especially with tPostgresPlusConnection and tPostgresPlusCommit. see Scenario: Rollback from inserting data in mother/daughter tables on page 498.

The fields that come after are pre-filled in using the fetched data. make sure that the available connection components are sharing the intended connection. When a Job contains the parent Job and the child Job.Databases components tPostgresPlusRow tPostgresPlusRow tPostgresPlusRow properties Component family Databases/Postgrespl us tPostgresPlusRow is the specific component for the database query. Depending on the nature of the query and the database. For more information about Dynamic settings. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Name of the database Exact name of the schema DB user authentication data. see your studio user guide. In this case. It executes the SQL query stated onto the specified database. Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. Property type Either Built-in or Repository. Built-in: No property data stored centrally. Use an existing connection Select this check box and click the relevant tPostgresPlusConnection component on the Component list to reuse the connection details you already defined. The SQLBuilder tool helps you write easily your SQL statements. For more information on how to share a DB connection across Job levels. Function Purpose Basic settings Creative Commons License Talend Open Studio Components 609 . see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Repository: Select the repository file where Properties are stored. Otherwise. so if you need to use an existing connection from the other level. tPostgresPlusRow acts on the actual DB structure or on the data (although without handling data). make sure the connection name is unique and distinctive all over through the two Job levels. The row suffix means the component implements a flow in the job design although it doesn’t provide output. Component list presents only the connection components in the same Job level.

If needed. Parameter Value: Enter the parameter value. This option ensures transaction quality (but not rollback) and above all better performance on executions. 610 Talend Open Studio Components Creative Commons License . This check box is selected by default. Performance levels are increased Die on error Advanced settings Propagate QUERY’s recordset Use PreparedStatement Encoding Type Select the encoding from the list or select Custom and define it manually. Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. Related topic: Setting a Repository schema of Talend Open Studio User Guide. This option is very useful if you need to execute the same query several times. Commit every tStatCatcher Statistics Select this check box to collect log data at the component level. it defines the number of fields to be processed and passed on to the next component. Related topic: Setting a built-in schema of Talend Open Studio User Guide. you can retrieve the rows on error via a Row > Rejects link. Clear the check box to skip the row on error and complete the process for error-free rows. hence can be reused. Repository: The schema already exists and is stored in the Repository. The schema is either built-in or remotely stored in the Repository.Databases components tPostgresPlusRow Schema and Edit Schema A schema is a row description. This field is compulsory for DB data handling. Either Built-in or Repository. define the parameters represented by “?” in the SQL instruction of the Query field in the Basic Settings tab. Table name Query type Name of the table to be read. Select this column from the use column list. Built-in: Fill in manually the query statement or build it graphically using SQLBuilder Repository: Select the relevant query stored in the Repository.. In the Set PreparedStatement Parameter table. Parameter Index: Enter the parameter position in the SQL instruction. The Query field gets accordingly filled in. Built-in: The schema is created and stored locally for this component only. Number of rows to be completed before committing batches of rows together into the DB. Select this checkbox if you want to query the database using a PreparedStatement.e. Select this check box to insert the result of the query into a COLUMN of the current flow. Parameter Type: Enter the parameter type. i.

Databases components tPostgresPlusRow Usage This component offers the flexibility benefit of the DB query and covers all possibilities of SQL queries. see: • tDBSQLRow Scenario: Resetting a DB auto-increment on page 262 • tMySQLRow Scenario 1: Removing and regenerating a MySQL table index on page 502. Creative Commons License Talend Open Studio Components 611 . Related scenarios For related topics.

see tPostgresPlusSCD on page 41.Databases components tPostgresPlusSCD tPostgresPlusSCD tPostgresPlusSCD belongs to two component families: Business Intelligence and Databases. 612 Talend Open Studio Components Creative Commons License . For more information on it.

see tPostgresPlusSCDELT on page 43.Databases components tPostgresPlusSCDELT tPostgresPlusSCDELT tPostgresPlusSCDELT belongs to two component families: Business Intelligence and Databases. For more information on it. Creative Commons License Talend Open Studio Components 613 .

so if you need to use an existing connection from the other level. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. The interest in having two separate elements lies in the fact that it allows transformations to be carried out before the data loading in the database. For more information about Dynamic settings. Use an existing connection Select this check box and click the relevant tPostgrresqlConnection component on the Component list to reuse the connection details you already defined. make sure the connection name is unique and distinctive all over through the two Job levels. As a dedicated component. Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. 614 Talend Open Studio Components Creative Commons License .Databases components tPostgresqlBulkExec tPostgresqlBulkExec tPostgresqlBulkExec properties tPostgresqlOutputBulk and tPostgresqlBulkExec components are used together to first output the file that will be then used as parameter to execute the SQL query stated. make sure that the available connection components are sharing the intended connection. These two steps compose the tPostgresqlOutputBulkExec component. DB user authentication data. The fields that come after are pre-filled in using the fetched data. Repository: Select the repository file where Properties are stored. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. Component list presents only the connection components in the same Job level. In this case. Name of the schema. Built-in: No property data stored centrally. Component family Databases/Postgresql Function Purpose Basic settings Executes the Insert action on the data provided. see your studio user guide. Otherwise. tPostgresqlBulkExec offers gains in performance while carrying out the Insert operations to a Postgresql database Property type Either Built-in or Repository. Name of the database. When a Job contains the parent Job and the child Job. detailed in a separate section. For more information on how to share a DB connection across Job levels.

Create table: The table does not exist and gets created. This component is to be used along with tPostgresqlOutputBulk component. hence can be reused. string or regular expression to separate fields. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Note that only one table can be written at a time and that the table must exist for the insert operation to succeed. Built-in: The schema is created and stored locally for this component only. you can perform one of the following operations: None: No operation is carried out.e. i. You don not have the possibility to rollback the operation. Action on table File Name Schema and Edit Schema Fields terminated by Usage Character. Related topic:Defining variables from the Component view of Talend Open Studio User Guide. Drop and create table: The table is removed and created again. Name of the file to be processed. On the table defined.Databases components tPostgresqlBulkExec Table Name of the table to be written. they can offer gains in performance while feeding a Postgresql database. Truncate table: The table content is deleted. The schema is either built-in or remotely stored in the Repository.. Used together. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Create table if not exists: The table is created if it does not exist. see the following scenarios: • tMysqlOutputBulk Scenario: Inserting transformed data in MySQL database on page 490 • tMysqlOutputBulkExec Scenario: Inserting data in MySQL database on page 495 • tOracleBulkExec Scenario: Truncating and inserting file data into Oracle DB on page 538 Creative Commons License Talend Open Studio Components 615 . it defines the number of fields to be processed and passed on to the next component. Clear table: The table content is deleted. A schema is a row description. Repository: The schema already exists and is stored in the Repository. n/a Limitation Related scenarios For uses cases in relation with tPostgresqlBulkExec.

especially with tPostgresqlConnection and tPostgresqlRollback components. In this case. If you want to use a Row > Main connection to link tAS400Commit to your Job. see tMysqlConnection on page 460. Component list Select the tPostgresqlConnection component in the list if more than one connection are planned for the current job. Basic settings Close Connection Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. It usually doesn’t make much sense to use these components independently in a transaction. It usually doesn’t make much sense to use one of these without using a tPostgresqlConnection component to open a connection for the current transaction. Clear this check box to continue to use the selected connection once the component has performed its task. This component is to be used along with Postgresql components. Component family Databases/Postgresql Function Purpose Validates the data processed through the job into the connected DB Using a unique connection. This check box is selected by default. 616 Talend Open Studio Components Creative Commons License .Databases components tPostgresqlCommit tPostgresqlCommit tPostgresqlCommit Properties This component is closely related to tPostgresqlCommit and tPostgresqlRollback. do not select the Close connection check box or your connection will be closed before the end of your first row commit. It allows you to close the database connection once the commit is done. n/a Related scenario This component is closely related to tPostgresqlConnection and tPostgresqlRollback. this component commits in one go a global transaction instead of doing that on every row or every batch and thus provides gain in performance. For tPostgresqlCommit related scenario. your data will be commited row by row.

Advanced settings Usage Limitation tStatCatcher Statistics Select this check box to collect log data at the component level. especially with tPostgresqlConnection and tPostgresqlCommit. n/a Related scenario No scenario is available for this component yet.Databases components tPostgresqlClose tPostgresqlClose tPostgresqlClose properties Component family Databases/Postgresql Function Purpose Basic settings tPostgresqlClose closes the transaction committed in the connected DB. Creative Commons License Talend Open Studio Components 617 . Component list Select the tPostgresqlConnection component in the list if more than one connection are planned for the current Job. This component is to be used along with Postgresql components. Close a transaction.

Component family Databases/Postgresql Function Purpose Basic settings Opens a connection to the database for a current transaction. Host Port Database Schema Username and Password Encoding Type Database server IP address Listening port number of DB server. especially with tPostgresqlCommit and tPostgresqlRollback components. Select this check box to share your connection or fetch a connection shared by a parent or child Job. This field is compulsory for DB data handling. This component allows you to commit all of the Job data to an output database in just a single transaction. 618 Talend Open Studio Components Creative Commons License . It usually doesn’t make much sense to use one of these without using a tPostgresqlConnection component to open a connection for the current transaction.Databases components tPostgresqlConnection tPostgresqlConnection tPostgresqlConnection Properties This component is closely related to tPostgresqlCommit and tPostgresqlRollback. Use or register a shared DB Connection Usage Limitation This component is to be used along with Postgresql components. Name of the database Exact name of the schema DB user authentication data. Select the encoding from the list or select Custom and define it manually. Property type Either Built-in or Repository. It usually doesn’t make much sense to use one of these without using a tPostgresqlConnection component to open a connection for the current transaction. n/a Related scenario This component is closely related to tPostgresqlCommit and tPostgresqlRollback. Repository: Select the repository file where Properties are stored. The fields that come after are pre-filled in using the fetched data. Built-in: No property data stored centrally. once the data has been validated. Shared DB Connection Name: set or type in the shared connection name. This allows you to share one single DB connection among several DB connection components from different Job levels that can be either parent or child.

see tMysqlConnection on page 460. Creative Commons License Talend Open Studio Components 619 .Databases components tPostgresqlConnection For tPostgresqlConnection related scenario.

make sure that the available connection components are sharing the intended connection. make sure the connection name is unique and distinctive all over through the two Job levels. The fields that come after are pre-filled in using the fetched data. Function Purpose Basic settings 620 Talend Open Studio Components Creative Commons License . For more information about Dynamic settings. see Setting up a DB connection of Talend Open Studio User Guide. For more information about setting up and storing database connection parameters. see your studio user guide. Name of the database Exact name of the schema DB user authentication data. Use an existing connection Select this check box when using a configured tPostgresqlConnection component. Repository: Select the repository file where Properties are stored. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. In this case. Host Port Database Schema Username and Password Database server IP address Listening port number of DB server. For more information on how to share a DB connection across Job levels. Property type Either Built-in or Repository Built-in: No property data stored centrally. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. so if you need to use an existing connection from the other level. Then it passes on the field list to the next component via a Main row link. tPostgresqlInput executes a DB query with a strictly defined order which must correspond to the schema definition. Otherwise.Databases components tPostgresqlInput tPostgresqlInput tPostgresqlInput properties Component family Databases/ PostgreSQL tPostgresqlInput reads a database and extracts fields based on a query. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. When a Job contains the parent Job and the child Job. Component list presents only the connection components in the same Job level.

hence can be reused. The schema is either built-in or remotely stored in the Repository. Select this check box to remove leading and trailing whitespace from all the String/Char columns..Databases components tPostgresqlInput Schema and Edit Schema A schema is a row description. Table name Name of the table to be read. Query type and Query Enter your DB query paying particularly attention to properly sequence the fields in order to match the schema definition. When selected. This field is compulsory for DB data handling. it defines the number of fields to be processed and passed on to the next component. Remove leading and trailing whitespace from defined columns. Related topic: Setting a built-in schema of Talend Open Studio User Guide. Related topic: Setting a Repository schema of Talend Open Studio User Guide. Related scenarios Related topics in tDBInput scenarios: • Scenario 1: Displaying selected data from DB table on page 253 • Scenario 2: Using StoreSQLQuery variable on page 254 Related topic in tContextLoad Scenario: Dynamic context use in MySQL DB insert on page 1049. Creative Commons License Talend Open Studio Components 621 . Built-in: The schema is created and stored locally for this component only.e. Usage This component covers all possibilities of SQL queries onto a Postgresql database. Repository: The schema already exists and is stored in the Repository. helps to decide the row set to work with at a time and thus optimize performance. Advanced settings Encoding Type Select the encoding type from the list or select Custom and define it manually. Use cursor Trim all the String/Char columns Trim column tStatCatcher Statistics Select this check box to collect log data at the component level. i.

updates. Repository: Select the repository file where Properties are stored.Databases components tPostgresqlOutput tPostgresqlOutput tPostgresqlOutput properties Component family Databases/Postgresql Function Purpose tPostgresqlOutput writes. For more information on how to share a DB connection across Job levels. Use an existing connection Select this check box when using a configured tPostgresqlConnection component. see Use or register a shared DB connection in any database connection component corresponding to the database you are using. Component list presents only the connection components in the same Job level. tPostgresqlOutput executes the action defined on the table and/or on the data contained in the table. Name of the database Exact name of the schema Basic settings 622 Talend Open Studio Components Creative Commons License . see your studio user guide. Built-in: No property data stored centrally. so if you need to use an existing connection from the other level. For more information about Dynamic settings. Property type Either Built-in or Repository. The fields that come after are pre-filled in using the fetched data. Click this icon to open a database connection wizard and store the database connection parameters you set in the component Basic settings view. see Setting up a DB connection of Talend Open Studio User Guide. Host Port Database Schema Database server IP address Listening port number of DB server. based on the flow incoming from the preceding component in the job. In this case. When a Job contains the parent Job and the child Job. makes changes or suppresses entries in a database. For more information about setting up and storing database connection parameters. make sure the connection name is unique and distinctive all over through the two Job levels. you can as well deactivate the connection components and use Dynamic settings of the component to specify the intended connection manually. make sure that the available connection components are sharing the intended connection. Otherwise.

you can perform one of the following operations: None: No operation is carried out. For an advanced use. On the data of the table defined. Create a table if not exists: The table is created if it does not exist. it defines the number of fields to be processed and passed on to