Talend Best practices


Talend Best practices book

  1. 1.INTRODUCTION 
    2. BEST PRACTICES 
    2.1. NOTICE …. 3
    2.2. ORGANIZATION OF FOLDER WORK 
    2.3. VERSIONING OF JOB 
    2.4. SUPPRESSION OF JOB 
    2.5. TEST DATA 
    2.6. PALETTE 
    2.7. METADATA ..
    2.8. COMPONENTS  
    2.8.1. Utilization 
    2.8.2. Use / do not use 
    2.8.3. Organization of components 
    2.8.4. Relation between components 
    2.9. DOCUMENTATION
    2.10. VARIABLES 0
    2.11. FILE FORMAT
    2.12. EXECUTION OF JOB ON LOCAL 
    2.12.1. Parameters 
    2.12.2. Debugger 
    3. A LOT OF JAVA 
    3.1. TEST VALUES: NULL, EMPTY, COMPARISON 
    3.2. CONDITIONS 
    3.3. CONCATENATION
  2.  Advices.

1. Introduction
This paper will present a list of best practices, to apply when developing with Talend.
2. Best practices
2.1. Notice
We must know that we develop on an eclipse platform and therefore think in terms of Java naming variables, methods, organization, instruction… (Java project requirements)
When you start the studio, don’t choose to “execute generation engine initialization” on background, and don’t open job until the initialization is finished.
2.2. Organization of folder work
Please prefer organization by project (for each customer) and after by process (import, export, synchronize … etc). It means create a folder grouping projects treatments separated for each client
Example:

talend best practice

talend best practice

 

 

 

 

 

 

 

 

 

 

We can list the following projects: MAAP and MEIE. UTILS folder would be common of jobs that can be used in all projects and are completely independent. Such as a multi-project log management or connection to CRM … Then it is preferable to order the treatment groups in subfolders T1_ … T2_ …and put them inside jobs.

 

Leave a Reply