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

Job versions


Mostly software development is an iterative process. Within a project, developers will iterate through a develop and test cycle until the software is ready to be put into production use. We can also think of an iterative process across projects; release 1 is deployed and is used for a period of time, but some enhancements or amendments are needed, so another project is undertaken and, at the end of this, release 2 is deployed into the wild. This process may go on for many years!

In order to support these iterative processes, the software is versioned to keep track of the code and components that constitute a given release. While the Studio does not contain a full-featured version control system, it does have some features which allow developers to manage software versions.

As we have been developing jobs in the previous chapters, you may have noticed that the Studio adds a version number to the end of the job name that we define. You can see this in the Repository view of jobs...