For detailed information about editing schedules in the Manager, refer to the administration guides for the modules.
NOTE:
- Before you start a schedule manually, check whether other processes will be executed as a result, that also need to be preprocessed by One Identity Manager.
- The last execution time is not updated when the schedule is started manually.
To start a schedule in the Designer immediately
- In the Designer, select the Base data | General | Schedules category.
- Select the schedule.
- Click Start.
- Confirm the security prompt with Yes.
For detailed information about editing schedules in the Manager, refer to the administration guides for the modules.
To edit a schedule in the Designer
- In the Designer, select the Base data | General | Schedules category.
- Select the schedule.
- OR -
Select Object | New to create a new schedule.
- Edit the schedule’s master data.
- Select Database | Save to database and click Save.
Detailed information about this topic
Enter the following properties for a schedule.
Table 19: Schedule properties
|
Name |
Schedule ID. Translate the given text using the  button. |
|
Description |
Detailed description of the schedule. Translate the given text using the button. |
|
Table |
Table whose data can be used by the schedule. |
|
Enabled |
Specifies whether the schedule is enabled or not.
NOTE: Only active schedules are run. |
|
Time zones |
Unique identifier for the time zone that is used for running the schedule. Choose between Universal Time Code or one of the time zones in the menu.
NOTE:
When you add a new schedule, the time zone is preset to that of the client from which you started the Designer. |
|
Start (date) |
The day on which the schedule should be run for the first time. If this day conflicts with the defined interval type, the first run is on the next available day based on the start date. |
|
Validity period |
Period within which the schedule is run.
-
If the schedule will be run for an unlimited period, select the Unlimited duration option.
-
To set a validity period, select the Limited duration option and enter the day the schedule will be run for the last time in End (date). |
|
Occurs |
Interval in which the task is run. Permitted interval types are Every minute, Hourly, Daily, Weekly, Monthly, and Yearly.
For the Weekly interval type, specify the precise weekday. For the Monthly interval type, specify the day of the month (1st to 31st day of the month). For the Yearly interval type, specify the day of the year (1st to 366th day of the year).
NOTE: If the schedule is not going to be run until next month because the interval type is Monthly with sub-interval 29, 30, or 31, the last day of the current month is used.
Example:
A schedule that is run on the 31st day of each month is run on 30th April. In February, the schedule is run on the 28th (or 29th in leap year).
Schedules with the interval type Yearly with sub interval 366 are only run in leap year. |
|
Start time |
Fixed start type for the Daily, Weekly, Monthly, and Yearly interval types. Enter the time in local format for the chosen time zone.
For the interval types Every minute and Hourly, the start time is calculated from the rate of occurrence and the interval type. |
|
Repeat every |
Rate of occurrence for running the schedule within the selected time interval. For the Weekly interval type, select at least one weekday. |
|
Last planned run/Next planned run |
Execution time calculated by the DBQueue Processor. Execution times are recalculated whilst the schedule is running. The time of the next run is calculated from the interval type, rate of occurrence, and the start time.
NOTE: One Identity Manager provides the start information in the time zone of the client where the program was started. Changes due to daylight saving are taken into account. |
The database schedule QBM_PWatchDog on <database> verifies the schedules that need to be run and their start times, at regular intervals. When the database scheduler is run, all tasks are found that are within the valid time period and are enabled. A task is queued in the DBQueue for each schedule to be run. Then the time for the next scheduled run is calculated through the database schedule and entered in the schedule.
For tasks with the Every minute and Hourly interval types, the next planned time of execution will be determined from the time at which the database schedule runs, the specified time zone and the execution rate. For schedules with the interval types Daily, Weekly, Monthly and Yearly, the next planned time of execution will be determined from the current day, the specified subinterval and the start time within the specified time zone.
Behavior of new schedules
When a new active schedule is added, the next scheduled run is calculated immediately. This is calculated on the basis on the start date or the current date of the next scheduled run. The time between runs is not taken into account.
The task is run if the time of execution has been reached. When the next scheduled run is calculated, this time the interval will be taken into account.
Behavior of modified schedules
If a schedule changes, the next scheduled run is calculated immediately. This is calculated on the basis on the start date or the current date of the next scheduled run. The time between runs is not taken into account.
The task is run if the execution time has been reached. When the next scheduled run is calculated, this time the interval will be taken into account.
