Book Image

Getting Started with Talend Open Studio for Data Integration

By : Jonathan Bowen
Book Image

Getting Started with Talend Open Studio for Data Integration

By: Jonathan Bowen

Overview of this book

Talend Open Studio for Data Integration (TOS) is an open source graphical development environment for creating custom integrations between systems. It comes with over 600 pre-built connectors that make it quick and easy to connect databases, transform files, load data, move, copy and rename files and connect individual components in order to define complex integration processes. "Getting Started with Talend Open Studio for Data Integration" illustrates common uses and scenarios in a simple, practical manner and, building on knowledge as the book progresses, works towards more complex integration solutions. TOS is a code generator and so does a lot of the "heavy lifting"ù for you. As such, it is a suitable tool for experienced developers and non-developers alike. You'll start by learning how to construct some common integrations tasks ñ transforming files and extracting data from a database, for example. These building blocks form a "toolkit"ù of techniques that you will learn how to apply in many different situations. By the end of the book, once complex integrations will appear easy and you will be your organization's integration expert! Best of all, TOS makes integrating systems fun!
Table of Contents (22 chapters)
Getting Started with Talend Open Studio for Data Integration
About the Author
About the Reviewers

Exporting and importing jobs

The Studio offers a number of different ways to export and import the jobs you create and each approach has a different purpose behind it. In this section we will look at the different methods of importing and exporting jobs and also look at why you might choose one method over another.

Exporting jobs

As we have seen in the section about job versions, the Studio creates file artifacts when you create a job design and stores these on your local computer's filesystem. When you run a job within the Studio, the artifacts, which represent the job configuration, are compiled into Java code before being executed. This development setup and process may be sufficient for some readers, particularly where there is only one developer creating jobs and/or the jobs can be run manually from the studio tool.

When this is not the case, it is useful to be able to export jobs from the Studio tool for two primary reasons:

  1. You want to collaborate with other developers and need some...