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

Dynamic database lookup


What do we mean by dynamic database lookup? Let's explain with an example scenario.

Let's suppose we have an integration process that passes some information to us and that each time the data set that is returned is different. For example, the information passed to us might be a list of product IDs that have been sold today; tomorrow it will be the product IDs that will be sold tomorrow, and so on. This information is very useful, but a little hard to work with as it is only a list of product IDs. We might want to know other information about the products, such as the product name or the product price.

As we have seen in a previous example, we could extract all of the product data from our database and, using a tJoin or tMap component, match this data with the incoming product order data, and create a file that has the product information appended to the order information. Although this approach would work perfectly well, it might not be the most efficient approach...