Chat now with support
Chat with Support

Identity Manager 8.0 - Configuration Guide

One Identity Manager Software Architecture Working with the Designer Customizing the One Identity Manager Default Configuration Checking Data Consistency Compiling a One Identity Manager Database Working with Change Labels Basic System Configuration Data
One Identity Manager Authentication Module Database Connection Data Configuration Parameters for System Configuration Setting up the Mail Notification System Enabling More Languages for Displaying and Maintaining Data Displaying Country Information Setting Up and Configuring Schedules Password Policies in One Identity Manager Reloading Changes Dynamically TimeTrace Databases Machine Roles and Server Functions Files for Software Update Operating Systems in Use System Configuration Reports Using Predefined Database Queries Managing Custom Database Objects within a Database
The One Identity Manager Data Model Granting One Identity Manager Schema Permissions Working with the User Interface
Object definitions for the User Interface User Interface Navigation Forms for the User Interface Statistics in the One Identity Manager Extending the Launchpad Task Definitions for the User Interface Applications for Configuring the User Interface Icons and Images for Configuring the User Interface Language Dependent Data Representation
Process Orchestration in One Identity Manager
Declaring the Job Server One Identity Manager Service Configuration Handling Processes in the One Identity Manager
Tracking Changes with Process Monitoring Conditional Compilation using Preprocessor Conditions One Identity Manager Scripts Maintaining Mail Templates Reports in the One Identity Manager Custom schema extensions Transporting One Identity Manager Schema Customizations Importing Data Web Service Integration SOAP Web Service One Identity Manager as SPML Provisioning Service Provider Searching for Errors in the One Identity Manager Processing DBQueue Tasks One Identity Manager Configuration Files

Modifying Public Holidays

The holidays are loaded into the database during the schema installation and do not normally have to be customized.

To display a holiday

  1. 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.

Table 62: Public Holiday Properties
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.
Related Topics

Setting Up and Configuring Schedules

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

  1. Select the category Base Data | General | Schedules in the Designer.
  2. Select the schedule.

    - OR -

    Create a new schedule with the menu item Object | New.

  3. Edit the schedule’s master data.
Table 63: Schedule Properties
Property Meaning

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 executed.

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.

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.

Validity period

Period within which the schedule is executed.

  • If the schedule will be run for an unlimited period, select the option Unlimited duration.
  • To set a validity period, select the option Limited duration and enter the day the schedule will be run for the last time in End (date).

Occurs

Interval in which the task is executed. Valid interval types are "Every minute", "Hourly", "Daily", "Weekly", "Monthly" and "Yearly".

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".

NOTE: Schedules that have the sub-interval "31" and interval type "monthly" are run on the "31st of the month". The task is, therefore, only run in months with 31 days. The same is true of the interval type "yearly" and the sub-interval "366".

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 interval types "Every minute" and "Hourly" is calculated from the rate of occurrence and the interval type.

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: The 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.

NOTE: Use the Start button to execute the schedule immediately. Take note:

  • The last execution time is not updated when the schedule is started manually.
  • Before you start a schedule manually, check whether other processes will be executed as a result, that also need to be preprocessed by the One Identity Manager.
Related Topics

Calculating the Execution Time

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.

Behavior of New Schedules
  • The execution times for a new schedule are initially empty.
  • Only the last scheduled run (date "01/02/1900") and the next scheduled run (date "12/30/1899") are entered the first time the database schedule is executed after a new schedule has been set up. The task is not executed.
  • The next time the database schedule is executed, the next possible execution time (without taking the interval into account) is found. The task is not executed.
  • 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.
Behavior of Modified Schedules
  • When a schedule is modified, the next scheduled run field is cleared.
  • The first time the database schedule is executed after the modifications, the next possible execution time (without taking the interval into account) is found. The task is not executed.
  • 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.
Example 1

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

Example 2

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

Example 3

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

Password Policies in One Identity Manager

Password Policies in One Identity Manager

One Identity Manager 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.

Detailed information about this topic
Related Documents