Skybot Scheduler is a modern job scheduling program that offers tried-and-true Java technology, its own database, and a Web-based interface that you can use anywhere with just a browser.
Skybot Scheduler is so light, fast, portable, and easy-to-use, there’s no need to install software on your desktop. Skybot Scheduler installs on your Windows, UNIX, or Linux batch scheduling system with a self-contained HTTP server and database. All you do is install the software on each server you want Skybot Scheduler to manage and use your favorite Web browser to view and manage your entire job schedule.
For step-by-step installation instructions, watch the following videos: Installing Skybot Scheduler and Installing Agents.
The host server on which you install Skybot Scheduler is called the Enterprise Server. It contains the database that stores your batch job management information and an HTTP server that sends information to your browser. The Skybot Scheduler Enterprise Server supports or requires the following software and hardware:
- Windows Server 2003, Server 2008, Server 2008 R2 (Windows 7 Server)
- AIX 5.3, 6.1, 7.1
- RedHat Enterprise Linux 5
- RedHat Enterprise Linux 6
- Suse Enterprise Linux 10
- Suse Enterprise Linux 11
- Ubuntu Linux 10.04
- Java 1.6
Hardware
- 2 GB RAM (4 GB recommended)
- 160 GB hard drive
Skybot Scheduler for Windows - 118.98 MB
Skybot Scheduler for AIX and Linux - 110.60 MB
Skybot Scheduler Agent for Windows - 31.60 MB
Skybot Scheduler Agent for Linux & UNIX - 7.91 MB
Yes! Skybot Scheduler makes it easy to run your cron scripts as part of your enterprise. You can either import your crontabs and convert them into Skybot Scheduler jobs or include them in your Skybot Scheduler job commands.
Crontab files can normally be found here:
/var/spool/cron/crontabs/
or
/var/spool/cron/crontabs/username
For step-by-step instructions, watch our Importing Cron Jobs video.
Firefox 3.5 (and above)
Google Chrome 12.0 (and above)
- Point a web browser to the following URL: https://xxx.xxx.xxx.xxx:8443/ where xxx.xxx.xxx.xxx is the IP address of your Enterprise Server.
- Point a web browser to the following URL: https://system_name:8443/
- The URL is saved as part of the start menu shortcut when it is installed.
- You can see the URL in the properties for the target.
Agent Environments store the User Account, Password, default directory when a process starts, and any Environment Variables needed by the job when it runs. Create an Agent Environment for each Agent or each application. When you are scheduling the job:
- Select Enabled on the Shared Agent Environment
- Choose an Agent Environment from the drop-down list to add to the job.
- There is no need to enter the user and password for each job.
If the password or user changes, upate the information on the Agent Environment and every job that uses that Agent Environment is updated automatically.
This is a two-step process:
1. Set up an Agent Event Monitor (Scheduling Object) for a file add:
.jpg)
2. Create a job with the Agent Event as a Prerequisite:
.jpg)
When creating the job select Schedule Type – Day of Week. Select Add Schedule, then Weekly. Select Last Week and check Fri. No special calendar is needed to schedule your jobs for specific days of the week or month.
When creating the job select Schedule Type – Day of Period. Select Add Schedule, then Run on day 1. Under Counting days, select from the end (backwards). Now your job will run on the last day of the month. No special calendar is needed to schedule your jobs for specific days of the week or month.
Watch our quick video tutorial for more information: Creating a Job Monitor.
Once your job is created, righ-click the job, point to Edit Job and select Job Monitors.
- Select Job Overrun and enter the Maximum Duration.
- Enter the user to notify or a pre-defined Notification List.
- You also can End the Job, if desired.
.jpg)
Watch our quick video tutorial for more information: Creating a Job Monitor.
Once your job is created, righ-click the job, point to Edit Job, and select Status Notification. Select Failed Status Notification and add your User or a pre-defined Notification List.
Scheduling Objects are created to help simplify the maintenance of your schedule. Each of the items in the Scheduling Objects area are created once and used multiple times.
For example, create a Command Set if you will be running the same list of commands on multiple Agents. This is helpful especially if there are multiple commands or scripts that are run within one Skybot Scheduler job.
This will eliminate typographical errors from your command line. Also, if the commands change, just change the Command Set and every job that runs that Set is automatically updated.
Calendars are used for two reasons in Skybot Scheduler.
1. Schedule exceptions based on holidays or non-working days.
- If you want to automate schedule exceptions on holidays or other non-working days of the year, simply add them to the Standard Calendar included in the base product.
- You can create multiple calendars for specific holiday exceptions, such as different countries or different holiday exceptions for specific groups of jobs.
2. Fiscal period end dates for monthly job schedules.
- If you run production jobs on fiscal period cycles instead of regular monthly cycles, create a fiscal calendar with your period end dates selected.
- When scheduling a job, add your fiscal calendar to the job. When you select to run on the last day of the month, Skybot Scheduler will look to that calendar for the proper dates.
