...
General Description
Calendar Types
Calendars
...
are configured as either working days or non-working days:
- . A working day Calendar specifies the business days for which job executions are targeted.
- Non-working days include days for which no jobs should not be executed.
Both calendar types can be combined with precedence on being given to non-working days for any overlapping days.
Frequencies
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 Day; every 2nd last day in every month,
- National Holidays: for a country for the a particular year.
Frequencies can be inclusive and exclusive, allowing a number of approaches to Calender configuration to be adopted in line with legacy procedures.
Calendars as Resources
As resources, Calendars are managed in the Calenders tab of the Resources view of the JOC Cockpit. Resources are objects that can be configured independently of other objects.
...
Note that similar to other Resources, e.g. Locks and Process Classes, Calendars are stored as XML objects in the file system. Calendars are managed with the JOC Cockpit, they are not editable using the JobScheduler Object Editor, JOE. Calendars are added to the inventory in the JobScheduler reporting database.
...
The calendar user interface can be used to define the Run-Times, i.e the days and times at which Orders, Jobs and Schedules are to be run. Here the Run-Time is saved as part of the configuration of the Order, Job or Schedule in XML format in the JobScheduler's live folder. Run-Times set in this manner are persistent - that is, they will not be lost after a restart of the JobScheduler.
Calendar Deployment
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 Calendar Management - Calendar Deployment article.
| Display children header |
|---|
...