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
Credits
Foreword
Foreword
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Extracting data from a database


One of the most common integration tasks is to take data from an application database and write it to a file where it might be processed by another system or converted to a report. In this first example, we'll take data from a single database table and export it to a delimited file.

If you're following the examples using the source code provided for this chapter, have a quick look at the tables provided. You'll see that there are two tables, products and brands. The tables are joined by a product ID that is present in both tables. For the first example, we will simply extract the data from the products table.

Perform the following steps:

  1. Under Job Designs in the Repository window, create a new folder named Chapter4 and, within this, create a new job named DBExtract.

  2. Expand the DEMO_DB metadata we created previously to show the Table schemas. Click on the products table and drag this onto the Job Designer. You will be presented with a window which shows lots...