The screen displays all the schedules for jobs, probes, and processes. The following details are supplied:

• The name of the schedule.
• The type of item being scheduled: a probe In the Administration Console architecture, a mechanism which allows for the execution of predefined queries and for the comparison of the results of those queries against pre-configured targets. Probes can be reviewed and managed via the Admin Console., process or job.
• The reference for the schedule, which is the name of the probe, process or job to which the schedule applies.
• A text description of the schedule, for example, At 04:00, only on Monday, Tuesday, Wednesday, Thursday and Friday.
• The date and time when the item will next be run, according to the schedule.
• Whether the schedule is currently active.

You can also drill-down into individual schedules for more details, such as notes, schedule settings and any exclusion calendars, outages, and pre- or post-requisites that apply.

When you create a schedule, you need to configure the following:

• The name, and type of the schedule.
• The reference for the item scheduled (the name of the probe, job or process).
• Any notes to help console users understand the schedule.
• Whether the schedule is active and the date from which it is active.
• The schedule itself: the days and times that the item is run, according to the schedule. The schedule options are very flexible, allowing you to easily configure daily, weekly, monthly, and yearly schedules. As well as schedules that run items every specified number of minutes or hours.

  The following table describes the schedule options and when to use them:

  Schedule Option	Description
  Daily
  Every <number> day(s) at	Use option to schedule the item to run every specified number of days each week at a certain time. For example: Every 1 day(s) at 04 30 00.
  Every week day (Monday through Friday) at <HH><MM><SS>	Use this option to schedule the item to run every week day at a certain time. For example: Every week day (Monday through Friday) at 23 59 00.
  Weekly
  Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday	Choose the weekly schedule when you want the item to run every week on a specific day or days at a set time - for example, every Monday and Friday at 13:00:00.
  Start time	Set the start time in hours, minutes and seconds.
  Monthly
  On the <number> of every <number> month(s) at <HH><MM><SS>	Choose this option when you want the item to run on a specific day of the month every specified number of months at a certain time, for example on the last day of every second month at noon. For example: On the 1st Day of every 1 month(s) at 01 00 00.
  On the <number> <day> of every <number> month(s) at <HH><MM><SS>	Use this option when you want the item to run on a specified day of the week every specified number of months at a certain time, for example every second Wednesday every month at midnight. For example: On the First Monday of every 1 month(s) at 23 59 59.
  Yearly
  Every <month> on the <numbered day> at <HH><MM><SS>.	Select this option to schedule an item to run every year on a certain day (first, last, 15th etc.) of a specified month at a set time.
  On the <number> <day of the week> of <month> at <HH><MM><SS>	Select this option to run every year on a certain day of the week (last Friday, first Monday etc.) of a specified month at a set time. For example: On the First Monday of January at 01 30 00.
  Minutes
  Every <number> minute(s) on second <number>	Use this option to run an item every specified number of minutes, for example every 10 minutes.
  Hourly
  Every <number> hour(s) on minute <number> and second <number>	Use this option to schedule an item to run every specified number of hours, for example every 2 hours on minute 1 and second 30.
  Advanced
  Cron expression	You can enter a cron expression A cron expression is a string consisting of fields separated by white space. The string represents a set of times that make a schedule for a routine. for a schedule. Tip: A link to a cron expression tutorial is provided in the console.

• Any exclusion calendars associated with the schedule.

  You can configure exclusion calendars to prevent items running on particular days such as weekends and public holidays. Exclusion calendars must be added to a schedule to become effective. In the Exclusion Calendar section, you can view the calendars that apply to a schedule and add calendars to the schedule.

• Any individual outages included in the schedule.

  You can add outages to a schedules - time periods where the scheduled item will not run, for example during deployments, upgrades or maintenance.

• Any pre- or post-requisites required by the schedule.

  Some jobs or processes may be dependent on the output or result of previous jobs, or must be run in a particular sequence. You can add prerequisites to a schedule to ensure that the scheduled item will not be run unless the requisite input is available or operation is complete. Similarly, you can configure post-requisites to ensure that a scheduled item has run correctly or that jobs and processes dependant on the scheduled item run in the required sequence.

  • For pre-requisites, you can select probes that must be run.
  • For post-requisites, you can select probes, jobs, or processes.