Chatta subito con l'assistenza
Chat con il supporto

erwin Data Transformation 9.2.3 - User Guide

erwin Data Transformation v9.2.3_User Guide
Getting Started Adapters Configuration Configurations Administrator Tools Running DT on Event Running DT from Cloud Platform Log Viewer Utilities Users, Roles and Security Troubleshooting Information Examples of Workflow Configurations

Execute and Schedule Jobs

Execute and Schedule Jobs

The administrator tools include the scheduler, which is the engine that runs the jobs mainly related to the adapters set up by the user. The scheduler allows the user to schedule a single job; the user may define and schedule job sequences that run the desired jobs with the assigned priority.

According to the type of jobs available and the timing facilities, the user may schedule each single job (or a job sequence) with a certain frequency.

In this window the user can choose to manage the jobs available for all the configurations or to select a specific model configuration to work on the model administration jobs. In particular, selecting from the upper dropdown list:

All Configurations”, the user can schedule the Custom Job (see related section) and the Adapters (CM, WS, File and DB Adapters) which may be used by different models within their specific workflows. In this case, when an adapter is executed by the scheduler engine, an embedded workflow manager will trigger all the workflows using that adapter as its data source to execute

For each of the available Adapters, the user can set up the definition of single job to be scheduled (section “Job Scheduler”)

A specific model configuration name, the user manages the scheduling of the given model administration jobs, as

oModel backup

oMultisource jobs defined within that configuration workflow (thus needed only for those and not available for any other)

          For each of the available model configuration, the user can set up:

oIf it is active or not (checkbox “Active configuration”) – a configuration could exist even if it is not active

oThe definition of single job to be scheduled (section “Job Scheduler”)

oThe definition of each job sequencer (“Job Sequencer”)

Job Scheduler

Job Scheduler

For any kind of job, the user can set the scheduling time for each job after selecting it from the list.

Here are the timing parameters available:

Time Window - gives the opportunity to set a date interval for job execution. The jobs are executed according to the following repetition options and set-up time field.

Repetition by “Minutes” - set the repetition of a job every “xx” minutes (optionally within an hour interval).

Repetition “Hourly” - set the repetition of a job every “xx” hours (12 hours in the example).

Repetition “Daily” - set the repetition of a job every “xx” days (2 days in the example).

Repetition “Weekly” - set the repetition of a job each “day” of the week (Sunday and Monday in the example).

Repetition “Monthly” - the repetition of the job every “xx” (ordinal number) of the month (first day in the example).

Repetition “Once” - schedule the job to run just once, in the specified date and accordingly to the “Start Time” field.

When the user has completed the scheduling configuration, the user can store the scheduling parameters in the DT database by pressing the  button.

When the user presses the “Apply” button, either if they selected a job sequence or a single job, the field “Next Execution Time” (in the Job Sequencer or Job Scheduler respectively) is filled with the next expected time the job will run.

If it is required to unschedule a job, the user has to select it in the list and then press the  button.

If it is required to execute a job or a job sequencer immediately, the user has to select it in the list and then press the  button.

The  button closes the window.

Active Configurations

Active Configurations

If you want the scheduler to execute the jobs at the scheduled time, activate the configuration by checking the  check box. Once activated the check-box changes colour from yellow to green.

 Please note that a configuration does not necessarily need to be activated to schedule its jobs.

The user is allowed to schedule any of the jobs, but the jobs will not be executed if at the execution time the configuration is not checked as “active”.


The “All the configurations” configuration is always active:

Define Jobs Sequences

Define Jobs Sequences


The user may define job sequences, configuring adapters and workflow in a real logical flow; the user may choose between available adapters and related workflows which ones, and which order they belong in the Job Sequence:


Using right/left arrows to include/ exclude an item, and up/down arrow to change their order.

User may include more than one occurrence of adapter, with different workflows, backup and custom jobs.

You can schedule a job using the standard timing parameters: the job will result in the execution of all the adapters belonging to the job sequencer definition and all of the selected workflow, in the configured order.

Please take into consideration that if a workflow included in a sequence is set inactive in the workflow configuration, then it will still belong to the sequence, but it will appear “grayed out” in the sequence definition window, and its execution will be skipped when running the sequence itself.

 Take into account the following internal behavior: when different workflows use source objects exported from the same model:

All the different requests will be aggregated, in terms of different object types, and in terms of filters (which attributes/associations are to be exported; the definition of filters on data).

So, if the objects to be exported, all at once, are typically more than a few thousand, or the filters are conflicting, it’s recommended to replicate the adapter execution, moving workflows in order to make the adapter request more efficient and avoid conflicts:

This is not mandatory and a single rule of workflow aggregation cannot be provided, as it hugely depends on the size/type of required export.

Sometimes, if DT Windows Services are forced to stop, or in case of severe internal error, sequences may enter an inconsistent state, that could stop other jobs from being executed. In that case the administrator may use the “Reset sequences” item in the “Tools” menu (See Utilities).

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione