Regular testing of company policies is managed through schedules. In the default installation of One Identity Manager, the "Policy check" schedule is assigned to every new company policy. This schedule generates a processing task at regular intervals for the DBQueue Processor for every company policy. You can configure your own schedule to check policies on a cycle which suits your requirements. Ensure that the schedules are assigned to the policies.
To edit schedules
- Select the Company Policies | Basic configuration data | Schedules category.
The result list shows all schedules configured for the QERPolicy table.
- Select a schedule in the result list and run the Change master data task.
– OR –
Click
in the result list.
- Edit the schedule’s master data.
- Save the changes.
Enter the following properties for a schedule.
|
Property |
Meaning |
|---|---|
|
Name |
Schedule ID. Translate the given text using the |
|
Description |
Detailed description of the schedule. Translate the given text using the |
|
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 Manager. |
|
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.
|
|
Occurs |
Interval in which the task is run. Permitted interval types are 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. |
button.