Ident2LDAPdir_File

Compares and calculates changes from Identity Store to LDAP and writes an LDIF change file

Ident2LDAPdir_File calculates the delta between the Identity Store and a connected LDAP directory and writes the result as an LDIF change file. Instead of applying the changes directly to LDAP, the workflow produces a file that an administrator can review and apply separately.

Use this workflow when you want the scheduled comparison and change calculation of an LDAP export, but you need the resulting updates as an LDIF file rather than as direct LDAP operations.

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

Ident2LDAPdir_File

Prerequisites

Configure MetaCP with the LDAP connector for the connected LDAP directory.
Create and configure the LDAP connected directory and make sure the corresponding target system subtree exists in the Identity Store.
Make sure the output location for the LDIF change file is writable by the C++-based Server.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`Ident2LDAPdir_File_MetaCP`	Synchronization from Identity Store into an LDAP Directory by producing an LDIF change file	`MetaCP`	start activity

Ident2LDAPdir_File_MetaCP

Synchronization from Identity Store into an LDAP Directory by producing an LDIF change file

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`Ident2LDAPdir_File_MetaCP`	`Ident2LDAPdir_File_MetaCP`	`MetaCP`	Full Export	`Ident2LDAPdir_File`	`LDIF-Change file`

Ident2LDAPdir_File_MetaCP

MetaCP

Full Export

Ident2LDAPdir_File

LDIF-Change file

Configuration Parameters

Table 1. Parameters of job `Ident2LDAPdir_File_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`	0
`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:

Ident2LDAPdir_File_MetaCP compares the Identity Store with the connected LDAP directory and writes the calculated changes to an LDIF file.

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

Operation

Start Ident2LDAPdir_File manually or on a schedule.
The single MetaCP activity compares the current state of the target system subtree in the Identity Store with the LDAP-side state defined by the connected directory mapping.
Instead of sending the calculated changes to LDAP, the workflow writes them as LDIF output.
If the comparison or file-writing step fails, no later step can compensate because the workflow contains only this one activity.
A successful run produces an LDIF change file that can be reviewed and applied outside the workflow.