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 changed 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 tasks should run is defined by the import modusmodes. This page describes the different available modusmodes.
Task
...
Mode
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 fast-track task ends up in the task-queue.
| Code Block |
|---|
<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">Database</TaskMode> |
Synchronous
Every data record is written to the database immediately (and by its own). The according fast-track tasks are started by the task handler in the synchronous Synchronous mode, which means, that the task is not set put into the queue but gets is executed immediately.
| Code Block |
|---|
<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">Synchronous</TaskMode> |
None
Standard mode. All imported data records get are written to the database as soon as they are processed by the import (each on its own). There are no fast-track tasks setup, so the changes (for instance ressource resource or role assignments for the newly imported data) will be applied by the according regular tasks.
| Code Block |
|---|
<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">None</TaskMode> |
Bulk
All imported data records get are written to the database as soon as they are processed by the import (each on its own). The according fast-track tasks are collected in bulks of up to bulks of a certain amount of data records (by default 100) 20 records and are set as bulk-fast-track tasks to the queue by the task-handler.
| Code Block |
|---|
<TaskMode xmlns="http://schemas.datacontract.org/2004/07/iTsense.Moving.Backend.Common.TaskScheduler">Bulk</TaskMode> |
Import Configuration
To configure those task modus modes you have to edit the task parameters of the appropriate task. You can do so by changing the parameters in the table moving_appcustomer_900000.taskscheduler_task_params.
...
| Code Block |
|---|
iTsense.Moving.Backend.Common.TaskScheduler.TaskMode, iTsense.Moving.Backend.Common |
For that this entry you can set the appropriate mode:
...
To use the “synchronous” mode, please make sure the appropriate moving_global.config_setting_value has been activated. The following parameters must be set to true (1):
...
Setting ID
...
Value
...
Description
...
42
...
1
...
Enables or disables OnCreate FastTrack Tasks
...
43
...
1
...
Enables or disables OnDelete FastTrack Tasks
...
44
...
1
...
Set the /wiki/spaces/IKB/pages/2165997571 values to true.
You can use the following SQL query to see all import task modes:
| Code Block |
|---|
SELECT d.name, p.serialized_value FROM moving_appcustomer_900000.taskscheduler_task_params as p
join taskscheduler_task_definition as d
on p.taskscheduler_task_definition_id = d.id
where p.type = "iTsense.Moving.Backend.Common.TaskScheduler.TaskMode, iTsense.Moving.Backend.Common"; |