JDBC2Ident_Sync_NewAcc

synch back the newly created accounts to Role to get the JDBC keys

After Ident_JDBC_Sync creates new accounts in the JDBC-connected database, the database can assign keys that do not yet exist in the Identity Store. JDBC2Ident_Sync_NewAcc exports those newly created accounts with JDBCExport and imports them with MetaCP so that the target system subtree in the Identity Store receives the JDBC-assigned keys.

JDBC2Ident_Sync_NewAcc is a companion sub-workflow of Ident_JDBC_Sync and completes the write cycle for newly created accounts.

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_Sync_NewAcc

Category

Target 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/Target Scheduled/JDBC/JDBC2Ident_Sync_NewAcc

Prerequisites

  • Configure JDBCExport for the JDBC-connected database.

  • Configure MetaCP for the corresponding target system subtree in the Identity Store.

Workflow and Activities

Step Activity Description Agent Runs after

1

JDBC2Ident_SyncNewAccount_JDBCExport

export new accounts

JDBCAgent

start activity

2

JDBC2Ident_SyncNewAcc_MetaCP

import new accounts to Role

MetaCP

JDBC2Ident_SyncNewAccount_JDBCExport

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

JDBC2Ident_SyncNewAccount_JDBCExport

JDBC2Ident_SyncAccountNew_JDBCExport

JDBCAgent

Full Export

JDBC2Ident_SyncAccNew

OutData

JDBC2Ident_SyncNewAcc_MetaCP

JDBC2Ident_SyncAccountNew_MetaCP

MetaCP

Full Export

InData

JDBC2Ident_SyncAccount11

Configuration Parameters

Table 1. Parameters of job JDBC2Ident_SyncAccountNew_JDBCExport
Parameter Default value

8bit

TRUE

controller_tracelevel

9

datahash

4

delta_mode

delta-or-full

delta_on

1

maxtracefiles

100

trace

1

traceflow

0

tracelevel

W S FS CA Stats Ref
Table 2. Parameters of job JDBC2Ident_SyncAccountNew_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.

In this workflow, the C++-based Server runs these activities in sequence:

  1. JDBC2Ident_SyncNewAccount_JDBCExport exports the newly created accounts from the JDBC-connected database.

  2. JDBC2Ident_SyncNewAcc_MetaCP imports those accounts into the Identity Store so that JDBC-assigned keys are written back.

If one activity fails, the workflow stops at that point and the remaining activities do not run.

Operation

  1. Start JDBC2Ident_Sync_NewAcc directly or let Ident_JDBC_Sync call it after the outbound account creation step.

  2. The workflow exports the relevant new JDBC-side accounts with JDBCExport.

  3. MetaCP imports that data into the Identity Store and updates the target system subtree with the keys assigned by the database.

  4. If the export or import step fails, the workflow stops and the JDBC-assigned keys are not written back during that run.

  5. A successful run leaves the newly created account objects in the Identity Store aligned with the identifiers returned by the JDBC-connected database.