지금 지원 담당자와 채팅
지원 담당자와 채팅

Identity Manager 9.0 LTS - Target System Synchronization Reference Guide

Target system synchronization with the Synchronization Editor Working with the Synchronization Editor Basics of target system synchronization Setting up synchronization
Starting the Synchronization Editor Creating a synchronization project Configuring synchronization
Setting up mappings Setting up synchronization workflows Connecting systems Editing the scope Using variables and variable sets Setting up start up configurations Setting up base objects
Overview of schema classes Customizing the synchronization configuration Checking the consistency of the synchronization configuration Activating the synchronization project Defining start up sequences
Running synchronization Synchronization analysis Setting up synchronization with default connectors Updating existing synchronization projects Script library for synchronization projects Additional information for experts Troubleshooting errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples

Specifying a schedule

SynchronizationClosed is started using scheduledClosed process plansClosed. A scheduled process plan is added once a start up configuration is assigned to a schedule. Use schedules to define running times for synchronization.

NOTE: Synchronization can only be started if the synchronization projectClosed is enabled.

IMPORTANT: As long as synchronization is running, you must not start another synchronization for the same target system. This applies especially, if the same synchronization objects would be processed.

If another synchronization is started with another start up configuration, that addresses same target system, it may lead to synchronization error or loss of data. Plan your start times carefully. If possible, specify your start times so that synchronization does not overlap.

To assign an existing schedule to a start up configuration

  1. Select the Configuration > Start up configurations category.
  2. Select a start up configuration in the document view and click Edit.
  3. Select a schedule from the Schedule menu.

    All active schedules assigned to the table JobAutoStart are available for selection.

  4. Click OK.

One Identity Manager specifies a process plan when changes are committed to the One Identity Manager database. This process plan starts the synchronizing process.

NOTE: You can manage existing schedules with DesignerClosed. For more information, see the One Identity Manager Operational Guide.

How to set up schedules

To create a scheduleClosed

  1. Select the Configuration > Start up configurations category.

  2. Select a start up configuration in the document view and click Create schedule.

  3. Edit the schedule properties.

  4. Click OK.

One Identity Manager specifies a process planClosed when changes are committed to the One Identity Manager database. This process plan starts the synchronizingClosed process.

To edit a schedule

  1. In the Synchronization EditorClosed, open the synchronization projectClosed.

  2. Select the Configuration > Start up configurations category.

  3. Select a start up configuration in the document view and click Edit schedule.

  4. Edit the schedule properties.

  5. To enable the schedule, click Activate.

  6. Click OK.
Related topics

Properties of a schedule

Enter the following properties for a scheduleClosed.

Table 65: 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.

Enabled

Specifies whether the schedule is enabled.

NOTE: Only active schedules are run. Active schedules are only run if the QBM | Schedules configuration parameterClosed is set.

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 Synchronization EditorClosed.

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. Other settings may be required depending on the settings.

  • Hourly: The schedule is run at defined intervals of a multiple of hours such as every two hours.

    • Under Repeat every, specify after how many hours the schedule is run again.

    • The starting point is calculated from the rate of occurrence and the interval type.

  • Daily: The schedule is run at specified times in a defined interval of days such as every second day at 6am and 6pm.

    • Under Start time, specify the times to run the schedule.

    • Under Repeat every, specify after how many days the schedule is run again.

  • Weekly: The schedule is run at a defined interval of weeks, on a specific day, at a specified time such as every second week on Monday at 6am and 6pm.

    • Under Start time, specify the times to run the schedule.

    • Under Repeat every, specify after how many weeks the schedule is run again.

    • Specify the set day of the week for running the schedule.

  • Weekly: The schedule is run at a defined interval of months, on a specific day, at a specified time such as every second month on the 1st and the 15th at 6am and 6pm.

    • Under Start time, specify the times to run the schedule.

    • Under Repeat every, specify after how many months the schedule is run again.

    • Specify the days of the month (1st - 31st of the month).

    NOTE: If the Monthly interval type with the sub interval 29, 30 or 31 does not exist in this month, the last day of the month is used.

    Example:

    A schedule that is run on the 31st day of each month is run on April 30th. In February, the schedule is run on the 28th (or 29th in leap year).

  • Yearly: The schedule is run at a defined interval of years, on a specific day, at a specified time such as every year on the 1st, the 100th, and the 200th day at 6am and 6pm.

    • Under Start time, specify the times to run the schedule.

    • Under Repeat every, specify after how many years the schedule is run again.

    • Specify the days of the year (1st - 366th day of the year).

      NOTE: If you select the 366th day of the year, the schedule is only run in leap years.

  • Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday: The schedule is run on a defined day of the week, in specified months, at specified times such as every second Saturday in January and June at 10am.

    • Under Start time, specify the times to run the schedule.

    • Under Repeat every, specify after how many days of the month the schedule is run again. The values 1 to 4, -1 (last day of the week), and -2 (last day but one of the week) are permitted.

    • Specify in which month to run the schedule. The values 1 to 12 are permitted. If the value is empty, the schedule is run each month.

Start time

Fixed start time Enter the time in local format for the chosen time zone. If there is a list of start times, the schedule is started at each of the given times.

Repeat every

Rate of occurrence for running the schedule within the selected time interval.

Setting up base objects

Base objects contain data about the target system to be synchronizedClosed, its system connection, and the synchronization serverClosed. Base objects form the basis for provisioning changes in the target system and synchronizing single objects. A base object is, for example, a specific Active Directory domain from the One Identity Manager database. The connection parameters for logging into a target system are assigned through a variable set. In addition, the synchronization server is declared in the base object.

Base objects are required for provisioning processes and single object synchronization of all the target systems that are connected by default to the One Identity Manager. You cannot normally specify a specific base object for provisioning and single object synchronization with database connectors or the CSV connectorClosed. In this case, assignment of one base table and the synchronization server is sufficient. You can only set up one synchronization projectClosed in the One Identity Manager database per base object.

The base object is used to determine which provisioning workflowClosed is suited to an object in the One Identity Manager database. In order to find the correct workflow for provisioning object modifications or for single object synchronization, you can only set up one synchronization project per base object.

If the synchronization project was creating using a default project templateClosed, a base object is added. You can edit this base object and create more base objects. If the synchronization project was created without a project template, no base object is set up.

NOTE: You cannot add base objects until the synchronization project has been permanently saved in the database.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택