- 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 using a
crontabfile that is globally available and which 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. JS7 covers all capabilities available with Cron Jobs.
- Migration of Cron jobs is carried out from the JS7 Configuration view in the JOC Cockpit using the Convert → cron operation.
- In the JS7 Configuration View click on the button Convert and then select cron.
- A modal window will open.
- Add the crontab file (via Drag&Drop or using the choose files for upload button)
- Open 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.
- Specify whether the cron file is a system crontab file or a user crontab file.
- System crontab files contain an account which will be used to run the script.
- Genreally user crontab files will be executed in the users context and therefore the crontab file will not contain an account name.
- If required enter the Audit credentials.
- Click the Button Convert to finish the process.
- A new Workflow and a Schedule will be generated in the target folder for each cron line in the uploaded crontab file.
- 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).
Manual Post Processing
- 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 has been correctly converted to the job.
- As all the generated configurations have default names users should rename the configurations according to their needs.