The holidays are loaded into the database during the schema installation and do not normally have to be customized.
To display a holiday
To display a country's holidays, select the category Base Data | Localization | Country | <country name> | Public holidays in the Designer.
- OR -
To display a state's holidays, select the category Base Data | Localization | Country | <country name> | States | <state name> | Public holidays in the Designer.
Property | Description |
---|---|
Date (ISO Format) |
The date of the public holiday is entered in ISO format, for example "yyyy-mm-dd" where: yyyy - year, 4-digit mm - month, 2-digit dd - day, 2-digit |
Public holiday name | Name of the holiday. |
Public holiday name (national language) |
Name of the holiday in the national language using the national script.
|
Country/State | Name of the country or state of the holiday. |
Processing status | The process state is used for creating custom configuration packages. |
Frequently, you need to run processes and calculation tasks at specified time intervals. To make this possible, you can define schedules in the One Identity Manager. Schedules are required, for example, for scheduled execution of processes within process handling or for different calculation tasks within One Identity Manager. A schedule can be in control of several tasks. Execution times are configured in a schedule for the tasks to be executed.
|
NOTE: There are already schedules defined in the default One Identity Manager installation. Configure these according to your custom requirements. |
|
NOTE: When a schedule is executed, all tasks assigned to the schedule are executed. Before you use a schedule on a repeated basis, check the effects of the process handling. |
To edit schedules
- OR -
Create a new schedule with the menu item Object | New.
Property | Meaning | ||
---|---|---|---|
Name |
Schedule ID. Translate the given text using the | ||
Description |
Detailed description of the schedule. Translate the given text using the | ||
Table |
Table whose data can be used by the schedule. | ||
Enabled |
Specifies whether the schedule is enabled or not.
| ||
Time zones |
Unique identifier for the time zone that is used for executing the schedule. Select either "Universal Time Code" or one of the time zones.
| ||
Start (date) |
The day on which the schedule should be run for the first time. | ||
Validity period |
Period within which the schedule is executed.
| ||
Occurs |
Interval in which the task is executed. Valid interval types are Specify the exact weekday for the interval type "Weekly". Specify the day of the month (1st - 31st) for the interval type "Monthly". Specify the day of the year (1 - 366) for the interval type "Yearly".
| ||
Start time |
Fixed start time for the interval types "daily", "weekly", "monthly" and "yearly". Enter the time in local format for the chosen time zone. The start time for | ||
Repeat every |
Rate of occurrence for executing the schedule within the selected time interval. Select at least one weekday for the interval type "Weekly". | ||
Last planned run/Next planned run |
Execution time calculated by the DBQueue Processor. They are recalculated each time a schedule is run. The time of the next run is calculated from the interval type, rate of occurrence and the start time.
|
|
NOTE: Use the Start button to execute the schedule immediately. Take note:
|
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 interval types "minutely" or "hourly", the next schedule start time is calculated from the database schedule run time, the time zone and the rate of execution. The next execution time for tasks with the interval types "Daily", "Weekly", "Monthly" and "Yearly" are calculated from the given sub-interval and the start time.
Run a schedule every 15 minutes.
Current time |
Monday, 7/14/2014, 8:59 AM |
Interval type |
Every minute |
Interval |
15 |
The next time the database schedule is run at 9 am the schedule is only preset because the execution time is empty. The following run of the database schedule at 9:01 am determines the next scheduled run.
This results in the follow scenario:
Last scheduled run |
1/2/1900, 00:00:00 AM |
Next scheduled run |
7/14/2014, 09:16:00 AM |
This task is run for the first time the next time the database schedule runs at 9:16 am. The next scheduled run is calculated as follows:
Last scheduled run |
7/14/2014, 09:16:00 AM |
Next scheduled run |
7/14/2014, 09:31:00 AM |
Run a schedule once a week on Wednesdays at 12 pm.
Current time |
Monday, 7/14/2014, 8:59 AM |
Interval type |
Weekly |
Interval |
1 |
Sub interval |
Wednesday |
Start time |
12:00 PM |
The next time the database schedule is run at 9 am the schedule is only preset because the execution time is empty. The following run of the database schedule at 9:01 am determines the next scheduled run. The next possible execution time is determined based on the current date (07/14/2014) without taking the interval into account.
This results in the follow scenario after the database schedule has run:
Last scheduled run |
1/2/1900, 00:00:00 AM |
Next scheduled run |
7/16/2014, 12:00:00 PM |
The task is run for the first time when the database schedule is executed on 07/16/2014 at 12 pm. The next scheduled run is calculated as follows:
Last scheduled run |
7/16/2014, 12:00:00 PM |
Next scheduled run |
7/23/2014, 12:00:00 PM |
Run a schedule every quarter on the 15th day of the month at 6pm.
Current time |
Monday, 7/14/2014, 8:59 AM |
Interval type |
Monthly |
Interval |
3 |
Sub interval |
15 |
Start time |
6 PM |
The next time the database schedule is run at 9 am the schedule is only preset because the execution time is empty. The following run of the database schedule at 9:01 am determines the next scheduled run. The next possible execution time is determined based on the current date (07/14/2014) without taking the interval into account.
This results in the follow scenario after the database schedule has run:
Last scheduled run |
1/2/1900. 00:00:00 AM |
Next scheduled run |
8/15/2014, 18:00:00 PM |
The task is run for the first time when the database schedule is executed on 08/15/2014 at 6 pm. The next scheduled run is calculated as follows:
Last scheduled run |
8/15/2014, 18:00:00 PM |
Next scheduled run |
11/15/2014, 18:00:00 PM |
provides you with support for creating complex password policies, for example, for system user passwords, the employees' central password as well as passwords for individual target systems. Password polices apply not only when the user enters a password but also when random passwords are generated.
Predefined password policies are supplied with the default installation that you can user or customize if required. You can also define your own password policies.
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy