ODBC2Ident_Sync_NewGroup

synch back newly created groups to Role to get the ODBC keys

After Ident_ODBC_Sync creates new groups in the ODBC-connected system, that system can assign keys that do not yet exist in the Identity Store. ODBC2Ident_Sync_NewGroup exports those newly created groups with ODBCExport and imports them with MetaCP so that the target system subtree in the Identity Store receives the ODBC-assigned keys.

ODBC2Ident_Sync_NewGroup is a companion sub-workflow of Ident_ODBC_Sync and completes the write cycle for newly created groups.

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_Sync_NewGroup

Category

Target 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/Target Scheduled/ODBC/ODBC2Ident_Sync_NewGroup

Prerequisites

  • Configure ODBCExport for the ODBC-connected system or database.

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

Workflow and Activities

Step Activity Description Agent Runs after

1

ODBC2Ident_SyncNewGroup_ODBCExport

export new groups

ODBCExport

start activity

2

ODBC2Ident_SyncNewGroup_MetaCP

synch new groups to Role

MetaCP

ODBC2Ident_SyncNewGroup_ODBCExport

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

ODBC2Ident_SyncNewGroup_ODBCExport

ODBC2Ident_SyncGroupNew_ODBCExport

ODBCExport

Full Export

ODBC2Ident_SyncGroupNew

OutData

ODBC2Ident_SyncNewGroup_MetaCP

ODBC2Ident_SyncGroupNew_MetaCP

MetaCP

Full Export

InData

ODBC2Ident_SyncGroupNew

Configuration Parameters

Table 1. Parameters of job ODBC2Ident_SyncGroupNew_ODBCExport
Parameter Default value

8bit

TRUE

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 ODBC2Ident_SyncGroupNew_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. ODBC2Ident_SyncNewGroup_ODBCExport exports the newly created groups from the ODBC-connected system.

  2. ODBC2Ident_SyncNewGroup_MetaCP imports those groups into the Identity Store so that ODBC-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 ODBC2Ident_Sync_NewGroup directly or let Ident_ODBC_Sync call it after the outbound group creation step.

  2. The workflow exports the relevant new ODBC-side groups with ODBCExport.

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

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

  5. A successful run leaves the newly created group objects in the Identity Store aligned with the identifiers returned by the ODBC-connected system.