JS7 - Migration of Cron Jobs

Introduction

Cron is a service daemon available with most Unix operating systems.
- Cron offers minimal scheduling capabilities by executing an operating system command or script at a given point in time.
- Cron jobs are configured from a crontab file that is globally available and that can be made available per operating system account.
- Cron does not consider any job dependencies, job execution results, job history and resource consumption when executing jobs.
Cron is frequently used as an entry level to job scheduling. The JS7 covers any capabilities available with Cron Jobs.
Migration of Cron jobs is offered from the JS7 Configuration view with the Convert → cron operation.

In the JS7 Configuration View click on the button Convert and then select cron.
A modal window open.
Add the crontab file (via Drag&Drop or by the choose files for upload button)
Enter the folder where the generated Workflows and Schedules should be stored.
Enter the calendar name of the Calendar which should be assigned to the Schedules.
Choose the Agent to run the job.
Choose, if the the cron file is a system crontab file or a user crontab file.
- System crontab files contain an account the script will be run by.
- Genreally user crontab files will be executed in the users context, therefor the crontab file doe not contain an account name.
- System crontab
```
5 12 * * * root /path_to_file/file.sh >> /path_to_file/file.log 2>&1
```
- Users crontab
```
5 12 * * * /path_to_file/file.sh >> /path_to_file/file.log 2>&1
```
If required enter the Audit credentials.
Click the Button Convert to finish the process.
For each cron line in the uploaded crontab file a new Workflow and a Schedule will be generated in the target folder.

A workflow will be generated with one Job containing an ExecutableScript of type ScriptExecutable with the command: /path_to_file/file.sh >> /path_to_file/file.log 2>&1
A schedule will be generated with the assigned calendar.
The schedule will contain the period(s) and include frequencies based on the cron definition (run at 12:05 each day).

All workflows will be generated with the name workflow_cron- followed by an ascending number.
All schedules will be generate with the name schedule_cron- followed by an ascending number.
The user should make sure that the script is correctly converted to the job.
As all the generated configurations have default names users should rename the configurations to their needs.