Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

Excerpt Include
Calendars
Calendars
nopaneltrue

Description

General Description

Calendar Types

Calendars are configured as for either working days or non-working days:

  • A working day Calendar specifies the business days for which job workflow executions are targeted.
  • Non-working days include days for which jobs workflows should not be executed.

Both calendar types can be combined with precedence 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; Days: 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 Calendar configuration to be adopted in line with legacy procedures.

Calendars as Resources

As resources, Calendars are managed in the Calenders tab Calendars node of the Resources Configuration -> Inventory view of the JOC Cockpit. Resources are objects that can be configured independently of other objectsIn addition, Calendars are visible with the Resources -> Calendars view.

Once they have been configured, one or more Calendars can be assigned to Orders and Jobs to Schedules as required.

Assigned Calendars can also be modified with modifications being applied to all objects Schedules that use the respective Calendar.Note that similar to other Resources, e.g. Locks and Process Classes,

Calendars

...

for

...

Schedules

The calendar Calendar user interface can be used to define the Run-Times, i.e. the days and times at for 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. that creates orders,

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 xCalendar Management JS7 - Calendar Deployment article.

...