Article Copy of JobScheduler Documentation. To be reworked.
JobScheduler Calendars provide a sophisticated method of specifying the days on which scheduling events are to occur. Calendars allow similar levels of complexity to that provided by other enterprise level workload automation applications thereby easing migration to JobScheduler.
Calendars are lists of days on which Orders, Jobs and Schedules are planned to be executed. Calendars can be defined as either working days or non-working days and can be both combined and reused. An example of Calendar combination would be one Calendar specifying that a normal working week contained the five days Monday to Friday being used in combination with a Calendar specifying the public holidays in the current year. Reuse allows, for example, a Business Day Calender to be defined once and then specified as required.
Calendars are configured for either working days or non-working days:
- A working day Calendar specifies the business days for which workflow executions are targeted.
- Non-working days include days for which workflows should not be executed.
Both calendar types can be combined with precedence being given to non-working days for any overlapping days.
Handling of days in both types of Calendars is simplified through the use of Frequencies. Typical Frequencies include:
- Weekdays: Monday to Friday, every week,
- Recurring Days: every 2nd last day in every month,
- National Holidays: for a country for the particular year.
Frequencies can be inclusive and exclusive, allowing a number of approaches to Calendar configuration to be adopted in line with legacy procedures.
Calendars as Resources
Calendars are managed in the Calendars node of the Configuration -> Inventory view of the JOC Cockpit. In addition, Calendars are visible with the Resources -> Calendars view.
Once they have been configured, one or more Calendars can be assigned to Schedules as required.
Assigned Calendars can also be modified with modifications being applied to all Schedules that use the respective Calendar.
Calendars for Schedules
The Calendar user interface can be used to define the Run-Times, i.e. the days and times for which Orders are to be run. Here the Run-Time is saved as part of the configuration of the Schedule that creates orders,
Export and import functions allow the bulk deployment of Calendars, for example, when updating non-working day information on a production system.
The Calendar deployment procedure is described in the JS7 - Calendar Deployment article.