Ident2JDBC

Workflow for Export from LDAP and Import into a JDBC database

Ident2JDBC exports data from the Identity Store to a JDBC database. You use it when another application stores its data in relational tables and you want DirX Identity to feed that database on a schedule.

The workflow uses MetaCP for the Identity Store export and JDBCAgent for the database write. The first step is delta-capable, so you can use the workflow for incremental exports as well as full refreshes.

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

Ident2JDBC

Category

Source Scheduled / JDBC

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

LDAP-JDBC

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Source Scheduled/JDBC/Ident2JDBC

Prerequisites

  • MetaCP is available and can reach the Identity Store.

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

  • The channels Ident2JDBC, OutData, and InData are configured for the export from the Identity Store and the handover to the database job.

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident2JDBC_MetaCP

Export from LDAP

MetaCP

start activity

2

Ident2JDBC_JDBCAgent

Import into a JDBC database

JDBCAgent

Ident2JDBC_MetaCP

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident2JDBC_MetaCP

Ident2JDBC_MetaCP

MetaCP

Full Export

Ident2JDBC

OutData

Ident2JDBC_JDBCAgent

Ident2JDBC_JDBCAgent

JDBCAgent

Full Export

InData

Ident2JDBC

Configuration Parameters

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

min_source_entries

0

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

test_max_entries

0

trace_level

1

trace_recordcount

0
Table 2. Parameters of job Ident2JDBC_JDBCAgent
Parameter Default value

controller_tracelevel

1

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. Ident2JDBC_MetaCP runs first and prepares the export data from the Identity Store. Ident2JDBC_JDBCAgent starts only after that step succeeds and writes the handover data to the JDBC target. If the first activity fails, the database step does not run; if the second activity fails, the workflow ends with that error.

Operation

  1. The scheduler starts activity Ident2JDBC_MetaCP in agent MetaCP.

  2. MetaCP reads the Identity Store data through channel Ident2JDBC, applies the configured mappings, and writes the handover result to channel OutData.

  3. Because delta handling is enabled for Ident2JDBC_MetaCP, you can use the workflow for delta exports or run it as a full export when needed.

  4. After a successful first step, activity Ident2JDBC_JDBCAgent reads the handover data through channel InData and writes it to the JDBC target. Any error stops the workflow at the failing activity.