Page Comparison

General

...

Introduction

With each import run several changes could be made to the dateset that is imported. Those changes can lead to subsequent changes with the CoreOne Suite Meta Directory. As an example we can take a changes last name. The change to the Core Identity should probably be reflected in all connected target systems. To do so certain tasks need to calculate those changes and then provision them. How and if those task should run is defined by the import modus. This page describes the different available modus.

Task Modus

Database

Each imported data record is imported immediately (and by its own) into the database. The according fast-track tasks are handled by the task handler, therefore the task ends up in the task-queue.

...

All imported data records get written to the database as soon as they are processed by the import (each on its own). The according fast-track tasks are collected up to bulks of a cretain amount of data records (by default 100) and are set as bulk-fast-track tasks to the queue by the task-handler.

Import Configuration

The configuration is setup in the To configure those task modus you have to edit the task parameters of the appropriate task. You can do so by changing the parameters in the tabl moving_appcustomer_900000.taskscheduler_task_params table, the parameter .

Make sure that you have the following entry configured:

iTsense.Moving.Backend.Common.TaskScheduler.TaskMode, iTsense.Moving.Backend.Common

For that entry you can be set as followsthe appropriate mode:

<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">None</TaskMode>

If the parameter is not set the mode “none” is used.

To use the “synchronous” mode, please make sure the appropriate moving_global.config_setting_value has to be changed in additionbeen activated. The following parameters must be set to true (1):