DataZen Jobs: Overview

This section provides an overview of the jobs you can create with DataZen.

Generally speaking, jobs fall into two main categories: Job Readers and Job Writers. These jobs can exist indivually, or be combined. When combined, they are referred to as Direct Jobs. Other, more specialized jobs also exist.

Jobs can be classified as follows:

• Job Reader: A job that reads from a database, drive/FTP (files), HTTP/S endpoint, or Big Data table
• Job Writer: A job that writes to a database, drive/FTP (files), HTTP/S endpoint, or Big Data table
• Direct Job: A job that combines a Job Reader and Job Writer into one
• Dynamic Job: A one-time job (reader or writer) that was created programmatically with no history
• Messaging Consumer: A Job Reader that consumes messages from a queuing platform and optionally forwards them to a target system
• Passthrough Consumer: A special Messaging Consumer that pushes messages into another queuing platform directly with metadata mapping/forwarding (reader + writer)

To create a new job, select the desired Sync Agent on the left bar in DataZen Manager, and click on the New dropdown menu.

How to Start a Job

The following options are available to start a job:

• Manual: Jobs can be started and stopped manually.
• Schedule: Except for Messaging Consumers jobs can be scheduled to start at a desired interval.
• Trigger: Except for Messaging Consumers jobs can have triggers that start other jobs upon completion
• Webhook: Jobs can be started or stopped using the DataZen HTTP API

Messaging Consumer jobs do not run on a schedule; their listener are either in a running or stopped status.

Job Name and Sync Files

The Job Name is used to tie Job Readers and Job Writers when created separately. The name of the Sync File that holds the change log for the source data starts with the Job Reader Name. When creating a Job Writer, you specify the name of the Job Reader that was used to create the Sync File so that the writer knows which files to read.

Once created, the name of a job cannot be changed since this would break the dependency chain of change logs. You can, however, copy and paste a job to create a new one.