Apache Oozie

Chapter 3. Setting Up Oozie

In this chapter, we describe how to build and install Oozie on a single machine. This is suitable for installing evaluation and development environments while also introducing Oozie’s general deployment architecture. Later in this chapter, we also cover advanced installation topics required for a production environment.

Oozie Deployment

In this section, we outline how to deploy and configure Oozie and its related modules on a real system. As explained in “Oozie Architecture”, there are four basic systems in a standard Oozie setup. A short overview of each of those systems will help you to better understand the Oozie setup and installation.

The Oozie server runs in a web container (e.g., Tomcat) and manages Oozie job scheduling and execution. The Oozie server is actually a Hadoop client and a database client while it acts as a server for Oozie clients. It also provides an optional web user interface for basic monitoring of jobs. This web UI utilizes a JavaScript library called extJS, which is not Apache compliant. The Oozie server needs to package all these required libraries into an oozie.war file. Although the Oozie server can be installed on any machine collocated with any other system, we recommend installing it on a separate machine to ensure its stability, especially in large production systems.

The Oozie client can connect to the Oozie server in multiple ways. The Oozie command-line interface (CLI) is the most popular and convenient way of interacting ...