JDBC2Ident

Workflow for Export from a JDBC database and Import into LDAP

JDBC2Ident loads data from a JDBC-accessible database into the Identity Store. You use it when authoritative source data stays in relational tables and you want DirX Identity to import that data on a schedule.

The workflow splits the work between JDBCAgent and MetaCP. JDBCAgent extracts the database data first, and MetaCP then imports the handover data into the Identity Store as a full load.

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

JDBC2Ident

Category

Source Scheduled / JDBC

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

JDBC-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Source Scheduled/JDBC/JDBC2Ident

Prerequisites

  • JDBCAgent is installed and can connect to the source JDBC database.

  • MetaCP is available and can reach the Identity Store.

  • The channels JDBC2Ident, OutData, and InData are configured for the database extract and the handover between the two jobs.

Workflow and Activities

Step Activity Description Agent Runs after

1

JDBC2Ident_JDBCAgent

Export from a JDBC database

JDBCAgent

start activity

2

JDBC2Ident_MetaCP

Import into LDAP

MetaCP

JDBC2Ident_JDBCAgent

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

JDBC2Ident_JDBCAgent

JDBC2Ident_JDBCAgent

JDBCAgent

Full Export

JDBC2Ident

OutData

JDBC2Ident_MetaCP

JDBC2Ident_MetaCP

MetaCP

Full Import

InData

JDBC2Ident

Configuration Parameters

Table 1. Parameters of job JDBC2Ident_JDBCAgent
Parameter Default value

controller_tracelevel

1
Table 2. Parameters of job JDBC2Ident_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

test_max_entries

10

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 contains two activities. JDBC2Ident_JDBCAgent runs first and extracts the source data from the JDBC database. If that step succeeds, JDBC2Ident_MetaCP starts and imports the handover data into the Identity Store. If the first activity fails, the second activity does not start; if the second activity fails, the workflow run ends in error there.

Operation

  1. The scheduler starts activity JDBC2Ident_JDBCAgent in agent JDBCAgent.

  2. JDBCAgent reads the source data through channel JDBC2Ident and writes the extracted result to the handover channel OutData.

  3. After a successful handover, activity JDBC2Ident_MetaCP starts in agent MetaCP, reads the data through channel InData, and applies the configured mappings.

  4. The MetaCP job runs in full mode, so it imports a complete data set into the Identity Store and does not use delta handling. Any error stops the workflow at the activity that reports it.