CSVfile2Ident

Workflow for Import to LDAP from a CSV file

CSVfile2Ident imports identity data from a CSV file into the Identity Store. You use it when a source system delivers periodic CSV extracts and you want DirX Identity to load that data as a scheduled job instead of through a live connected directory.

The workflow runs entirely in MetaCP. It is intended for complete refreshes, so each run processes the full file content and applies the configured mappings to the Identity Store.

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

CSVfile2Ident

Prerequisites

The MetaCP agent is available for scheduled execution.
The channel CSVfile2Ident is configured for the CSV source and the Identity Store side of the job.
The CSV 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	`CSVfile2Ident_MetaCP`	Import to LDAP from a CSV file	`MetaCP`	start activity

CSVfile2Ident_MetaCP

Import to LDAP from a CSV file

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`CSVfile2Ident_MetaCP`	`CSVfile2Ident_MetaCP`	`MetaCP`	Full Export	`CSVfile2Ident`	`CSVfile2Ident`

CSVfile2Ident_MetaCP

MetaCP

Full Export

CSVfile2Ident

Configuration Parameters

Table 1. Parameters of job `CSVfile2Ident_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, CSVfile2Ident_MetaCP. This activity runs one MetaCP job and handles the complete load through channel CSVfile2Ident. Because there is no follow-on activity, any job error ends the workflow run at this point.

Operation

The scheduler starts job CSVfile2Ident_MetaCP in agent MetaCP.
MetaCP reads the CSV content through channel CSVfile2Ident and applies the configured mappings.
The job runs in full mode, so it expects a complete source extract and does not use delta handling.
MetaCP writes the resulting entries to the Identity Store in normal execution mode. If processing fails, the workflow ends with that job error.