LDIFfile2Ident

Workflow for Import to LDAP from an LDIF file

LDIFfile2Ident imports identity data from an LDIF file into the Identity Store. You use it when source data is delivered as LDIF and you want a scheduled file-based load into DirX Identity.

The workflow is executed entirely by MetaCP through channel LDIFfile2Ident. It is intended for full imports rather than delta updates.

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

LDIFfile2Ident

Prerequisites

The MetaCP agent is available for scheduled execution.
The channel LDIFfile2Ident is configured for the LDIF source and the Identity Store side of the job.
The LDIF file is available on the system where MetaCP runs.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`LDIFfile2Ident_MetaCP`	Import to LDAP from an LDIF file	`MetaCP`	start activity

LDIFfile2Ident_MetaCP

Import to LDAP from an LDIF file

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`LDIFfile2Ident_MetaCP`	`LDIFfile2Ident_MetaCP`	`MetaCP`	Full Export	`LDIFfile2Ident`	`LDIFfile2Ident`

LDIFfile2Ident_MetaCP

MetaCP

Full Export

LDIFfile2Ident

Configuration Parameters

Table 1. Parameters of job `LDIFfile2Ident_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
`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 has one activity, LDIFfile2Ident_MetaCP. This activity runs the complete import through channel LDIFfile2Ident in one MetaCP job. Because the workflow has no follow-on activity, any job error ends the run immediately.

Operation

The scheduler starts job LDIFfile2Ident_MetaCP in agent MetaCP.
MetaCP reads the LDIF content through channel LDIFfile2Ident and applies the configured mappings.
The job runs in full mode, so it does not use delta handling. Because min_source_entries is 0, the job does not require a minimum number of source entries before it can finish successfully.
MetaCP writes the mapped result to the Identity Store in normal execution mode. If processing fails, the workflow ends with that job error.