Ident2ODBC

Workflow for Export from LDAP to ODBC

Ident2ODBC exports data from the Identity Store to an ODBC target. You use it when a database expects a scheduled feed from DirX Identity instead of reading the Identity Store directly.

The workflow separates data selection from database loading. MetaCP prepares the export from the Identity Store, and ODBCImport writes the transferred result to the ODBC target.

The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.

At a Glance

Name

Ident2ODBC

Category

Source Scheduled / ODBC

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

LDAP-ODBC

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Source Scheduled/ODBC/Ident2ODBC

Prerequisites

  • An agent that can run MetaCP.

  • An agent that can run ODBCImport.

  • Access to the Identity Store for the export step and an ODBC target for the import step.

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident2ODBC_metaCP

Export from LDAP

MetaCP

start activity

2

Ident2ODBC_ODBCImport

Import to ODBC

ODBCImport

Ident2ODBC_metaCP

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident2ODBC_metaCP

Ident2ODBC_metaCP

MetaCP

Full Export

Ident2ODBC

OutData

Ident2ODBC_ODBCImport

Ident2ODBC_ODBCImport

ODBCImport

Full Import

InData

Ident2ODBC

Configuration Parameters

Table 1. Parameters of job Ident2ODBC_metaCP
Parameter Default value

debug_trace

0

delta_mode

delta-or-full

delta_on

1

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

trace_level

1

trace_recordcount

0
Table 2. Parameters of job Ident2ODBC_ODBCImport
Parameter Default value

8bit

TRUE

datahash

4

delta_mode

full

delta_on

0

maxtracefiles

100

trace

0

traceflow

0

tracelevel

W S FS CA Stats

A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent with one input and one output channel. Agents exchange their data through files or directly through the meta controller, so a typical workflow consists of an export activity that writes the data of the connected system and an import activity that maps and loads that data into the Identity Store.

You start these workflows manually from the Identity Manager or attach them to a schedule.

The workflow has two activities. Ident2ODBC_metaCP exports the data set from the Identity Store, and Ident2ODBC_ODBCImport receives that data through the internal OutData / InData handover and writes it to the database.

If the export step fails, the import step does not run. If the import step fails, the workflow stops with that error after the handover has already been created.

Operation

  1. Ident2ODBC_metaCP reads the configured objects from the Identity Store and prepares the transfer data for the workflow.

  2. Because delta_on is enabled with delta_mode set to delta-or-full, you can use this first step for delta exports as well as full exports.

  3. Ident2ODBC_ODBCImport reads the transferred data from InData and writes it to the ODBC target in one full import pass.