ODBC2Ident

Workflow for Export from ODBC and Import to LDAP

ODBC2Ident imports data from an ODBC-accessible source into the Identity Store. You use it when authoritative source data sits in a relational database and you want a scheduled load into DirX Identity.

The workflow separates extraction from import. ODBCExport reads the database and passes the result to MetaCP, which applies the import into the Identity Store.

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

ODBC2Ident

Category

Source Scheduled / ODBC

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

ODBC-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Source Scheduled/ODBC/ODBC2Ident

Prerequisites

  • An agent that can run ODBCExport.

  • An agent that can run MetaCP.

  • An ODBC source for the ODBC2Ident export step and access to the Identity Store for the import step.

Workflow and Activities

Step Activity Description Agent Runs after

1

ODBC2Ident_ODBCExport

Export from ODBC

ODBCExport

start activity

2

ODBC2Ident_metaCP

Import to LDAP

MetaCP

ODBC2Ident_ODBCExport

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

ODBC2Ident_ODBCExport

ODBC2Ident_ODBCExport

ODBCExport

Full Export

ODBC2Ident

OutData

ODBC2Ident_metaCP

ODBC2Ident_metaCP

MetaCP

Full Export

InData

ODBC2Ident

Configuration Parameters

Table 1. Parameters of job ODBC2Ident_ODBCExport
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
Table 2. Parameters of job ODBC2Ident_metaCP
Parameter Default value

debug_trace

0

delta_mode

full

delta_on

0

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

min_source_entries

0

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

trace_level

1

trace_recordcount

0

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 runs in two activities. ODBC2Ident_ODBCExport extracts the source data and hands it over through the internal OutData / InData transfer to ODBC2Ident_metaCP, which imports the data into the Identity Store.

If the export step fails, the import step does not start. If the import step fails, the workflow ends with that error and no later recovery activity runs.

Operation

  1. ODBC2Ident_ODBCExport connects to the ODBC source through ODBC2Ident and performs a full export of the selected source data.

  2. The exported data is passed to ODBC2Ident_metaCP through the workflow’s internal transfer channels.

  3. ODBC2Ident_metaCP imports that data into the Identity Store. Because both jobs run in full mode, each execution processes the complete selected source set.