HOW TO: Use Data Quality Runtime plans with a schedule
Solution:
As a command line application Data Quality Runtime can be called from any scheduler that has the ability to run command line executables.
Data Quality Runtime has been successfully scheduled using the Windows Task Scheduler, Unix Cron, BMC Control and Informatica Workflow Manager amongst others.
Scheduling Data Quality Runtime jobs on Windows
The following steps detail how to schedule a plan, Profile.xml, to execute using Data Quality Runtime on Windows.
1.Create a batch file called QualityReport.bat and add the command you would normally run.
Example:
C:\Program Files\Athanor\bin\Athanor-Rt.exe -f C:\Plans\Profile.xml
2.Go to Start > Settings > Control Panel > Scheduled Tasks > Add Scheduled Tasks.
3.Use the Scheduled Task Wizard to select the QualityReport.bat file, define when and how often it should run.
4.Enter "Quality Report" for the name of the Scheduled Task.
Similar scheduling can be achieved using any other scheduler than has the ability to run command line executables.
To add pre and post task operations you can add additional steps to the batch file or add new tasks to the scheduler.
Scheduling Data Quality Runtime jobs on Unix/Linux
The following steps detail how to schedule a plan, Profile.xml on a Solaris machine using the cron scheduler.
Similar steps can be used on most popular Unix/Linux systems.
1.Create a shell script called QualityReport.sh and add the command you
would normally run to execute the plan.
Example:
$HOME/athanor/bin/athanor-rt -f $HOME/Plans/Profile.xml
2.Run the batch file to ensure it works as expected.
3.Create a new scheduled task using the following shell command:
crontab -e"
Example:
The following task runs QualityReport.sh and logs standard and error messages to a file called QualityReport.log in the tmp directory:
For more information on using cron and crontab use the "man crontab" and "man cron" commands or contact your system administrator.
Troubleshooting
If the Windows Scheduler warns that it cannot find the file specified it may be because the path you provided is incorrect or contains spaces. Check the path by running it from the command line and if spaces are present surround the path with quotation marks (for example, C:\My Tasks\QualityReport.bat becomes "C:\my tasks\QualityReport.bat").
Also, remember that the error code returned by a windows batch file or unix script will always be that of the last command executed by that file.
If the script fails to run on Unix it may be because the script itself is not executable. To change this run the command chmod u+x "scriptname" or contact your local system administrator.
